Many thanks, it's a good news that resolve my problem. But still remain "a trick", i think the behaviour descripted in my original feedback is "strange".. i understand, if all fields have the same value, an index on that have a zero "height" in computing the best indexes to use, but not use index at all and do a full-table-scan, for what i understand about sqlite, imho is strange...
Thanks again! Clodo > Greetings, Clodo, > > Regarding: "[is it]possible to force the use of the index?" > > The very latest release of sqlite, 3.6.4, implements precisely that, in > the form of an "INDEXED BY" clause. > > See: > http://www.sqlite.org/releaselog/3_6_4.html > Specifically: > http://www.sqlite.org/lang_indexedby.html > > There was a flurry of discussion regarding "INDEXED BY" just before its > release if you want to search the archives of this list, but the link > above may be all you need at this point. > > I can't speak to other parts of your question. > > Regards, > Donald Griggs > > _______________________________________________ > 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 > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
