holland-coredev team mailing list archive

[Andrew Garner <670192@xxxxxxxxxxxxxxxxxx>]

In holland 1.1's mysqldump plugin I've added three settings for fine-
tuning the --single-transaction auto-detection logic:

transactional-databases-override => Always treat an entire database (or list of databases) as transactional
transactional-tables-override => always treat a specific table (or list of tables) as transactional
transactional-engines-override => always treat a specific storage engine (or list of engines) as transactional

innodb is always considered transactional, but additional engines can be
flagged as suitable for --single-transaction in holland as well (e.g.
memory, sphinx, myisam, etc.)

I'm currently testing this in my branch here:

https://github.com/abg/holland/tree/amsterdam

And this will be merged into the main amsterdam branch of holland-
backup/holland for alpha release probably later this week/early next
week.

** Changed in: holland-backup
       Status: Confirmed => In Progress

-- 
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.