Re: [sqlite] Multiple Match statements per query

. If cloning isn't an option, I can create a statement pool; I would just prefer the simpler option. Thanks dw _ From: Igor Tandetnik [mailto:itandet...@mvps.org] To: sqlite-users@sqlite.org Sent: Tue, 19 Apr 2011 17:08:09 -0600 Subject: Re: [sqlite] Multiple Match statements per query On 4/19

Re: [sqlite] Multiple Match statements per query

On 4/19/2011 6:57 PM, Dave White wrote: > So, if I could prepare the statement once, then clone it every time I > need to use it, I may see a 4 fold speed increase when calling this > operation frequently. Why can't you just reuse the same statement every time? Are you aware of sqlite3_reset ?

Re: [sqlite] Multiple Match statements per query

I'll look into GLOB. For the statement cloning, I'm looking for something a little different. I already have the connection and query string, and duplicating bindings is not necessary. It's the sqlite3_stmt that I want. right after sqlite3_prepare_v2 has been called. I was doing some

Re: [sqlite] Multiple Match statements per query

On Tue, 19 Apr 2011 14:18:05 -0600 Dave White wrote: > For example, this works: > SELECT T01_fts.docid FROM T01_fts JOIN T01 ON T01_fts.docid = T01.rowid > WHERE T01.hasPic = 0 AND T01_fts.words MATCH 'SBNTKN*' > > These do not: > SELECT T01_fts.docid

[sqlite] Multiple Match statements per query

It appears that I cannot use MATCH more than once per query. It also looks like I can't use it if prefaced with OR or NOT. For example, this works: SELECT T01_fts.docid FROM T01_fts JOIN T01 ON T01_fts.docid = T01.rowid WHERE T01.hasPic = 0 AND T01_fts.words MATCH 'SBNTKN*' These do