Re: [sqlite] disk image malformed

I recently reported a similar error. After upgrading to sqlite3, I noticed that I would occassionally get the "database disk image is malformed" errors using the library code. I just closed/reopened the db, retried the query and always had success on the retry. No idea why - D. Richard Hipp

Re: [sqlite] transient SQLITE_CORRUPT

From everything I've read, I would have thought this was the case. But in practice I have been seeing transient SQLITE_CORRUPT errors. I tried "pragma integrity_check" and it said ok. I'm running my app on an embedded linux machine. The db is in ramdisk and I'm using TEMP_STORE=3, so

[sqlite] transient SQLITE_CORRUPT

As I reported earlier, after updating to sqlite 3.2.2, I started getting occasional SQLITE_CORRUPT errors. The next query always worked, so the error was only a temporary condition. I decided that if I got an error on a query, I would retry the query after closing and reopening the db. I

[sqlite] database disk image is malformed

I just recently switched from sqlite 2.8.14 to 3.2.2. Since switching, I've seen a few SQLITE_CORRUPT errors returned from sqlite_exec. However, almost all queries work - this error seems to only indicate a transient condition.After receiving the error, my process closes the connection

[sqlite] attach fails with misleading error code

Using sqlite 2.8.14, I've seen attach fail with a return value of 1 (SQLITE_ERROR) but when I check the error message, it says "database is locked". It seems like the return value of sqlite_exec should be 6 (SQLITE_LOCKED). Anyone know why this is? Thanks, Kevin

Re: [sqlite] SQLITE_BUSY returned without busy handler called

What if transactions only executed if they were able to get an EXCLUSIVE lock? Wouldn't that solve the problem you described? Granted, this would be overkill for transactions that only did SELECTs, but... --- "b.bum" <[EMAIL PROTECTED]> wrote: > > Not in a transaction. > > The purpose

Re: [sqlite] SQLITE_BUSY returned without busy handler called

b.bum" <[EMAIL PROTECTED]> wrote: > On Oct 18, 2004, at 12:01 PM, Kevin Schmeichel > wrote: > > What are some examples of circumstances when > waiting > > and retrying a lock won't help? > > Consider two processes, A and B. Lock state is in > [BRACKETS]. &

Re: [sqlite] SQLITE_BUSY returned without busy handler called

What are some examples of circumstances when waiting and retrying a lock won't help? Kevin --- "D. Richard Hipp" <[EMAIL PROTECTED]> wrote: > Kevin Schmeichel wrote: > > By examining the code, it can be seen that there > are > > many places where SQLI

[sqlite] busy handler sometimes not called

I've noticed that sometimes the busy handler doesn't get called by functions that return SQLITE_BUSY. One example is sqlite_finalize. I'm using sqlite 2.8.14. Anyone know if there's any reason for this, or is it just sloppy coding? Kevin ___

RE: [sqlite] Documentation help

http://www.sqlite.org/cvstrac/wiki?p=DateAndTimeFunctions Not sure why this is in such an obscure place - it's pretty useful stuff... Kevin --- Bob Dankert <[EMAIL PROTECTED]> wrote: > I believe if you take a look in the wiki, you will > find the date and > time functions. Otherwise, look

[sqlite] SQLITE_BUSY returned without busy handler called

By examining the code, it can be seen that there are many places where SQLITE_BUSY is returned (from an API function) without the busy handler being called. Anyone know if there is any reason for this? I would have thought that the busy handler would be called *every* time that the db is