That's not exactly correct. On modern systems, unless you exhaust memory you'll never hit the journal (in which case you'd need a journal- but read on). What you really want is to run the database without syncing.
You _can_ comment this code out in os.c- but I wouldn't recommend it. The time is so minimal that you're not likely to gain much. You can find out exactly how much you'll gain by testing against a ramdisk- AFAIK, modern systems don't do anything special when fsync() occurs on a file in a ramdisk, although I suppose that strictly isn't very portable... On Mon, 2003-10-27 at 02:16, v t wrote: > I am trying to use sqlite in a context where I will be using it to > store some configuration about a system. I want to try to minimize the > disk access. Since journalling uses a file on the disk, I wanted to > turn it off. I am not worried about rolling back the database to a > known state in case of some failure. > > vt > > "Mrs. Brisby" <[EMAIL PROTECTED]> wrote: > On Thu, 2003-10-23 at 19:46, v t wrote: > > Hi, > > > > How do I turn journalling OFF? > > Why do you want to? What exactly are you trying to accomplish? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ______________________________________________________________________ > Do you Yahoo!? > Exclusive Video Premiere - Britney Spears --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
