Kern Sibbald wrote:
Hello,
It looks to me like MySQL 4.0 has changed the way they deal with indexing and
keys since version 3.23.51. It appears as if they are using *only* the index
to decide if the key is unique or not. The index was setup on the first 50
characters of the path. Previously, the index was used for indexing only and
not to determine uniqueness.
Did you recently upgrade to MySQL 4.0? The solution I can see is to drop the
index on Path and the index on Filename, then recreate them but create them
on the full Path and the full Name rather than limiting it as is currently
the case in the make_mysql_tables file.
Would just running an alter table fix it?
If so, what is the sql statement that you would recommend?
This is not an upgrade. This is a brand new installation.
On Sunday 20 March 2005 20:11, Michael Joyner wrote:
Hi!
I am getting the following errors on backup.
Using bacula-mysql for SuSE 9.1
I ran the dbcheck, and all it does is delete "orphaned" files and
insists there are no duplicate records anywhere.
So now what do I do?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
