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. 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.
I'm mainly thinking about what happens if a customer doesn't realize what the journal file is and throws it away. Probably the best way to avoid that problem is to be sure to tell the customer not to do that :)
