Philip Newton wrote:
It even lets you mix the two with REPLACE INTO, which will do an INSERT, unless the record is already present, in which case it'll do an UPDATE instead.
Rather, it does a DELETE then an INSERT. Which I'd rate slightly more hateful, since it's another entry towards any auto-insert fields running out of numbers. But it probably depends on the situation.
