This isn't true for innodb. I think the only requirement is that you need to have a unique index on the auto increment column. We created a composite primary key + auto_increment to take advantage of clustering by primary key while satisfying unique constraint for the primary key. It worked out well for us except for the sheer size of the indexes. Kyong
2010/6/29 João Cândido de Souza Neto <j...@consultorweb.cnt.br>: > As far as I know, if you have an auto_increment primary key, you cant have > any other field in its primary key. > > > João Cândido. > > "Victor Subervi" <victorsube...@gmail.com> escreveu na mensagem > news:aanlktikzksmbx5hue0x_q3hx_68gicndghpkjdrna...@mail.gmail.com... >> Hi; >> I have the following: >> >> create table pics ( >>  picture_id int auto_increment primary key, >>  product_sku int not null primary key, >>  picture_num int not null, >>  picture_desc varchar(100), >>  picture_data longblob >> ); >> >> which doesn't work I need to auto_increment and declare primary key on two >> fields. How do? >> TIA, >> Victor >> > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:   http://lists.mysql.com/mysql?unsub=kykim...@gmail.com > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
