| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Geoff Tolley <geoff(dot)tolley(at)yougov(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5102: Silent IN (list of strings) failure to detect syntax error when list is linewrapped |
| Date: | 2009-10-08 15:19:28 |
| Message-ID: | 24247.1255015168@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-10-08 15:22:42 | Re: BUG #5105: "Select Into Strict" does not throw NO_DATA_FOUND |
| Previous Message | Tom Lane | 2009-10-08 15:12:22 | Re: BUG #5104: tsearch parser mislead |