Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Peter Geoghegan <pg@heroku.com>
From: Peter Geoghegan <pg@heroku.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>,
Craig Ringer <craig@2ndquadrant.com>
Date: 2014-10-08T19:19:01Z
Lists: pgsql-hackers
On Wed, Oct 8, 2014 at 12:12 PM, Peter Geoghegan <pg@heroku.com> wrote: > On Mon, Sep 29, 2014 at 7:21 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >> Having said that, it would be much nicer to have a mode that allows >> you to just say the word "UPDATE" and have it copy the data into the >> correct columns, like MySQL does. That is very intuitive, even if it >> isn't very flexible. > > I thought about this, and at first I agreed, but now I'm not so sure. Actually, I don't think MySQL supports this. It doesn't allow INSERT ON DUPLICATE KEY UPDATE to do it, AFAICT. Their REPLACE syntax supports that, but that's a feature that is quite distinct to what I have in mind here. -- Peter Geoghegan
Commits
-
Change the way we mark tuples as frozen.
- 37484ad2aace 9.4.0 cited
-
Add documentation for data-modifying statements in WITH clauses.
- 0ef0b3020402 9.1.0 cited