... SQLITE_BUSY, SQLITE_LOCKED, SQLITE_NOMEM, SQLITE_READONLY, SQLITE_INTERRUPT, SQLITE_IOERR ... 

Many SQLite functions return an integer result code from the set shown here in order to indicate success or failure. New error codes may be added in future versions of SQLite. See also: extended result code definitions See also lists ... 

sqlite3_get_autocommit()

 ... If certain kinds of errors occur on a statement within a multi-statement transaction (errors including SQLITE_FULL, SQLITE_IOERR, SQLITE_NOMEM, SQLITE_BUSY, and SQLITE_INTERRUPT) then the transaction might be rolled back automatically. The only way to find out whether SQLite automatically rolled ... 

sqlite3_win32_set_directory(), sqlite3_win32_set_directory8(), sqlite3_win32_set_directory16()

 ... The sqlite3_win32_set_directory interface returns SQLITE_OK to indicate success, SQLITE_ERROR if the type is unsupported, or SQLITE_NOMEM if memory could not be allocated. The value of the sqlite3_data_directory variable is intended to act as a replacement for the current directory on ... 

sqlite3_str_new()

 ... The sqlite3_str_new(D) interface always returns a pointer to a valid sqlite3_str object, though in the event of an out-of-memory error the returned object might be a special singleton that will silently reject new text, always return SQLITE_NOMEM ... 

sqlite3_str_errcode(), sqlite3_str_length(), sqlite3_str_value()

 ... The sqlite3_str_errcode(X) method returns SQLITE_NOMEM following any out-of-memory error, or SQLITE_TOOBIG if the size of the dynamic string exceeds SQLITE_MAX_LENGTH, or SQLITE_OK if there have been no errors. The sqlite3_str_length(X) method returns the current length, in ... 

sqlite3_complete(), sqlite3_complete16()

 ... If a memory allocation fails, then SQLITE_NOMEM is returned. These routines do not parse the SQL statements thus will not detect syntactically incorrect SQL. If SQLite has not been initialized using sqlite3_initialize() prior to invoking sqlite3_complete16() then sqlite3_initialize() is invoked ... 

SQLITE_LIMIT_LENGTH, SQLITE_LIMIT_SQL_LENGTH, SQLITE_LIMIT_COLUMN, SQLITE_LIMIT_EXPR_DEPTH, SQLITE_LIMIT_COMPOUND_SELECT, SQLITE_LIMIT_VDBE_OP ... 

 ... If sqlite3_prepare_v2() or the equivalent tries to allocate space for more than this many opcodes in a single prepared statement, an SQLITE_NOMEM error is returned. SQLITE_LIMIT_FUNCTION_ARG The maximum number of arguments on a function. SQLITE_LIMIT_ATTACHED The maximum number of attached ... 

sqlite3_snapshot_get()

 ... This function may also return SQLITE_NOMEM. If it is called with the database handle in autocommit mode but fails for some other reason, whether or not a read transaction is opened on schema S is undefined. The sqlite3_snapshot object returned ... 

sqlite3_vtab_in_first(), sqlite3_vtab_in_next()

 ... The return value might be some other value, such as SQLITE_NOMEM, in the event of a malfunction. The *ppOut values returned by these routines are only valid until the next call to either of these routines or until the end ... 

sqlite3_soft_heap_limit64(), sqlite3_hard_heap_limit64()

 ... The soft heap limit is "soft" because even though SQLite strives to stay below the limit, it will exceed the limit rather than generate an SQLITE_NOMEM error. In other words, the soft heap limit is advisory only. The sqlite3_hard_heap_limit64(N ...