Comment 6 for bug 674588

This is part of the randgen / gendata.
The program does ENABLE/DISABLE when it is loading a table.

I'm not certain if this should be logged given that it doesn't actually do
anything. I do think such changes that do have an effect *should* be logged
though.

On Sun, Nov 14, 2010 at 6:35 PM, Joe Daly <email address hidden> wrote:

> Is this something that should even be in the transaction log? Im leaning
> towards no, it currently shows up and seems to be causing some
> strangeness with transaction ids.
>
> drizzle> ALTER TABLE `A` ENABLE KEYS;
> Query OK, 0 rows affected, 1 warning (0.01 sec)
>
> drizzle> show warnings;
> +-------+------+-------------------------------------------------------+
> | Level | Code | Message |
> +-------+------+-------------------------------------------------------+
> | Note | 1031 | Table storage engine for 'A' doesn't have this option |
> +-------+------+-------------------------------------------------------+
> 1 row in set (0 sec)
>
> drizzle>
>
> --
> Transaction ID not unique
> https://bugs.launchpad.net/bugs/674588
> You received this bug notification because you are a member of Drizzle-
> developers, which is subscribed to Drizzle.
>
> Status in A Lightweight SQL Database for Cloud Infrastructure and Web
> Applications: New
>
> Bug description:
> When running randgen to look for bug 673105, I saw several messages in the
> transaction log with the same transaction id number. They are not part of a
> multi-message Transaction (they are rather small). Used the following
> randgen command:
>
> ./gentest.pl--dsn=dbi:drizzle:host=localhost:port=9306:user=root:password="":database=test
> --gendata=conf/drizzle/translog_drizzle.zz
> --grammar=conf/drizzle/translog_concurrent3.yy --queries=50 --threads=10
> --sqltrace --debug --Reporter=DrizzleConcurrentTransactionLog >
> /tmp/randgen.out
>
>
>