Lines Matching defs:module

1299 ** The mutex module within SQLite defines [sqlite3_mutex] to be an
1350 ** The zName field holds the name of the VFS module. The name must
1635 ** setting up a default [sqlite3_vfs] module, or setting up
3436 const char *zVfs /* Name of VFS module to use */
6022 ** KEYWORDS: sqlite3_module {virtual table module}
6024 ** This structure, sometimes called a "virtual table module",
6026 ** This structure consists mostly of methods for the module.
6028 ** ^A virtual table module is created by filling in a persistent
6032 ** module or until the [database connection] closes. The content
6078 ** method of a [virtual table module]. The fields under **Inputs** are the
6224 ** ^These routines are used to register a new [virtual table module] name.
6226 ** creating a new [virtual table] using the module and before using a
6227 ** preexisting [virtual table] for the module.
6229 ** ^The module name is registered on the [database connection] specified
6230 ** by the first parameter. ^The name of the module is given by the
6232 ** the implementation of the [virtual table module]. ^The fourth
6234 ** into the [xCreate] and [xConnect] methods of the virtual table module
6247 sqlite3 *db, /* SQLite connection to register module with */
6248 const char *zName, /* Name of the module */
6249 const sqlite3_module *p, /* Methods for the module */
6253 sqlite3 *db, /* SQLite connection to register module with */
6254 const char *zName, /* Name of the module */
6255 const sqlite3_module *p, /* Methods for the module */
6264 ** Every [virtual table module] implementation uses a subclass
6267 ** be tailored to the specific needs of the module implementation.
6269 ** common to all module implementations.
6279 const sqlite3_module *pModule; /* The module for this virtual table */
6289 ** Every [virtual table module] implementation uses a subclass of the
6293 ** [sqlite3_module.xOpen | xOpen] method of the module and are destroyed
6296 ** of the module. Each module implementation will define
6311 ** [virtual table module] call this interface
6322 ** using the [xFindFunction] method of the [virtual table module].
7314 ** the pluggable module. The SQLite core has no knowledge of
8781 ** module function, including [sqlite3session_delete()] on the session object
8784 ** Because the session module uses the [sqlite3_preupdate_hook()] API, it
8807 ** results of attempting to use pSession with any other session module
9842 ** change that caused the conflict is not applied. The session module
9895 ** the sessions module invokes to incrementally request input data as it is
9910 ** Each time the xInput callback is invoked by the sessions module, the first
9922 ** invoked by the sessions module at any point during the lifetime of the
9954 ** The sessions module never invokes an xOutput callback with the third
13287 /* Try to return memory used by the pcache module to the main memory heap */
14242 ** Each SQLite module (virtual table definition) is defined by an
14251 Table *pEpoTab; /* Eponymous table for this module */
14384 Module *pMod; /* Pointer to module implementation */
14420 int nModuleArg; /* Number of arguments to the module */
14421 char **azModuleArg; /* 0: module 1: schema 2: vtab name 3...: args */
15572 Token sArg; /* Complete text of a module argument */
17617 ** This module implements the sqlite3_status() interface and related
20493 ** Initialize this module.
20529 ** Deinitialize this module.
20636 ** All of the static variables used by this module are collected
20639 ** when this module is combined with other in the amalgamation.
21185 ** All of the static variables used by this module are collected
21188 ** when this module is combined with other in the amalgamation.
21640 ** Initialize this module.
21665 ** Deinitialize this module.
21867 ** All of the static variables used by this module are collected
21870 ** when this module is combined with other in the amalgamation.
22286 ** Deinitialize this module.
28793 ** only zeroes the requested number of bytes whereas this module will
34904 ** used by the test_multiplex.c module.
38665 ** Initialize this module.
38714 ** Deinitialize this module.
43543 sqlite3_pcache *pCache; /* Pluggable cache module */
44393 ** is the extension added by the btree.c module containing information such
44397 ** module (pcache1.c). The PgHdr1 header is a subclass of sqlite3_pcache_page.
44415 ** This module tracks pointers to PgHdr1 objects. Only pcache.c communicates
44416 ** with this module. Information is passed back and forth as PgHdr1 pointers.
44419 ** The btree.c module deals with pointers to MemPage objects.
45531 ** install the default pluggable cache module, assuming the user has not
45639 ** This module implements an object we call a "RowSet".
46275 /* Return true if the argument is non-NULL and the WAL module is using
46277 ** WAL module is using shared-memory, return false.
46810 ** the pcache module to the pagerStress() routine to write cached data
46816 ** comes up during savepoint rollback that requires the pcache module
51545 ** read from the database file. In some cases, the pcache module may
53054 ** This function is called by the wal module when writing page content
53428 ** Return a pointer to the pPager->pBackup variable. The backup module
53429 ** in backup.c maintains the content of this variable. This module
53513 /* If the pager is already in exclusive-mode, the WAL module will use
54956 sqlite3_vfs *pVfs, /* vfs module to open wal and wal-index */
57048 ** Return true if the argument is non-NULL and the WAL module is using
57050 ** WAL module is using shared-memory, return false.
57058 ** every other subsystem, so the WAL module can put whatever it needs
58268 ** as this module treats each table as a separate structure. To determine
67827 ** Return the size of the header added to each page by this module.
68155 ** Then clear the Btree layer MemPage.isInit flag. Both this module
72530 ** virtual module tables written in this transaction. This has to
83602 ** method of the module. The interpretation of the P4 string is left
83603 ** to the module implementation.
83728 /* Invoke the xNext() method of the module. There is no way for the
84515 ** are not easily obtainable. And for the sessions module, an
84519 ** using the incremental-blob API, this works. For the sessions module
84634 ** Here is the (internal, non-API) interface between this module and the
84755 ** If SQLITE_DEBUG_SORTER_THREADS is defined, this module outputs various
85042 ** by this module. If using a separate allocation for each in-memory record
85524 ** Usually, the sorter module uses the value of (pCsr->pKeyInfo->nField)
87729 ** case none of the code in this module is executed as a result of calls
105176 ** Externally accessible module functions
107735 /* Record that this module has started */
111113 ** buffer that the pager module resizes using sqlite3_realloc().
121745 ** The actual function that does the work of creating a new module.
121750 sqlite3 *db, /* Database in which module is registered */
121751 const char *zName, /* Name assigned to this module */
121752 const sqlite3_module *pModule, /* The definition of the module */
121792 ** External API function used to create a new virtual-table module.
121795 sqlite3 *db, /* Database in which module is registered */
121796 const char *zName, /* Name assigned to this module */
121797 const sqlite3_module *pModule, /* The definition of the module */
121807 ** External API function used to create a new virtual-table module.
121810 sqlite3 *db, /* Database in which module is registered */
121811 const char *zName, /* Name assigned to this module */
121812 const sqlite3_module *pModule, /* The definition of the module */
121996 ** Add a new module argument to pTable->azModuleArg[].
122017 ** statement. The module name has been parsed, but the optional list
122018 ** of parameters that follow the module name are still pending.
122024 Token *pModuleName, /* Name of the module for the virtual table */
122066 ** This routine takes the module argument that has been accumulating
122165 ** of an argument to the module name in a CREATE VIRTUAL TABLE statement.
122175 ** in an argument to the module name in a CREATE VIRTUAL TABLE statement.
122333 /* Locate the required virtual table module */
122339 sqlite3ErrorMsg(pParse, "no such module: %s", zModule);
122401 /* Locate the required virtual table module */
122405 /* If the module has been registered and includes a Create method,
122406 ** invoke it now. If the module has not been registered, return an
122410 *pzErr = sqlite3MPrintf(db, "no such module: %s", zMod);
122431 ** virtual table module.
122634 ** virtual module xSync() callback. It is illegal to write to
122635 ** virtual module tables in this case, so return SQLITE_LOCKED.
122820 ** Check to see if virtual table module pMod can be have an eponymous
122826 ** module, and more importantly, does not require a CREATE VIRTUAL TABLE
122830 ** Any virtual table module for which xConnect and xCreate are the same
122869 ** virtual table module pMod, if it exists.
122954 ** This module contains C code that generates VDBE code used to process
123977 /* This module is only called on query plans that use an index. */
125354 ** This module contains C code that generates VDBE code used to process
126718 ** This module contains C code that generates VDBE code used to process
126719 ** the WHERE clause of SQL statements. This module is responsible for
126722 ** so is applicable. Because this module is responsible for selecting
126723 ** indices, you might also think of this module as the "query optimizer".
139582 const char *zVfs /* Name of VFS module to use */
140204 ** SQL Logic Test or SLT test module) can run the same SQL multiple times
140864 ** This is an SQLite module implementing full-text search.
140870 ** * The FTS3 module is being built as an extension
140873 ** * The FTS3 module is being built into the core of
141272 ** Destroy an existing tokenizer. The fts3 module calls this method
141289 ** Destroy an existing tokenizer cursor. The fts3 module calls this
141337 const sqlite3_tokenizer_module *pModule; /* The module for this tokenizer */
141369 ** hash table implementation for the full-text indexing module.
141856 /* The following are used by the fts3_eval.c module. */
141862 /* The following are used by the fts3_snippet.c module. */
142857 ** argv[0] -> module name ("fts3" or "fts4")
142860 ** argv[...] -> "column name" and other module argument fields.
142923 ** module (i.e. all the column names and special arguments). This loop
144587 ** made by an fts4aux module, not an FTS table. In this case calling
145590 ** This function is registered as the module destructor (called when an
145686 ** module with sqlite.
146038 ** through doclists. It is used by this module to iterate through phrase
146039 ** doclists in reverse and by the fts3_write.c module to iterate through
147426 ** This function is used by the matchinfo() module to query a phrase
147632 ** the eval module. Specifically, this means to free:
148116 ** this module will not return a row with a negative languageid), and
148195 ** Register the fts3aux module with database connection db. Return SQLITE_OK
148246 ** This module contains code that implements a parser for fts3 query strings
148255 ** By default, this module parses the legacy syntax that has been
148271 ** If compiled with SQLITE_TEST defined, then this module exports the
148273 ** to zero causes the module to use the old syntax. If it is set to
148279 ** generator. This module does not use actually lemon, it uses a
148327 sqlite3_tokenizer *pTokenizer; /* Tokenizer module */
148752 ** first implemented. Whichever it was, this module duplicates the
149194 sqlite3_tokenizer *pTokenizer, /* Tokenizer module */
149244 ** The first parameter, pTokenizer, is passed the fts3 tokenizer module to
149257 sqlite3_tokenizer *pTokenizer, /* Tokenizer module */
149469 sqlite3_result_error(context, "No such tokenizer module", -1);
149559 ** implementation for the full-text indexing module.
149565 ** * The FTS3 module is being built as an extension
149568 ** * The FTS3 module is being built into the core of
149950 ** * The FTS3 module is being built as an extension
149953 ** * The FTS3 module is being built into the core of
150609 ** This is part of an SQLite module implementing full-text search.
150616 ** * The FTS3 module is being built as an extension
150619 ** * The FTS3 module is being built into the core of
151134 ** * The FTS3 module is being built as an extension
151137 ** * The FTS3 module is being built into the core of
151365 ** This file contains code for the "fts3tokenize" virtual table module.
151380 ** The virtual table module tokenizes this <string>, using the FTS3
151505 ** argv[0]: module name
151771 ** Register the fts3tok module with database connection db. Return SQLITE_OK
151822 ** This file is part of the SQLite FTS3 extension module. Specifically,
151864 ** If this module is built with SQLITE_TEST defined, these constants may
158220 sqlite3_tokenizer_module *pMod; /* Tokenizer module methods object */
159579 static const sqlite3_tokenizer_module module = {
159588 *ppModule = &module;
159976 ** algorithms packaged as an SQLite virtual table module.
160713 ** the virtual table module xCreate() and xConnect() methods.
160720 ** Rtree virtual table module xCreate method.
160733 ** Rtree virtual table module xConnect method.
160773 ** Rtree virtual table module xDisconnect method.
160781 ** Rtree virtual table module xDestroy method.
160808 ** Rtree virtual table module xOpen method.
160845 ** Rtree virtual table module xClose method.
160859 ** Rtree virtual table module xEof method.
160882 ** implementation will only be used if this module is compiled as part
161347 ** Rtree virtual table module xNext method.
161361 ** Rtree virtual table module xRowid method.
161375 ** Rtree virtual table module xColumn method.
161482 ** Rtree virtual table module xFilter method.
161599 ** Rtree virtual table module xBestIndex method. There are three
162815 ** The xUpdate method for rtree module virtual tables.
162946 ** The xRename method for rtree module virtual tables.
163184 ** argv[0] -> module name
163363 ** Register the r-tree module with database handle db. This creates the
163364 ** virtual table module "rtree" and the debugging/analysis scalar
164387 ** module takes an EXCLUSIVE lock on the database file, ensuring
165019 /* Maximum number of prepared UPDATE statements held by this module */
170312 ** Invoke this routine to register the "dbstat" virtual table module
170893 ** module does not record changes for rows with NULL values stored in
171427 ** session module. */
171553 ** The 'pre-update' hook registered by this module with SQLite databases.
177937 ** This exists in order to allow the fts5_index.c module to return a
178147 /* The following are used internally by the fts5_index.c module. They are
178207 ** This interface is used by the fts5vocab module.
178261 ** Functions called by the storage module as part of integrity-check.
178266 ** Called during virtual module initialization to register UDF
178491 ** C code in this module. The interfaces below this point are called by
180747 ** used by the fts5_hash.c module. This is not important for correct
180748 ** operation of the module, but is necessary to ensure that some tests
180809 ** This is an SQLite module implementing full-text search.
185004 ** The %_data table managed by this module,
187473 ** This function is a no-op unless SQLITE_DEBUG is defined when this module
190322 ** Move to the next matching term/rowid. Used by the fts5vocab module.
190413 ** Return the total number of blocks this module has read from the %_data
191371 ** This is called as part of registering the FTS5 module with database
191419 ** This is an SQLite module implementing full-text search.
191462 ** During a write-transaction the fts5_index.c module may cache some data
191478 ** A single object of this type is allocated when the FTS5 module is
191488 Fts5TokenizerModule *pDfltTok; /* Default tokenizer module */
191493 ** Each auxiliary function registered with the FTS5 module is represented
191507 ** Each tokenizer module registered with the FTS5 module is represented
191516 Fts5TokenizerModule *pNext; /* Next registered tokenizer module */
191757 ** argv[0] -> module name ("fts5")
191760 ** argv[...] -> "column name" and other module argument fields.
194099 ** The following functions are used to register the module with SQLite. If
194100 ** this module is being built as part of the SQLite core (SQLITE_CORE is
194103 ** Or, if this module is being built as a loadable extension,
194585 Fts5Storage *p, /* Storage module to write to */
195100 /* Pass the expected checksum down to the FTS index module. It will
195778 fts5_tokenizer tokenizer; /* Parent tokenizer module */
197236 ** This is an SQLite virtual table module implementing direct access to an
197237 ** existing FTS5 index. The module may create several different types of
197362 ** argv[0] -> module name ("fts5vocab")