Gary, > Keyname Type Cardinality Field > PRIMARY PRIMARY 0 id > id UNIQUE 0 id > users_idx_email INDEX None email > PRIMARY and INDEX keys should not both be set for column `id` > > Using "SERIAL PRIMARY KEY" appears to have created a new problem. > It looks like it creates two indexes. > > Reverting back to: "INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY" > solves the newly introduced problem, at least I think it does, > as now I get: > Keyname Type Cardinality Field > PRIMARY PRIMARY 0 id > users_idx_email INDEX None email
Thanks for pointing it out. You are right. The reason is probably because SERIAL stands for BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE, the culprit being the UNIQUE, which creates an index on its own, and since the 'id' is already a primary key with an implicit index, the 'id' field now has two indices. It is a waste of resources, although is not harmful. I modified the README.sql to reflect this: http://www.ijs.si/software/amavisd/README.sql.txt Mark ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
