Hi!
In working on replication I end up in our transaction code. Today DDL
causes whatever transaction that is in play to commit.
Is this really a good behavior?
I am looking at cleaning up the API so that an engine will be able to
do transactional DDL (assuming it can handle it). This piece of
behavior is going to cause this to become... messy.
Should we toss an error on DDL if the engine does support it
transactionally? Current behavior good enough/would break too much to
change?
What is the proper behavior?
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
