Yes, fixed in pre-release snapshot 201610041220.
Thank you.
> On 10/5/16, Richard Hipp wrote:
> > On 10/5/16, Clemens Ladisch wrote:
> >> stop
> >>
> >> This looks like a bug.
> >>
> >
> > I think it might be fixed on trunk. I was just trying to bisect...
>
> I think this
On 10/5/16, Richard Hipp wrote:
> On 10/5/16, Clemens Ladisch wrote:
>> stop
>>
>> This looks like a bug.
>>
>
> I think it might be fixed on trunk. I was just trying to bisect...
I think this may be a repeat of the problem described by ticket
On 10/5/16, Clemens Ladisch wrote:
> stop
>
> This looks like a bug.
>
I think it might be fixed on trunk. I was just trying to bisect...
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
> Paul wrote:
> > I've traced this issue down to the simplest test case:
> >
> > CREATE TABLE IF NOT EXISTS foo
> > (
> > id INTEGER,
> > baz INTEGER,
> > PRIMARY KEY(id)
> > );
> >
> > CREATE INDEX IF NOT EXISTS baz_foo_idx ON foo(baz, id);
> >
> > CREATE TABLE IF NOT EXISTS bar
> > (
> >
Paul wrote:
> I've traced this issue down to the simplest test case:
>
> CREATE TABLE IF NOT EXISTS foo
> (
> id INTEGER,
> baz INTEGER,
> PRIMARY KEY(id)
> );
>
> CREATE INDEX IF NOT EXISTS baz_foo_idx ON foo(baz, id);
>
> CREATE TABLE IF NOT EXISTS bar
> (
> foo INTEGER,
> PRIMARY
To add to that, EXPLAIN QUERY PLAN shows that covering index will be used:
sqlite> EXPLAIN QUERY PLAN SELECT id FROM foo WHERE baz = 1 AND id IN
(SELECT foo FROM bar) LIMIT 1;
selectidorder fromdetail
6 matches
Mail list logo