Re: [sqlite] Fine tuning table indexes

2014-02-02 Thread James K. Lowden
On Sat, 1 Feb 2014 11:21:45 -0500 Stephen Chrzanowski pontia...@gmail.com wrote: Would be interesting to see when and where that single index comes into play when multiple indexes are defined. create table T (t int primary key, a int , b int); create index Ta on T(a); create index Tb on T(b);

Re: [sqlite] Fine tuning table indexes

2014-02-02 Thread Keith Medcalf
You mean, of course, doing a re-write as: select * from T where rowid in (select rowid from T where a 1 UNION select rowid from T where b 1) which uses four indices. one on a, one

Re: [sqlite] Fine tuning table indexes

2014-02-02 Thread Petite Abeille
On Feb 2, 2014, at 5:55 PM, Keith Medcalf kmedc...@dessus.com wrote: Nevertheless, each traversal operation is only using one index at a time. One word: bitmap. As in bitmap index: http://www.oracle.com/technetwork/articles/sharma-indexes-093638.html http://en.wikipedia.org/wiki/Bitmap_index

Re: [sqlite] ORDER BY issue v3.8.2 amalgamtion

2014-02-02 Thread Labar, Ken
Hello Simon, Below is the query, and the schema I’m trying to debug. FYI: I’m signed up for the daily digest, so please CC kla...@hach.commailto:kla...@hach.com on replies for a faster response. CREATE TABLE userParameter ( hepi_parameter_id INT NOT NULL

Re: [sqlite] Fine tuning table indexes

2014-02-02 Thread Dan Kennedy
On 02/02/2014 11:16 PM, James K. Lowden wrote: On Sat, 1 Feb 2014 11:21:45 -0500 Stephen Chrzanowski pontia...@gmail.com wrote: Would be interesting to see when and where that single index comes into play when multiple indexes are defined. create table T (t int primary key, a int , b int);