Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Gavin Flower <gavinflower@archidevsys.co.nz>
From: Gavin Flower <GavinFlower@archidevsys.co.nz>
To: Peter Geoghegan <pg@heroku.com>
Cc: Simon Riggs <simon@2ndquadrant.com>,
Pg Hackers <pgsql-hackers@postgresql.org>,
Craig Ringer <craig@2ndquadrant.com>
Date: 2014-09-29T01:15:34Z
Lists: pgsql-hackers
On 29/09/14 11:57, Peter Geoghegan wrote: > On Sun, Sep 28, 2014 at 3:41 PM, Gavin Flower > <GavinFlower@archidevsys.co.nz> wrote: >> How about have a stub page for MERGE, saying it is not implemented yet, but >> how about considering UPSERT - or something of that nature? >> >> I can suspect that people are much more likely to look for 'MERGE' in an >> index, or look for 'MERGE' in the list of SQL commands, than 'UPSERT'. > Seems reasonable. > > What I have a problem with is using the MERGE syntax to match people's > preexisting confused ideas about what MERGE does. If we do that, it'll > definitely bite us when we go to make what we'd be calling MERGE do > what MERGE is actually supposed to do. I favor clearly explaining > that. > Opinionated I may be, but I wanted stay well clear of the syntax minefield in this area - as I still have at least a vestigial instinct for self preservation! :-)
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