Opinion: Of all the DBMS's UPSERT/MERGE semantics, postgresql's is the
least useful because it's very limited: It can only do a check against a
constraint, and the cost of evaluating that constraint has to be carried
by all other statements which mutate the table. Oracle/Teradata MERGE is
a far more useful semantics because it's defined more like a self-join,
where the constraint is specified in the statement, not the DBMS.
On 04/19/2018 11:29 AM, Richard Hipp wrote:
The latest pre-release snapshot [1] contains support for UPSERT
following the PostgreSQL syntax. The documentation is still pending.
Nevertheless, early feedback is welcomed. You can respond either to
this mailing list, or directly to me.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
