Isaac Goldberg wrote:
> I'm seeing that EXPLAIN QUERY PLAN returns SEARCH instead of SCAN when
> using min() or max(). For example:
>
> sqlite> create table t(a int, b int);
> sqlite> explain query plan select min(b) from t;
> 0|0|0|SEARCH TABLE t
>
> Why is this a SEARCH instead of a SCAN?
On 2 Sep 2015, at 2:00pm, Simon Slavin wrote:
> Because there's no convenient index.
Whoops. Sorry. Ignore me. Pay attention to Clemens.
Simon.
On 1 Sep 2015, at 7:40am, Isaac Goldberg wrote:
> I'm seeing that EXPLAIN QUERY PLAN returns SEARCH instead of SCAN when
> using min() or max(). For example:
>
> sqlite> create table t(a int, b int);
>> sqlite> explain query plan select min(b) from t;
>> 0|0|0|SEARCH TABLE t
>
> Why is this a
Hi all,
I'm seeing that EXPLAIN QUERY PLAN returns SEARCH instead of SCAN when
using min() or max(). For example:
sqlite> create table t(a int, b int);
> sqlite> explain query plan select min(b) from t;
> 0|0|0|SEARCH TABLE t
Why is this a SEARCH instead of a SCAN? Furthermore, is it expected
4 matches
Mail list logo