From: | David Pradier <dpradier(at)apartia(dot)fr> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Erratic error message "ERROR: column "id_compte" does |
Date: | 2005-03-16 12:18:24 |
Message-ID: | 20050316121824.GD17220@apartia.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 ?
David
On Wed, Mar 16, 2005 at 11:49:28AM +0000, Richard Huxton wrote:
> David Pradier wrote:
> >But when i put this query inside another query, i don't have anymore the
> >error message :
> >select distinct id_operation from compte where id_compte in
> >(select id_compte from operation where not compta_g5);
> >No error message.
>
> It looks like it's binding to the outer query - where you seem to have
> an id_compte.
>
> --
> Richard Huxton
> Archonet Ltd
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
--
dpradier(at)apartia(dot)fr - tel: 01.46.47.21.33 - fax: 01.46.47.21.37
From | Date | Subject | |
---|---|---|---|
Next Message | Satoshi Nagayasu | 2005-03-16 12:28:17 | read-only database |
Previous Message | strk | 2005-03-16 12:04:03 | caches lifetime with SQL vs PL/PGSQL procs |