> I think I may have found another bug: > > WITH RECURSIVE t(i,j) AS ( > VALUES (1,2) > UNION ALL > SELECT t2.i, t.j > FROM ( > SELECT 2 AS i > UNION ALL /* Wrongly getting detected, I think */ > SELECT 3 AS i > ) AS t2 > JOIN > t > ON (t2.i = t.i) > ) > SELECT * FROM t; > ERROR: attribute number 2 exceeds number of columns 1 > > Is there some way to ensure that in the case of WITH RECURSIVE, the > query to the right of UNION ALL follows only the SQL:2008 rules about > not having outer JOINs, etc. in it, but otherwise make it opaque to > the error-checking code? > > I know I didn't explain that well, but the above SQL should work and > the error appears to stem from the parser's looking at the innermost > UNION ALL instead of the outermost.
Thanks for the report. I will look into this. -- Tatsuo Ishii SRA OSS, Inc. Japan -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches
