Lines Matching refs:xUnlock
1066 ** argument to calls it makes to the xLock() and xUnlock() methods
1142 ** The integer values to xLock() and xUnlock() are one of
1150 ** xLock() increases the lock. xUnlock() decreases the lock.
1218 int (*xUnlock)(sqlite3_file*, int);
13784 return id->pMethods->xUnlock(id, lockType);
26904 UNLOCK, /* xUnlock */ \
26932 unixUnlock, /* xUnlock method */
26941 nolockUnlock, /* xUnlock method */
26950 dotlockUnlock, /* xUnlock method */
26961 flockUnlock, /* xUnlock method */
26973 semUnlock, /* xUnlock method */
26985 afpUnlock, /* xUnlock method */
27010 proxyUnlock, /* xUnlock method */
27023 nfsUnlock, /* xUnlock method */
28825 conchFile->pMethod->xUnlock((sqlite3_file*)conchFile, SHARED_LOCK);
28883 conchFile->pMethod->xUnlock((sqlite3_file*)conchFile, NO_LOCK);
28907 rc = conchFile->pMethod->xUnlock((sqlite3_file*)conchFile, NO_LOCK);
29256 rc = proxy->pMethod->xUnlock((sqlite3_file*)proxy, eFileLock);
29277 rc = lockProxy->pMethod->xUnlock((sqlite3_file*)lockProxy, NO_LOCK);
31489 winUnlock, /* xUnlock */
35170 ** If the VFS xLock() or xUnlock() returns an error other than SQLITE_BUSY
35179 ** This is usually safe. If an xUnlock fails or appears to fail, there may
35186 ** transition, by the same pager or any other). If the call to xUnlock()
35194 ** doesn't know it because of a previous error in xUnlock). If this happens
35199 ** To work around this, if a call to xUnlock() fails when unlocking the
35850 ** or SHARED_LOCK. Regardless of whether or not the call to xUnlock()
67140 0, /* xUnlock */
67424 0, /* xUnlock */
