drizzledump migration to use new TIME type
Bug #694642 reported by
Andrew Hutchings
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Won't Fix
|
Low
|
Andrew Hutchings | ||
| 7.0 |
Won't Fix
|
Low
|
Andrew Hutchings | ||
Bug Description
TIME data type is back in Drizzle, so lets support it for MySQL migration
Revision history for this message
| Andrew Hutchings (linuxjedi) wrote | #1 |
| Changed in drizzle: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Not going to implement this. MySQL's TIME type has a range of -838:59:59 - 838:59:59. Drizzle's type has the more correct 00:00:00 - 23:59:59 range. So if someone is using outside Drizzle's range in MySQL there would be data loss. INT is still the most likely best conversion for this.
The other possibility is to add a new option which will explicitly tell drizzledump to use the TIME type instead and error if it meets an out-of-range time entry. I'm not comfortable about adding more complexity / options so documenting this would be best.
Making a note in bug#684803