Re: BUG #1629: subquery IN returns incorrect results - Mailing list pgsql-bugs

From Mike G.
Subject Re: BUG #1629: subquery IN returns incorrect results
Date
Msg-id 20050427162156.GB18093@localhost.localdomain
Whole thread Raw
In response to Re: BUG #1629: subquery IN returns incorrect results  (Russell Smith <mr-russ@pws.com.au>)
List pgsql-bugs
[snip]

You are correct about the comma missing between the B and C in the query. It is turning it into B'C.  I can't think of
agood way for postgres to try and generate a warning in case a typo like this is made.   

Thank you.

Mike
>
> Unless this is a copy/paste error, you have missed a , in your query.  Which effectively turns it into
> ('A', 'B''C', 'D' ...
>
> Which mean that switching those two will give incorrect results. One will be missing C, and it will be included with
B,
> and the other D for the same reason.
>
> > 'C',  --switch me
> > 'D',  -- and switch me
> > 'E',
> > 'F',
> [snip]
>
> Regards
>
> Russell Smith.
>
> ---------------------------(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

pgsql-bugs by date:

Previous
From: "Mike G."
Date:
Subject: Re: BUG #1629: subquery IN returns incorrect results
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #1634: Configure step for build does not define HAVE_POSIX_SIGNALS