>
>Using "PRAGMA journal_mode=truncate" made no difference, the journal
>reappeared with file size > 0.
>
>But "PRAGMA journal_mode=persist" fixes the problem, the database is no
>longer rolled back after a power cut.
>
FYI,
The problem turned out to be a bug in the UBIFS backport we are using.
>> I'm using SQLite 3.6.20 on an ARM Linux device which uses the UBIFS
>> filesystem (on OneNAND flash).
>>
>> When I perform a database update, and cut the power a few seconds
>> later, the
>> changes are rolled back
>> when the device restarts. This is because after the restart the
>> journal
On Nov 26, 2009, at 12:01 AM, Ronny Dierckx wrote:
> Dear list,
>
> I'm using SQLite 3.6.20 on an ARM Linux device which uses the UBIFS
> filesystem (on OneNAND flash).
>
> When I perform a database update, and cut the power a few seconds
> later, the
> changes are rolled back
> when the device
Dear list,
I'm using SQLite 3.6.20 on an ARM Linux device which uses the UBIFS
filesystem (on OneNAND flash).
When I perform a database update, and cut the power a few seconds later, the
changes are rolled back
when the device restarts. This is because after the restart the journal file
has re-ap
4 matches
Mail list logo