Package-level declarations

These integer constants can be used as the third parameter to the xAccess method of an sqlite3_vfs object. They determine what kind of permissions the xAccess method is looking for. With SQLITE_ACCESS_EXISTS, the xAccess method simply checks whether the file exists.

The sqlite3_set_authorizer() interface registers a callback function that is invoked to authorize certain SQL statement actions. The second parameter to the callback is an integer code that specifies what action is being authorized. These are the integer action codes that the authorizer callback may be passed.

The authorizer callback function must return either SQLITE_OK or one of these two constants in order to signal SQLite whether or not the action is permitted. See the authorizer documentation for additional information.

Flags for opening a BLOB.

These constants define all valid values for the "checkpoint mode" passed as the third parameter to the sqlite3_wal_checkpoint_v2() interface. See the sqlite3_wal_checkpoint_v2() documentation for details on the meaning of each of these checkpoint modes.

Result for sqlite3_complete().

These constants are returned by sqlite3_vtab_on_conflict() to inform a virtual table implementation of the ON CONFLICT mode for the SQL statement being evaluated.

Every value in SQLite has one of five fundamental datatypes: These constants are codes for each of those types.

Result for sqlite3_db_readonly().

These constants are the available integer "verbs" that can be passed as the second argument to the sqlite3_db_status() interface.

The following are allowed values for the 6th argument (the F argument) to the sqlite3_deserialize(D,S,P,N,M,F) interface.

Available modes for prepared statement explain setting.

These constants may be ORed together with the preferred text encoding as the fourth argument to sqlite3_create_function(), sqlite3_create_function16(), or sqlite3_create_function_v2().

Text encoding that can be ORed with SqliteFunctionFlag and passed to SQLite create function API family.

These bit values are intended for use in the 3rd parameter to the sqlite3_open_v2() interface and in the 4th parameter to the sqlite3_vfs.xOpen method.

These constants define various flags that can be passed into the "prepFlags" parameter of the sqlite3_prepare_v3() and sqlite3_prepare16_v3() interfaces.

Result of an SQLite C-API call returning a result integer.

These constants define various performance limits that can be lowered at run-time using sqlite3_limit(). A concise description of these limits follows, and additional information is available at Limits in SQLite.

The following are allowed values for the 4th argument (the F argument) to the serializeInternal(D,S,P,F) interface.

Event passed as third parameter to an SQLLOG callback.

These constants define integer codes that name counter values associated with the sqlite3_stmt_status() interface.

These integer constants designate various run-time status parameters that can be returned by sqlite3_status().

These constants define integer codes that represent the various text encodings supported by SQLite.

These constants identify classes of events that can be monitored using the sqlite3_trace_v2() tracing logic. The M argument to sqlite3_trace_v2(D,M,X,P) is an OR-ed combination of one or more of the following constants. The first argument to the trace callback is one of the following constants.

These constants define the current transaction state of a database file. The sqlite3_txn_state(D,S) interface returns one of these constants in order to describe the transaction state of schema S in database connection D.

Whether this result is a subclass of SqliteResultCode.OK.

Returns the primary result code for this result.