lp://staging/~linuxjedi/drizzle/trunk-drizzledump-bugs

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/drizzle/7.0 at revision 1977

Andrew Hutchings: Needs Fixing on 2010-12-06

Diff: 166 lines (+65/-8)

3 files modified

client/drizzledump_data.cc (+30/-3)
client/drizzledump_data.h (+3/-1)
client/drizzledump_mysql.cc (+32/-4)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #684986: Drizzledump migration does not appear to handle BIT datatype gracefully	High	Fix Released
Bug #685003: Drizzledump adding extra ')' to CREATE TABLE output when dealing with foreign keys	High	Fix Released
Bug #685046: Drizzledump not handling MySQL CHAR(0) /VARCHAR(0) columns gracefully	Low	Fix Released
Bug #685173: drizzledump should error if > max bigint value found	High	Fix Released
Bug #685176: drizzledump migration SET with default value failure	Medium	Fix Released

Link a bug report

Related blueprints

1979. By Andrew Hutchings on 2010-12-06

Fix uninitialized bool

1978. By Andrew Hutchings on 2010-12-06

Oops, this line shouldn't have been committed

1977. By Andrew Hutchings on 2010-12-06

Make BIGINT range check only happen on MySQL BIGINT UNSIGNED as it is tripping up on negative BIGINT values.

Also, don't quote BIGINT values

1976. By Andrew Hutchings on 2010-12-04

Drop the default when converting SET data type. Ugly but I can't think of a better way until we support SET properly

1975. By Andrew Hutchings on 2010-12-04

MySQL support CHAR(0), erm.. OK. Lets at least make this 1 char long.

1974. By Andrew Hutchings on 2010-12-04

If migrating a BIGINT UNISIGNED value > BIGINT signed max value, error. We cannot store it.

Also fix a bug on NULLs within varbinary data

1973. By Andrew Hutchings on 2010-12-04

Add BIT support when converting MySQL. We convert this to a varbinary and covert the bit length to a byte length.

Values are therefore automaticaly converted to printed hex due to previous rules.

1972. By Andrew Hutchings on 2010-12-04

Drizzledump MySQL migration fkey regex was too greedy causing output errors

1971. By Lee Bieber on 2010-12-03

Merge Stewart - update Innobase plugin based on InnoDB 1.1.2

1970. By Lee Bieber on 2010-12-03

Merge Andrew - fix bug 683940: Drizzledump not preserving FOREIGN KEY information during migration from MySQL
Merge Andrew - fix bug 683917: Drizzledump fails when trying to migrate MEMORY tables from MySQL