Hi! A serious bug has been found in the big BLOB and TEXT support of InnoDB. If you update the primary key of a row whose length is > 8000 bytes, then the table becomes corrupt. Also the tablespace may become corrupt. Note that also a REPLACE can internally be handled as an update. A fixed version 3.23.42 of MySQL/InnoDB will be released by Friday. I have already fixed the bug. Unfortunately the fix will not save your corrupt tables. So if you possibly have performed the buggy operation on your table, you HAVE to reimport your table with version 3.23.42, and it is safest to recreate the whole database. Always keep dumps of your tables or backups! They are the only help in this kind of situation. With apologies, Heikki Tuuri Innobase Oy --------------------------------------------------------------------- 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
