Question: Manage_Db: Mysql Error 1059
0
Pieter Neerincx • 360 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... 0010_hda_display_at_authz_table DEBUG 2009-08-05
13:52:36,228 Creating
history_dataset_association_display_at_authorization table failed:
(OperationalError) (1059, "Identifier name
'ix_history_dataset_association_display_at_authorization_update_time'
is too long") u'CREATE INDEX
ix_history_dataset_association_display_at_authorization_update_time ON
history_dataset_association_display_at_authorization (update_time)' {}
0010_hda_display_at_authz_table DEBUG 2009-08-05 13:52:36,228 Creating
history_dataset_association_display_at_authorization table failed:
(OperationalError) (1059, "Identifier name
'ix_history_dataset_association_display_at_authorization_update_time'
is too long") u'CREATE INDEX
ix_history_dataset_association_display_at_authorization_update_time ON
history_dataset_association_display_at_authorization (update_time)' {}
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:
mysql> describe history_dataset_association_display_at_authorization;
+--------------------------------+--------------+------+-----+--------
-
+----------------+
| Field | Type | Null | Key | Default
| Extra |
+--------------------------------+--------------+------+-----+--------
-
+----------------+
| id | int(11) | NO | PRI | NULL
| auto_increment |
| create_time | datetime | YES | | NULL
| |
| update_time | datetime | YES | | NULL
| |
| history_dataset_association_id | int(11) | YES | MUL | NULL
| |
| user_id | int(11) | YES | MUL | NULL
| |
| site | varchar(255) | YES | | NULL
| |
+--------------------------------+--------------+------+-----+--------
-
+----------------+
6 rows in set (0.01 sec)
and I have the following indices on this table:
mysql> show index from
history_dataset_association_display_at_authorization;
+------------------------------------------------------+------------
+------------------------------------------+--------------
+--------------------------------+-----------+-------------+----------
+--------+------+------------+---------+
| Table | Non_unique |
Key_name | Seq_in_index |
Column_name | Collation | Cardinality | Sub_part |
Packed | Null | Index_type | Comment |
+------------------------------------------------------+------------
+------------------------------------------+--------------
+--------------------------------+-----------+-------------+----------
+--------+------+------------+---------+
| history_dataset_association_display_at_authorization | 0 |
PRIMARY | 1 |
id | A | 0 | NULL |
NULL | | BTREE | |
| history_dataset_association_display_at_authorization | 1 |
user_id | 1 |
user_id | A | NULL | NULL |
NULL | YES | BTREE | |
| history_dataset_association_display_at_authorization | 1 |
ix_hdadaa_history_dataset_association_id | 1 |
history_dataset_association_id | A | NULL | NULL |
NULL | YES | BTREE | |
+------------------------------------------------------+------------
+------------------------------------------+--------------
+--------------------------------+-----------+-------------+----------
+--------+------+------------+---------+
3 rows in set (0.00 sec)
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?
Cheers,
Pi
Biomolecular Mass Spectrometry and Proteomics
Utrecht University
Visiting address:
H.R. Kruyt building room O607
Padualaan 8
3584 CH Utrecht
The Netherlands
Mail address:
P.O. box 80.082
3508 TB Utrecht
The Netherlands
phone: +31 (0)6-143 66 783
email: pieter.neerincx@gmail.com
skype: pieter.online