[Ritesh]

We will try to duplicate this problem at our end.

We will revert back shortly.

[Ritesh]

This is strange! Clicking on “Test Connection..” should either show you an error message or it should show a Messagebox reporting the MySQL server version running on the remote host.

Are you able to get past the connection dialog?

Could you please try accessing the tunnelling URL from a browser and send us the results?

[Ritesh]

Are you using BETA 4?

Are you able to view the list of your databases in the Object Browser?

[Ritesh]

SQLyog logs up all the queries that it executes in the History Window.

Do you find anything unusual?

[Ritesh]

Execute All Query(s)… (Shift+F5) is the option you are looking for.

[Ritesh]

SJA for both Windows and Linux only supports Data Sync and Notification Services.

For structure sync, you have to use SQLyog.

[Ritesh]

Currently, SQLyog's ODBC Import Tool only supports importing of Table Structures and Data.

We plan to add options for importing other objects like Indexes, PKs, FKs in the next version i.e. 4.1.

[Ritesh]

Just select the table in the ObjectBrowser and select Alter Table Structure… from the popup menu (or press F6). Check the corresponding PK? checkboxes for the columns on which you want to create the keys.

After you are done, click Alter Table

[Ritesh]

No *LOCK* query(s) are executed by SJA.

[Ritesh]

lion78at wrote on Oct 5 2004, 04:22 PM:

Hello!

I think I found a new BUG (in Version 4 BETA 3): “Don't delete extra row(s) in Target database” doesn't work. Extra rows will be always deleted!

Kind regards,

Bernhard

The bug has been fixed in SQLyog 4.0 BETA 4. For more information please visit:

http://www.webyog.com/forums/index.php?act…f=2&t=977&st=0&

[Ritesh]

The bug has been fixed in SQLyog 4.0 BETA 4. For more details, please visit:

http://www.webyog.com/forums/index.php?act…f=2&t=977&st=0&

[Ritesh]

This behaviour is correct according to the design.

When you select specific columns, those columns are the ones which are used to *detect* changes – however if a change has been detected the entire row is updated.

Selecting specific columns would instruct SJA to sync the entire row only if there is a change in the selected columns.

The feature that you want is an interesting one and we can look at it later. Right now, we are approaching deep freeze of 4.0 code.

[Ritesh]

lion78at wrote on Oct 5 2004, 08:49 AM:

Hello!

I think I found an error in SJA:

I have 2 mysql databases (with same scheme) which I have to synchronize: a local database and an online database.

In my databases a have a table “T_Report” with the columns “ReportID”, “Title”, “Content”, … and “Counter”.

New reports are added from me to the local database, old reports are updated from me in the local database. After data manipulation I synchronize the databases with SJA. The problem is that the column “Counter” mustn't synchronized, cause this column is updated in the online database via web-app and must synchronized from online => local.

Procedure:

1. Set the column “Counter” = 0 in local database (this is necessary only for new reports).

2. Synchronize only the column “Counter” from online to local database.

3. Synchronize the other columns (other than “Counter”) from local to online database.

=> Now the reports in both databases should be up to date and having counter-data from online database.

BUG:

If I have changed a report (e.g. I changed the column “Content”) in the local database than in step 2 not only the column “Counter” is synchronized, but also all other columns are updated from online to local database.

=> I lose all changes in the local database!

Is there a workaround? Will this problem be fixed in Verion 4.x?

Kind regards,

Bernhard

Can you explain the problem with more details?

Sample data and schema file will be appreciated.

[Ritesh]

lion78at wrote on Oct 5 2004, 04:22 PM:

Hello!

I think I found a new BUG (in Version 4 BETA 3): “Don't delete extra row(s) in Target database” doesn't work. Extra rows will be always deleted!

Kind regards,

Bernhard

I have forwarded this issue to my development team. Will revert back within 48 hours.

[Ritesh]

SQLyog 4.0 BETA 3 has been released. This release fixes the above bug(s).

For more information please visit: http://www.webyog.com/forums/index.php?act…ct=ST&f=2&t=977

[Author]

Posts