Lines Matching defs:api
336 ** not a published API of SQLite, is subject to change without
345 ** The official C-language API documentation for SQLite is derived
808 ** In its default configuration, SQLite API routines return one of 30 integer
817 ** [sqlite3_extended_result_codes()] API. Or, the extended code for
1766 ** API. The SQLITE_OPEN_EXCLUSIVE flag, when paired with the
2704 ** The [sqlite3_enable_load_extension()] API enables or disables both the
2705 ** C-API [sqlite3_load_extension()] and the SQL function [load_extension()].
2707 ** When the first argument to this interface is 1, then only the C-API is
2709 ** this interface is 0, then both the C-API and the SQL function are disabled.
2711 ** the C-API or the SQL function.
2793 ** process requires the use of this obscure API and multiple steps to
3426 ** passed to this API, the new connection blocks until the exclusive lock
4505 ** ^If the most recent sqlite3_* API call associated with
4508 ** API call.
4515 ** sqlite3_extended_errcode() might change with each API call.
4591 ** API call.
5213 ** [sqlite3_bind_parameter_index()] API if desired. ^The index
5263 ** if the call to the bind API fails, except the destructor is not called if
5619 ** API always returns a generic error code, [SQLITE_ERROR], following any
5945 ** the [sqlite3_bind_blob | sqlite3_bind_*() API] retain their values.
7067 ** ^If the function is registered using the sqlite3_collation_needed() API,
7316 ** threads should mutex-protect calls to this API and should make their own
7469 ** ^For the purposes of this API, a transaction is said to have been
7810 ** call to any SQLite API function.
7877 ** prior to calling this API,
7902 ** [extension loading] while evaluating user-entered SQL, the following API
7910 ** ^This interface enables or disables both the C-API
7913 ** to enable or disable only the C-API.)^
8379 ** ^(This API makes sure a global version of a function with a particular
8381 ** before this API is called, a new function is created.)^ ^The implementation
8429 ** the API is not misused, it is always safe to call [sqlite3_blob_close()]
8608 ** not possible to increase the size of a BLOB using this API.
8991 ** Unlike most of the SQLite API, this function is not guaranteed to
9672 ** custom page cache using this API, an application can better control
9868 ** See Also: [Using the SQLite Online Backup API]
9873 ** CAPI3REF: Online Backup API.
9875 ** The backup API copies the content of one database into another.
9879 ** See Also: [Using the SQLite Online Backup API]
10036 ** [database connection] is not passed to any other API (by any thread) after
10058 ** <b>Alternatives To Using The Backup API</b>
10087 ** ^This API may be used to register a callback that SQLite will invoke
10089 ** ^This API is only available if the library was compiled with the
10129 ** any sqlite3_xxx API functions from within an unlock-notify callback, a
10157 ** action (a reasonable assumption), then using this API may cause the
10676 ** This API may only be used from within an [xBestIndex|xBestIndex method]
10892 ** This API may only be used from within the [xBestIndex|xBestIndex method]
11044 ** the EXPLAIN QUERY PLAN output) are available. Invoking API
11084 ** This API is only available if the library is built with pre-processor
11207 ** When the [sqlite3_blob_write()] API is used to update a blob column,
11211 ** sqlite3_blob_write() API, the [sqlite3_preupdate_blobwrite()] returns
11413 ** Otherwise, this API returns a negative value if P1 refers to an older
11857 ** Because the session module uses the [sqlite3_preupdate_hook()] API, it
11909 ** the [sqlite3session_changeset_size()] API. Because it imposes some
11910 ** computational overhead, this API is disabled by default. Argument
11912 ** 0, then the sqlite3session_changeset_size() API is disabled. If it
11913 ** is greater than 0, then the same API is enabled. Or, if the initial
11915 ** variable is set to 1 if the sqlite3session_changeset_size() API is
12100 ** using the [sqlite3changeset_start()] API. A changeset may be applied to
12102 ** API.
12162 ** When a session object is disabled (see the [sqlite3session_enable()] API),
12186 ** to enable this API using sqlite3session_object_config() with the
12276 ** sqlite3changeset_xxx API functions except for sqlite3changeset_invert(),
12283 ** is passed to the sqlite3changeset_apply() API. Other conflict types work
12317 ** This API returns the total amount of heap memory in bytes currently
12360 ** Note that the sqlite3changeset_start_v2() API is still <b>experimental</b>
12844 ** sqlite3changegroup_schema() API, then it is possible to combine changesets
13085 ** Note that the sqlite3changeset_apply_v2() API is still <b>experimental</b>
13205 API are undefined.
13234 ** sqlite3changeset_conflict() API are undefined.
13435 ** CAPI3REF: Streaming Versions of API functions.
13437 ** The six streaming API xxx_strm() functions serve similar purposes to the
13438 ** corresponding non-streaming API functions:
13460 ** is passed to a streaming API functions by way of a callback function that
13462 ** required. In all cases, a pair of API function parameters such as
13484 ** an error, all processing is abandoned and the streaming API function
13493 ** Similarly, streaming API functions that return changesets (or patchsets)
13517 ** is immediately abandoned and the streaming API function returns a copy
13704 ** This API is used, in concert with other sqlite3changegroup_change_xxx()
13941 const Fts5ExtensionApi *pApi, /* API offered by current FTS version */
13954 ** EXTENSION API FUNCTIONS
13958 ** API when the extension function was registered.
14014 ** This API can be quite slow if used with an FTS5 table created with the
14017 ** (i.e. if it is a contentless table), then this API always returns 0.
14031 ** This API can be quite slow if used with an FTS5 table created with the
14041 ** This API function is used to query the FTS table for phrase iPhrase
14050 ** is invoked. The context and API objects passed to the callback
14052 ** Invoking Api.xUserData() returns a copy of the pointer passed as
14074 ** the same MATCH query using the xGetAuxdata() API.
14117 ** to use, this API may be faster under some circumstances. To iterate
14131 ** with the xPhraseFirst() and xPhraseNext() API methods (and by
14134 ** This API can be quite slow if used with an FTS5 table created with the
14137 ** (i.e. if it is a contentless table), then this API always iterates
14163 ** This API can be quite slow if used with an FTS5 table created with the
14166 ** then this API always iterates through an empty set (all calls to
14169 ** The information accessed using this API and its companion
14171 ** (or xInst/xInstCount). The chief advantage of this API is that it is
14206 ** This API may be slow in some cases if the token identified by parameters
14208 ** first call to this API for each prefix token in the query is forced
14210 ** token to collect the extra data required by this API. If the prefix
14214 ** If the user knows in advance that a query may use this API for a
14217 ** entirely. This also causes prefix queries that do not use this API to
14223 ** This API can be quite slow if used with an FTS5 table created with the
14246 ** API is the same as the xTokenize() API, except that it allows a tokenizer
14420 ** Tokenizer implementations registered using either API may be retrieved
14593 ** FTS5 EXTENSION REGISTRATION API
14646 ** END OF REGISTRATION API
15149 ** SQLITE_WIN32_MALLOC // Use Win32 native heap API
16827 ** sqlite3PagerJournalSizeLimit() API. See also "PRAGMA journal_size_limit".
16879 ** are exposed in the API via the "PRAGMA journal_mode" command and
16932 ** that make up the Pager sub-system API. See source code comments for
19039 ** SQLITE_FUNC_CONSTANT == SQLITE_DETERMINISTIC from the API
19040 ** SQLITE_FUNC_DIRECT == SQLITE_DIRECTONLY from the API
19042 ** SQLITE_FUNC_ENCMASK depends on SQLITE_UTF* macros in the API
24811 ** sqlite3_preupdate_*() API functions.
31074 ** API.
31083 ** For WinCE, some API function parameters do not appear to be declared as
32339 ** Take actions at the end of an API call to deal with error codes.
32351 ** This function must be called before exiting any API function (i.e.
38269 ** Log an error that is an API call on a connection pointer that should
38275 "API call with %s database connection pointer",
44150 ** when restoring a database using the backup API from a zero-length
47566 ** sqlite_file_control API is not affected by SQLITE_FORCE_PROXY_LOCKING).
49075 * various Win32 API heap functions instead of our own.
50136 ** the LockFileEx() API. But we can still statically link against that
50137 ** API as long as we don't call it when running Win95/98/ME. A call to
50140 ** the LockFileEx() API.
51093 ** An implementation of the LockFile() API of Windows for CE
51159 ** An implementation of the UnlockFile API of Windows for CE
51241 ** API LockFile.
51359 ** API UnlockFile.
51419 /* API oddity: If successful, SetFilePointer() returns a dword
51991 ** Different API routines are called depending on whether or not this
52002 ** API LockFileEx.
53870 ** it must be converted to a native Win32 path via the Cygwin API
54536 ** using the GetFullPathName Win32 API function (if available).
61516 ** the error-code about to be returned by a pager API function. The
61522 ** all major API calls on the Pager will immediately return Pager.errCode.
63305 ** returned to the caller of the pager API function.
64301 ** via the sqlite3PagerGetExtra() API. When a new page is allocated, the
64429 ** filename without using the sqlite3_filename_database() API. This is a
67090 ** or wal_blocking_checkpoint() API functions.
76233 ** This is useful in one special case in the backup API code where it is
79383 ** have been deleted? This API will need to change to return an error code
84703 ** API functions and the related features.
84739 ** * Via the sqlite3_backup_XXX() API function backup_step() and
84750 ** The other sqlite3_backup_XXX() API functions, backup_remaining() and
87016 ** external API. It works in a similar way to sqlite3_value_text(),
87043 ** TODO: Maybe someday promote this interface into a published API so
93570 sqlite3_log(SQLITE_MISUSE, "API called with finalized prepared statement");
93578 sqlite3_log(SQLITE_MISUSE, "API called with NULL prepared statement");
94295 ** API. The only thing omitted is the automatic recompile if a
94892 ** sqlite3_column_XXX API, then set the return code of the statement to
96716 ** be freed lazily via the sqlite3_release_memory() API. This
105263 ** sqlite3_set_auxdata() API may be safely retained until the next
105282 ** sqlite3_set_auxdata() API may be safely retained until the next
105820 /* Jump to here if the sqlite3_interrupt() API sets the interrupt
106256 ** using the incremental-blob API, this works. For the sessions module
106389 ** Here is the (internal, non-API) interface between this module and the
126062 ** API. This facility is an optional feature of the library. Embedded
133139 ** API function sqlite3_count_changes) to be set incorrectly.
134314 ** value is the same as the sqlite3_last_insert_rowid() API function.
134348 ** the same as the sqlite3_total_changes64() API function.
135532 ** flag is set. See the sqlite3_enable_load_extension() API.
136852 ** in production builds. This function is not an API and is subject to
136896 ** in production builds. This function is not an API and is subject to
137271 ** Query API Notes
142217 #define SQLITE_CORE 1 /* Disable the API redefinition in sqlite3ext.h */
142243 ** The following structure holds pointers to all of the SQLite API
142608 const sqlite3_api_routines *pThunk /* Extension API function pointers. */
142612 ** The following macros redefine the API routines so that they are
142619 ** the API. So the redefinition macros are only valid if the
142967 ** Some API routines are omitted when various features are
143062 ** The following structure contains pointers to all SQLite API routines.
143071 ** sqlite3_libversion_number() to make sure that the API they
143209 ** The original API set ends here. All extensions can call any
143213 ** a library that is new enough to support that API.
147242 ** sqlite3_hard_heap_limit64() C-language API can raise or deactivate
148581 ** Two versions of the official API. Legacy and new use. In the legacy
148709 ** Two versions of the official API. Legacy and new use. In the legacy
161726 ** External API function used to create a new virtual-table module.
161741 ** External API function used to create a new virtual-table module.
161757 ** External API to drop all virtual-table modules, except those named
166950 ** API. To work around them, add a dummy OP_Variable here.
168597 ** This object is not an API and can be changed from one release to the
176594 ** be implemented using an API, built-in window functions are much more
176597 ** As such, some built-in window functions use the same API as aggregate
176599 ** instructions. Additionally, for those functions that use the API, the
178114 ** that do not use the standard function API, generate the required
178246 ** API, generate the equivalent VM code.
178383 ** aggregate window functions that use the standard API, a single
186729 ** This file contains C code that implements the sqlite3_complete() API.
187520 ** This API allows applications to modify the global configuration of
188226 ** Set the value returned by the sqlite3_last_insert_rowid() API function.
188773 /* SQLITE_MISUSE */ "bad parameter or other API misuse",
189294 ** wrong context. The sqlite3_overload_function() API might construct
190147 ** user to API functions sqlite3_open() or sqlite3_open_v2(), and for database
190523 /* Beginning with version 3.37.0, using the VFS xFetch() API to memory-map
190723 ** using the sqlite3_automatic_extension() API.
191233 ** API uses microseconds. Hence the 1000's.
192319 ** API method and its associated functionality.
193016 ** we will need a way to register the API consistently.
193492 ** statements is run and reset within a single virtual table API call.
199814 ** Initialize API pointer table, if required.
225588 ** The API declared below allows an application to apply an RBU update
225677 ** the zipvfs_create_vfs() API below for details on using RBU with zipvfs.
225718 ** describing the sqlite3rbu_create_vfs() API function below for
225752 ** API allows the application direct access to these database handles.
225837 ** progress indications for the two stages of an RBU update. This API may
225849 ** If this API is called during stage 2 of the update, output variable
225855 ** If this API is called during stage 1 of the update, output variable
225869 ** API is called during stage 1, the *pnOne output variable is set to the
225919 ** Except on WINCE platforms, where it uses win32 API MoveFileW(). This
226281 ** API to calculate the permyriadage progress of populating the *-oal file
237259 ** API sqlite3changeset_next(). If SQLITE_ROW is returned, then the
240629 const Fts5ExtensionApi *pApi, /* API offered by current FTS version */
240642 ** EXTENSION API FUNCTIONS
240646 ** API when the extension function was registered.
240702 ** This API can be quite slow if used with an FTS5 table created with the
240705 ** (i.e. if it is a contentless table), then this API always returns 0.
240719 ** This API can be quite slow if used with an FTS5 table created with the
240729 ** This API function is used to query the FTS table for phrase iPhrase
240738 ** is invoked. The context and API objects passed to the callback
240740 ** Invoking Api.xUserData() returns a copy of the pointer passed as
240762 ** the same MATCH query using the xGetAuxdata() API.
240805 ** to use, this API may be faster under some circumstances. To iterate
240819 ** with the xPhraseFirst() and xPhraseNext() API methods (and by
240822 ** This API can be quite slow if used with an FTS5 table created with the
240825 ** (i.e. if it is a contentless table), then this API always iterates
240851 ** This API can be quite slow if used with an FTS5 table created with the
240854 ** then this API always iterates through an empty set (all calls to
240857 ** The information accessed using this API and its companion
240859 ** (or xInst/xInstCount). The chief advantage of this API is that it is
240894 ** This API may be slow in some cases if the token identified by parameters
240896 ** first call to this API for each prefix token in the query is forced
240898 ** token to collect the extra data required by this API. If the prefix
240902 ** If the user knows in advance that a query may use this API for a
240905 ** entirely. This also causes prefix queries that do not use this API to
240911 ** This API can be quite slow if used with an FTS5 table created with the
240934 ** API is the same as the xTokenize() API, except that it allows a tokenizer
241108 API may be retrieved
241281 ** FTS5 EXTENSION REGISTRATION API
241334 ** END OF REGISTRATION API
242197 ** The fts5_expr.c API above this point is used by the other hand-written
243879 const Fts5ExtensionApi *pApi; /* API offered by current FTS version */
244074 const Fts5ExtensionApi *pApi, /* API offered by current FTS version */
244202 const Fts5ExtensionApi *pApi, /* API offered by current FTS version */
244259 const Fts5ExtensionApi *pApi, /* API offered by current FTS version */
244534 const Fts5ExtensionApi *pApi, /* API offered by current FTS version */
244593 const Fts5ExtensionApi *pApi, /* API offered by current FTS version */
249413 ** Does the work of the fts5_api.xQueryToken() API method.
249438 ** Does the work of the fts5_api.xInstToken() API method.
256458 ** xInstToken() API.
256495 ** when the xInstToken() API is used. This is done by the nMapAlloc, nMap and
257759 ** using the xInstToken() API. In this case the caller tokenizers the
259703 fts5_api api; /* User visible part of object (see fts5.h) */
259851 /* Cache used by auxiliary API
261815 ** Implementation of xTokenize_v2() API.
261838 ** Implementation of xTokenize() API. This is just xTokenize_v2() with NULL/0
261930 ** This is called by various API functions - xInst, xPhraseFirst,
262365 ** xQueryToken() API implemenetation.
262379 ** xInstToken() API implemenetation.
262413 ** The xColumnLocale() API.
262480 ** Implementation of API function xQueryPhrase().
262919 ** the fts5_tokenizer_v2 API, and those that provide access to a v2 tokenizer
262920 ** via the fts5_tokenizer API.
263226 ** API pointer.
263238 if( ppApi ) *ppApi = &pGlobal->api;
263422 pGlobal->api.iVersion = 3;
263423 pGlobal->api.xCreateFunction = fts5CreateAux;
263424 pGlobal->api.xCreateTokenizer = fts5CreateTokenizer;
263425 pGlobal->api.xFindTokenizer = fts5FindTokenizer;
263426 pGlobal->api.xCreateTokenizer_v2 = fts5CreateTokenizer_v2;
263427 pGlobal->api.xFindTokenizer_v2 = fts5FindTokenizer_v2;
263441 if( rc==SQLITE_OK ) rc = sqlite3Fts5AuxInit(&pGlobal->api);
263442 if( rc==SQLITE_OK ) rc = sqlite3Fts5TokenizerInit(&pGlobal->api);
263478 rc = sqlite3Fts5TestRegisterMatchinfoAPI(&pGlobal->api);
264995 ** rows. However this function is only called from the xRowCount() API,
264996 ** and there is no way for that API to be invoked if the table contains
Indexes created Sun May 03 00:22:47 UTC 2026