MySQL Bugs: #116001: Issue: Inconsistent Timestamp Values After Import

Bug #116001	Issue: Inconsistent Timestamp Values After Import
Submitted:	4 Sep 2024 13:50	Modified:	6 Sep 2024 11:31
Reporter:	Bhargavaram Nallam	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: mysqldump Command-line Client	Severity:	S3 (Non-critical)
Version:	8.0.35/8.0.39	OS:	Any (Primary Timestamp Values: Example: 2024-08-22 04:28:25 to 2024-08-22 04:34:04 Timezone: US/Pacific )
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
 After importing a database dump into MySQL 8, the timestamp column values are not consistent with the original data. Specifically, timestamps that were set with a default value of 0000-00-00 00:00:00 or CURRENT_TIMESTAMP are showing unexpected results. This discrepancy is observed between primary and secondary timestamp values due to timezone differences.

Details:

Primary Timestamp Values:

Example: 2024-08-22 04:28:25 to 2024-08-22 04:34:04
Timezone: US/Pacific
Column Definition: timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP or timestamp NOT NULL DEFAULT '0000-00-00 00:00:00'
Secondary Timestamp Values:

Example: 2024-08-22 16:58:25 to 2024-08-22 17:04:04
Timezone: System default timezone
Impact: Timestamps are not consistent between the original database and the restored database, which may lead to issues with data accuracy and integrity.

How to repeat:
To address the issue of inconsistent timestamp values during the dump and restore process using mysqldump.

We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

For details on getting support for MySQL products see http://www.mysql.com/support/
You can also check our forums (free) at http://forums.mysql.com/

Thank you for your interest in MySQL.