ed, either because of a typo while
>> making it or some other reason.
>>
>>
>> -Original Message-
>> From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org]
>> On Behalf Of Wout Mertens
>> Sent: Wednesday, August 09, 2017 10:51 AM
>> To: SQ
o:sqlite-users-boun...@mailinglists.sqlite.org]
> On Behalf Of Wout Mertens
> Sent: Wednesday, August 09, 2017 10:51 AM
> To: SQLite mailing list
> Subject: [sqlite] Using multi-value indexes for subset queries
>
> Hi all,
>
> in experimenting with indexes I found that
nglists.sqlite.org] On
Behalf Of Wout Mertens
Sent: Wednesday, August 09, 2017 10:51 AM
To: SQLite mailing list
Subject: [sqlite] Using multi-value indexes for subset queries
Hi all,
in experimenting with indexes I found that if you create an index on (a, b)
and then SELECT * FROM data WHER
the rowid.
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Wout Mertens
Gesendet: Mittwoch, 09. August 2017 16:51
An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org>
Betreff: [sqlite] Using multi-value indexes for subset
On 8/9/2017 10:50 AM, Wout Mertens wrote:
in experimenting with indexes I found that if you create an index on (a, b)
and then SELECT * FROM data WHERE a = 1 AND B = 2, it will use the index,
great.
However, if you write SELECT * FROM data WHERE a = 1, it won't use the
index.
Are you sure?
Hi all,
in experimenting with indexes I found that if you create an index on (a, b)
and then SELECT * FROM data WHERE a = 1 AND B = 2, it will use the index,
great.
However, if you write SELECT * FROM data WHERE a = 1, it won't use the
index. If you write SELECT * FROM data WHERE a = 1 AND B !=
6 matches
Mail list logo
