holland-coredev team mailing list archive

[Andrew Garner <1204208@xxxxxxxxxxxxxxxxxx>]

holland-mysqldump has a list of database names easily available so
aborting here if len(databases) is 0 is an easy fix here.

Regarding restricted grants, mysqldump will silently skip triggers if
the available privilege is not defined.   This can be caused by not
upgrading a 5.0 instance -> 5.1 for instance where a user may not have
the TRIGGER privilege (or forgetting to give the backup user SUPER
privileges).   It would be nice for holland to understand its granted
options and at least log a warning - if not conditionally fail in these
cases.   I can think of a few cases where this may be intentional, so
perhaps an option to skip this sort of failure (e.g. ignore-
insufficient-grants) would make sense.

-- 
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/1204208

Title:
  mysqldump plugin exits without error when grant is only usage

Status in Holland Backup Framework:
  New

Bug description:
  When you have mysqldump provider configured to use an account with
  "GRANT USAGE ON *.* TO", holland will exit cleanly despite no
  databases being backed up. This should probably be an error condition
  when zero databases are exported, though we currently allow restricted
  grants to act as a filtering method without an explicit exclude in the
  backupset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/holland-backup/+bug/1204208/+subscriptions