/ View Ticket
Ticket UUID: f46ca03b55ae0ecab698c623031abbb550e1f405
Title: The order of two operations in asyncLock()
Status: Closed Type: Code_Defect
Severity: Important Priority: Immediate
Subsystem: Extensions Resolution: Overcome_By_Events
Last Modified: 2012-11-29 14:27:13
Version Found In:
In file sqlite3async.c, the function asyncLock(), line 888
Why set the lock.eLock and lock.eAsyncLock before getFileLock() is called?
If getFileLock() failed, why not reset the eLock and eAsyncLock?
It looks like if the first asyncLock() called failed, the second will succeed without any check?
User Comments:
drh added on 2012-11-29 14:27:13: (text/x-fossil-wiki)
We no longer support the async extension.  The features provided
by async is now provided in a much better way by WAL mode.