Am 18.11.2013 22:35, schrieb Jorge Bastos: >>> 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; > > I'm already there with 2.3.6, already have this table
this is the output of "show create table" and should show how the scheme looks like, in that context it does not matter what exists, that's what "alter table" is for
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
