holland-coredev team mailing list archive

[Andrew Garner <1262352@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The metadata path in MySQL 5.0 fails to detect invalid views with a
broken query.   This is due to not correctly setting the engine type.
On MySQL 5.1+ this is set as 'view' when a view is detected, but with
5.0 this is set to '' and only a warning is logged.  This is a bug.

This affects the client show_metadata*() method for 5.0 and is a simple
fix.

** Affects: holland-backup
     Importance: Critical
     Assignee: Andrew Garner (muzazzi)
         Status: In Progress

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

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

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

** Changed in: holland-backup
    Milestone: None => 1.0.12

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

Title:
  exclude-invalid-views can fail on MySQL 5.0

Status in Holland Backup Framework:
  In Progress

Bug description:
  The metadata path in MySQL 5.0 fails to detect invalid views with a
  broken query.   This is due to not correctly setting the engine type.
  On MySQL 5.1+ this is set as 'view' when a view is detected, but with
  5.0 this is set to '' and only a warning is logged.  This is a bug.

  This affects the client show_metadata*() method for 5.0 and is a
  simple fix.

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