On Thu, Sep 1, 2016 at 12:10 PM, dandl <david@xxxxxxxx> 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
