| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Alex Goncharov <alex(dot)goncharov(dot)usa(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-28 23:07:25 |
| Message-ID: | 545021AD.8080406@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/28/14, 4:25 PM, David E. Wheeler wrote:
>> This is a misfeature for the benefit of edit-lazy users only.
> This one, however, is more a judgment of people and their practices rather than the feature itself. Color me unimpressed.
+1.
Having users sweat of comma placement in this day and age is pretty stupid. I can understand why we wouldn't want to break backwards compatibility, but I think it does us and our users a disservice to dismiss the issue.
(BTW, I use a "comma first" formatting standard, so this doesn't actually effect me much, but I still find the original complaint very valid.)
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2014-10-28 23:22:00 | Re: group locking: incomplete patch, just for discussion |
| Previous Message | Jim Nasby | 2014-10-28 22:59:04 | Re: REINDEX CONCURRENTLY 2.0 |