[Ritesh]

This feature is already in the TO-DO list but I cannot confirm which release will have this feature.

[Ritesh]

Just take a backup of SQLyog.ini and restore it after re-insallation.

[Ritesh]

This is a known issue.

We plan to have complete character-set/language support in v5.2. First BETA of 5.2 is expected by end-Feb.

[Ritesh]

5.2 BETA is expected in mid-Feb.

[Ritesh]

This is very strange. Can you provide me with steps to reproduce the error?

Any hints where I can start?

We run our code through the best memory leak detection tool and it has never reported us anything like this.

@carltond: Can you send me the table structure and sample data so that I can run your query against the db and try to reproduce the problem?

[Ritesh]

v5.02 BETA has been released at:

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

This release fixes the above bug. Can you confirm the bug fix?

[Ritesh]

v5.02 BETA has been released at:

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

This release fixes the above bug. Can you confirm the bug fix?

[Ritesh]

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

Does that help?

[Ritesh]

Can you execute the same query using the mysql command line once and tell me the result?

[Ritesh]

Hmmm…

Looks like that's the issue. We will work on it and fix it in v5.1.

[Ritesh]

How many rows does the query return?

Are you sure the query is proper i.e. indexes are correctly used? It might be that the MySQL client library needs to create lot of data at the client side to create the correct resultset for your query.

Personally, I believe its a query problem rather then SQLyog.

[Ritesh]

This is very strange. It seems to be a error returned from MySQL itself.

Can you check the HISTORY tab which should contain the ALTER/CREATE table statement that SQLyog generates? Do you find anything wrong in that?

[Ritesh]

Or did I miss something?

[Ritesh]

Bug confirmed. When you drop the last database in the Object Browser, the currently selected database shown in the combo box is incorrect. It has been fixed in v5.02 development tree. Now it will correctly show “NONE” as currently selected database in the dialog.

Quote:

you will get this error:

“There was an error while executing a query…”

I dont think this is an error. What does sqlyog.err say?

It generally happens when you deselect the option “Add CREATE DATABASE” option while exporting the data. This result in execution of statements with respect to the currently selected database which is not existing as you have just dropped it. Can you confirm that CREATE DATABASE IF NOT EXISTS sql is present in the dump file?

[Ritesh]

select database() returns the current database for the connection. SQLyog uses the result to know the current selected database.

[Author]

Posts