Hi, I started the work to evaluate the innodb trx log: https://blueprints.launchpad.net/drizzle/+spec/evaluate-innodb-trx-log
At present, we are stuck due to this bug: https://bugs.launchpad.net/drizzle/+bug/708102 transaction_reader utility dumping generated SQL out of order when using innodb trx log When we call the transaction_reader, the generated SQL is in craaaazy order- we are altering tables that haven't been created in schemas that don't exist yet : ( Once we have a means of extracting data from the log so that it can populate a validation server, we can proceed with making sure that the log accurately reflects the state of the master. Until then, we are a bit stuck. Thanks, Patrick
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
