MySQL Bugs: #12202: all edits/deletes fail because of apparent lost contact with server

Bug #12202	all edits/deletes fail because of apparent lost contact with server
Submitted:	27 Jul 2005 10:35	Modified:	26 Sep 2005 15:17
Reporter:	bastiaan schupp	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.1.13	OS:	Windows (Windows XP Home SP2)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
When trying to edit or delete records or fields in records using a result table, Query Browser returns a message: MySQL server has gone away, errorNr 2006. The field(s) / row(s) that failed to update are marked with blue text on a red background.

Corresponding manual changes using SQL (e.g. Update or Delete) work as expected. 

Server is on network.

How to repeat:
See above

Suggested fix:
Got no Idea...

What's mysql server version?

server version is 4.0.18, sorry

tested against 4.0.23 (latest 4.0 server) and was not able to reproduce this error.
Bastiaan, could you please to try 4.0.23 and check if this error appears on your computer?

Hi,

I get the same poblem. Using win 2000, SP 4. MySQL Query browser 1.1.13.

Trying to connect to MySql Server 4.0.24 through SecureCRT.

I can edit the row using an other GUI like Navicate or MySql controlcenter. I can also edit the row by manually typing in the update query.

Hi,

Sorry for late reply, I was away. You asked for further feedback. I'm currently unable to go to 4.0.23 as I do not own that server. I could try to get one up later but I am not able to reliably reproduce the problem on 4.0.18 now. 
It seems that it sometimes occurs, and sometimes not. Perhaps some time-out issue? Yesterday I connected to the server via VPN and it did not work, now I am back in office and it does work... When I reported this bug I was in the office as well so the VPN is probably not the cause here. Notice that I was again able to do manual updates by typing the query (in query browser) when the edit function failed even over the VPN, so it must definitely be something in how query browser does these updates.

Good Luck,

Bastiaan

Hi,

After some further experimentation I was able to reproduce. The error occurs after the network connection has been lost during operation of the client. (e.g. by disconnecting the network cable, or releasing and renewing the lease) Restarting the client solves the problem, it works without the error afterwards until the connection is lost again. 
This could for instance imply that if the connection (id) changes, query browser get the problem.
Hope this additional information is helpful. 
BTW, don't think the problem is S1 (critical) anymore.

Cheers,

B.A. Schupp

Hi!

I was able to reproduce this bug by phisically disconnecting the network cable to my Linux machine while doing queries w/QB 1.1.13.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

I added a dialog to the result set grid and the query editor which pops up when the connection to the server was lost asking the user whether to reconnect or not. Hope this helps with such network problems.