Yes, that's exactly what it is. Here is the definition of one of the table:
CREATE TABLE [Attributes] ( [Id] INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, [Name] VARCHAR(50) NOT NULL ) Will creating explicit index on Id fix this issue? Thanks. On Thu, Jun 23, 2011 at 11:07 PM, Dan Kennedy <danielk1...@gmail.com> wrote: > On 06/24/2011 12:26 PM, logan...@gmail.com wrote: > > Hello, > > > > My understanding is that an index is automatically created on any column > > that is used in the primary key (or a composite index is created if the > key > > is composed of different columns). If this is correct then why don't I > see > > indexes for those in my table (I'm using SQLite Administrator and Firefox > > plugin based SQLite manager). I do see indexes for the columns that I > added > > a unique constraint upon. > > > > Is the above just a GUI error in these tools or an index need to be > created > > separately on the columns used in primary keys? > > Maybe your tables have "integer primary keys". Those are an exception > See here: > > http://www.sqlite.org/lang_createtable.html#rowid > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
