Navigation
- FAQ Home
- All categories
- About Webyog support and about this FAQ
- About the SQLyog program

- Connection issues

- Using the GUI
- Managing your MySQL Database Systems

- Database Schema Synchronization
- MySQL DATA synchronization
- SQL Scheduler and Reporting Tool
- Importing external data
- Backup/Restore
- SQLyog Job Agent (SJA)

- Working with Views, Stored Procedures and Triggers
- Character Set and Localization Issues
- MySQL bugs that affect SQLyog
- Questions on Open Source and Compiling
- Sitemap
Most popular FAQs 
- I get error 1130 "Host is not allowed to ... (169366 views)
- Error no. 2003: Can't connect... (86310 views)
- SQLyog Version History (63975 views)
- Error no. 1045: "Connection denied..." (61371 views)
- Error no. 1251: "Client does not support authentication..." (58326 views)
- Error No. 2005: Unknown MySQL server host... (50214 views)
- What is HTTP-tunneling? (42290 views)
- What Is SSH and SSH-tunneling? (38087 views)
- Can I use SQLyog with the WINE Windows emulator ... (34956 views)
- Why are Stored Procedures not created when I import ... (34273 views)
Latest FAQs 
- SQLyog Version History (2012-01-26 08:20)
- SQLyog is a client for the MySQL server - ... (2011-11-04 04:48)
- I get error 1130 "Host is not allowed to ... (2011-11-01 05:21)
- Problems on Ubuntu 11.x (2011-10-29 13:02)
- Problems creating a functional DSN on 64 bit Windows. ... (2011-09-15 14:34)
Sticky FAQs
MySQL bugs that affect SQLyog
Data Synchronization fails when a DATETIME column is used for the Primary Key.
You experience that Data Synchronization fails when a DATETIME column is used for the Primary Key (alone or in conjunction with other columns). You probably get the 'infamous' MySQL Server error 1064 'You have an error in your SQL syntax ....'.
MySQL AB has confirmed a change with the most recent MySQL builds (4.1 higher than or equal to 4.1.13 and 5.0 higher than or equal to 5.0.8 (and most likely 5.1.x as well)). It is described here http://bugs.mysql.com/bug.php?id=16546 .
Executing/calculating 'datetime_variable+0' is exactly what the DATA SYNC tool does to convert the DATETIME to a number.
At the time this functional change was introduced there were no noting of it in the MySQL changelogs, so we did not (and did not have any chance to) change the code of SJA accordingly.
Starting from SQLyog 5.16 we TRUNCATE (datetime_column + 0, 0)' for SJA to be able to work correctly with DATETIME-based PK's on all MySQL versions.
Tags: -
Related entries:
- Do I need PHP to use SQLyog with MySQL?
- SQLyog Version History
- What kind of ODBC databases are supported by SQLyog Import External Data Tool?
- What is and what is not imported by the SQLyog Import External Data Tool?
- Can I perform "incremental import" with the SQLyog Import External Data Tool?
Last update: 2006-07-25 11:25
Author: Peter Laursen
Revision: 1.0
You can comment this FAQ