> It sounds like the client didn't crash, but the server did. If mysqldcrashed, then any MyISAM tables that were in use at the time of the crash would definitely need reparing. If you want to ensure that crashes don't affect tables, use InnoDB or BDB tables instead.
the machine that crashed was a client during simple quering(select,update or delete)... this is the problem... can anybody assure me that it happens only in windows distribution or in that release(MySQL 4.0.15-nt )? if it's a common problem mysql isn't a dbms... :) Emiliano
The current release for MySQL 4.0 is 4.0.18. You might try upgrading to see if the problem persists. If it's a repeatable thing, then please report it on our bugs page and provide the information needed to reproduce the problem so that it can be fixed. Thanks.
http://bugs.mysql.com/
-- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com
MySQL Users Conference: April 14-16, 2004 http://www.mysql.com/uc2004/
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
