Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Sqlyog Lockup When Query Gets Terminated From Server Side

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Sqlyog Lockup When Query Gets Terminated From Server Side

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • September 16, 2010 at 10:54 am #12104
      interas
      Member

      When a query is being executed, but gets terminated from server side (kill, timeout etc.) SQLyog doesn't reflect that changed state.

      From SQLyog side, the query can then not be stopped with “Stop Execution” (it says the Thread ID does not exist), nor can the tab or the program be closed (is says that queries are still running).

      The only way to stop SQLyog is using the task manager and kill it from the system.

      SUGGESTION:

      When “Stop Execution” is pressed and it's detected that the Thread ID is not existent on the server, treat the query as if it had been stopped from client side, and make the program usable again.

    • September 16, 2010 at 11:43 am #31316
      peterlaursen
      Participant

      Looks like a very valid request.  We will need a little time to verify details and internals though.

      Maybe we should even output something like “This query is no longer running on the server.  It may have been killed by another client.” That would be useful to know when it happens.

    • September 17, 2010 at 5:07 am #31317
      nithin
      Member

      Could you please tell, SQLyog version and OS where the SQLyog is running?

    • September 21, 2010 at 9:20 pm #31318
      methai
      Member

      We've been running 8.5 and 8.6 and have seen this issue quite a bit. I'd thumb-up this request!!

  • Author
    Posts
Viewing 3 reply threads
  • You must be logged in to reply to this topic.