SQLite
Ticket Change Details
Not logged in
Overview

Artifact ID: e93ae3ff2a461c5a9cdce3eef2483a4bb11f79c5
Ticket: f46ca03b55ae0ecab698c623031abbb550e1f405
The order of two operations in asyncLock()
Date: 2012-11-29 08:31:34
User: anonymous
Changes

  1. Change comment to:

    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?

  2. Change detected to "Code_Review"
  3. Change foundin to "3.7.14.1"
  4. Change private_contact to "7775aa316ff01dfe638bbf525a453db28dc737a8"
  5. Change severity to "Important"
  6. Change status to "Open"
  7. Change subsystem to "Extensions"
  8. Change title to "The order of two operations in asyncLock()"