On Mar 1, 2012, at 3:13 PM, Igor Tandetnik wrote: >> I would if I could. Unfortunately, in SQLite, in the case of unique >> constraints, this cannot be done as far as I know. Or? > > Just create a unique index, in lieu of unique constraint.
I would rather see SQLite support some sort of USING INDEX [1] clause for constraints, e.g.: constraint fubar unique( baz ) using index( /* index clause */ ) Or something... I know, wishful thinking, but hope is eternal :D > >> (2) If one create an unique, named index, one cannot use an unique constraint > > Why would one want to? For completeness' sake and the metadata it provides. Otherwise, functionally, in SQLite, they are both identical in practice as one gets an unique index either ways. It's just another case where there is a disconnect in the data dictionary. Sigh... [1] http://docs.oracle.com/cd/B28359_01/server.111/b28310/indexes003.htm#i1006566 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
