MySQL Bugs: #11975: UPDATE,ALTER, etc. fail to work after mysql server has gone away,SELECT works

Bug #11975	UPDATE,ALTER, etc. fail to work after mysql server has gone away,SELECT works
Submitted:	15 Jul 2005 18:24	Modified:	22 Jul 2005 21:02
Reporter:	Jeremy Knope	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.1.13	OS:	Windows (Windows XP SP2)
Assigned to:		CPU Architecture:	Any

Description:
After connecting to a remote MySQL server with some timeout issues, MySQL Query Browser will fail to do any kind of altering query like UPDATE, DELETE, ALTER, CREATE after getting an initial 'MySQL Server has gone away' error.  After that error, SELECT still continues to work and return data without any problems, but attempting to try UPDATE/DELETE etc. even after seeing SELECT still works results in a gone away error again.  Only solution is to do File->Reconnect and after a fresh connection CREATE/UPDATE/ALTER/DELETE will successfully work until a connection drop occurs again.

Server used: 4.0.22-standard

How to repeat:
1. Find a server to test against that times out easily, or produces MySQL Server has gone away if on for a short bit, in our case our servers in the data center time out with at least UPDATEs easily.
2. Connection, do a few SELECTs or UPDATEs, let it sit idle for maybe 10 minutes.
3. Try to UPDATE some rows or even modify a table, should get a MySQL Server has gone away or a lost connection during query
4. Try to SELECT, usually works
5. Try UPDATE or ALTER etc. again and should get a MySQL server has gone away again even with working SELECTs

Hi!

I was unable to reproduce this bug under Xp by stopping the server and then restarting it.

I"ll try to find out more about our loss of connection issues to see if I can provide enough information about the cause of the connection issues that might shed light on the error caused.  IN other clients it sometimes causes problems like timeout lockups (like in CocoaMySQL) but seems less frequent than problems that happen with query browser.