Hi Pieter,
I moved this over to the galaxy-dev list since it's related to a local installation.
Pieter Neerincx wrote:
Hi,
I upgraded today from a Galaxy release from about a month ago and got this error when I ran the manage_db script:
7 -> 8... done 8 -> 9... done 9 -> 10... done 10 -> 11... done
This is with MySQL 5.0.45-7.el5 (on CentOS 5.3). Manual inspection shows that despite the error the table was created:
and I have the following indices on this table:
I guess that the ix_hdadaa_history_dataset_association_id is the abbreviated name for ix_history_dataset_association_display_at_authorization_update_time... or not? The question is can I safely ignore the update error or do I have a problem?
Database version 11 was created to fix the problem in 10. MySQL has a name length limit and thus the index has to be manually created. You can safely ignore these errors.
--nate