On 20 Jul 2016 at 20:29, Richard Hipp wrote:
> On 7/19/16, Doug Nebeker wrote:
>> there is only one process using the database file (though multiple
>> threads, but they each have their own database handle).
>
> That threading mode
On 7/19/16, Doug Nebeker wrote:
> there is only one process using the database file (though multiple
> threads, but they each have their own database handle).
That threading mode (https://www.sqlite.org/threadsafe.html) are you
using? Are you sure that you are using the
On 19 Jul 2016, at 5:43pm, Doug Nebeker wrote:
> Would it be possible for a file scanning process (anti-virus, backup, etc) to
> grab hold of a database file at just the right moment, momentarily blocking a
> write or delete, and causing corruption?
It might prevent the
Been using SQLite for a long time and a huge fan. We occasionally see database
corruption on a local NTFS Windows drive and I've been trying to figure it out.
I finally have some logs from the SQLITE_CONFIG_LOG callback that may be of
help:
(11) database corruption at line 78267 of
4 matches
Mail list logo