This notes that view errors that raise 1267 are now handled and generally holland mysqldump now handles these errors more gracefully.
- previously if a failing view was detected and MySQL raised an unknown error code, this method just reraised the original MySQLError. This converts it to a more useful BackupError so holland does not raise an uncaught exception trace. If the invalid view handling fails still this probably means more error code classes need to be detected by holland.
Only check the first line of /etc/redhat-release for a version string.
holland was previously checking os.isatty(stdin) and would disable log output to the console if this was false regardless of whether holland --quiet was used. Now console logging is only disabled with an explicit holland --quiet ... invocation. Fixes issue #98
Fixes #106 Previously some queries were passing bare strings to cursor.execute(query, param). This worked under MySQLdb 1.2.3 but fails under MySQL 1.2.5. This is likely broken on other connectors which also expect a sequence of params.
- Upstream xtrabackup has deprecated innobackupex-1.5.1 and the holland defaults have become stale