It would be very nice to have a way to explicitly control index use.
I'm going to test my theory this weekend but I think if the index is
not cached and the data large then the group by is faster without the
index. If this is the case I have a real issue. I need the index for
other queries and can't afford to drop it for the aggregations. I just
want to tell the query planner to not use any index.
If there is no way to do this with the current parser could we have an
extension to select? Maybe something like:
select with no index ....
select with index index1,index2 ....
Thoughts?
On Sep 20, 2008, at 10:33 AM, "Jay A. Kreibich" <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 19, 2008 at 10:47:33PM -0400, Russ Leighton scratched on
> the wall:
>
>> What about the null values for the aggregation keys when I put a '+'
>> to disable the index? Is that 'as designed'?
>
> The "+" operator gets rid of type-affinities, and that can lead to
> unexpected results. I'm not sure if one would consider these
> specific results "as designed" or not, but it is known that "+" is
> not totally without side effects:
>
> http://www.sqlite.org/cvstrac/tktview?tn=3279
>
>
> -j
>
>
> --
> Jay A. Kreibich < J A Y @ K R E I B I.C H >
>
> "Our opponent is an alien starship packed with atomic bombs. We have
> a protractor." "I'll go home and see if I can scrounge up a ruler
> and a piece of string." --from Anathem by Neal Stephenson
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
