On Jan 20, 2006, at 8:25 AM, Will Leshner wrote:
Thanks for this information. It sounds like a reasonable precaution
might be not to make "too many" changes to a database in one
transaction. But I guess knowing how many changes is too many would
be a pretty hard thing to figure out.
On Jan 20, 2006, at 8:07 AM, [EMAIL PROTECTED] wrote:
Deleting a hot journal after a power loss or OS crash is more
likely to result in severe database corruption, but database
corruption is possible from deleting a hot journal after an
ordinary program crash.
Thanks for this information.
Will Leshner <[EMAIL PROTECTED]> wrote:
> On Jan 20, 2006, at 7:41 AM, [EMAIL PROTECTED] wrote:
>
> > The database might be completely unusable. It depends on
> > which writes completed and which had not at the time of the
> > crash.
>
> Am I right in thinking that that would be more likely to
On Jan 20, 2006, at 7:41 AM, [EMAIL PROTECTED] wrote:
The database might be completely unusable. It depends on
which writes completed and which had not at the time of the
crash.
Am I right in thinking that that would be more likely to happen in,
say, a hardware failure, and less likely to
Will Leshner <[EMAIL PROTECTED]> wrote:
> In the article about locking and concurrency on the SQLite website,
> where it talks about how to corrupt a SQLite database, it says that a
> SQLite database can be corrupted if a hot journal file is missing
> when SQLite reconnects to the database.
In the article about locking and concurrency on the SQLite website,
where it talks about how to corrupt a SQLite database, it says that a
SQLite database can be corrupted if a hot journal file is missing
when SQLite reconnects to the database. What kind of corruption are
we talking about,
6 matches
Mail list logo
