drizzledump should error if > max bigint value found
Bug #685173 reported by
Andrew Hutchings
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
High
|
Andrew Hutchings | ||
| 7.0 |
Fix Released
|
High
|
Andrew Hutchings | ||
Bug Description
During MySQL migration from BIGINT UNSIGNED -> BIGINT it is possible a value > max BIGINT (signed) could be hit. We need to error about this during dump, not during the import.
Related branches
lp:~linuxjedi/drizzle/trunk-drizzledump-bugs
- Andrew Hutchings: Needs Fixing
-
Diff: 166 lines (+65/-8)3 files modifiedclient/drizzledump_data.cc (+30/-3)
client/drizzledump_data.h (+3/-1)
client/drizzledump_mysql.cc (+32/-4)
| Changed in drizzle: | |
| importance: | Undecided → High |
To post a comment you must log in.
