Re: Oracle Discoverer Joins

Hi,
I think your talking about "Fan-Traps" e.g when we write sql we can prevent cartisean products via the where clause, Discoverer though cannot handle this because of the way it works. If so it is NOT fixed in 308
BUT
if you get v3.1 there is an option to stop fan-trap detection thus relying on you to specify the correct conditions (dodgy but necessary in many cases).

In the meantime you must do something like the following to work around this :

In Admin Layer

Detail1 (Master)

    |
Detail2 (Child / Master)

    |
Detail3 (Child)

even though in underlying schema it is

• Detail1 Detail2 |
• Detail3

Hope this helps,
Mark
doug_brough_at_my-dejanews.com wrote in message <7e0790$cfm$1_at_nnrp1.dejanews.com>...
>I have a demo copy of Discover 3.0.8 that I am trying out. I'm about ready
to
>throw it out! My problem, I have LOTS of the following (master table with
>multiple detail tables):
>
> -- detail 1
> /
> Master --- detail 2
> \
> -- detail 3
>
>Discover lets me create the joins, but when I try to query from them, I get
>"Invalid Join Configuration". I did some research and found out the above
is
>a bug in older Discoverer versions, but should be fixed in 3.0.8.
>
>Any light anyone can shed would be GREATLY appreciated. Any general
comments
>about Discoverer would also be greatly appreciated (e.g. we use this and
think
>it's great, we tried it and didn't like it because of X, etc). Thanks!
>
>Doug Brough
>brough_at_shellus.com
>
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Received on Fri Apr 02 1999 - 01:27:27 CEST