Jim Starkey wrote:

>>
> Withholding a final opinion until I see the actual syntax, I tend to
> favor the keyword REPLACE. Yes, MySQL has a REPLACE statement with
> approximately (?) the same syntax, but the MySQL statement is completely
> screwed up and works badly, if at all, with triggers or foreign keys.
> Having Firebird do it right will making fixing MySQL easier (believe it
> or not).

I don't believe that at all. No project is going to change the
semantics of an existing statement because some other (much smaller)
project implemented it differently. The way to get MySQL to change
is to use a different keyword and the right semantics. Then, they
might consider implementing ours and eventually deprecating theirs.


Regards,


Ann