holland-coredev team mailing list archive
-
holland-coredev team
-
Mailing list archive
-
Message #00129
[Bug 670192] Re: Specify engines to be treated as transactional
Ah you read my mind. I was thinking after posted my last update that
actually having aliases would be the best of both worlds. I don't think
it matters, but I think the long version should be the default (non-
alised) since it explains the most about what the command does without
any assumption.
How many aliases can we have? I don't think we need to go crazy making
aliases but people who hate to type could use really compact things
might be happy if we had really small config options (like 'tx-dbs-
ovrrde'). I think just shortening transaction goes a long way though.
--
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