On Wed, 8 Dec 2010 20:21:04 -0500, Joe Daly <[email protected]> wrote: > The ID field maps to the inno trx id and the MESSAGE field holds the GPB > message. In Drizzle its not safe to assume that the inno trx id 2 committed > before trx id 1, so having this as the primary key will cause problems, > think out of order slave replay. While Im fixing that problem Id like to > propose the following layout for the table modeled after > http://code.google.com/p/google-mysql-tools/wiki/GlobalTransactionIds > > I propose the following layout: > > group_id, trx_id, server_id, timestamp, message > > group_id= increasing uint64_t value (primary key) > trx_id= inno trx id > server_id= id for the server > timestamp= gpb end timestamp > message= gpb message > > Opinions? other suggestions
Sounds reasonable. Note that the auto_increment impl in InnoDB is all in the cursor/engine code and *not* in lower level innodb. -- Stewart Smith _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
