It may not be perfect, but it is impressive. Impressive and frustrating are not mutually exclusive :)
Anyway, I'm probably not a typical sqlite user. I use sqlite as a simple indexing system, where all reads are expected to hit an index and return instantly. For this project, direct control over the indexing system would be better. But when the SQL-translation works as expected, it is nice to have sql available as a tool for general reporting. Fredrik On Tue, Oct 1, 2019 at 8:05 PM Richard Hipp <d...@sqlite.org> wrote: > On 10/1/19, Fredrik Larsen <frel...@gmail.com> wrote: > > > > The declarative model of SQL is nice, but when you care about > performance, > > it quickly gets frustrating and time consuming. > > In a perfect world, the query planner would recognize your intent and > do the right thing. You would be able to write the query any way you > want, and the result would always be fast. > > Alas, SQLite's query planner is not perfect. > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
