Comment 3 for bug 652228

This diff is from comparing drizzledump files from MySQL vs. Drizzle (after
it has been populated via drizzledump from the MySQL server)

On Thu, Sep 30, 2010 at 2:04 PM, Andrew Hutchings <<email address hidden>
> wrote:

> Filed bug#652272 anyway. If that is the cause I will close this one as
> a dupe.
>
> --
> AUTO_INCREMENT values from MySQL tables not being captured / dumped via
> drizzledump
> https://bugs.launchpad.net/bugs/652228
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in A Lightweight SQL Database for Cloud Infrastructure and Web
> Applications: Triaged
> Status in Drizzle elliott series: Triaged
>
> Bug description:
> Randgen testing has shown that AUTO_INCREMENT values are not being captured
> when using drizzledump to dump MySQL tables:
>
> Output below is from a diff of MySQL vs. a Drizzle server populated via
> drizzledump output produced against the MySQL server.
>
> CREATE TABLE `dump_table2` (
> `col_enum_key`
> ENUM('a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z')
> DEFAULT NULL,
> @@ -42,7 +42,7 @@
> KEY `col_enum_not_null_key` (`col_enum_not_null_key`),
> KEY `col_bigint_key` (`col_bigint_key`),
> KEY `col_char_10_key` (`col_char_10_key`)
> -) ENGINE=InnoDB AUTO_INCREMENT=1 COLLATE = utf8_general_ci;
> +) ENGINE=InnoDB COLLATE = utf8_general_ci;
>
> I populated the MySQL server via the randgen, using the gendata file
> conf/drizzle.zz.
>
> If for any reason you'd like additional information or help in reproducing
> this, just let me know and I'll do what I can.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/drizzle/+bug/652228/+subscribe
>