Hi,
In past attempts at improving query performance these have
been added to encourage it to use an index that it can do a
SCAN thru' rather than the table that it would need to do a
SEARCH thru'.
SQLite is not using the PRIMARY INDEX to immediately locate the
appropriate row, but is actually faster when you fake it into
using a longer index ? That's weird.
There is more than one row returned. Potentially several million.
...so it's quicker to do a linear scan thru' something that's in the same
order (table or index) rather than a series of tree accesses for each and
every row.
Best wishes,
@ndy
--
andy...@ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
