Hmm. I was looking at this more in depth and it occurs to me that in
these cases I would always set single-transaction explicitly. Is there
a good use case where you want to run through holland's engine auto-
detect logic with modification but you wouldn't want to simply change
the lock type?
Should we always treat the memory engine as transactional for the
purpose of mysqldump? I'm not sure that's a good idea either.
** Changed in: holland-backup
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Holland
Discuss, 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:
Incomplete
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.
_______________________________________________
Mailing list: https://launchpad.net/~holland-coredev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~holland-coredev
More help : https://help.launchpad.net/ListHelp
