Lines Matching refs:used

47 ** Be aware that these macros may not be used within this particular
50 ** The SQLITE_EXTERN and SQLITE_API macros are used to instruct the
53 ** The SQLITE_CDECL macro is used to set the calling convention for
56 ** The SQLITE_APICALL macro is used to set the calling convention for
59 ** The SQLITE_STDCALL macro is no longer used and is now deprecated.
61 ** The SQLITE_CALLBACK macro is used to set the calling convention for
64 ** The SQLITE_SYSAPI macro is used to set the calling convention for
68 ** SQLITE_SYSAPI macros are used only when building for environments
94 ** These no-op macros are used in front of interfaces to mark those
100 ** These macros used to resolve to various kinds of compiler magic that
101 ** would generate warning messages when they were used. But that
128 ** numbers used in [SQLITE_VERSION].)^
239 ** This interface can be used by an application to make sure that the
466 #define SQLITE_MISUSE 21 /* Library used incorrectly */
469 #define SQLITE_FORMAT 24 /* Not used */
579 ** used as the third argument to the [sqlite3_open_v2()] interface.
692 ** When the SQLITE_SYNC_DATAONLY flag is used, it means that the
737 ** This object defines the methods used to perform various operations
869 ** The [SQLITE_FCNTL_LOCKSTATE] opcode is used for debugging. This
877 ** The [SQLITE_FCNTL_SIZE_HINT] opcode is used by SQLite to give the VFS
885 ** The [SQLITE_FCNTL_SIZE_LIMIT] opcode is used by in-memory VFS that
894 ** The [SQLITE_FCNTL_CHUNK_SIZE] opcode is used to request that the VFS
903 ** The [SQLITE_FCNTL_FILE_POINTER] opcode is used to obtain a pointer
908 ** The [SQLITE_FCNTL_JOURNAL_POINTER] opcode is used to obtain a pointer
939 ** ^The [SQLITE_FCNTL_WIN32_AV_RETRY] opcode is used to configure automatic
956 ** ^The [SQLITE_FCNTL_PERSIST_WAL] opcode is used to set or query the
959 ** files used for transaction control
972 ** ^The [SQLITE_FCNTL_POWERSAFE_OVERWRITE] opcode is used to set or query the
985 ** transaction. This is used by VACUUM operations.
988 ** ^The [SQLITE_FCNTL_VFSNAME] opcode can be used to obtain the names of
1055 ** The [SQLITE_FCNTL_MMAP_SIZE] file control is used to query or set the
1056 ** maximum number of bytes that will be used for memory-mapped I/O.
1062 ** file-control is used internally to implement [PRAGMA mmap_size].
1067 ** This file control is used by some VFS activity tracing [shims].
1079 ** The [SQLITE_FCNTL_WIN32_GET_HANDLE] opcode can be used to obtain the
1085 ** The [SQLITE_FCNTL_WIN32_SET_HANDLE] opcode is used for debugging. This
1087 ** pointed to by the pArg argument. This capability is used during testing
1102 ** The [SQLITE_FCNTL_RBU] opcode is implemented by the special VFS used by
1141 ** The [SQLITE_FCNTL_LOCK_TIMEOUT] opcode is used to configure a VFS
1149 ** The [SQLITE_FCNTL_DATA_VERSION] opcode is used to detect changes to
1156 ** interface can be used to find if any database on the connection has changed,
1181 ** The EXPERIMENTAL [SQLITE_FCNTL_EXTERNAL_READER] opcode is used to detect
1189 ** other process. This opcode cannot be used to detect transactions opened
1269 ** Type [sqlite3_filename] is used by SQLite to pass filenames to the
1308 ** structure used by this VFS. mxPathname is the maximum length of
1346 ** or [sqlite3_open16()] is used, then flags includes at least
1386 ** ^The [SQLITE_OPEN_EXCLUSIVE] flag is always used in conjunction
1390 ** SQLITE_OPEN_CREATE, is used to indicate that file should always
1392 ** It is <i>not</i> used to indicate the file should be opened
1410 ** flag is never actually used and is not implemented in the built-in
1444 ** are not used by the SQLite core. These optional interfaces are provided
1499 ** These integer constants can be used as the third parameter to
1508 ** The SQLITE_ACCESS_READWRITE constant is currently used only by the
1513 ** currently unused, though it might be used in a future release of
1641 ** The sqlite3_config() interface is used to make global configuration
1675 ** The sqlite3_db_config() interface is used to make configuration
1696 ** This object is used in only one place in the SQLite interface.
1710 ** also used during testing of SQLite in order to specify an alternative
1736 ** by xInit. The pAppData pointer is used as the only parameter to
1783 ** all mutexing and puts SQLite into a mode where it can only be used
1825 ** alternative low-level memory allocation routines to be used in place of
1835 ** This option can be used to overload the default memory allocation
1867 ** <dd> The SQLITE_CONFIG_SCRATCH option is no longer used.
1923 ** The argument specifies alternative low-level mutex routines to be used
1937 ** This option can be used to overload the default mutex allocation
1938 ** routines with a wrapper used to track mutex usage for performance
1952 ** option to [sqlite3_db_config()] can be used to change the lookaside
1967 ** <dd> The SQLITE_CONFIG_LOG option is used to configure the SQLite
2015 ** <dd> These options are obsolete and should not be used by new code.
2113 ** configuration setting is never used, then the default maximum is determined
2123 #define SQLITE_CONFIG_SCRATCH 6 /* No longer used */
2187 ** <dd> ^This option is used to enable or disable the enforcement of
2198 ** <dd> ^This option is used to enable or disable [CREATE TRIGGER | triggers].
2215 ** <dd> ^This option is used to enable or disable [CREATE VIEW | views].
2232 ** <dd> ^This option is used to enable or disable the
2246 ** <dd> ^This option is used to enable or disable the [sqlite3_load_extension()]
2263 ** <dd> ^This option is used to change the name of the "main" database
2276 ** operation before closing the connection. This option may be used to
2293 ** was used during testing in the lab.
2304 ** option is used to set or clear (the default) a flag that governs this
2468 ** names are not also used by explicitly declared columns. ^If
2572 ** ^This means that if the changes() SQL function (or similar) is used
2575 ** ^If it is used by the second or subsequent such statement within a trigger
2719 ** The sqlite3_busy_handler() interface is used to implement
2985 ** option is used.
3032 ** SQLite contains a high-quality pseudo-random number generator (PRNG) used to
3034 ** already uses the largest possible [ROWID]. The PRNG is also used for
3094 ** return can be used to deny an untrusted user access to individual
3104 ** An authorizer is used when [sqlite3_prepare | preparing]
3130 ** ^When [sqlite3_prepare_v2()] is used to prepare a statement, the
3156 ** Note that SQLITE_IGNORE is also used as a [conflict resolution mode]
3174 ** codes is used as the second parameter. ^(The 5th parameter to the
3214 #define SQLITE_COPY 0 /* No longer used */
3224 ** These routines register callback functions that can be used for
3235 ** The [SQLITE_TRACE_SIZE_LIMIT] compile-time option can be used to limit
3370 ** interrupted. This feature can be used to implement a
3394 ** [sqlite3_errmsg()] or [sqlite3_errmsg16()] routines can be used to obtain
3424 ** it does not already exist. This is the behavior that is always used for
3495 ** a NULL pointer then the default [sqlite3_vfs] object is used.
3543 ** <li> <b>vfs</b>: ^The "vfs" parameter may be used to specify the name of
3545 ** be used to access the database file on disk. ^If this option is set to
3546 ** an empty string the default VFS object is used. ^Specifying an unknown
3547 ** VFS is an error. ^If sqlite3_open_v2() is used and the vfs option is
3562 ** or writes from disk is used. ^It is an error to specify a value for
3571 ** ^If sqlite3_open_v2() is used and the "cache" parameter is present in
3619 ** necessary - space characters can be used literally
3642 ** <b>Note to Windows users:</b> The encoding used for the filename argument
3830 ** used again after sqlite3_free_filename(Y) has been called. This means
4008 ** used to implement an SQL statement. If [sqlite3_prepare_v2()] or
4063 ** be used just once or at most a few times and then destroyed using
4070 ** <dd>The SQLITE_PREPARE_NORMALIZE flag is a no-op. This flag used
4099 ** [sqlite3_prepare_v3()] has an extra "prepFlags" option that is used
4154 ** always used to do, [sqlite3_step()] will automatically recompile the SQL
4237 ** SQL text used to create [prepared statement] P if P was
4245 ** semantics used to normalize a SQL statement are unspecified and subject
4353 ** This interface can be used in combination [sqlite3_next_stmt()]
4355 ** connection that are in need of being reset. This can be used,
4375 ** [sqlite3_value_dup()] interface can be used to construct a new
4386 ** sqlite3_value objects and they can be used interchangeably. However,
4397 ** Unprotected sqlite3_value objects may only be used as arguments
4448 ** SQL parameter is used more than once, second and subsequent
4579 ** ^This routine can be used to find the number of [SQL parameters]
4587 ** number of unique parameters. If parameters of the ?NNN form are used,
4775 ** used to hold those values.
4833 ** be the case that the same database connection is being used by two or
4847 ** can be used to restore the legacy behavior.
4901 ** Note that the SQLITE_TEXT constant was also used in SQLite version 2
4969 ** is used to extract the value) then an automatic type conversion is performed.
4975 ** The return value of sqlite3_column_type() can be used to decide which
4976 ** of the first six interface should be used to extract the column value.
4985 ** or sqlite3_column_bytes16() interfaces can be used to determine the size
5022 ** an unprotected sqlite3_value object may only be used safely with
5025 ** [sqlite3_column_value()] is used in any other way, including calls
5035 ** is requested, [sqlite3_snprintf()] is used internally to perform the
5105 ** [sqlite3_finalize()] is called. ^The memory space used to hold strings
5202 ** are used to add SQL functions or aggregates or to redefine the behavior
5237 ** [SQLITE_UTF16] if [sqlite3_value_text16()] is used, or [SQLITE_UTF8]
5259 ** used inside of triggers, view, CHECK constraints, or other elements of
5285 ** non-NULL, in which case the new function may be used as either an aggregate
5303 ** SQL function is used. ^A function implementation with a non-negative
5390 ** be deterministic in order to be used in certain contexts such as
5398 ** from top-level SQL, and cannot be used in VIEWs or TRIGGERs nor in
5503 ** are used to pass parameter information into the functions that
5627 ** information can be used to pass a limited amount of context from
5727 ** These functions may be used by (non-aggregate) SQL functions to
5806 ** These routines are used by the xFunc or xFinal callbacks that
5812 ** functions used to bind values to host parameters in prepared statements.
5930 ** ^A [protected sqlite3_value] object may always be used where an
5932 ** kind of [sqlite3_value] object can be used with this interface.
6047 ** collating function is registered and used, then the behavior of SQLite
6096 ** can be used, a single callback function may be registered with the
6102 ** encoded in UTF-8. ^If sqlite3_collation_needed16() is used,
6177 ** if a [database connection] is being used at the same time in a separate
6234 ** if a [database connection] is being used at the same time in a separate
6257 ** [sqlite3_win32_set_directory] interface is used to set the value associated
6262 ** prior to being used. The [sqlite3_win32_set_directory] interface returns
6320 ** to the [sqlite3_prepare_v2()] call (or its variants) that was used to
6363 ** will be an absolute pathname, even if the filename used
6367 ** can be used as the filename input parameter to these routines:
6657 ** must be used, it is recommended that shared cache only be enabled for
6678 ** held by the database library. Memory used to cache database
6804 ** for the table using the same algorithm used by the database engine to
6899 ** [SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION] method be used to enable only this
7009 ** Structures used by the virtual table interface
7074 ** The sqlite3_index_info structure and its substructures is used as part
7128 ** ^[sqlite3_free()] is used to free idxPtr if and only if
7162 ** used with an SQLite version earlier than 3.8.2, the results of attempting
7165 ** therefore only be used if [sqlite3_libversion_number()] returns a
7168 ** It may therefore only be used if
7191 int idxNum; /* Number used to identify the index */
7201 sqlite3_uint64 colUsed; /* Input: Mask of columns used by statement */
7227 ** used.
7245 ** The collating sequence to be used for comparison can be found using
7273 ** ^These routines are used to register a new [virtual table module] name.
7363 ** [virtual table] and are used
7366 ** by the [sqlite3_module.xClose | xClose] method. Cursors are used
7427 ** can be used to read or write small subsections of the BLOB.
7505 ** and the built-in [zeroblob] SQL function may be used to create a
7529 ** ^This function is used to move an existing [BLOB handle] so that it points
7593 ** ^(This function is used to read data from an open [BLOB handle] into a
7622 ** ^(This function is used to write data into an open [BLOB handle] from a
7752 ** is used but not necessarily so when SQLITE_MUTEX_FAST is used.
7763 ** used by the current version of SQLite. Future versions of SQLite
7770 ** or SQLITE_MUTEX_RECURSIVE) is used then sqlite3_mutex_alloc()
7817 ** used to allocate and use mutexes.
7825 ** Additionally, an instance of this structure can be used as an
7979 ** ^A NULL pointer can be used in place of "main" to refer to the
8014 ** ^The sqlite3_test_control() interface is used to read out internal
8033 ** These constants are the valid operation code parameters used
8098 ** The parser used by SQLite is forgiving. It is often possible to use
8104 ** using keywords as identifiers. Common techniques used to avoid keyword
8209 ** ^This method can be used, for example, to add whitespace indentation.
8247 ** [sqlite3_str] object. Applications must not used the pointer returned
8261 ** ^These interfaces are used to retrieve runtime status information
8322 ** <dd>This parameter returns the number of pages used out of the
8344 ** <dd>No longer used.</dd>
8347 ** <dd>No longer used.</dd>
8350 ** <dd>No longer used.</dd>
8375 ** ^This interface is used to retrieve runtime status information
8437 ** memory used by all pager caches associated with the database connection.)^
8444 ** memory used by that pager cache is divided evenly between the attached
8454 ** memory used to store the schema for all databases associated
8456 ** ^The full amount of memory used by the schemas is reported, even if the
8463 ** and lookaside memory used by all prepared statements associated with
8496 ** additional overhead. This parameter can be used help identify
8530 ** be used to monitor the performance characteristics of the prepared
8536 ** ^(This interface is used to retrieve and reset counter values from
8580 ** used as a proxy for the total work done by the prepared statement.
8608 ** used to store the prepared statement. ^This value is not actually
8661 ** SQLite is used for the page cache.
8665 ** that memory is allocated and released, and the policies used to
8686 ** built-in default page cache is used instead of the application defined
8691 ** It can be used to clean up
8717 ** created will be used to cache database pages of a file stored on disk, or
8718 ** false if it is used for an in-memory database. The cache implementation
8743 ** pointer to a buffer of szPage bytes used to store the content of a
8787 ** The xRekey() method is used to change the key value associated with the
8800 ** ^The xDestroy() method is used to delete a cache allocated by xCreate().
8832 ** by sqlite3_pcache_methods2. This object is not used by SQLite. It is
8919 ** ^The [sqlite3_backup] object may be used with the sqlite3_backup_step() and
8954 ** is being used to write to the source database when sqlite3_backup_step()
8974 ** used by the backup operation, then the backup will be automatically
8976 ** database is modified by the using the same database connection as is used
8990 ** and may not be used following a call to sqlite3_backup_finish().
9020 ** ^The source [database connection] may be used by the application for other
9023 ** connections, then the source database connection may be used concurrently
9036 ** guarantee that the shared cache used by the destination database
9068 ** ^This API may be used to register a callback that SQLite will invoke
9198 ** ^The definition of [GLOB] pattern matching used in
9215 ** ^The definition of [LIKE] pattern matching used in
9239 ** used with [sqlite3_snprintf()] to generate the final output string.
9260 ** ^The [sqlite3_wal_hook()] function is used to register a callback that
9314 ** ^The [wal_autocheckpoint pragma] can be used to invoke this interface
9341 ** This interface used to be the only way to cause a checkpoint to
9439 ** ^The [PRAGMA wal_checkpoint] command can be used to invoke this interface
9480 ** is used.
9530 ** prohibits that virtual table from being used from within triggers and
9627 ** This API may only be used from within an [xBestIndex|xBestIndex method]
9650 ** "aOrderBy" field are adjacent.)^ This mode is used when the query planner
9663 ** This mode is used for a DISTINCT query.
9669 ** it is not required to omit any rows. This mode is used for queries
9699 ** This interface may only be used from within an
9822 ** This API may only be used from within the [xBestIndex|xBestIndex method]
9868 ** Note that the [SQLITE_IGNORE] constant is also used as a potential
9873 /* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback */
9882 ** The following constants can be used for the T parameter to the
9910 ** used for the X-th loop.
9941 ** Since this interface is expected to be rarely used, it is only
9952 ** zero or greater than or equal to the total number of loops used to implement
10075 ** undefined. This must only be used within SQLITE_UPDATE and SQLITE_DELETE
10076 ** preupdate callbacks; if it is used by an SQLITE_INSERT callback then the
10084 ** undefined. This must only be used within SQLITE_INSERT and SQLITE_UPDATE
10085 ** preupdate callbacks; if it is used by an SQLITE_DELETE callback then the
10095 ** When the [sqlite3_blob_write()] API is used to update a blob column,
10205 ** [SQLITE_ENABLE_SNAPSHOT] compile-time option is used.
10254 ** [SQLITE_ENABLE_SNAPSHOT] compile-time option is used.
10271 ** [SQLITE_ENABLE_SNAPSHOT] compile-time option is used.
10279 ** The sqlite3_snapshot_cmp(P1, P2) interface is used to compare the ages
10445 ** flag should only be used if SQLITE_DESERIALIZE_FREEONCLOSE is also used.