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.
IT IS THE INDEX. :(
Why would MySQL be giving me duplicate errors on a MULTIPLE KEY INDEX?
I ran the following:
use bacula;
alter table File drop index FilenameID;
alter table Path drop index Path;
Error messages gone.
I haven't created new indexes yet.
I actually want a RECORD of a set of backups recorded! :)
After the 12Gig over the internet backup completes,
I will probably try a 255 sized index.
-------------------------------------------------------
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
