Devart Forums

(Because our IT person who forwarded to you my multi-issue email has moved on, I will re-post here individually, thanks.)

If I have a stored procedure open in the editor for long enough for the connection to the MySQL server to time out (eg several hours), when I go to save it, I have to press Ctrl-S THREE TIMES before it saves. The first gives a message about the server connection timing out and going away. The second Ctrl-S gives an error message about 'No Database Selected' and the third Ctrl-S, it saves it correctly with no further error. I confirmed this by closing and reloading it, and the changes were saved correctly.

The old version 6.0.151 only gave ONE error message (the first) and then saved on the second try. So this is now worse.

Db Forge Studio for MySQL should recognise the server has gone away and retry for itself for a number of tries over a period of time before resorting to an error message - and then only if the server REALLY has gone away, not just a recoverable connection timeout.
Thanks

YOU REPLIED:
We will investigating this issue when developing the next product builds.

Status:
Awaiting new build.

The fix will be included in the next product build that should be released within one week.

Thanks!