Timestamp data not portable between servers on differnt timezones
Bug #1125997 reported by
David Busby
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL Data Dumper |
Fix Released
|
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.
Revision history for this message
| David Busby (d-busby) wrote | #3 |
| description: | updated |
| tags: | added: utc |
Revision history for this message
| David Busby (d-busby) wrote | #4 |
| 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.
updated patch corrected issue where @TIME_ZONE was being used instead of TIME_ZONE