On Wed, Sep 15, 2010 at 8:25 PM, Roger Binns <rog...@rogerbinns.com> wrote: > On 09/15/2010 06:00 PM, Cory Nelson wrote: >> SQLite doesn't support automatic indexing, > > And your basis for that claim is? >
This might not be doing what you think it is. When you have a query that will do a full table scan multiple times, SQLite can sometimes create an index to make it only do a full table scan once, and use the index every time after that. The index doesn't stick around though -- it is deleted as soon as your query ends, and remade every time you run it. Since they are created per-query, there's no way to tune them prior to when you run them. While faster than the alternative, it's still very expensive and really only useful if your queries are very rare and can stand to run slowly, or if you've got no clue what queries will be run. They're not meant to make development easier by replacing permanent indexes. It sounds like you already know which columns will be queried against. You should probably be creating permanent indexes. -- Cory Nelson http://int64.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
