Am 17.11.2013 22:19, schrieb Jorge Bastos: > I’m doing some tests with real data but with a copied machine, and applying > an index from the sql changes I have: > > CREATE UNIQUE INDEX dbmail_envelope_1 ON dbmail_envelope(physmessage_id);
you should avoid random index names! 2_2-3.0.mysql contains different index-names and that may lead to fail future upgrades removing named indexes and adding new ones which was also part of 3.0 migartion where such differences hurted me CREATE TABLE IF NOT EXISTS `dbmail_envelope` ( `physmessage_id` bigint(20) unsigned NOT NULL DEFAULT '0', `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `envelope` text NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `physmessage_id_1` (`physmessage_id`), UNIQUE KEY `physmessage_id_2` (`physmessage_id`,`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=COMPRESSED; > ERROR 1062 (23000): Duplicate entry '2424860' for key 3 > I saw and I have about 4000 records with this problem. > > Question is, can i: > > Truncate dbmail_envelope; > Apply the new unique index and then: > > dbmail-utils –yb ? surely, the 2.2-3.0 migration in fact contains >> -- Empty cache tables >> TRUNCATE TABLE dbmail_envelope;
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
