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 = Record-file is crashed) Adam Clauss [EMAIL PROTECTED] > -----Original 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 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 > tables gives: > 1 clients is using or hasn't closed the table properly > > This sounds like I locked it, but didn't unlock it? But I am > positive I > did. > I use the following procedure: > > AddItem() > LockTable > InsertItem > UnlockTable > > > Just to double check, I have the a function for LockTable and > a function for > UnlockTable. These functions keep a counter and increment > it/decrement it > each time it is called. I verified that prior to running > this query (an > UPDATE query) that the counter is 0 - which indicates that everytime I > locked the table, I unlocked it. > > Note that this same code did not cause this problem with 4.0.12 (had > problems in other places, which are the reasons I just upgraded this). > > Any ideas? > Adam Clauss > [EMAIL PROTECTED] > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?> [EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
