From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | David Pradier <dpradier(at)apartia(dot)fr> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Erratic error message "ERROR: column "id_compte" does |
Date: | 2005-03-16 14:52:55 |
Message-ID: | 42384847.5010001@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Pradier wrote:
> Ok, understood.
> One can access the columns of the main query from the subquery,
> therefore in my own query the column "id_compte" is found,
> therefore there is no error message.
>
> Doesn't this count as a bug ?
Tricky, you could have something like:
SELECT a.* FROM a WHERE (a1,a2) IN (SELECT a1,b3 FROM b ...)
If that's legal, then so is your query.
> On Wed, Mar 16, 2005 at 02:24:48PM +0000, Richard Huxton wrote:
>
>>David Pradier wrote:
>>
>>>Actually, the column "id_compte" is the primary key of the table "compte".
>>>The column "id_compte" doesn't exist in the table "operation".
>>>
>>>But i still don't understand why there is no error message, could you
>>>explain a little more ?
>>
>>I think it's intended for use in the WHERE clause:
>> SELECT a.* FROM a WHERE a1 IN (SELECT b3 FROM b WHERE b2=a2)
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-03-16 15:07:28 | Re: [pgsql-hackers-win32] snprintf causes regression tests |
Previous Message | Merlin Moncure | 2005-03-16 14:52:52 | Re: PQexecParams |