Package: mysql-server-5.0
Version: mysql-dfsg-5.0 5.0.45-1

I guess this should be fixed upstream, but upstream bug opened
at 20th March, 2007 with "Severity: S1 (Critical)", yet not seem
to be fixed.
(http://bugs.mysql.com/bug.php?id=27303)

Patch and all other previous details:


----- Original Message ----- From: Gabor FUNK To: [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] Sent: Sunday, August 05, 2007 10:45 AM
Subject: Fw: 5.0.41a-1 - mysqlhotcopy error


I know mysql package is a bit orphaned, and mysqlhotcopy has even
less priority, but I provide a patch to fix stil existing mysqlhotcopy
"error", hoping that it will make into the distribution....


#--8<----------------------

--- mysqlhotcopy.ori 2007-06-25 03:05:26.000000000 +0200
+++ mysqlhotcopy 2007-08-05 10:37:51.000000000 +0200
@@ -837,6 +837,7 @@
    });

    my @dbh_tables = eval { $dbh->tables() };
+    map { s/^.*?\.//o } @dbh_tables;

    ## Remove quotes around table names
    my $quote = $dbh->get_info(29); # SQL_IDENTIFIER_QUOTE_CHAR

#--8<----------------------


Cheers, G.



----- Original Message ----- From: "Gabor FUNK" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 02, 2007 10:28 AM
Subject: 5.0.41a-1 - mysqlhotcopy error


I recently updated my testing system, mysql is at 5.0.41a-1 now.
Before mysqlhotcopy was working well, after the upgrade it
displayed the following error message:

Invalid db.table name 'foo.foo`.`bar' at /usr/bin/mysqlhotcopy line 859.
(real example:
Invalid db.table name 'huweb-forum.huweb-forum`.`phpbb_attach_quota' at /usr/bin/mysqlhotcopy line 859. )

This seems to be sort of upstream - but it is only in "verified" status.
http://bugs.mysql.com/bug.php?id=27303

As described above, it can be fixed by adding a line containing:
   map { s/^.*?\.//o } @dbh_tables;
after line 839 which is my @dbh_tables = eval { $dbh->tables() };
(This is mysqlhotcopy v1.22, size 33225, dated Jun 25, 03:05)

I can confirm that this works indeed .

G.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to