From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Bogdan Pilch <bogdan(at)matfyz(dot)cz> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Trailing comma support in SELECT statements |
Date: | 2014-10-03 21:14:39 |
Message-ID: | CAFj8pRC1GWeT3w2w1A0+zbdR3ogmBdhyKzKpwLnmxY_p_TpDWQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2014-09-28 13:42 GMT+02:00 Bogdan Pilch <bogdan(at)matfyz(dot)cz>:
> Hi,
> I have created a small patch to postgres source (in particular the
> psql part of it) that accepts trailing comma at the end of list in
> SELECT statement.
>
It is ANSI/SQL ?
Why we should to enable? We can be tolerant to this bug, but then
developers will hate us, when they will try to port to other servers.
-1 from me
Regards
Pavel
>
> The idea is to be able to say both (with the same result):
> SELECT a, b, c from t;
> SELECT a, b, c, from t;
>
> Attached you can find a patch containing regression test (incorporated
> into the serial_schedule).
> My patch is relative to origin/REL9_4_STABLE branch as that is the one
> I started from.
>
> My plea is to have this change merged into the main stream so that it
> becomes available in upcoming releases.
>
> This modification does not require any interaction with user.
> It does not create any backward compatibility issues.
> Not does it have any performance impact.
>
> regards
> bogdan
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-10-03 21:15:13 | Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept) |
Previous Message | Brightwell, Adam | 2014-10-03 21:13:36 | Re: superuser() shortcuts |