Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
| От | Thom Brown |
|---|---|
| Тема | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Дата | |
| Msg-id | CAA-aLv7PwX24Ex2EWceOUtg0oEjdTbYiQ670j4dWf2nR369oUA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
|
| Список | pgsql-hackers |
On 20 May 2015 at 17:54, Andres Freund <andres@anarazel.de> wrote: > On 2015-05-20 17:44:05 +0100, Thom Brown wrote: >> On 8 May 2015 at 16:03, Andres Freund <andres@anarazel.de> wrote: >> > So I've committed the patch yesterday evening. I'm pretty sure there'll >> > be some more minor things to change. But overall I feel good about the >> > current state. >> > >> > It'd be quite helpful if others could read the docs, specifically for >> > insert, and comment whether they're understandable. I've spent a fair >> > amount of time trying to make them somewhat simpler, but I do think I >> > only succeeded partially. And there's also my own brand of english to >> > consider ;) >> >> The docs say "Note that exclusion constraints are not supported with >> ON CONFLICT DO UPDATE." >> >> But I get the following error message text: >> >> "ERROR: there is no unique or exclusion constraint matching the ON >> CONFLICT specification" >> >> This implies that an exclusion constraint is valid in the statement, >> which contradicts the docs. Which one is correct? > > ON CONFLICT can be used for ... DO NOTHING as well. Yes, but still confusing when not using DO NOTHING. -- Thom
В списке pgsql-hackers по дате отправления: