Lines Matching defs:module
1504 ** Used by the cksmvfs VFS module only.
1564 ** The mutex module within SQLite defines [sqlite3_mutex] to be an
1641 ** The zName field holds the name of the VFS module. The name must
1932 ** setting up a default [sqlite3_vfs] module, or setting up
3986 const char *zVfs /* Name of VFS module to use */
7379 ** KEYWORDS: sqlite3_module {virtual table module}
7381 ** This structure, sometimes called a "virtual table module",
7383 ** This structure consists mostly of methods for the module.
7385 ** ^A virtual table module is created by filling in a persistent
7389 ** module or until the [database connection] closes. The content
7438 ** method of a [virtual table module]. The fields under **Inputs** are the
7634 ** ^These routines are used to register a new [virtual table module] name.
7636 ** creating a new [virtual table] using the module and before using a
7637 ** preexisting [virtual table] for the module.
7639 ** ^The module name is registered on the [database connection] specified
7640 ** by the first parameter. ^The name of the module is given by the
7642 ** the implementation of the [virtual table module]. ^The fourth
7644 ** into the [xCreate] and [xConnect] methods of the virtual table module
7657 ** NULL then no new module is created and any existing modules with the
7663 sqlite3 *db, /* SQLite connection to register module with */
7664 const char *zName, /* Name of the module */
7665 const sqlite3_module *p, /* Methods for the module */
7669 sqlite3 *db, /* SQLite connection to register module with */
7670 const char *zName, /* Name of the module */
7671 const sqlite3_module *p, /* Methods for the module */
7697 ** Every [virtual table module] implementation uses a subclass
7700 ** be tailored to the specific needs of the module implementation.
7702 ** common to all module implementations.
7712 const sqlite3_module *pModule; /* The module for this virtual table */
7722 ** Every [virtual table module] implementation uses a subclass of the
7726 ** [sqlite3_module.xOpen | xOpen] method of the module and are destroyed
7729 ** of the module. Each module implementation will define
7744 ** [virtual table module] call this interface
7755 ** using the [xFindFunction] method of the [virtual table module].
8989 ** the pluggable module. The SQLite core has no knowledge of
11015 ** module function, including [sqlite3session_delete()] on the session object
11018 ** Because the session module uses the [sqlite3_preupdate_hook()] API, it
11042 ** results of attempting to use pSession with any other session module
11187 ** Legacy (older than 3.22.0) versions of the sessions module cannot capture
12203 ** Usually, the sessions module encloses all operations performed by
12207 ** causes the sessions module to omit this savepoint. In this case, if the
12288 ** change that caused the conflict is not applied. The session module
12497 ** the sessions module invokes to incrementally request input data as it is
12512 ** Each time the xInput callback is invoked by the sessions module, the first
12524 ** invoked by the sessions module at any point during the lifetime of the
12556 ** The sessions module never invokes an xOutput callback with the third
12647 ** changes to the sessions module in order to tune it to the specific needs
12663 ** By default, the sessions module streaming interfaces attempt to input
16648 /* Try to return memory used by the pcache module to the main memory heap */
17536 ** Each SQLite module (virtual table definition) is defined by an
17546 Table *pEpoTab; /* Eponymous table for this module */
17732 Module *pMod; /* Pointer to module implementation */
17782 int nArg; /* Number of arguments to the module */
17783 char **azArg; /* 0: module 1: schema 2: vtab name 3...: args */
19206 Token sArg; /* Complete text of a module argument */
22403 ** This module implements the sqlite3_status() interface and related
25702 ** Initialize this module.
25729 ** Deinitialize this module.
25836 ** All of the static variables used by this module are collected
25839 ** when this module is combined with other in the amalgamation.
26385 ** All of the static variables used by this module are collected
26388 ** when this module is combined with other in the amalgamation.
26840 ** Initialize this module.
26865 ** Deinitialize this module.
27067 ** All of the static variables used by this module are collected
27070 ** when this module is combined with other in the amalgamation.
27495 ** Deinitialize this module.
35438 ** only zeroes the requested number of bytes whereas this module will
42928 ** used by the test_multiplex.c module.
46643 ** Initialize this module.
46692 ** Deinitialize this module.
52662 sqlite3_pcache *pCache; /* Pluggable cache module */
52926 ** to this module, the extra space really ends up being the MemPage
53561 ** is the extension added by the btree.c module containing information such
53565 ** module (pcache1.c). The PgHdr1 header is a subclass of sqlite3_pcache_page.
53584 ** This module tracks pointers to PgHdr1 objects. Only pcache.c communicates
53585 ** with this module. Information is passed back and forth as PgHdr1 pointers.
53588 ** The btree.c module deals with pointers to MemPage objects.
54725 ** install the default pluggable cache module, assuming the user has not
54830 ** This module implements an object we call a "RowSet".
55471 /* Return true if the argument is non-NULL and the WAL module is using
55473 ** WAL module is using shared-memory, return false.
56015 ** the pcache module to the pagerStress() routine to write cached data
56021 ** comes up during savepoint rollback that requires the pcache module
61014 ** read from the database file. In some cases, the pcache module may
62656 ** This function is called by the wal module when writing page content
63020 ** Return a pointer to the pPager->pBackup variable. The backup module
63021 ** in backup.c maintains the content of this variable. This module
63123 /* If the pager is already in exclusive-mode, the WAL module will use
64835 sqlite3_vfs *pVfs, /* vfs module to open wal and wal-index */
67427 ** Return true if the argument is non-NULL and the WAL module is using
67429 ** WAL module is using shared-memory, return false.
67437 ** every other subsystem, so the WAL module can put whatever it needs
68789 ** as this module treats each table as a separate structure. To determine
79711 ** Return the size of the header added to each page by this module.
80040 ** Then clear the Btree layer MemPage.isInit flag. Both this module
85311 ** virtual module tables written in this transaction. This has to
98425 ** method of the module. The interpretation of the P4 string is left
98426 ** to the module implementation.
98565 /* Invoke the xNext() method of the module. There is no way for the
99675 ** are not easily obtainable. And for the sessions module, an
99679 ** using the incremental-blob API, this works. For the sessions module
99797 ** Here is the (internal, non-API) interface between this module and the
99918 ** If SQLITE_DEBUG_SORTER_THREADS is defined, this module outputs various
100205 ** by this module. If using a separate allocation for each in-memory record
100688 ** Usually, the sorter module uses the value of (pCsr->pKeyInfo->nKeyField)
103338 ** case none of the code in this module is executed as a result of calls
127242 ** Externally accessible module functions
130328 /* Record that this module has started */
134815 ** buffer that the pager module resizes using sqlite3_realloc().
136851 ** Pragma virtual table module xConnect method.
136913 ** Pragma virtual table module xDisconnect method.
137011 ** Pragma virtual table module xFilter method.
137061 ** Pragma virtual table module xEof method.
137087 ** Pragma virtual table module xRowid method.
149970 ** and the module is not already part of the connection.
149972 ** If there already exists a module with zName, replace it with the new one.
149973 ** If pModule==0, then delete the module zName if it exists.
149976 sqlite3 *db, /* Database in which module is registered */
149977 const char *zName, /* Name assigned to this module */
149978 const sqlite3_module *pModule, /* The definition of the module */
150019 ** The actual function that does the work of creating a new module.
150024 sqlite3 *db, /* Database in which module is registered */
150025 const char *zName, /* Name assigned to this module */
150026 const sqlite3_module *pModule, /* The definition of the module */
150042 ** External API function used to create a new virtual-table module.
150045 sqlite3 *db, /* Database in which module is registered */
150046 const char *zName, /* Name assigned to this module */
150047 const sqlite3_module *pModule, /* The definition of the module */
150057 ** External API function used to create a new virtual-table module.
150060 sqlite3 *db, /* Database in which module is registered */
150061 const char *zName, /* Name assigned to this module */
150062 const sqlite3_module *pModule, /* The definition of the module */
150096 ** module when the reference count reaches zero.
150291 ** Add a new module argument to pTable->u.vtab.azArg[].
150319 ** statement. The module name has been parsed, but the optional list
150320 ** of parameters that follow the module name are still pending.
150326 Token *pModuleName, /* Name of the module for the virtual table */
150367 ** This routine takes the module argument that has been accumulating
150465 ** of an argument to the module name in a CREATE VIRTUAL TABLE statement.
150475 ** in an argument to the module name in a CREATE VIRTUAL TABLE statement.
150641 /* Locate the required virtual table module */
150647 sqlite3ErrorMsg(pParse, "no such module: %s", zModule);
150711 /* Locate the required virtual table module */
150715 /* If the module has been registered and includes a Create method,
150716 ** invoke it now. If the module has not been registered, return an
150720 *pzErr = sqlite3MPrintf(db, "no such module: %s", zMod);
150741 ** virtual table module.
150959 ** virtual module xSync() callback. It is illegal to write to
150960 ** virtual module tables in this case, so return SQLITE_LOCKED.
151151 ** Check to see if virtual table module pMod can be have an eponymous
151158 ** module, and more importantly, does not require a CREATE VIRTUAL TABLE
151162 ** Any virtual table module for which xConnect and xCreate are the same
151201 ** virtual table module pMod, if it exists.
151296 ** This module contains C code that generates VDBE code used to process
152706 /* This module is only called on query plans that use an index. */
154709 ** This module contains C code that generates VDBE code used to process
156562 ** This module contains C code that generates VDBE code used to process
156563 ** the WHERE clause of SQL statements. This module is responsible for
156566 ** so is applicable. Because this module is responsible for selecting
156567 ** indices, you might also think of this module as the "query optimizer".
173448 ** Forward declarations of external module initializer functions
177001 const char *zVfs /* Name of VFS module to use */
177679 ** SQL Logic Test or SLT test module) can run the same SQL multiple times
178715 ** This is an SQLite module implementing full-text search.
178721 ** * The FTS3 module is being built as an extension
178724 ** * The FTS3 module is being built into the core of
179123 ** Destroy an existing tokenizer. The fts3 module calls this method
179140 ** Destroy an existing tokenizer cursor. The fts3 module calls this
179188 const sqlite3_tokenizer_module *pModule; /* The module for this tokenizer */
179220 ** hash table implementation for the full-text indexing module.
179740 /* The following are used by the fts3_eval.c module. */
179746 /* The following are used by the fts3_snippet.c module. */
180808 ** argv[0] -> module name ("fts3" or "fts4")
180811 ** argv[...] -> "column name" and other module argument fields.
180874 ** module (i.e. all the column names and special arguments). This loop
182624 ** made by an fts4aux module, not an FTS table. In this case calling
183611 ** by this module.
183652 ** This function is registered as the module destructor (called when an
183752 ** module with sqlite.
184112 ** through doclists. It is used by this module to iterate through phrase
184113 ** doclists in reverse and by the fts3_write.c module to iterate through
185503 ** This function is used by the matchinfo() module to query a phrase
185712 ** the eval module. Specifically, this means to free:
186201 ** this module will not return a row with a negative languageid), and
186280 ** Register the fts3aux module with database connection db. Return SQLITE_OK
186332 ** This module contains code that implements a parser for fts3 query strings
186341 ** By default, this module parses the legacy syntax that has been
186357 ** If compiled with SQLITE_TEST defined, then this module exports the
186359 ** to zero causes the module to use the old syntax. If it is set to
186365 ** generator. This module does not use actually lemon, it uses a
186413 sqlite3_tokenizer *pTokenizer; /* Tokenizer module */
186839 ** first implemented. Whichever it was, this module duplicates the
187281 sqlite3_tokenizer *pTokenizer, /* Tokenizer module */
187331 ** The first parameter, pTokenizer, is passed the fts3 tokenizer module to
187344 sqlite3_tokenizer *pTokenizer, /* Tokenizer module */
187629 ** implementation for the full-text indexing module.
187635 ** * The FTS3 module is being built as an extension
187638 ** * The FTS3 module is being built into the core of
188020 ** * The FTS3 module is being built as an extension
188023 ** * The FTS3 module is being built into the core of
188679 ** This is part of an SQLite module implementing full-text search.
188686 ** * The FTS3 module is being built as an extension
188689 ** * The FTS3 module is being built into the core of
189208 ** * The FTS3 module is being built as an extension
189211 ** * The FTS3 module is being built into the core of
189439 ** This file contains code for the "fts3tokenize" virtual table module.
189454 ** The virtual table module tokenizes this <string>, using the FTS3
189579 ** argv[0]: module name
189846 ** Register the fts3tok module with database connection db. Return SQLITE_OK
189900 ** This file is part of the SQLite FTS3 extension module. Specifically,
189942 ** If this module is built with SQLITE_TEST defined, these constants may
196443 sqlite3_tokenizer_module *pMod; /* Tokenizer module methods object */
197842 static const sqlite3_tokenizer_module module = {
197851 *ppModule = &module;
200959 ** algorithms packaged as an SQLite virtual table module.
201915 ** the virtual table module xCreate() and xConnect() methods.
201922 ** Rtree virtual table module xCreate method.
201935 ** Rtree virtual table module xConnect method.
201980 ** Rtree virtual table module xDisconnect method.
201988 ** Rtree virtual table module xDestroy method.
202016 ** Rtree virtual table module xOpen method.
202065 ** Rtree virtual table module xClose method.
202080 ** Rtree virtual table module xEof method.
202634 ** Rtree virtual table module xNext method.
202652 ** Rtree virtual table module xRowid method.
202666 ** Rtree virtual table module xColumn method.
202776 ** Rtree virtual table module xFilter method.
202898 ** Rtree virtual table module xBestIndex method. There are three
204162 ** The xUpdate method for rtree module virtual tables.
204331 ** The xRename method for rtree module virtual tables.
204355 ** This module does not need to do anything to support savepoints. However,
204413 ** by this module.
204668 ** argv[0] -> module name
206566 ** argv[0] -> module name
206653 ** GEOPOLY virtual table module xCreate method.
206666 ** GEOPOLY virtual table module xConnect method.
206680 ** GEOPOLY virtual table module xFilter method.
206811 ** Rtree virtual table module xBestIndex method. There are three
206873 ** GEOPOLY virtual table module xColumn method.
206910 ** The xUpdate method for GEOPOLY module virtual tables.
207171 ** Register the r-tree module with database handle db. This creates the
207172 ** virtual table module "rtree" and the debugging/analysis scalar
208213 ** module takes an EXCLUSIVE lock on the database file, ensuring
208815 ** function may be used to register a callback that the RBU module will invoke
208905 /* Maximum number of prepared UPDATE statements held by this module */
209067 ** this array set set to 1. This is because in that case, the module has
214216 ** do not cause undefined behaviour. This module pads each page buffer
214269 /* Forward reference to data structured used in this module */
215051 ** Invoke this routine to register the "dbstat" virtual table module
215479 ** Invoke this routine to register the "dbpage" virtual table module
216129 ** module does not record changes for rows with NULL values stored in
216864 ** session module. */
217002 ** The 'pre-update' hook registered by this module with SQLite databases.
220983 ** Buffers a1 and a2 must both contain a sessions module record nCol
220984 ** fields in size. This function appends an nCol sessions module
222096 ** This exists in order to allow the fts5_index.c module to return a
222310 /* The following are used internally by the fts5_index.c module. They are
222375 ** This interface is used by the fts5vocab module.
222432 ** Functions called by the storage module as part of integrity-check.
222437 ** Called during virtual module initialization to register UDF
222684 ** C code in this module. The interfaces below this point are called by
225357 ** used by the fts5_hash.c module. This is not important for correct
225358 ** operation of the module, but is necessary to ensure that some tests
225419 ** This is an SQLite module implementing full-text search.
230065 ** The %_data table managed by this module,
232628 ** This function is a no-op unless SQLITE_DEBUG is defined when this module
235654 ** Move to the next matching term/rowid. Used by the fts5vocab module.
235746 ** Return the total number of blocks this module has read from the %_data
236788 ** This is called as part of registering the FTS5 module with database
236841 ** This is an SQLite module implementing full-text search.
236886 ** During a write-transaction the fts5_index.c module may cache some data
236902 ** A single object of this type is allocated when the FTS5 module is
236912 Fts5TokenizerModule *pDfltTok; /* Default tokenizer module */
236917 ** Each auxiliary function registered with the FTS5 module is represented
236931 ** Each tokenizer module registered with the FTS5 module is represented
236940 Fts5TokenizerModule *pNext; /* Next registered tokenizer module */
237179 ** argv[0] -> module name ("fts5")
237182 ** argv[...] -> "column name" and other module argument fields.
239629 ** by this module.
239716 ** The following functions are used to register the module with SQLite. If
239717 ** this module is being built as part of the SQLite core (SQLITE_CORE is
239720 ** Or, if this module is being built as a loadable extension,
240217 Fts5Storage *p, /* Storage module to write to */
240736 /* Pass the expected checksum down to the FTS index module. It will
241476 fts5_tokenizer tokenizer; /* Parent tokenizer module */
243477 ** This is an SQLite virtual table module implementing direct access to an
243478 ** existing FTS5 index. The module may create several different types of
243618 ** argv[0] -> module name ("fts5vocab")