Have you read this document? http://sqlite.org/optoverview.html
<http://sqlite.org/optoverview.html>I think it's good start for you. The main rule of optimizer is whether the query uses an index. On Wed, Nov 18, 2009 at 12:03 AM, P Kishor <[email protected]> wrote: > Recent travails of the user trying to figure out how the optimizer > figures out how to optimize query with a LIKE clause set me > thinking... I really don't know anything about this optimizer. When I > work with a db, I spend a considerable amount of time thinking about > the most appropriate db structure, and then, the most appropriate > queries, but then, it seems that I hand it over to this optimizer > that, as Richard said, evaluates "hundreds, thousands" or way of doing > the query, and then chooses the best one. Once it chooses that way, it > sticks with that way until something about the query changes. > > Except, I know nothing about this optimizer. Richard is a smart guy... > he created SQLite, and the optimizer. But, is he so smart that he can > figure out the best way to run every query that will ever be handed to > SQLite? ;-) > > In this time and world of open source, am I submitting my precious > query to a black box I know nothing about? > > Where can I learn more about this optimizer? Where can I sign up? > > Oh, if you tell me that I should read the SQLite source code, that > will be the correct, open source specific answer. However, I am hoping > someone can point me to a "optimizer for dummies" version. > > > -- > Puneet Kishor > _______________________________________________ > 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
