[nithin]

Hello,

Thanks for the test case.

I am giving a special build with this issue got fixed. Please verify with your environment and let us know the status.

Please find the special build here.

Regards

Nithin

[nithin]

Hello,

This issue is already fixed in version 8.18. SQlyog version 8.18 release notes tells:

— Schema Sync failed to set the auto-increment flag when syncing a table having this flag to a table not having.

So please verify with latest 8.4RC or 8.32, and let's know the status?

http://www.webyog.com/en/downloads.php

Thanks

Nithin

[nithin]

Quote:

even though SQLyog crashed, all the tables were dropped.

Can you verify whether crash dump created or not?, please attach the dump if created so we can analyze the issue whether its due to the SQLyog code or not.

[nithin]

Thanks for the cooperation.

We provide you special build with issue got fixed(also no logging here).

You can use this until we do next public release.

http://webyog.com/downloads/betas/not_released/SQLyog84n3.exe

Regards

Nithin

[nithin]

Thanks for the reply. From the log file we confirmed the API is failing, and we modified it. In btw what's your OS?

This is the another special build.

– Delete the 'sqlyog_ssh.log' before install this.

– Connect SQLyog again and attach new log file created. (This special build is for assuring the locking *port for current session is working fine)

http://webyog.com/downloads/betas/not_released/SQLyog84n2.exe

Thanks again

Nithin

[nithin]

Thanks for attaching log file.

Also please tell whether this build has been worked fine for you?

Regards

Nithin

[nithin]

Thanks for verifying the build(But issue has not been solved here with, just commented out some functions to confirm the issue)

We are providing you another special build, there we had made some code changes as well as logging some function return values.

– The path of the log file is 'App Data folder' where the SQLyog.ini is(C:Documents and Settings{user}Application DataSQLyog).

– log file name is “sqlyog_ssh.log”

– Install this special binary, and click on 'Test connection' button in connection dialog, then copy the 'sqlyog_ssh.log' and send to us (one fix we did may solve your issue but please attach the log file whatever is the situation, so that we could analyze the issue)

http://webyog.com/downloads/betas/not_released/SQLyog84n1.exe

Thank you

Nithin

[nithin]

Hello,

The 'SshForPort' is no longer required.

The 8.21 version change log tells:

— The local port used by SSH-tunneling will now be selected automatically. This will avoid conflicts in case multiple programs use SSH. Also with Data Sync from command-line/scheduler it was possible to use same port for both connections what would effectively sync a server with itself

I provide you a special binary, please try this and let us know the status?

http://webyog.com/downloads/betas/not_released/SQLyog83n1.exe

Thank you

Nithin

[nithin]

Also please tell are those Innodb tables?

Also execute these queries at source db and target db and tell if any error:

SELECT * FROM FOR UPDATE;

SELECT * FROM LOCK IN SHARE MODE;

Regards

Nithin

[nithin]

1) We do not understand “target: not in the list of tables of SHOW GRANTS results”. Please detail this.

2) Could you try to add global SUPER privilege to user? Just to check if server 5.0.45 is affected by same bug as the one we linked to above.

[nithin]

Hello,

Please tell,

1) OS where SQLyog is running

2) MySQL server version of source and target (and OS where server installed)

3) Please execute this on both source and target:

SHOW GRANTS FOR 'username'@'host';

[nithin]

Hello,

This issue could be related to Ubuntu package and wine.

Still there's no solution found for this.

And also this seems to be fine with other linux distribution(like RHEL 5)

We could not tell when we can solve this issue because solving/concluding this issue may require some more communication between Ubuntu, wine developers.

Thank you

Nithin

[nithin]

Hello,

Thanks for your patience and you may no need to raise it again..

This feature has been scheduled for 8.4 version. Expected release time for 1st beta is first week of next month.

Thank you

Nithin

[nithin]

Currently we are keeping the table level persistence for “All rows”, “rows in range”.

But the issue here is once you selected the 'all rows' or 'rows in range' for a table the subsequent newly selected tables also would be set that settings.

– So what we will do is, for newly selected table the default will be always 'Rows in range'.

– And We will persist the selected option only when the display is completed(with out any crash).

– If in case the table is grown and taking more time you can use the 'Stop' button to stop the process.

– As a work around you can do any of these:

– rename/delete the 'ColumnAttributes.db' from App Data folder(where the .ini is)

– If you have any SQLite browser you can open this db and delete the particular row(for that database and table)

Thank you

Nithin

[nithin]

Thanks for reporting the issue

What is the SQYog version and Windows version?

Please attach the crash dump created from this path

Windows Vista/2008/7:

C:Users{user}AppDataRoamingSQLyog

For Windows 2K/XP/2003:

C:Documents and Settings{user}Application DataSQLyog

Thank you

Nithin

[Author]

Posts