Re: [sqlite] FTS3, UPDATE of one column: why are all columns affected?

This turned out to be a bug in my code. I apologize. Yaroslav -- View this message in context: http://www.nabble.com/FTS3%2C-UPDATE-of-one-column%3A-why-are-all-columns-affected--tp20036520p20039068.html Sent from the SQLite mailing list archive at Nabble.com.

[sqlite] FTS3, UPDATE of one column: why are all columns affected?

Hi All, I am using an FTS3 virtual table with multiple columns. This works very well, until I try to do an UPDATE on _one_ of the columns in the vtable. In that case, the other columns are cleared. After looking into the FTS3 code, I discovered that the columns in the original SQL statement are

[sqlite] Large blobs - slow UPDATEs on non-blob columns

Hi all, For testing purposes, I created a single row with a large blob (hundreds of megs) in my database. There is also an integer column. When I do an update on the integer, the query is very slow, and there's a lot of disk activity. The bigger the blob, the slower the query (a rule of thumb -

[sqlite] FTS3: (1) cloning index rows? (2) not storing original text?

Dear All, After some searching I still could not find the answers to the following questions. Any answers or pointers would be greatly appreciated. (1) In my FTS-enabled database, I want to clone some document, stored in a binary format. (Which means copying the same contents to a new row with