Apparantly the bug does not go away after upgrading MySQL (appears to be an error in the table itself).
After upgrading MySQL, I had to do
alter table XXXX engine=InnoDB; alter table XXXX engine=MyIsam; create index ....;
and now all seems well.
Jeff McCune wrote:
Michael Joyner wrote:Jeff McCune wrote:
I ran the following:
use bacula; alter table File drop index FilenameID; alter table Path drop index Path;
Error messages gone.
IT ISN'T THE INDEX!
When you ran the statement: alter table File drop index FilenameID; I think you REMOVED THE PRIMARY KEY from the File table.
According to the description of Path, the primary key on PathId still exists.
mysql> describe Path; +--------+------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +--------+------------------+------+-----+---------+----------------+ | PathId | int(10) unsigned | | PRI | NULL | auto_increment | | Path | blob | | | | | +--------+------------------+------+-----+---------+----------------+ 2 rows in set (0.00 sec)
As it should... I think you removed the primary key from the *File* table, not the Path table.
What's describe File; look like?
Look at your two alter table statements more closely...
Regards,
------------------------------------------------------- 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
