Gerry, We are using a flash filesystem.
The changes are made to a separate area of the flash, when the file is flushed then the descriptor blocks are updated to point to the new block of flash. If the power is lost before the file is flushed then the descriptor is not updated and therefore the file is still in the same state as it was prior to any of the writes. The file is only changed when it is flushed or closed. We believe based on this that we do not need to journal the database file. Indeed we had no problems with 3.2.1 albeit as we were benfiting from flushes that where not supposed to be happening. Regards Mark > -----Original Message----- > From: Gerry Snyder [mailto:[EMAIL PROTECTED] > Sent: 01 November 2005 14:58 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] disabling journalling of the database - side > affects? > > > Allan, Mark wrote: > > > > > > .... We do believe however that journaling the database for us > > is of no benefit as our filing system is 100% fail safe and will > > return to the last flushed state of the file on power loss. > > Mark, > > I am probably in over my head, as usual, but how do you > recover if power > goes down during the write process for an update; that is, if > some of an > update is written to the file and some of it is not? > > I guess it must be a journalling fs. Double journalling would > indeed be > inefficient. > > Maybe it might be easier to turn off the fs journalling than > that in sqlite? > > Gerry > > -- > ------------------ > Gerry Snyder > American Iris Society Director, Symposium Chair > in warm, winterless Los Angeles -- USDA zone 9b, Sunset 18-19 > > > DISCLAIMER: This information and any attachments contained in this email message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, forwarding, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email, and delete the original message immediately.
