On Thu, Oct 30, 2003 at 12:03:58AM -0600, Adam Clauss wrote:
Narrowed it down - it doesn't seem to have anything to do with the table
locking. I removed ALL locking/unlocking and it made no difference. Still
getting there error.
What would cause the 127 error? (perror says: 127 =
I just upgraded an embedded server application to use 4.0.16 (from 4.0.12)
and now I am quite consistently getting a corrupt table. I am now getting
Got error 127 from table handler returned as the error. Copying the data
directory into a true SQL server and executing a CHECK on the involved
Message-
From: Adam Clauss [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2003 9:21 PM
To: [EMAIL PROTECTED]
Subject: MyISAM table corrupting in 4.0.16???
I just upgraded an embedded server application to use 4.0.16
(from 4.0.12)
and now I am quite consistently getting
