Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint
От | Geoff Winkless |
---|---|
Тема | Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint |
Дата | |
Msg-id | CAEzk6ff1W0rmKuo1DOvX+5en8xZyZRQhwhOGY6pUKdO2sUkEfQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint (Simon Riggs <simon@2ndQuadrant.com>) |
Список | pgsql-hackers |
<p dir="ltr"><br /> On 21 May 2015 21:15, "Simon Riggs" <<a href="mailto:simon@2ndquadrant.com">simon@2ndquadrant.com</a>>wrote:<br /> > I would like to see this happen now beforewe get hit with usage questions similar to OP's. If both requests cannot happen now, if we can at least agree a pathfor future enhancement we can refer people to what will happen in later releases when they ask.<p dir="ltr">FWIW as theOP I was merely asking for clarification as to why it was required for UPDATE and not DO NOTHING. <p dir="ltr">The discussionhas been enough to clarify for me: putting something along the lines of what was discussed in this thread in thedocumentation alongside the requirement would, IMO, be sufficient.<p dir="ltr">I'm not trying to suggest that I representeveryone and that the discussion is over, but as you pointed at the OP I thought I should put in where I am withthis now.<p dir="ltr">Ta<p dir="ltr">Geoff<br />
В списке pgsql-hackers по дате отправления: