Re: BUG #10201: Invalid input accepted with IN expression - Mailing list pgsql-bugs

From Daniel Baston
Subject Re: BUG #10201: Invalid input accepted with IN expression
Date
Msg-id CA+K_q_p8jRb=td0=NWhV_Hq+n+hPkEowDn_yQ4BV6c_b+xUR8Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #10201: Invalid input accepted with IN expression  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Got it.  Apologies for the false positive.


On Fri, May 2, 2014 at 4:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> dbaston@gmail.com writes:
> > If two items in an IN expression are separated by a newline instead of a
> > comma, those items will be ignored with no error.
>
> > CREATE TABLE testing (id varchar(1));
> > INSERT INTO testing VALUES ('1'), ('2'), ('3'), ('4'), ('5');
>
> > -- Missing comma produces a syntax error
> > SELECT * FROM testing WHERE id IN ('1'  '2', '3');
>
> > -- Unless there is a newline
> > SELECT * FROM testing WHERE id IN ('1'
> > '2', '3');
>
> This is not a bug; what you've got there is the SQL-standard way of
> breaking a literal across lines.  Compare
>
> select '1'
> '2', '3';
>  ?column? | ?column?
> ----------+----------
>  12       | 3
> (1 row)
>
>                         regards, tom lane
>

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #10201: Invalid input accepted with IN expression
Next
From: vetri_2020@yahoo.com
Date:
Subject: BUG #10207: Simple select query returns duplicate row - Critical issue