Scott Robison wrote...
Yes, it might just need to walk through a larger data set. If nulls are
rare, there probably wouldn't be much of a difference (not in front of a
computer to check). If the column was mostly nulls, and a lot of rows, it
might be a lot faster.
Hmmm... Thanks. I have lots
On May 9, 2017 9:07 PM, "jose isaias cabrera" wrote:
Scott Robison wrote...
On Mon, May 8, 2017 at 11:40 AM, Paul van Helden
wrote:
> Hi,
>>
>> I use a lot of indexes on fields that typically contain lots of NULLs, so
>> the WHERE NOT NULL partial indexing seems very useful.
>>
>> However whe
Scott Robison wrote...
On Mon, May 8, 2017 at 11:40 AM, Paul van Helden
wrote:
Hi,
I use a lot of indexes on fields that typically contain lots of NULLs, so
the WHERE NOT NULL partial indexing seems very useful.
However when I compare the "EXPLAIN QUERY PLAN" with a partial index vs.
a
norm
On Mon, May 8, 2017 at 8:20 PM, Scott Robison
wrote:
> On Mon, May 8, 2017 at 11:40 AM, Paul van Helden
> wrote:
> > Hi,
> >
> > I use a lot of indexes on fields that typically contain lots of NULLs, so
> > the WHERE NOT NULL partial indexing seems very useful.
> >
> > However when I compare the
On Mon, May 8, 2017 at 11:40 AM, Paul van Helden wrote:
> Hi,
>
> I use a lot of indexes on fields that typically contain lots of NULLs, so
> the WHERE NOT NULL partial indexing seems very useful.
>
> However when I compare the "EXPLAIN QUERY PLAN" with a partial index vs. a
> normal index, SQLite
Hi,
I use a lot of indexes on fields that typically contain lots of NULLs, so
the WHERE NOT NULL partial indexing seems very useful.
However when I compare the "EXPLAIN QUERY PLAN" with a partial index vs. a
normal index, SQLite won't use the index to find Max(IndexedField) if it is
a partial ind
6 matches
Mail list logo