Re: SET syntax in INSERT - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: SET syntax in INSERT
Date
Msg-id CAFj8pRCa_mxU8HH2PX-XS3PncrfHBkCxQqo4vwGH4UR8AviY4g@mail.gmail.com
Whole thread Raw
In response to Re: SET syntax in INSERT  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: SET syntax in INSERT  (Marko Tiikkaja <marko@joh.to>)
List pgsql-hackers


2016-01-14 19:51 GMT+01:00 Robert Haas <robertmhaas@gmail.com>:
On Thu, Jan 14, 2016 at 12:13 PM, Marko Tiikkaja <marko@joh.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.

Now I am able to write more correct argument. It is one from basic SQL statement, and for using proprietary syntax should be pretty strong reason.

Probably there is less risk than 7 years ago, but still creating own syntax isn't the best idea. This is syntactic sugar only and different from ANSi SQL or common standard.

Regards

Pavel

 

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: SET syntax in INSERT
Next
From: Marko Tiikkaja
Date:
Subject: Re: SET syntax in INSERT