[sqlite] Performance of sparse sqlite tables

2012-11-04 Thread Dominguez Bonini, David
Hi, I have an application where a table is filled with elements whose primary key is specified at insertion, and is actually a combination of several independent IDs. Example: ItemID = (id0 32) + (id1 16) + (id2). The range covered by each ID guarantees that their sum will never exceed the

Re: [sqlite] Performance of sparse sqlite tables

2012-11-04 Thread Pavel Ivanov
I'd say generally speaking your way of storing data has no significant downsides. There's just one but: if each row in your table stores pretty significant amount of data (blobs, long text fields or just lots of different fields) you'd better not make your ItemID INTEGER PRIMARY KEY. Because

Re: [sqlite] Performance of sparse sqlite tables

2012-11-04 Thread Simon Slavin
On 4 Nov 2012, at 5:26pm, Dominguez Bonini, David david.doming...@ikusi.com wrote: I have an application where a table is filled with elements whose primary key is specified at insertion, and is actually a combination of several independent IDs. Example: ItemID = (id0 32) + (id1 16) +