The following issue has been SUBMITTED. ====================================================================== http://www.dbmail.org/mantis/view.php?id=937 ====================================================================== Reported By: john Assigned To: ====================================================================== Project: DBMail Issue ID: 937 Category: installation scripts Reproducibility: always Severity: major Priority: normal Status: new target: ====================================================================== Date Submitted: 07-Nov-11 16:36 CET Last Modified: 07-Nov-11 16:36 CET ====================================================================== Summary: 2_2-3_0.mysql: cleanup required for dbmail_sievescripts Description: The MySQL upgrade script[1] for a 2.2 -> 3.0 migration does not work for the dbmail 2.2 dbmail_sievescripts table format.
This is because prior to dbmail 2.3, there is no unique constraint for (owner_idnr, name). See Bug http://www.dbmail.org/mantis/view.php?id=636 [2] for details, it seems this was not backported to 2.2, and if so, there are still users with a vanilla 2.2 schema. Please provide a workaround, or extend the script to do some cleanup of this table. The problematic statement is: ALTER TABLE dbmail_sievescripts ADD UNIQUE INDEX dbmail_sievescripts_1 (owner_idnr, name); [1] http://git.dbmail.eu/paul/dbmail/tree/sql/mysql/2_2-3_0.mysql [2] http://www.dbmail.org/mantis/view.php?id=636 ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 07-Nov-11 16:36 john New Issue ====================================================================== _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
