[nithin]

We have fixed this issue and released 9.0 Beta2.

http://www.webyog.com/blog/2011/04/01/sqlyog-mysql-gui-9-0-beta-2-released/

Can you confirm this into your envirment and let us know the status.

[nithin]

We are checking this issue at our end.

BTW Can you try whether you are able to reproduce this case?

We may provide you a special build to find the exact issue.

[nithin]

Thanks for updating.

We will include this fix into the next public release. Until then you can use the special binary I provide here, where no information is logged as compared to the previous special build.

You can download the special build by below link.

Ultimate/Enterprise

http://www.webyog.com/downloads/betas/not_released/SQLyog-8.8.3-n6.exe

Trial

http://www.webyog.com/downloads/betas/not_released/SQLyog-8.8.3-n6Trial.exe

Please confirm the status once checked.

[nithin]

Hello,

We have got a similar crash internally, that was pointing to same point where your crash dump points. Its solved internally and will include into the next public release. FYI It was not connection type related, it was a bug with code where we do format the query to display at the bottom of result tab.

Thank you

Nithin

[nithin]

Hello,

Let us know whether you got time to check the special binary.

We had similar post in our ticket system, and its got solved now. We give you the same special build where this issue is solved. Please try it in your side and confirm us the status.

Also when click 'Connect' on connection widow it will create a log file at the path “Application Data SQLyog”(where the sqlyog.ini is).

The log file name is – crash_log83n5.log. Please attach this once its got created.

To download click the below link

Ultimate/Enterprise

http://www.webyog.com/downloads/betas/not_released/SQLyog-8.8.3-n5.exe

Trial

http://www.webyog.com/downloads/betas/not_released/SQLyog-8.8.3-n5Trial.exe

Regards

Nithin

[nithin]

Hello,

We are providing you a special binary that logs some info when click on 'Connect' (and also commented out come code).

The log file name is 'crash_log83n1.log', will be created at 'Application DataSQLyog' folder.

To download click the below link

Ultimate/Enterprise

http://www.webyog.com/downloads/betas/not_released/SQLyog-8.8.3-n3.exe

Trial

http://www.webyog.com/downloads/betas/not_released/SQLyog-8.8.3-n3Trial.exe

-Install this binary in different path, connect, and attach the log file created.

-If crashing disable the AutoComplete(Tools->Preferences->Power Tools->Enable Autocomplete) feature and try again.

-If you find this special binary is not crashing for a case try the same with your 8.82 normal build.

We expect the log file generated will reveal some info about this issue.

Thank you

Nithin

[nithin]

Hello,

Quote:

Now, I got a new problem out of the blue that I got few days ago

You mean it was working fine for sometime and this problem started?

Can you reboot your system and try again?

The dump is not providing much info rather say it happened during start-up. We may provide you a special build that logs some info to a file that helps identify the exact issue.

Thank you

Nithin

[nithin]

You feature request is added to issue tracker, We will consider this after discussing with team

http://code.google.com/p/sqlyog/issues/detail?id=1614

[nithin]

A valid suggestion.

We will consider this. Let me know your thoughts about where do you like to see the 'foreground color option'? In the same dialog where the background color option is defined?

Thank you

Nithin

[nithin]

Quote:

does it stop the process or skip the problematic rows? Is this recorded in the log?

SQLyog's Import-External-Data feature has got an option “Abort on error” (screen-shot is attached), If this option is selected the process will be stopped and logs the query to sja.log(located where the sqlyog.ini is)when it encounters any error, else it ignores the error and continues the process.

[nithin]

There is no limitation on the number of rows of data that SQLyog can import .You can download and verify with trial version of SQLyog(but trial has a limitation. It can import only two tables at a time. But these tables can contain any amount of data).

Quote:

SQLyog manages to insert rows that violate FK in the MySQL. It seems like the tool is dropping the FK for migration. Is there any way to disable it?

If want to import the FKs you must select the option “import foreign keys” in the advanced-option. See the screen-shot attached.

But the referential integrity is disabled internally always by issuing SET FOREIGN_KEY_CHECKS = 0 before INSERT rows, and enabled again by SET FOREIGN_KEY_CHECKS = 1 after the insertions are completed.

[nithin]

Hello,

I agree your point. But this is the behaviour of any merging tool, it should show the 'differences' where they are present (Source/Target) and user can merge the differences to the target. But in this case the confusion arises because we use a tree view display instead of the normal text merging display. The current design considers the source as well so that the user gets a clear idea of the exact differences before syncing. Changing the current behaviour may introduce new confusions. But honestly we did consider all these before implementing this design.

But we will definately discuss your suggestions.

Thank you

Nithin

[nithin]

We have tried the case at our end in Linux as well as Windows. But it works as expected.

Quote:

You will notice that the “Position” should still be at position 106, which means it did not binlog the ALTER action.

Its not happening at our end, the “Position” got changed after killed-Alter table.

Since we are not able to reproduce this we can consider the web meeting with screen sharing session.

We request you to create a support ticket by sending mail to [email protected]

Please tell us your timezone also in the mail.

[nithin]

Your first post:-

Quote:

Here at work, we have a simple master/master setup in MySql, which we setup and everything was working fine, but for some reason the “slave” of the 2 masters was breaking and stopped syncing.

When we dug though the logs we found that the table(s) that we altered did not get altered on the slave. After some researching we found the problem, this is not a “bug” by definition, but you would expect SQLyog to issue a new USE command when a connection gets broken and re-connected.

What error you got during syncing?

How you connected to server(direct/ssh/http)?

Your server versions?

Alter table returns any error? or it executed against wrong database/table?

2nd post:-

Quote:

SHOW TABLE STATUS FROM `demo` LIKE 'TableName1';

/* KILL CONNECTION TO DATABASE HERE ON THE SERVER HERE !!!! */

/*[1:05:52 PM][ 62 ms]*/ ALTER TABLE `demo`.`TableName1` ADD COLUMN `test2` INT(11) NULL AFTER `test`;

/*[1:05:54 PM][ 0 ms]*/ SHOW FULL TABLES FROM `demo` WHERE table_type = 'BASE TABLE';

Notice that ALTER TABLE statement used fully qualified table name(database.table), so USE database is not required here.

Can you tell whether it's thrown any error or table is not altered, when you did this ALTER TABLE after killing the connection? Please explain it.

I have tried this case, it worked fine for me.

Its not showing the USE database in history because we handle this internally.

Please try this case and let us know whether it works for you:-

– Select a database from object-browser(the left panel where the databases are shown in tree view)

– Execute a SELECT query from editor like, SELECT * from (Note that the table name is not fully qualified)

– Stop server. Reconnect. Execute this query again. It returns the result, because we handled the USE internally.

Please explain the case in step-by step so that we can reproduce and handle the problem quickly.

[nithin]

The dump points in MySQL library and it happened when executing query.

Is this always reproducible to you?

Can you tell how to reproduce this?

So either it crashing or hanging always?

Can you try the case again after disable the query_profiler by unchecking the preference option(Tools->Preference->PowerTools->Enable Query Profiler)?

Thanks

Nithin

[Author]

Posts