From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(at)joh(dot)to> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SET syntax in INSERT |
Date: | 2016-01-14 18:51:21 |
Message-ID: | CA+Tgmob571i7mmHWx-3fG3tYqfdbgkxtrH_NZ-GLeSjDWijuAg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 14, 2016 at 12:13 PM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
> SET syntax for INSERT was brought up a few years ago here:
> http://www.postgresql.org/message-id/2c5ef4e30908251010s46d9d566m1da21357891bab3d@mail.gmail.com
>
> From the discussion it seems that one committer was against, one committer
> was not against, and one committer saw something good in the proposal.
> Personally, I believe this would be a huge readability improvement to
> INSERTs with more than a few columns. I'm willing to put in some work to
> make this happen for 9.7, but I'd like to know that I'm not wasting my time.
I'm mildly in favor of this proposal. I think that "-1 PostgreSQL
isn't MySQL!" is maybe the lamest reason for not supporting useful
syntax that I can think of.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2016-01-14 19:06:25 | Re: SET syntax in INSERT |
Previous Message | Robert Haas | 2016-01-14 18:46:44 | Re: Performance degradation in commit ac1d794 |