Drizzle devs, I was reviewing the filtered_replicator code and I found that the plugin removes filtered queries from the transaction event. I haven't tested it, but it seems that if table foo is being filtered, then this transaction,
update foo set ... insert into bar ... becomes simply, insert into bar ... That seems odd to me because 1) the same transaction has two contents (on the master it has 2 statements, on the slave it will have 1) and 2) if statement 2 uses data created/modified by statement 1 but statement 1 is filtered then statement 2 will fail or worse. I would not expect a _filter_ to modify things, especially not the contents of transactions. Is it just too late for me to be coding, or does anyone else agree that filtered_replicator is doing something very bad? -Daniel _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
