| From: | Diego <mrstephenamell(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Bug in create type when missed the comma between element list |
| Date: | 2024-11-04 16:28:29 |
| Message-ID: | 8658d294-81b0-492c-9c73-d6cd2c2472a1@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thank you David!
That note: This slightly bizarre behavior is specified by SQL;
PostgreSQL is following the standard.
On 11/4/24 13:19, David G. Johnston wrote:
> On Mon, Nov 4, 2024 at 9:17 AM Diego <mrstephenamell(at)gmail(dot)com> wrote:
>
>
> u: daf db: daf # CREATE TYPE test_enum AS ENUM(
> 'one'
> 'two',
> 'three',
> 'four'
> );
>
> maybe, some of you can help me to report it properly.
>
> That is working per SQL standard. If you hadn't used newlines between
> the elements you would have gotten an error; but the newlines between
> literals is valid string literal syntax.
>
> https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-STRINGS
>
> David J.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2024-11-04 16:41:33 | Re: Adding skip scan (including MDAM style range skip scan) to nbtree |
| Previous Message | Erik Wienhold | 2024-11-04 16:24:34 | Re: pg_dump --no-comments confusion |