holland-coredev team mailing list archive

[m00dawg <tim@xxxxxxxxxxxxxxxxxxxxx>]

Online docs (1.0 and 1.1) are also a bit vague:

"additional-options = <mysqldump arguments>

Can optionally specify additional options directly to mysqldump if there
is no native Holland option for it."

That said, I wonder if it would be better to use the latter syntax (if
possible) as it feels more like what you would put on the command-line?
Otherwise, yes, this needs updating and clarification.

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

Title:
  mysqldump additional-options behavior discrepancy

Status in Holland Backup Framework:
  New
Status in holland-backup 1.0 series:
  New
Status in holland-backup 1.1 series:
  New

Bug description:
  The mysqldump plugin expects the 'additional-options' setting to
  provide a comma separated list.   However the configspec currently has
  a comment that notes this should be provided "exactly as on the
  command line".  This causes multiple options to be misinterpretted
  (and mysqldump will fail) and is confusing.   The
  comment/documentation at least needs to be clear on the format
  required here and possibly the implementation updated.

  Example:

  additional-options = --no-data, --routines # OK
  additional-options = --no-data --routines # misinterpreted as mysqldump "--no-data --routines"

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