No problem. In fact, I had to consult the docs again to be sure! I've sorted through these several times myself.
They are quite good, though I have to admit that I'm constantly having to consult them to remember how the locking works. I do agree that a BEGIN SHARED would be nice for cases where you'd like consistent reads across multiple statements without using a BEGIN IMMEDIATE and locking other threads doing the same out. Pat -----Original Message----- From: A. Pagaltzis [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 07, 2006 7:01 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Problems with multiple threads? * Pat Wibbeler <[EMAIL PROTECTED]> [2006-06-07 22:55]: > It's entirely possible I'm reading these docs incorrectly, but > this strategy has worked quite well for me. No, I don't see any error in your reading. My apologies; I should have consulted the docs instead of going by mailing list posts. It's interesting that there's no way to force a SHARED lock to be obtained immediately. The available mechanisms allow serialising write operations with respect to each other, but not forcing a well-defined sequence of read operations relative to write operations. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
