MySQL Bugs: #69395: MySQL Workbench cannot execute SQL queries that take longer 99999 seconds

Bug #69395	MySQL Workbench cannot execute SQL queries that take longer 99999 seconds
Submitted:	4 Jun 2013 0:50	Modified:	11 Jul 2013 1:02
Reporter:	Franck Dernoncourt	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S4 (Feature request)
Version:	5.2.47	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
I would like to execute a query that takes more than 99,999 seconds to execute (e.g. SELECT SLEEP(150000);). To change the timeout in MySQL Workbench, we have to go to Edit → Preferences → SQL Editor → DBMS connection read time out (in seconds). However, the "DBMS connection read time out" field only accept up to 5 figures, and setting the field to 0 is equivalent to the default parameter (600 seconds). If the query takes more time than the timeout, I get the error message: "Error Code: 2013. Lost connection to MySQL server during query". Therefore, MySQL Workbench cannot execute SQL queries that take longer 99999 seconds, which is less than 3 days. 

(Screenshots if needed are available on http://stackoverflow.com/q/16877574/395857)

How to repeat:
Execute SELECT SLEEP(150000);

Suggested fix:
Setting the "DBMS connection read time out" field to 0 second should correspond to no time out (if this is possible). Also, the field should accept more figures: 7 or 8 figures should be enough.

Thanks for the feature reqeust.

Posted by developer:
 
Bug was fixed in trunk

Fixed as of MySQL Workbench 6.0.3 (BETA 2), and here's the changelog entry:

The "DBMS connection read time out" user preference was limited to 5
characters in length.

Thank you for the bug report.

I know this is more than 2 years old now. But I'm in the same predicament and don't understand the Oracle documentation or the online forum exchanges.

The bug recommended fix from this guy was "Setting the "DBMS connection read time out" field to 0 second should correspond to no time out (if this is possible). Also, the field should accept more figures: 7 or 8 figures should be enough."

It wasn't clear what the ultimate fix was, it simply said it was fixed.

Should I set the field to "0"  or set it to some very high number such as 1 million?

What does it mean when the documentation reads, "Set 0 to not check the read time out"?  Does it mean that by using "0" my query won't time out even if it takes 4 days to execute?