Hi,

I am using the latest JDBC drivers from last month with MySQL 3.23.40 and every
so often I run into this bug:

1) I go into table X, delete record Y (using the MySQL console) 2) I then fire up my Java program which uses the JDBC drivers to access that
same table, looking for that same record I just deleted and I get these error
messages:

java.sql.SQLException: General error: Got error 134 from table handler at org.gjt.mm.mysql.MysqlIO.sendCommand(Unknown Source) at org.gjt.mm.mysql.MysqlIO.sqlQueryDirect(Unknown Source) at org.gjt.mm.mysql.MysqlIO.sqlQuery(Unknown Source) at org.gjt.mm.mysql.Connection.execSQL(Unknown Source) at org.gjt.mm.mysql.Connection.execSQL(Unknown Source) at org.gjt.mm.mysql.Statement.executeQuery(Unknown Source) at org.gjt.mm.mysql.jdbc2.Statement.executeQuery(Unknown Source) at
com.shadowcraft.guardian.EmailAddressValidator.addValidCache(EmailAddressValidator.java:228) at
com.shadowcraft.guardian.EmailAddressValidator.isValid(EmailAddressValidator.java:517) at com.shadowcraft.guardian.Guardian.run(Guardian.java:212) at com.shadowcraft.guardian.Guardian.main(Guardian.java:778) SQLState=S1000 SQL String=INSERT INTO VALID_CACHE (EMAIL, VALID, DATE)VALUES
('Java...@aol.com', '1', '2002-02-09')

The SQLState and SQLString are my addition so you know what I'm executing. I
got the same error for:

SQL String=SELECT EMAIL, VALID, DATE FROM VALID_CACHE WHERE EMAIL =
'Java...@aol.com'

and it seems that no matter what my SQL statement is I get the same error. The
next morning I woke up and the error went away so whatever it is it is temporal
and probably disappears within the hour.

Has anyone seen this before? Are there known bugs in MySQL with error 134? What
is error 134?