In a message dated 98-07-07 14:32:19 EDT, you write:
I have created a shortcut join between two tables by checking the
‘Shortcut join’ box on the Edit Join window. This created a dotted line between the tables on my data model.
When I create a query using objects from these two tables the generated SQL does not use the shortcut join. Instead, the SQL takes the long way around and contains joins for three other tables which are otherwise not needed.
I’ve spoke to Business Objects Tech Support but so far they cannot tell me why the shortcut join is not being used. Is there something else I need to do to get this to work?
Thanks.
Jane Kelly
Jane:
Here are a few things to check regarding BusObj’s refusal to use a shortcut join…
This may be an obvious thing, but it has happened to me before so I will ask: you are sure that you are using the updated universe (with the shortcut join) on the pc where you are creating the query? In other words, you did not forget to save and / or export the universe? As I said, this is probably not the problem.
Another issue that could be a problem is that somewhere along the line one of your objects is referencing more than one table, and that is forcing BusObj into the “long path”. The best way to test this is to create a new object from each table involved in the shortcut join and test your query with just those two objects. If your query now works, then one of the other objects you were trying to use is the culprit; check the “Tables” button for each object and you may find where this is the case. Alternatively, test your query by adding one object at a time and checking the SQL that is generated. Once the shortcut join is no longer used, the most recent object to be added is likely to be the candidate for the problem.
Is there a security setting in the supervisor module that is adding an additional table to your query?
I have not experimented with this nor actually seen this as a problem, but do you have cardinality information for all of your joins? I don’t know if that is supposed to affect short cut joins or not, but it is something else to check, perhaps.
Finally, does one of your other join clauses reference multiple (ie more than two) tables? If so, then that join may be forcing the “long path” instead of an object.
These are all things that came off the top of my head. If you can’t solve the problem, I suspect that you will need to post more information about your universe and object design to get more detailed help.
Regards,
Dave Rathbun
Integra Solutions
www.islink.com See you in Orlando in '98!
Listserv Archives (BOB member since 2002-06-25)