Robert Treat wrote:
Perhaps a better option would be to implement Merge per spec, and then implement a "replace into" command for the oltp scenario. This way you keep the spec behavior for the spec syntax, and have a clearly non-spec command for non-spec behavior.
MySQL's "REPLACE INTO" is *NOT* semantically equivalent to any flavor of "insert or update". It is "delete plus insert". They do have "INSERT ... ON DUPLICATE KEY UPDATE ..."
Presumably, if we implement MERGE with transaction-safe semantics, which Simon has agreed to do, we would not need to consider anything like the latter, but we might still want to consider REPLACE INTO (in the MySQL sense).
cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
