- Home
- Show all categories
- About Webyog support and about this FAQ
- About the SQLyog program

- Connection issues

- Using the GUI
- Managing your MySQL Database Systems

- Database Structure Synchronization
- MySQL DATA synchronization
- Notification Services
- ODBC and Migration
- 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
- Instant Response
- Sitemap
MySQL bugs that affect SQLyog
Timestamp defined "ON UPDATE CURRENT_TIMESTAMP" updates incorrectly.
It has been reported that with MySQL 5.1.x and the INNODB storage engine the "ON UPDATE CURRENT_TIMESTAMP" clause for TIMESTAMP types is not functional! Sometimes such timestamp for a row will update even if there is no change in any other column.
Refer to: http://bugs.mysql.com/bug.php?id=29310
MyISAM tables work as expected/as documented. It is not known if any 3rd party engines are affected.
Probably all MySQL 5.1 versions before 5.1.21 are affected by this bug.
Tags: -
Related entries:
- SQLyog Version History
- Can I perform "incremental import" with the SQLyog Migration Tool?
- What Storage Engines are supported by SQLyog?
- What is the difference between MySQL server replication and SQLyog synchronization?
- I only changed one row of data, but SQLyog wants to update more rows in the database. Why?
Last update: 2007-07-04 05:45
Author: Peter Laursen
Revision: 1.0
You can comment on this entry