I definately have a problem when I disable journalling on version 3.2.7 of SQLite. I dont see the same problem with 3.2.1 of SQlite. I disable the journalling of the database file as described in my earlier email. With version 3.2.7 this causes SQlite to not sync the database file after some updates (i.e. sqlite3OsSync() is not called). This means that if power is lost before the database file is explicitly closed we are losing those changes.
I realise that the purpose of the journal file is to allow the database to return to its last valid state if power is lost during an update, however we believe that in our system we will not need this as our flash filing system is 100% power safe. i.e. it will return to the last flushed state of the file on power loss. So we believe that not only is the journalling of the database time consuming it is also unnecessary for us, which is a little annoying. If this is a bug in 3.2.7 of SQlite can it be fixed? If I cannot disable the journal file safely by the mechanism described in my previous email then can somebody please indicate how I can disable journalling of the database safely. Regards Mark > -----Original Message----- > From: Allan, Mark [mailto:[EMAIL PROTECTED] > Sent: 01 November 2005 09:52 > To: sqlite-users@sqlite.org > Subject: [sqlite] disabling journalling of the database - > side affects? > > > > Can anybody tell me if I will suffer any sideaffects if I > disable the journalling of the database file with version 3.2.7? > > We have changed the SQlite code locally to omit the > journalling of the database file by supplying 1 as the value > for omitJournal to calls to the function sqlite3BtreeFactory. > We have done this as we do not want the performance overhead > of doubling the amount of writes we make as we are using an > NOR flash filing system and this is not particularly quick. > > Can anybody help me? > > Thanks > > > Mark > > > 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. > > > 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.
