On Sat, 30 Jan 2016 19:07:21 +0000 Simon Slavin <slavins at bigfraud.org> wrote:
> > On 30 Jan 2016, at 6:56pm, Yannick Duch?ne <yannick_duchene at yahoo.fr> > wrote: > > > > That's strange, or may be it's SQLiteBrowser specific (I'm using it to test > > queries and get timings). > > Oh, you're not using your own code. > > Download the SQLite command line tool and try the same queries. The shell > tool does no caching or optimisation of its own, it just calls the SQLite API > directly. Ouch, using `.timer ON` (after a quick web search), I get 90ms instead of 200 or 120, and indeed, there is no more difference whether or not I did an `EXPLAIN` before. Thanks. I was not suspecting there were big things in the background with SQLiteBrowser. I will always use the command?line version for timings, since now. -- Yannick Duch?ne
