On 4/19/2015 7:08 PM, Richard Hipp wrote:
>> Since power loss occurs relatively
>> frequently, do you recommend synchronous=1 (Normal) or 2 (Full)?
> Either will be fine.
>> Can a power failure during
>> a COMMIT to a TEMPORARY table in memory, with synchronous=0, result in
>> corruption
> No.
On 19 Apr 2015, at 9:45pm, Joe Pasquariello wrote:
> Some users of my application have their servers in remote locations that lose
> power.
Richard has answered your questions, but you can help further by telling us
these:
Are the database files held on the same computer as the one doing
On 4/19/15, Joe Pasquariello wrote:
> Since power loss occurs relatively
> frequently, do you recommend synchronous=1 (Normal) or 2 (Full)?
Either will be fine.
>
> Can a power failure during
> a COMMIT to a TEMPORARY table in memory, with synchronous=0, result in
> corruption
No.
--
D.
On 4/19/2015 2:02 PM, Richard Hipp wrote:
> On 4/19/15, Joe Pasquariello wrote:
>> Some users of my application have their servers in remote locations that
>> lose power. They have UPS backup, but the battery runs down and the
>> computers will suddenly stop. When power returns and the
On 4/19/15, Joe Pasquariello wrote:
> Some users of my application have their servers in remote locations that
> lose power. They have UPS backup, but the battery runs down and the
> computers will suddenly stop. When power returns and the application
> starts, the SQLITE database is sometimes
Some users of my application have their servers in remote locations that
lose power. They have UPS backup, but the battery runs down and the
computers will suddenly stop. When power returns and the application
starts, the SQLITE database is sometimes corrupt. The vast majority of
writes to the
6 matches
Mail list logo
