On 7/12/05, Alex Chudnovsky <[EMAIL PROTECTED]> wrote: > Gé Weijers wrote: > > > No, sqlite3 uses database-level locking, either one process can > > write, or many processes can read. Good enough for most embedded uses. > > Any plans for internal queueing of queries waiting for their turn to > write rather than just return database locked?
sqlite 3.x does have the busy timeout, which sounds like a spin lock. maybe it does queue things? > I did implement similar mechanism in C# wrapper on top of ADO.NET > wrapper, but it seems to me that having this queuing inside sqlite > itself would be much more efficient and beneficial for all. > > regards > > Alex > -- Cory Nelson http://www.int64.org
