Re: [sqlite] Indexing virtual tables

2008-05-19 Thread Aladdin Lampé
Nobody? Did I make myself clear or do you need more (or maybe less!) explanations? Thanks, Aladdin > From: [EMAIL PROTECTED] > To: sqlite-users@sqlite.org > Date: Sat, 17 May 2008 16:41:49 +0200 > Subject: [sqlite] Indexing virtual tables > > > Hi! Here is what I'm st

[sqlite] Indexing virtual tables

2008-05-17 Thread Aladdin Lampé
timal. What is the best strategy to achieve optimal speed and needed storage? Am I missing a trivial point? Thank you for any help on that! Aladdin > Date: Mon, 12 May 2008 15:37:22 -0700 > From: [EMAIL PROTECTED] > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Indexing virtual tables

Re: [sqlite] Indexing virtual tables

2008-05-12 Thread Scott Hess
I'm not quite clear on your question - why wouldn't you just create any indices you need within the virtual-table implementation itself? Sort of like how fts uses SQLite tables to implement data-storage for the full-text index. -scott On Mon, May 5, 2008 at 10:13 AM, Aladdin Lampé <[EMAIL

[sqlite] Indexing virtual tables

2008-05-05 Thread Aladdin Lampé
Just thinking again about indexing strategies on virtual tables, I'm wondering why virtual tables could not be indexed using the "normal" SQLite command "INDEX". Indeed, I just expected that the data inside the column of the virtual table could be sequentially scanned (using the "xColumn"