> > 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?
>
> This gets my vote (since MERGE is apparently not available).
> It is clear about what it does, and does not introduce yet
> more keywords into the vocabulary.
>
>
> PS. I think that REPLACE is the correct word for the behaviour
> in MySQL - and would be the incorrect word for what you want to
> achieve. Replace does imply removal of the existing, or the
> restoration of something previously removed.

It depends on how you look at it. If I replace the bulb in my car
headlights, I will take out the current bulb and put a new one in. Then
again, I will have to put back the cover as well (dependencies? FKs? ;)

In the case of no new keywords, INSERT OR UPDATE sounds good
to me.

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com