Wow! Thank you, all! Just adding the index dropped the query time down into
the 3 second range.
These two versions had a similiar effects:
CREATE INDEX idx1 ON settings(rate, year, month);
CREATE INDEX idx1 ON settings(rate);
I'll experiment with this whole new world of INDEX and maybe I can get i
Actually I think you can drop the index on just rate.
On Thu, Sep 18, 2008 at 3:12 PM, John Stanton <[EMAIL PROTECTED]> wrote:
> I would get rid of your separate columns for day, month and year and use
> the Sqlite date format and use an index on it.
>
> chris wrote:
>> I'm at a loss and need some
I would get rid of your separate columns for day, month and year and use
the Sqlite date format and use an index on it.
chris wrote:
> I'm at a loss and need some guidance. My queries are taking way longer than
> I can use but I'm not sure what steps to take next.
>
> I'm using SQLite 3.6.2 on
On Thu, Sep 18, 2008 at 11:58 AM, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
>
> On Sep 18, 2008, at 12:46 PM, chris wrote:
>
> I'm at a loss and need some guidance. My queries are taking way longer
>> than I can use but I'm not sure what steps to take next.
>>
>>
>> Try this and see if it helps
Try creating an index on settings(rate)
On Thu, Sep 18, 2008 at 12:46 PM, chris <[EMAIL PROTECTED]> wrote:
> I'm at a loss and need some guidance. My queries are taking way longer than
> I can use but I'm not sure what steps to take next.
>
> I'm using SQLite 3.6.2 on a small reasonable powerful
On Sep 18, 2008, at 12:46 PM, chris wrote:
> I'm at a loss and need some guidance. My queries are taking way
> longer than I can use but I'm not sure what steps to take next.
>
> I'm using SQLite 3.6.2 on a small reasonable powerful embedded
> platform with 256M ram. I'm using Python to acc
6 matches
Mail list logo