-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All,
As I was hacking on the new replication code today, I noticed that Drizzle (and MySQL 6) is passing through REPAIR, OPTIMIZE, and ANALYZE TABLE statements as-is into the binlog and the replication stream. Oddly, CHECK TABLE is not replicated. ?. Question: Should any of these statements be replicated or sent to a binary log? I'm currently more concerned with the replication, but the binlog will be getting re-built based on the replicator so it's relevant. As some of you may know, Drizzle only does row-based replication. But...what if there are no rows to replicate? :) DDL statements such as CREATE TABLE or DROP TABLE and administrative statements such as OPTIMIZE TABLE don't actually affect *rows*. The way that MySQL handles this is to simply replicate the SQL statement using statement-based replication when it sees these statements (with certain exceptions around temporary tables). Should Drizzle replicate any administrative commands at all? Personally, I don't see the value in replicating them or storing them in a recovery log either...but...input is always welcome! Thanks in advance, - -jay -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknS47gACgkQ2upbWsB4UtHiZwCfbBTYVfDWaT/haWG/m2/X/oaN R4sAnijKO1c3jYaC0yFrdvDVibI01/P6 =2PTW -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
