Re: [sqlite] Not a Bug -- works as documented: [BUG REPORT] Open blob is invalidated by the update to unrelated fields in the same row

2017-03-04 Thread Simon Slavin
On 4 Mar 2017, at 11:25pm, Yuri wrote: > What is the reason to expire the blob handle when unrelated fields are > modified? Because the BLOB has moved in the file. Because SQLite stores all of a row’s data in one continuous chunk. When you change any field it has to write the entire row of

Re: [sqlite] Not a Bug -- works as documented: [BUG REPORT] Open blob is invalidated by the update to unrelated fields in the same row

2017-03-04 Thread Yuri
On 03/04/2017 00:08, Keith Medcalf wrote: If the row that a BLOB handle points to is modified by an UPDATE, DELETE, or by ON CONFLICT side-effects then the BLOB handle is marked as "expired". This is true if any column of the row is changed, even a column other than the one the BLOB handle is

[sqlite] Not a Bug -- works as documented: [BUG REPORT] Open blob is invalidated by the update to unrelated fields in the same row

2017-03-04 Thread Keith Medcalf
Working as coded (and as documented): https://sqlite.org/c3ref/blob_open.html In particular read the paragraph that says: If the row that a BLOB handle points to is modified by an UPDATE, DELETE, or by ON CONFLICT side-effects then the BLOB handle is marked as "expired". This is true if any c