Oracle Discoverer Administrator Administration Guide 10g (9.0.4) Part Number B10270-01 |
|
Use this dialog to specify whether detail items exist in the master folder and optionally specify an outer join and the join relationship (also known as the cardinality of the join).
This dialog is also displayed as:
For more information, see:
"What effect do joins have on query results and query performance?"
Use this option to specify whether Discoverer can assume that detail item values exist in the master folder for this join. For more information about which radio button to select, see "Examples of how joins can affect query results from complex folders".
Use this radio button to display rows for detail items assuming that values in the detail folder always have corresponding values in the master folder (for more information, see "What effect do joins have on query results and query performance?")
Use this radio button not to display rows for detail items assuming that values in the detail folder do not always have corresponding values in the master folder (for more information, see "What effect do joins have on query results and query performance?").
For more information about when to use these settings, see "Examples of how joins can affect query results from complex folders".
Use this check box to create an outer join on the detail table. This returns all master rows that have no corresponding detail items, as well as all matching master and detail rows. For more information, see "What are outer joins?".
Use this check box to create an outer join on the master table. This returns all detail rows that have no corresponding master items, as well as all matching detail and master rows. This construct is rare in real business scenarios. To use this construct you must select the Detail item values might not exist in the master folder radio button. For more information, see "What are outer joins?".
Select this check box to create a one-to-one relationship instead of a one-to-many relationship between the master and detail tables. There is no real master and detail in this case, because each row in the master table can correspond to no more than one row in the detail table.
This setting has no effect on the SQL that Discoverer generates, because SQL does not know about the cardinality of joins. It only affects the fan trap detection (for more information, see "What are fan traps, and how does Discoverer handle them?").
For more information about join relationships, see "What are one-to-many joins, one-to-one joins, and many-to-many joins?".
|
![]() Copyright © 1996, 2003 Oracle Corporation. All Rights Reserved. |
|