Searched refs:ops (Results 1 – 7 of 7) sorted by relevance
37 -- into no-ops.56 # the deletes should be no-ops so the table should remain unchanged.68 # the updates should be no-ops so the table should remain unchanged.
42 # mutex (sqlite3Config.pInitMutex) twice. Subsequent calls are no-ops
99 # no-ops.
119 # e_vacuum-1.2.1 - Perform many INSERT, UPDATE and DELETE ops on table t1.
878 # PRAGMA index_info and index_xinfo are no-ops on a virtual table
1231 static const u8 ops[] = {TK_GE, TK_LE}; in exprAnalyze() local1239 pNewExpr = sqlite3PExpr(pParse, ops[i], in exprAnalyze()
1369 ** also be no-ops, and any attempt to read the journal would return1573 ** are harmless no-ops.)^1578 ** All other valid calls to sqlite3_shutdown() are harmless no-ops.)^2016 ** They are retained for backwards compatibility but are now no-ops.7803 ** behave as no-ops.7866 ** xMutexInit() must be no-ops.