Re: [sqlite] Indexing - a test example

On Mar 7, 2011, at 1:58 PM, Richard Hipp wrote: > The beauty of SQL (not just SQLite but any SQL database engine) is that you > can focus on the semantics of your query and not worry about the > implementation - the SQL database engine will figure out the best query > algorithm for you. Ah,

Re: [sqlite] Indexing - a test example

On 7 Mar 2011, at 11:07am, J Trahair wrote: > Picking one of my tables at random (the first one, in fact): > CREATE TABLE CostItems( > RecNo INTEGER PRIMARY KEY AUTOINCREMENT, > CustomerCode TEXT, > ProjectName TEXT, > SupplierName TEXT, > WhatExactly TEXT, > CostDate TEXT > etc. > ); > > I

Re: [sqlite] Indexing - a test example

On Mon, Mar 7, 2011 at 6:07 AM, J Trahair wrote: > > Questions: > 1. Do the differing orders of fields in the 2 SELECTs require me to use 2 > indexes as above? > You'll need two indices if you want your two SELECTs to run efficiently. And the two indices you

Re: [sqlite] Indexing - a test example

: Monday, March 07, 2011 5:07 AM To: sqlite-users@sqlite.org Subject: EXT :[sqlite] Indexing - a test example I have looked at some information on indexing, and watched a 44 minute presentation by Dr Richard Hipp. I looked at the project I am converting to SQLite, and I have identited all the SELECTs

[sqlite] Indexing - a test example

I have looked at some information on indexing, and watched a 44 minute presentation by Dr Richard Hipp. I looked at the project I am converting to SQLite, and I have identited all the SELECTs for all the tables. They do not fall easily into the 'SELECT x, y, z FROM Table1 WHERE w = 5 AND x = 6