Dear all,
I am having the same problem as Linda with a fresh installation of version 20130603. In the thread of her mail Dannon Baker said : "That said, this doesn't resolve the mysql index issues, which I'm currently working on. I hope to have a fix for them available soon, though."
I would like to know if what is the status of this thread. Should I use the solution provided in Linda's mail (CREATE INDEX ix_history_slug ON history (slug(1000));)
Thx a lot for your help
Best
Jean-François
On 06/05/2013 05:12 PM, Linda Cham wrote:
Hi. I am new to the Galaxy forum and I am trying to setup a new local Galaxy instance with MySQL on RH6.2 x86_64.
On a newly installed OS node, using the hg clone command (hg clone _https://bitbucket.org/galaxy/galaxy-dist#stable_ https://bitbucket.org/galaxy/galaxy-dist) which gets the current Galaxy 20130603 image, I am getting the following errors when running run.sh: File "build/bdist.linux-x86_64-ucs4/egg/MySQLdb/cursors.py", line 173, in execute self.errorhandler(self, exc, value) File "build/bdist.linux-x86_64-ucs4/egg/MySQLdb/connections.py", line 36, in defaulterrorhandler raise errorclass, errorvalue OperationalError: (OperationalError) (1170, "BLOB/TEXT column 'slug' used in key specification without a key length") 'CREATE INDEX ix_history_slug ON history (slug)' ()
Reading the forum, someone stated it can be bypass by running the CREATE INDEX.
mysql> CREATE INDEX ix_history_slug ON history (slug(1000)); Query OK, 0 rows affected (0.09 sec) Records: 0 Duplicates: 0 Warnings: 0