day, February 03, 2017 3:55 AM
To: SQLite mailing list
Subject: Re: [sqlite] "DISTINCT" makes a query take 37 times as long
On Fri, Feb 3, 2017 at 12:27 AM, Kevin O'Gorman <kevinogorm...@gmail.com>
wrote:
> But the big thing is that I took a look at EXPLAIN QUERY PLAN using
iling list <sqlite-users@mailinglists.sqlite.org>
Betreff: Re: [sqlite] "DISTINCT" makes a query take 37 times as long
When I read this, it seemed like it made sense. The thing is, it does not
match up with reality.
First, the analysis of what happens when I pipe the results
On Fri, Feb 3, 2017 at 12:27 AM, Kevin O'Gorman
wrote:
> But the big thing is that I took a look at EXPLAIN QUERY PLAN using this
> ...
Maybe somebody can explain them to me, but it doesn't really matter whether
> I ever understand them. Perhaps Mr. Hipp can make use of
When I read this, it seemed like it made sense. The thing is, it does not
match up with reality.
First, the analysis of what happens when I pipe the results to 'sort'
misses the fact that the sort process executes within the 31 minutes of
that version. It would not make a dent in the time of
On 2/2/17, Hick Gunter wrote:
> DISTINCT forces the query optimizer to create an intermediate table to hold
> the results and compare each row of the non-distinct result set with an
> automatically created index. It may also affect the query plan in a way that
> chooses
DISTINCT forces the query optimizer to create an intermediate table to hold the
results and compare each row of the non-distinct result set with an
automatically created index. It may also affect the query plan in a way that
chooses inefficient indices, which is more likely if you have not run
On Wed, Feb 1, 2017 at 6:35 PM, Richard Hipp wrote:
> On 2/1/17, Kevin O'Gorman wrote:
> > I have a database of positions and moves in a strategic game, and I'm
> > searching for unsolved positions that have been connected to an immediate
> > ancestor.
On 2/1/17, Kevin O'Gorman wrote:
> I have a database of positions and moves in a strategic game, and I'm
> searching for unsolved positions that have been connected to an immediate
> ancestor. I'm using Python 3.5.2, and the code looks like
Please provide us with the
8 matches
Mail list logo