Re: BUG #1629: subquery IN returns incorrect results

[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 a good 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