Nikolaus Rath <nikol...@rath.org> wrote: > After creating another index, it seems to work: > > sqlite> create index foo on contents(parent_inode); > sqlite> explain query plan SELECT name_id, inode, rowid FROM contents WHERE > parent_inode=42 AND rowid > 12932 ORDER BY rowid; > 0|0|0|SEARCH TABLE contents USING INDEX foo (parent_inode=?) (~3 rows) > > Is that a good solution, or am I missing something? I assume that SQLite > deliberately chose the new index to avoid the explicit sorting, rather > than just because it was the first one at hand?
I believe SQLite did choose the new index deliberately, yes. -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
