Re: BUG #5102: Silent IN (list of strings) failure to detect syntax error when list is linewrapped - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5102: Silent IN (list of strings) failure to detect syntax error when list is linewrapped
Date
Msg-id 24247.1255015168@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #5102: Silent IN (list of strings) failure to detect syntax error when list is linewrapped  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: BUG #5102: Silent IN (list of strings) failure to detect syntax error when list is linewrapped
List pgsql-bugs
Alvaro Herrera <alvherre@commandprompt.com> writes:
> I don't know much about this oddity but my first guess is that it's
> mandated by the SQL standard.

Yeah.  The spec defines that you can split a literal across lines this
way.  Notable quotes from SQL92:

         <separator> ::= { <comment> | <space> | <newline> }...


         1) In a <character string literal> or <national character string
            literal>, the sequence:

              <quote> <character representation>... <quote>
              <separator>... <quote> <character representation>... <quote>

            is equivalent to the sequence

              <quote> <character representation>... <character representa-
              tion>... <quote>


         4) In a <character string literal>, <national character string
            literal>, <bit string literal>, or <hex string literal>, a <sep-
            arator> shall contain a <newline>.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5104: tsearch parser mislead
Next
From: Tom Lane
Date:
Subject: Re: BUG #5105: "Select Into Strict" does not throw NO_DATA_FOUND