Ann,

> The semantics of the statement suggested by Vlad for Firebird
> are much better and the statement is useful. In our case,
> the ON UPDATE actions of constraints would be invoked as
> appropriate, and update triggers will fire. I suggest we
> use a different keyword so developers who have been exposed
> to MySQL don't assume we use their semantics.
>
> Here are some possibilities....
>
> SUPPLANT, SUBSTITUTE, SUPERSEDE, USURP, RECONSTRUCT, REBUILD,
> REDO, reconstitute; reconvert; renew, renovate; regenerate;
> rejuvenate, reestablish, restore, recreate...

While I realize this is one of Jim's favorite things -- worrying about
the name of something...

I would like to make a, perhaps extreme, proposal.

Since we already support "CREATE OR ALTER ..."

Why don't we use "INSERT OR UPDATE ..." for the new 'replace'
functionality?


Sean