Re: [sqlite] FTS3 performance oddity

2009-10-10 Thread Alexey Pechnikov
Hello! How about solution like to select rowid from my_fts_table where my_fts_table match @query2 and rowid in (select rowid from my_fts_table where my_fts_table match @query1) limit 21 I don't know about performance of this but rowid index may be used success. Best regards, Alexey Pechnik

Re: [sqlite] FTS3 performance oddity

2009-10-09 Thread Scott Hess
Your analysis is correct. One way this is often fixed in full-text-search systems is to keep index stats so that the more specific bits of the query can come first. In this case, "nicky" AND "nigel" gives you a small enough result set that it would be more efficient to scan the matched documents

[sqlite] FTS3 performance oddity

2009-10-09 Thread Mark
I have a database containing a single table, with FTS3: create virtual table my_fts_table using fts3 ( last_name text not null, first_name text not null, middle_name text not null, identifiers text not null, address_1 text not null, city