Need to update Drizzledump documentation with migration conversions / caveats
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
Low
|
marisa plumb | ||
| 7.0 |
Fix Released
|
Low
|
marisa plumb | ||
Bug Description
I think we should update the online drizzledump docs with the conversions listed in the drizzledump blueprint:
https:/
Specifically, this information:
During step 3 the following conversions are required:
MyISAM -> InnoDB
FullText -> drop it (with stderr warning)
int unsigned -> bigint
tinyint -> int
smallint -> int
mediumint -> int
tinytext -> text
mediumtext -> text
longtext -> text
tinyblob -> blob
mediumblob -> blob
longblob -> blob
time -> int (of seconds)
year -> int
set -> text (can't guess length so safer than varchar, may need to normalise in later versions)
date/datetime default 0000-00-00 -> default NULL *(It currently appears that ALL date columns have their DEFAULT set to NULL on migration)
date/datetime NOT NULL columns -> NULL
any date data containing 0000-00-00 -> NULL
| Changed in drizzle: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| importance: | Wishlist → Low |
| Changed in drizzle: | |
| assignee: | nobody → marisa plumb (marisa-plumb) |
| Andrew Hutchings (linuxjedi) wrote | #1 |
| Andrew Hutchings (linuxjedi) wrote | #2 |
Also:
MEMORY/HEAP -> InnoDB (we only support memory/heap for temp tables in Drizzle)
BIT -> VARBINARY with adjusted field sizes, so BIT(16) -> BINARY(2)
CHAR -> VARCHAR
BINARY -> VARBINARY
FLOAT -> DOUBLE
unsigned on INT is dropped (since we don't support it)
For BIGINT UNSIGNED values > BiGINT SIGNED MAX (92233720368547