| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | andreas(dot)imboden(at)bl(dot)ch |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14394: No error raised in IN-clause when commas are missing |
| Date: | 2016-10-24 14:47:37 |
| Message-ID: | CAKFQuwY9fqaZ-zg6rWJV7uJvxCo=utKV8B=h=CdP07o-+qqG7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Oct 24, 2016 at 7:28 AM, <andreas(dot)imboden(at)bl(dot)ch> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14394
> Logged by: Andreas Imboden
> Email address: andreas(dot)imboden(at)bl(dot)ch
> PostgreSQL version: 9.6.0
> Operating system: Red Hat Entreprise Linux
> Description:
>
> /*
> pg-version:
> "PostgreSQL 9.6.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5
> 201506
> (...)""
>
> bug description:
> in list with new line instead of comma produces incorrect result.
> should instead report a syntax error message
>
> */
> [...]
>
> 'two'
> 'three',
>
Working as designed
and mandated by the SQL standard.
The above resolve
s
into
a single string
"two
three
"
.
https://www.postgresql.org/docs/9.6/static/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2016-10-24 14:48:49 | Re: BUG #14394: No error raised in IN-clause when commas are missing |
| Previous Message | Tom Lane | 2016-10-24 14:46:31 | Re: BUG #14394: No error raised in IN-clause when commas are missing |