[EMAIL PROTECTED] writes:
> INTERSECT fails
I believe this is fixed in current sources (7.2-to-be). The problem
is with INTERSECT (or EXCEPT) as the input to another INTERSECT/EXCEPT.
You could work around it in 7.1 by doing one INTERSECT into a temp
table and then intersecting with that.
Tamas Vincze ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
INTERSECT fails
Long Description
I've used INTERSECT to get the common rows in 3 simple SELECTs.
If I write the query without grouping parentheses, PG reports 0 rows
