Lines Matching defs:ops
179 ** large file support, or if the OS is windows, these should be no-ops.
1686 ** also be no-ops, and any attempt to read the journal would return
1890 ** are harmless no-ops.)^
1895 ** All other valid calls to sqlite3_shutdown() are harmless no-ops.)^
2333 ** They are retained for backwards compatibility but are now no-ops.
8164 ** behave as no-ops.
8227 ** xMutexInit() must be no-ops.
14712 ** macros become no-ops and have zero performance impact.
15650 ** and DELETE operations as no-ops, and any READ operation against a
15798 ** Enter and Leave procedures no-ops.
38423 ** operations become no-ops. Locking operations still happen internally,
55369 ** commits (WAL_SYNC_FLAGS(X)) or for checkpoint ops (CKPT_SYNC_FLAGS(X)):
59363 ** Unless -DSQLITE_TEST=1 is used, these routines are all no-ops
64291 ** In locking_mode=EXCLUSIVE, all of these routines become no-ops.
68552 ** these two routines, all mutex operations are no-ops in that case and
68556 ** the ones below, are no-ops and are null #defines in btree.h.
68699 ** So define the lock related functions as no-ops.
73151 ** operations on this cursor can be no-ops and all READ operations can
90445 ** should be no-ops except for special builds used to measure test coverage.
91280 ** of VDBE ops have been executed (either since this invocation of
129172 ** above are all no-ops
152307 ** are no-ops) at the beginning and end of zAff are ignored. If all entries
155928 static const u8 ops[] = {TK_GE, TK_LE};
155936 pNewExpr = sqlite3PExpr(pParse, ops[i],
157253 ** are no-ops.
208686 ** SQLITE_OK, all subsequent calls on the same RBU handle are no-ops
209098 sqlite3_stmt *pDelete; /* Statement for DELETE ops */
211840 ** no-ops. These locks will not be released until the connection
213272 ** are no-ops on target database files in RBU_STAGE_OAL mode. This is
213288 ** locks are no-ops (so that once obtained, these locks are never