Re: [sqlite] Index not used in simple look-up-value query

Hi Pavel Re: how many rows MyDataTable and MyIntermediateTable have I had mentioned that their size is comparable to MyTable. More specifically: MyDataTable has 100K rows and MyIntermediateTable has 300K rows Their structure is as follow: CREATE TABLE [MyDataTable] ( [RecordID] INTEGER

Re: [sqlite] Index not used in simple look-up-value query

Thanks for your prompt response Dan. I missed mentioning that in my tests, I've made sure both queries lead to a single row (value) being returned in all cases. -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Dan Kennedy

Re: [sqlite] Index not used in simple look-up-value query

In the light of the work on query-plan optimizations currently being undertaken, I wonder if this issue could be looked at more closely. I can confirm the returning type doesn't affect the performance I'm seeing from the simple query. For example, returning an INT instead: SELECT ElementID

Re: [sqlite] Index not used in simple look-up-value query

Thanks Dan for clarifying that NotExists op does a seek on the IPK column. However, I'm still confused as why the first query (simple) takes much longer (from 2 to 5 times more) than the complicated one. Some numbers: 50K runs of the simple query takes ~3 sec in total. 50K runs of the

[sqlite] Index not used in simple look-up-value query

Hello, I have a question regarding the query-optimizer. I've tested SQLite with the following situation: 1 table defined as CREATE TABLE MyTable (ElementID INTEGER CONSTRAINT ElementID_PK PRIMARY KEY AUTOINCREMENT, Label VARCHAR(255)) After filling that table with lots of records (e.g.