Hi!

Ok, confirmed (finally :-)  )

My fault was that I was using our latest developmnet tree.
When I've tried this on 3.23.39 as went public, the bug appeared.

So, looks like the bug was fixed even before it was found :-)
Probably, it is somehow related to over bug I've fixed
since 3.23.39 release.

On Jul 20, Carsten Gehling wrote:
> I'm going to Spain today and cannot respond to any questions in the next
> week. I was going to wait with this until I got home again, but what the
> heck ;-)
> 
> Run the following script through your MySQL on an empty database with
> 
> mysql -uusername -ppassword dbname <scriptname
> 
> and the last command should produce the following error:
> 
> ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to
> repair it
> 
Regards,
Sergei

--
MySQL Development Team
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /   Sergei Golubchik <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Osnabrueck, Germany
       <___/

---------------------------------------------------------------------
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

Reply via email to