Quoth Maciej Lotkowski <maciej.lotkow...@gmail.com>, on 2011-02-16 09:45:45 +0100: > It's not about the real use case. I understand, that having such a > primary key probably doesn't make much sense. I'm asking if it is > technically possible to create a table like > > create table foo ( > id integer not null autoincrement, > another_id integer not null, > primary key(id, another_id) > ) > > > without Error: near "autoincrement": syntax error.
No. Note that you can create an PRIMARY KEY AUTOINCREMENT and have a separate compound UNIQUE constraint including that column, but that doesn't allow (A, B) and (A, C) to exist simultaneously. ---> Drake Wilson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
