Hi,
As long as line 7 is actually a 'DROP INDEX' you should be fine, it just
means the index it was doing to remove wasn't there.
With mySQL, when you run 'describe messages' it will only show the
columns from the table, not any indexes. If you want to show indexes,
use 'show index in messages'.
On 24/10/2011 9:16 PM, Simon Loewenthal wrote:
Hi,
After a RC upgrade (.5.4 -> 0.6), can one blindly run the
mysql.update.sql, or should I adjust it accordingly to the release I am
upgrading from? I ask as I tried and it complained:-
root@peon /www/roundcube/SQL # mysql*-p roundcubemail < mysql.update.sql *
Enter password:
ERROR 1091 (42000) at line 7: Can't DROP 'idx'; check that column/key exist
Entry in the mysql.update.sql reads:
ALTER TABLE `messages`
DROP INDEX `idx`,
DROP INDEX `uid`;
mysql> describe messages;
+------------+------------------+------+-----+---------------------+----------------+
| Field | Type | Null | Key | Default |
Extra |
+------------+------------------+------+-----+---------------------+----------------+
| message_id | int(11) unsigned | NO | PRI | NULL |
auto_increment |
| user_id | int(10) unsigned | NO | MUL | 0
| |
| del | tinyint(1) | NO | | 0
| |
| cache_key | varchar(128) | NO | | NULL
| |
| created | datetime | NO | MUL | 1000-01-01 00:00:00
| |
| *idx* | int(11) unsigned | NO | | 0
| |
| *uid* | int(11) unsigned | NO | | 0
| |
| subject | varchar(255) | NO | | NULL
| |
| from | varchar(255) | NO | | NULL
| |
| to | varchar(255) | NO | | NULL
| |
| cc | varchar(255) | NO | | NULL
| |
| date | datetime | NO | | 1000-01-01 00:00:00
| |
| size | int(11) unsigned | NO | | 0
| |
| headers | text | NO | | NULL
| |
| structure | text | YES | | NULL
| |
+------------+------------------+------+-----+---------------------+----------------+
15 rows in set (0.00 sec)
Regards, S