Hi!
On Jul 24, 2009, at 1:56 AM, Paul McCullagh wrote:
We discussed this on Drizzle Day, and that was my recommendatio
++
This would mean, after a transaction has committed, the replication
system asks the engine for a "list of operations" that were
performed by the transaction.
To make this happen... you would need to skip the trigger for the
replication, not hard, and then have a separate thread convert the log
to protos and push it into the replication storage piece.
Yes... native log would be faster (aka skip the system), but you would
lose out on having filtering/transportable/scriptable... for some I am
sure the speed would be great, but I suspect most would want
flexibility.
The nice thing about this? It is entirely up to whomever writes the
plugins :)
Cheers,
-Brian
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
