This *might* make your updates a bit faster. I don't think MySQL optimizes updates this way (it would be nice if it did.)
Depending on your data it may be possible to eliminate updating some of the rows if the row already has the new value. As strange as this seems, something as simple as: update table set column = "x" where column <> "x" can eliminate some of the work involved in updating of the row (and perhaps the locking) just by checking to see if the row already has the value that you're updating it to. It is faster to put this logic in the Where clause than have MySQL try to optimize it during the update. This seems like an incredibly simple solution that can save you time when updating a table. Brent _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php