Syncronise Schemas

[yetanotherjimbo]

Hi,

Just started looking at SQLyog Ent. 4.07 and noticed a bug (?) in the Schema Sync tool.

If I make connection to remote boxes via an SSH tunnel ( so that they are both connecting as 'thesameusername'@'localhost' ) when you are provided with the drop-down list to choose which two databases to compare you're only given the one database.

If I change one of my connection settings to 'thesameusername'@'127.0.0.1' though, for example, I get both; as I would expect.

Hope this helps.

Cheers,

J.

PS. Have only just downloaded but SQLyog looks stunning so far! 🙂

[Ritesh]

Are you connecting to the same MySQL server?

[CalEvans]

Ritesh wrote on Jul 12 2005, 01:49 PM:

Are you connecting to the same MySQL server?

While I've not tried to duplicate his problem, I can see it in my mind. The drop down lists all show database@server. If you are using ssh then the server is always localhost, regardless of what server you are really connecting to. therefore I could be connecting via ssh to Bert and Ernie but when i go to select the schemas to compare, they will ALL show @localhost.

=C=

[peterlaursen]

The solution thus must be to include the NAME of the connection, ie:

DB_name – connection_name: user@server

or

connection_name – DB_name: user@server

The problem must be the same with the sync tool and any other possible feature of SQLyog that uses two connections simutaneously. Am I right ?

[Ritesh]

As I understand you are connecting to the same SSH box.

Later on, are you connecting to the same MySQL server or different servers? Can you give me more details about your setup?

[yetanotherjimbo]

Hiya..

( sorry – I dissapeared! 😉 ) Cal is right – I think it's just a naming issue.

I am connecting to 2x boxes, 2x different machines etc, 2x SSH tunnels. The catch is that because the setup of the boxes are the same once your inside the tunnel what you do is identical… ie. both connections are made to “dbname@localhost” …

… the two “localhost's” are entirely different machines.

This problem ( afaik ) is only going to show up where you are able to make 2x identical 'looking' connections to two different databases. Only place this occurs in practice is when you use a hostname like localhost which always refers to the loopback to yourself and not to a real location…

.. I guess if the lists of DB's are getting thrown into a hash somewhere under the bonnet in SQLyog, key'ed by the connection string, then there is the potential to conflict where you can make two legitiamtely identically named different connections..

… hope I'm managing to explain myself – say if I'm still not making sense – very early Monday morning! 😉

J.

[Ritesh]

As I visualise the situation:

You are connecting to different SSH hosts:

192.168.1.1 and 192.168.1.2

From there you are tunneling to MySQL servers running on the same machine as the SSH Host i.e. *localhost*. Am I right? Thus you are providing two different addresses in the SSH Host field of Tunnel tab?

[yetanotherjimbo]

Ritesh wrote on Jul 25 2005, 09:46 AM:

As I visualise the situation:

You are connecting to different SSH hosts:

192.168.1.1 and 192.168.1.2

From there you are tunneling to MySQL servers running on the same machine as the SSH Host i.e. *localhost*. Am I right? Thus you are providing two different addresses in the SSH Host field of Tunnel tab?

[post=”6568″]<{POST_SNAPBACK}>[/post]

Yep.. That sounds right.

[Ritesh]

http://www.webyog.com/forums/index.php?act…&st=0#entry6571

v4.1 BETA 4 fixes the above bug.

[Author]

Posts