On Sep 26, 2008, at 2:29 PM, Kees Nuyt wrote:
> On Fri, 26 Sep 2008 12:54:36 -0400, Russell wrote:
>
>> I need a 2 key index for some queries and also want to aggregate on
>> these 2 columns. I need this index BUT I have many large sqlite dbs I
>> iterate over and they won't fit in the
DRH,
I think most people like the nature of your proposal to allow control
of indexes in queries. There were a number
of suggestions on variations of the syntax. Have you made a final
decision on what the syntax will be?
Thx
Russ
___
sqlite-users
e
> rules based (rather than cost based) optimizer. but nobody
> (including sqlite) does that anymore for good reasons.
>
>
> On Sep 21, 2008, at 12:59 PM, Stephen Woodbridge wrote:
>
>> D. Richard Hipp wrote:
>>> On Sep 21, 2008, at 8:51 AM, Russ Leighton wrote:
>
On Sep 19, 2008, at 6:30 PM, D. Richard Hipp wrote:
>
> On Sep 19, 2008, at 5:47 PM, Russ Leighton wrote:
>
>>
>> Observation 1: Group by (in my case) is faster w/out using the index
>> than with using the index by 10X
>>
>> In my app I have a table-
>&
Observation 1: Group by (in my case) is faster w/out using the index
than with using the index by 10X
In my app I have a table-
create table foo(k1integer ,k2 integer,k3 integer,...);
create index foo_idx on foo(k1,k2,k3);
when I do-
select k1,k2,sum() as s,count(1) as c from foo
5 matches
Mail list logo
