Re: [sqlite] FTS index size

2008-07-24 Thread Jiri Hajek
> So, indeed, there's room for improvement! Thanks for looking into it, I'm interested in your results. That said, I still believe that the best way would be to make the current FTS implementation independent of the VIRTUAL TABLE structure, but be able to accept more general structures, namely

Re: [sqlite] FTS index size

2008-07-23 Thread Scott Hess
OK! This gives me something I can sink my teeth into! I hacked together a TCL script which takes info about 100 albums (snagged from a list on the Internet), makes up 10 song titles each, makes up a path in the obvious way, and stuffs them into a table. Then it times SELECT COUNT(*). Three

Re: [sqlite] FTS index size

2008-07-23 Thread Jiri Hajek
> Again, you've given a relatively broad description of what you're > trying to do. I could make up a bunch of stuff and answer my own > question, but you'd probably rather than I considered the problem > _you_ are having. Ok, I'll try to be as specific as possible. The main table I have is (the

Re: [sqlite] FTS index size

2008-07-22 Thread Scott Hess
Again, you've given a relatively broad description of what you're trying to do. I could make up a bunch of stuff and answer my own question, but you'd probably rather than I considered the problem _you_ are having. It sounds like you've actually committed code to do this - post the SQL CREATE

Re: [sqlite] FTS index size

2008-07-22 Thread Jiri Hajek
> It's hard to say - you might want to describe your tables and the join > by simply including the SQL itself, rather than a loose description of > it. It may be that there's a simple change which will clear things > up. Ok, what exactly I mean is a table containing tracks in an audio library,

Re: [sqlite] FTS index size

2008-07-21 Thread Scott Hess
On Fri, Jul 18, 2008 at 12:54 AM, Jiri Hajek <[EMAIL PROTECTED]> wrote: > from what I have read about FTS3, it stores the original data as well as the > index needed for fast full-text access. Therefore, in several posts here it > was recommended to use two tables joined one-to-one in case it's

[sqlite] FTS index size

2008-07-18 Thread Jiri Hajek
Hello, from what I have read about FTS3, it stores the original data as well as the index needed for fast full-text access. Therefore, in several posts here it was recommended to use two tables joined one-to-one in case it's needed to store both text data and some other, possibly numeric data.