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? Regards David M Bennett FACS Andl - A New Database Language - andl.org |
