Re: [sqlite] async io and locks (CORRECTION)

(A) I was able to reply inside the thread. *confused* (B) "that the lock is acquired independent..." is incorrect and irrelevant. It should be ignored. -robert ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] async io and locks

Once again, I am forced to reply to the top-level, outside the thread b/c I am not receiving individual replies. I apologize for the inconvenience. On Jun 20, 2009, at 12:30 AM, Dan wrote: > On Jun 20, 2009, at 12:06 AM, Robert Lehr wrote: > > I finally got around to reviewing

[sqlite] (no subject)

Date: Fri, 19 Jun 2009 14:53:05 -0700 From: Robert Lehr <rl...@cadence.com> Subject: Re: [sqlite] async io and locks To: sqlite-users@sqlite.org In-Reply-To: <43c62cbb-57db-4d1b-af36-2facf239c...@gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes I hav

[sqlite] async io and locks

I finally got around to reviewing SQLite's asynchronous I/O functionality. http://sqlite.org/asyncvfs.html We actually have an C++ wrapper to uses the same concept, a background thread for I/O. The async functionality included w/ SQLite is not a

[sqlite] DDL statements in transactions

> On Wed, Jun 11, 2008 at 3:55 PM, Robert Lehr wrote: > > > Oracle does not allow DDL statements [ ... snippage ... ] > > > > PostgreSQL does allow DDL statements [ ... snippage ... ] > > > > Which behaviour is implemented in SQLite? > > > On Wed,

[sqlite] DDL statements in transactions

is rolled back and no tables, indices, etc., are created, modified, etc. Which behaviour is implemented in SQLite? -rlehr Robert Lehr ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] transaction locks w/ multiple DBs open/ATTACHed

locking sequence does SQLite execute? -rlehr Robert Lehr ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] sqlite-users Digest, Vol 6, Issue 6

ion in question can be written to that specification. Whether or not another DB SW can recover from it is uninteresting, particularly in that context. that being the case, I suspect that SQLite will return an SQLITE_IOERROR (something from the SQLITE_IOERROR*