holland-coredev team mailing list archive

[Andrew Garner <962436@xxxxxxxxxxxxxxxxxx>]

I think a better bug to reference is:
http://bugs.mysql.com/bug.php?id=55587

This behavior was difference prior to the RC+1 release (5.1.23)) and the
note in the changelog is pretty subtle.   Nevertheless this is a bit of
braindamage in holland-mysqldump - we probably should correct the
default behavior rather than requiring events to be explicitly enabled
we should instead allow for them to be explicitly disabled, if desired.

** Bug watch added: MySQL Bug System #55587
   http://bugs.mysql.com/bug.php?id=55587

** Changed in: holland-backup
       Status: New => Confirmed

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

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

Title:
  holland-mysqldump events documentation bug

Status in Holland Backup Framework:
  Confirmed

Bug description:
  In light of http://bugs.mysql.com/bug.php?id=16853 we should change
  the default behavior or documentation regarding events

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