[Ritesh]

Very strange. 😮

I am using 4.05 BETA and the two screenshots below should make things more clear.

[Ritesh]

Thanks for your suggestions. I have forwarded it to my development team.

[Ritesh]

How many rows are you trying to display?

Whenever you execute a query, the execute query button (green color) in the toolbar is replaced by a red stop sign. Click on it to stop a currently executing query.

Have you unchecked Tools -> Preferences -> Truncate Column Header To Max Data Size?

[Ritesh]

From v4.05 BETA you can actually stop a query while its being executed.

[Ritesh]

The current version of SQLyog supports 3.23.x and above. To use it with 3.22.x we have to provide you with a special build of SQLyog.

[Ritesh]

First of all, thank you for your valuable time and we are absolutely delighted to have so many well-wishers for SQLyog!

We would like to take this forward and target it for Rel 4.2. Please send your design and we can discuss it on the forum. We are committed towards providing the most intuitive UI to MySQL.

All Webyog forum members are welcome to improvise on the UI design.

Additionally, please send a mail to [email protected] if you want to become a beta-tester for SQLyog.

[Ritesh]

First of all, thank you for your valuable time and we are absolutely delighted to have so many well-wishers for SQLyog!

We would like to take this forward and target it for Rel 4.2. Please send your design and we can discuss it on the forum. We are committed towards providing the most intuitive UI to MySQL.

All Webyog forum members are welcome to improvise on the UI design.

Additionally, please send a mail to [email protected] if you want to become a beta-tester for SQLyog.

[Ritesh]

In v3.23.54, a simple table definition is given as:

Code:

CREATE TABLE `TableName1` (                                                                                                          
             `id` int(11) NOT NULL auto_increment,                                                                                              
             `t` timestamp(14) NOT NULL,                                                                                                        
             PRIMARY KEY  (`id`)                                                                                                                
           ) TYPE=MyISAM

In 4.1.9, the same table definition is given as:

Code:

CREATE TABLE `tablename1` (                                                                                                                                      
             `id` int(11) NOT NULL auto_increment,                                                                                                                          
             `t` timestamp NULL default NULL,                                                                                                                              
             PRIMARY KEY  (`id`)                                                                                                                                            
           ) ENGINE=MyISAM

If you notice, the column t is having different definitions i.e. timestamp(14) and timestamp across multiple MySQL versions. We plan to fix this issue in one of the future version of SJA.

Currently the only solution is to use same MySQL versions for both source and target.

[Ritesh]

We dont plan to add option for forms in SQLyog.

SQLyog is an admin tool for MySQL and we believe tools like VB etc. are better suited for the above purpose.

[Ritesh]

Which window would you like to be colored?

[Ritesh]

Quote:

I can see two problems in that transcript. One is about creating a temporary table (the one that stores my data to be inserted back into my real table after reconstruction) “if not exists”, so if it does exist I guess I'd get supplemental data that wasn't there before… I guess something like “DROP TABLE IF EXISTS” would be safe.

We use if not exists so that we dont delete an existing table (which might be important) by mistake.

Quote:

Second, at least MySQL 4.1 knows about this, which is safer and needs no warning 11 point warning from SQLyog:

SQLyog v4.1 BETA actually checks for MySQL version and uses the correct method. For e.g. if MySQL version is 4.1.x then it will use ALTER TABLE Test1 DROP FOREIGN KEY `Test1_ibfk_1` statement. Otherwise it will go for the original 11 steps method to drop the FK.

[Ritesh]

Are you talking about Result Window or the Insert/Update window?

[Ritesh]

You probably want to use SQLyog Data Synchronization Tool.

Its available from Tools -> PowerTools -> Database Synchronization Wizard

[Ritesh]

G is a special command supported by the MySQL command line utility.

Its not a valid SQL statement and thus the error.

[Ritesh]

Bug confirmed.

Will be fixed in the next BETA.

[Author]

Posts