[Shadow]

You better check back because the current production version is 3.64 and v3.7 is already in beta!

[Shadow]

Then – unfortunately – I cannot help. I don't have any computers around running linux…

[Shadow]

You may try to route through a machine that has a fixed IP address.

[Shadow]

Do you use any unusual (special) characters?

[Shadow]

How did you add a new user if you can't connect to the db? What rights does that root@% have?

[Shadow]

Sja can be used to:

1. sync content and structure

2. schedule or issue a group of SQL queries (v3.7 beta only!).

Sja cannot be used to view the differences of two dbs, it syncs their content immediately. From v3.7 on it supports two-way sync as well.

Which parts of its XML schema is unclear to you?

[Shadow]

And it's not even a final version. Hmmmm…

[Shadow]

Or have your provider add the new accounts to the server…

[Shadow]

No, you cannot select which tables are not to be synchronized in the current versions.

[Shadow]

See roadmap for details about SQLyog MAX.

[Shadow]

He even volounteers, you don't need to ask! 😀

[Shadow]

I thought he had already forgotten this topic…

[Shadow]

Well, you should ask Ritesh, if you could send him the problematic records (given it's possible) and if he could debug sja using your data.

MySql 3.x supports only one character set/server…

[Shadow]

Well, then I have no idea what could cause your problem. Doest the replication fail only on those records that contain special characters?

[Shadow]

I did encounter similar problems regarding special Central European characters. It turned out that the backup db had wrong character set setting…

[Author]

Posts