Forum Replies Created
-
AuthorPosts
-
Ritesh
MemberHello Richard,
We confirm the presence of above bugs in SQLyog 4.0 BETA 2. We are working on these issues and will release BETA 3 soon with the bugs fixed.
With this, I would like to say that these error occur due to anomalies in the way MySQL returns Meta-data information.
1.) First error
In versions prior to MySQL 4.1.4-gamma the result returned from SQL:
show table status from mydb was:
Name Type Row_format Rows Avg_row_length Data_length Max_data_length Index_length Data_free Auto_increment Create_time Update_time Check_time Charset Create_options Comment
where as in MySQL 4.1.4-gamma it is:
Name Engine Row_format Rows Avg_row_length Data_length Max_data_length Index_length Data_free Auto_increment Create_time Update_time Check_time Charset Create_options Comment
This causes SQLyog to throw up the error: could not read data for the table
2.) Second error
In versions < 4.1.4, MySQL allowed to issue SQL stmt. to drop primary key for a table even if there were none. With 4.1.4, it has changed. Now we need to have a PRIMARY KEY to issue DROP PRIMARY KEY stmt. This issue results in SQLyog throwing up error: Error No. 1091 Can't DROP 'PRIMARY'; check that column/key exists
Therefore, the errors returned are specific to version of MySQL you are using.
MemberCurrently, you can only automate the following two features:
- Database synchronization
- Notification services
HTH
MemberBug confirmed.
We will be releasing SQLyog 4.0 BETA 3 soon that will have this bug fixed 🙂
MemberI have forwarded the issue to my development team.
Meanwhile, can you send us the table structure with some sample data to reproduce the error?
Information about your MySQL version will also be helpful.
MemberWe are not able to reproduce this error at our end. If you help us reproduce this error at our end, we assure you to fix it in the next three business days.
Please mention the following information:
- Exact MySQL version
- Table schema
- Relationships between test tables
- Index information
MemberI have forwarded the issue to my development team.
BTW, if the data is not confidential then can you send me a copy of the same? It will be easier for us to find and fix the bug. You can mail them to [email protected]
MemberHello,
Check out SQLyog 4.0 BETA 2.
Apart from various bugfixes of BETA 1 (including the bug reported by you), it has got a new and improved SQL Editor. Now you can edit large SQL files without noticing any performance degradation.
For more information visit: http://www.webyog.com/forums/index.php?act…st=0&#entry3674
Eagerly waiting for your comments.
MemberWhich version of SQLyog?
MemberAre you trying to delete a FK?
Can you send us the CREATE TABLE… stmts. for your tables so that we can work on it out here and resolve the bugs (if there are any)?
MemberThis is a known bug and has been fixed in SQLyog 4.0 BETA 1. SQLyog 4.0 BETA 2 is on the way.
More information on SQLyog 4.0 BETA can be found at http://www.webyog.com/forums/index.php?act…ct=ST&f=2&t=977
MemberCheck out the following link: http://dev.mysql.com/tech-resources/articl…/installer.html
MemberSQLyog will always show you the data with a limit clause (to accidently avoid huge SELECT stmts.). It takes these values from sqlyog.ini file.
There are two ways to change this value:
1.) Open up sqlyog.ini (found in the installation directory of SQLyog), and change the values for LowLimit and HighLimit value in SQLYOG section to whatever values you want. In your case it should be 0 for lowlimit and an arbitrarily high value for highlimit.
2.) Select the table, press F11. In the Insert/Update window there will be two limit boxes. Change the limit values and close the dialog. It will write down the modified value in the INI file.
HTH
MemberRight now the official MySQL forums does not seem to be very active. I always prefer the MySQL Mailling Lists 🙂
MemberYes but you have to do it separately using the SQLyog GUI. Copying database is not supported in SQLyog Job Agent (engine that performs the synchronization).
We plan to add a feature in one of future releases of SJA where it will automatically drop all data in the target table if there are no PRIMARY KEYs defined. It will then do a complete insert from source to target.
MemberMaybe you can try the MySQL Mailing Lists.
The issues reported by you might be bugs which MySQL would love to resolve. Probably, they could point you to some documentation that answers the questions.
-
AuthorPosts
