holland-coredev team mailing list archive
-
holland-coredev team
-
Mailing list archive
-
Message #00134
[Bug 670192] Re: Specify engines to be treated as transactional
Good catch. :) This was caused by a typo where I was treating a function
(Database.is_transactional()) as an attribute so it was always true
introduced when I had cleaned up some of the auto-detection code. That
really should be a property in order to be consistent with how
Table.is_transactional is handled by the schema walking code. I just
pushed a fix for that and I am getting the expected behavior with this
test case now.
--
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/670192
Title:
Specify engines to be treated as transactional
Status in Holland Backup Framework:
In Progress
Bug description:
It would be useful to have a configuration option to specify which
engines are to be considered transactional when determining whether or
not to use --single-transaction in mysqldump providers. An example
would be a schema that has 5 InnoDB tables and one HEAP table being
downgraded to using --lock-tables.
References