On Sep 5, 2008, at 3:01 AM, [EMAIL PROTECTED] wrote: > >> One occasionally sees SQLite schemas of the following form: >> >> CREATE TABLE meta(id LONGVARCHAR UNIQUE PRIMARY KEY, ....); >> >> In other words, one sometimes finds a PRIMARY KEY and a UNIQUE >> declaration on the same column. This works fine in SQLite, but it is >> wasteful, both of disk space and of CPU time. > > I'm trying to reproduce the issue, but I only see a single index. > What am I missing? >
I stand corrected. What I said was true for SQLite version 2.x. But the problem was fixed during the file format change going from the 2.8.14 series to 3.0.0. The fix occurred with check-in #1575 on 2004-05-12. Dan made that fix and I never noticed. I've been telling people ever since that UNIQUE PRIMARY KEY generated a redundant index. Good that I've finally been straightened out on that point. Sorry for the false alarm.... D. Richard Hipp [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
