Re: UPDATE OR REPLACE?
| От | Michael Paquier |
|---|---|
| Тема | Re: UPDATE OR REPLACE? |
| Дата | |
| Msg-id | CAB7nPqRnwqj=OEH4mekhdc=TH3PRVX4qrji97nksPDxnihKBig@mail.gmail.com обсуждение исходный текст |
| Ответ на | UPDATE OR REPLACE? ("dandl" <david@andl.org>) |
| Ответы |
Re: UPDATE OR REPLACE?
|
| Список | pgsql-general |
On Thu, Sep 1, 2016 at 12:10 PM, dandl <david@andl.org> wrote: > Sqlite has options to handle an update that causes a duplicate key. Is there > anything similar in Postgres? > This is not an UPSERT. The scenario is an UPDATE that changes some key field > so that there is now a duplicate key. In Sqlite this handled as: > UPDATE OR IGNORE table SET <etc> > UPDATE OR REPLACE table SET <etc> > > And so on > > See https://www.sqlite.org/lang_update.html. > > Can Postgres do this? Somewhat with a plpgsql function, but with a native UPDATE query, the answer is no. -- Michael
В списке pgsql-general по дате отправления: