The main goal here would be to not lock by default on a schema which has innodb tables and one memory table. Whether that is to treat memory as transactional by default, just grab the DDL for memory tables before doing the dump, or anything similar, I would consider this resolved.
-- 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
