From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Open 6.5 items |
Date: | 1999-06-04 04:15:12 |
Message-ID: | 15980.928469712@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> The issue is the issue:
> test=> drop table test;
> DROP
> test=> create table test(x int);
> CREATE
> test=> insert into test values (3);
> INSERT 72169 1
> test=> select * from test where test in (select x from test);
> NOTICE: unknown node tag 704 in fireRIRonSubselect()
> NOTICE: Node is: { IDENT "test" }
> ERROR: ExecEvalExpr: unknown expression type 704
Hmm. Doesn't happen if one does
select * from test where x in (select x from test);
Is there any rational interpretation to the first query? test is not an
available column name, so I don't know what it is supposed to mean.
I'm having a hard time seeing this as a showstopper bug... at best it's
an error that needs to be caught somewhere where a better error message
can be given...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-06-04 04:16:02 | Re: [HACKERS] Open 6.5 items |
Previous Message | Philip Warner | 1999-06-04 04:13:43 | Re: [HACKERS] Priorities for 6.6 |