Well spotted! :-)
It looks like the bug must actually be with Hibernate, which generated
the offending code.
I'll take it up with those guys.
Thanks for your help!
Pete
Stephan Szabo wrote:
On Fri, 16 Sep 2005, Pete Beck wrote:
The following bug has been logged online:
Bug reference: 1886
Logged by: Pete Beck
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1 & 8.0.3
Operating system: Linux and Windows
Description: Bug in SQL parsing
Details:
Postgres incorrectly reports a relation is being missing in a SQL.
The following query reports:
ERROR: relation "product0_" does not exist
I believe this error is correct.
It looks to me like you have:
A Left join B on condition, C left join D on condition2
where condition2 refers to A.
IIRC, in standard SQL, the scope for condition contains A and B and the
scope for condition2 contains C and D but not A.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
