| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Subject: | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |
| Date: | 2014-10-08 08:36:49 |
| Message-ID: | CABRT9RD-4M-STEXth7tvmM8Z6xCGTKzj9OpfWRuhcPiKMPDg6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 8, 2014 at 3:47 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> It seems like what you're talking about here is just changing the
> spelling of what I already have.
I think there's a subtle difference in expectations too. The current
BEFORE INSERT trigger behavior is somewhat defensible with an
INSERT-driven syntax (though I don't like it even now [1]). But the
MERGE syntax, to me, strongly implies that insertion doesn't begin
before determining whether a conflict exists or not.
Regards,
Marti
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paweł Cesar Sanjuan Szklarz | 2014-10-08 08:38:22 | Context lenses to set/get values in json values. |
| Previous Message | Heikki Linnakangas | 2014-10-08 08:25:59 | Re: Promise index tuples for UPSERT |