Hi mr. jolt,
I agree that I need an inner join, and do not know why an outer join is set up between these 2 tables.
(i am not the Discov. admin, yet i have asked him in the past to create outer joins for me)
Anyway, the fact that you brought up OUTER JOINs reminded me of a Discov. peculiarity:
I learned at the oracle forum called OTN a few months ago, that you have to alert Discoverer
to use an outer join by doing this "fake out"
, repeating the condition on the 2 tables that you like this in the Discoverer screen:
( Course_Credits <> Credit_Min OR Course_Credits <> Credit_Min )
then Discoverer knows that you are doing an outer join:
So now i ran the query, and do not have this error, but i have to check the results to see if my
approach is correct.
below is a screen shot of conditions:
in code window is the GENERATED sql behind the query.
will be back soon, to report my research of query results, tx, s
want outer joined twice.
Main Topics
Browse All Topics





by: mrjoltcolaPosted on 2009-10-19 at 09:05:53ID: 25606456
Which version of Oracle and which version of Discoverer?
Can you print the actual SQL query? It is possible that Discoverer is trying to write a full outer join with the old syntax. There are ways around it, but I am not sure with Discoverer, since I don't use it. One way is to use the ANSI join syntax, however, I am not sure you even need outer joins at all. If you just need to compare valid courses that differ in credits, then an INNER JOIN is adequate.
The query you are writing is simple to write if you need the SQL. If we provide the SQL for you can you plug it into Discoverer such that it is convenient for you to use? If so, can you provide your table descriptions?
Something like this...
Select allOpen in new window