Kees Nuyt <k.n...@zonnet.nl> wrote: > If you need a compound index for performance reasons, you can use > the autoincrement key as the primary key for the table and define a > unique index on the compound key.
I can't think of any statement that would run faster if you, in addition to an existing unique index on A, also create one on (A, B). Am I missing something obvious? -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
