| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Trailing comma support in SELECT statements |
| Date: | 2014-10-20 15:59:53 |
| Message-ID: | AFD796C4-8C81-40D0-BCA8-6D509EBC17FD@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 18, 2014, at 7:06 PM, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> wrote:
> Yes.
>
> The only case I can think of where we wouldn't want this is COPY.
>
> BTW, this should also apply to delimiters other than commas; for example, some geometry types use ; as a delimiter between points.
I don’t think it should apply to the internals of types, necessarily. JSON, for example, always dies on an trailing comma, so should probably stay that way. Well, maybe allow it on JSONB input, but not JSON. Though we perhaps don’t want their behaviors to diverge.
D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G Johnston | 2014-10-20 16:02:32 | Re: Would you help to review our modifications |
| Previous Message | Brightwell, Adam | 2014-10-20 15:30:42 | Re: alter user/role CURRENT_USER |