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

Problem With Db Selection When Using Multiple Connections In Single Wi

forums forums SQLyog SQLyog: Bugs / Feature Requests Problem With Db Selection When Using Multiple Connections In Single Wi

  • This topic is empty.
Viewing 0 reply threads
  • Author
    Posts
    • #12844
      danT
      Member

      I have encountered a bug in SQLYog Ultimate 10.11.

      This bug occurs when executing scripts in different tabs connected to multiple database servers within the same SQLYog window.

      Database selection in the toolbar of SQLYog should be specific to the tab that has focus, regardless of what is executing on a different tab. If a script on a different tab chooses another database schema and you have a schema with the same name on current tab connection the drop down goes to the schema selected by the script in the different tab, even if it does not exist in current tab.

      If you run different scripts that work with different schemas on more than one tab at the same time, the database selected in the drop down takes precedence over the db selection stated in the script with the USE database statement.

      To recreate this issue or just to see how it happens:

      Create databases on one server with a couple schemas

      Create databases on another server with a couple schemas but with at least one schema that matches the name of one of the schemas on the other server

      Create a script that changes the schema selection

      Now in SQLYog

      1. Connect to 1 database. — tab 1

      2. Connect to 2 database in a new tab keeping the previous open within the same SQLYog window. — tab 2

      3. Execute a large script in the first tab (tab 1) that switches between different schemas and select the second tab (tab2) to change the focus to it.

      4. Notice when a new schema is selected in the script from tab1, the database selection drop down changes to the database referenced from tab 1 even though you have tab 2 selected

      5. Execute a script in the second tab against objects that do not exist in the schemas in tab 1, making both scripts execute at the same time

      6. tab 2 script returns error object not found or object not a member of schema from tab 1

      The database selected in the drop down should not affect a script executing, especially not if that script has the USE database statement. Furthermore the drop down should be specific to the connection tab wth the focus, regardless of what is happening on a different tab.

      Tabs are different connections (in my case to different servers – two of my schemas has the same name) and should be completely independent of one another.

      The work around is to open another SQLYog window and execute the second script from there.

Viewing 0 reply threads
  • You must be logged in to reply to this topic.