Thank you. That clear things up. On Fri, May 10, 2013 at 11:28 PM, Nico Williams <[email protected]>wrote:
> On Sat, May 11, 2013 at 1:12 AM, Igor Korot <[email protected]> wrote: > > On Fri, May 10, 2013 at 11:07 PM, Nico Williams <[email protected] > >wrote: > >> It'd help if you posted a simplified schema and statements that are > >> not planned correctly by SQLite3. > > > > I'm not saying that my statements are not planned correctly. > > What I'm saying is that by reading the link above _I_ gather: > > > > Using index will eliminate the need of B-Tree. > > > > However, it simply not true. Or is it? > > SQLite3 only implements B-trees. What that page says is that in some > cases SQLite3 will create a temporary B-tree to help with sorting, and > in other cases SQLite3 can take advantage of an existing index. But > the index will still be a B-tree, and it's not implied that it > wouldn't be. > > Nico > -- > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
