Lines Matching refs:xUnlock
1073 ** argument to calls it makes to the xLock() and xUnlock() methods
1149 ** The integer values to xLock() and xUnlock() are one of
1157 ** xLock() increases the lock. xUnlock() decreases the lock.
1225 int (*xUnlock)(sqlite3_file*, int);
13791 return id->pMethods->xUnlock(id, lockType);
26911 UNLOCK, /* xUnlock */ \
26939 unixUnlock, /* xUnlock method */
26948 nolockUnlock, /* xUnlock method */
26957 dotlockUnlock, /* xUnlock method */
26968 flockUnlock, /* xUnlock method */
26980 semUnlock, /* xUnlock method */
26992 afpUnlock, /* xUnlock method */
27017 proxyUnlock, /* xUnlock method */
27030 nfsUnlock, /* xUnlock method */
28832 conchFile->pMethod->xUnlock((sqlite3_file*)conchFile, SHARED_LOCK);
28890 conchFile->pMethod->xUnlock((sqlite3_file*)conchFile, NO_LOCK);
28914 rc = conchFile->pMethod->xUnlock((sqlite3_file*)conchFile, NO_LOCK);
29263 rc = proxy->pMethod->xUnlock((sqlite3_file*)proxy, eFileLock);
29284 rc = lockProxy->pMethod->xUnlock((sqlite3_file*)lockProxy, NO_LOCK);
31496 winUnlock, /* xUnlock */
35177 ** If the VFS xLock() or xUnlock() returns an error other than SQLITE_BUSY
35186 ** This is usually safe. If an xUnlock fails or appears to fail, there may
35193 ** transition, by the same pager or any other). If the call to xUnlock()
35201 ** doesn't know it because of a previous error in xUnlock). If this happens
35206 ** To work around this, if a call to xUnlock() fails when unlocking the
35857 ** or SHARED_LOCK. Regardless of whether or not the call to xUnlock()
67147 0, /* xUnlock */
67431 0, /* xUnlock */
