On 10/19/2018 02:30 AM, Deon Brewis wrote:
Hi,
I seem to have run into a limit where SQLITE doesn't use an index correctly if
an indexed column is over the 64th column in the table. It's a partial index
like:
CREATE INDEX idx ON
table(A, B DESC, C, D)
WHERE A > 0
Where A and B are
Okay, next question: Does the query you're testing this with obey the
requirements needed to use the partial index (see
https://sqlite.org/partialindex.html#queries_using_partial_indexes)?
On Thu, Oct 18, 2018 at 9:43 PM Deon Brewis wrote:
> Yes a non partial index beyond column 64 works as I
Yes a non partial index beyond column 64 works as I would expect.
- Deon
> On Oct 18, 2018, at 12:34 PM, Shawn Wagner wrote:
>
> Does a normal non-partial index make a difference in the query plan?
>
>> On Thu, Oct 18, 2018, 12:30 PM Deon Brewis wrote:
>>
>> Hi,
>>
>> I seem to have run
Does a normal non-partial index make a difference in the query plan?
On Thu, Oct 18, 2018, 12:30 PM Deon Brewis wrote:
> Hi,
>
> I seem to have run into a limit where SQLITE doesn't use an index
> correctly if an indexed column is over the 64th column in the table. It's a
> partial index like:
Hi,
I seem to have run into a limit where SQLITE doesn't use an index correctly if
an indexed column is over the 64th column in the table. It's a partial index
like:
CREATE INDEX idx ON
table(A, B DESC, C, D)
WHERE A > 0
Where A and B are columns 70 and 72 on 'table'.
I know about the
5 matches
Mail list logo