[ChrisB]

Perhaps a new checkbox preference could be added for each connection record: “Slow/remote connection: object/tables tab should not auto-refresh”.

A system-wide preference about whether that checkbox is auto-selected by default for new connections could also be added.

Then, whatever that setting is would determine the refresh behavior of both the “table data” and “object info” tabs. If the “slow connection” option is checked, then perhaps instead of auto-refreshing the content in the “object info” and “table data” tabs, a refresh button could appear … thus giving control to the user.

Alternatively, when connecting to a given database, one could do an nslookup on the server address (or tunneling URL as the case may be), convert it to an IP address if necessary, and check to see whether its address is “local” to the subnet of the computer running SQLyog. And, if it's found to be “local” it could be treated as “fast”, and if it's not local to the subnet, treat it as “slow”. In this case, the per-connection-preference could be overridden by the discovered speed.

(I don't have any problem with the “object info” tab being refreshed. I often find unexpected delays for table data when clicking on different tables in the table list. Fortunately, unchecking the “show all” box, and using a smaller number in the limit boxes is helpful. This is the reason why I included the “table data” tab in my comments above.)

I wouldn't consider this to be a huge or serious issue … but something of a possible enhancement down the road. As the original poster has noted, there *are* workarounds.

[ChrisB]

• Start SQLyog
• Dialog of saved connections appears automatically for me
• The “Saved Connections” pulldown currently says “Baskets And Hoops”
• Hover over the pulldown and click on it to open the pulldown menu
• All my available connections are listed … “Baskets And Hoops” is still selected in the top of the pulldown
• Don't move the mouse
• Press the letter R twice to select “Randy Server 1”, and then “RunningRoom”
• Note that the top of the pulldown, where originally clicked to open the pulldown, now says “RunningRoom”
• Click the mouse button ON the top of the pulldown, on “RunningRoom” (NOT down in the list … just on the top of the menu)
• The pulldown closes, leaving “RunningRoom” in the top of the pulldown, suggesting that it's been Selected
• The rest of the dialog box fields still show the DB connection settings for “Baskets And Hoops”
• If I click Connect, I get connected to the “Baskets And Hoops” server

[ChrisB]

I'm using 6.13 now.

I explained it incorrectly … the problem is not primarily when pressing Enter, but rather if you leave your mouse over the pulldown input box after clicking to open it, and then navigate with keystrokes, but use the mouse button to click and choose the selected entry whose name has been auto-entered into the input field because of keystroke navigation. After clicking, the displayed name updates, but all the fields in the rest of the dialog box do not.

It's as if it's decided that nothing has really been selected … but only changes the displayed name instead of actually selecting it, or reverting back.

I think that it should select the displayed option, rather than reverting back to what was there prior to clicking to open the pulldown initially.

Sorry for the mistaken explanation.

[ChrisB]

Thank you.

Installing 6.13 has improved speed significantly. A delay is still present, but almost unnoticeable now.

I tried my backup file which contained the blank line, and it seems to work properly … no loss of data.

Thanks again.

I have another issue with the connection dialog box, but I'll log it in another thread since it's a GUI issue more than a logic issue as these were.

[ChrisB]

A secondary problem is that having 50+ connections defined makes loading the Connection dialog in SQLyog very very slow. I'd noticed it getting slower and slower more and more with each 6.x release, but now it's painful.

Windows XP SP2, 3.0 GHz CPU, 2 GB RAM.

[ChrisB]

After hunting high and low, I found a sqlyog.bak.ini file from 3 months ago, which contains 51 connections.

I went to my AppData folder and renamed the current sqlyog.ini to sqlyog.ini.new

Then I copied my sqlyog.bak.ini file to the AppData folder as sqlyog.ini.

Then I started SQLyog Enterprise 6.12.

It wiped out all my Saved Connections again.

I compared the .ini files and found that the “old” file contains this section:[codebox][CSVESCAPING]

ESCAPEDBY=\

FESCAPE=t

LESCAPE=rn

ENCLOSEDBY=”

ISESCAPED=1

ISFIXED=0

LINETERMINATED=1

ISENCLOSED=1

ISOPTIONALLY=0

FIELDSTERM=1[/codebox]…whereas the new one contains just this:[codebox][CSVESCAPING]

ESCAPEDBY=\

FESCAPE=t

LESCAPE=r[/codebox]

I did some further testing and found that simply removing the blank line from the file seems to let even my backup file be accepted and functional.

Thus, it would seem that 6.12 has a bug that causes blank lines in the sqlyog.ini file to cause it to stop reading the file and ignore the rest of its content.

[Author]

Posts