holland-coredev team mailing list archive

[Andrew Garner <801691@xxxxxxxxxxxxxxxxxx>]

Fixing additional-options is difficult now, since it has been a comma
separated list for a long time before this bug was opened.  In holland
1.1+ option aliases in config files are supported so we can potentially
fix this there while maintaining compatibility by providing a separate
option name.

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

** Changed in: holland-backup
     Assignee: (unassigned) => Andrew Garner (muzazzi)

** Changed in: holland-backup
   Importance: Undecided => Low

** Changed in: holland-backup
    Milestone: None => 1.1.0a3

-- 
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:
  In Progress
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