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
wrote:
On Tue, 19 Apr 2011 14:18:05 -0600
Dave White dwh...@companioncorp.com 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 FROM
I can't get WAL checkpoints to work, automatically or forced. The WAL file
seems to grow forever until the database is shutdown. I have tried:
sqlite3_wal_checkpoint()
and
PRAGMA wal_checkpoint (with all different options)
My 84MB data file is now paired with a
We are considering using rowids as a unique and stable ID for all records. I
know that in order to do this, we need to prevent recycling by using primary
key autoincrement.
The concern is that over time, as records are added and removed, there will
appear large gaps in the rowids of a table.
We are currently migrating from a different type of database and I'm having a
little trouble with performance.
Our old selection method queries indexes and returns the equivalent of a list
of rowids that we then use to access records as needed. I've managed to mimic
this behavior but it is
