Robert Huff <com> wrote:
Nasty, nasty: REPLACE INTO... If you're using a primary ID, this will
actually delete the row with that ID, and insert a new one with that ID.
Any constraints may be checked and/or cascaded AFAIK. I'm actually very
against this kind of 'update'. Also, specifying column names is a good
thing. It will save you loads of debugging when for instance it's decided
there should be a field more or less in a table.
Posted on Usenet, not any forum you might see this in.
Ask Smart Questions: http://tinyurl.com/anel