Hanging temporary hang due to timeout

[jpipes]

Whenever I have a query window open and leave it for some amount of time, and then return to it, and execute, SQLYog hangs for what seems like an eternity, then comes back saying connection timed out, then “No database selected”.

A) Is there somewhere I can change this default behaviour to continually “NOOP” (like in FTP) the server to keep the connection alive, so that this behaviour doesn't happen?

and

😎 If I close the window before SQLYog comes back with the error message, and I log in to the *nix server, I see a mysql process thread hand around for about 10 minutes while it keeps querying the handle for the connection for a response… Is there any way for you to associate a terminate event with the application process so that the connected server is told to disconnect the process associated with the SQLYog queries?

Thanks in advance for your input!

Jay Pipes

[CalEvans]

Hi,

A)

There is no NOOP command in SQL.

I guess they could determine what database you are connected to and select * where 1=2 but that's really troublesome.

I've already put in a request for an auto-reconnect and re-select the database I was last in. I've been told that they are considering it. This would do the trick. (I have 1 server I work with that has a 2 minute disconnect! It really gets annoying after a while)

In the mean time, I've worked around this problem by adding databasename. to each of my table names in my from clause. I'm never exited about having to change my habits to work around flaws in a tool but SQLyog is a very important tool for me and it's still the best out there for mysql. So I begrudgingly work around it.

HTH,

=C=

[jpipes]

Hey, thanks a bunch for the post

I was aware that there was no NOOP command in SQL ( 😉 ), but thought it might serve to illustrate the situation better…

Thanks again!

[Author]

Posts