Timestamp data not portable between servers on differnt timezones

Reported by David Busby on 2013-02-15
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MySQL Data Dumper
High
Unassigned

Bug Description

Timestamp data is not preserved when data is dumped under one timezone and imported into another.

The attached patch is a quick fix to clone functionality of mysqldump by defaulting to setting the timezone to UTC during dump, and providing the --skip-tz-utc flag to disable.

David Busby (d-busby) wrote :

updated patch corrected issue where @TIME_ZONE was being used instead of TIME_ZONE

David Busby (d-busby) on 2013-04-23
description: updated
tags: added: utc
David Busby (d-busby) wrote :

Please see merge request: https://code.launchpad.net/~perconardba/mydumper/0.5.2_lesslocking/+merge/168997 this contains this proposed patch aswell as additional functionality.

Changed in mydumper:
milestone: none → 0.5.3
Changed in mydumper:
status: New → Fix Committed
Changed in mydumper:
milestone: 0.5.3 → 0.6.0
Changed in mydumper:
importance: Undecided → High
Changed in mydumper:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers