Lines Matching defs:xUnlock
693 ** argument to calls it makes to the xLock() and xUnlock() methods
770 ** The integer values to xLock() and xUnlock() are one of
778 ** xLock() increases the lock. xUnlock() decreases the lock.
848 int (*xUnlock)(sqlite3_file*, int);
15827 return id->pMethods->xUnlock(id, lockType);
29234 UNLOCK, /* xUnlock */ \
29264 unixUnlock, /* xUnlock method */
29273 nolockUnlock, /* xUnlock method */
29282 dotlockUnlock, /* xUnlock method */
29293 flockUnlock, /* xUnlock method */
29305 semUnlock, /* xUnlock method */
29317 afpUnlock, /* xUnlock method */
29342 proxyUnlock, /* xUnlock method */
29355 nfsUnlock, /* xUnlock method */
31195 conchFile->pMethod->xUnlock((sqlite3_file*)conchFile, SHARED_LOCK);
31246 conchFile->pMethod->xUnlock((sqlite3_file*)conchFile, NO_LOCK);
31270 rc = conchFile->pMethod->xUnlock((sqlite3_file*)conchFile, NO_LOCK);
31619 rc = proxy->pMethod->xUnlock((sqlite3_file*)proxy, eFileLock);
31640 rc = lockProxy->pMethod->xUnlock((sqlite3_file*)lockProxy, NO_LOCK);
36166 winUnlock, /* xUnlock */
40632 ** If the VFS xLock() or xUnlock() returns an error other than SQLITE_BUSY
40641 ** This is usually safe. If an xUnlock fails or appears to fail, there may
40648 ** transition, by the same pager or any other). If the call to xUnlock()
40656 ** doesn't know it because of a previous error in xUnlock). If this happens
40661 ** To work around this, if a call to xUnlock() fails when unlocking the
41346 ** or SHARED_LOCK. Regardless of whether or not the call to xUnlock()
76305 0, /* xUnlock */
76593 0, /* xUnlock */
