>> Would be interesting to see >> when and where that single index comes into play when multiple indexes >> are >> defined.
>MS SQL allows for many sorts of indexes, and SQLite has only one. MS SQL >has a Tuning Wizard, which will recommend indexes to create or drop, but >SQLite has a better query optimiser which is better at figuring out which >index (per table) to use, partly because it can use the results of >ANALYZE. No access method (yet invented) in any product (yet invented) can use more than a single traversal path through a collection of data at any given time during a single traversal operation. I believe this is a physical constraint of the universe in which we exist (or the rules of the computer simulation which we perceive as reality). _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
