Re: [sqlite] database disk image is malformed

It was a typo. I was setting fullsync when the correct pragma name is fullfsync. On Fri, Sep 26, 2008 at 9:50 AM, Jeffrey Rennie (レニー） <[EMAIL PROTECTED]>wrote: > > 2008/9/25 D. Richard Hipp <[EMAIL PROTECTED]> > >> >> You are confusing the statement

Re: [sqlite] database disk image is malformed

2008/9/25 D. Richard Hipp <[EMAIL PROTECTED]> > > You are confusing the statement journal with the rollback journal. > The statement journal has nothing to do with database recovery - that > is the task of the rollback journal. So the statement journal can be > deleted at will without damaging

Re: [sqlite] database disk image is malformed

, then your DB will be corrupt. It also makes it much harder to debug issues on clients' machines, because you can no longer just say "send me all the files in the folder yadayada..." 2008/9/25 Jeffrey Rennie (レニー） <[EMAIL PROTECTED]> > Small correction: I'm using sqlite version 3.5.9

Re: [sqlite] database disk image is malformed

Small correction: I'm using sqlite version 3.5.9. On Thu, Sep 25, 2008 at 1:08 PM, Jeffrey Rennie (レニー） <[EMAIL PROTECTED]>wrote: > I'm seeing this happen on Mac OS X, after the user hard reboots his > computer. I'm compiling with -DHAVE_FULLFSYNC=1 and running with PRAGMA >

Re: [sqlite] Performance on HP

Are there any other processes or threads trying to open your db file while you run your tests? On Mon, Jun 23, 2008 at 9:48 AM, Andrea Connell <[EMAIL PROTECTED]> wrote: > > > >> The program took 47 seconds to run, but the results only account for > >> .39 seconds > > > > Most likely all the