+roundcube (0.5-2) experimental; urgency=low
+
+ * If 0.3.1 was installed from scratch, upgrade does not work on MySQL
+ and PostgreSQL because we try to create an index which already
+ exists. With SQLite, the error is ignored. When using PostgreSQL, drop
+ the index if it already exists. Nothing similar seems to exist with
+ MySQL. Therefore, just don't create the index. We need to handle this
+ later. See bug #610725. Not closing.
+
+ -- Vincent Bernat <bernat@debian.org> Fri, 21 Jan 2011 21:44:05 +0100
+
roundcube (0.5-1) experimental; urgency=low
* New upstream release. Closes: #592312.
TRUNCATE `messages`;
-ALTER TABLE `messages`
- ADD INDEX `index_index` (`user_id`, `cache_key`, `idx`);
+-- ALTER TABLE `messages`
+-- ADD INDEX `index_index` (`user_id`, `cache_key`, `idx`);
-ALTER TABLE `session`
- CHANGE `vars` `vars` MEDIUMTEXT NOT NULL;
+-- ALTER TABLE `session`
+-- CHANGE `vars` `vars` MEDIUMTEXT NOT NULL;
-ALTER TABLE `contacts`
- ADD INDEX `user_contacts_index` (`user_id`,`email`);
+-- ALTER TABLE `contacts`
+-- ADD INDEX `user_contacts_index` (`user_id`,`email`);
-- Updates from version 0.3.1
-- WARNING: Make sure that all tables are using InnoDB engine!!!
-- Updates from version 0.3-stable
TRUNCATE messages;
+DROP INDEX IF EXISTS messages_index_idx;
CREATE INDEX messages_index_idx ON messages (user_id, cache_key, idx);
DROP INDEX contacts_user_id_idx;
CREATE INDEX contacts_user_id_idx ON contacts (user_id, email);