Its not the primary Key. There are more fields but the index on id is created also. Sorry I missed it in the post.
If I do a EXPLAIN QUERY PLAN sqlite tells me its going to use the id INDEX. But the sorting is slow. Thanks in advance On Tue, Jun 29, 2010 at 5:32 PM, Jim Morris <jmor...@bearriver.com> wrote: > You also haven't specified a primary key, i.e. on "id" > > On 6/28/2010 11:24 PM, J. Rios wrote: > > I have the next table > > > > table1( id INTEGER, name VARCHAR, id2 INTEGER, name2 VARCHAR, year > INTEGER > > ); > > > > I have created the next indexes : index1( name ), index2( id2 ), index3( > > name2 ); > > > > > _______________________________________________ > 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
