(1) Added output of 'diff -u' as requested by Clint Byrum (see attachment)
(2) Test case:
-----------------
To reproduce the problem, MySQL database must contain at least 2 schemas with a view definition; say 'schema1.'view1' and 'schema2.view2'
When you run the command 'mysqlhotcopy --user=backup schema1 schema2 <some backup directory>', you get the syntax error as described in bug report.
Problem description:
----------------------------
Script mysqlhotcopy creates internally the following MySQL statement: LOCK TABLES schema1.view1 , schema2.view2 READ
which is invalid. Correct syntax is: LOCK TABLES 'schema1.view1' READ, 'schema2.view2' READ
(3) Question:
-----------------
There was a comment, that mysqlhotcopy should not be used any more in future releases.
Which solution/alternative do you recommend instead for doing _online_ backup?
(by the way: I don't use InnoDB but MyISAM)
(1) Added output of 'diff -u' as requested by Clint Byrum (see attachment)
(2) Test case:
-----------------
To reproduce the problem, MySQL database must contain at least 2 schemas with a view definition; say 'schema1.'view1' and 'schema2.view2'
When you run the command 'mysqlhotcopy --user=backup schema1 schema2 <some backup directory>', you get the syntax error as described in bug report.
Problem description: ------- ------- -------
-------
Script mysqlhotcopy creates internally the following MySQL statement: LOCK TABLES schema1.view1 , schema2.view2 READ
which is invalid. Correct syntax is: LOCK TABLES 'schema1.view1' READ, 'schema2.view2' READ
(3) Question: alternative do you recommend instead for doing _online_ backup?
-----------------
There was a comment, that mysqlhotcopy should not be used any more in future releases.
Which solution/
(by the way: I don't use InnoDB but MyISAM)
Best regards,
leonick