1 /* 2 ** 2001-09-15 3 ** 4 ** The author disclaims copyright to this source code. In place of 5 ** a legal notice, here is a blessing: 6 ** 7 ** May you do good and not evil. 8 ** May you find forgiveness for yourself and forgive others. 9 ** May you share freely, never taking more than you give. 10 ** 11 ************************************************************************* 12 ** This header file defines the interface that the SQLite library 13 ** presents to client programs. If a C-function, structure, datatype, 14 ** or constant definition does not appear in this file, then it is 15 ** not a published API of SQLite, is subject to change without 16 ** notice, and should not be referenced by programs that use SQLite. 17 ** 18 ** Some of the definitions that are in this file are marked as 19 ** "experimental". Experimental interfaces are normally new 20 ** features recently added to SQLite. We do not anticipate changes 21 ** to experimental interfaces but reserve the right to make minor changes 22 ** if experience from use "in the wild" suggest such changes are prudent. 23 ** 24 ** The official C-language API documentation for SQLite is derived 25 ** from comments in this file. This file is the authoritative source 26 ** on how SQLite interfaces are supposed to operate. 27 ** 28 ** The name of this file under configuration management is "sqlite.h.in". 29 ** The makefile makes some minor changes to this file (such as inserting 30 ** the version number) and changes its name to "sqlite3.h" as 31 ** part of the build process. 32 */ 33 #ifndef SQLITE3_H 34 #define SQLITE3_H 35 #include <stdarg.h> /* Needed for the definition of va_list */ 36 37 /* 38 ** Make sure we can call this stuff from C++. 39 */ 40 #ifdef __cplusplus 41 extern "C" { 42 #endif 43 44 45 /* 46 ** Facilitate override of interface linkage and calling conventions. 47 ** Be aware that these macros may not be used within this particular 48 ** translation of the amalgamation and its associated header file. 49 ** 50 ** The SQLITE_EXTERN and SQLITE_API macros are used to instruct the 51 ** compiler that the target identifier should have external linkage. 52 ** 53 ** The SQLITE_CDECL macro is used to set the calling convention for 54 ** public functions that accept a variable number of arguments. 55 ** 56 ** The SQLITE_APICALL macro is used to set the calling convention for 57 ** public functions that accept a fixed number of arguments. 58 ** 59 ** The SQLITE_STDCALL macro is no longer used and is now deprecated. 60 ** 61 ** The SQLITE_CALLBACK macro is used to set the calling convention for 62 ** function pointers. 63 ** 64 ** The SQLITE_SYSAPI macro is used to set the calling convention for 65 ** functions provided by the operating system. 66 ** 67 ** Currently, the SQLITE_CDECL, SQLITE_APICALL, SQLITE_CALLBACK, and 68 ** SQLITE_SYSAPI macros are used only when building for environments 69 ** that require non-default calling conventions. 70 */ 71 #ifndef SQLITE_EXTERN 72 # define SQLITE_EXTERN extern 73 #endif 74 #ifndef SQLITE_API 75 # define SQLITE_API 76 #endif 77 #ifndef SQLITE_CDECL 78 # define SQLITE_CDECL 79 #endif 80 #ifndef SQLITE_APICALL 81 # define SQLITE_APICALL 82 #endif 83 #ifndef SQLITE_STDCALL 84 # define SQLITE_STDCALL SQLITE_APICALL 85 #endif 86 #ifndef SQLITE_CALLBACK 87 # define SQLITE_CALLBACK 88 #endif 89 #ifndef SQLITE_SYSAPI 90 # define SQLITE_SYSAPI 91 #endif 92 93 /* 94 ** These no-op macros are used in front of interfaces to mark those 95 ** interfaces as either deprecated or experimental. New applications 96 ** should not use deprecated interfaces - they are supported for backwards 97 ** compatibility only. Application writers should be aware that 98 ** experimental interfaces are subject to change in point releases. 99 ** 100 ** These macros used to resolve to various kinds of compiler magic that 101 ** would generate warning messages when they were used. But that 102 ** compiler magic ended up generating such a flurry of bug reports 103 ** that we have taken it all out and gone back to using simple 104 ** noop macros. 105 */ 106 #define SQLITE_DEPRECATED 107 #define SQLITE_EXPERIMENTAL 108 109 /* 110 ** Ensure these symbols were not defined by some previous header file. 111 */ 112 #ifdef SQLITE_VERSION 113 # undef SQLITE_VERSION 114 #endif 115 #ifdef SQLITE_VERSION_NUMBER 116 # undef SQLITE_VERSION_NUMBER 117 #endif 118 119 /* 120 ** CAPI3REF: Compile-Time Library Version Numbers 121 ** 122 ** ^(The [SQLITE_VERSION] C preprocessor macro in the sqlite3.h header 123 ** evaluates to a string literal that is the SQLite version in the 124 ** format "X.Y.Z" where X is the major version number (always 3 for 125 ** SQLite3) and Y is the minor version number and Z is the release number.)^ 126 ** ^(The [SQLITE_VERSION_NUMBER] C preprocessor macro resolves to an integer 127 ** with the value (X*1000000 + Y*1000 + Z) where X, Y, and Z are the same 128 ** numbers used in [SQLITE_VERSION].)^ 129 ** The SQLITE_VERSION_NUMBER for any given release of SQLite will also 130 ** be larger than the release from which it is derived. Either Y will 131 ** be held constant and Z will be incremented or else Y will be incremented 132 ** and Z will be reset to zero. 133 ** 134 ** Since [version 3.6.18] ([dateof:3.6.18]), 135 ** SQLite source code has been stored in the 136 ** <a href="http://www.fossil-scm.org/">Fossil configuration management 137 ** system</a>. ^The SQLITE_SOURCE_ID macro evaluates to 138 ** a string which identifies a particular check-in of SQLite 139 ** within its configuration management system. ^The SQLITE_SOURCE_ID 140 ** string contains the date and time of the check-in (UTC) and a SHA1 141 ** or SHA3-256 hash of the entire source tree. If the source code has 142 ** been edited in any way since it was last checked in, then the last 143 ** four hexadecimal digits of the hash may be modified. 144 ** 145 ** See also: [sqlite3_libversion()], 146 ** [sqlite3_libversion_number()], [sqlite3_sourceid()], 147 ** [sqlite_version()] and [sqlite_source_id()]. 148 */ 149 #define SQLITE_VERSION "3.44.3" 150 #define SQLITE_VERSION_NUMBER 3044003 151 #define SQLITE_SOURCE_ID "2024-03-24 21:15:01 d68fb8b5dbb8305e00d2dd14d8fe6b3d9f67e2459102ff160d956a6b75ddc18e" 152 153 /* 154 ** CAPI3REF: Run-Time Library Version Numbers 155 ** KEYWORDS: sqlite3_version sqlite3_sourceid 156 ** 157 ** These interfaces provide the same information as the [SQLITE_VERSION], 158 ** [SQLITE_VERSION_NUMBER], and [SQLITE_SOURCE_ID] C preprocessor macros 159 ** but are associated with the library instead of the header file. ^(Cautious 160 ** programmers might include assert() statements in their application to 161 ** verify that values returned by these interfaces match the macros in 162 ** the header, and thus ensure that the application is 163 ** compiled with matching library and header files. 164 ** 165 ** <blockquote><pre> 166 ** assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER ); 167 ** assert( strncmp(sqlite3_sourceid(),SQLITE_SOURCE_ID,80)==0 ); 168 ** assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0 ); 169 ** </pre></blockquote>)^ 170 ** 171 ** ^The sqlite3_version[] string constant contains the text of [SQLITE_VERSION] 172 ** macro. ^The sqlite3_libversion() function returns a pointer to the 173 ** to the sqlite3_version[] string constant. The sqlite3_libversion() 174 ** function is provided for use in DLLs since DLL users usually do not have 175 ** direct access to string constants within the DLL. ^The 176 ** sqlite3_libversion_number() function returns an integer equal to 177 ** [SQLITE_VERSION_NUMBER]. ^(The sqlite3_sourceid() function returns 178 ** a pointer to a string constant whose value is the same as the 179 ** [SQLITE_SOURCE_ID] C preprocessor macro. Except if SQLite is built 180 ** using an edited copy of [the amalgamation], then the last four characters 181 ** of the hash might be different from [SQLITE_SOURCE_ID].)^ 182 ** 183 ** See also: [sqlite_version()] and [sqlite_source_id()]. 184 */ 185 SQLITE_API SQLITE_EXTERN const char sqlite3_version[]; 186 SQLITE_API const char *sqlite3_libversion(void); 187 SQLITE_API const char *sqlite3_sourceid(void); 188 SQLITE_API int sqlite3_libversion_number(void); 189 190 /* 191 ** CAPI3REF: Run-Time Library Compilation Options Diagnostics 192 ** 193 ** ^The sqlite3_compileoption_used() function returns 0 or 1 194 ** indicating whether the specified option was defined at 195 ** compile time. ^The SQLITE_ prefix may be omitted from the 196 ** option name passed to sqlite3_compileoption_used(). 197 ** 198 ** ^The sqlite3_compileoption_get() function allows iterating 199 ** over the list of options that were defined at compile time by 200 ** returning the N-th compile time option string. ^If N is out of range, 201 ** sqlite3_compileoption_get() returns a NULL pointer. ^The SQLITE_ 202 ** prefix is omitted from any strings returned by 203 ** sqlite3_compileoption_get(). 204 ** 205 ** ^Support for the diagnostic functions sqlite3_compileoption_used() 206 ** and sqlite3_compileoption_get() may be omitted by specifying the 207 ** [SQLITE_OMIT_COMPILEOPTION_DIAGS] option at compile time. 208 ** 209 ** See also: SQL functions [sqlite_compileoption_used()] and 210 ** [sqlite_compileoption_get()] and the [compile_options pragma]. 211 */ 212 #ifndef SQLITE_OMIT_COMPILEOPTION_DIAGS 213 SQLITE_API int sqlite3_compileoption_used(const char *zOptName); 214 SQLITE_API const char *sqlite3_compileoption_get(int N); 215 #else 216 # define sqlite3_compileoption_used(X) 0 217 # define sqlite3_compileoption_get(X) ((void*)0) 218 #endif 219 220 /* 221 ** CAPI3REF: Test To See If The Library Is Threadsafe 222 ** 223 ** ^The sqlite3_threadsafe() function returns zero if and only if 224 ** SQLite was compiled with mutexing code omitted due to the 225 ** [SQLITE_THREADSAFE] compile-time option being set to 0. 226 ** 227 ** SQLite can be compiled with or without mutexes. When 228 ** the [SQLITE_THREADSAFE] C preprocessor macro is 1 or 2, mutexes 229 ** are enabled and SQLite is threadsafe. When the 230 ** [SQLITE_THREADSAFE] macro is 0, 231 ** the mutexes are omitted. Without the mutexes, it is not safe 232 ** to use SQLite concurrently from more than one thread. 233 ** 234 ** Enabling mutexes incurs a measurable performance penalty. 235 ** So if speed is of utmost importance, it makes sense to disable 236 ** the mutexes. But for maximum safety, mutexes should be enabled. 237 ** ^The default behavior is for mutexes to be enabled. 238 ** 239 ** This interface can be used by an application to make sure that the 240 ** version of SQLite that it is linking against was compiled with 241 ** the desired setting of the [SQLITE_THREADSAFE] macro. 242 ** 243 ** This interface only reports on the compile-time mutex setting 244 ** of the [SQLITE_THREADSAFE] flag. If SQLite is compiled with 245 ** SQLITE_THREADSAFE=1 or =2 then mutexes are enabled by default but 246 ** can be fully or partially disabled using a call to [sqlite3_config()] 247 ** with the verbs [SQLITE_CONFIG_SINGLETHREAD], [SQLITE_CONFIG_MULTITHREAD], 248 ** or [SQLITE_CONFIG_SERIALIZED]. ^(The return value of the 249 ** sqlite3_threadsafe() function shows only the compile-time setting of 250 ** thread safety, not any run-time changes to that setting made by 251 ** sqlite3_config(). In other words, the return value from sqlite3_threadsafe() 252 ** is unchanged by calls to sqlite3_config().)^ 253 ** 254 ** See the [threading mode] documentation for additional information. 255 */ 256 SQLITE_API int sqlite3_threadsafe(void); 257 258 /* 259 ** CAPI3REF: Database Connection Handle 260 ** KEYWORDS: {database connection} {database connections} 261 ** 262 ** Each open SQLite database is represented by a pointer to an instance of 263 ** the opaque structure named "sqlite3". It is useful to think of an sqlite3 264 ** pointer as an object. The [sqlite3_open()], [sqlite3_open16()], and 265 ** [sqlite3_open_v2()] interfaces are its constructors, and [sqlite3_close()] 266 ** and [sqlite3_close_v2()] are its destructors. There are many other 267 ** interfaces (such as 268 ** [sqlite3_prepare_v2()], [sqlite3_create_function()], and 269 ** [sqlite3_busy_timeout()] to name but three) that are methods on an 270 ** sqlite3 object. 271 */ 272 typedef struct sqlite3 sqlite3; 273 274 /* 275 ** CAPI3REF: 64-Bit Integer Types 276 ** KEYWORDS: sqlite_int64 sqlite_uint64 277 ** 278 ** Because there is no cross-platform way to specify 64-bit integer types 279 ** SQLite includes typedefs for 64-bit signed and unsigned integers. 280 ** 281 ** The sqlite3_int64 and sqlite3_uint64 are the preferred type definitions. 282 ** The sqlite_int64 and sqlite_uint64 types are supported for backwards 283 ** compatibility only. 284 ** 285 ** ^The sqlite3_int64 and sqlite_int64 types can store integer values 286 ** between -9223372036854775808 and +9223372036854775807 inclusive. ^The 287 ** sqlite3_uint64 and sqlite_uint64 types can store integer values 288 ** between 0 and +18446744073709551615 inclusive. 289 */ 290 #ifdef SQLITE_INT64_TYPE 291 typedef SQLITE_INT64_TYPE sqlite_int64; 292 # ifdef SQLITE_UINT64_TYPE 293 typedef SQLITE_UINT64_TYPE sqlite_uint64; 294 # else 295 typedef unsigned SQLITE_INT64_TYPE sqlite_uint64; 296 # endif 297 #elif defined(_MSC_VER) || defined(__BORLANDC__) 298 typedef __int64 sqlite_int64; 299 typedef unsigned __int64 sqlite_uint64; 300 #else 301 typedef long long int sqlite_int64; 302 typedef unsigned long long int sqlite_uint64; 303 #endif 304 typedef sqlite_int64 sqlite3_int64; 305 typedef sqlite_uint64 sqlite3_uint64; 306 307 /* 308 ** If compiling for a processor that lacks floating point support, 309 ** substitute integer for floating-point. 310 */ 311 #ifdef SQLITE_OMIT_FLOATING_POINT 312 # define double sqlite3_int64 313 #endif 314 315 /* 316 ** CAPI3REF: Closing A Database Connection 317 ** DESTRUCTOR: sqlite3 318 ** 319 ** ^The sqlite3_close() and sqlite3_close_v2() routines are destructors 320 ** for the [sqlite3] object. 321 ** ^Calls to sqlite3_close() and sqlite3_close_v2() return [SQLITE_OK] if 322 ** the [sqlite3] object is successfully destroyed and all associated 323 ** resources are deallocated. 324 ** 325 ** Ideally, applications should [sqlite3_finalize | finalize] all 326 ** [prepared statements], [sqlite3_blob_close | close] all [BLOB handles], and 327 ** [sqlite3_backup_finish | finish] all [sqlite3_backup] objects associated 328 ** with the [sqlite3] object prior to attempting to close the object. 329 ** ^If the database connection is associated with unfinalized prepared 330 ** statements, BLOB handlers, and/or unfinished sqlite3_backup objects then 331 ** sqlite3_close() will leave the database connection open and return 332 ** [SQLITE_BUSY]. ^If sqlite3_close_v2() is called with unfinalized prepared 333 ** statements, unclosed BLOB handlers, and/or unfinished sqlite3_backups, 334 ** it returns [SQLITE_OK] regardless, but instead of deallocating the database 335 ** connection immediately, it marks the database connection as an unusable 336 ** "zombie" and makes arrangements to automatically deallocate the database 337 ** connection after all prepared statements are finalized, all BLOB handles 338 ** are closed, and all backups have finished. The sqlite3_close_v2() interface 339 ** is intended for use with host languages that are garbage collected, and 340 ** where the order in which destructors are called is arbitrary. 341 ** 342 ** ^If an [sqlite3] object is destroyed while a transaction is open, 343 ** the transaction is automatically rolled back. 344 ** 345 ** The C parameter to [sqlite3_close(C)] and [sqlite3_close_v2(C)] 346 ** must be either a NULL 347 ** pointer or an [sqlite3] object pointer obtained 348 ** from [sqlite3_open()], [sqlite3_open16()], or 349 ** [sqlite3_open_v2()], and not previously closed. 350 ** ^Calling sqlite3_close() or sqlite3_close_v2() with a NULL pointer 351 ** argument is a harmless no-op. 352 */ 353 SQLITE_API int sqlite3_close(sqlite3*); 354 SQLITE_API int sqlite3_close_v2(sqlite3*); 355 356 /* 357 ** The type for a callback function. 358 ** This is legacy and deprecated. It is included for historical 359 ** compatibility and is not documented. 360 */ 361 typedef int (*sqlite3_callback)(void*,int,char**, char**); 362 363 /* 364 ** CAPI3REF: One-Step Query Execution Interface 365 ** METHOD: sqlite3 366 ** 367 ** The sqlite3_exec() interface is a convenience wrapper around 368 ** [sqlite3_prepare_v2()], [sqlite3_step()], and [sqlite3_finalize()], 369 ** that allows an application to run multiple statements of SQL 370 ** without having to use a lot of C code. 371 ** 372 ** ^The sqlite3_exec() interface runs zero or more UTF-8 encoded, 373 ** semicolon-separate SQL statements passed into its 2nd argument, 374 ** in the context of the [database connection] passed in as its 1st 375 ** argument. ^If the callback function of the 3rd argument to 376 ** sqlite3_exec() is not NULL, then it is invoked for each result row 377 ** coming out of the evaluated SQL statements. ^The 4th argument to 378 ** sqlite3_exec() is relayed through to the 1st argument of each 379 ** callback invocation. ^If the callback pointer to sqlite3_exec() 380 ** is NULL, then no callback is ever invoked and result rows are 381 ** ignored. 382 ** 383 ** ^If an error occurs while evaluating the SQL statements passed into 384 ** sqlite3_exec(), then execution of the current statement stops and 385 ** subsequent statements are skipped. ^If the 5th parameter to sqlite3_exec() 386 ** is not NULL then any error message is written into memory obtained 387 ** from [sqlite3_malloc()] and passed back through the 5th parameter. 388 ** To avoid memory leaks, the application should invoke [sqlite3_free()] 389 ** on error message strings returned through the 5th parameter of 390 ** sqlite3_exec() after the error message string is no longer needed. 391 ** ^If the 5th parameter to sqlite3_exec() is not NULL and no errors 392 ** occur, then sqlite3_exec() sets the pointer in its 5th parameter to 393 ** NULL before returning. 394 ** 395 ** ^If an sqlite3_exec() callback returns non-zero, the sqlite3_exec() 396 ** routine returns SQLITE_ABORT without invoking the callback again and 397 ** without running any subsequent SQL statements. 398 ** 399 ** ^The 2nd argument to the sqlite3_exec() callback function is the 400 ** number of columns in the result. ^The 3rd argument to the sqlite3_exec() 401 ** callback is an array of pointers to strings obtained as if from 402 ** [sqlite3_column_text()], one for each column. ^If an element of a 403 ** result row is NULL then the corresponding string pointer for the 404 ** sqlite3_exec() callback is a NULL pointer. ^The 4th argument to the 405 ** sqlite3_exec() callback is an array of pointers to strings where each 406 ** entry represents the name of corresponding result column as obtained 407 ** from [sqlite3_column_name()]. 408 ** 409 ** ^If the 2nd parameter to sqlite3_exec() is a NULL pointer, a pointer 410 ** to an empty string, or a pointer that contains only whitespace and/or 411 ** SQL comments, then no SQL statements are evaluated and the database 412 ** is not changed. 413 ** 414 ** Restrictions: 415 ** 416 ** <ul> 417 ** <li> The application must ensure that the 1st parameter to sqlite3_exec() 418 ** is a valid and open [database connection]. 419 ** <li> The application must not close the [database connection] specified by 420 ** the 1st parameter to sqlite3_exec() while sqlite3_exec() is running. 421 ** <li> The application must not modify the SQL statement text passed into 422 ** the 2nd parameter of sqlite3_exec() while sqlite3_exec() is running. 423 ** </ul> 424 */ 425 SQLITE_API int sqlite3_exec( 426 sqlite3*, /* An open database */ 427 const char *sql, /* SQL to be evaluated */ 428 int (*callback)(void*,int,char**,char**), /* Callback function */ 429 void *, /* 1st argument to callback */ 430 char **errmsg /* Error msg written here */ 431 ); 432 433 /* 434 ** CAPI3REF: Result Codes 435 ** KEYWORDS: {result code definitions} 436 ** 437 ** Many SQLite functions return an integer result code from the set shown 438 ** here in order to indicate success or failure. 439 ** 440 ** New error codes may be added in future versions of SQLite. 441 ** 442 ** See also: [extended result code definitions] 443 */ 444 #define SQLITE_OK 0 /* Successful result */ 445 /* beginning-of-error-codes */ 446 #define SQLITE_ERROR 1 /* Generic error */ 447 #define SQLITE_INTERNAL 2 /* Internal logic error in SQLite */ 448 #define SQLITE_PERM 3 /* Access permission denied */ 449 #define SQLITE_ABORT 4 /* Callback routine requested an abort */ 450 #define SQLITE_BUSY 5 /* The database file is locked */ 451 #define SQLITE_LOCKED 6 /* A table in the database is locked */ 452 #define SQLITE_NOMEM 7 /* A malloc() failed */ 453 #define SQLITE_READONLY 8 /* Attempt to write a readonly database */ 454 #define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/ 455 #define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */ 456 #define SQLITE_CORRUPT 11 /* The database disk image is malformed */ 457 #define SQLITE_NOTFOUND 12 /* Unknown opcode in sqlite3_file_control() */ 458 #define SQLITE_FULL 13 /* Insertion failed because database is full */ 459 #define SQLITE_CANTOPEN 14 /* Unable to open the database file */ 460 #define SQLITE_PROTOCOL 15 /* Database lock protocol error */ 461 #define SQLITE_EMPTY 16 /* Internal use only */ 462 #define SQLITE_SCHEMA 17 /* The database schema changed */ 463 #define SQLITE_TOOBIG 18 /* String or BLOB exceeds size limit */ 464 #define SQLITE_CONSTRAINT 19 /* Abort due to constraint violation */ 465 #define SQLITE_MISMATCH 20 /* Data type mismatch */ 466 #define SQLITE_MISUSE 21 /* Library used incorrectly */ 467 #define SQLITE_NOLFS 22 /* Uses OS features not supported on host */ 468 #define SQLITE_AUTH 23 /* Authorization denied */ 469 #define SQLITE_FORMAT 24 /* Not used */ 470 #define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */ 471 #define SQLITE_NOTADB 26 /* File opened that is not a database file */ 472 #define SQLITE_NOTICE 27 /* Notifications from sqlite3_log() */ 473 #define SQLITE_WARNING 28 /* Warnings from sqlite3_log() */ 474 #define SQLITE_ROW 100 /* sqlite3_step() has another row ready */ 475 #define SQLITE_DONE 101 /* sqlite3_step() has finished executing */ 476 /* end-of-error-codes */ 477 478 /* 479 ** CAPI3REF: Extended Result Codes 480 ** KEYWORDS: {extended result code definitions} 481 ** 482 ** In its default configuration, SQLite API routines return one of 30 integer 483 ** [result codes]. However, experience has shown that many of 484 ** these result codes are too coarse-grained. They do not provide as 485 ** much information about problems as programmers might like. In an effort to 486 ** address this, newer versions of SQLite (version 3.3.8 [dateof:3.3.8] 487 ** and later) include 488 ** support for additional result codes that provide more detailed information 489 ** about errors. These [extended result codes] are enabled or disabled 490 ** on a per database connection basis using the 491 ** [sqlite3_extended_result_codes()] API. Or, the extended code for 492 ** the most recent error can be obtained using 493 ** [sqlite3_extended_errcode()]. 494 */ 495 #define SQLITE_ERROR_MISSING_COLLSEQ (SQLITE_ERROR | (1<<8)) 496 #define SQLITE_ERROR_RETRY (SQLITE_ERROR | (2<<8)) 497 #define SQLITE_ERROR_SNAPSHOT (SQLITE_ERROR | (3<<8)) 498 #define SQLITE_IOERR_READ (SQLITE_IOERR | (1<<8)) 499 #define SQLITE_IOERR_SHORT_READ (SQLITE_IOERR | (2<<8)) 500 #define SQLITE_IOERR_WRITE (SQLITE_IOERR | (3<<8)) 501 #define SQLITE_IOERR_FSYNC (SQLITE_IOERR | (4<<8)) 502 #define SQLITE_IOERR_DIR_FSYNC (SQLITE_IOERR | (5<<8)) 503 #define SQLITE_IOERR_TRUNCATE (SQLITE_IOERR | (6<<8)) 504 #define SQLITE_IOERR_FSTAT (SQLITE_IOERR | (7<<8)) 505 #define SQLITE_IOERR_UNLOCK (SQLITE_IOERR | (8<<8)) 506 #define SQLITE_IOERR_RDLOCK (SQLITE_IOERR | (9<<8)) 507 #define SQLITE_IOERR_DELETE (SQLITE_IOERR | (10<<8)) 508 #define SQLITE_IOERR_BLOCKED (SQLITE_IOERR | (11<<8)) 509 #define SQLITE_IOERR_NOMEM (SQLITE_IOERR | (12<<8)) 510 #define SQLITE_IOERR_ACCESS (SQLITE_IOERR | (13<<8)) 511 #define SQLITE_IOERR_CHECKRESERVEDLOCK (SQLITE_IOERR | (14<<8)) 512 #define SQLITE_IOERR_LOCK (SQLITE_IOERR | (15<<8)) 513 #define SQLITE_IOERR_CLOSE (SQLITE_IOERR | (16<<8)) 514 #define SQLITE_IOERR_DIR_CLOSE (SQLITE_IOERR | (17<<8)) 515 #define SQLITE_IOERR_SHMOPEN (SQLITE_IOERR | (18<<8)) 516 #define SQLITE_IOERR_SHMSIZE (SQLITE_IOERR | (19<<8)) 517 #define SQLITE_IOERR_SHMLOCK (SQLITE_IOERR | (20<<8)) 518 #define SQLITE_IOERR_SHMMAP (SQLITE_IOERR | (21<<8)) 519 #define SQLITE_IOERR_SEEK (SQLITE_IOERR | (22<<8)) 520 #define SQLITE_IOERR_DELETE_NOENT (SQLITE_IOERR | (23<<8)) 521 #define SQLITE_IOERR_MMAP (SQLITE_IOERR | (24<<8)) 522 #define SQLITE_IOERR_GETTEMPPATH (SQLITE_IOERR | (25<<8)) 523 #define SQLITE_IOERR_CONVPATH (SQLITE_IOERR | (26<<8)) 524 #define SQLITE_IOERR_VNODE (SQLITE_IOERR | (27<<8)) 525 #define SQLITE_IOERR_AUTH (SQLITE_IOERR | (28<<8)) 526 #define SQLITE_IOERR_BEGIN_ATOMIC (SQLITE_IOERR | (29<<8)) 527 #define SQLITE_IOERR_COMMIT_ATOMIC (SQLITE_IOERR | (30<<8)) 528 #define SQLITE_IOERR_ROLLBACK_ATOMIC (SQLITE_IOERR | (31<<8)) 529 #define SQLITE_IOERR_DATA (SQLITE_IOERR | (32<<8)) 530 #define SQLITE_IOERR_CORRUPTFS (SQLITE_IOERR | (33<<8)) 531 #define SQLITE_IOERR_IN_PAGE (SQLITE_IOERR | (34<<8)) 532 #define SQLITE_LOCKED_SHAREDCACHE (SQLITE_LOCKED | (1<<8)) 533 #define SQLITE_LOCKED_VTAB (SQLITE_LOCKED | (2<<8)) 534 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8)) 535 #define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY | (2<<8)) 536 #define SQLITE_BUSY_TIMEOUT (SQLITE_BUSY | (3<<8)) 537 #define SQLITE_CANTOPEN_NOTEMPDIR (SQLITE_CANTOPEN | (1<<8)) 538 #define SQLITE_CANTOPEN_ISDIR (SQLITE_CANTOPEN | (2<<8)) 539 #define SQLITE_CANTOPEN_FULLPATH (SQLITE_CANTOPEN | (3<<8)) 540 #define SQLITE_CANTOPEN_CONVPATH (SQLITE_CANTOPEN | (4<<8)) 541 #define SQLITE_CANTOPEN_DIRTYWAL (SQLITE_CANTOPEN | (5<<8)) /* Not Used */ 542 #define SQLITE_CANTOPEN_SYMLINK (SQLITE_CANTOPEN | (6<<8)) 543 #define SQLITE_CORRUPT_VTAB (SQLITE_CORRUPT | (1<<8)) 544 #define SQLITE_CORRUPT_SEQUENCE (SQLITE_CORRUPT | (2<<8)) 545 #define SQLITE_CORRUPT_INDEX (SQLITE_CORRUPT | (3<<8)) 546 #define SQLITE_READONLY_RECOVERY (SQLITE_READONLY | (1<<8)) 547 #define SQLITE_READONLY_CANTLOCK (SQLITE_READONLY | (2<<8)) 548 #define SQLITE_READONLY_ROLLBACK (SQLITE_READONLY | (3<<8)) 549 #define SQLITE_READONLY_DBMOVED (SQLITE_READONLY | (4<<8)) 550 #define SQLITE_READONLY_CANTINIT (SQLITE_READONLY | (5<<8)) 551 #define SQLITE_READONLY_DIRECTORY (SQLITE_READONLY | (6<<8)) 552 #define SQLITE_ABORT_ROLLBACK (SQLITE_ABORT | (2<<8)) 553 #define SQLITE_CONSTRAINT_CHECK (SQLITE_CONSTRAINT | (1<<8)) 554 #define SQLITE_CONSTRAINT_COMMITHOOK (SQLITE_CONSTRAINT | (2<<8)) 555 #define SQLITE_CONSTRAINT_FOREIGNKEY (SQLITE_CONSTRAINT | (3<<8)) 556 #define SQLITE_CONSTRAINT_FUNCTION (SQLITE_CONSTRAINT | (4<<8)) 557 #define SQLITE_CONSTRAINT_NOTNULL (SQLITE_CONSTRAINT | (5<<8)) 558 #define SQLITE_CONSTRAINT_PRIMARYKEY (SQLITE_CONSTRAINT | (6<<8)) 559 #define SQLITE_CONSTRAINT_TRIGGER (SQLITE_CONSTRAINT | (7<<8)) 560 #define SQLITE_CONSTRAINT_UNIQUE (SQLITE_CONSTRAINT | (8<<8)) 561 #define SQLITE_CONSTRAINT_VTAB (SQLITE_CONSTRAINT | (9<<8)) 562 #define SQLITE_CONSTRAINT_ROWID (SQLITE_CONSTRAINT |(10<<8)) 563 #define SQLITE_CONSTRAINT_PINNED (SQLITE_CONSTRAINT |(11<<8)) 564 #define SQLITE_CONSTRAINT_DATATYPE (SQLITE_CONSTRAINT |(12<<8)) 565 #define SQLITE_NOTICE_RECOVER_WAL (SQLITE_NOTICE | (1<<8)) 566 #define SQLITE_NOTICE_RECOVER_ROLLBACK (SQLITE_NOTICE | (2<<8)) 567 #define SQLITE_NOTICE_RBU (SQLITE_NOTICE | (3<<8)) 568 #define SQLITE_WARNING_AUTOINDEX (SQLITE_WARNING | (1<<8)) 569 #define SQLITE_AUTH_USER (SQLITE_AUTH | (1<<8)) 570 #define SQLITE_OK_LOAD_PERMANENTLY (SQLITE_OK | (1<<8)) 571 #define SQLITE_OK_SYMLINK (SQLITE_OK | (2<<8)) /* internal use only */ 572 573 /* 574 ** CAPI3REF: Flags For File Open Operations 575 ** 576 ** These bit values are intended for use in the 577 ** 3rd parameter to the [sqlite3_open_v2()] interface and 578 ** in the 4th parameter to the [sqlite3_vfs.xOpen] method. 579 ** 580 ** Only those flags marked as "Ok for sqlite3_open_v2()" may be 581 ** used as the third argument to the [sqlite3_open_v2()] interface. 582 ** The other flags have historically been ignored by sqlite3_open_v2(), 583 ** though future versions of SQLite might change so that an error is 584 ** raised if any of the disallowed bits are passed into sqlite3_open_v2(). 585 ** Applications should not depend on the historical behavior. 586 ** 587 ** Note in particular that passing the SQLITE_OPEN_EXCLUSIVE flag into 588 ** [sqlite3_open_v2()] does *not* cause the underlying database file 589 ** to be opened using O_EXCL. Passing SQLITE_OPEN_EXCLUSIVE into 590 ** [sqlite3_open_v2()] has historically be a no-op and might become an 591 ** error in future versions of SQLite. 592 */ 593 #define SQLITE_OPEN_READONLY 0x00000001 /* Ok for sqlite3_open_v2() */ 594 #define SQLITE_OPEN_READWRITE 0x00000002 /* Ok for sqlite3_open_v2() */ 595 #define SQLITE_OPEN_CREATE 0x00000004 /* Ok for sqlite3_open_v2() */ 596 #define SQLITE_OPEN_DELETEONCLOSE 0x00000008 /* VFS only */ 597 #define SQLITE_OPEN_EXCLUSIVE 0x00000010 /* VFS only */ 598 #define SQLITE_OPEN_AUTOPROXY 0x00000020 /* VFS only */ 599 #define SQLITE_OPEN_URI 0x00000040 /* Ok for sqlite3_open_v2() */ 600 #define SQLITE_OPEN_MEMORY 0x00000080 /* Ok for sqlite3_open_v2() */ 601 #define SQLITE_OPEN_MAIN_DB 0x00000100 /* VFS only */ 602 #define SQLITE_OPEN_TEMP_DB 0x00000200 /* VFS only */ 603 #define SQLITE_OPEN_TRANSIENT_DB 0x00000400 /* VFS only */ 604 #define SQLITE_OPEN_MAIN_JOURNAL 0x00000800 /* VFS only */ 605 #define SQLITE_OPEN_TEMP_JOURNAL 0x00001000 /* VFS only */ 606 #define SQLITE_OPEN_SUBJOURNAL 0x00002000 /* VFS only */ 607 #define SQLITE_OPEN_SUPER_JOURNAL 0x00004000 /* VFS only */ 608 #define SQLITE_OPEN_NOMUTEX 0x00008000 /* Ok for sqlite3_open_v2() */ 609 #define SQLITE_OPEN_FULLMUTEX 0x00010000 /* Ok for sqlite3_open_v2() */ 610 #define SQLITE_OPEN_SHAREDCACHE 0x00020000 /* Ok for sqlite3_open_v2() */ 611 #define SQLITE_OPEN_PRIVATECACHE 0x00040000 /* Ok for sqlite3_open_v2() */ 612 #define SQLITE_OPEN_WAL 0x00080000 /* VFS only */ 613 #define SQLITE_OPEN_NOFOLLOW 0x01000000 /* Ok for sqlite3_open_v2() */ 614 #define SQLITE_OPEN_EXRESCODE 0x02000000 /* Extended result codes */ 615 616 /* Reserved: 0x00F00000 */ 617 /* Legacy compatibility: */ 618 #define SQLITE_OPEN_MASTER_JOURNAL 0x00004000 /* VFS only */ 619 620 621 /* 622 ** CAPI3REF: Device Characteristics 623 ** 624 ** The xDeviceCharacteristics method of the [sqlite3_io_methods] 625 ** object returns an integer which is a vector of these 626 ** bit values expressing I/O characteristics of the mass storage 627 ** device that holds the file that the [sqlite3_io_methods] 628 ** refers to. 629 ** 630 ** The SQLITE_IOCAP_ATOMIC property means that all writes of 631 ** any size are atomic. The SQLITE_IOCAP_ATOMICnnn values 632 ** mean that writes of blocks that are nnn bytes in size and 633 ** are aligned to an address which is an integer multiple of 634 ** nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means 635 ** that when data is appended to a file, the data is appended 636 ** first then the size of the file is extended, never the other 637 ** way around. The SQLITE_IOCAP_SEQUENTIAL property means that 638 ** information is written to disk in the same order as calls 639 ** to xWrite(). The SQLITE_IOCAP_POWERSAFE_OVERWRITE property means that 640 ** after reboot following a crash or power loss, the only bytes in a 641 ** file that were written at the application level might have changed 642 ** and that adjacent bytes, even bytes within the same sector are 643 ** guaranteed to be unchanged. The SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN 644 ** flag indicates that a file cannot be deleted when open. The 645 ** SQLITE_IOCAP_IMMUTABLE flag indicates that the file is on 646 ** read-only media and cannot be changed even by processes with 647 ** elevated privileges. 648 ** 649 ** The SQLITE_IOCAP_BATCH_ATOMIC property means that the underlying 650 ** filesystem supports doing multiple write operations atomically when those 651 ** write operations are bracketed by [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] and 652 ** [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE]. 653 */ 654 #define SQLITE_IOCAP_ATOMIC 0x00000001 655 #define SQLITE_IOCAP_ATOMIC512 0x00000002 656 #define SQLITE_IOCAP_ATOMIC1K 0x00000004 657 #define SQLITE_IOCAP_ATOMIC2K 0x00000008 658 #define SQLITE_IOCAP_ATOMIC4K 0x00000010 659 #define SQLITE_IOCAP_ATOMIC8K 0x00000020 660 #define SQLITE_IOCAP_ATOMIC16K 0x00000040 661 #define SQLITE_IOCAP_ATOMIC32K 0x00000080 662 #define SQLITE_IOCAP_ATOMIC64K 0x00000100 663 #define SQLITE_IOCAP_SAFE_APPEND 0x00000200 664 #define SQLITE_IOCAP_SEQUENTIAL 0x00000400 665 #define SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN 0x00000800 666 #define SQLITE_IOCAP_POWERSAFE_OVERWRITE 0x00001000 667 #define SQLITE_IOCAP_IMMUTABLE 0x00002000 668 #define SQLITE_IOCAP_BATCH_ATOMIC 0x00004000 669 670 /* 671 ** CAPI3REF: File Locking Levels 672 ** 673 ** SQLite uses one of these integer values as the second 674 ** argument to calls it makes to the xLock() and xUnlock() methods 675 ** of an [sqlite3_io_methods] object. These values are ordered from 676 ** lest restrictive to most restrictive. 677 ** 678 ** The argument to xLock() is always SHARED or higher. The argument to 679 ** xUnlock is either SHARED or NONE. 680 */ 681 #define SQLITE_LOCK_NONE 0 /* xUnlock() only */ 682 #define SQLITE_LOCK_SHARED 1 /* xLock() or xUnlock() */ 683 #define SQLITE_LOCK_RESERVED 2 /* xLock() only */ 684 #define SQLITE_LOCK_PENDING 3 /* xLock() only */ 685 #define SQLITE_LOCK_EXCLUSIVE 4 /* xLock() only */ 686 687 /* 688 ** CAPI3REF: Synchronization Type Flags 689 ** 690 ** When SQLite invokes the xSync() method of an 691 ** [sqlite3_io_methods] object it uses a combination of 692 ** these integer values as the second argument. 693 ** 694 ** When the SQLITE_SYNC_DATAONLY flag is used, it means that the 695 ** sync operation only needs to flush data to mass storage. Inode 696 ** information need not be flushed. If the lower four bits of the flag 697 ** equal SQLITE_SYNC_NORMAL, that means to use normal fsync() semantics. 698 ** If the lower four bits equal SQLITE_SYNC_FULL, that means 699 ** to use Mac OS X style fullsync instead of fsync(). 700 ** 701 ** Do not confuse the SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags 702 ** with the [PRAGMA synchronous]=NORMAL and [PRAGMA synchronous]=FULL 703 ** settings. The [synchronous pragma] determines when calls to the 704 ** xSync VFS method occur and applies uniformly across all platforms. 705 ** The SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags determine how 706 ** energetic or rigorous or forceful the sync operations are and 707 ** only make a difference on Mac OSX for the default SQLite code. 708 ** (Third-party VFS implementations might also make the distinction 709 ** between SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL, but among the 710 ** operating systems natively supported by SQLite, only Mac OSX 711 ** cares about the difference.) 712 */ 713 #define SQLITE_SYNC_NORMAL 0x00002 714 #define SQLITE_SYNC_FULL 0x00003 715 #define SQLITE_SYNC_DATAONLY 0x00010 716 717 /* 718 ** CAPI3REF: OS Interface Open File Handle 719 ** 720 ** An [sqlite3_file] object represents an open file in the 721 ** [sqlite3_vfs | OS interface layer]. Individual OS interface 722 ** implementations will 723 ** want to subclass this object by appending additional fields 724 ** for their own use. The pMethods entry is a pointer to an 725 ** [sqlite3_io_methods] object that defines methods for performing 726 ** I/O operations on the open file. 727 */ 728 typedef struct sqlite3_file sqlite3_file; 729 struct sqlite3_file { 730 const struct sqlite3_io_methods *pMethods; /* Methods for an open file */ 731 }; 732 733 /* 734 ** CAPI3REF: OS Interface File Virtual Methods Object 735 ** 736 ** Every file opened by the [sqlite3_vfs.xOpen] method populates an 737 ** [sqlite3_file] object (or, more commonly, a subclass of the 738 ** [sqlite3_file] object) with a pointer to an instance of this object. 739 ** This object defines the methods used to perform various operations 740 ** against the open file represented by the [sqlite3_file] object. 741 ** 742 ** If the [sqlite3_vfs.xOpen] method sets the sqlite3_file.pMethods element 743 ** to a non-NULL pointer, then the sqlite3_io_methods.xClose method 744 ** may be invoked even if the [sqlite3_vfs.xOpen] reported that it failed. The 745 ** only way to prevent a call to xClose following a failed [sqlite3_vfs.xOpen] 746 ** is for the [sqlite3_vfs.xOpen] to set the sqlite3_file.pMethods element 747 ** to NULL. 748 ** 749 ** The flags argument to xSync may be one of [SQLITE_SYNC_NORMAL] or 750 ** [SQLITE_SYNC_FULL]. The first choice is the normal fsync(). 751 ** The second choice is a Mac OS X style fullsync. The [SQLITE_SYNC_DATAONLY] 752 ** flag may be ORed in to indicate that only the data of the file 753 ** and not its inode needs to be synced. 754 ** 755 ** The integer values to xLock() and xUnlock() are one of 756 ** <ul> 757 ** <li> [SQLITE_LOCK_NONE], 758 ** <li> [SQLITE_LOCK_SHARED], 759 ** <li> [SQLITE_LOCK_RESERVED], 760 ** <li> [SQLITE_LOCK_PENDING], or 761 ** <li> [SQLITE_LOCK_EXCLUSIVE]. 762 ** </ul> 763 ** xLock() upgrades the database file lock. In other words, xLock() moves the 764 ** database file lock in the direction NONE toward EXCLUSIVE. The argument to 765 ** xLock() is always on of SHARED, RESERVED, PENDING, or EXCLUSIVE, never 766 ** SQLITE_LOCK_NONE. If the database file lock is already at or above the 767 ** requested lock, then the call to xLock() is a no-op. 768 ** xUnlock() downgrades the database file lock to either SHARED or NONE. 769 * If the lock is already at or below the requested lock state, then the call 770 ** to xUnlock() is a no-op. 771 ** The xCheckReservedLock() method checks whether any database connection, 772 ** either in this process or in some other process, is holding a RESERVED, 773 ** PENDING, or EXCLUSIVE lock on the file. It returns true 774 ** if such a lock exists and false otherwise. 775 ** 776 ** The xFileControl() method is a generic interface that allows custom 777 ** VFS implementations to directly control an open file using the 778 ** [sqlite3_file_control()] interface. The second "op" argument is an 779 ** integer opcode. The third argument is a generic pointer intended to 780 ** point to a structure that may contain arguments or space in which to 781 ** write return values. Potential uses for xFileControl() might be 782 ** functions to enable blocking locks with timeouts, to change the 783 ** locking strategy (for example to use dot-file locks), to inquire 784 ** about the status of a lock, or to break stale locks. The SQLite 785 ** core reserves all opcodes less than 100 for its own use. 786 ** A [file control opcodes | list of opcodes] less than 100 is available. 787 ** Applications that define a custom xFileControl method should use opcodes 788 ** greater than 100 to avoid conflicts. VFS implementations should 789 ** return [SQLITE_NOTFOUND] for file control opcodes that they do not 790 ** recognize. 791 ** 792 ** The xSectorSize() method returns the sector size of the 793 ** device that underlies the file. The sector size is the 794 ** minimum write that can be performed without disturbing 795 ** other bytes in the file. The xDeviceCharacteristics() 796 ** method returns a bit vector describing behaviors of the 797 ** underlying device: 798 ** 799 ** <ul> 800 ** <li> [SQLITE_IOCAP_ATOMIC] 801 ** <li> [SQLITE_IOCAP_ATOMIC512] 802 ** <li> [SQLITE_IOCAP_ATOMIC1K] 803 ** <li> [SQLITE_IOCAP_ATOMIC2K] 804 ** <li> [SQLITE_IOCAP_ATOMIC4K] 805 ** <li> [SQLITE_IOCAP_ATOMIC8K] 806 ** <li> [SQLITE_IOCAP_ATOMIC16K] 807 ** <li> [SQLITE_IOCAP_ATOMIC32K] 808 ** <li> [SQLITE_IOCAP_ATOMIC64K] 809 ** <li> [SQLITE_IOCAP_SAFE_APPEND] 810 ** <li> [SQLITE_IOCAP_SEQUENTIAL] 811 ** <li> [SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN] 812 ** <li> [SQLITE_IOCAP_POWERSAFE_OVERWRITE] 813 ** <li> [SQLITE_IOCAP_IMMUTABLE] 814 ** <li> [SQLITE_IOCAP_BATCH_ATOMIC] 815 ** </ul> 816 ** 817 ** The SQLITE_IOCAP_ATOMIC property means that all writes of 818 ** any size are atomic. The SQLITE_IOCAP_ATOMICnnn values 819 ** mean that writes of blocks that are nnn bytes in size and 820 ** are aligned to an address which is an integer multiple of 821 ** nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means 822 ** that when data is appended to a file, the data is appended 823 ** first then the size of the file is extended, never the other 824 ** way around. The SQLITE_IOCAP_SEQUENTIAL property means that 825 ** information is written to disk in the same order as calls 826 ** to xWrite(). 827 ** 828 ** If xRead() returns SQLITE_IOERR_SHORT_READ it must also fill 829 ** in the unread portions of the buffer with zeros. A VFS that 830 ** fails to zero-fill short reads might seem to work. However, 831 ** failure to zero-fill short reads will eventually lead to 832 ** database corruption. 833 */ 834 typedef struct sqlite3_io_methods sqlite3_io_methods; 835 struct sqlite3_io_methods { 836 int iVersion; 837 int (*xClose)(sqlite3_file*); 838 int (*xRead)(sqlite3_file*, void*, int iAmt, sqlite3_int64 iOfst); 839 int (*xWrite)(sqlite3_file*, const void*, int iAmt, sqlite3_int64 iOfst); 840 int (*xTruncate)(sqlite3_file*, sqlite3_int64 size); 841 int (*xSync)(sqlite3_file*, int flags); 842 int (*xFileSize)(sqlite3_file*, sqlite3_int64 *pSize); 843 int (*xLock)(sqlite3_file*, int); 844 int (*xUnlock)(sqlite3_file*, int); 845 int (*xCheckReservedLock)(sqlite3_file*, int *pResOut); 846 int (*xFileControl)(sqlite3_file*, int op, void *pArg); 847 int (*xSectorSize)(sqlite3_file*); 848 int (*xDeviceCharacteristics)(sqlite3_file*); 849 /* Methods above are valid for version 1 */ 850 int (*xShmMap)(sqlite3_file*, int iPg, int pgsz, int, void volatile**); 851 int (*xShmLock)(sqlite3_file*, int offset, int n, int flags); 852 void (*xShmBarrier)(sqlite3_file*); 853 int (*xShmUnmap)(sqlite3_file*, int deleteFlag); 854 /* Methods above are valid for version 2 */ 855 int (*xFetch)(sqlite3_file*, sqlite3_int64 iOfst, int iAmt, void **pp); 856 int (*xUnfetch)(sqlite3_file*, sqlite3_int64 iOfst, void *p); 857 /* Methods above are valid for version 3 */ 858 /* Additional methods may be added in future releases */ 859 }; 860 861 /* 862 ** CAPI3REF: Standard File Control Opcodes 863 ** KEYWORDS: {file control opcodes} {file control opcode} 864 ** 865 ** These integer constants are opcodes for the xFileControl method 866 ** of the [sqlite3_io_methods] object and for the [sqlite3_file_control()] 867 ** interface. 868 ** 869 ** <ul> 870 ** <li>[[SQLITE_FCNTL_LOCKSTATE]] 871 ** The [SQLITE_FCNTL_LOCKSTATE] opcode is used for debugging. This 872 ** opcode causes the xFileControl method to write the current state of 873 ** the lock (one of [SQLITE_LOCK_NONE], [SQLITE_LOCK_SHARED], 874 ** [SQLITE_LOCK_RESERVED], [SQLITE_LOCK_PENDING], or [SQLITE_LOCK_EXCLUSIVE]) 875 ** into an integer that the pArg argument points to. 876 ** This capability is only available if SQLite is compiled with [SQLITE_DEBUG]. 877 ** 878 ** <li>[[SQLITE_FCNTL_SIZE_HINT]] 879 ** The [SQLITE_FCNTL_SIZE_HINT] opcode is used by SQLite to give the VFS 880 ** layer a hint of how large the database file will grow to be during the 881 ** current transaction. This hint is not guaranteed to be accurate but it 882 ** is often close. The underlying VFS might choose to preallocate database 883 ** file space based on this hint in order to help writes to the database 884 ** file run faster. 885 ** 886 ** <li>[[SQLITE_FCNTL_SIZE_LIMIT]] 887 ** The [SQLITE_FCNTL_SIZE_LIMIT] opcode is used by in-memory VFS that 888 ** implements [sqlite3_deserialize()] to set an upper bound on the size 889 ** of the in-memory database. The argument is a pointer to a [sqlite3_int64]. 890 ** If the integer pointed to is negative, then it is filled in with the 891 ** current limit. Otherwise the limit is set to the larger of the value 892 ** of the integer pointed to and the current database size. The integer 893 ** pointed to is set to the new limit. 894 ** 895 ** <li>[[SQLITE_FCNTL_CHUNK_SIZE]] 896 ** The [SQLITE_FCNTL_CHUNK_SIZE] opcode is used to request that the VFS 897 ** extends and truncates the database file in chunks of a size specified 898 ** by the user. The fourth argument to [sqlite3_file_control()] should 899 ** point to an integer (type int) containing the new chunk-size to use 900 ** for the nominated database. Allocating database file space in large 901 ** chunks (say 1MB at a time), may reduce file-system fragmentation and 902 ** improve performance on some systems. 903 ** 904 ** <li>[[SQLITE_FCNTL_FILE_POINTER]] 905 ** The [SQLITE_FCNTL_FILE_POINTER] opcode is used to obtain a pointer 906 ** to the [sqlite3_file] object associated with a particular database 907 ** connection. See also [SQLITE_FCNTL_JOURNAL_POINTER]. 908 ** 909 ** <li>[[SQLITE_FCNTL_JOURNAL_POINTER]] 910 ** The [SQLITE_FCNTL_JOURNAL_POINTER] opcode is used to obtain a pointer 911 ** to the [sqlite3_file] object associated with the journal file (either 912 ** the [rollback journal] or the [write-ahead log]) for a particular database 913 ** connection. See also [SQLITE_FCNTL_FILE_POINTER]. 914 ** 915 ** <li>[[SQLITE_FCNTL_SYNC_OMITTED]] 916 ** No longer in use. 917 ** 918 ** <li>[[SQLITE_FCNTL_SYNC]] 919 ** The [SQLITE_FCNTL_SYNC] opcode is generated internally by SQLite and 920 ** sent to the VFS immediately before the xSync method is invoked on a 921 ** database file descriptor. Or, if the xSync method is not invoked 922 ** because the user has configured SQLite with 923 ** [PRAGMA synchronous | PRAGMA synchronous=OFF] it is invoked in place 924 ** of the xSync method. In most cases, the pointer argument passed with 925 ** this file-control is NULL. However, if the database file is being synced 926 ** as part of a multi-database commit, the argument points to a nul-terminated 927 ** string containing the transactions super-journal file name. VFSes that 928 ** do not need this signal should silently ignore this opcode. Applications 929 ** should not call [sqlite3_file_control()] with this opcode as doing so may 930 ** disrupt the operation of the specialized VFSes that do require it. 931 ** 932 ** <li>[[SQLITE_FCNTL_COMMIT_PHASETWO]] 933 ** The [SQLITE_FCNTL_COMMIT_PHASETWO] opcode is generated internally by SQLite 934 ** and sent to the VFS after a transaction has been committed immediately 935 ** but before the database is unlocked. VFSes that do not need this signal 936 ** should silently ignore this opcode. Applications should not call 937 ** [sqlite3_file_control()] with this opcode as doing so may disrupt the 938 ** operation of the specialized VFSes that do require it. 939 ** 940 ** <li>[[SQLITE_FCNTL_WIN32_AV_RETRY]] 941 ** ^The [SQLITE_FCNTL_WIN32_AV_RETRY] opcode is used to configure automatic 942 ** retry counts and intervals for certain disk I/O operations for the 943 ** windows [VFS] in order to provide robustness in the presence of 944 ** anti-virus programs. By default, the windows VFS will retry file read, 945 ** file write, and file delete operations up to 10 times, with a delay 946 ** of 25 milliseconds before the first retry and with the delay increasing 947 ** by an additional 25 milliseconds with each subsequent retry. This 948 ** opcode allows these two values (10 retries and 25 milliseconds of delay) 949 ** to be adjusted. The values are changed for all database connections 950 ** within the same process. The argument is a pointer to an array of two 951 ** integers where the first integer is the new retry count and the second 952 ** integer is the delay. If either integer is negative, then the setting 953 ** is not changed but instead the prior value of that setting is written 954 ** into the array entry, allowing the current retry settings to be 955 ** interrogated. The zDbName parameter is ignored. 956 ** 957 ** <li>[[SQLITE_FCNTL_PERSIST_WAL]] 958 ** ^The [SQLITE_FCNTL_PERSIST_WAL] opcode is used to set or query the 959 ** persistent [WAL | Write Ahead Log] setting. By default, the auxiliary 960 ** write ahead log ([WAL file]) and shared memory 961 ** files used for transaction control 962 ** are automatically deleted when the latest connection to the database 963 ** closes. Setting persistent WAL mode causes those files to persist after 964 ** close. Persisting the files is useful when other processes that do not 965 ** have write permission on the directory containing the database file want 966 ** to read the database file, as the WAL and shared memory files must exist 967 ** in order for the database to be readable. The fourth parameter to 968 ** [sqlite3_file_control()] for this opcode should be a pointer to an integer. 969 ** That integer is 0 to disable persistent WAL mode or 1 to enable persistent 970 ** WAL mode. If the integer is -1, then it is overwritten with the current 971 ** WAL persistence setting. 972 ** 973 ** <li>[[SQLITE_FCNTL_POWERSAFE_OVERWRITE]] 974 ** ^The [SQLITE_FCNTL_POWERSAFE_OVERWRITE] opcode is used to set or query the 975 ** persistent "powersafe-overwrite" or "PSOW" setting. The PSOW setting 976 ** determines the [SQLITE_IOCAP_POWERSAFE_OVERWRITE] bit of the 977 ** xDeviceCharacteristics methods. The fourth parameter to 978 ** [sqlite3_file_control()] for this opcode should be a pointer to an integer. 979 ** That integer is 0 to disable zero-damage mode or 1 to enable zero-damage 980 ** mode. If the integer is -1, then it is overwritten with the current 981 ** zero-damage mode setting. 982 ** 983 ** <li>[[SQLITE_FCNTL_OVERWRITE]] 984 ** ^The [SQLITE_FCNTL_OVERWRITE] opcode is invoked by SQLite after opening 985 ** a write transaction to indicate that, unless it is rolled back for some 986 ** reason, the entire database file will be overwritten by the current 987 ** transaction. This is used by VACUUM operations. 988 ** 989 ** <li>[[SQLITE_FCNTL_VFSNAME]] 990 ** ^The [SQLITE_FCNTL_VFSNAME] opcode can be used to obtain the names of 991 ** all [VFSes] in the VFS stack. The names are of all VFS shims and the 992 ** final bottom-level VFS are written into memory obtained from 993 ** [sqlite3_malloc()] and the result is stored in the char* variable 994 ** that the fourth parameter of [sqlite3_file_control()] points to. 995 ** The caller is responsible for freeing the memory when done. As with 996 ** all file-control actions, there is no guarantee that this will actually 997 ** do anything. Callers should initialize the char* variable to a NULL 998 ** pointer in case this file-control is not implemented. This file-control 999 ** is intended for diagnostic use only. 1000 ** 1001 ** <li>[[SQLITE_FCNTL_VFS_POINTER]] 1002 ** ^The [SQLITE_FCNTL_VFS_POINTER] opcode finds a pointer to the top-level 1003 ** [VFSes] currently in use. ^(The argument X in 1004 ** sqlite3_file_control(db,SQLITE_FCNTL_VFS_POINTER,X) must be 1005 ** of type "[sqlite3_vfs] **". This opcodes will set *X 1006 ** to a pointer to the top-level VFS.)^ 1007 ** ^When there are multiple VFS shims in the stack, this opcode finds the 1008 ** upper-most shim only. 1009 ** 1010 ** <li>[[SQLITE_FCNTL_PRAGMA]] 1011 ** ^Whenever a [PRAGMA] statement is parsed, an [SQLITE_FCNTL_PRAGMA] 1012 ** file control is sent to the open [sqlite3_file] object corresponding 1013 ** to the database file to which the pragma statement refers. ^The argument 1014 ** to the [SQLITE_FCNTL_PRAGMA] file control is an array of 1015 ** pointers to strings (char**) in which the second element of the array 1016 ** is the name of the pragma and the third element is the argument to the 1017 ** pragma or NULL if the pragma has no argument. ^The handler for an 1018 ** [SQLITE_FCNTL_PRAGMA] file control can optionally make the first element 1019 ** of the char** argument point to a string obtained from [sqlite3_mprintf()] 1020 ** or the equivalent and that string will become the result of the pragma or 1021 ** the error message if the pragma fails. ^If the 1022 ** [SQLITE_FCNTL_PRAGMA] file control returns [SQLITE_NOTFOUND], then normal 1023 ** [PRAGMA] processing continues. ^If the [SQLITE_FCNTL_PRAGMA] 1024 ** file control returns [SQLITE_OK], then the parser assumes that the 1025 ** VFS has handled the PRAGMA itself and the parser generates a no-op 1026 ** prepared statement if result string is NULL, or that returns a copy 1027 ** of the result string if the string is non-NULL. 1028 ** ^If the [SQLITE_FCNTL_PRAGMA] file control returns 1029 ** any result code other than [SQLITE_OK] or [SQLITE_NOTFOUND], that means 1030 ** that the VFS encountered an error while handling the [PRAGMA] and the 1031 ** compilation of the PRAGMA fails with an error. ^The [SQLITE_FCNTL_PRAGMA] 1032 ** file control occurs at the beginning of pragma statement analysis and so 1033 ** it is able to override built-in [PRAGMA] statements. 1034 ** 1035 ** <li>[[SQLITE_FCNTL_BUSYHANDLER]] 1036 ** ^The [SQLITE_FCNTL_BUSYHANDLER] 1037 ** file-control may be invoked by SQLite on the database file handle 1038 ** shortly after it is opened in order to provide a custom VFS with access 1039 ** to the connection's busy-handler callback. The argument is of type (void**) 1040 ** - an array of two (void *) values. The first (void *) actually points 1041 ** to a function of type (int (*)(void *)). In order to invoke the connection's 1042 ** busy-handler, this function should be invoked with the second (void *) in 1043 ** the array as the only argument. If it returns non-zero, then the operation 1044 ** should be retried. If it returns zero, the custom VFS should abandon the 1045 ** current operation. 1046 ** 1047 ** <li>[[SQLITE_FCNTL_TEMPFILENAME]] 1048 ** ^Applications can invoke the [SQLITE_FCNTL_TEMPFILENAME] file-control 1049 ** to have SQLite generate a 1050 ** temporary filename using the same algorithm that is followed to generate 1051 ** temporary filenames for TEMP tables and other internal uses. The 1052 ** argument should be a char** which will be filled with the filename 1053 ** written into memory obtained from [sqlite3_malloc()]. The caller should 1054 ** invoke [sqlite3_free()] on the result to avoid a memory leak. 1055 ** 1056 ** <li>[[SQLITE_FCNTL_MMAP_SIZE]] 1057 ** The [SQLITE_FCNTL_MMAP_SIZE] file control is used to query or set the 1058 ** maximum number of bytes that will be used for memory-mapped I/O. 1059 ** The argument is a pointer to a value of type sqlite3_int64 that 1060 ** is an advisory maximum number of bytes in the file to memory map. The 1061 ** pointer is overwritten with the old value. The limit is not changed if 1062 ** the value originally pointed to is negative, and so the current limit 1063 ** can be queried by passing in a pointer to a negative number. This 1064 ** file-control is used internally to implement [PRAGMA mmap_size]. 1065 ** 1066 ** <li>[[SQLITE_FCNTL_TRACE]] 1067 ** The [SQLITE_FCNTL_TRACE] file control provides advisory information 1068 ** to the VFS about what the higher layers of the SQLite stack are doing. 1069 ** This file control is used by some VFS activity tracing [shims]. 1070 ** The argument is a zero-terminated string. Higher layers in the 1071 ** SQLite stack may generate instances of this file control if 1072 ** the [SQLITE_USE_FCNTL_TRACE] compile-time option is enabled. 1073 ** 1074 ** <li>[[SQLITE_FCNTL_HAS_MOVED]] 1075 ** The [SQLITE_FCNTL_HAS_MOVED] file control interprets its argument as a 1076 ** pointer to an integer and it writes a boolean into that integer depending 1077 ** on whether or not the file has been renamed, moved, or deleted since it 1078 ** was first opened. 1079 ** 1080 ** <li>[[SQLITE_FCNTL_WIN32_GET_HANDLE]] 1081 ** The [SQLITE_FCNTL_WIN32_GET_HANDLE] opcode can be used to obtain the 1082 ** underlying native file handle associated with a file handle. This file 1083 ** control interprets its argument as a pointer to a native file handle and 1084 ** writes the resulting value there. 1085 ** 1086 ** <li>[[SQLITE_FCNTL_WIN32_SET_HANDLE]] 1087 ** The [SQLITE_FCNTL_WIN32_SET_HANDLE] opcode is used for debugging. This 1088 ** opcode causes the xFileControl method to swap the file handle with the one 1089 ** pointed to by the pArg argument. This capability is used during testing 1090 ** and only needs to be supported when SQLITE_TEST is defined. 1091 ** 1092 ** <li>[[SQLITE_FCNTL_WAL_BLOCK]] 1093 ** The [SQLITE_FCNTL_WAL_BLOCK] is a signal to the VFS layer that it might 1094 ** be advantageous to block on the next WAL lock if the lock is not immediately 1095 ** available. The WAL subsystem issues this signal during rare 1096 ** circumstances in order to fix a problem with priority inversion. 1097 ** Applications should <em>not</em> use this file-control. 1098 ** 1099 ** <li>[[SQLITE_FCNTL_ZIPVFS]] 1100 ** The [SQLITE_FCNTL_ZIPVFS] opcode is implemented by zipvfs only. All other 1101 ** VFS should return SQLITE_NOTFOUND for this opcode. 1102 ** 1103 ** <li>[[SQLITE_FCNTL_RBU]] 1104 ** The [SQLITE_FCNTL_RBU] opcode is implemented by the special VFS used by 1105 ** the RBU extension only. All other VFS should return SQLITE_NOTFOUND for 1106 ** this opcode. 1107 ** 1108 ** <li>[[SQLITE_FCNTL_BEGIN_ATOMIC_WRITE]] 1109 ** If the [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] opcode returns SQLITE_OK, then 1110 ** the file descriptor is placed in "batch write mode", which 1111 ** means all subsequent write operations will be deferred and done 1112 ** atomically at the next [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE]. Systems 1113 ** that do not support batch atomic writes will return SQLITE_NOTFOUND. 1114 ** ^Following a successful SQLITE_FCNTL_BEGIN_ATOMIC_WRITE and prior to 1115 ** the closing [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE] or 1116 ** [SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE], SQLite will make 1117 ** no VFS interface calls on the same [sqlite3_file] file descriptor 1118 ** except for calls to the xWrite method and the xFileControl method 1119 ** with [SQLITE_FCNTL_SIZE_HINT]. 1120 ** 1121 ** <li>[[SQLITE_FCNTL_COMMIT_ATOMIC_WRITE]] 1122 ** The [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE] opcode causes all write 1123 ** operations since the previous successful call to 1124 ** [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] to be performed atomically. 1125 ** This file control returns [SQLITE_OK] if and only if the writes were 1126 ** all performed successfully and have been committed to persistent storage. 1127 ** ^Regardless of whether or not it is successful, this file control takes 1128 ** the file descriptor out of batch write mode so that all subsequent 1129 ** write operations are independent. 1130 ** ^SQLite will never invoke SQLITE_FCNTL_COMMIT_ATOMIC_WRITE without 1131 ** a prior successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE]. 1132 ** 1133 ** <li>[[SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE]] 1134 ** The [SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE] opcode causes all write 1135 ** operations since the previous successful call to 1136 ** [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] to be rolled back. 1137 ** ^This file control takes the file descriptor out of batch write mode 1138 ** so that all subsequent write operations are independent. 1139 ** ^SQLite will never invoke SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE without 1140 ** a prior successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE]. 1141 ** 1142 ** <li>[[SQLITE_FCNTL_LOCK_TIMEOUT]] 1143 ** The [SQLITE_FCNTL_LOCK_TIMEOUT] opcode is used to configure a VFS 1144 ** to block for up to M milliseconds before failing when attempting to 1145 ** obtain a file lock using the xLock or xShmLock methods of the VFS. 1146 ** The parameter is a pointer to a 32-bit signed integer that contains 1147 ** the value that M is to be set to. Before returning, the 32-bit signed 1148 ** integer is overwritten with the previous value of M. 1149 ** 1150 ** <li>[[SQLITE_FCNTL_DATA_VERSION]] 1151 ** The [SQLITE_FCNTL_DATA_VERSION] opcode is used to detect changes to 1152 ** a database file. The argument is a pointer to a 32-bit unsigned integer. 1153 ** The "data version" for the pager is written into the pointer. The 1154 ** "data version" changes whenever any change occurs to the corresponding 1155 ** database file, either through SQL statements on the same database 1156 ** connection or through transactions committed by separate database 1157 ** connections possibly in other processes. The [sqlite3_total_changes()] 1158 ** interface can be used to find if any database on the connection has changed, 1159 ** but that interface responds to changes on TEMP as well as MAIN and does 1160 ** not provide a mechanism to detect changes to MAIN only. Also, the 1161 ** [sqlite3_total_changes()] interface responds to internal changes only and 1162 ** omits changes made by other database connections. The 1163 ** [PRAGMA data_version] command provides a mechanism to detect changes to 1164 ** a single attached database that occur due to other database connections, 1165 ** but omits changes implemented by the database connection on which it is 1166 ** called. This file control is the only mechanism to detect changes that 1167 ** happen either internally or externally and that are associated with 1168 ** a particular attached database. 1169 ** 1170 ** <li>[[SQLITE_FCNTL_CKPT_START]] 1171 ** The [SQLITE_FCNTL_CKPT_START] opcode is invoked from within a checkpoint 1172 ** in wal mode before the client starts to copy pages from the wal 1173 ** file to the database file. 1174 ** 1175 ** <li>[[SQLITE_FCNTL_CKPT_DONE]] 1176 ** The [SQLITE_FCNTL_CKPT_DONE] opcode is invoked from within a checkpoint 1177 ** in wal mode after the client has finished copying pages from the wal 1178 ** file to the database file, but before the *-shm file is updated to 1179 ** record the fact that the pages have been checkpointed. 1180 ** 1181 ** <li>[[SQLITE_FCNTL_EXTERNAL_READER]] 1182 ** The EXPERIMENTAL [SQLITE_FCNTL_EXTERNAL_READER] opcode is used to detect 1183 ** whether or not there is a database client in another process with a wal-mode 1184 ** transaction open on the database or not. It is only available on unix.The 1185 ** (void*) argument passed with this file-control should be a pointer to a 1186 ** value of type (int). The integer value is set to 1 if the database is a wal 1187 ** mode database and there exists at least one client in another process that 1188 ** currently has an SQL transaction open on the database. It is set to 0 if 1189 ** the database is not a wal-mode db, or if there is no such connection in any 1190 ** other process. This opcode cannot be used to detect transactions opened 1191 ** by clients within the current process, only within other processes. 1192 ** 1193 ** <li>[[SQLITE_FCNTL_CKSM_FILE]] 1194 ** The [SQLITE_FCNTL_CKSM_FILE] opcode is for use internally by the 1195 ** [checksum VFS shim] only. 1196 ** 1197 ** <li>[[SQLITE_FCNTL_RESET_CACHE]] 1198 ** If there is currently no transaction open on the database, and the 1199 ** database is not a temp db, then the [SQLITE_FCNTL_RESET_CACHE] file-control 1200 ** purges the contents of the in-memory page cache. If there is an open 1201 ** transaction, or if the db is a temp-db, this opcode is a no-op, not an error. 1202 ** </ul> 1203 */ 1204 #define SQLITE_FCNTL_LOCKSTATE 1 1205 #define SQLITE_FCNTL_GET_LOCKPROXYFILE 2 1206 #define SQLITE_FCNTL_SET_LOCKPROXYFILE 3 1207 #define SQLITE_FCNTL_LAST_ERRNO 4 1208 #define SQLITE_FCNTL_SIZE_HINT 5 1209 #define SQLITE_FCNTL_CHUNK_SIZE 6 1210 #define SQLITE_FCNTL_FILE_POINTER 7 1211 #define SQLITE_FCNTL_SYNC_OMITTED 8 1212 #define SQLITE_FCNTL_WIN32_AV_RETRY 9 1213 #define SQLITE_FCNTL_PERSIST_WAL 10 1214 #define SQLITE_FCNTL_OVERWRITE 11 1215 #define SQLITE_FCNTL_VFSNAME 12 1216 #define SQLITE_FCNTL_POWERSAFE_OVERWRITE 13 1217 #define SQLITE_FCNTL_PRAGMA 14 1218 #define SQLITE_FCNTL_BUSYHANDLER 15 1219 #define SQLITE_FCNTL_TEMPFILENAME 16 1220 #define SQLITE_FCNTL_MMAP_SIZE 18 1221 #define SQLITE_FCNTL_TRACE 19 1222 #define SQLITE_FCNTL_HAS_MOVED 20 1223 #define SQLITE_FCNTL_SYNC 21 1224 #define SQLITE_FCNTL_COMMIT_PHASETWO 22 1225 #define SQLITE_FCNTL_WIN32_SET_HANDLE 23 1226 #define SQLITE_FCNTL_WAL_BLOCK 24 1227 #define SQLITE_FCNTL_ZIPVFS 25 1228 #define SQLITE_FCNTL_RBU 26 1229 #define SQLITE_FCNTL_VFS_POINTER 27 1230 #define SQLITE_FCNTL_JOURNAL_POINTER 28 1231 #define SQLITE_FCNTL_WIN32_GET_HANDLE 29 1232 #define SQLITE_FCNTL_PDB 30 1233 #define SQLITE_FCNTL_BEGIN_ATOMIC_WRITE 31 1234 #define SQLITE_FCNTL_COMMIT_ATOMIC_WRITE 32 1235 #define SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE 33 1236 #define SQLITE_FCNTL_LOCK_TIMEOUT 34 1237 #define SQLITE_FCNTL_DATA_VERSION 35 1238 #define SQLITE_FCNTL_SIZE_LIMIT 36 1239 #define SQLITE_FCNTL_CKPT_DONE 37 1240 #define SQLITE_FCNTL_RESERVE_BYTES 38 1241 #define SQLITE_FCNTL_CKPT_START 39 1242 #define SQLITE_FCNTL_EXTERNAL_READER 40 1243 #define SQLITE_FCNTL_CKSM_FILE 41 1244 #define SQLITE_FCNTL_RESET_CACHE 42 1245 1246 /* deprecated names */ 1247 #define SQLITE_GET_LOCKPROXYFILE SQLITE_FCNTL_GET_LOCKPROXYFILE 1248 #define SQLITE_SET_LOCKPROXYFILE SQLITE_FCNTL_SET_LOCKPROXYFILE 1249 #define SQLITE_LAST_ERRNO SQLITE_FCNTL_LAST_ERRNO 1250 1251 1252 /* 1253 ** CAPI3REF: Mutex Handle 1254 ** 1255 ** The mutex module within SQLite defines [sqlite3_mutex] to be an 1256 ** abstract type for a mutex object. The SQLite core never looks 1257 ** at the internal representation of an [sqlite3_mutex]. It only 1258 ** deals with pointers to the [sqlite3_mutex] object. 1259 ** 1260 ** Mutexes are created using [sqlite3_mutex_alloc()]. 1261 */ 1262 typedef struct sqlite3_mutex sqlite3_mutex; 1263 1264 /* 1265 ** CAPI3REF: Loadable Extension Thunk 1266 ** 1267 ** A pointer to the opaque sqlite3_api_routines structure is passed as 1268 ** the third parameter to entry points of [loadable extensions]. This 1269 ** structure must be typedefed in order to work around compiler warnings 1270 ** on some platforms. 1271 */ 1272 typedef struct sqlite3_api_routines sqlite3_api_routines; 1273 1274 /* 1275 ** CAPI3REF: File Name 1276 ** 1277 ** Type [sqlite3_filename] is used by SQLite to pass filenames to the 1278 ** xOpen method of a [VFS]. It may be cast to (const char*) and treated 1279 ** as a normal, nul-terminated, UTF-8 buffer containing the filename, but 1280 ** may also be passed to special APIs such as: 1281 ** 1282 ** <ul> 1283 ** <li> sqlite3_filename_database() 1284 ** <li> sqlite3_filename_journal() 1285 ** <li> sqlite3_filename_wal() 1286 ** <li> sqlite3_uri_parameter() 1287 ** <li> sqlite3_uri_boolean() 1288 ** <li> sqlite3_uri_int64() 1289 ** <li> sqlite3_uri_key() 1290 ** </ul> 1291 */ 1292 typedef const char *sqlite3_filename; 1293 1294 /* 1295 ** CAPI3REF: OS Interface Object 1296 ** 1297 ** An instance of the sqlite3_vfs object defines the interface between 1298 ** the SQLite core and the underlying operating system. The "vfs" 1299 ** in the name of the object stands for "virtual file system". See 1300 ** the [VFS | VFS documentation] for further information. 1301 ** 1302 ** The VFS interface is sometimes extended by adding new methods onto 1303 ** the end. Each time such an extension occurs, the iVersion field 1304 ** is incremented. The iVersion value started out as 1 in 1305 ** SQLite [version 3.5.0] on [dateof:3.5.0], then increased to 2 1306 ** with SQLite [version 3.7.0] on [dateof:3.7.0], and then increased 1307 ** to 3 with SQLite [version 3.7.6] on [dateof:3.7.6]. Additional fields 1308 ** may be appended to the sqlite3_vfs object and the iVersion value 1309 ** may increase again in future versions of SQLite. 1310 ** Note that due to an oversight, the structure 1311 ** of the sqlite3_vfs object changed in the transition from 1312 ** SQLite [version 3.5.9] to [version 3.6.0] on [dateof:3.6.0] 1313 ** and yet the iVersion field was not increased. 1314 ** 1315 ** The szOsFile field is the size of the subclassed [sqlite3_file] 1316 ** structure used by this VFS. mxPathname is the maximum length of 1317 ** a pathname in this VFS. 1318 ** 1319 ** Registered sqlite3_vfs objects are kept on a linked list formed by 1320 ** the pNext pointer. The [sqlite3_vfs_register()] 1321 ** and [sqlite3_vfs_unregister()] interfaces manage this list 1322 ** in a thread-safe way. The [sqlite3_vfs_find()] interface 1323 ** searches the list. Neither the application code nor the VFS 1324 ** implementation should use the pNext pointer. 1325 ** 1326 ** The pNext field is the only field in the sqlite3_vfs 1327 ** structure that SQLite will ever modify. SQLite will only access 1328 ** or modify this field while holding a particular static mutex. 1329 ** The application should never modify anything within the sqlite3_vfs 1330 ** object once the object has been registered. 1331 ** 1332 ** The zName field holds the name of the VFS module. The name must 1333 ** be unique across all VFS modules. 1334 ** 1335 ** [[sqlite3_vfs.xOpen]] 1336 ** ^SQLite guarantees that the zFilename parameter to xOpen 1337 ** is either a NULL pointer or string obtained 1338 ** from xFullPathname() with an optional suffix added. 1339 ** ^If a suffix is added to the zFilename parameter, it will 1340 ** consist of a single "-" character followed by no more than 1341 ** 11 alphanumeric and/or "-" characters. 1342 ** ^SQLite further guarantees that 1343 ** the string will be valid and unchanged until xClose() is 1344 ** called. Because of the previous sentence, 1345 ** the [sqlite3_file] can safely store a pointer to the 1346 ** filename if it needs to remember the filename for some reason. 1347 ** If the zFilename parameter to xOpen is a NULL pointer then xOpen 1348 ** must invent its own temporary name for the file. ^Whenever the 1349 ** xFilename parameter is NULL it will also be the case that the 1350 ** flags parameter will include [SQLITE_OPEN_DELETEONCLOSE]. 1351 ** 1352 ** The flags argument to xOpen() includes all bits set in 1353 ** the flags argument to [sqlite3_open_v2()]. Or if [sqlite3_open()] 1354 ** or [sqlite3_open16()] is used, then flags includes at least 1355 ** [SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE]. 1356 ** If xOpen() opens a file read-only then it sets *pOutFlags to 1357 ** include [SQLITE_OPEN_READONLY]. Other bits in *pOutFlags may be set. 1358 ** 1359 ** ^(SQLite will also add one of the following flags to the xOpen() 1360 ** call, depending on the object being opened: 1361 ** 1362 ** <ul> 1363 ** <li> [SQLITE_OPEN_MAIN_DB] 1364 ** <li> [SQLITE_OPEN_MAIN_JOURNAL] 1365 ** <li> [SQLITE_OPEN_TEMP_DB] 1366 ** <li> [SQLITE_OPEN_TEMP_JOURNAL] 1367 ** <li> [SQLITE_OPEN_TRANSIENT_DB] 1368 ** <li> [SQLITE_OPEN_SUBJOURNAL] 1369 ** <li> [SQLITE_OPEN_SUPER_JOURNAL] 1370 ** <li> [SQLITE_OPEN_WAL] 1371 ** </ul>)^ 1372 ** 1373 ** The file I/O implementation can use the object type flags to 1374 ** change the way it deals with files. For example, an application 1375 ** that does not care about crash recovery or rollback might make 1376 ** the open of a journal file a no-op. Writes to this journal would 1377 ** also be no-ops, and any attempt to read the journal would return 1378 ** SQLITE_IOERR. Or the implementation might recognize that a database 1379 ** file will be doing page-aligned sector reads and writes in a random 1380 ** order and set up its I/O subsystem accordingly. 1381 ** 1382 ** SQLite might also add one of the following flags to the xOpen method: 1383 ** 1384 ** <ul> 1385 ** <li> [SQLITE_OPEN_DELETEONCLOSE] 1386 ** <li> [SQLITE_OPEN_EXCLUSIVE] 1387 ** </ul> 1388 ** 1389 ** The [SQLITE_OPEN_DELETEONCLOSE] flag means the file should be 1390 ** deleted when it is closed. ^The [SQLITE_OPEN_DELETEONCLOSE] 1391 ** will be set for TEMP databases and their journals, transient 1392 ** databases, and subjournals. 1393 ** 1394 ** ^The [SQLITE_OPEN_EXCLUSIVE] flag is always used in conjunction 1395 ** with the [SQLITE_OPEN_CREATE] flag, which are both directly 1396 ** analogous to the O_EXCL and O_CREAT flags of the POSIX open() 1397 ** API. The SQLITE_OPEN_EXCLUSIVE flag, when paired with the 1398 ** SQLITE_OPEN_CREATE, is used to indicate that file should always 1399 ** be created, and that it is an error if it already exists. 1400 ** It is <i>not</i> used to indicate the file should be opened 1401 ** for exclusive access. 1402 ** 1403 ** ^At least szOsFile bytes of memory are allocated by SQLite 1404 ** to hold the [sqlite3_file] structure passed as the third 1405 ** argument to xOpen. The xOpen method does not have to 1406 ** allocate the structure; it should just fill it in. Note that 1407 ** the xOpen method must set the sqlite3_file.pMethods to either 1408 ** a valid [sqlite3_io_methods] object or to NULL. xOpen must do 1409 ** this even if the open fails. SQLite expects that the sqlite3_file.pMethods 1410 ** element will be valid after xOpen returns regardless of the success 1411 ** or failure of the xOpen call. 1412 ** 1413 ** [[sqlite3_vfs.xAccess]] 1414 ** ^The flags argument to xAccess() may be [SQLITE_ACCESS_EXISTS] 1415 ** to test for the existence of a file, or [SQLITE_ACCESS_READWRITE] to 1416 ** test whether a file is readable and writable, or [SQLITE_ACCESS_READ] 1417 ** to test whether a file is at least readable. The SQLITE_ACCESS_READ 1418 ** flag is never actually used and is not implemented in the built-in 1419 ** VFSes of SQLite. The file is named by the second argument and can be a 1420 ** directory. The xAccess method returns [SQLITE_OK] on success or some 1421 ** non-zero error code if there is an I/O error or if the name of 1422 ** the file given in the second argument is illegal. If SQLITE_OK 1423 ** is returned, then non-zero or zero is written into *pResOut to indicate 1424 ** whether or not the file is accessible. 1425 ** 1426 ** ^SQLite will always allocate at least mxPathname+1 bytes for the 1427 ** output buffer xFullPathname. The exact size of the output buffer 1428 ** is also passed as a parameter to both methods. If the output buffer 1429 ** is not large enough, [SQLITE_CANTOPEN] should be returned. Since this is 1430 ** handled as a fatal error by SQLite, vfs implementations should endeavor 1431 ** to prevent this by setting mxPathname to a sufficiently large value. 1432 ** 1433 ** The xRandomness(), xSleep(), xCurrentTime(), and xCurrentTimeInt64() 1434 ** interfaces are not strictly a part of the filesystem, but they are 1435 ** included in the VFS structure for completeness. 1436 ** The xRandomness() function attempts to return nBytes bytes 1437 ** of good-quality randomness into zOut. The return value is 1438 ** the actual number of bytes of randomness obtained. 1439 ** The xSleep() method causes the calling thread to sleep for at 1440 ** least the number of microseconds given. ^The xCurrentTime() 1441 ** method returns a Julian Day Number for the current date and time as 1442 ** a floating point value. 1443 ** ^The xCurrentTimeInt64() method returns, as an integer, the Julian 1444 ** Day Number multiplied by 86400000 (the number of milliseconds in 1445 ** a 24-hour day). 1446 ** ^SQLite will use the xCurrentTimeInt64() method to get the current 1447 ** date and time if that method is available (if iVersion is 2 or 1448 ** greater and the function pointer is not NULL) and will fall back 1449 ** to xCurrentTime() if xCurrentTimeInt64() is unavailable. 1450 ** 1451 ** ^The xSetSystemCall(), xGetSystemCall(), and xNestSystemCall() interfaces 1452 ** are not used by the SQLite core. These optional interfaces are provided 1453 ** by some VFSes to facilitate testing of the VFS code. By overriding 1454 ** system calls with functions under its control, a test program can 1455 ** simulate faults and error conditions that would otherwise be difficult 1456 ** or impossible to induce. The set of system calls that can be overridden 1457 ** varies from one VFS to another, and from one version of the same VFS to the 1458 ** next. Applications that use these interfaces must be prepared for any 1459 ** or all of these interfaces to be NULL or for their behavior to change 1460 ** from one release to the next. Applications must not attempt to access 1461 ** any of these methods if the iVersion of the VFS is less than 3. 1462 */ 1463 typedef struct sqlite3_vfs sqlite3_vfs; 1464 typedef void (*sqlite3_syscall_ptr)(void); 1465 struct sqlite3_vfs { 1466 int iVersion; /* Structure version number (currently 3) */ 1467 int szOsFile; /* Size of subclassed sqlite3_file */ 1468 int mxPathname; /* Maximum file pathname length */ 1469 sqlite3_vfs *pNext; /* Next registered VFS */ 1470 const char *zName; /* Name of this virtual file system */ 1471 void *pAppData; /* Pointer to application-specific data */ 1472 int (*xOpen)(sqlite3_vfs*, sqlite3_filename zName, sqlite3_file*, 1473 int flags, int *pOutFlags); 1474 int (*xDelete)(sqlite3_vfs*, const char *zName, int syncDir); 1475 int (*xAccess)(sqlite3_vfs*, const char *zName, int flags, int *pResOut); 1476 int (*xFullPathname)(sqlite3_vfs*, const char *zName, int nOut, char *zOut); 1477 void *(*xDlOpen)(sqlite3_vfs*, const char *zFilename); 1478 void (*xDlError)(sqlite3_vfs*, int nByte, char *zErrMsg); 1479 void (*(*xDlSym)(sqlite3_vfs*,void*, const char *zSymbol))(void); 1480 void (*xDlClose)(sqlite3_vfs*, void*); 1481 int (*xRandomness)(sqlite3_vfs*, int nByte, char *zOut); 1482 int (*xSleep)(sqlite3_vfs*, int microseconds); 1483 int (*xCurrentTime)(sqlite3_vfs*, double*); 1484 int (*xGetLastError)(sqlite3_vfs*, int, char *); 1485 /* 1486 ** The methods above are in version 1 of the sqlite_vfs object 1487 ** definition. Those that follow are added in version 2 or later 1488 */ 1489 int (*xCurrentTimeInt64)(sqlite3_vfs*, sqlite3_int64*); 1490 /* 1491 ** The methods above are in versions 1 and 2 of the sqlite_vfs object. 1492 ** Those below are for version 3 and greater. 1493 */ 1494 int (*xSetSystemCall)(sqlite3_vfs*, const char *zName, sqlite3_syscall_ptr); 1495 sqlite3_syscall_ptr (*xGetSystemCall)(sqlite3_vfs*, const char *zName); 1496 const char *(*xNextSystemCall)(sqlite3_vfs*, const char *zName); 1497 /* 1498 ** The methods above are in versions 1 through 3 of the sqlite_vfs object. 1499 ** New fields may be appended in future versions. The iVersion 1500 ** value will increment whenever this happens. 1501 */ 1502 }; 1503 1504 /* 1505 ** CAPI3REF: Flags for the xAccess VFS method 1506 ** 1507 ** These integer constants can be used as the third parameter to 1508 ** the xAccess method of an [sqlite3_vfs] object. They determine 1509 ** what kind of permissions the xAccess method is looking for. 1510 ** With SQLITE_ACCESS_EXISTS, the xAccess method 1511 ** simply checks whether the file exists. 1512 ** With SQLITE_ACCESS_READWRITE, the xAccess method 1513 ** checks whether the named directory is both readable and writable 1514 ** (in other words, if files can be added, removed, and renamed within 1515 ** the directory). 1516 ** The SQLITE_ACCESS_READWRITE constant is currently used only by the 1517 ** [temp_store_directory pragma], though this could change in a future 1518 ** release of SQLite. 1519 ** With SQLITE_ACCESS_READ, the xAccess method 1520 ** checks whether the file is readable. The SQLITE_ACCESS_READ constant is 1521 ** currently unused, though it might be used in a future release of 1522 ** SQLite. 1523 */ 1524 #define SQLITE_ACCESS_EXISTS 0 1525 #define SQLITE_ACCESS_READWRITE 1 /* Used by PRAGMA temp_store_directory */ 1526 #define SQLITE_ACCESS_READ 2 /* Unused */ 1527 1528 /* 1529 ** CAPI3REF: Flags for the xShmLock VFS method 1530 ** 1531 ** These integer constants define the various locking operations 1532 ** allowed by the xShmLock method of [sqlite3_io_methods]. The 1533 ** following are the only legal combinations of flags to the 1534 ** xShmLock method: 1535 ** 1536 ** <ul> 1537 ** <li> SQLITE_SHM_LOCK | SQLITE_SHM_SHARED 1538 ** <li> SQLITE_SHM_LOCK | SQLITE_SHM_EXCLUSIVE 1539 ** <li> SQLITE_SHM_UNLOCK | SQLITE_SHM_SHARED 1540 ** <li> SQLITE_SHM_UNLOCK | SQLITE_SHM_EXCLUSIVE 1541 ** </ul> 1542 ** 1543 ** When unlocking, the same SHARED or EXCLUSIVE flag must be supplied as 1544 ** was given on the corresponding lock. 1545 ** 1546 ** The xShmLock method can transition between unlocked and SHARED or 1547 ** between unlocked and EXCLUSIVE. It cannot transition between SHARED 1548 ** and EXCLUSIVE. 1549 */ 1550 #define SQLITE_SHM_UNLOCK 1 1551 #define SQLITE_SHM_LOCK 2 1552 #define SQLITE_SHM_SHARED 4 1553 #define SQLITE_SHM_EXCLUSIVE 8 1554 1555 /* 1556 ** CAPI3REF: Maximum xShmLock index 1557 ** 1558 ** The xShmLock method on [sqlite3_io_methods] may use values 1559 ** between 0 and this upper bound as its "offset" argument. 1560 ** The SQLite core will never attempt to acquire or release a 1561 ** lock outside of this range 1562 */ 1563 #define SQLITE_SHM_NLOCK 8 1564 1565 1566 /* 1567 ** CAPI3REF: Initialize The SQLite Library 1568 ** 1569 ** ^The sqlite3_initialize() routine initializes the 1570 ** SQLite library. ^The sqlite3_shutdown() routine 1571 ** deallocates any resources that were allocated by sqlite3_initialize(). 1572 ** These routines are designed to aid in process initialization and 1573 ** shutdown on embedded systems. Workstation applications using 1574 ** SQLite normally do not need to invoke either of these routines. 1575 ** 1576 ** A call to sqlite3_initialize() is an "effective" call if it is 1577 ** the first time sqlite3_initialize() is invoked during the lifetime of 1578 ** the process, or if it is the first time sqlite3_initialize() is invoked 1579 ** following a call to sqlite3_shutdown(). ^(Only an effective call 1580 ** of sqlite3_initialize() does any initialization. All other calls 1581 ** are harmless no-ops.)^ 1582 ** 1583 ** A call to sqlite3_shutdown() is an "effective" call if it is the first 1584 ** call to sqlite3_shutdown() since the last sqlite3_initialize(). ^(Only 1585 ** an effective call to sqlite3_shutdown() does any deinitialization. 1586 ** All other valid calls to sqlite3_shutdown() are harmless no-ops.)^ 1587 ** 1588 ** The sqlite3_initialize() interface is threadsafe, but sqlite3_shutdown() 1589 ** is not. The sqlite3_shutdown() interface must only be called from a 1590 ** single thread. All open [database connections] must be closed and all 1591 ** other SQLite resources must be deallocated prior to invoking 1592 ** sqlite3_shutdown(). 1593 ** 1594 ** Among other things, ^sqlite3_initialize() will invoke 1595 ** sqlite3_os_init(). Similarly, ^sqlite3_shutdown() 1596 ** will invoke sqlite3_os_end(). 1597 ** 1598 ** ^The sqlite3_initialize() routine returns [SQLITE_OK] on success. 1599 ** ^If for some reason, sqlite3_initialize() is unable to initialize 1600 ** the library (perhaps it is unable to allocate a needed resource such 1601 ** as a mutex) it returns an [error code] other than [SQLITE_OK]. 1602 ** 1603 ** ^The sqlite3_initialize() routine is called internally by many other 1604 ** SQLite interfaces so that an application usually does not need to 1605 ** invoke sqlite3_initialize() directly. For example, [sqlite3_open()] 1606 ** calls sqlite3_initialize() so the SQLite library will be automatically 1607 ** initialized when [sqlite3_open()] is called if it has not be initialized 1608 ** already. ^However, if SQLite is compiled with the [SQLITE_OMIT_AUTOINIT] 1609 ** compile-time option, then the automatic calls to sqlite3_initialize() 1610 ** are omitted and the application must call sqlite3_initialize() directly 1611 ** prior to using any other SQLite interface. For maximum portability, 1612 ** it is recommended that applications always invoke sqlite3_initialize() 1613 ** directly prior to using any other SQLite interface. Future releases 1614 ** of SQLite may require this. In other words, the behavior exhibited 1615 ** when SQLite is compiled with [SQLITE_OMIT_AUTOINIT] might become the 1616 ** default behavior in some future release of SQLite. 1617 ** 1618 ** The sqlite3_os_init() routine does operating-system specific 1619 ** initialization of the SQLite library. The sqlite3_os_end() 1620 ** routine undoes the effect of sqlite3_os_init(). Typical tasks 1621 ** performed by these routines include allocation or deallocation 1622 ** of static resources, initialization of global variables, 1623 ** setting up a default [sqlite3_vfs] module, or setting up 1624 ** a default configuration using [sqlite3_config()]. 1625 ** 1626 ** The application should never invoke either sqlite3_os_init() 1627 ** or sqlite3_os_end() directly. The application should only invoke 1628 ** sqlite3_initialize() and sqlite3_shutdown(). The sqlite3_os_init() 1629 ** interface is called automatically by sqlite3_initialize() and 1630 ** sqlite3_os_end() is called by sqlite3_shutdown(). Appropriate 1631 ** implementations for sqlite3_os_init() and sqlite3_os_end() 1632 ** are built into SQLite when it is compiled for Unix, Windows, or OS/2. 1633 ** When [custom builds | built for other platforms] 1634 ** (using the [SQLITE_OS_OTHER=1] compile-time 1635 ** option) the application must supply a suitable implementation for 1636 ** sqlite3_os_init() and sqlite3_os_end(). An application-supplied 1637 ** implementation of sqlite3_os_init() or sqlite3_os_end() 1638 ** must return [SQLITE_OK] on success and some other [error code] upon 1639 ** failure. 1640 */ 1641 SQLITE_API int sqlite3_initialize(void); 1642 SQLITE_API int sqlite3_shutdown(void); 1643 SQLITE_API int sqlite3_os_init(void); 1644 SQLITE_API int sqlite3_os_end(void); 1645 1646 /* 1647 ** CAPI3REF: Configuring The SQLite Library 1648 ** 1649 ** The sqlite3_config() interface is used to make global configuration 1650 ** changes to SQLite in order to tune SQLite to the specific needs of 1651 ** the application. The default configuration is recommended for most 1652 ** applications and so this routine is usually not necessary. It is 1653 ** provided to support rare applications with unusual needs. 1654 ** 1655 ** <b>The sqlite3_config() interface is not threadsafe. The application 1656 ** must ensure that no other SQLite interfaces are invoked by other 1657 ** threads while sqlite3_config() is running.</b> 1658 ** 1659 ** The first argument to sqlite3_config() is an integer 1660 ** [configuration option] that determines 1661 ** what property of SQLite is to be configured. Subsequent arguments 1662 ** vary depending on the [configuration option] 1663 ** in the first argument. 1664 ** 1665 ** For most configuration options, the sqlite3_config() interface 1666 ** may only be invoked prior to library initialization using 1667 ** [sqlite3_initialize()] or after shutdown by [sqlite3_shutdown()]. 1668 ** The exceptional configuration options that may be invoked at any time 1669 ** are called "anytime configuration options". 1670 ** ^If sqlite3_config() is called after [sqlite3_initialize()] and before 1671 ** [sqlite3_shutdown()] with a first argument that is not an anytime 1672 ** configuration option, then the sqlite3_config() call will return SQLITE_MISUSE. 1673 ** Note, however, that ^sqlite3_config() can be called as part of the 1674 ** implementation of an application-defined [sqlite3_os_init()]. 1675 ** 1676 ** ^When a configuration option is set, sqlite3_config() returns [SQLITE_OK]. 1677 ** ^If the option is unknown or SQLite is unable to set the option 1678 ** then this routine returns a non-zero [error code]. 1679 */ 1680 SQLITE_API int sqlite3_config(int, ...); 1681 1682 /* 1683 ** CAPI3REF: Configure database connections 1684 ** METHOD: sqlite3 1685 ** 1686 ** The sqlite3_db_config() interface is used to make configuration 1687 ** changes to a [database connection]. The interface is similar to 1688 ** [sqlite3_config()] except that the changes apply to a single 1689 ** [database connection] (specified in the first argument). 1690 ** 1691 ** The second argument to sqlite3_db_config(D,V,...) is the 1692 ** [SQLITE_DBCONFIG_LOOKASIDE | configuration verb] - an integer code 1693 ** that indicates what aspect of the [database connection] is being configured. 1694 ** Subsequent arguments vary depending on the configuration verb. 1695 ** 1696 ** ^Calls to sqlite3_db_config() return SQLITE_OK if and only if 1697 ** the call is considered successful. 1698 */ 1699 SQLITE_API int sqlite3_db_config(sqlite3*, int op, ...); 1700 1701 /* 1702 ** CAPI3REF: Memory Allocation Routines 1703 ** 1704 ** An instance of this object defines the interface between SQLite 1705 ** and low-level memory allocation routines. 1706 ** 1707 ** This object is used in only one place in the SQLite interface. 1708 ** A pointer to an instance of this object is the argument to 1709 ** [sqlite3_config()] when the configuration option is 1710 ** [SQLITE_CONFIG_MALLOC] or [SQLITE_CONFIG_GETMALLOC]. 1711 ** By creating an instance of this object 1712 ** and passing it to [sqlite3_config]([SQLITE_CONFIG_MALLOC]) 1713 ** during configuration, an application can specify an alternative 1714 ** memory allocation subsystem for SQLite to use for all of its 1715 ** dynamic memory needs. 1716 ** 1717 ** Note that SQLite comes with several [built-in memory allocators] 1718 ** that are perfectly adequate for the overwhelming majority of applications 1719 ** and that this object is only useful to a tiny minority of applications 1720 ** with specialized memory allocation requirements. This object is 1721 ** also used during testing of SQLite in order to specify an alternative 1722 ** memory allocator that simulates memory out-of-memory conditions in 1723 ** order to verify that SQLite recovers gracefully from such 1724 ** conditions. 1725 ** 1726 ** The xMalloc, xRealloc, and xFree methods must work like the 1727 ** malloc(), realloc() and free() functions from the standard C library. 1728 ** ^SQLite guarantees that the second argument to 1729 ** xRealloc is always a value returned by a prior call to xRoundup. 1730 ** 1731 ** xSize should return the allocated size of a memory allocation 1732 ** previously obtained from xMalloc or xRealloc. The allocated size 1733 ** is always at least as big as the requested size but may be larger. 1734 ** 1735 ** The xRoundup method returns what would be the allocated size of 1736 ** a memory allocation given a particular requested size. Most memory 1737 ** allocators round up memory allocations at least to the next multiple 1738 ** of 8. Some allocators round up to a larger multiple or to a power of 2. 1739 ** Every memory allocation request coming in through [sqlite3_malloc()] 1740 ** or [sqlite3_realloc()] first calls xRoundup. If xRoundup returns 0, 1741 ** that causes the corresponding memory allocation to fail. 1742 ** 1743 ** The xInit method initializes the memory allocator. For example, 1744 ** it might allocate any required mutexes or initialize internal data 1745 ** structures. The xShutdown method is invoked (indirectly) by 1746 ** [sqlite3_shutdown()] and should deallocate any resources acquired 1747 ** by xInit. The pAppData pointer is used as the only parameter to 1748 ** xInit and xShutdown. 1749 ** 1750 ** SQLite holds the [SQLITE_MUTEX_STATIC_MAIN] mutex when it invokes 1751 ** the xInit method, so the xInit method need not be threadsafe. The 1752 ** xShutdown method is only called from [sqlite3_shutdown()] so it does 1753 ** not need to be threadsafe either. For all other methods, SQLite 1754 ** holds the [SQLITE_MUTEX_STATIC_MEM] mutex as long as the 1755 ** [SQLITE_CONFIG_MEMSTATUS] configuration option is turned on (which 1756 ** it is by default) and so the methods are automatically serialized. 1757 ** However, if [SQLITE_CONFIG_MEMSTATUS] is disabled, then the other 1758 ** methods must be threadsafe or else make their own arrangements for 1759 ** serialization. 1760 ** 1761 ** SQLite will never invoke xInit() more than once without an intervening 1762 ** call to xShutdown(). 1763 */ 1764 typedef struct sqlite3_mem_methods sqlite3_mem_methods; 1765 struct sqlite3_mem_methods { 1766 void *(*xMalloc)(int); /* Memory allocation function */ 1767 void (*xFree)(void*); /* Free a prior allocation */ 1768 void *(*xRealloc)(void*,int); /* Resize an allocation */ 1769 int (*xSize)(void*); /* Return the size of an allocation */ 1770 int (*xRoundup)(int); /* Round up request size to allocation size */ 1771 int (*xInit)(void*); /* Initialize the memory allocator */ 1772 void (*xShutdown)(void*); /* Deinitialize the memory allocator */ 1773 void *pAppData; /* Argument to xInit() and xShutdown() */ 1774 }; 1775 1776 /* 1777 ** CAPI3REF: Configuration Options 1778 ** KEYWORDS: {configuration option} 1779 ** 1780 ** These constants are the available integer configuration options that 1781 ** can be passed as the first argument to the [sqlite3_config()] interface. 1782 ** 1783 ** Most of the configuration options for sqlite3_config() 1784 ** will only work if invoked prior to [sqlite3_initialize()] or after 1785 ** [sqlite3_shutdown()]. The few exceptions to this rule are called 1786 ** "anytime configuration options". 1787 ** ^Calling [sqlite3_config()] with a first argument that is not an 1788 ** anytime configuration option in between calls to [sqlite3_initialize()] and 1789 ** [sqlite3_shutdown()] is a no-op that returns SQLITE_MISUSE. 1790 ** 1791 ** The set of anytime configuration options can change (by insertions 1792 ** and/or deletions) from one release of SQLite to the next. 1793 ** As of SQLite version 3.42.0, the complete set of anytime configuration 1794 ** options is: 1795 ** <ul> 1796 ** <li> SQLITE_CONFIG_LOG 1797 ** <li> SQLITE_CONFIG_PCACHE_HDRSZ 1798 ** </ul> 1799 ** 1800 ** New configuration options may be added in future releases of SQLite. 1801 ** Existing configuration options might be discontinued. Applications 1802 ** should check the return code from [sqlite3_config()] to make sure that 1803 ** the call worked. The [sqlite3_config()] interface will return a 1804 ** non-zero [error code] if a discontinued or unsupported configuration option 1805 ** is invoked. 1806 ** 1807 ** <dl> 1808 ** [[SQLITE_CONFIG_SINGLETHREAD]] <dt>SQLITE_CONFIG_SINGLETHREAD</dt> 1809 ** <dd>There are no arguments to this option. ^This option sets the 1810 ** [threading mode] to Single-thread. In other words, it disables 1811 ** all mutexing and puts SQLite into a mode where it can only be used 1812 ** by a single thread. ^If SQLite is compiled with 1813 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1814 ** it is not possible to change the [threading mode] from its default 1815 ** value of Single-thread and so [sqlite3_config()] will return 1816 ** [SQLITE_ERROR] if called with the SQLITE_CONFIG_SINGLETHREAD 1817 ** configuration option.</dd> 1818 ** 1819 ** [[SQLITE_CONFIG_MULTITHREAD]] <dt>SQLITE_CONFIG_MULTITHREAD</dt> 1820 ** <dd>There are no arguments to this option. ^This option sets the 1821 ** [threading mode] to Multi-thread. In other words, it disables 1822 ** mutexing on [database connection] and [prepared statement] objects. 1823 ** The application is responsible for serializing access to 1824 ** [database connections] and [prepared statements]. But other mutexes 1825 ** are enabled so that SQLite will be safe to use in a multi-threaded 1826 ** environment as long as no two threads attempt to use the same 1827 ** [database connection] at the same time. ^If SQLite is compiled with 1828 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1829 ** it is not possible to set the Multi-thread [threading mode] and 1830 ** [sqlite3_config()] will return [SQLITE_ERROR] if called with the 1831 ** SQLITE_CONFIG_MULTITHREAD configuration option.</dd> 1832 ** 1833 ** [[SQLITE_CONFIG_SERIALIZED]] <dt>SQLITE_CONFIG_SERIALIZED</dt> 1834 ** <dd>There are no arguments to this option. ^This option sets the 1835 ** [threading mode] to Serialized. In other words, this option enables 1836 ** all mutexes including the recursive 1837 ** mutexes on [database connection] and [prepared statement] objects. 1838 ** In this mode (which is the default when SQLite is compiled with 1839 ** [SQLITE_THREADSAFE=1]) the SQLite library will itself serialize access 1840 ** to [database connections] and [prepared statements] so that the 1841 ** application is free to use the same [database connection] or the 1842 ** same [prepared statement] in different threads at the same time. 1843 ** ^If SQLite is compiled with 1844 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1845 ** it is not possible to set the Serialized [threading mode] and 1846 ** [sqlite3_config()] will return [SQLITE_ERROR] if called with the 1847 ** SQLITE_CONFIG_SERIALIZED configuration option.</dd> 1848 ** 1849 ** [[SQLITE_CONFIG_MALLOC]] <dt>SQLITE_CONFIG_MALLOC</dt> 1850 ** <dd> ^(The SQLITE_CONFIG_MALLOC option takes a single argument which is 1851 ** a pointer to an instance of the [sqlite3_mem_methods] structure. 1852 ** The argument specifies 1853 ** alternative low-level memory allocation routines to be used in place of 1854 ** the memory allocation routines built into SQLite.)^ ^SQLite makes 1855 ** its own private copy of the content of the [sqlite3_mem_methods] structure 1856 ** before the [sqlite3_config()] call returns.</dd> 1857 ** 1858 ** [[SQLITE_CONFIG_GETMALLOC]] <dt>SQLITE_CONFIG_GETMALLOC</dt> 1859 ** <dd> ^(The SQLITE_CONFIG_GETMALLOC option takes a single argument which 1860 ** is a pointer to an instance of the [sqlite3_mem_methods] structure. 1861 ** The [sqlite3_mem_methods] 1862 ** structure is filled with the currently defined memory allocation routines.)^ 1863 ** This option can be used to overload the default memory allocation 1864 ** routines with a wrapper that simulations memory allocation failure or 1865 ** tracks memory usage, for example. </dd> 1866 ** 1867 ** [[SQLITE_CONFIG_SMALL_MALLOC]] <dt>SQLITE_CONFIG_SMALL_MALLOC</dt> 1868 ** <dd> ^The SQLITE_CONFIG_SMALL_MALLOC option takes single argument of 1869 ** type int, interpreted as a boolean, which if true provides a hint to 1870 ** SQLite that it should avoid large memory allocations if possible. 1871 ** SQLite will run faster if it is free to make large memory allocations, 1872 ** but some application might prefer to run slower in exchange for 1873 ** guarantees about memory fragmentation that are possible if large 1874 ** allocations are avoided. This hint is normally off. 1875 ** </dd> 1876 ** 1877 ** [[SQLITE_CONFIG_MEMSTATUS]] <dt>SQLITE_CONFIG_MEMSTATUS</dt> 1878 ** <dd> ^The SQLITE_CONFIG_MEMSTATUS option takes single argument of type int, 1879 ** interpreted as a boolean, which enables or disables the collection of 1880 ** memory allocation statistics. ^(When memory allocation statistics are 1881 ** disabled, the following SQLite interfaces become non-operational: 1882 ** <ul> 1883 ** <li> [sqlite3_hard_heap_limit64()] 1884 ** <li> [sqlite3_memory_used()] 1885 ** <li> [sqlite3_memory_highwater()] 1886 ** <li> [sqlite3_soft_heap_limit64()] 1887 ** <li> [sqlite3_status64()] 1888 ** </ul>)^ 1889 ** ^Memory allocation statistics are enabled by default unless SQLite is 1890 ** compiled with [SQLITE_DEFAULT_MEMSTATUS]=0 in which case memory 1891 ** allocation statistics are disabled by default. 1892 ** </dd> 1893 ** 1894 ** [[SQLITE_CONFIG_SCRATCH]] <dt>SQLITE_CONFIG_SCRATCH</dt> 1895 ** <dd> The SQLITE_CONFIG_SCRATCH option is no longer used. 1896 ** </dd> 1897 ** 1898 ** [[SQLITE_CONFIG_PAGECACHE]] <dt>SQLITE_CONFIG_PAGECACHE</dt> 1899 ** <dd> ^The SQLITE_CONFIG_PAGECACHE option specifies a memory pool 1900 ** that SQLite can use for the database page cache with the default page 1901 ** cache implementation. 1902 ** This configuration option is a no-op if an application-defined page 1903 ** cache implementation is loaded using the [SQLITE_CONFIG_PCACHE2]. 1904 ** ^There are three arguments to SQLITE_CONFIG_PAGECACHE: A pointer to 1905 ** 8-byte aligned memory (pMem), the size of each page cache line (sz), 1906 ** and the number of cache lines (N). 1907 ** The sz argument should be the size of the largest database page 1908 ** (a power of two between 512 and 65536) plus some extra bytes for each 1909 ** page header. ^The number of extra bytes needed by the page header 1910 ** can be determined using [SQLITE_CONFIG_PCACHE_HDRSZ]. 1911 ** ^It is harmless, apart from the wasted memory, 1912 ** for the sz parameter to be larger than necessary. The pMem 1913 ** argument must be either a NULL pointer or a pointer to an 8-byte 1914 ** aligned block of memory of at least sz*N bytes, otherwise 1915 ** subsequent behavior is undefined. 1916 ** ^When pMem is not NULL, SQLite will strive to use the memory provided 1917 ** to satisfy page cache needs, falling back to [sqlite3_malloc()] if 1918 ** a page cache line is larger than sz bytes or if all of the pMem buffer 1919 ** is exhausted. 1920 ** ^If pMem is NULL and N is non-zero, then each database connection 1921 ** does an initial bulk allocation for page cache memory 1922 ** from [sqlite3_malloc()] sufficient for N cache lines if N is positive or 1923 ** of -1024*N bytes if N is negative, . ^If additional 1924 ** page cache memory is needed beyond what is provided by the initial 1925 ** allocation, then SQLite goes to [sqlite3_malloc()] separately for each 1926 ** additional cache line. </dd> 1927 ** 1928 ** [[SQLITE_CONFIG_HEAP]] <dt>SQLITE_CONFIG_HEAP</dt> 1929 ** <dd> ^The SQLITE_CONFIG_HEAP option specifies a static memory buffer 1930 ** that SQLite will use for all of its dynamic memory allocation needs 1931 ** beyond those provided for by [SQLITE_CONFIG_PAGECACHE]. 1932 ** ^The SQLITE_CONFIG_HEAP option is only available if SQLite is compiled 1933 ** with either [SQLITE_ENABLE_MEMSYS3] or [SQLITE_ENABLE_MEMSYS5] and returns 1934 ** [SQLITE_ERROR] if invoked otherwise. 1935 ** ^There are three arguments to SQLITE_CONFIG_HEAP: 1936 ** An 8-byte aligned pointer to the memory, 1937 ** the number of bytes in the memory buffer, and the minimum allocation size. 1938 ** ^If the first pointer (the memory pointer) is NULL, then SQLite reverts 1939 ** to using its default memory allocator (the system malloc() implementation), 1940 ** undoing any prior invocation of [SQLITE_CONFIG_MALLOC]. ^If the 1941 ** memory pointer is not NULL then the alternative memory 1942 ** allocator is engaged to handle all of SQLites memory allocation needs. 1943 ** The first pointer (the memory pointer) must be aligned to an 8-byte 1944 ** boundary or subsequent behavior of SQLite will be undefined. 1945 ** The minimum allocation size is capped at 2**12. Reasonable values 1946 ** for the minimum allocation size are 2**5 through 2**8.</dd> 1947 ** 1948 ** [[SQLITE_CONFIG_MUTEX]] <dt>SQLITE_CONFIG_MUTEX</dt> 1949 ** <dd> ^(The SQLITE_CONFIG_MUTEX option takes a single argument which is a 1950 ** pointer to an instance of the [sqlite3_mutex_methods] structure. 1951 ** The argument specifies alternative low-level mutex routines to be used 1952 ** in place the mutex routines built into SQLite.)^ ^SQLite makes a copy of 1953 ** the content of the [sqlite3_mutex_methods] structure before the call to 1954 ** [sqlite3_config()] returns. ^If SQLite is compiled with 1955 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1956 ** the entire mutexing subsystem is omitted from the build and hence calls to 1957 ** [sqlite3_config()] with the SQLITE_CONFIG_MUTEX configuration option will 1958 ** return [SQLITE_ERROR].</dd> 1959 ** 1960 ** [[SQLITE_CONFIG_GETMUTEX]] <dt>SQLITE_CONFIG_GETMUTEX</dt> 1961 ** <dd> ^(The SQLITE_CONFIG_GETMUTEX option takes a single argument which 1962 ** is a pointer to an instance of the [sqlite3_mutex_methods] structure. The 1963 ** [sqlite3_mutex_methods] 1964 ** structure is filled with the currently defined mutex routines.)^ 1965 ** This option can be used to overload the default mutex allocation 1966 ** routines with a wrapper used to track mutex usage for performance 1967 ** profiling or testing, for example. ^If SQLite is compiled with 1968 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1969 ** the entire mutexing subsystem is omitted from the build and hence calls to 1970 ** [sqlite3_config()] with the SQLITE_CONFIG_GETMUTEX configuration option will 1971 ** return [SQLITE_ERROR].</dd> 1972 ** 1973 ** [[SQLITE_CONFIG_LOOKASIDE]] <dt>SQLITE_CONFIG_LOOKASIDE</dt> 1974 ** <dd> ^(The SQLITE_CONFIG_LOOKASIDE option takes two arguments that determine 1975 ** the default size of lookaside memory on each [database connection]. 1976 ** The first argument is the 1977 ** size of each lookaside buffer slot and the second is the number of 1978 ** slots allocated to each database connection.)^ ^(SQLITE_CONFIG_LOOKASIDE 1979 ** sets the <i>default</i> lookaside size. The [SQLITE_DBCONFIG_LOOKASIDE] 1980 ** option to [sqlite3_db_config()] can be used to change the lookaside 1981 ** configuration on individual connections.)^ </dd> 1982 ** 1983 ** [[SQLITE_CONFIG_PCACHE2]] <dt>SQLITE_CONFIG_PCACHE2</dt> 1984 ** <dd> ^(The SQLITE_CONFIG_PCACHE2 option takes a single argument which is 1985 ** a pointer to an [sqlite3_pcache_methods2] object. This object specifies 1986 ** the interface to a custom page cache implementation.)^ 1987 ** ^SQLite makes a copy of the [sqlite3_pcache_methods2] object.</dd> 1988 ** 1989 ** [[SQLITE_CONFIG_GETPCACHE2]] <dt>SQLITE_CONFIG_GETPCACHE2</dt> 1990 ** <dd> ^(The SQLITE_CONFIG_GETPCACHE2 option takes a single argument which 1991 ** is a pointer to an [sqlite3_pcache_methods2] object. SQLite copies of 1992 ** the current page cache implementation into that object.)^ </dd> 1993 ** 1994 ** [[SQLITE_CONFIG_LOG]] <dt>SQLITE_CONFIG_LOG</dt> 1995 ** <dd> The SQLITE_CONFIG_LOG option is used to configure the SQLite 1996 ** global [error log]. 1997 ** (^The SQLITE_CONFIG_LOG option takes two arguments: a pointer to a 1998 ** function with a call signature of void(*)(void*,int,const char*), 1999 ** and a pointer to void. ^If the function pointer is not NULL, it is 2000 ** invoked by [sqlite3_log()] to process each logging event. ^If the 2001 ** function pointer is NULL, the [sqlite3_log()] interface becomes a no-op. 2002 ** ^The void pointer that is the second argument to SQLITE_CONFIG_LOG is 2003 ** passed through as the first parameter to the application-defined logger 2004 ** function whenever that function is invoked. ^The second parameter to 2005 ** the logger function is a copy of the first parameter to the corresponding 2006 ** [sqlite3_log()] call and is intended to be a [result code] or an 2007 ** [extended result code]. ^The third parameter passed to the logger is 2008 ** log message after formatting via [sqlite3_snprintf()]. 2009 ** The SQLite logging interface is not reentrant; the logger function 2010 ** supplied by the application must not invoke any SQLite interface. 2011 ** In a multi-threaded application, the application-defined logger 2012 ** function must be threadsafe. </dd> 2013 ** 2014 ** [[SQLITE_CONFIG_URI]] <dt>SQLITE_CONFIG_URI 2015 ** <dd>^(The SQLITE_CONFIG_URI option takes a single argument of type int. 2016 ** If non-zero, then URI handling is globally enabled. If the parameter is zero, 2017 ** then URI handling is globally disabled.)^ ^If URI handling is globally 2018 ** enabled, all filenames passed to [sqlite3_open()], [sqlite3_open_v2()], 2019 ** [sqlite3_open16()] or 2020 ** specified as part of [ATTACH] commands are interpreted as URIs, regardless 2021 ** of whether or not the [SQLITE_OPEN_URI] flag is set when the database 2022 ** connection is opened. ^If it is globally disabled, filenames are 2023 ** only interpreted as URIs if the SQLITE_OPEN_URI flag is set when the 2024 ** database connection is opened. ^(By default, URI handling is globally 2025 ** disabled. The default value may be changed by compiling with the 2026 ** [SQLITE_USE_URI] symbol defined.)^ 2027 ** 2028 ** [[SQLITE_CONFIG_COVERING_INDEX_SCAN]] <dt>SQLITE_CONFIG_COVERING_INDEX_SCAN 2029 ** <dd>^The SQLITE_CONFIG_COVERING_INDEX_SCAN option takes a single integer 2030 ** argument which is interpreted as a boolean in order to enable or disable 2031 ** the use of covering indices for full table scans in the query optimizer. 2032 ** ^The default setting is determined 2033 ** by the [SQLITE_ALLOW_COVERING_INDEX_SCAN] compile-time option, or is "on" 2034 ** if that compile-time option is omitted. 2035 ** The ability to disable the use of covering indices for full table scans 2036 ** is because some incorrectly coded legacy applications might malfunction 2037 ** when the optimization is enabled. Providing the ability to 2038 ** disable the optimization allows the older, buggy application code to work 2039 ** without change even with newer versions of SQLite. 2040 ** 2041 ** [[SQLITE_CONFIG_PCACHE]] [[SQLITE_CONFIG_GETPCACHE]] 2042 ** <dt>SQLITE_CONFIG_PCACHE and SQLITE_CONFIG_GETPCACHE 2043 ** <dd> These options are obsolete and should not be used by new code. 2044 ** They are retained for backwards compatibility but are now no-ops. 2045 ** </dd> 2046 ** 2047 ** [[SQLITE_CONFIG_SQLLOG]] 2048 ** <dt>SQLITE_CONFIG_SQLLOG 2049 ** <dd>This option is only available if sqlite is compiled with the 2050 ** [SQLITE_ENABLE_SQLLOG] pre-processor macro defined. The first argument should 2051 ** be a pointer to a function of type void(*)(void*,sqlite3*,const char*, int). 2052 ** The second should be of type (void*). The callback is invoked by the library 2053 ** in three separate circumstances, identified by the value passed as the 2054 ** fourth parameter. If the fourth parameter is 0, then the database connection 2055 ** passed as the second argument has just been opened. The third argument 2056 ** points to a buffer containing the name of the main database file. If the 2057 ** fourth parameter is 1, then the SQL statement that the third parameter 2058 ** points to has just been executed. Or, if the fourth parameter is 2, then 2059 ** the connection being passed as the second parameter is being closed. The 2060 ** third parameter is passed NULL In this case. An example of using this 2061 ** configuration option can be seen in the "test_sqllog.c" source file in 2062 ** the canonical SQLite source tree.</dd> 2063 ** 2064 ** [[SQLITE_CONFIG_MMAP_SIZE]] 2065 ** <dt>SQLITE_CONFIG_MMAP_SIZE 2066 ** <dd>^SQLITE_CONFIG_MMAP_SIZE takes two 64-bit integer (sqlite3_int64) values 2067 ** that are the default mmap size limit (the default setting for 2068 ** [PRAGMA mmap_size]) and the maximum allowed mmap size limit. 2069 ** ^The default setting can be overridden by each database connection using 2070 ** either the [PRAGMA mmap_size] command, or by using the 2071 ** [SQLITE_FCNTL_MMAP_SIZE] file control. ^(The maximum allowed mmap size 2072 ** will be silently truncated if necessary so that it does not exceed the 2073 ** compile-time maximum mmap size set by the 2074 ** [SQLITE_MAX_MMAP_SIZE] compile-time option.)^ 2075 ** ^If either argument to this option is negative, then that argument is 2076 ** changed to its compile-time default. 2077 ** 2078 ** [[SQLITE_CONFIG_WIN32_HEAPSIZE]] 2079 ** <dt>SQLITE_CONFIG_WIN32_HEAPSIZE 2080 ** <dd>^The SQLITE_CONFIG_WIN32_HEAPSIZE option is only available if SQLite is 2081 ** compiled for Windows with the [SQLITE_WIN32_MALLOC] pre-processor macro 2082 ** defined. ^SQLITE_CONFIG_WIN32_HEAPSIZE takes a 32-bit unsigned integer value 2083 ** that specifies the maximum size of the created heap. 2084 ** 2085 ** [[SQLITE_CONFIG_PCACHE_HDRSZ]] 2086 ** <dt>SQLITE_CONFIG_PCACHE_HDRSZ 2087 ** <dd>^The SQLITE_CONFIG_PCACHE_HDRSZ option takes a single parameter which 2088 ** is a pointer to an integer and writes into that integer the number of extra 2089 ** bytes per page required for each page in [SQLITE_CONFIG_PAGECACHE]. 2090 ** The amount of extra space required can change depending on the compiler, 2091 ** target platform, and SQLite version. 2092 ** 2093 ** [[SQLITE_CONFIG_PMASZ]] 2094 ** <dt>SQLITE_CONFIG_PMASZ 2095 ** <dd>^The SQLITE_CONFIG_PMASZ option takes a single parameter which 2096 ** is an unsigned integer and sets the "Minimum PMA Size" for the multithreaded 2097 ** sorter to that integer. The default minimum PMA Size is set by the 2098 ** [SQLITE_SORTER_PMASZ] compile-time option. New threads are launched 2099 ** to help with sort operations when multithreaded sorting 2100 ** is enabled (using the [PRAGMA threads] command) and the amount of content 2101 ** to be sorted exceeds the page size times the minimum of the 2102 ** [PRAGMA cache_size] setting and this value. 2103 ** 2104 ** [[SQLITE_CONFIG_STMTJRNL_SPILL]] 2105 ** <dt>SQLITE_CONFIG_STMTJRNL_SPILL 2106 ** <dd>^The SQLITE_CONFIG_STMTJRNL_SPILL option takes a single parameter which 2107 ** becomes the [statement journal] spill-to-disk threshold. 2108 ** [Statement journals] are held in memory until their size (in bytes) 2109 ** exceeds this threshold, at which point they are written to disk. 2110 ** Or if the threshold is -1, statement journals are always held 2111 ** exclusively in memory. 2112 ** Since many statement journals never become large, setting the spill 2113 ** threshold to a value such as 64KiB can greatly reduce the amount of 2114 ** I/O required to support statement rollback. 2115 ** The default value for this setting is controlled by the 2116 ** [SQLITE_STMTJRNL_SPILL] compile-time option. 2117 ** 2118 ** [[SQLITE_CONFIG_SORTERREF_SIZE]] 2119 ** <dt>SQLITE_CONFIG_SORTERREF_SIZE 2120 ** <dd>The SQLITE_CONFIG_SORTERREF_SIZE option accepts a single parameter 2121 ** of type (int) - the new value of the sorter-reference size threshold. 2122 ** Usually, when SQLite uses an external sort to order records according 2123 ** to an ORDER BY clause, all fields required by the caller are present in the 2124 ** sorted records. However, if SQLite determines based on the declared type 2125 ** of a table column that its values are likely to be very large - larger 2126 ** than the configured sorter-reference size threshold - then a reference 2127 ** is stored in each sorted record and the required column values loaded 2128 ** from the database as records are returned in sorted order. The default 2129 ** value for this option is to never use this optimization. Specifying a 2130 ** negative value for this option restores the default behavior. 2131 ** This option is only available if SQLite is compiled with the 2132 ** [SQLITE_ENABLE_SORTER_REFERENCES] compile-time option. 2133 ** 2134 ** [[SQLITE_CONFIG_MEMDB_MAXSIZE]] 2135 ** <dt>SQLITE_CONFIG_MEMDB_MAXSIZE 2136 ** <dd>The SQLITE_CONFIG_MEMDB_MAXSIZE option accepts a single parameter 2137 ** [sqlite3_int64] parameter which is the default maximum size for an in-memory 2138 ** database created using [sqlite3_deserialize()]. This default maximum 2139 ** size can be adjusted up or down for individual databases using the 2140 ** [SQLITE_FCNTL_SIZE_LIMIT] [sqlite3_file_control|file-control]. If this 2141 ** configuration setting is never used, then the default maximum is determined 2142 ** by the [SQLITE_MEMDB_DEFAULT_MAXSIZE] compile-time option. If that 2143 ** compile-time option is not set, then the default maximum is 1073741824. 2144 ** 2145 ** [[SQLITE_CONFIG_ROWID_IN_VIEW]] 2146 ** <dt>SQLITE_CONFIG_ROWID_IN_VIEW 2147 ** <dd>The SQLITE_CONFIG_ROWID_IN_VIEW option enables or disables the ability 2148 ** for VIEWs to have a ROWID. The capability can only be enabled if SQLite is 2149 ** compiled with -DSQLITE_ALLOW_ROWID_IN_VIEW, in which case the capability 2150 ** defaults to on. This configuration option queries the current setting or 2151 ** changes the setting to off or on. The argument is a pointer to an integer. 2152 ** If that integer initially holds a value of 1, then the ability for VIEWs to 2153 ** have ROWIDs is activated. If the integer initially holds zero, then the 2154 ** ability is deactivated. Any other initial value for the integer leaves the 2155 ** setting unchanged. After changes, if any, the integer is written with 2156 ** a 1 or 0, if the ability for VIEWs to have ROWIDs is on or off. If SQLite 2157 ** is compiled without -DSQLITE_ALLOW_ROWID_IN_VIEW (which is the usual and 2158 ** recommended case) then the integer is always filled with zero, regardless 2159 ** if its initial value. 2160 ** </dl> 2161 */ 2162 #define SQLITE_CONFIG_SINGLETHREAD 1 /* nil */ 2163 #define SQLITE_CONFIG_MULTITHREAD 2 /* nil */ 2164 #define SQLITE_CONFIG_SERIALIZED 3 /* nil */ 2165 #define SQLITE_CONFIG_MALLOC 4 /* sqlite3_mem_methods* */ 2166 #define SQLITE_CONFIG_GETMALLOC 5 /* sqlite3_mem_methods* */ 2167 #define SQLITE_CONFIG_SCRATCH 6 /* No longer used */ 2168 #define SQLITE_CONFIG_PAGECACHE 7 /* void*, int sz, int N */ 2169 #define SQLITE_CONFIG_HEAP 8 /* void*, int nByte, int min */ 2170 #define SQLITE_CONFIG_MEMSTATUS 9 /* boolean */ 2171 #define SQLITE_CONFIG_MUTEX 10 /* sqlite3_mutex_methods* */ 2172 #define SQLITE_CONFIG_GETMUTEX 11 /* sqlite3_mutex_methods* */ 2173 /* previously SQLITE_CONFIG_CHUNKALLOC 12 which is now unused. */ 2174 #define SQLITE_CONFIG_LOOKASIDE 13 /* int int */ 2175 #define SQLITE_CONFIG_PCACHE 14 /* no-op */ 2176 #define SQLITE_CONFIG_GETPCACHE 15 /* no-op */ 2177 #define SQLITE_CONFIG_LOG 16 /* xFunc, void* */ 2178 #define SQLITE_CONFIG_URI 17 /* int */ 2179 #define SQLITE_CONFIG_PCACHE2 18 /* sqlite3_pcache_methods2* */ 2180 #define SQLITE_CONFIG_GETPCACHE2 19 /* sqlite3_pcache_methods2* */ 2181 #define SQLITE_CONFIG_COVERING_INDEX_SCAN 20 /* int */ 2182 #define SQLITE_CONFIG_SQLLOG 21 /* xSqllog, void* */ 2183 #define SQLITE_CONFIG_MMAP_SIZE 22 /* sqlite3_int64, sqlite3_int64 */ 2184 #define SQLITE_CONFIG_WIN32_HEAPSIZE 23 /* int nByte */ 2185 #define SQLITE_CONFIG_PCACHE_HDRSZ 24 /* int *psz */ 2186 #define SQLITE_CONFIG_PMASZ 25 /* unsigned int szPma */ 2187 #define SQLITE_CONFIG_STMTJRNL_SPILL 26 /* int nByte */ 2188 #define SQLITE_CONFIG_SMALL_MALLOC 27 /* boolean */ 2189 #define SQLITE_CONFIG_SORTERREF_SIZE 28 /* int nByte */ 2190 #define SQLITE_CONFIG_MEMDB_MAXSIZE 29 /* sqlite3_int64 */ 2191 #define SQLITE_CONFIG_ROWID_IN_VIEW 30 /* int* */ 2192 2193 /* 2194 ** CAPI3REF: Database Connection Configuration Options 2195 ** 2196 ** These constants are the available integer configuration options that 2197 ** can be passed as the second argument to the [sqlite3_db_config()] interface. 2198 ** 2199 ** New configuration options may be added in future releases of SQLite. 2200 ** Existing configuration options might be discontinued. Applications 2201 ** should check the return code from [sqlite3_db_config()] to make sure that 2202 ** the call worked. ^The [sqlite3_db_config()] interface will return a 2203 ** non-zero [error code] if a discontinued or unsupported configuration option 2204 ** is invoked. 2205 ** 2206 ** <dl> 2207 ** [[SQLITE_DBCONFIG_LOOKASIDE]] 2208 ** <dt>SQLITE_DBCONFIG_LOOKASIDE</dt> 2209 ** <dd> ^This option takes three additional arguments that determine the 2210 ** [lookaside memory allocator] configuration for the [database connection]. 2211 ** ^The first argument (the third parameter to [sqlite3_db_config()] is a 2212 ** pointer to a memory buffer to use for lookaside memory. 2213 ** ^The first argument after the SQLITE_DBCONFIG_LOOKASIDE verb 2214 ** may be NULL in which case SQLite will allocate the 2215 ** lookaside buffer itself using [sqlite3_malloc()]. ^The second argument is the 2216 ** size of each lookaside buffer slot. ^The third argument is the number of 2217 ** slots. The size of the buffer in the first argument must be greater than 2218 ** or equal to the product of the second and third arguments. The buffer 2219 ** must be aligned to an 8-byte boundary. ^If the second argument to 2220 ** SQLITE_DBCONFIG_LOOKASIDE is not a multiple of 8, it is internally 2221 ** rounded down to the next smaller multiple of 8. ^(The lookaside memory 2222 ** configuration for a database connection can only be changed when that 2223 ** connection is not currently using lookaside memory, or in other words 2224 ** when the "current value" returned by 2225 ** [sqlite3_db_status](D,[SQLITE_DBSTATUS_LOOKASIDE_USED],...) is zero. 2226 ** Any attempt to change the lookaside memory configuration when lookaside 2227 ** memory is in use leaves the configuration unchanged and returns 2228 ** [SQLITE_BUSY].)^</dd> 2229 ** 2230 ** [[SQLITE_DBCONFIG_ENABLE_FKEY]] 2231 ** <dt>SQLITE_DBCONFIG_ENABLE_FKEY</dt> 2232 ** <dd> ^This option is used to enable or disable the enforcement of 2233 ** [foreign key constraints]. There should be two additional arguments. 2234 ** The first argument is an integer which is 0 to disable FK enforcement, 2235 ** positive to enable FK enforcement or negative to leave FK enforcement 2236 ** unchanged. The second parameter is a pointer to an integer into which 2237 ** is written 0 or 1 to indicate whether FK enforcement is off or on 2238 ** following this call. The second parameter may be a NULL pointer, in 2239 ** which case the FK enforcement setting is not reported back. </dd> 2240 ** 2241 ** [[SQLITE_DBCONFIG_ENABLE_TRIGGER]] 2242 ** <dt>SQLITE_DBCONFIG_ENABLE_TRIGGER</dt> 2243 ** <dd> ^This option is used to enable or disable [CREATE TRIGGER | triggers]. 2244 ** There should be two additional arguments. 2245 ** The first argument is an integer which is 0 to disable triggers, 2246 ** positive to enable triggers or negative to leave the setting unchanged. 2247 ** The second parameter is a pointer to an integer into which 2248 ** is written 0 or 1 to indicate whether triggers are disabled or enabled 2249 ** following this call. The second parameter may be a NULL pointer, in 2250 ** which case the trigger setting is not reported back. 2251 ** 2252 ** <p>Originally this option disabled all triggers. ^(However, since 2253 ** SQLite version 3.35.0, TEMP triggers are still allowed even if 2254 ** this option is off. So, in other words, this option now only disables 2255 ** triggers in the main database schema or in the schemas of ATTACH-ed 2256 ** databases.)^ </dd> 2257 ** 2258 ** [[SQLITE_DBCONFIG_ENABLE_VIEW]] 2259 ** <dt>SQLITE_DBCONFIG_ENABLE_VIEW</dt> 2260 ** <dd> ^This option is used to enable or disable [CREATE VIEW | views]. 2261 ** There should be two additional arguments. 2262 ** The first argument is an integer which is 0 to disable views, 2263 ** positive to enable views or negative to leave the setting unchanged. 2264 ** The second parameter is a pointer to an integer into which 2265 ** is written 0 or 1 to indicate whether views are disabled or enabled 2266 ** following this call. The second parameter may be a NULL pointer, in 2267 ** which case the view setting is not reported back. 2268 ** 2269 ** <p>Originally this option disabled all views. ^(However, since 2270 ** SQLite version 3.35.0, TEMP views are still allowed even if 2271 ** this option is off. So, in other words, this option now only disables 2272 ** views in the main database schema or in the schemas of ATTACH-ed 2273 ** databases.)^ </dd> 2274 ** 2275 ** [[SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER]] 2276 ** <dt>SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER</dt> 2277 ** <dd> ^This option is used to enable or disable the 2278 ** [fts3_tokenizer()] function which is part of the 2279 ** [FTS3] full-text search engine extension. 2280 ** There should be two additional arguments. 2281 ** The first argument is an integer which is 0 to disable fts3_tokenizer() or 2282 ** positive to enable fts3_tokenizer() or negative to leave the setting 2283 ** unchanged. 2284 ** The second parameter is a pointer to an integer into which 2285 ** is written 0 or 1 to indicate whether fts3_tokenizer is disabled or enabled 2286 ** following this call. The second parameter may be a NULL pointer, in 2287 ** which case the new setting is not reported back. </dd> 2288 ** 2289 ** [[SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION]] 2290 ** <dt>SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION</dt> 2291 ** <dd> ^This option is used to enable or disable the [sqlite3_load_extension()] 2292 ** interface independently of the [load_extension()] SQL function. 2293 ** The [sqlite3_enable_load_extension()] API enables or disables both the 2294 ** C-API [sqlite3_load_extension()] and the SQL function [load_extension()]. 2295 ** There should be two additional arguments. 2296 ** When the first argument to this interface is 1, then only the C-API is 2297 ** enabled and the SQL function remains disabled. If the first argument to 2298 ** this interface is 0, then both the C-API and the SQL function are disabled. 2299 ** If the first argument is -1, then no changes are made to state of either the 2300 ** C-API or the SQL function. 2301 ** The second parameter is a pointer to an integer into which 2302 ** is written 0 or 1 to indicate whether [sqlite3_load_extension()] interface 2303 ** is disabled or enabled following this call. The second parameter may 2304 ** be a NULL pointer, in which case the new setting is not reported back. 2305 ** </dd> 2306 ** 2307 ** [[SQLITE_DBCONFIG_MAINDBNAME]] <dt>SQLITE_DBCONFIG_MAINDBNAME</dt> 2308 ** <dd> ^This option is used to change the name of the "main" database 2309 ** schema. ^The sole argument is a pointer to a constant UTF8 string 2310 ** which will become the new schema name in place of "main". ^SQLite 2311 ** does not make a copy of the new main schema name string, so the application 2312 ** must ensure that the argument passed into this DBCONFIG option is unchanged 2313 ** until after the database connection closes. 2314 ** </dd> 2315 ** 2316 ** [[SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE]] 2317 ** <dt>SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE</dt> 2318 ** <dd> Usually, when a database in wal mode is closed or detached from a 2319 ** database handle, SQLite checks if this will mean that there are now no 2320 ** connections at all to the database. If so, it performs a checkpoint 2321 ** operation before closing the connection. This option may be used to 2322 ** override this behavior. The first parameter passed to this operation 2323 ** is an integer - positive to disable checkpoints-on-close, or zero (the 2324 ** default) to enable them, and negative to leave the setting unchanged. 2325 ** The second parameter is a pointer to an integer 2326 ** into which is written 0 or 1 to indicate whether checkpoints-on-close 2327 ** have been disabled - 0 if they are not disabled, 1 if they are. 2328 ** </dd> 2329 ** 2330 ** [[SQLITE_DBCONFIG_ENABLE_QPSG]] <dt>SQLITE_DBCONFIG_ENABLE_QPSG</dt> 2331 ** <dd>^(The SQLITE_DBCONFIG_ENABLE_QPSG option activates or deactivates 2332 ** the [query planner stability guarantee] (QPSG). When the QPSG is active, 2333 ** a single SQL query statement will always use the same algorithm regardless 2334 ** of values of [bound parameters].)^ The QPSG disables some query optimizations 2335 ** that look at the values of bound parameters, which can make some queries 2336 ** slower. But the QPSG has the advantage of more predictable behavior. With 2337 ** the QPSG active, SQLite will always use the same query plan in the field as 2338 ** was used during testing in the lab. 2339 ** The first argument to this setting is an integer which is 0 to disable 2340 ** the QPSG, positive to enable QPSG, or negative to leave the setting 2341 ** unchanged. The second parameter is a pointer to an integer into which 2342 ** is written 0 or 1 to indicate whether the QPSG is disabled or enabled 2343 ** following this call. 2344 ** </dd> 2345 ** 2346 ** [[SQLITE_DBCONFIG_TRIGGER_EQP]] <dt>SQLITE_DBCONFIG_TRIGGER_EQP</dt> 2347 ** <dd> By default, the output of EXPLAIN QUERY PLAN commands does not 2348 ** include output for any operations performed by trigger programs. This 2349 ** option is used to set or clear (the default) a flag that governs this 2350 ** behavior. The first parameter passed to this operation is an integer - 2351 ** positive to enable output for trigger programs, or zero to disable it, 2352 ** or negative to leave the setting unchanged. 2353 ** The second parameter is a pointer to an integer into which is written 2354 ** 0 or 1 to indicate whether output-for-triggers has been disabled - 0 if 2355 ** it is not disabled, 1 if it is. 2356 ** </dd> 2357 ** 2358 ** [[SQLITE_DBCONFIG_RESET_DATABASE]] <dt>SQLITE_DBCONFIG_RESET_DATABASE</dt> 2359 ** <dd> Set the SQLITE_DBCONFIG_RESET_DATABASE flag and then run 2360 ** [VACUUM] in order to reset a database back to an empty database 2361 ** with no schema and no content. The following process works even for 2362 ** a badly corrupted database file: 2363 ** <ol> 2364 ** <li> If the database connection is newly opened, make sure it has read the 2365 ** database schema by preparing then discarding some query against the 2366 ** database, or calling sqlite3_table_column_metadata(), ignoring any 2367 ** errors. This step is only necessary if the application desires to keep 2368 ** the database in WAL mode after the reset if it was in WAL mode before 2369 ** the reset. 2370 ** <li> sqlite3_db_config(db, SQLITE_DBCONFIG_RESET_DATABASE, 1, 0); 2371 ** <li> [sqlite3_exec](db, "[VACUUM]", 0, 0, 0); 2372 ** <li> sqlite3_db_config(db, SQLITE_DBCONFIG_RESET_DATABASE, 0, 0); 2373 ** </ol> 2374 ** Because resetting a database is destructive and irreversible, the 2375 ** process requires the use of this obscure API and multiple steps to 2376 ** help ensure that it does not happen by accident. Because this 2377 ** feature must be capable of resetting corrupt databases, and 2378 ** shutting down virtual tables may require access to that corrupt 2379 ** storage, the library must abandon any installed virtual tables 2380 ** without calling their xDestroy() methods. 2381 ** 2382 ** [[SQLITE_DBCONFIG_DEFENSIVE]] <dt>SQLITE_DBCONFIG_DEFENSIVE</dt> 2383 ** <dd>The SQLITE_DBCONFIG_DEFENSIVE option activates or deactivates the 2384 ** "defensive" flag for a database connection. When the defensive 2385 ** flag is enabled, language features that allow ordinary SQL to 2386 ** deliberately corrupt the database file are disabled. The disabled 2387 ** features include but are not limited to the following: 2388 ** <ul> 2389 ** <li> The [PRAGMA writable_schema=ON] statement. 2390 ** <li> The [PRAGMA journal_mode=OFF] statement. 2391 ** <li> The [PRAGMA schema_version=N] statement. 2392 ** <li> Writes to the [sqlite_dbpage] virtual table. 2393 ** <li> Direct writes to [shadow tables]. 2394 ** </ul> 2395 ** </dd> 2396 ** 2397 ** [[SQLITE_DBCONFIG_WRITABLE_SCHEMA]] <dt>SQLITE_DBCONFIG_WRITABLE_SCHEMA</dt> 2398 ** <dd>The SQLITE_DBCONFIG_WRITABLE_SCHEMA option activates or deactivates the 2399 ** "writable_schema" flag. This has the same effect and is logically equivalent 2400 ** to setting [PRAGMA writable_schema=ON] or [PRAGMA writable_schema=OFF]. 2401 ** The first argument to this setting is an integer which is 0 to disable 2402 ** the writable_schema, positive to enable writable_schema, or negative to 2403 ** leave the setting unchanged. The second parameter is a pointer to an 2404 ** integer into which is written 0 or 1 to indicate whether the writable_schema 2405 ** is enabled or disabled following this call. 2406 ** </dd> 2407 ** 2408 ** [[SQLITE_DBCONFIG_LEGACY_ALTER_TABLE]] 2409 ** <dt>SQLITE_DBCONFIG_LEGACY_ALTER_TABLE</dt> 2410 ** <dd>The SQLITE_DBCONFIG_LEGACY_ALTER_TABLE option activates or deactivates 2411 ** the legacy behavior of the [ALTER TABLE RENAME] command such it 2412 ** behaves as it did prior to [version 3.24.0] (2018-06-04). See the 2413 ** "Compatibility Notice" on the [ALTER TABLE RENAME documentation] for 2414 ** additional information. This feature can also be turned on and off 2415 ** using the [PRAGMA legacy_alter_table] statement. 2416 ** </dd> 2417 ** 2418 ** [[SQLITE_DBCONFIG_DQS_DML]] 2419 ** <dt>SQLITE_DBCONFIG_DQS_DML</dt> 2420 ** <dd>The SQLITE_DBCONFIG_DQS_DML option activates or deactivates 2421 ** the legacy [double-quoted string literal] misfeature for DML statements 2422 ** only, that is DELETE, INSERT, SELECT, and UPDATE statements. The 2423 ** default value of this setting is determined by the [-DSQLITE_DQS] 2424 ** compile-time option. 2425 ** </dd> 2426 ** 2427 ** [[SQLITE_DBCONFIG_DQS_DDL]] 2428 ** <dt>SQLITE_DBCONFIG_DQS_DDL</dt> 2429 ** <dd>The SQLITE_DBCONFIG_DQS option activates or deactivates 2430 ** the legacy [double-quoted string literal] misfeature for DDL statements, 2431 ** such as CREATE TABLE and CREATE INDEX. The 2432 ** default value of this setting is determined by the [-DSQLITE_DQS] 2433 ** compile-time option. 2434 ** </dd> 2435 ** 2436 ** [[SQLITE_DBCONFIG_TRUSTED_SCHEMA]] 2437 ** <dt>SQLITE_DBCONFIG_TRUSTED_SCHEMA</dt> 2438 ** <dd>The SQLITE_DBCONFIG_TRUSTED_SCHEMA option tells SQLite to 2439 ** assume that database schemas are untainted by malicious content. 2440 ** When the SQLITE_DBCONFIG_TRUSTED_SCHEMA option is disabled, SQLite 2441 ** takes additional defensive steps to protect the application from harm 2442 ** including: 2443 ** <ul> 2444 ** <li> Prohibit the use of SQL functions inside triggers, views, 2445 ** CHECK constraints, DEFAULT clauses, expression indexes, 2446 ** partial indexes, or generated columns 2447 ** unless those functions are tagged with [SQLITE_INNOCUOUS]. 2448 ** <li> Prohibit the use of virtual tables inside of triggers or views 2449 ** unless those virtual tables are tagged with [SQLITE_VTAB_INNOCUOUS]. 2450 ** </ul> 2451 ** This setting defaults to "on" for legacy compatibility, however 2452 ** all applications are advised to turn it off if possible. This setting 2453 ** can also be controlled using the [PRAGMA trusted_schema] statement. 2454 ** </dd> 2455 ** 2456 ** [[SQLITE_DBCONFIG_LEGACY_FILE_FORMAT]] 2457 ** <dt>SQLITE_DBCONFIG_LEGACY_FILE_FORMAT</dt> 2458 ** <dd>The SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option activates or deactivates 2459 ** the legacy file format flag. When activated, this flag causes all newly 2460 ** created database file to have a schema format version number (the 4-byte 2461 ** integer found at offset 44 into the database header) of 1. This in turn 2462 ** means that the resulting database file will be readable and writable by 2463 ** any SQLite version back to 3.0.0 ([dateof:3.0.0]). Without this setting, 2464 ** newly created databases are generally not understandable by SQLite versions 2465 ** prior to 3.3.0 ([dateof:3.3.0]). As these words are written, there 2466 ** is now scarcely any need to generate database files that are compatible 2467 ** all the way back to version 3.0.0, and so this setting is of little 2468 ** practical use, but is provided so that SQLite can continue to claim the 2469 ** ability to generate new database files that are compatible with version 2470 ** 3.0.0. 2471 ** <p>Note that when the SQLITE_DBCONFIG_LEGACY_FILE_FORMAT setting is on, 2472 ** the [VACUUM] command will fail with an obscure error when attempting to 2473 ** process a table with generated columns and a descending index. This is 2474 ** not considered a bug since SQLite versions 3.3.0 and earlier do not support 2475 ** either generated columns or descending indexes. 2476 ** </dd> 2477 ** 2478 ** [[SQLITE_DBCONFIG_STMT_SCANSTATUS]] 2479 ** <dt>SQLITE_DBCONFIG_STMT_SCANSTATUS</dt> 2480 ** <dd>The SQLITE_DBCONFIG_STMT_SCANSTATUS option is only useful in 2481 ** SQLITE_ENABLE_STMT_SCANSTATUS builds. In this case, it sets or clears 2482 ** a flag that enables collection of the sqlite3_stmt_scanstatus_v2() 2483 ** statistics. For statistics to be collected, the flag must be set on 2484 ** the database handle both when the SQL statement is prepared and when it 2485 ** is stepped. The flag is set (collection of statistics is enabled) 2486 ** by default. This option takes two arguments: an integer and a pointer to 2487 ** an integer.. The first argument is 1, 0, or -1 to enable, disable, or 2488 ** leave unchanged the statement scanstatus option. If the second argument 2489 ** is not NULL, then the value of the statement scanstatus setting after 2490 ** processing the first argument is written into the integer that the second 2491 ** argument points to. 2492 ** </dd> 2493 ** 2494 ** [[SQLITE_DBCONFIG_REVERSE_SCANORDER]] 2495 ** <dt>SQLITE_DBCONFIG_REVERSE_SCANORDER</dt> 2496 ** <dd>The SQLITE_DBCONFIG_REVERSE_SCANORDER option changes the default order 2497 ** in which tables and indexes are scanned so that the scans start at the end 2498 ** and work toward the beginning rather than starting at the beginning and 2499 ** working toward the end. Setting SQLITE_DBCONFIG_REVERSE_SCANORDER is the 2500 ** same as setting [PRAGMA reverse_unordered_selects]. This option takes 2501 ** two arguments which are an integer and a pointer to an integer. The first 2502 ** argument is 1, 0, or -1 to enable, disable, or leave unchanged the 2503 ** reverse scan order flag, respectively. If the second argument is not NULL, 2504 ** then 0 or 1 is written into the integer that the second argument points to 2505 ** depending on if the reverse scan order flag is set after processing the 2506 ** first argument. 2507 ** </dd> 2508 ** 2509 ** </dl> 2510 */ 2511 #define SQLITE_DBCONFIG_MAINDBNAME 1000 /* const char* */ 2512 #define SQLITE_DBCONFIG_LOOKASIDE 1001 /* void* int int */ 2513 #define SQLITE_DBCONFIG_ENABLE_FKEY 1002 /* int int* */ 2514 #define SQLITE_DBCONFIG_ENABLE_TRIGGER 1003 /* int int* */ 2515 #define SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER 1004 /* int int* */ 2516 #define SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION 1005 /* int int* */ 2517 #define SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE 1006 /* int int* */ 2518 #define SQLITE_DBCONFIG_ENABLE_QPSG 1007 /* int int* */ 2519 #define SQLITE_DBCONFIG_TRIGGER_EQP 1008 /* int int* */ 2520 #define SQLITE_DBCONFIG_RESET_DATABASE 1009 /* int int* */ 2521 #define SQLITE_DBCONFIG_DEFENSIVE 1010 /* int int* */ 2522 #define SQLITE_DBCONFIG_WRITABLE_SCHEMA 1011 /* int int* */ 2523 #define SQLITE_DBCONFIG_LEGACY_ALTER_TABLE 1012 /* int int* */ 2524 #define SQLITE_DBCONFIG_DQS_DML 1013 /* int int* */ 2525 #define SQLITE_DBCONFIG_DQS_DDL 1014 /* int int* */ 2526 #define SQLITE_DBCONFIG_ENABLE_VIEW 1015 /* int int* */ 2527 #define SQLITE_DBCONFIG_LEGACY_FILE_FORMAT 1016 /* int int* */ 2528 #define SQLITE_DBCONFIG_TRUSTED_SCHEMA 1017 /* int int* */ 2529 #define SQLITE_DBCONFIG_STMT_SCANSTATUS 1018 /* int int* */ 2530 #define SQLITE_DBCONFIG_REVERSE_SCANORDER 1019 /* int int* */ 2531 #define SQLITE_DBCONFIG_MAX 1019 /* Largest DBCONFIG */ 2532 2533 /* 2534 ** CAPI3REF: Enable Or Disable Extended Result Codes 2535 ** METHOD: sqlite3 2536 ** 2537 ** ^The sqlite3_extended_result_codes() routine enables or disables the 2538 ** [extended result codes] feature of SQLite. ^The extended result 2539 ** codes are disabled by default for historical compatibility. 2540 */ 2541 SQLITE_API int sqlite3_extended_result_codes(sqlite3*, int onoff); 2542 2543 /* 2544 ** CAPI3REF: Last Insert Rowid 2545 ** METHOD: sqlite3 2546 ** 2547 ** ^Each entry in most SQLite tables (except for [WITHOUT ROWID] tables) 2548 ** has a unique 64-bit signed 2549 ** integer key called the [ROWID | "rowid"]. ^The rowid is always available 2550 ** as an undeclared column named ROWID, OID, or _ROWID_ as long as those 2551 ** names are not also used by explicitly declared columns. ^If 2552 ** the table has a column of type [INTEGER PRIMARY KEY] then that column 2553 ** is another alias for the rowid. 2554 ** 2555 ** ^The sqlite3_last_insert_rowid(D) interface usually returns the [rowid] of 2556 ** the most recent successful [INSERT] into a rowid table or [virtual table] 2557 ** on database connection D. ^Inserts into [WITHOUT ROWID] tables are not 2558 ** recorded. ^If no successful [INSERT]s into rowid tables have ever occurred 2559 ** on the database connection D, then sqlite3_last_insert_rowid(D) returns 2560 ** zero. 2561 ** 2562 ** As well as being set automatically as rows are inserted into database 2563 ** tables, the value returned by this function may be set explicitly by 2564 ** [sqlite3_set_last_insert_rowid()] 2565 ** 2566 ** Some virtual table implementations may INSERT rows into rowid tables as 2567 ** part of committing a transaction (e.g. to flush data accumulated in memory 2568 ** to disk). In this case subsequent calls to this function return the rowid 2569 ** associated with these internal INSERT operations, which leads to 2570 ** unintuitive results. Virtual table implementations that do write to rowid 2571 ** tables in this way can avoid this problem by restoring the original 2572 ** rowid value using [sqlite3_set_last_insert_rowid()] before returning 2573 ** control to the user. 2574 ** 2575 ** ^(If an [INSERT] occurs within a trigger then this routine will 2576 ** return the [rowid] of the inserted row as long as the trigger is 2577 ** running. Once the trigger program ends, the value returned 2578 ** by this routine reverts to what it was before the trigger was fired.)^ 2579 ** 2580 ** ^An [INSERT] that fails due to a constraint violation is not a 2581 ** successful [INSERT] and does not change the value returned by this 2582 ** routine. ^Thus INSERT OR FAIL, INSERT OR IGNORE, INSERT OR ROLLBACK, 2583 ** and INSERT OR ABORT make no changes to the return value of this 2584 ** routine when their insertion fails. ^(When INSERT OR REPLACE 2585 ** encounters a constraint violation, it does not fail. The 2586 ** INSERT continues to completion after deleting rows that caused 2587 ** the constraint problem so INSERT OR REPLACE will always change 2588 ** the return value of this interface.)^ 2589 ** 2590 ** ^For the purposes of this routine, an [INSERT] is considered to 2591 ** be successful even if it is subsequently rolled back. 2592 ** 2593 ** This function is accessible to SQL statements via the 2594 ** [last_insert_rowid() SQL function]. 2595 ** 2596 ** If a separate thread performs a new [INSERT] on the same 2597 ** database connection while the [sqlite3_last_insert_rowid()] 2598 ** function is running and thus changes the last insert [rowid], 2599 ** then the value returned by [sqlite3_last_insert_rowid()] is 2600 ** unpredictable and might not equal either the old or the new 2601 ** last insert [rowid]. 2602 */ 2603 SQLITE_API sqlite3_int64 sqlite3_last_insert_rowid(sqlite3*); 2604 2605 /* 2606 ** CAPI3REF: Set the Last Insert Rowid value. 2607 ** METHOD: sqlite3 2608 ** 2609 ** The sqlite3_set_last_insert_rowid(D, R) method allows the application to 2610 ** set the value returned by calling sqlite3_last_insert_rowid(D) to R 2611 ** without inserting a row into the database. 2612 */ 2613 SQLITE_API void sqlite3_set_last_insert_rowid(sqlite3*,sqlite3_int64); 2614 2615 /* 2616 ** CAPI3REF: Count The Number Of Rows Modified 2617 ** METHOD: sqlite3 2618 ** 2619 ** ^These functions return the number of rows modified, inserted or 2620 ** deleted by the most recently completed INSERT, UPDATE or DELETE 2621 ** statement on the database connection specified by the only parameter. 2622 ** The two functions are identical except for the type of the return value 2623 ** and that if the number of rows modified by the most recent INSERT, UPDATE 2624 ** or DELETE is greater than the maximum value supported by type "int", then 2625 ** the return value of sqlite3_changes() is undefined. ^Executing any other 2626 ** type of SQL statement does not modify the value returned by these functions. 2627 ** 2628 ** ^Only changes made directly by the INSERT, UPDATE or DELETE statement are 2629 ** considered - auxiliary changes caused by [CREATE TRIGGER | triggers], 2630 ** [foreign key actions] or [REPLACE] constraint resolution are not counted. 2631 ** 2632 ** Changes to a view that are intercepted by 2633 ** [INSTEAD OF trigger | INSTEAD OF triggers] are not counted. ^The value 2634 ** returned by sqlite3_changes() immediately after an INSERT, UPDATE or 2635 ** DELETE statement run on a view is always zero. Only changes made to real 2636 ** tables are counted. 2637 ** 2638 ** Things are more complicated if the sqlite3_changes() function is 2639 ** executed while a trigger program is running. This may happen if the 2640 ** program uses the [changes() SQL function], or if some other callback 2641 ** function invokes sqlite3_changes() directly. Essentially: 2642 ** 2643 ** <ul> 2644 ** <li> ^(Before entering a trigger program the value returned by 2645 ** sqlite3_changes() function is saved. After the trigger program 2646 ** has finished, the original value is restored.)^ 2647 ** 2648 ** <li> ^(Within a trigger program each INSERT, UPDATE and DELETE 2649 ** statement sets the value returned by sqlite3_changes() 2650 ** upon completion as normal. Of course, this value will not include 2651 ** any changes performed by sub-triggers, as the sqlite3_changes() 2652 ** value will be saved and restored after each sub-trigger has run.)^ 2653 ** </ul> 2654 ** 2655 ** ^This means that if the changes() SQL function (or similar) is used 2656 ** by the first INSERT, UPDATE or DELETE statement within a trigger, it 2657 ** returns the value as set when the calling statement began executing. 2658 ** ^If it is used by the second or subsequent such statement within a trigger 2659 ** program, the value returned reflects the number of rows modified by the 2660 ** previous INSERT, UPDATE or DELETE statement within the same trigger. 2661 ** 2662 ** If a separate thread makes changes on the same database connection 2663 ** while [sqlite3_changes()] is running then the value returned 2664 ** is unpredictable and not meaningful. 2665 ** 2666 ** See also: 2667 ** <ul> 2668 ** <li> the [sqlite3_total_changes()] interface 2669 ** <li> the [count_changes pragma] 2670 ** <li> the [changes() SQL function] 2671 ** <li> the [data_version pragma] 2672 ** </ul> 2673 */ 2674 SQLITE_API int sqlite3_changes(sqlite3*); 2675 SQLITE_API sqlite3_int64 sqlite3_changes64(sqlite3*); 2676 2677 /* 2678 ** CAPI3REF: Total Number Of Rows Modified 2679 ** METHOD: sqlite3 2680 ** 2681 ** ^These functions return the total number of rows inserted, modified or 2682 ** deleted by all [INSERT], [UPDATE] or [DELETE] statements completed 2683 ** since the database connection was opened, including those executed as 2684 ** part of trigger programs. The two functions are identical except for the 2685 ** type of the return value and that if the number of rows modified by the 2686 ** connection exceeds the maximum value supported by type "int", then 2687 ** the return value of sqlite3_total_changes() is undefined. ^Executing 2688 ** any other type of SQL statement does not affect the value returned by 2689 ** sqlite3_total_changes(). 2690 ** 2691 ** ^Changes made as part of [foreign key actions] are included in the 2692 ** count, but those made as part of REPLACE constraint resolution are 2693 ** not. ^Changes to a view that are intercepted by INSTEAD OF triggers 2694 ** are not counted. 2695 ** 2696 ** The [sqlite3_total_changes(D)] interface only reports the number 2697 ** of rows that changed due to SQL statement run against database 2698 ** connection D. Any changes by other database connections are ignored. 2699 ** To detect changes against a database file from other database 2700 ** connections use the [PRAGMA data_version] command or the 2701 ** [SQLITE_FCNTL_DATA_VERSION] [file control]. 2702 ** 2703 ** If a separate thread makes changes on the same database connection 2704 ** while [sqlite3_total_changes()] is running then the value 2705 ** returned is unpredictable and not meaningful. 2706 ** 2707 ** See also: 2708 ** <ul> 2709 ** <li> the [sqlite3_changes()] interface 2710 ** <li> the [count_changes pragma] 2711 ** <li> the [changes() SQL function] 2712 ** <li> the [data_version pragma] 2713 ** <li> the [SQLITE_FCNTL_DATA_VERSION] [file control] 2714 ** </ul> 2715 */ 2716 SQLITE_API int sqlite3_total_changes(sqlite3*); 2717 SQLITE_API sqlite3_int64 sqlite3_total_changes64(sqlite3*); 2718 2719 /* 2720 ** CAPI3REF: Interrupt A Long-Running Query 2721 ** METHOD: sqlite3 2722 ** 2723 ** ^This function causes any pending database operation to abort and 2724 ** return at its earliest opportunity. This routine is typically 2725 ** called in response to a user action such as pressing "Cancel" 2726 ** or Ctrl-C where the user wants a long query operation to halt 2727 ** immediately. 2728 ** 2729 ** ^It is safe to call this routine from a thread different from the 2730 ** thread that is currently running the database operation. But it 2731 ** is not safe to call this routine with a [database connection] that 2732 ** is closed or might close before sqlite3_interrupt() returns. 2733 ** 2734 ** ^If an SQL operation is very nearly finished at the time when 2735 ** sqlite3_interrupt() is called, then it might not have an opportunity 2736 ** to be interrupted and might continue to completion. 2737 ** 2738 ** ^An SQL operation that is interrupted will return [SQLITE_INTERRUPT]. 2739 ** ^If the interrupted SQL operation is an INSERT, UPDATE, or DELETE 2740 ** that is inside an explicit transaction, then the entire transaction 2741 ** will be rolled back automatically. 2742 ** 2743 ** ^The sqlite3_interrupt(D) call is in effect until all currently running 2744 ** SQL statements on [database connection] D complete. ^Any new SQL statements 2745 ** that are started after the sqlite3_interrupt() call and before the 2746 ** running statement count reaches zero are interrupted as if they had been 2747 ** running prior to the sqlite3_interrupt() call. ^New SQL statements 2748 ** that are started after the running statement count reaches zero are 2749 ** not effected by the sqlite3_interrupt(). 2750 ** ^A call to sqlite3_interrupt(D) that occurs when there are no running 2751 ** SQL statements is a no-op and has no effect on SQL statements 2752 ** that are started after the sqlite3_interrupt() call returns. 2753 ** 2754 ** ^The [sqlite3_is_interrupted(D)] interface can be used to determine whether 2755 ** or not an interrupt is currently in effect for [database connection] D. 2756 ** It returns 1 if an interrupt is currently in effect, or 0 otherwise. 2757 */ 2758 SQLITE_API void sqlite3_interrupt(sqlite3*); 2759 SQLITE_API int sqlite3_is_interrupted(sqlite3*); 2760 2761 /* 2762 ** CAPI3REF: Determine If An SQL Statement Is Complete 2763 ** 2764 ** These routines are useful during command-line input to determine if the 2765 ** currently entered text seems to form a complete SQL statement or 2766 ** if additional input is needed before sending the text into 2767 ** SQLite for parsing. ^These routines return 1 if the input string 2768 ** appears to be a complete SQL statement. ^A statement is judged to be 2769 ** complete if it ends with a semicolon token and is not a prefix of a 2770 ** well-formed CREATE TRIGGER statement. ^Semicolons that are embedded within 2771 ** string literals or quoted identifier names or comments are not 2772 ** independent tokens (they are part of the token in which they are 2773 ** embedded) and thus do not count as a statement terminator. ^Whitespace 2774 ** and comments that follow the final semicolon are ignored. 2775 ** 2776 ** ^These routines return 0 if the statement is incomplete. ^If a 2777 ** memory allocation fails, then SQLITE_NOMEM is returned. 2778 ** 2779 ** ^These routines do not parse the SQL statements thus 2780 ** will not detect syntactically incorrect SQL. 2781 ** 2782 ** ^(If SQLite has not been initialized using [sqlite3_initialize()] prior 2783 ** to invoking sqlite3_complete16() then sqlite3_initialize() is invoked 2784 ** automatically by sqlite3_complete16(). If that initialization fails, 2785 ** then the return value from sqlite3_complete16() will be non-zero 2786 ** regardless of whether or not the input SQL is complete.)^ 2787 ** 2788 ** The input to [sqlite3_complete()] must be a zero-terminated 2789 ** UTF-8 string. 2790 ** 2791 ** The input to [sqlite3_complete16()] must be a zero-terminated 2792 ** UTF-16 string in native byte order. 2793 */ 2794 SQLITE_API int sqlite3_complete(const char *sql); 2795 SQLITE_API int sqlite3_complete16(const void *sql); 2796 2797 /* 2798 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors 2799 ** KEYWORDS: {busy-handler callback} {busy handler} 2800 ** METHOD: sqlite3 2801 ** 2802 ** ^The sqlite3_busy_handler(D,X,P) routine sets a callback function X 2803 ** that might be invoked with argument P whenever 2804 ** an attempt is made to access a database table associated with 2805 ** [database connection] D when another thread 2806 ** or process has the table locked. 2807 ** The sqlite3_busy_handler() interface is used to implement 2808 ** [sqlite3_busy_timeout()] and [PRAGMA busy_timeout]. 2809 ** 2810 ** ^If the busy callback is NULL, then [SQLITE_BUSY] 2811 ** is returned immediately upon encountering the lock. ^If the busy callback 2812 ** is not NULL, then the callback might be invoked with two arguments. 2813 ** 2814 ** ^The first argument to the busy handler is a copy of the void* pointer which 2815 ** is the third argument to sqlite3_busy_handler(). ^The second argument to 2816 ** the busy handler callback is the number of times that the busy handler has 2817 ** been invoked previously for the same locking event. ^If the 2818 ** busy callback returns 0, then no additional attempts are made to 2819 ** access the database and [SQLITE_BUSY] is returned 2820 ** to the application. 2821 ** ^If the callback returns non-zero, then another attempt 2822 ** is made to access the database and the cycle repeats. 2823 ** 2824 ** The presence of a busy handler does not guarantee that it will be invoked 2825 ** when there is lock contention. ^If SQLite determines that invoking the busy 2826 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY] 2827 ** to the application instead of invoking the 2828 ** busy handler. 2829 ** Consider a scenario where one process is holding a read lock that 2830 ** it is trying to promote to a reserved lock and 2831 ** a second process is holding a reserved lock that it is trying 2832 ** to promote to an exclusive lock. The first process cannot proceed 2833 ** because it is blocked by the second and the second process cannot 2834 ** proceed because it is blocked by the first. If both processes 2835 ** invoke the busy handlers, neither will make any progress. Therefore, 2836 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this 2837 ** will induce the first process to release its read lock and allow 2838 ** the second process to proceed. 2839 ** 2840 ** ^The default busy callback is NULL. 2841 ** 2842 ** ^(There can only be a single busy handler defined for each 2843 ** [database connection]. Setting a new busy handler clears any 2844 ** previously set handler.)^ ^Note that calling [sqlite3_busy_timeout()] 2845 ** or evaluating [PRAGMA busy_timeout=N] will change the 2846 ** busy handler and thus clear any previously set busy handler. 2847 ** 2848 ** The busy callback should not take any actions which modify the 2849 ** database connection that invoked the busy handler. In other words, 2850 ** the busy handler is not reentrant. Any such actions 2851 ** result in undefined behavior. 2852 ** 2853 ** A busy handler must not close the database connection 2854 ** or [prepared statement] that invoked the busy handler. 2855 */ 2856 SQLITE_API int sqlite3_busy_handler(sqlite3*,int(*)(void*,int),void*); 2857 2858 /* 2859 ** CAPI3REF: Set A Busy Timeout 2860 ** METHOD: sqlite3 2861 ** 2862 ** ^This routine sets a [sqlite3_busy_handler | busy handler] that sleeps 2863 ** for a specified amount of time when a table is locked. ^The handler 2864 ** will sleep multiple times until at least "ms" milliseconds of sleeping 2865 ** have accumulated. ^After at least "ms" milliseconds of sleeping, 2866 ** the handler returns 0 which causes [sqlite3_step()] to return 2867 ** [SQLITE_BUSY]. 2868 ** 2869 ** ^Calling this routine with an argument less than or equal to zero 2870 ** turns off all busy handlers. 2871 ** 2872 ** ^(There can only be a single busy handler for a particular 2873 ** [database connection] at any given moment. If another busy handler 2874 ** was defined (using [sqlite3_busy_handler()]) prior to calling 2875 ** this routine, that other busy handler is cleared.)^ 2876 ** 2877 ** See also: [PRAGMA busy_timeout] 2878 */ 2879 SQLITE_API int sqlite3_busy_timeout(sqlite3*, int ms); 2880 2881 /* 2882 ** CAPI3REF: Convenience Routines For Running Queries 2883 ** METHOD: sqlite3 2884 ** 2885 ** This is a legacy interface that is preserved for backwards compatibility. 2886 ** Use of this interface is not recommended. 2887 ** 2888 ** Definition: A <b>result table</b> is memory data structure created by the 2889 ** [sqlite3_get_table()] interface. A result table records the 2890 ** complete query results from one or more queries. 2891 ** 2892 ** The table conceptually has a number of rows and columns. But 2893 ** these numbers are not part of the result table itself. These 2894 ** numbers are obtained separately. Let N be the number of rows 2895 ** and M be the number of columns. 2896 ** 2897 ** A result table is an array of pointers to zero-terminated UTF-8 strings. 2898 ** There are (N+1)*M elements in the array. The first M pointers point 2899 ** to zero-terminated strings that contain the names of the columns. 2900 ** The remaining entries all point to query results. NULL values result 2901 ** in NULL pointers. All other values are in their UTF-8 zero-terminated 2902 ** string representation as returned by [sqlite3_column_text()]. 2903 ** 2904 ** A result table might consist of one or more memory allocations. 2905 ** It is not safe to pass a result table directly to [sqlite3_free()]. 2906 ** A result table should be deallocated using [sqlite3_free_table()]. 2907 ** 2908 ** ^(As an example of the result table format, suppose a query result 2909 ** is as follows: 2910 ** 2911 ** <blockquote><pre> 2912 ** Name | Age 2913 ** ----------------------- 2914 ** Alice | 43 2915 ** Bob | 28 2916 ** Cindy | 21 2917 ** </pre></blockquote> 2918 ** 2919 ** There are two columns (M==2) and three rows (N==3). Thus the 2920 ** result table has 8 entries. Suppose the result table is stored 2921 ** in an array named azResult. Then azResult holds this content: 2922 ** 2923 ** <blockquote><pre> 2924 ** azResult[0] = "Name"; 2925 ** azResult[1] = "Age"; 2926 ** azResult[2] = "Alice"; 2927 ** azResult[3] = "43"; 2928 ** azResult[4] = "Bob"; 2929 ** azResult[5] = "28"; 2930 ** azResult[6] = "Cindy"; 2931 ** azResult[7] = "21"; 2932 ** </pre></blockquote>)^ 2933 ** 2934 ** ^The sqlite3_get_table() function evaluates one or more 2935 ** semicolon-separated SQL statements in the zero-terminated UTF-8 2936 ** string of its 2nd parameter and returns a result table to the 2937 ** pointer given in its 3rd parameter. 2938 ** 2939 ** After the application has finished with the result from sqlite3_get_table(), 2940 ** it must pass the result table pointer to sqlite3_free_table() in order to 2941 ** release the memory that was malloced. Because of the way the 2942 ** [sqlite3_malloc()] happens within sqlite3_get_table(), the calling 2943 ** function must not try to call [sqlite3_free()] directly. Only 2944 ** [sqlite3_free_table()] is able to release the memory properly and safely. 2945 ** 2946 ** The sqlite3_get_table() interface is implemented as a wrapper around 2947 ** [sqlite3_exec()]. The sqlite3_get_table() routine does not have access 2948 ** to any internal data structures of SQLite. It uses only the public 2949 ** interface defined here. As a consequence, errors that occur in the 2950 ** wrapper layer outside of the internal [sqlite3_exec()] call are not 2951 ** reflected in subsequent calls to [sqlite3_errcode()] or 2952 ** [sqlite3_errmsg()]. 2953 */ 2954 SQLITE_API int sqlite3_get_table( 2955 sqlite3 *db, /* An open database */ 2956 const char *zSql, /* SQL to be evaluated */ 2957 char ***pazResult, /* Results of the query */ 2958 int *pnRow, /* Number of result rows written here */ 2959 int *pnColumn, /* Number of result columns written here */ 2960 char **pzErrmsg /* Error msg written here */ 2961 ); 2962 SQLITE_API void sqlite3_free_table(char **result); 2963 2964 /* 2965 ** CAPI3REF: Formatted String Printing Functions 2966 ** 2967 ** These routines are work-alikes of the "printf()" family of functions 2968 ** from the standard C library. 2969 ** These routines understand most of the common formatting options from 2970 ** the standard library printf() 2971 ** plus some additional non-standard formats ([%q], [%Q], [%w], and [%z]). 2972 ** See the [built-in printf()] documentation for details. 2973 ** 2974 ** ^The sqlite3_mprintf() and sqlite3_vmprintf() routines write their 2975 ** results into memory obtained from [sqlite3_malloc64()]. 2976 ** The strings returned by these two routines should be 2977 ** released by [sqlite3_free()]. ^Both routines return a 2978 ** NULL pointer if [sqlite3_malloc64()] is unable to allocate enough 2979 ** memory to hold the resulting string. 2980 ** 2981 ** ^(The sqlite3_snprintf() routine is similar to "snprintf()" from 2982 ** the standard C library. The result is written into the 2983 ** buffer supplied as the second parameter whose size is given by 2984 ** the first parameter. Note that the order of the 2985 ** first two parameters is reversed from snprintf().)^ This is an 2986 ** historical accident that cannot be fixed without breaking 2987 ** backwards compatibility. ^(Note also that sqlite3_snprintf() 2988 ** returns a pointer to its buffer instead of the number of 2989 ** characters actually written into the buffer.)^ We admit that 2990 ** the number of characters written would be a more useful return 2991 ** value but we cannot change the implementation of sqlite3_snprintf() 2992 ** now without breaking compatibility. 2993 ** 2994 ** ^As long as the buffer size is greater than zero, sqlite3_snprintf() 2995 ** guarantees that the buffer is always zero-terminated. ^The first 2996 ** parameter "n" is the total size of the buffer, including space for 2997 ** the zero terminator. So the longest string that can be completely 2998 ** written will be n-1 characters. 2999 ** 3000 ** ^The sqlite3_vsnprintf() routine is a varargs version of sqlite3_snprintf(). 3001 ** 3002 ** See also: [built-in printf()], [printf() SQL function] 3003 */ 3004 SQLITE_API char *sqlite3_mprintf(const char*,...); 3005 SQLITE_API char *sqlite3_vmprintf(const char*, va_list); 3006 SQLITE_API char *sqlite3_snprintf(int,char*,const char*, ...); 3007 SQLITE_API char *sqlite3_vsnprintf(int,char*,const char*, va_list); 3008 3009 /* 3010 ** CAPI3REF: Memory Allocation Subsystem 3011 ** 3012 ** The SQLite core uses these three routines for all of its own 3013 ** internal memory allocation needs. "Core" in the previous sentence 3014 ** does not include operating-system specific [VFS] implementation. The 3015 ** Windows VFS uses native malloc() and free() for some operations. 3016 ** 3017 ** ^The sqlite3_malloc() routine returns a pointer to a block 3018 ** of memory at least N bytes in length, where N is the parameter. 3019 ** ^If sqlite3_malloc() is unable to obtain sufficient free 3020 ** memory, it returns a NULL pointer. ^If the parameter N to 3021 ** sqlite3_malloc() is zero or negative then sqlite3_malloc() returns 3022 ** a NULL pointer. 3023 ** 3024 ** ^The sqlite3_malloc64(N) routine works just like 3025 ** sqlite3_malloc(N) except that N is an unsigned 64-bit integer instead 3026 ** of a signed 32-bit integer. 3027 ** 3028 ** ^Calling sqlite3_free() with a pointer previously returned 3029 ** by sqlite3_malloc() or sqlite3_realloc() releases that memory so 3030 ** that it might be reused. ^The sqlite3_free() routine is 3031 ** a no-op if is called with a NULL pointer. Passing a NULL pointer 3032 ** to sqlite3_free() is harmless. After being freed, memory 3033 ** should neither be read nor written. Even reading previously freed 3034 ** memory might result in a segmentation fault or other severe error. 3035 ** Memory corruption, a segmentation fault, or other severe error 3036 ** might result if sqlite3_free() is called with a non-NULL pointer that 3037 ** was not obtained from sqlite3_malloc() or sqlite3_realloc(). 3038 ** 3039 ** ^The sqlite3_realloc(X,N) interface attempts to resize a 3040 ** prior memory allocation X to be at least N bytes. 3041 ** ^If the X parameter to sqlite3_realloc(X,N) 3042 ** is a NULL pointer then its behavior is identical to calling 3043 ** sqlite3_malloc(N). 3044 ** ^If the N parameter to sqlite3_realloc(X,N) is zero or 3045 ** negative then the behavior is exactly the same as calling 3046 ** sqlite3_free(X). 3047 ** ^sqlite3_realloc(X,N) returns a pointer to a memory allocation 3048 ** of at least N bytes in size or NULL if insufficient memory is available. 3049 ** ^If M is the size of the prior allocation, then min(N,M) bytes 3050 ** of the prior allocation are copied into the beginning of buffer returned 3051 ** by sqlite3_realloc(X,N) and the prior allocation is freed. 3052 ** ^If sqlite3_realloc(X,N) returns NULL and N is positive, then the 3053 ** prior allocation is not freed. 3054 ** 3055 ** ^The sqlite3_realloc64(X,N) interfaces works the same as 3056 ** sqlite3_realloc(X,N) except that N is a 64-bit unsigned integer instead 3057 ** of a 32-bit signed integer. 3058 ** 3059 ** ^If X is a memory allocation previously obtained from sqlite3_malloc(), 3060 ** sqlite3_malloc64(), sqlite3_realloc(), or sqlite3_realloc64(), then 3061 ** sqlite3_msize(X) returns the size of that memory allocation in bytes. 3062 ** ^The value returned by sqlite3_msize(X) might be larger than the number 3063 ** of bytes requested when X was allocated. ^If X is a NULL pointer then 3064 ** sqlite3_msize(X) returns zero. If X points to something that is not 3065 ** the beginning of memory allocation, or if it points to a formerly 3066 ** valid memory allocation that has now been freed, then the behavior 3067 ** of sqlite3_msize(X) is undefined and possibly harmful. 3068 ** 3069 ** ^The memory returned by sqlite3_malloc(), sqlite3_realloc(), 3070 ** sqlite3_malloc64(), and sqlite3_realloc64() 3071 ** is always aligned to at least an 8 byte boundary, or to a 3072 ** 4 byte boundary if the [SQLITE_4_BYTE_ALIGNED_MALLOC] compile-time 3073 ** option is used. 3074 ** 3075 ** The pointer arguments to [sqlite3_free()] and [sqlite3_realloc()] 3076 ** must be either NULL or else pointers obtained from a prior 3077 ** invocation of [sqlite3_malloc()] or [sqlite3_realloc()] that have 3078 ** not yet been released. 3079 ** 3080 ** The application must not read or write any part of 3081 ** a block of memory after it has been released using 3082 ** [sqlite3_free()] or [sqlite3_realloc()]. 3083 */ 3084 SQLITE_API void *sqlite3_malloc(int); 3085 SQLITE_API void *sqlite3_malloc64(sqlite3_uint64); 3086 SQLITE_API void *sqlite3_realloc(void*, int); 3087 SQLITE_API void *sqlite3_realloc64(void*, sqlite3_uint64); 3088 SQLITE_API void sqlite3_free(void*); 3089 SQLITE_API sqlite3_uint64 sqlite3_msize(void*); 3090 3091 /* 3092 ** CAPI3REF: Memory Allocator Statistics 3093 ** 3094 ** SQLite provides these two interfaces for reporting on the status 3095 ** of the [sqlite3_malloc()], [sqlite3_free()], and [sqlite3_realloc()] 3096 ** routines, which form the built-in memory allocation subsystem. 3097 ** 3098 ** ^The [sqlite3_memory_used()] routine returns the number of bytes 3099 ** of memory currently outstanding (malloced but not freed). 3100 ** ^The [sqlite3_memory_highwater()] routine returns the maximum 3101 ** value of [sqlite3_memory_used()] since the high-water mark 3102 ** was last reset. ^The values returned by [sqlite3_memory_used()] and 3103 ** [sqlite3_memory_highwater()] include any overhead 3104 ** added by SQLite in its implementation of [sqlite3_malloc()], 3105 ** but not overhead added by the any underlying system library 3106 ** routines that [sqlite3_malloc()] may call. 3107 ** 3108 ** ^The memory high-water mark is reset to the current value of 3109 ** [sqlite3_memory_used()] if and only if the parameter to 3110 ** [sqlite3_memory_highwater()] is true. ^The value returned 3111 ** by [sqlite3_memory_highwater(1)] is the high-water mark 3112 ** prior to the reset. 3113 */ 3114 SQLITE_API sqlite3_int64 sqlite3_memory_used(void); 3115 SQLITE_API sqlite3_int64 sqlite3_memory_highwater(int resetFlag); 3116 3117 /* 3118 ** CAPI3REF: Pseudo-Random Number Generator 3119 ** 3120 ** SQLite contains a high-quality pseudo-random number generator (PRNG) used to 3121 ** select random [ROWID | ROWIDs] when inserting new records into a table that 3122 ** already uses the largest possible [ROWID]. The PRNG is also used for 3123 ** the built-in random() and randomblob() SQL functions. This interface allows 3124 ** applications to access the same PRNG for other purposes. 3125 ** 3126 ** ^A call to this routine stores N bytes of randomness into buffer P. 3127 ** ^The P parameter can be a NULL pointer. 3128 ** 3129 ** ^If this routine has not been previously called or if the previous 3130 ** call had N less than one or a NULL pointer for P, then the PRNG is 3131 ** seeded using randomness obtained from the xRandomness method of 3132 ** the default [sqlite3_vfs] object. 3133 ** ^If the previous call to this routine had an N of 1 or more and a 3134 ** non-NULL P then the pseudo-randomness is generated 3135 ** internally and without recourse to the [sqlite3_vfs] xRandomness 3136 ** method. 3137 */ 3138 SQLITE_API void sqlite3_randomness(int N, void *P); 3139 3140 /* 3141 ** CAPI3REF: Compile-Time Authorization Callbacks 3142 ** METHOD: sqlite3 3143 ** KEYWORDS: {authorizer callback} 3144 ** 3145 ** ^This routine registers an authorizer callback with a particular 3146 ** [database connection], supplied in the first argument. 3147 ** ^The authorizer callback is invoked as SQL statements are being compiled 3148 ** by [sqlite3_prepare()] or its variants [sqlite3_prepare_v2()], 3149 ** [sqlite3_prepare_v3()], [sqlite3_prepare16()], [sqlite3_prepare16_v2()], 3150 ** and [sqlite3_prepare16_v3()]. ^At various 3151 ** points during the compilation process, as logic is being created 3152 ** to perform various actions, the authorizer callback is invoked to 3153 ** see if those actions are allowed. ^The authorizer callback should 3154 ** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the 3155 ** specific action but allow the SQL statement to continue to be 3156 ** compiled, or [SQLITE_DENY] to cause the entire SQL statement to be 3157 ** rejected with an error. ^If the authorizer callback returns 3158 ** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY] 3159 ** then the [sqlite3_prepare_v2()] or equivalent call that triggered 3160 ** the authorizer will fail with an error message. 3161 ** 3162 ** When the callback returns [SQLITE_OK], that means the operation 3163 ** requested is ok. ^When the callback returns [SQLITE_DENY], the 3164 ** [sqlite3_prepare_v2()] or equivalent call that triggered the 3165 ** authorizer will fail with an error message explaining that 3166 ** access is denied. 3167 ** 3168 ** ^The first parameter to the authorizer callback is a copy of the third 3169 ** parameter to the sqlite3_set_authorizer() interface. ^The second parameter 3170 ** to the callback is an integer [SQLITE_COPY | action code] that specifies 3171 ** the particular action to be authorized. ^The third through sixth parameters 3172 ** to the callback are either NULL pointers or zero-terminated strings 3173 ** that contain additional details about the action to be authorized. 3174 ** Applications must always be prepared to encounter a NULL pointer in any 3175 ** of the third through the sixth parameters of the authorization callback. 3176 ** 3177 ** ^If the action code is [SQLITE_READ] 3178 ** and the callback returns [SQLITE_IGNORE] then the 3179 ** [prepared statement] statement is constructed to substitute 3180 ** a NULL value in place of the table column that would have 3181 ** been read if [SQLITE_OK] had been returned. The [SQLITE_IGNORE] 3182 ** return can be used to deny an untrusted user access to individual 3183 ** columns of a table. 3184 ** ^When a table is referenced by a [SELECT] but no column values are 3185 ** extracted from that table (for example in a query like 3186 ** "SELECT count(*) FROM tab") then the [SQLITE_READ] authorizer callback 3187 ** is invoked once for that table with a column name that is an empty string. 3188 ** ^If the action code is [SQLITE_DELETE] and the callback returns 3189 ** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the 3190 ** [truncate optimization] is disabled and all rows are deleted individually. 3191 ** 3192 ** An authorizer is used when [sqlite3_prepare | preparing] 3193 ** SQL statements from an untrusted source, to ensure that the SQL statements 3194 ** do not try to access data they are not allowed to see, or that they do not 3195 ** try to execute malicious statements that damage the database. For 3196 ** example, an application may allow a user to enter arbitrary 3197 ** SQL queries for evaluation by a database. But the application does 3198 ** not want the user to be able to make arbitrary changes to the 3199 ** database. An authorizer could then be put in place while the 3200 ** user-entered SQL is being [sqlite3_prepare | prepared] that 3201 ** disallows everything except [SELECT] statements. 3202 ** 3203 ** Applications that need to process SQL from untrusted sources 3204 ** might also consider lowering resource limits using [sqlite3_limit()] 3205 ** and limiting database size using the [max_page_count] [PRAGMA] 3206 ** in addition to using an authorizer. 3207 ** 3208 ** ^(Only a single authorizer can be in place on a database connection 3209 ** at a time. Each call to sqlite3_set_authorizer overrides the 3210 ** previous call.)^ ^Disable the authorizer by installing a NULL callback. 3211 ** The authorizer is disabled by default. 3212 ** 3213 ** The authorizer callback must not do anything that will modify 3214 ** the database connection that invoked the authorizer callback. 3215 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their 3216 ** database connections for the meaning of "modify" in this paragraph. 3217 ** 3218 ** ^When [sqlite3_prepare_v2()] is used to prepare a statement, the 3219 ** statement might be re-prepared during [sqlite3_step()] due to a 3220 ** schema change. Hence, the application should ensure that the 3221 ** correct authorizer callback remains in place during the [sqlite3_step()]. 3222 ** 3223 ** ^Note that the authorizer callback is invoked only during 3224 ** [sqlite3_prepare()] or its variants. Authorization is not 3225 ** performed during statement evaluation in [sqlite3_step()], unless 3226 ** as stated in the previous paragraph, sqlite3_step() invokes 3227 ** sqlite3_prepare_v2() to reprepare a statement after a schema change. 3228 */ 3229 SQLITE_API int sqlite3_set_authorizer( 3230 sqlite3*, 3231 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*), 3232 void *pUserData 3233 ); 3234 3235 /* 3236 ** CAPI3REF: Authorizer Return Codes 3237 ** 3238 ** The [sqlite3_set_authorizer | authorizer callback function] must 3239 ** return either [SQLITE_OK] or one of these two constants in order 3240 ** to signal SQLite whether or not the action is permitted. See the 3241 ** [sqlite3_set_authorizer | authorizer documentation] for additional 3242 ** information. 3243 ** 3244 ** Note that SQLITE_IGNORE is also used as a [conflict resolution mode] 3245 ** returned from the [sqlite3_vtab_on_conflict()] interface. 3246 */ 3247 #define SQLITE_DENY 1 /* Abort the SQL statement with an error */ 3248 #define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */ 3249 3250 /* 3251 ** CAPI3REF: Authorizer Action Codes 3252 ** 3253 ** The [sqlite3_set_authorizer()] interface registers a callback function 3254 ** that is invoked to authorize certain SQL statement actions. The 3255 ** second parameter to the callback is an integer code that specifies 3256 ** what action is being authorized. These are the integer action codes that 3257 ** the authorizer callback may be passed. 3258 ** 3259 ** These action code values signify what kind of operation is to be 3260 ** authorized. The 3rd and 4th parameters to the authorization 3261 ** callback function will be parameters or NULL depending on which of these 3262 ** codes is used as the second parameter. ^(The 5th parameter to the 3263 ** authorizer callback is the name of the database ("main", "temp", 3264 ** etc.) if applicable.)^ ^The 6th parameter to the authorizer callback 3265 ** is the name of the inner-most trigger or view that is responsible for 3266 ** the access attempt or NULL if this access attempt is directly from 3267 ** top-level SQL code. 3268 */ 3269 /******************************************* 3rd ************ 4th ***********/ 3270 #define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */ 3271 #define SQLITE_CREATE_TABLE 2 /* Table Name NULL */ 3272 #define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */ 3273 #define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */ 3274 #define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */ 3275 #define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */ 3276 #define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */ 3277 #define SQLITE_CREATE_VIEW 8 /* View Name NULL */ 3278 #define SQLITE_DELETE 9 /* Table Name NULL */ 3279 #define SQLITE_DROP_INDEX 10 /* Index Name Table Name */ 3280 #define SQLITE_DROP_TABLE 11 /* Table Name NULL */ 3281 #define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */ 3282 #define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */ 3283 #define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */ 3284 #define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */ 3285 #define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */ 3286 #define SQLITE_DROP_VIEW 17 /* View Name NULL */ 3287 #define SQLITE_INSERT 18 /* Table Name NULL */ 3288 #define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */ 3289 #define SQLITE_READ 20 /* Table Name Column Name */ 3290 #define SQLITE_SELECT 21 /* NULL NULL */ 3291 #define SQLITE_TRANSACTION 22 /* Operation NULL */ 3292 #define SQLITE_UPDATE 23 /* Table Name Column Name */ 3293 #define SQLITE_ATTACH 24 /* Filename NULL */ 3294 #define SQLITE_DETACH 25 /* Database Name NULL */ 3295 #define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */ 3296 #define SQLITE_REINDEX 27 /* Index Name NULL */ 3297 #define SQLITE_ANALYZE 28 /* Table Name NULL */ 3298 #define SQLITE_CREATE_VTABLE 29 /* Table Name Module Name */ 3299 #define SQLITE_DROP_VTABLE 30 /* Table Name Module Name */ 3300 #define SQLITE_FUNCTION 31 /* NULL Function Name */ 3301 #define SQLITE_SAVEPOINT 32 /* Operation Savepoint Name */ 3302 #define SQLITE_COPY 0 /* No longer used */ 3303 #define SQLITE_RECURSIVE 33 /* NULL NULL */ 3304 3305 /* 3306 ** CAPI3REF: Tracing And Profiling Functions 3307 ** METHOD: sqlite3 3308 ** 3309 ** These routines are deprecated. Use the [sqlite3_trace_v2()] interface 3310 ** instead of the routines described here. 3311 ** 3312 ** These routines register callback functions that can be used for 3313 ** tracing and profiling the execution of SQL statements. 3314 ** 3315 ** ^The callback function registered by sqlite3_trace() is invoked at 3316 ** various times when an SQL statement is being run by [sqlite3_step()]. 3317 ** ^The sqlite3_trace() callback is invoked with a UTF-8 rendering of the 3318 ** SQL statement text as the statement first begins executing. 3319 ** ^(Additional sqlite3_trace() callbacks might occur 3320 ** as each triggered subprogram is entered. The callbacks for triggers 3321 ** contain a UTF-8 SQL comment that identifies the trigger.)^ 3322 ** 3323 ** The [SQLITE_TRACE_SIZE_LIMIT] compile-time option can be used to limit 3324 ** the length of [bound parameter] expansion in the output of sqlite3_trace(). 3325 ** 3326 ** ^The callback function registered by sqlite3_profile() is invoked 3327 ** as each SQL statement finishes. ^The profile callback contains 3328 ** the original statement text and an estimate of wall-clock time 3329 ** of how long that statement took to run. ^The profile callback 3330 ** time is in units of nanoseconds, however the current implementation 3331 ** is only capable of millisecond resolution so the six least significant 3332 ** digits in the time are meaningless. Future versions of SQLite 3333 ** might provide greater resolution on the profiler callback. Invoking 3334 ** either [sqlite3_trace()] or [sqlite3_trace_v2()] will cancel the 3335 ** profile callback. 3336 */ 3337 SQLITE_API SQLITE_DEPRECATED void *sqlite3_trace(sqlite3*, 3338 void(*xTrace)(void*,const char*), void*); 3339 SQLITE_API SQLITE_DEPRECATED void *sqlite3_profile(sqlite3*, 3340 void(*xProfile)(void*,const char*,sqlite3_uint64), void*); 3341 3342 /* 3343 ** CAPI3REF: SQL Trace Event Codes 3344 ** KEYWORDS: SQLITE_TRACE 3345 ** 3346 ** These constants identify classes of events that can be monitored 3347 ** using the [sqlite3_trace_v2()] tracing logic. The M argument 3348 ** to [sqlite3_trace_v2(D,M,X,P)] is an OR-ed combination of one or more of 3349 ** the following constants. ^The first argument to the trace callback 3350 ** is one of the following constants. 3351 ** 3352 ** New tracing constants may be added in future releases. 3353 ** 3354 ** ^A trace callback has four arguments: xCallback(T,C,P,X). 3355 ** ^The T argument is one of the integer type codes above. 3356 ** ^The C argument is a copy of the context pointer passed in as the 3357 ** fourth argument to [sqlite3_trace_v2()]. 3358 ** The P and X arguments are pointers whose meanings depend on T. 3359 ** 3360 ** <dl> 3361 ** [[SQLITE_TRACE_STMT]] <dt>SQLITE_TRACE_STMT</dt> 3362 ** <dd>^An SQLITE_TRACE_STMT callback is invoked when a prepared statement 3363 ** first begins running and possibly at other times during the 3364 ** execution of the prepared statement, such as at the start of each 3365 ** trigger subprogram. ^The P argument is a pointer to the 3366 ** [prepared statement]. ^The X argument is a pointer to a string which 3367 ** is the unexpanded SQL text of the prepared statement or an SQL comment 3368 ** that indicates the invocation of a trigger. ^The callback can compute 3369 ** the same text that would have been returned by the legacy [sqlite3_trace()] 3370 ** interface by using the X argument when X begins with "--" and invoking 3371 ** [sqlite3_expanded_sql(P)] otherwise. 3372 ** 3373 ** [[SQLITE_TRACE_PROFILE]] <dt>SQLITE_TRACE_PROFILE</dt> 3374 ** <dd>^An SQLITE_TRACE_PROFILE callback provides approximately the same 3375 ** information as is provided by the [sqlite3_profile()] callback. 3376 ** ^The P argument is a pointer to the [prepared statement] and the 3377 ** X argument points to a 64-bit integer which is approximately 3378 ** the number of nanoseconds that the prepared statement took to run. 3379 ** ^The SQLITE_TRACE_PROFILE callback is invoked when the statement finishes. 3380 ** 3381 ** [[SQLITE_TRACE_ROW]] <dt>SQLITE_TRACE_ROW</dt> 3382 ** <dd>^An SQLITE_TRACE_ROW callback is invoked whenever a prepared 3383 ** statement generates a single row of result. 3384 ** ^The P argument is a pointer to the [prepared statement] and the 3385 ** X argument is unused. 3386 ** 3387 ** [[SQLITE_TRACE_CLOSE]] <dt>SQLITE_TRACE_CLOSE</dt> 3388 ** <dd>^An SQLITE_TRACE_CLOSE callback is invoked when a database 3389 ** connection closes. 3390 ** ^The P argument is a pointer to the [database connection] object 3391 ** and the X argument is unused. 3392 ** </dl> 3393 */ 3394 #define SQLITE_TRACE_STMT 0x01 3395 #define SQLITE_TRACE_PROFILE 0x02 3396 #define SQLITE_TRACE_ROW 0x04 3397 #define SQLITE_TRACE_CLOSE 0x08 3398 3399 /* 3400 ** CAPI3REF: SQL Trace Hook 3401 ** METHOD: sqlite3 3402 ** 3403 ** ^The sqlite3_trace_v2(D,M,X,P) interface registers a trace callback 3404 ** function X against [database connection] D, using property mask M 3405 ** and context pointer P. ^If the X callback is 3406 ** NULL or if the M mask is zero, then tracing is disabled. The 3407 ** M argument should be the bitwise OR-ed combination of 3408 ** zero or more [SQLITE_TRACE] constants. 3409 ** 3410 ** ^Each call to either sqlite3_trace(D,X,P) or sqlite3_trace_v2(D,M,X,P) 3411 ** overrides (cancels) all prior calls to sqlite3_trace(D,X,P) or 3412 ** sqlite3_trace_v2(D,M,X,P) for the [database connection] D. Each 3413 ** database connection may have at most one trace callback. 3414 ** 3415 ** ^The X callback is invoked whenever any of the events identified by 3416 ** mask M occur. ^The integer return value from the callback is currently 3417 ** ignored, though this may change in future releases. Callback 3418 ** implementations should return zero to ensure future compatibility. 3419 ** 3420 ** ^A trace callback is invoked with four arguments: callback(T,C,P,X). 3421 ** ^The T argument is one of the [SQLITE_TRACE] 3422 ** constants to indicate why the callback was invoked. 3423 ** ^The C argument is a copy of the context pointer. 3424 ** The P and X arguments are pointers whose meanings depend on T. 3425 ** 3426 ** The sqlite3_trace_v2() interface is intended to replace the legacy 3427 ** interfaces [sqlite3_trace()] and [sqlite3_profile()], both of which 3428 ** are deprecated. 3429 */ 3430 SQLITE_API int sqlite3_trace_v2( 3431 sqlite3*, 3432 unsigned uMask, 3433 int(*xCallback)(unsigned,void*,void*,void*), 3434 void *pCtx 3435 ); 3436 3437 /* 3438 ** CAPI3REF: Query Progress Callbacks 3439 ** METHOD: sqlite3 3440 ** 3441 ** ^The sqlite3_progress_handler(D,N,X,P) interface causes the callback 3442 ** function X to be invoked periodically during long running calls to 3443 ** [sqlite3_step()] and [sqlite3_prepare()] and similar for 3444 ** database connection D. An example use for this 3445 ** interface is to keep a GUI updated during a large query. 3446 ** 3447 ** ^The parameter P is passed through as the only parameter to the 3448 ** callback function X. ^The parameter N is the approximate number of 3449 ** [virtual machine instructions] that are evaluated between successive 3450 ** invocations of the callback X. ^If N is less than one then the progress 3451 ** handler is disabled. 3452 ** 3453 ** ^Only a single progress handler may be defined at one time per 3454 ** [database connection]; setting a new progress handler cancels the 3455 ** old one. ^Setting parameter X to NULL disables the progress handler. 3456 ** ^The progress handler is also disabled by setting N to a value less 3457 ** than 1. 3458 ** 3459 ** ^If the progress callback returns non-zero, the operation is 3460 ** interrupted. This feature can be used to implement a 3461 ** "Cancel" button on a GUI progress dialog box. 3462 ** 3463 ** The progress handler callback must not do anything that will modify 3464 ** the database connection that invoked the progress handler. 3465 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their 3466 ** database connections for the meaning of "modify" in this paragraph. 3467 ** 3468 ** The progress handler callback would originally only be invoked from the 3469 ** bytecode engine. It still might be invoked during [sqlite3_prepare()] 3470 ** and similar because those routines might force a reparse of the schema 3471 ** which involves running the bytecode engine. However, beginning with 3472 ** SQLite version 3.41.0, the progress handler callback might also be 3473 ** invoked directly from [sqlite3_prepare()] while analyzing and generating 3474 ** code for complex queries. 3475 */ 3476 SQLITE_API void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*); 3477 3478 /* 3479 ** CAPI3REF: Opening A New Database Connection 3480 ** CONSTRUCTOR: sqlite3 3481 ** 3482 ** ^These routines open an SQLite database file as specified by the 3483 ** filename argument. ^The filename argument is interpreted as UTF-8 for 3484 ** sqlite3_open() and sqlite3_open_v2() and as UTF-16 in the native byte 3485 ** order for sqlite3_open16(). ^(A [database connection] handle is usually 3486 ** returned in *ppDb, even if an error occurs. The only exception is that 3487 ** if SQLite is unable to allocate memory to hold the [sqlite3] object, 3488 ** a NULL will be written into *ppDb instead of a pointer to the [sqlite3] 3489 ** object.)^ ^(If the database is opened (and/or created) successfully, then 3490 ** [SQLITE_OK] is returned. Otherwise an [error code] is returned.)^ ^The 3491 ** [sqlite3_errmsg()] or [sqlite3_errmsg16()] routines can be used to obtain 3492 ** an English language description of the error following a failure of any 3493 ** of the sqlite3_open() routines. 3494 ** 3495 ** ^The default encoding will be UTF-8 for databases created using 3496 ** sqlite3_open() or sqlite3_open_v2(). ^The default encoding for databases 3497 ** created using sqlite3_open16() will be UTF-16 in the native byte order. 3498 ** 3499 ** Whether or not an error occurs when it is opened, resources 3500 ** associated with the [database connection] handle should be released by 3501 ** passing it to [sqlite3_close()] when it is no longer required. 3502 ** 3503 ** The sqlite3_open_v2() interface works like sqlite3_open() 3504 ** except that it accepts two additional parameters for additional control 3505 ** over the new database connection. ^(The flags parameter to 3506 ** sqlite3_open_v2() must include, at a minimum, one of the following 3507 ** three flag combinations:)^ 3508 ** 3509 ** <dl> 3510 ** ^(<dt>[SQLITE_OPEN_READONLY]</dt> 3511 ** <dd>The database is opened in read-only mode. If the database does 3512 ** not already exist, an error is returned.</dd>)^ 3513 ** 3514 ** ^(<dt>[SQLITE_OPEN_READWRITE]</dt> 3515 ** <dd>The database is opened for reading and writing if possible, or 3516 ** reading only if the file is write protected by the operating 3517 ** system. In either case the database must already exist, otherwise 3518 ** an error is returned. For historical reasons, if opening in 3519 ** read-write mode fails due to OS-level permissions, an attempt is 3520 ** made to open it in read-only mode. [sqlite3_db_readonly()] can be 3521 ** used to determine whether the database is actually 3522 ** read-write.</dd>)^ 3523 ** 3524 ** ^(<dt>[SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE]</dt> 3525 ** <dd>The database is opened for reading and writing, and is created if 3526 ** it does not already exist. This is the behavior that is always used for 3527 ** sqlite3_open() and sqlite3_open16().</dd>)^ 3528 ** </dl> 3529 ** 3530 ** In addition to the required flags, the following optional flags are 3531 ** also supported: 3532 ** 3533 ** <dl> 3534 ** ^(<dt>[SQLITE_OPEN_URI]</dt> 3535 ** <dd>The filename can be interpreted as a URI if this flag is set.</dd>)^ 3536 ** 3537 ** ^(<dt>[SQLITE_OPEN_MEMORY]</dt> 3538 ** <dd>The database will be opened as an in-memory database. The database 3539 ** is named by the "filename" argument for the purposes of cache-sharing, 3540 ** if shared cache mode is enabled, but the "filename" is otherwise ignored. 3541 ** </dd>)^ 3542 ** 3543 ** ^(<dt>[SQLITE_OPEN_NOMUTEX]</dt> 3544 ** <dd>The new database connection will use the "multi-thread" 3545 ** [threading mode].)^ This means that separate threads are allowed 3546 ** to use SQLite at the same time, as long as each thread is using 3547 ** a different [database connection]. 3548 ** 3549 ** ^(<dt>[SQLITE_OPEN_FULLMUTEX]</dt> 3550 ** <dd>The new database connection will use the "serialized" 3551 ** [threading mode].)^ This means the multiple threads can safely 3552 ** attempt to use the same database connection at the same time. 3553 ** (Mutexes will block any actual concurrency, but in this mode 3554 ** there is no harm in trying.) 3555 ** 3556 ** ^(<dt>[SQLITE_OPEN_SHAREDCACHE]</dt> 3557 ** <dd>The database is opened [shared cache] enabled, overriding 3558 ** the default shared cache setting provided by 3559 ** [sqlite3_enable_shared_cache()].)^ 3560 ** The [use of shared cache mode is discouraged] and hence shared cache 3561 ** capabilities may be omitted from many builds of SQLite. In such cases, 3562 ** this option is a no-op. 3563 ** 3564 ** ^(<dt>[SQLITE_OPEN_PRIVATECACHE]</dt> 3565 ** <dd>The database is opened [shared cache] disabled, overriding 3566 ** the default shared cache setting provided by 3567 ** [sqlite3_enable_shared_cache()].)^ 3568 ** 3569 ** [[OPEN_EXRESCODE]] ^(<dt>[SQLITE_OPEN_EXRESCODE]</dt> 3570 ** <dd>The database connection comes up in "extended result code mode". 3571 ** In other words, the database behaves has if 3572 ** [sqlite3_extended_result_codes(db,1)] where called on the database 3573 ** connection as soon as the connection is created. In addition to setting 3574 ** the extended result code mode, this flag also causes [sqlite3_open_v2()] 3575 ** to return an extended result code.</dd> 3576 ** 3577 ** [[OPEN_NOFOLLOW]] ^(<dt>[SQLITE_OPEN_NOFOLLOW]</dt> 3578 ** <dd>The database filename is not allowed to contain a symbolic link</dd> 3579 ** </dl>)^ 3580 ** 3581 ** If the 3rd parameter to sqlite3_open_v2() is not one of the 3582 ** required combinations shown above optionally combined with other 3583 ** [SQLITE_OPEN_READONLY | SQLITE_OPEN_* bits] 3584 ** then the behavior is undefined. Historic versions of SQLite 3585 ** have silently ignored surplus bits in the flags parameter to 3586 ** sqlite3_open_v2(), however that behavior might not be carried through 3587 ** into future versions of SQLite and so applications should not rely 3588 ** upon it. Note in particular that the SQLITE_OPEN_EXCLUSIVE flag is a no-op 3589 ** for sqlite3_open_v2(). The SQLITE_OPEN_EXCLUSIVE does *not* cause 3590 ** the open to fail if the database already exists. The SQLITE_OPEN_EXCLUSIVE 3591 ** flag is intended for use by the [sqlite3_vfs|VFS interface] only, and not 3592 ** by sqlite3_open_v2(). 3593 ** 3594 ** ^The fourth parameter to sqlite3_open_v2() is the name of the 3595 ** [sqlite3_vfs] object that defines the operating system interface that 3596 ** the new database connection should use. ^If the fourth parameter is 3597 ** a NULL pointer then the default [sqlite3_vfs] object is used. 3598 ** 3599 ** ^If the filename is ":memory:", then a private, temporary in-memory database 3600 ** is created for the connection. ^This in-memory database will vanish when 3601 ** the database connection is closed. Future versions of SQLite might 3602 ** make use of additional special filenames that begin with the ":" character. 3603 ** It is recommended that when a database filename actually does begin with 3604 ** a ":" character you should prefix the filename with a pathname such as 3605 ** "./" to avoid ambiguity. 3606 ** 3607 ** ^If the filename is an empty string, then a private, temporary 3608 ** on-disk database will be created. ^This private database will be 3609 ** automatically deleted as soon as the database connection is closed. 3610 ** 3611 ** [[URI filenames in sqlite3_open()]] <h3>URI Filenames</h3> 3612 ** 3613 ** ^If [URI filename] interpretation is enabled, and the filename argument 3614 ** begins with "file:", then the filename is interpreted as a URI. ^URI 3615 ** filename interpretation is enabled if the [SQLITE_OPEN_URI] flag is 3616 ** set in the third argument to sqlite3_open_v2(), or if it has 3617 ** been enabled globally using the [SQLITE_CONFIG_URI] option with the 3618 ** [sqlite3_config()] method or by the [SQLITE_USE_URI] compile-time option. 3619 ** URI filename interpretation is turned off 3620 ** by default, but future releases of SQLite might enable URI filename 3621 ** interpretation by default. See "[URI filenames]" for additional 3622 ** information. 3623 ** 3624 ** URI filenames are parsed according to RFC 3986. ^If the URI contains an 3625 ** authority, then it must be either an empty string or the string 3626 ** "localhost". ^If the authority is not an empty string or "localhost", an 3627 ** error is returned to the caller. ^The fragment component of a URI, if 3628 ** present, is ignored. 3629 ** 3630 ** ^SQLite uses the path component of the URI as the name of the disk file 3631 ** which contains the database. ^If the path begins with a '/' character, 3632 ** then it is interpreted as an absolute path. ^If the path does not begin 3633 ** with a '/' (meaning that the authority section is omitted from the URI) 3634 ** then the path is interpreted as a relative path. 3635 ** ^(On windows, the first component of an absolute path 3636 ** is a drive specification (e.g. "C:").)^ 3637 ** 3638 ** [[core URI query parameters]] 3639 ** The query component of a URI may contain parameters that are interpreted 3640 ** either by SQLite itself, or by a [VFS | custom VFS implementation]. 3641 ** SQLite and its built-in [VFSes] interpret the 3642 ** following query parameters: 3643 ** 3644 ** <ul> 3645 ** <li> <b>vfs</b>: ^The "vfs" parameter may be used to specify the name of 3646 ** a VFS object that provides the operating system interface that should 3647 ** be used to access the database file on disk. ^If this option is set to 3648 ** an empty string the default VFS object is used. ^Specifying an unknown 3649 ** VFS is an error. ^If sqlite3_open_v2() is used and the vfs option is 3650 ** present, then the VFS specified by the option takes precedence over 3651 ** the value passed as the fourth parameter to sqlite3_open_v2(). 3652 ** 3653 ** <li> <b>mode</b>: ^(The mode parameter may be set to either "ro", "rw", 3654 ** "rwc", or "memory". Attempting to set it to any other value is 3655 ** an error)^. 3656 ** ^If "ro" is specified, then the database is opened for read-only 3657 ** access, just as if the [SQLITE_OPEN_READONLY] flag had been set in the 3658 ** third argument to sqlite3_open_v2(). ^If the mode option is set to 3659 ** "rw", then the database is opened for read-write (but not create) 3660 ** access, as if SQLITE_OPEN_READWRITE (but not SQLITE_OPEN_CREATE) had 3661 ** been set. ^Value "rwc" is equivalent to setting both 3662 ** SQLITE_OPEN_READWRITE and SQLITE_OPEN_CREATE. ^If the mode option is 3663 ** set to "memory" then a pure [in-memory database] that never reads 3664 ** or writes from disk is used. ^It is an error to specify a value for 3665 ** the mode parameter that is less restrictive than that specified by 3666 ** the flags passed in the third parameter to sqlite3_open_v2(). 3667 ** 3668 ** <li> <b>cache</b>: ^The cache parameter may be set to either "shared" or 3669 ** "private". ^Setting it to "shared" is equivalent to setting the 3670 ** SQLITE_OPEN_SHAREDCACHE bit in the flags argument passed to 3671 ** sqlite3_open_v2(). ^Setting the cache parameter to "private" is 3672 ** equivalent to setting the SQLITE_OPEN_PRIVATECACHE bit. 3673 ** ^If sqlite3_open_v2() is used and the "cache" parameter is present in 3674 ** a URI filename, its value overrides any behavior requested by setting 3675 ** SQLITE_OPEN_PRIVATECACHE or SQLITE_OPEN_SHAREDCACHE flag. 3676 ** 3677 ** <li> <b>psow</b>: ^The psow parameter indicates whether or not the 3678 ** [powersafe overwrite] property does or does not apply to the 3679 ** storage media on which the database file resides. 3680 ** 3681 ** <li> <b>nolock</b>: ^The nolock parameter is a boolean query parameter 3682 ** which if set disables file locking in rollback journal modes. This 3683 ** is useful for accessing a database on a filesystem that does not 3684 ** support locking. Caution: Database corruption might result if two 3685 ** or more processes write to the same database and any one of those 3686 ** processes uses nolock=1. 3687 ** 3688 ** <li> <b>immutable</b>: ^The immutable parameter is a boolean query 3689 ** parameter that indicates that the database file is stored on 3690 ** read-only media. ^When immutable is set, SQLite assumes that the 3691 ** database file cannot be changed, even by a process with higher 3692 ** privilege, and so the database is opened read-only and all locking 3693 ** and change detection is disabled. Caution: Setting the immutable 3694 ** property on a database file that does in fact change can result 3695 ** in incorrect query results and/or [SQLITE_CORRUPT] errors. 3696 ** See also: [SQLITE_IOCAP_IMMUTABLE]. 3697 ** 3698 ** </ul> 3699 ** 3700 ** ^Specifying an unknown parameter in the query component of a URI is not an 3701 ** error. Future versions of SQLite might understand additional query 3702 ** parameters. See "[query parameters with special meaning to SQLite]" for 3703 ** additional information. 3704 ** 3705 ** [[URI filename examples]] <h3>URI filename examples</h3> 3706 ** 3707 ** <table border="1" align=center cellpadding=5> 3708 ** <tr><th> URI filenames <th> Results 3709 ** <tr><td> file:data.db <td> 3710 ** Open the file "data.db" in the current directory. 3711 ** <tr><td> file:/home/fred/data.db<br> 3712 ** file:///home/fred/data.db <br> 3713 ** file://localhost/home/fred/data.db <br> <td> 3714 ** Open the database file "/home/fred/data.db". 3715 ** <tr><td> file://darkstar/home/fred/data.db <td> 3716 ** An error. "darkstar" is not a recognized authority. 3717 ** <tr><td style="white-space:nowrap"> 3718 ** file:///C:/Documents%20and%20Settings/fred/Desktop/data.db 3719 ** <td> Windows only: Open the file "data.db" on fred's desktop on drive 3720 ** C:. Note that the %20 escaping in this example is not strictly 3721 ** necessary - space characters can be used literally 3722 ** in URI filenames. 3723 ** <tr><td> file:data.db?mode=ro&cache=private <td> 3724 ** Open file "data.db" in the current directory for read-only access. 3725 ** Regardless of whether or not shared-cache mode is enabled by 3726 ** default, use a private cache. 3727 ** <tr><td> file:/home/fred/data.db?vfs=unix-dotfile <td> 3728 ** Open file "/home/fred/data.db". Use the special VFS "unix-dotfile" 3729 ** that uses dot-files in place of posix advisory locking. 3730 ** <tr><td> file:data.db?mode=readonly <td> 3731 ** An error. "readonly" is not a valid option for the "mode" parameter. 3732 ** Use "ro" instead: "file:data.db?mode=ro". 3733 ** </table> 3734 ** 3735 ** ^URI hexadecimal escape sequences (%HH) are supported within the path and 3736 ** query components of a URI. A hexadecimal escape sequence consists of a 3737 ** percent sign - "%" - followed by exactly two hexadecimal digits 3738 ** specifying an octet value. ^Before the path or query components of a 3739 ** URI filename are interpreted, they are encoded using UTF-8 and all 3740 ** hexadecimal escape sequences replaced by a single byte containing the 3741 ** corresponding octet. If this process generates an invalid UTF-8 encoding, 3742 ** the results are undefined. 3743 ** 3744 ** <b>Note to Windows users:</b> The encoding used for the filename argument 3745 ** of sqlite3_open() and sqlite3_open_v2() must be UTF-8, not whatever 3746 ** codepage is currently defined. Filenames containing international 3747 ** characters must be converted to UTF-8 prior to passing them into 3748 ** sqlite3_open() or sqlite3_open_v2(). 3749 ** 3750 ** <b>Note to Windows Runtime users:</b> The temporary directory must be set 3751 ** prior to calling sqlite3_open() or sqlite3_open_v2(). Otherwise, various 3752 ** features that require the use of temporary files may fail. 3753 ** 3754 ** See also: [sqlite3_temp_directory] 3755 */ 3756 SQLITE_API int sqlite3_open( 3757 const char *filename, /* Database filename (UTF-8) */ 3758 sqlite3 **ppDb /* OUT: SQLite db handle */ 3759 ); 3760 SQLITE_API int sqlite3_open16( 3761 const void *filename, /* Database filename (UTF-16) */ 3762 sqlite3 **ppDb /* OUT: SQLite db handle */ 3763 ); 3764 SQLITE_API int sqlite3_open_v2( 3765 const char *filename, /* Database filename (UTF-8) */ 3766 sqlite3 **ppDb, /* OUT: SQLite db handle */ 3767 int flags, /* Flags */ 3768 const char *zVfs /* Name of VFS module to use */ 3769 ); 3770 3771 /* 3772 ** CAPI3REF: Obtain Values For URI Parameters 3773 ** 3774 ** These are utility routines, useful to [VFS|custom VFS implementations], 3775 ** that check if a database file was a URI that contained a specific query 3776 ** parameter, and if so obtains the value of that query parameter. 3777 ** 3778 ** The first parameter to these interfaces (hereafter referred to 3779 ** as F) must be one of: 3780 ** <ul> 3781 ** <li> A database filename pointer created by the SQLite core and 3782 ** passed into the xOpen() method of a VFS implementation, or 3783 ** <li> A filename obtained from [sqlite3_db_filename()], or 3784 ** <li> A new filename constructed using [sqlite3_create_filename()]. 3785 ** </ul> 3786 ** If the F parameter is not one of the above, then the behavior is 3787 ** undefined and probably undesirable. Older versions of SQLite were 3788 ** more tolerant of invalid F parameters than newer versions. 3789 ** 3790 ** If F is a suitable filename (as described in the previous paragraph) 3791 ** and if P is the name of the query parameter, then 3792 ** sqlite3_uri_parameter(F,P) returns the value of the P 3793 ** parameter if it exists or a NULL pointer if P does not appear as a 3794 ** query parameter on F. If P is a query parameter of F and it 3795 ** has no explicit value, then sqlite3_uri_parameter(F,P) returns 3796 ** a pointer to an empty string. 3797 ** 3798 ** The sqlite3_uri_boolean(F,P,B) routine assumes that P is a boolean 3799 ** parameter and returns true (1) or false (0) according to the value 3800 ** of P. The sqlite3_uri_boolean(F,P,B) routine returns true (1) if the 3801 ** value of query parameter P is one of "yes", "true", or "on" in any 3802 ** case or if the value begins with a non-zero number. The 3803 ** sqlite3_uri_boolean(F,P,B) routines returns false (0) if the value of 3804 ** query parameter P is one of "no", "false", or "off" in any case or 3805 ** if the value begins with a numeric zero. If P is not a query 3806 ** parameter on F or if the value of P does not match any of the 3807 ** above, then sqlite3_uri_boolean(F,P,B) returns (B!=0). 3808 ** 3809 ** The sqlite3_uri_int64(F,P,D) routine converts the value of P into a 3810 ** 64-bit signed integer and returns that integer, or D if P does not 3811 ** exist. If the value of P is something other than an integer, then 3812 ** zero is returned. 3813 ** 3814 ** The sqlite3_uri_key(F,N) returns a pointer to the name (not 3815 ** the value) of the N-th query parameter for filename F, or a NULL 3816 ** pointer if N is less than zero or greater than the number of query 3817 ** parameters minus 1. The N value is zero-based so N should be 0 to obtain 3818 ** the name of the first query parameter, 1 for the second parameter, and 3819 ** so forth. 3820 ** 3821 ** If F is a NULL pointer, then sqlite3_uri_parameter(F,P) returns NULL and 3822 ** sqlite3_uri_boolean(F,P,B) returns B. If F is not a NULL pointer and 3823 ** is not a database file pathname pointer that the SQLite core passed 3824 ** into the xOpen VFS method, then the behavior of this routine is undefined 3825 ** and probably undesirable. 3826 ** 3827 ** Beginning with SQLite [version 3.31.0] ([dateof:3.31.0]) the input F 3828 ** parameter can also be the name of a rollback journal file or WAL file 3829 ** in addition to the main database file. Prior to version 3.31.0, these 3830 ** routines would only work if F was the name of the main database file. 3831 ** When the F parameter is the name of the rollback journal or WAL file, 3832 ** it has access to all the same query parameters as were found on the 3833 ** main database file. 3834 ** 3835 ** See the [URI filename] documentation for additional information. 3836 */ 3837 SQLITE_API const char *sqlite3_uri_parameter(sqlite3_filename z, const char *zParam); 3838 SQLITE_API int sqlite3_uri_boolean(sqlite3_filename z, const char *zParam, int bDefault); 3839 SQLITE_API sqlite3_int64 sqlite3_uri_int64(sqlite3_filename, const char*, sqlite3_int64); 3840 SQLITE_API const char *sqlite3_uri_key(sqlite3_filename z, int N); 3841 3842 /* 3843 ** CAPI3REF: Translate filenames 3844 ** 3845 ** These routines are available to [VFS|custom VFS implementations] for 3846 ** translating filenames between the main database file, the journal file, 3847 ** and the WAL file. 3848 ** 3849 ** If F is the name of an sqlite database file, journal file, or WAL file 3850 ** passed by the SQLite core into the VFS, then sqlite3_filename_database(F) 3851 ** returns the name of the corresponding database file. 3852 ** 3853 ** If F is the name of an sqlite database file, journal file, or WAL file 3854 ** passed by the SQLite core into the VFS, or if F is a database filename 3855 ** obtained from [sqlite3_db_filename()], then sqlite3_filename_journal(F) 3856 ** returns the name of the corresponding rollback journal file. 3857 ** 3858 ** If F is the name of an sqlite database file, journal file, or WAL file 3859 ** that was passed by the SQLite core into the VFS, or if F is a database 3860 ** filename obtained from [sqlite3_db_filename()], then 3861 ** sqlite3_filename_wal(F) returns the name of the corresponding 3862 ** WAL file. 3863 ** 3864 ** In all of the above, if F is not the name of a database, journal or WAL 3865 ** filename passed into the VFS from the SQLite core and F is not the 3866 ** return value from [sqlite3_db_filename()], then the result is 3867 ** undefined and is likely a memory access violation. 3868 */ 3869 SQLITE_API const char *sqlite3_filename_database(sqlite3_filename); 3870 SQLITE_API const char *sqlite3_filename_journal(sqlite3_filename); 3871 SQLITE_API const char *sqlite3_filename_wal(sqlite3_filename); 3872 3873 /* 3874 ** CAPI3REF: Database File Corresponding To A Journal 3875 ** 3876 ** ^If X is the name of a rollback or WAL-mode journal file that is 3877 ** passed into the xOpen method of [sqlite3_vfs], then 3878 ** sqlite3_database_file_object(X) returns a pointer to the [sqlite3_file] 3879 ** object that represents the main database file. 3880 ** 3881 ** This routine is intended for use in custom [VFS] implementations 3882 ** only. It is not a general-purpose interface. 3883 ** The argument sqlite3_file_object(X) must be a filename pointer that 3884 ** has been passed into [sqlite3_vfs].xOpen method where the 3885 ** flags parameter to xOpen contains one of the bits 3886 ** [SQLITE_OPEN_MAIN_JOURNAL] or [SQLITE_OPEN_WAL]. Any other use 3887 ** of this routine results in undefined and probably undesirable 3888 ** behavior. 3889 */ 3890 SQLITE_API sqlite3_file *sqlite3_database_file_object(const char*); 3891 3892 /* 3893 ** CAPI3REF: Create and Destroy VFS Filenames 3894 ** 3895 ** These interfaces are provided for use by [VFS shim] implementations and 3896 ** are not useful outside of that context. 3897 ** 3898 ** The sqlite3_create_filename(D,J,W,N,P) allocates memory to hold a version of 3899 ** database filename D with corresponding journal file J and WAL file W and 3900 ** with N URI parameters key/values pairs in the array P. The result from 3901 ** sqlite3_create_filename(D,J,W,N,P) is a pointer to a database filename that 3902 ** is safe to pass to routines like: 3903 ** <ul> 3904 ** <li> [sqlite3_uri_parameter()], 3905 ** <li> [sqlite3_uri_boolean()], 3906 ** <li> [sqlite3_uri_int64()], 3907 ** <li> [sqlite3_uri_key()], 3908 ** <li> [sqlite3_filename_database()], 3909 ** <li> [sqlite3_filename_journal()], or 3910 ** <li> [sqlite3_filename_wal()]. 3911 ** </ul> 3912 ** If a memory allocation error occurs, sqlite3_create_filename() might 3913 ** return a NULL pointer. The memory obtained from sqlite3_create_filename(X) 3914 ** must be released by a corresponding call to sqlite3_free_filename(Y). 3915 ** 3916 ** The P parameter in sqlite3_create_filename(D,J,W,N,P) should be an array 3917 ** of 2*N pointers to strings. Each pair of pointers in this array corresponds 3918 ** to a key and value for a query parameter. The P parameter may be a NULL 3919 ** pointer if N is zero. None of the 2*N pointers in the P array may be 3920 ** NULL pointers and key pointers should not be empty strings. 3921 ** None of the D, J, or W parameters to sqlite3_create_filename(D,J,W,N,P) may 3922 ** be NULL pointers, though they can be empty strings. 3923 ** 3924 ** The sqlite3_free_filename(Y) routine releases a memory allocation 3925 ** previously obtained from sqlite3_create_filename(). Invoking 3926 ** sqlite3_free_filename(Y) where Y is a NULL pointer is a harmless no-op. 3927 ** 3928 ** If the Y parameter to sqlite3_free_filename(Y) is anything other 3929 ** than a NULL pointer or a pointer previously acquired from 3930 ** sqlite3_create_filename(), then bad things such as heap 3931 ** corruption or segfaults may occur. The value Y should not be 3932 ** used again after sqlite3_free_filename(Y) has been called. This means 3933 ** that if the [sqlite3_vfs.xOpen()] method of a VFS has been called using Y, 3934 ** then the corresponding [sqlite3_module.xClose() method should also be 3935 ** invoked prior to calling sqlite3_free_filename(Y). 3936 */ 3937 SQLITE_API sqlite3_filename sqlite3_create_filename( 3938 const char *zDatabase, 3939 const char *zJournal, 3940 const char *zWal, 3941 int nParam, 3942 const char **azParam 3943 ); 3944 SQLITE_API void sqlite3_free_filename(sqlite3_filename); 3945 3946 /* 3947 ** CAPI3REF: Error Codes And Messages 3948 ** METHOD: sqlite3 3949 ** 3950 ** ^If the most recent sqlite3_* API call associated with 3951 ** [database connection] D failed, then the sqlite3_errcode(D) interface 3952 ** returns the numeric [result code] or [extended result code] for that 3953 ** API call. 3954 ** ^The sqlite3_extended_errcode() 3955 ** interface is the same except that it always returns the 3956 ** [extended result code] even when extended result codes are 3957 ** disabled. 3958 ** 3959 ** The values returned by sqlite3_errcode() and/or 3960 ** sqlite3_extended_errcode() might change with each API call. 3961 ** Except, there are some interfaces that are guaranteed to never 3962 ** change the value of the error code. The error-code preserving 3963 ** interfaces include the following: 3964 ** 3965 ** <ul> 3966 ** <li> sqlite3_errcode() 3967 ** <li> sqlite3_extended_errcode() 3968 ** <li> sqlite3_errmsg() 3969 ** <li> sqlite3_errmsg16() 3970 ** <li> sqlite3_error_offset() 3971 ** </ul> 3972 ** 3973 ** ^The sqlite3_errmsg() and sqlite3_errmsg16() return English-language 3974 ** text that describes the error, as either UTF-8 or UTF-16 respectively. 3975 ** (See how SQLite handles [invalid UTF] for exceptions to this rule.) 3976 ** ^(Memory to hold the error message string is managed internally. 3977 ** The application does not need to worry about freeing the result. 3978 ** However, the error string might be overwritten or deallocated by 3979 ** subsequent calls to other SQLite interface functions.)^ 3980 ** 3981 ** ^The sqlite3_errstr() interface returns the English-language text 3982 ** that describes the [result code], as UTF-8. 3983 ** ^(Memory to hold the error message string is managed internally 3984 ** and must not be freed by the application)^. 3985 ** 3986 ** ^If the most recent error references a specific token in the input 3987 ** SQL, the sqlite3_error_offset() interface returns the byte offset 3988 ** of the start of that token. ^The byte offset returned by 3989 ** sqlite3_error_offset() assumes that the input SQL is UTF8. 3990 ** ^If the most recent error does not reference a specific token in the input 3991 ** SQL, then the sqlite3_error_offset() function returns -1. 3992 ** 3993 ** When the serialized [threading mode] is in use, it might be the 3994 ** case that a second error occurs on a separate thread in between 3995 ** the time of the first error and the call to these interfaces. 3996 ** When that happens, the second error will be reported since these 3997 ** interfaces always report the most recent result. To avoid 3998 ** this, each thread can obtain exclusive use of the [database connection] D 3999 ** by invoking [sqlite3_mutex_enter]([sqlite3_db_mutex](D)) before beginning 4000 ** to use D and invoking [sqlite3_mutex_leave]([sqlite3_db_mutex](D)) after 4001 ** all calls to the interfaces listed here are completed. 4002 ** 4003 ** If an interface fails with SQLITE_MISUSE, that means the interface 4004 ** was invoked incorrectly by the application. In that case, the 4005 ** error code and message may or may not be set. 4006 */ 4007 SQLITE_API int sqlite3_errcode(sqlite3 *db); 4008 SQLITE_API int sqlite3_extended_errcode(sqlite3 *db); 4009 SQLITE_API const char *sqlite3_errmsg(sqlite3*); 4010 SQLITE_API const void *sqlite3_errmsg16(sqlite3*); 4011 SQLITE_API const char *sqlite3_errstr(int); 4012 SQLITE_API int sqlite3_error_offset(sqlite3 *db); 4013 4014 /* 4015 ** CAPI3REF: Prepared Statement Object 4016 ** KEYWORDS: {prepared statement} {prepared statements} 4017 ** 4018 ** An instance of this object represents a single SQL statement that 4019 ** has been compiled into binary form and is ready to be evaluated. 4020 ** 4021 ** Think of each SQL statement as a separate computer program. The 4022 ** original SQL text is source code. A prepared statement object 4023 ** is the compiled object code. All SQL must be converted into a 4024 ** prepared statement before it can be run. 4025 ** 4026 ** The life-cycle of a prepared statement object usually goes like this: 4027 ** 4028 ** <ol> 4029 ** <li> Create the prepared statement object using [sqlite3_prepare_v2()]. 4030 ** <li> Bind values to [parameters] using the sqlite3_bind_*() 4031 ** interfaces. 4032 ** <li> Run the SQL by calling [sqlite3_step()] one or more times. 4033 ** <li> Reset the prepared statement using [sqlite3_reset()] then go back 4034 ** to step 2. Do this zero or more times. 4035 ** <li> Destroy the object using [sqlite3_finalize()]. 4036 ** </ol> 4037 */ 4038 typedef struct sqlite3_stmt sqlite3_stmt; 4039 4040 /* 4041 ** CAPI3REF: Run-time Limits 4042 ** METHOD: sqlite3 4043 ** 4044 ** ^(This interface allows the size of various constructs to be limited 4045 ** on a connection by connection basis. The first parameter is the 4046 ** [database connection] whose limit is to be set or queried. The 4047 ** second parameter is one of the [limit categories] that define a 4048 ** class of constructs to be size limited. The third parameter is the 4049 ** new limit for that construct.)^ 4050 ** 4051 ** ^If the new limit is a negative number, the limit is unchanged. 4052 ** ^(For each limit category SQLITE_LIMIT_<i>NAME</i> there is a 4053 ** [limits | hard upper bound] 4054 ** set at compile-time by a C preprocessor macro called 4055 ** [limits | SQLITE_MAX_<i>NAME</i>]. 4056 ** (The "_LIMIT_" in the name is changed to "_MAX_".))^ 4057 ** ^Attempts to increase a limit above its hard upper bound are 4058 ** silently truncated to the hard upper bound. 4059 ** 4060 ** ^Regardless of whether or not the limit was changed, the 4061 ** [sqlite3_limit()] interface returns the prior value of the limit. 4062 ** ^Hence, to find the current value of a limit without changing it, 4063 ** simply invoke this interface with the third parameter set to -1. 4064 ** 4065 ** Run-time limits are intended for use in applications that manage 4066 ** both their own internal database and also databases that are controlled 4067 ** by untrusted external sources. An example application might be a 4068 ** web browser that has its own databases for storing history and 4069 ** separate databases controlled by JavaScript applications downloaded 4070 ** off the Internet. The internal databases can be given the 4071 ** large, default limits. Databases managed by external sources can 4072 ** be given much smaller limits designed to prevent a denial of service 4073 ** attack. Developers might also want to use the [sqlite3_set_authorizer()] 4074 ** interface to further control untrusted SQL. The size of the database 4075 ** created by an untrusted script can be contained using the 4076 ** [max_page_count] [PRAGMA]. 4077 ** 4078 ** New run-time limit categories may be added in future releases. 4079 */ 4080 SQLITE_API int sqlite3_limit(sqlite3*, int id, int newVal); 4081 4082 /* 4083 ** CAPI3REF: Run-Time Limit Categories 4084 ** KEYWORDS: {limit category} {*limit categories} 4085 ** 4086 ** These constants define various performance limits 4087 ** that can be lowered at run-time using [sqlite3_limit()]. 4088 ** The synopsis of the meanings of the various limits is shown below. 4089 ** Additional information is available at [limits | Limits in SQLite]. 4090 ** 4091 ** <dl> 4092 ** [[SQLITE_LIMIT_LENGTH]] ^(<dt>SQLITE_LIMIT_LENGTH</dt> 4093 ** <dd>The maximum size of any string or BLOB or table row, in bytes.<dd>)^ 4094 ** 4095 ** [[SQLITE_LIMIT_SQL_LENGTH]] ^(<dt>SQLITE_LIMIT_SQL_LENGTH</dt> 4096 ** <dd>The maximum length of an SQL statement, in bytes.</dd>)^ 4097 ** 4098 ** [[SQLITE_LIMIT_COLUMN]] ^(<dt>SQLITE_LIMIT_COLUMN</dt> 4099 ** <dd>The maximum number of columns in a table definition or in the 4100 ** result set of a [SELECT] or the maximum number of columns in an index 4101 ** or in an ORDER BY or GROUP BY clause.</dd>)^ 4102 ** 4103 ** [[SQLITE_LIMIT_EXPR_DEPTH]] ^(<dt>SQLITE_LIMIT_EXPR_DEPTH</dt> 4104 ** <dd>The maximum depth of the parse tree on any expression.</dd>)^ 4105 ** 4106 ** [[SQLITE_LIMIT_COMPOUND_SELECT]] ^(<dt>SQLITE_LIMIT_COMPOUND_SELECT</dt> 4107 ** <dd>The maximum number of terms in a compound SELECT statement.</dd>)^ 4108 ** 4109 ** [[SQLITE_LIMIT_VDBE_OP]] ^(<dt>SQLITE_LIMIT_VDBE_OP</dt> 4110 ** <dd>The maximum number of instructions in a virtual machine program 4111 ** used to implement an SQL statement. If [sqlite3_prepare_v2()] or 4112 ** the equivalent tries to allocate space for more than this many opcodes 4113 ** in a single prepared statement, an SQLITE_NOMEM error is returned.</dd>)^ 4114 ** 4115 ** [[SQLITE_LIMIT_FUNCTION_ARG]] ^(<dt>SQLITE_LIMIT_FUNCTION_ARG</dt> 4116 ** <dd>The maximum number of arguments on a function.</dd>)^ 4117 ** 4118 ** [[SQLITE_LIMIT_ATTACHED]] ^(<dt>SQLITE_LIMIT_ATTACHED</dt> 4119 ** <dd>The maximum number of [ATTACH | attached databases].)^</dd> 4120 ** 4121 ** [[SQLITE_LIMIT_LIKE_PATTERN_LENGTH]] 4122 ** ^(<dt>SQLITE_LIMIT_LIKE_PATTERN_LENGTH</dt> 4123 ** <dd>The maximum length of the pattern argument to the [LIKE] or 4124 ** [GLOB] operators.</dd>)^ 4125 ** 4126 ** [[SQLITE_LIMIT_VARIABLE_NUMBER]] 4127 ** ^(<dt>SQLITE_LIMIT_VARIABLE_NUMBER</dt> 4128 ** <dd>The maximum index number of any [parameter] in an SQL statement.)^ 4129 ** 4130 ** [[SQLITE_LIMIT_TRIGGER_DEPTH]] ^(<dt>SQLITE_LIMIT_TRIGGER_DEPTH</dt> 4131 ** <dd>The maximum depth of recursion for triggers.</dd>)^ 4132 ** 4133 ** [[SQLITE_LIMIT_WORKER_THREADS]] ^(<dt>SQLITE_LIMIT_WORKER_THREADS</dt> 4134 ** <dd>The maximum number of auxiliary worker threads that a single 4135 ** [prepared statement] may start.</dd>)^ 4136 ** </dl> 4137 */ 4138 #define SQLITE_LIMIT_LENGTH 0 4139 #define SQLITE_LIMIT_SQL_LENGTH 1 4140 #define SQLITE_LIMIT_COLUMN 2 4141 #define SQLITE_LIMIT_EXPR_DEPTH 3 4142 #define SQLITE_LIMIT_COMPOUND_SELECT 4 4143 #define SQLITE_LIMIT_VDBE_OP 5 4144 #define SQLITE_LIMIT_FUNCTION_ARG 6 4145 #define SQLITE_LIMIT_ATTACHED 7 4146 #define SQLITE_LIMIT_LIKE_PATTERN_LENGTH 8 4147 #define SQLITE_LIMIT_VARIABLE_NUMBER 9 4148 #define SQLITE_LIMIT_TRIGGER_DEPTH 10 4149 #define SQLITE_LIMIT_WORKER_THREADS 11 4150 4151 /* 4152 ** CAPI3REF: Prepare Flags 4153 ** 4154 ** These constants define various flags that can be passed into 4155 ** "prepFlags" parameter of the [sqlite3_prepare_v3()] and 4156 ** [sqlite3_prepare16_v3()] interfaces. 4157 ** 4158 ** New flags may be added in future releases of SQLite. 4159 ** 4160 ** <dl> 4161 ** [[SQLITE_PREPARE_PERSISTENT]] ^(<dt>SQLITE_PREPARE_PERSISTENT</dt> 4162 ** <dd>The SQLITE_PREPARE_PERSISTENT flag is a hint to the query planner 4163 ** that the prepared statement will be retained for a long time and 4164 ** probably reused many times.)^ ^Without this flag, [sqlite3_prepare_v3()] 4165 ** and [sqlite3_prepare16_v3()] assume that the prepared statement will 4166 ** be used just once or at most a few times and then destroyed using 4167 ** [sqlite3_finalize()] relatively soon. The current implementation acts 4168 ** on this hint by avoiding the use of [lookaside memory] so as not to 4169 ** deplete the limited store of lookaside memory. Future versions of 4170 ** SQLite may act on this hint differently. 4171 ** 4172 ** [[SQLITE_PREPARE_NORMALIZE]] <dt>SQLITE_PREPARE_NORMALIZE</dt> 4173 ** <dd>The SQLITE_PREPARE_NORMALIZE flag is a no-op. This flag used 4174 ** to be required for any prepared statement that wanted to use the 4175 ** [sqlite3_normalized_sql()] interface. However, the 4176 ** [sqlite3_normalized_sql()] interface is now available to all 4177 ** prepared statements, regardless of whether or not they use this 4178 ** flag. 4179 ** 4180 ** [[SQLITE_PREPARE_NO_VTAB]] <dt>SQLITE_PREPARE_NO_VTAB</dt> 4181 ** <dd>The SQLITE_PREPARE_NO_VTAB flag causes the SQL compiler 4182 ** to return an error (error code SQLITE_ERROR) if the statement uses 4183 ** any virtual tables. 4184 ** </dl> 4185 */ 4186 #define SQLITE_PREPARE_PERSISTENT 0x01 4187 #define SQLITE_PREPARE_NORMALIZE 0x02 4188 #define SQLITE_PREPARE_NO_VTAB 0x04 4189 4190 /* 4191 ** CAPI3REF: Compiling An SQL Statement 4192 ** KEYWORDS: {SQL statement compiler} 4193 ** METHOD: sqlite3 4194 ** CONSTRUCTOR: sqlite3_stmt 4195 ** 4196 ** To execute an SQL statement, it must first be compiled into a byte-code 4197 ** program using one of these routines. Or, in other words, these routines 4198 ** are constructors for the [prepared statement] object. 4199 ** 4200 ** The preferred routine to use is [sqlite3_prepare_v2()]. The 4201 ** [sqlite3_prepare()] interface is legacy and should be avoided. 4202 ** [sqlite3_prepare_v3()] has an extra "prepFlags" option that is used 4203 ** for special purposes. 4204 ** 4205 ** The use of the UTF-8 interfaces is preferred, as SQLite currently 4206 ** does all parsing using UTF-8. The UTF-16 interfaces are provided 4207 ** as a convenience. The UTF-16 interfaces work by converting the 4208 ** input text into UTF-8, then invoking the corresponding UTF-8 interface. 4209 ** 4210 ** The first argument, "db", is a [database connection] obtained from a 4211 ** prior successful call to [sqlite3_open()], [sqlite3_open_v2()] or 4212 ** [sqlite3_open16()]. The database connection must not have been closed. 4213 ** 4214 ** The second argument, "zSql", is the statement to be compiled, encoded 4215 ** as either UTF-8 or UTF-16. The sqlite3_prepare(), sqlite3_prepare_v2(), 4216 ** and sqlite3_prepare_v3() 4217 ** interfaces use UTF-8, and sqlite3_prepare16(), sqlite3_prepare16_v2(), 4218 ** and sqlite3_prepare16_v3() use UTF-16. 4219 ** 4220 ** ^If the nByte argument is negative, then zSql is read up to the 4221 ** first zero terminator. ^If nByte is positive, then it is the 4222 ** number of bytes read from zSql. ^If nByte is zero, then no prepared 4223 ** statement is generated. 4224 ** If the caller knows that the supplied string is nul-terminated, then 4225 ** there is a small performance advantage to passing an nByte parameter that 4226 ** is the number of bytes in the input string <i>including</i> 4227 ** the nul-terminator. 4228 ** 4229 ** ^If pzTail is not NULL then *pzTail is made to point to the first byte 4230 ** past the end of the first SQL statement in zSql. These routines only 4231 ** compile the first statement in zSql, so *pzTail is left pointing to 4232 ** what remains uncompiled. 4233 ** 4234 ** ^*ppStmt is left pointing to a compiled [prepared statement] that can be 4235 ** executed using [sqlite3_step()]. ^If there is an error, *ppStmt is set 4236 ** to NULL. ^If the input text contains no SQL (if the input is an empty 4237 ** string or a comment) then *ppStmt is set to NULL. 4238 ** The calling procedure is responsible for deleting the compiled 4239 ** SQL statement using [sqlite3_finalize()] after it has finished with it. 4240 ** ppStmt may not be NULL. 4241 ** 4242 ** ^On success, the sqlite3_prepare() family of routines return [SQLITE_OK]; 4243 ** otherwise an [error code] is returned. 4244 ** 4245 ** The sqlite3_prepare_v2(), sqlite3_prepare_v3(), sqlite3_prepare16_v2(), 4246 ** and sqlite3_prepare16_v3() interfaces are recommended for all new programs. 4247 ** The older interfaces (sqlite3_prepare() and sqlite3_prepare16()) 4248 ** are retained for backwards compatibility, but their use is discouraged. 4249 ** ^In the "vX" interfaces, the prepared statement 4250 ** that is returned (the [sqlite3_stmt] object) contains a copy of the 4251 ** original SQL text. This causes the [sqlite3_step()] interface to 4252 ** behave differently in three ways: 4253 ** 4254 ** <ol> 4255 ** <li> 4256 ** ^If the database schema changes, instead of returning [SQLITE_SCHEMA] as it 4257 ** always used to do, [sqlite3_step()] will automatically recompile the SQL 4258 ** statement and try to run it again. As many as [SQLITE_MAX_SCHEMA_RETRY] 4259 ** retries will occur before sqlite3_step() gives up and returns an error. 4260 ** </li> 4261 ** 4262 ** <li> 4263 ** ^When an error occurs, [sqlite3_step()] will return one of the detailed 4264 ** [error codes] or [extended error codes]. ^The legacy behavior was that 4265 ** [sqlite3_step()] would only return a generic [SQLITE_ERROR] result code 4266 ** and the application would have to make a second call to [sqlite3_reset()] 4267 ** in order to find the underlying cause of the problem. With the "v2" prepare 4268 ** interfaces, the underlying reason for the error is returned immediately. 4269 ** </li> 4270 ** 4271 ** <li> 4272 ** ^If the specific value bound to a [parameter | host parameter] in the 4273 ** WHERE clause might influence the choice of query plan for a statement, 4274 ** then the statement will be automatically recompiled, as if there had been 4275 ** a schema change, on the first [sqlite3_step()] call following any change 4276 ** to the [sqlite3_bind_text | bindings] of that [parameter]. 4277 ** ^The specific value of a WHERE-clause [parameter] might influence the 4278 ** choice of query plan if the parameter is the left-hand side of a [LIKE] 4279 ** or [GLOB] operator or if the parameter is compared to an indexed column 4280 ** and the [SQLITE_ENABLE_STAT4] compile-time option is enabled. 4281 ** </li> 4282 ** </ol> 4283 ** 4284 ** <p>^sqlite3_prepare_v3() differs from sqlite3_prepare_v2() only in having 4285 ** the extra prepFlags parameter, which is a bit array consisting of zero or 4286 ** more of the [SQLITE_PREPARE_PERSISTENT|SQLITE_PREPARE_*] flags. ^The 4287 ** sqlite3_prepare_v2() interface works exactly the same as 4288 ** sqlite3_prepare_v3() with a zero prepFlags parameter. 4289 */ 4290 SQLITE_API int sqlite3_prepare( 4291 sqlite3 *db, /* Database handle */ 4292 const char *zSql, /* SQL statement, UTF-8 encoded */ 4293 int nByte, /* Maximum length of zSql in bytes. */ 4294 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 4295 const char **pzTail /* OUT: Pointer to unused portion of zSql */ 4296 ); 4297 SQLITE_API int sqlite3_prepare_v2( 4298 sqlite3 *db, /* Database handle */ 4299 const char *zSql, /* SQL statement, UTF-8 encoded */ 4300 int nByte, /* Maximum length of zSql in bytes. */ 4301 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 4302 const char **pzTail /* OUT: Pointer to unused portion of zSql */ 4303 ); 4304 SQLITE_API int sqlite3_prepare_v3( 4305 sqlite3 *db, /* Database handle */ 4306 const char *zSql, /* SQL statement, UTF-8 encoded */ 4307 int nByte, /* Maximum length of zSql in bytes. */ 4308 unsigned int prepFlags, /* Zero or more SQLITE_PREPARE_ flags */ 4309 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 4310 const char **pzTail /* OUT: Pointer to unused portion of zSql */ 4311 ); 4312 SQLITE_API int sqlite3_prepare16( 4313 sqlite3 *db, /* Database handle */ 4314 const void *zSql, /* SQL statement, UTF-16 encoded */ 4315 int nByte, /* Maximum length of zSql in bytes. */ 4316 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 4317 const void **pzTail /* OUT: Pointer to unused portion of zSql */ 4318 ); 4319 SQLITE_API int sqlite3_prepare16_v2( 4320 sqlite3 *db, /* Database handle */ 4321 const void *zSql, /* SQL statement, UTF-16 encoded */ 4322 int nByte, /* Maximum length of zSql in bytes. */ 4323 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 4324 const void **pzTail /* OUT: Pointer to unused portion of zSql */ 4325 ); 4326 SQLITE_API int sqlite3_prepare16_v3( 4327 sqlite3 *db, /* Database handle */ 4328 const void *zSql, /* SQL statement, UTF-16 encoded */ 4329 int nByte, /* Maximum length of zSql in bytes. */ 4330 unsigned int prepFlags, /* Zero or more SQLITE_PREPARE_ flags */ 4331 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 4332 const void **pzTail /* OUT: Pointer to unused portion of zSql */ 4333 ); 4334 4335 /* 4336 ** CAPI3REF: Retrieving Statement SQL 4337 ** METHOD: sqlite3_stmt 4338 ** 4339 ** ^The sqlite3_sql(P) interface returns a pointer to a copy of the UTF-8 4340 ** SQL text used to create [prepared statement] P if P was 4341 ** created by [sqlite3_prepare_v2()], [sqlite3_prepare_v3()], 4342 ** [sqlite3_prepare16_v2()], or [sqlite3_prepare16_v3()]. 4343 ** ^The sqlite3_expanded_sql(P) interface returns a pointer to a UTF-8 4344 ** string containing the SQL text of prepared statement P with 4345 ** [bound parameters] expanded. 4346 ** ^The sqlite3_normalized_sql(P) interface returns a pointer to a UTF-8 4347 ** string containing the normalized SQL text of prepared statement P. The 4348 ** semantics used to normalize a SQL statement are unspecified and subject 4349 ** to change. At a minimum, literal values will be replaced with suitable 4350 ** placeholders. 4351 ** 4352 ** ^(For example, if a prepared statement is created using the SQL 4353 ** text "SELECT $abc,:xyz" and if parameter $abc is bound to integer 2345 4354 ** and parameter :xyz is unbound, then sqlite3_sql() will return 4355 ** the original string, "SELECT $abc,:xyz" but sqlite3_expanded_sql() 4356 ** will return "SELECT 2345,NULL".)^ 4357 ** 4358 ** ^The sqlite3_expanded_sql() interface returns NULL if insufficient memory 4359 ** is available to hold the result, or if the result would exceed the 4360 ** the maximum string length determined by the [SQLITE_LIMIT_LENGTH]. 4361 ** 4362 ** ^The [SQLITE_TRACE_SIZE_LIMIT] compile-time option limits the size of 4363 ** bound parameter expansions. ^The [SQLITE_OMIT_TRACE] compile-time 4364 ** option causes sqlite3_expanded_sql() to always return NULL. 4365 ** 4366 ** ^The strings returned by sqlite3_sql(P) and sqlite3_normalized_sql(P) 4367 ** are managed by SQLite and are automatically freed when the prepared 4368 ** statement is finalized. 4369 ** ^The string returned by sqlite3_expanded_sql(P), on the other hand, 4370 ** is obtained from [sqlite3_malloc()] and must be freed by the application 4371 ** by passing it to [sqlite3_free()]. 4372 ** 4373 ** ^The sqlite3_normalized_sql() interface is only available if 4374 ** the [SQLITE_ENABLE_NORMALIZE] compile-time option is defined. 4375 */ 4376 SQLITE_API const char *sqlite3_sql(sqlite3_stmt *pStmt); 4377 SQLITE_API char *sqlite3_expanded_sql(sqlite3_stmt *pStmt); 4378 #ifdef SQLITE_ENABLE_NORMALIZE 4379 SQLITE_API const char *sqlite3_normalized_sql(sqlite3_stmt *pStmt); 4380 #endif 4381 4382 /* 4383 ** CAPI3REF: Determine If An SQL Statement Writes The Database 4384 ** METHOD: sqlite3_stmt 4385 ** 4386 ** ^The sqlite3_stmt_readonly(X) interface returns true (non-zero) if 4387 ** and only if the [prepared statement] X makes no direct changes to 4388 ** the content of the database file. 4389 ** 4390 ** Note that [application-defined SQL functions] or 4391 ** [virtual tables] might change the database indirectly as a side effect. 4392 ** ^(For example, if an application defines a function "eval()" that 4393 ** calls [sqlite3_exec()], then the following SQL statement would 4394 ** change the database file through side-effects: 4395 ** 4396 ** <blockquote><pre> 4397 ** SELECT eval('DELETE FROM t1') FROM t2; 4398 ** </pre></blockquote> 4399 ** 4400 ** But because the [SELECT] statement does not change the database file 4401 ** directly, sqlite3_stmt_readonly() would still return true.)^ 4402 ** 4403 ** ^Transaction control statements such as [BEGIN], [COMMIT], [ROLLBACK], 4404 ** [SAVEPOINT], and [RELEASE] cause sqlite3_stmt_readonly() to return true, 4405 ** since the statements themselves do not actually modify the database but 4406 ** rather they control the timing of when other statements modify the 4407 ** database. ^The [ATTACH] and [DETACH] statements also cause 4408 ** sqlite3_stmt_readonly() to return true since, while those statements 4409 ** change the configuration of a database connection, they do not make 4410 ** changes to the content of the database files on disk. 4411 ** ^The sqlite3_stmt_readonly() interface returns true for [BEGIN] since 4412 ** [BEGIN] merely sets internal flags, but the [BEGIN|BEGIN IMMEDIATE] and 4413 ** [BEGIN|BEGIN EXCLUSIVE] commands do touch the database and so 4414 ** sqlite3_stmt_readonly() returns false for those commands. 4415 ** 4416 ** ^This routine returns false if there is any possibility that the 4417 ** statement might change the database file. ^A false return does 4418 ** not guarantee that the statement will change the database file. 4419 ** ^For example, an UPDATE statement might have a WHERE clause that 4420 ** makes it a no-op, but the sqlite3_stmt_readonly() result would still 4421 ** be false. ^Similarly, a CREATE TABLE IF NOT EXISTS statement is a 4422 ** read-only no-op if the table already exists, but 4423 ** sqlite3_stmt_readonly() still returns false for such a statement. 4424 ** 4425 ** ^If prepared statement X is an [EXPLAIN] or [EXPLAIN QUERY PLAN] 4426 ** statement, then sqlite3_stmt_readonly(X) returns the same value as 4427 ** if the EXPLAIN or EXPLAIN QUERY PLAN prefix were omitted. 4428 */ 4429 SQLITE_API int sqlite3_stmt_readonly(sqlite3_stmt *pStmt); 4430 4431 /* 4432 ** CAPI3REF: Query The EXPLAIN Setting For A Prepared Statement 4433 ** METHOD: sqlite3_stmt 4434 ** 4435 ** ^The sqlite3_stmt_isexplain(S) interface returns 1 if the 4436 ** prepared statement S is an EXPLAIN statement, or 2 if the 4437 ** statement S is an EXPLAIN QUERY PLAN. 4438 ** ^The sqlite3_stmt_isexplain(S) interface returns 0 if S is 4439 ** an ordinary statement or a NULL pointer. 4440 */ 4441 SQLITE_API int sqlite3_stmt_isexplain(sqlite3_stmt *pStmt); 4442 4443 /* 4444 ** CAPI3REF: Change The EXPLAIN Setting For A Prepared Statement 4445 ** METHOD: sqlite3_stmt 4446 ** 4447 ** The sqlite3_stmt_explain(S,E) interface changes the EXPLAIN 4448 ** setting for [prepared statement] S. If E is zero, then S becomes 4449 ** a normal prepared statement. If E is 1, then S behaves as if 4450 ** its SQL text began with "[EXPLAIN]". If E is 2, then S behaves as if 4451 ** its SQL text began with "[EXPLAIN QUERY PLAN]". 4452 ** 4453 ** Calling sqlite3_stmt_explain(S,E) might cause S to be reprepared. 4454 ** SQLite tries to avoid a reprepare, but a reprepare might be necessary 4455 ** on the first transition into EXPLAIN or EXPLAIN QUERY PLAN mode. 4456 ** 4457 ** Because of the potential need to reprepare, a call to 4458 ** sqlite3_stmt_explain(S,E) will fail with SQLITE_ERROR if S cannot be 4459 ** reprepared because it was created using [sqlite3_prepare()] instead of 4460 ** the newer [sqlite3_prepare_v2()] or [sqlite3_prepare_v3()] interfaces and 4461 ** hence has no saved SQL text with which to reprepare. 4462 ** 4463 ** Changing the explain setting for a prepared statement does not change 4464 ** the original SQL text for the statement. Hence, if the SQL text originally 4465 ** began with EXPLAIN or EXPLAIN QUERY PLAN, but sqlite3_stmt_explain(S,0) 4466 ** is called to convert the statement into an ordinary statement, the EXPLAIN 4467 ** or EXPLAIN QUERY PLAN keywords will still appear in the sqlite3_sql(S) 4468 ** output, even though the statement now acts like a normal SQL statement. 4469 ** 4470 ** This routine returns SQLITE_OK if the explain mode is successfully 4471 ** changed, or an error code if the explain mode could not be changed. 4472 ** The explain mode cannot be changed while a statement is active. 4473 ** Hence, it is good practice to call [sqlite3_reset(S)] 4474 ** immediately prior to calling sqlite3_stmt_explain(S,E). 4475 */ 4476 SQLITE_API int sqlite3_stmt_explain(sqlite3_stmt *pStmt, int eMode); 4477 4478 /* 4479 ** CAPI3REF: Determine If A Prepared Statement Has Been Reset 4480 ** METHOD: sqlite3_stmt 4481 ** 4482 ** ^The sqlite3_stmt_busy(S) interface returns true (non-zero) if the 4483 ** [prepared statement] S has been stepped at least once using 4484 ** [sqlite3_step(S)] but has neither run to completion (returned 4485 ** [SQLITE_DONE] from [sqlite3_step(S)]) nor 4486 ** been reset using [sqlite3_reset(S)]. ^The sqlite3_stmt_busy(S) 4487 ** interface returns false if S is a NULL pointer. If S is not a 4488 ** NULL pointer and is not a pointer to a valid [prepared statement] 4489 ** object, then the behavior is undefined and probably undesirable. 4490 ** 4491 ** This interface can be used in combination [sqlite3_next_stmt()] 4492 ** to locate all prepared statements associated with a database 4493 ** connection that are in need of being reset. This can be used, 4494 ** for example, in diagnostic routines to search for prepared 4495 ** statements that are holding a transaction open. 4496 */ 4497 SQLITE_API int sqlite3_stmt_busy(sqlite3_stmt*); 4498 4499 /* 4500 ** CAPI3REF: Dynamically Typed Value Object 4501 ** KEYWORDS: {protected sqlite3_value} {unprotected sqlite3_value} 4502 ** 4503 ** SQLite uses the sqlite3_value object to represent all values 4504 ** that can be stored in a database table. SQLite uses dynamic typing 4505 ** for the values it stores. ^Values stored in sqlite3_value objects 4506 ** can be integers, floating point values, strings, BLOBs, or NULL. 4507 ** 4508 ** An sqlite3_value object may be either "protected" or "unprotected". 4509 ** Some interfaces require a protected sqlite3_value. Other interfaces 4510 ** will accept either a protected or an unprotected sqlite3_value. 4511 ** Every interface that accepts sqlite3_value arguments specifies 4512 ** whether or not it requires a protected sqlite3_value. The 4513 ** [sqlite3_value_dup()] interface can be used to construct a new 4514 ** protected sqlite3_value from an unprotected sqlite3_value. 4515 ** 4516 ** The terms "protected" and "unprotected" refer to whether or not 4517 ** a mutex is held. An internal mutex is held for a protected 4518 ** sqlite3_value object but no mutex is held for an unprotected 4519 ** sqlite3_value object. If SQLite is compiled to be single-threaded 4520 ** (with [SQLITE_THREADSAFE=0] and with [sqlite3_threadsafe()] returning 0) 4521 ** or if SQLite is run in one of reduced mutex modes 4522 ** [SQLITE_CONFIG_SINGLETHREAD] or [SQLITE_CONFIG_MULTITHREAD] 4523 ** then there is no distinction between protected and unprotected 4524 ** sqlite3_value objects and they can be used interchangeably. However, 4525 ** for maximum code portability it is recommended that applications 4526 ** still make the distinction between protected and unprotected 4527 ** sqlite3_value objects even when not strictly required. 4528 ** 4529 ** ^The sqlite3_value objects that are passed as parameters into the 4530 ** implementation of [application-defined SQL functions] are protected. 4531 ** ^The sqlite3_value objects returned by [sqlite3_vtab_rhs_value()] 4532 ** are protected. 4533 ** ^The sqlite3_value object returned by 4534 ** [sqlite3_column_value()] is unprotected. 4535 ** Unprotected sqlite3_value objects may only be used as arguments 4536 ** to [sqlite3_result_value()], [sqlite3_bind_value()], and 4537 ** [sqlite3_value_dup()]. 4538 ** The [sqlite3_value_blob | sqlite3_value_type()] family of 4539 ** interfaces require protected sqlite3_value objects. 4540 */ 4541 typedef struct sqlite3_value sqlite3_value; 4542 4543 /* 4544 ** CAPI3REF: SQL Function Context Object 4545 ** 4546 ** The context in which an SQL function executes is stored in an 4547 ** sqlite3_context object. ^A pointer to an sqlite3_context object 4548 ** is always first parameter to [application-defined SQL functions]. 4549 ** The application-defined SQL function implementation will pass this 4550 ** pointer through into calls to [sqlite3_result_int | sqlite3_result()], 4551 ** [sqlite3_aggregate_context()], [sqlite3_user_data()], 4552 ** [sqlite3_context_db_handle()], [sqlite3_get_auxdata()], 4553 ** and/or [sqlite3_set_auxdata()]. 4554 */ 4555 typedef struct sqlite3_context sqlite3_context; 4556 4557 /* 4558 ** CAPI3REF: Binding Values To Prepared Statements 4559 ** KEYWORDS: {host parameter} {host parameters} {host parameter name} 4560 ** KEYWORDS: {SQL parameter} {SQL parameters} {parameter binding} 4561 ** METHOD: sqlite3_stmt 4562 ** 4563 ** ^(In the SQL statement text input to [sqlite3_prepare_v2()] and its variants, 4564 ** literals may be replaced by a [parameter] that matches one of following 4565 ** templates: 4566 ** 4567 ** <ul> 4568 ** <li> ? 4569 ** <li> ?NNN 4570 ** <li> :VVV 4571 ** <li> @VVV 4572 ** <li> $VVV 4573 ** </ul> 4574 ** 4575 ** In the templates above, NNN represents an integer literal, 4576 ** and VVV represents an alphanumeric identifier.)^ ^The values of these 4577 ** parameters (also called "host parameter names" or "SQL parameters") 4578 ** can be set using the sqlite3_bind_*() routines defined here. 4579 ** 4580 ** ^The first argument to the sqlite3_bind_*() routines is always 4581 ** a pointer to the [sqlite3_stmt] object returned from 4582 ** [sqlite3_prepare_v2()] or its variants. 4583 ** 4584 ** ^The second argument is the index of the SQL parameter to be set. 4585 ** ^The leftmost SQL parameter has an index of 1. ^When the same named 4586 ** SQL parameter is used more than once, second and subsequent 4587 ** occurrences have the same index as the first occurrence. 4588 ** ^The index for named parameters can be looked up using the 4589 ** [sqlite3_bind_parameter_index()] API if desired. ^The index 4590 ** for "?NNN" parameters is the value of NNN. 4591 ** ^The NNN value must be between 1 and the [sqlite3_limit()] 4592 ** parameter [SQLITE_LIMIT_VARIABLE_NUMBER] (default value: 32766). 4593 ** 4594 ** ^The third argument is the value to bind to the parameter. 4595 ** ^If the third parameter to sqlite3_bind_text() or sqlite3_bind_text16() 4596 ** or sqlite3_bind_blob() is a NULL pointer then the fourth parameter 4597 ** is ignored and the end result is the same as sqlite3_bind_null(). 4598 ** ^If the third parameter to sqlite3_bind_text() is not NULL, then 4599 ** it should be a pointer to well-formed UTF8 text. 4600 ** ^If the third parameter to sqlite3_bind_text16() is not NULL, then 4601 ** it should be a pointer to well-formed UTF16 text. 4602 ** ^If the third parameter to sqlite3_bind_text64() is not NULL, then 4603 ** it should be a pointer to a well-formed unicode string that is 4604 ** either UTF8 if the sixth parameter is SQLITE_UTF8, or UTF16 4605 ** otherwise. 4606 ** 4607 ** [[byte-order determination rules]] ^The byte-order of 4608 ** UTF16 input text is determined by the byte-order mark (BOM, U+FEFF) 4609 ** found in first character, which is removed, or in the absence of a BOM 4610 ** the byte order is the native byte order of the host 4611 ** machine for sqlite3_bind_text16() or the byte order specified in 4612 ** the 6th parameter for sqlite3_bind_text64().)^ 4613 ** ^If UTF16 input text contains invalid unicode 4614 ** characters, then SQLite might change those invalid characters 4615 ** into the unicode replacement character: U+FFFD. 4616 ** 4617 ** ^(In those routines that have a fourth argument, its value is the 4618 ** number of bytes in the parameter. To be clear: the value is the 4619 ** number of <u>bytes</u> in the value, not the number of characters.)^ 4620 ** ^If the fourth parameter to sqlite3_bind_text() or sqlite3_bind_text16() 4621 ** is negative, then the length of the string is 4622 ** the number of bytes up to the first zero terminator. 4623 ** If the fourth parameter to sqlite3_bind_blob() is negative, then 4624 ** the behavior is undefined. 4625 ** If a non-negative fourth parameter is provided to sqlite3_bind_text() 4626 ** or sqlite3_bind_text16() or sqlite3_bind_text64() then 4627 ** that parameter must be the byte offset 4628 ** where the NUL terminator would occur assuming the string were NUL 4629 ** terminated. If any NUL characters occurs at byte offsets less than 4630 ** the value of the fourth parameter then the resulting string value will 4631 ** contain embedded NULs. The result of expressions involving strings 4632 ** with embedded NULs is undefined. 4633 ** 4634 ** ^The fifth argument to the BLOB and string binding interfaces controls 4635 ** or indicates the lifetime of the object referenced by the third parameter. 4636 ** These three options exist: 4637 ** ^ (1) A destructor to dispose of the BLOB or string after SQLite has finished 4638 ** with it may be passed. ^It is called to dispose of the BLOB or string even 4639 ** if the call to the bind API fails, except the destructor is not called if 4640 ** the third parameter is a NULL pointer or the fourth parameter is negative. 4641 ** ^ (2) The special constant, [SQLITE_STATIC], may be passed to indicate that 4642 ** the application remains responsible for disposing of the object. ^In this 4643 ** case, the object and the provided pointer to it must remain valid until 4644 ** either the prepared statement is finalized or the same SQL parameter is 4645 ** bound to something else, whichever occurs sooner. 4646 ** ^ (3) The constant, [SQLITE_TRANSIENT], may be passed to indicate that the 4647 ** object is to be copied prior to the return from sqlite3_bind_*(). ^The 4648 ** object and pointer to it must remain valid until then. ^SQLite will then 4649 ** manage the lifetime of its private copy. 4650 ** 4651 ** ^The sixth argument to sqlite3_bind_text64() must be one of 4652 ** [SQLITE_UTF8], [SQLITE_UTF16], [SQLITE_UTF16BE], or [SQLITE_UTF16LE] 4653 ** to specify the encoding of the text in the third parameter. If 4654 ** the sixth argument to sqlite3_bind_text64() is not one of the 4655 ** allowed values shown above, or if the text encoding is different 4656 ** from the encoding specified by the sixth parameter, then the behavior 4657 ** is undefined. 4658 ** 4659 ** ^The sqlite3_bind_zeroblob() routine binds a BLOB of length N that 4660 ** is filled with zeroes. ^A zeroblob uses a fixed amount of memory 4661 ** (just an integer to hold its size) while it is being processed. 4662 ** Zeroblobs are intended to serve as placeholders for BLOBs whose 4663 ** content is later written using 4664 ** [sqlite3_blob_open | incremental BLOB I/O] routines. 4665 ** ^A negative value for the zeroblob results in a zero-length BLOB. 4666 ** 4667 ** ^The sqlite3_bind_pointer(S,I,P,T,D) routine causes the I-th parameter in 4668 ** [prepared statement] S to have an SQL value of NULL, but to also be 4669 ** associated with the pointer P of type T. ^D is either a NULL pointer or 4670 ** a pointer to a destructor function for P. ^SQLite will invoke the 4671 ** destructor D with a single argument of P when it is finished using 4672 ** P. The T parameter should be a static string, preferably a string 4673 ** literal. The sqlite3_bind_pointer() routine is part of the 4674 ** [pointer passing interface] added for SQLite 3.20.0. 4675 ** 4676 ** ^If any of the sqlite3_bind_*() routines are called with a NULL pointer 4677 ** for the [prepared statement] or with a prepared statement for which 4678 ** [sqlite3_step()] has been called more recently than [sqlite3_reset()], 4679 ** then the call will return [SQLITE_MISUSE]. If any sqlite3_bind_() 4680 ** routine is passed a [prepared statement] that has been finalized, the 4681 ** result is undefined and probably harmful. 4682 ** 4683 ** ^Bindings are not cleared by the [sqlite3_reset()] routine. 4684 ** ^Unbound parameters are interpreted as NULL. 4685 ** 4686 ** ^The sqlite3_bind_* routines return [SQLITE_OK] on success or an 4687 ** [error code] if anything goes wrong. 4688 ** ^[SQLITE_TOOBIG] might be returned if the size of a string or BLOB 4689 ** exceeds limits imposed by [sqlite3_limit]([SQLITE_LIMIT_LENGTH]) or 4690 ** [SQLITE_MAX_LENGTH]. 4691 ** ^[SQLITE_RANGE] is returned if the parameter 4692 ** index is out of range. ^[SQLITE_NOMEM] is returned if malloc() fails. 4693 ** 4694 ** See also: [sqlite3_bind_parameter_count()], 4695 ** [sqlite3_bind_parameter_name()], and [sqlite3_bind_parameter_index()]. 4696 */ 4697 SQLITE_API int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*)); 4698 SQLITE_API int sqlite3_bind_blob64(sqlite3_stmt*, int, const void*, sqlite3_uint64, 4699 void(*)(void*)); 4700 SQLITE_API int sqlite3_bind_double(sqlite3_stmt*, int, double); 4701 SQLITE_API int sqlite3_bind_int(sqlite3_stmt*, int, int); 4702 SQLITE_API int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite3_int64); 4703 SQLITE_API int sqlite3_bind_null(sqlite3_stmt*, int); 4704 SQLITE_API int sqlite3_bind_text(sqlite3_stmt*,int,const char*,int,void(*)(void*)); 4705 SQLITE_API int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*)); 4706 SQLITE_API int sqlite3_bind_text64(sqlite3_stmt*, int, const char*, sqlite3_uint64, 4707 void(*)(void*), unsigned char encoding); 4708 SQLITE_API int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*); 4709 SQLITE_API int sqlite3_bind_pointer(sqlite3_stmt*, int, void*, const char*,void(*)(void*)); 4710 SQLITE_API int sqlite3_bind_zeroblob(sqlite3_stmt*, int, int n); 4711 SQLITE_API int sqlite3_bind_zeroblob64(sqlite3_stmt*, int, sqlite3_uint64); 4712 4713 /* 4714 ** CAPI3REF: Number Of SQL Parameters 4715 ** METHOD: sqlite3_stmt 4716 ** 4717 ** ^This routine can be used to find the number of [SQL parameters] 4718 ** in a [prepared statement]. SQL parameters are tokens of the 4719 ** form "?", "?NNN", ":AAA", "$AAA", or "@AAA" that serve as 4720 ** placeholders for values that are [sqlite3_bind_blob | bound] 4721 ** to the parameters at a later time. 4722 ** 4723 ** ^(This routine actually returns the index of the largest (rightmost) 4724 ** parameter. For all forms except ?NNN, this will correspond to the 4725 ** number of unique parameters. If parameters of the ?NNN form are used, 4726 ** there may be gaps in the list.)^ 4727 ** 4728 ** See also: [sqlite3_bind_blob|sqlite3_bind()], 4729 ** [sqlite3_bind_parameter_name()], and 4730 ** [sqlite3_bind_parameter_index()]. 4731 */ 4732 SQLITE_API int sqlite3_bind_parameter_count(sqlite3_stmt*); 4733 4734 /* 4735 ** CAPI3REF: Name Of A Host Parameter 4736 ** METHOD: sqlite3_stmt 4737 ** 4738 ** ^The sqlite3_bind_parameter_name(P,N) interface returns 4739 ** the name of the N-th [SQL parameter] in the [prepared statement] P. 4740 ** ^(SQL parameters of the form "?NNN" or ":AAA" or "@AAA" or "$AAA" 4741 ** have a name which is the string "?NNN" or ":AAA" or "@AAA" or "$AAA" 4742 ** respectively. 4743 ** In other words, the initial ":" or "$" or "@" or "?" 4744 ** is included as part of the name.)^ 4745 ** ^Parameters of the form "?" without a following integer have no name 4746 ** and are referred to as "nameless" or "anonymous parameters". 4747 ** 4748 ** ^The first host parameter has an index of 1, not 0. 4749 ** 4750 ** ^If the value N is out of range or if the N-th parameter is 4751 ** nameless, then NULL is returned. ^The returned string is 4752 ** always in UTF-8 encoding even if the named parameter was 4753 ** originally specified as UTF-16 in [sqlite3_prepare16()], 4754 ** [sqlite3_prepare16_v2()], or [sqlite3_prepare16_v3()]. 4755 ** 4756 ** See also: [sqlite3_bind_blob|sqlite3_bind()], 4757 ** [sqlite3_bind_parameter_count()], and 4758 ** [sqlite3_bind_parameter_index()]. 4759 */ 4760 SQLITE_API const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int); 4761 4762 /* 4763 ** CAPI3REF: Index Of A Parameter With A Given Name 4764 ** METHOD: sqlite3_stmt 4765 ** 4766 ** ^Return the index of an SQL parameter given its name. ^The 4767 ** index value returned is suitable for use as the second 4768 ** parameter to [sqlite3_bind_blob|sqlite3_bind()]. ^A zero 4769 ** is returned if no matching parameter is found. ^The parameter 4770 ** name must be given in UTF-8 even if the original statement 4771 ** was prepared from UTF-16 text using [sqlite3_prepare16_v2()] or 4772 ** [sqlite3_prepare16_v3()]. 4773 ** 4774 ** See also: [sqlite3_bind_blob|sqlite3_bind()], 4775 ** [sqlite3_bind_parameter_count()], and 4776 ** [sqlite3_bind_parameter_name()]. 4777 */ 4778 SQLITE_API int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName); 4779 4780 /* 4781 ** CAPI3REF: Reset All Bindings On A Prepared Statement 4782 ** METHOD: sqlite3_stmt 4783 ** 4784 ** ^Contrary to the intuition of many, [sqlite3_reset()] does not reset 4785 ** the [sqlite3_bind_blob | bindings] on a [prepared statement]. 4786 ** ^Use this routine to reset all host parameters to NULL. 4787 */ 4788 SQLITE_API int sqlite3_clear_bindings(sqlite3_stmt*); 4789 4790 /* 4791 ** CAPI3REF: Number Of Columns In A Result Set 4792 ** METHOD: sqlite3_stmt 4793 ** 4794 ** ^Return the number of columns in the result set returned by the 4795 ** [prepared statement]. ^If this routine returns 0, that means the 4796 ** [prepared statement] returns no data (for example an [UPDATE]). 4797 ** ^However, just because this routine returns a positive number does not 4798 ** mean that one or more rows of data will be returned. ^A SELECT statement 4799 ** will always have a positive sqlite3_column_count() but depending on the 4800 ** WHERE clause constraints and the table content, it might return no rows. 4801 ** 4802 ** See also: [sqlite3_data_count()] 4803 */ 4804 SQLITE_API int sqlite3_column_count(sqlite3_stmt *pStmt); 4805 4806 /* 4807 ** CAPI3REF: Column Names In A Result Set 4808 ** METHOD: sqlite3_stmt 4809 ** 4810 ** ^These routines return the name assigned to a particular column 4811 ** in the result set of a [SELECT] statement. ^The sqlite3_column_name() 4812 ** interface returns a pointer to a zero-terminated UTF-8 string 4813 ** and sqlite3_column_name16() returns a pointer to a zero-terminated 4814 ** UTF-16 string. ^The first parameter is the [prepared statement] 4815 ** that implements the [SELECT] statement. ^The second parameter is the 4816 ** column number. ^The leftmost column is number 0. 4817 ** 4818 ** ^The returned string pointer is valid until either the [prepared statement] 4819 ** is destroyed by [sqlite3_finalize()] or until the statement is automatically 4820 ** reprepared by the first call to [sqlite3_step()] for a particular run 4821 ** or until the next call to 4822 ** sqlite3_column_name() or sqlite3_column_name16() on the same column. 4823 ** 4824 ** ^If sqlite3_malloc() fails during the processing of either routine 4825 ** (for example during a conversion from UTF-8 to UTF-16) then a 4826 ** NULL pointer is returned. 4827 ** 4828 ** ^The name of a result column is the value of the "AS" clause for 4829 ** that column, if there is an AS clause. If there is no AS clause 4830 ** then the name of the column is unspecified and may change from 4831 ** one release of SQLite to the next. 4832 */ 4833 SQLITE_API const char *sqlite3_column_name(sqlite3_stmt*, int N); 4834 SQLITE_API const void *sqlite3_column_name16(sqlite3_stmt*, int N); 4835 4836 /* 4837 ** CAPI3REF: Source Of Data In A Query Result 4838 ** METHOD: sqlite3_stmt 4839 ** 4840 ** ^These routines provide a means to determine the database, table, and 4841 ** table column that is the origin of a particular result column in 4842 ** [SELECT] statement. 4843 ** ^The name of the database or table or column can be returned as 4844 ** either a UTF-8 or UTF-16 string. ^The _database_ routines return 4845 ** the database name, the _table_ routines return the table name, and 4846 ** the origin_ routines return the column name. 4847 ** ^The returned string is valid until the [prepared statement] is destroyed 4848 ** using [sqlite3_finalize()] or until the statement is automatically 4849 ** reprepared by the first call to [sqlite3_step()] for a particular run 4850 ** or until the same information is requested 4851 ** again in a different encoding. 4852 ** 4853 ** ^The names returned are the original un-aliased names of the 4854 ** database, table, and column. 4855 ** 4856 ** ^The first argument to these interfaces is a [prepared statement]. 4857 ** ^These functions return information about the Nth result column returned by 4858 ** the statement, where N is the second function argument. 4859 ** ^The left-most column is column 0 for these routines. 4860 ** 4861 ** ^If the Nth column returned by the statement is an expression or 4862 ** subquery and is not a column value, then all of these functions return 4863 ** NULL. ^These routines might also return NULL if a memory allocation error 4864 ** occurs. ^Otherwise, they return the name of the attached database, table, 4865 ** or column that query result column was extracted from. 4866 ** 4867 ** ^As with all other SQLite APIs, those whose names end with "16" return 4868 ** UTF-16 encoded strings and the other functions return UTF-8. 4869 ** 4870 ** ^These APIs are only available if the library was compiled with the 4871 ** [SQLITE_ENABLE_COLUMN_METADATA] C-preprocessor symbol. 4872 ** 4873 ** If two or more threads call one or more 4874 ** [sqlite3_column_database_name | column metadata interfaces] 4875 ** for the same [prepared statement] and result column 4876 ** at the same time then the results are undefined. 4877 */ 4878 SQLITE_API const char *sqlite3_column_database_name(sqlite3_stmt*,int); 4879 SQLITE_API const void *sqlite3_column_database_name16(sqlite3_stmt*,int); 4880 SQLITE_API const char *sqlite3_column_table_name(sqlite3_stmt*,int); 4881 SQLITE_API const void *sqlite3_column_table_name16(sqlite3_stmt*,int); 4882 SQLITE_API const char *sqlite3_column_origin_name(sqlite3_stmt*,int); 4883 SQLITE_API const void *sqlite3_column_origin_name16(sqlite3_stmt*,int); 4884 4885 /* 4886 ** CAPI3REF: Declared Datatype Of A Query Result 4887 ** METHOD: sqlite3_stmt 4888 ** 4889 ** ^(The first parameter is a [prepared statement]. 4890 ** If this statement is a [SELECT] statement and the Nth column of the 4891 ** returned result set of that [SELECT] is a table column (not an 4892 ** expression or subquery) then the declared type of the table 4893 ** column is returned.)^ ^If the Nth column of the result set is an 4894 ** expression or subquery, then a NULL pointer is returned. 4895 ** ^The returned string is always UTF-8 encoded. 4896 ** 4897 ** ^(For example, given the database schema: 4898 ** 4899 ** CREATE TABLE t1(c1 VARIANT); 4900 ** 4901 ** and the following statement to be compiled: 4902 ** 4903 ** SELECT c1 + 1, c1 FROM t1; 4904 ** 4905 ** this routine would return the string "VARIANT" for the second result 4906 ** column (i==1), and a NULL pointer for the first result column (i==0).)^ 4907 ** 4908 ** ^SQLite uses dynamic run-time typing. ^So just because a column 4909 ** is declared to contain a particular type does not mean that the 4910 ** data stored in that column is of the declared type. SQLite is 4911 ** strongly typed, but the typing is dynamic not static. ^Type 4912 ** is associated with individual values, not with the containers 4913 ** used to hold those values. 4914 */ 4915 SQLITE_API const char *sqlite3_column_decltype(sqlite3_stmt*,int); 4916 SQLITE_API const void *sqlite3_column_decltype16(sqlite3_stmt*,int); 4917 4918 /* 4919 ** CAPI3REF: Evaluate An SQL Statement 4920 ** METHOD: sqlite3_stmt 4921 ** 4922 ** After a [prepared statement] has been prepared using any of 4923 ** [sqlite3_prepare_v2()], [sqlite3_prepare_v3()], [sqlite3_prepare16_v2()], 4924 ** or [sqlite3_prepare16_v3()] or one of the legacy 4925 ** interfaces [sqlite3_prepare()] or [sqlite3_prepare16()], this function 4926 ** must be called one or more times to evaluate the statement. 4927 ** 4928 ** The details of the behavior of the sqlite3_step() interface depend 4929 ** on whether the statement was prepared using the newer "vX" interfaces 4930 ** [sqlite3_prepare_v3()], [sqlite3_prepare_v2()], [sqlite3_prepare16_v3()], 4931 ** [sqlite3_prepare16_v2()] or the older legacy 4932 ** interfaces [sqlite3_prepare()] and [sqlite3_prepare16()]. The use of the 4933 ** new "vX" interface is recommended for new applications but the legacy 4934 ** interface will continue to be supported. 4935 ** 4936 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY], 4937 ** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE]. 4938 ** ^With the "v2" interface, any of the other [result codes] or 4939 ** [extended result codes] might be returned as well. 4940 ** 4941 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the 4942 ** database locks it needs to do its job. ^If the statement is a [COMMIT] 4943 ** or occurs outside of an explicit transaction, then you can retry the 4944 ** statement. If the statement is not a [COMMIT] and occurs within an 4945 ** explicit transaction then you should rollback the transaction before 4946 ** continuing. 4947 ** 4948 ** ^[SQLITE_DONE] means that the statement has finished executing 4949 ** successfully. sqlite3_step() should not be called again on this virtual 4950 ** machine without first calling [sqlite3_reset()] to reset the virtual 4951 ** machine back to its initial state. 4952 ** 4953 ** ^If the SQL statement being executed returns any data, then [SQLITE_ROW] 4954 ** is returned each time a new row of data is ready for processing by the 4955 ** caller. The values may be accessed using the [column access functions]. 4956 ** sqlite3_step() is called again to retrieve the next row of data. 4957 ** 4958 ** ^[SQLITE_ERROR] means that a run-time error (such as a constraint 4959 ** violation) has occurred. sqlite3_step() should not be called again on 4960 ** the VM. More information may be found by calling [sqlite3_errmsg()]. 4961 ** ^With the legacy interface, a more specific error code (for example, 4962 ** [SQLITE_INTERRUPT], [SQLITE_SCHEMA], [SQLITE_CORRUPT], and so forth) 4963 ** can be obtained by calling [sqlite3_reset()] on the 4964 ** [prepared statement]. ^In the "v2" interface, 4965 ** the more specific error code is returned directly by sqlite3_step(). 4966 ** 4967 ** [SQLITE_MISUSE] means that the this routine was called inappropriately. 4968 ** Perhaps it was called on a [prepared statement] that has 4969 ** already been [sqlite3_finalize | finalized] or on one that had 4970 ** previously returned [SQLITE_ERROR] or [SQLITE_DONE]. Or it could 4971 ** be the case that the same database connection is being used by two or 4972 ** more threads at the same moment in time. 4973 ** 4974 ** For all versions of SQLite up to and including 3.6.23.1, a call to 4975 ** [sqlite3_reset()] was required after sqlite3_step() returned anything 4976 ** other than [SQLITE_ROW] before any subsequent invocation of 4977 ** sqlite3_step(). Failure to reset the prepared statement using 4978 ** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from 4979 ** sqlite3_step(). But after [version 3.6.23.1] ([dateof:3.6.23.1], 4980 ** sqlite3_step() began 4981 ** calling [sqlite3_reset()] automatically in this circumstance rather 4982 ** than returning [SQLITE_MISUSE]. This is not considered a compatibility 4983 ** break because any application that ever receives an SQLITE_MISUSE error 4984 ** is broken by definition. The [SQLITE_OMIT_AUTORESET] compile-time option 4985 ** can be used to restore the legacy behavior. 4986 ** 4987 ** <b>Goofy Interface Alert:</b> In the legacy interface, the sqlite3_step() 4988 ** API always returns a generic error code, [SQLITE_ERROR], following any 4989 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call 4990 ** [sqlite3_reset()] or [sqlite3_finalize()] in order to find one of the 4991 ** specific [error codes] that better describes the error. 4992 ** We admit that this is a goofy design. The problem has been fixed 4993 ** with the "v2" interface. If you prepare all of your SQL statements 4994 ** using [sqlite3_prepare_v3()] or [sqlite3_prepare_v2()] 4995 ** or [sqlite3_prepare16_v2()] or [sqlite3_prepare16_v3()] instead 4996 ** of the legacy [sqlite3_prepare()] and [sqlite3_prepare16()] interfaces, 4997 ** then the more specific [error codes] are returned directly 4998 ** by sqlite3_step(). The use of the "vX" interfaces is recommended. 4999 */ 5000 SQLITE_API int sqlite3_step(sqlite3_stmt*); 5001 5002 /* 5003 ** CAPI3REF: Number of columns in a result set 5004 ** METHOD: sqlite3_stmt 5005 ** 5006 ** ^The sqlite3_data_count(P) interface returns the number of columns in the 5007 ** current row of the result set of [prepared statement] P. 5008 ** ^If prepared statement P does not have results ready to return 5009 ** (via calls to the [sqlite3_column_int | sqlite3_column()] family of 5010 ** interfaces) then sqlite3_data_count(P) returns 0. 5011 ** ^The sqlite3_data_count(P) routine also returns 0 if P is a NULL pointer. 5012 ** ^The sqlite3_data_count(P) routine returns 0 if the previous call to 5013 ** [sqlite3_step](P) returned [SQLITE_DONE]. ^The sqlite3_data_count(P) 5014 ** will return non-zero if previous call to [sqlite3_step](P) returned 5015 ** [SQLITE_ROW], except in the case of the [PRAGMA incremental_vacuum] 5016 ** where it always returns zero since each step of that multi-step 5017 ** pragma returns 0 columns of data. 5018 ** 5019 ** See also: [sqlite3_column_count()] 5020 */ 5021 SQLITE_API int sqlite3_data_count(sqlite3_stmt *pStmt); 5022 5023 /* 5024 ** CAPI3REF: Fundamental Datatypes 5025 ** KEYWORDS: SQLITE_TEXT 5026 ** 5027 ** ^(Every value in SQLite has one of five fundamental datatypes: 5028 ** 5029 ** <ul> 5030 ** <li> 64-bit signed integer 5031 ** <li> 64-bit IEEE floating point number 5032 ** <li> string 5033 ** <li> BLOB 5034 ** <li> NULL 5035 ** </ul>)^ 5036 ** 5037 ** These constants are codes for each of those types. 5038 ** 5039 ** Note that the SQLITE_TEXT constant was also used in SQLite version 2 5040 ** for a completely different meaning. Software that links against both 5041 ** SQLite version 2 and SQLite version 3 should use SQLITE3_TEXT, not 5042 ** SQLITE_TEXT. 5043 */ 5044 #define SQLITE_INTEGER 1 5045 #define SQLITE_FLOAT 2 5046 #define SQLITE_BLOB 4 5047 #define SQLITE_NULL 5 5048 #ifdef SQLITE_TEXT 5049 # undef SQLITE_TEXT 5050 #else 5051 # define SQLITE_TEXT 3 5052 #endif 5053 #define SQLITE3_TEXT 3 5054 5055 /* 5056 ** CAPI3REF: Result Values From A Query 5057 ** KEYWORDS: {column access functions} 5058 ** METHOD: sqlite3_stmt 5059 ** 5060 ** <b>Summary:</b> 5061 ** <blockquote><table border=0 cellpadding=0 cellspacing=0> 5062 ** <tr><td><b>sqlite3_column_blob</b><td>→<td>BLOB result 5063 ** <tr><td><b>sqlite3_column_double</b><td>→<td>REAL result 5064 ** <tr><td><b>sqlite3_column_int</b><td>→<td>32-bit INTEGER result 5065 ** <tr><td><b>sqlite3_column_int64</b><td>→<td>64-bit INTEGER result 5066 ** <tr><td><b>sqlite3_column_text</b><td>→<td>UTF-8 TEXT result 5067 ** <tr><td><b>sqlite3_column_text16</b><td>→<td>UTF-16 TEXT result 5068 ** <tr><td><b>sqlite3_column_value</b><td>→<td>The result as an 5069 ** [sqlite3_value|unprotected sqlite3_value] object. 5070 ** <tr><td> <td> <td> 5071 ** <tr><td><b>sqlite3_column_bytes</b><td>→<td>Size of a BLOB 5072 ** or a UTF-8 TEXT result in bytes 5073 ** <tr><td><b>sqlite3_column_bytes16 </b> 5074 ** <td>→ <td>Size of UTF-16 5075 ** TEXT in bytes 5076 ** <tr><td><b>sqlite3_column_type</b><td>→<td>Default 5077 ** datatype of the result 5078 ** </table></blockquote> 5079 ** 5080 ** <b>Details:</b> 5081 ** 5082 ** ^These routines return information about a single column of the current 5083 ** result row of a query. ^In every case the first argument is a pointer 5084 ** to the [prepared statement] that is being evaluated (the [sqlite3_stmt*] 5085 ** that was returned from [sqlite3_prepare_v2()] or one of its variants) 5086 ** and the second argument is the index of the column for which information 5087 ** should be returned. ^The leftmost column of the result set has the index 0. 5088 ** ^The number of columns in the result can be determined using 5089 ** [sqlite3_column_count()]. 5090 ** 5091 ** If the SQL statement does not currently point to a valid row, or if the 5092 ** column index is out of range, the result is undefined. 5093 ** These routines may only be called when the most recent call to 5094 ** [sqlite3_step()] has returned [SQLITE_ROW] and neither 5095 ** [sqlite3_reset()] nor [sqlite3_finalize()] have been called subsequently. 5096 ** If any of these routines are called after [sqlite3_reset()] or 5097 ** [sqlite3_finalize()] or after [sqlite3_step()] has returned 5098 ** something other than [SQLITE_ROW], the results are undefined. 5099 ** If [sqlite3_step()] or [sqlite3_reset()] or [sqlite3_finalize()] 5100 ** are called from a different thread while any of these routines 5101 ** are pending, then the results are undefined. 5102 ** 5103 ** The first six interfaces (_blob, _double, _int, _int64, _text, and _text16) 5104 ** each return the value of a result column in a specific data format. If 5105 ** the result column is not initially in the requested format (for example, 5106 ** if the query returns an integer but the sqlite3_column_text() interface 5107 ** is used to extract the value) then an automatic type conversion is performed. 5108 ** 5109 ** ^The sqlite3_column_type() routine returns the 5110 ** [SQLITE_INTEGER | datatype code] for the initial data type 5111 ** of the result column. ^The returned value is one of [SQLITE_INTEGER], 5112 ** [SQLITE_FLOAT], [SQLITE_TEXT], [SQLITE_BLOB], or [SQLITE_NULL]. 5113 ** The return value of sqlite3_column_type() can be used to decide which 5114 ** of the first six interface should be used to extract the column value. 5115 ** The value returned by sqlite3_column_type() is only meaningful if no 5116 ** automatic type conversions have occurred for the value in question. 5117 ** After a type conversion, the result of calling sqlite3_column_type() 5118 ** is undefined, though harmless. Future 5119 ** versions of SQLite may change the behavior of sqlite3_column_type() 5120 ** following a type conversion. 5121 ** 5122 ** If the result is a BLOB or a TEXT string, then the sqlite3_column_bytes() 5123 ** or sqlite3_column_bytes16() interfaces can be used to determine the size 5124 ** of that BLOB or string. 5125 ** 5126 ** ^If the result is a BLOB or UTF-8 string then the sqlite3_column_bytes() 5127 ** routine returns the number of bytes in that BLOB or string. 5128 ** ^If the result is a UTF-16 string, then sqlite3_column_bytes() converts 5129 ** the string to UTF-8 and then returns the number of bytes. 5130 ** ^If the result is a numeric value then sqlite3_column_bytes() uses 5131 ** [sqlite3_snprintf()] to convert that value to a UTF-8 string and returns 5132 ** the number of bytes in that string. 5133 ** ^If the result is NULL, then sqlite3_column_bytes() returns zero. 5134 ** 5135 ** ^If the result is a BLOB or UTF-16 string then the sqlite3_column_bytes16() 5136 ** routine returns the number of bytes in that BLOB or string. 5137 ** ^If the result is a UTF-8 string, then sqlite3_column_bytes16() converts 5138 ** the string to UTF-16 and then returns the number of bytes. 5139 ** ^If the result is a numeric value then sqlite3_column_bytes16() uses 5140 ** [sqlite3_snprintf()] to convert that value to a UTF-16 string and returns 5141 ** the number of bytes in that string. 5142 ** ^If the result is NULL, then sqlite3_column_bytes16() returns zero. 5143 ** 5144 ** ^The values returned by [sqlite3_column_bytes()] and 5145 ** [sqlite3_column_bytes16()] do not include the zero terminators at the end 5146 ** of the string. ^For clarity: the values returned by 5147 ** [sqlite3_column_bytes()] and [sqlite3_column_bytes16()] are the number of 5148 ** bytes in the string, not the number of characters. 5149 ** 5150 ** ^Strings returned by sqlite3_column_text() and sqlite3_column_text16(), 5151 ** even empty strings, are always zero-terminated. ^The return 5152 ** value from sqlite3_column_blob() for a zero-length BLOB is a NULL pointer. 5153 ** 5154 ** ^Strings returned by sqlite3_column_text16() always have the endianness 5155 ** which is native to the platform, regardless of the text encoding set 5156 ** for the database. 5157 ** 5158 ** <b>Warning:</b> ^The object returned by [sqlite3_column_value()] is an 5159 ** [unprotected sqlite3_value] object. In a multithreaded environment, 5160 ** an unprotected sqlite3_value object may only be used safely with 5161 ** [sqlite3_bind_value()] and [sqlite3_result_value()]. 5162 ** If the [unprotected sqlite3_value] object returned by 5163 ** [sqlite3_column_value()] is used in any other way, including calls 5164 ** to routines like [sqlite3_value_int()], [sqlite3_value_text()], 5165 ** or [sqlite3_value_bytes()], the behavior is not threadsafe. 5166 ** Hence, the sqlite3_column_value() interface 5167 ** is normally only useful within the implementation of 5168 ** [application-defined SQL functions] or [virtual tables], not within 5169 ** top-level application code. 5170 ** 5171 ** These routines may attempt to convert the datatype of the result. 5172 ** ^For example, if the internal representation is FLOAT and a text result 5173 ** is requested, [sqlite3_snprintf()] is used internally to perform the 5174 ** conversion automatically. ^(The following table details the conversions 5175 ** that are applied: 5176 ** 5177 ** <blockquote> 5178 ** <table border="1"> 5179 ** <tr><th> Internal<br>Type <th> Requested<br>Type <th> Conversion 5180 ** 5181 ** <tr><td> NULL <td> INTEGER <td> Result is 0 5182 ** <tr><td> NULL <td> FLOAT <td> Result is 0.0 5183 ** <tr><td> NULL <td> TEXT <td> Result is a NULL pointer 5184 ** <tr><td> NULL <td> BLOB <td> Result is a NULL pointer 5185 ** <tr><td> INTEGER <td> FLOAT <td> Convert from integer to float 5186 ** <tr><td> INTEGER <td> TEXT <td> ASCII rendering of the integer 5187 ** <tr><td> INTEGER <td> BLOB <td> Same as INTEGER->TEXT 5188 ** <tr><td> FLOAT <td> INTEGER <td> [CAST] to INTEGER 5189 ** <tr><td> FLOAT <td> TEXT <td> ASCII rendering of the float 5190 ** <tr><td> FLOAT <td> BLOB <td> [CAST] to BLOB 5191 ** <tr><td> TEXT <td> INTEGER <td> [CAST] to INTEGER 5192 ** <tr><td> TEXT <td> FLOAT <td> [CAST] to REAL 5193 ** <tr><td> TEXT <td> BLOB <td> No change 5194 ** <tr><td> BLOB <td> INTEGER <td> [CAST] to INTEGER 5195 ** <tr><td> BLOB <td> FLOAT <td> [CAST] to REAL 5196 ** <tr><td> BLOB <td> TEXT <td> [CAST] to TEXT, ensure zero terminator 5197 ** </table> 5198 ** </blockquote>)^ 5199 ** 5200 ** Note that when type conversions occur, pointers returned by prior 5201 ** calls to sqlite3_column_blob(), sqlite3_column_text(), and/or 5202 ** sqlite3_column_text16() may be invalidated. 5203 ** Type conversions and pointer invalidations might occur 5204 ** in the following cases: 5205 ** 5206 ** <ul> 5207 ** <li> The initial content is a BLOB and sqlite3_column_text() or 5208 ** sqlite3_column_text16() is called. A zero-terminator might 5209 ** need to be added to the string.</li> 5210 ** <li> The initial content is UTF-8 text and sqlite3_column_bytes16() or 5211 ** sqlite3_column_text16() is called. The content must be converted 5212 ** to UTF-16.</li> 5213 ** <li> The initial content is UTF-16 text and sqlite3_column_bytes() or 5214 ** sqlite3_column_text() is called. The content must be converted 5215 ** to UTF-8.</li> 5216 ** </ul> 5217 ** 5218 ** ^Conversions between UTF-16be and UTF-16le are always done in place and do 5219 ** not invalidate a prior pointer, though of course the content of the buffer 5220 ** that the prior pointer references will have been modified. Other kinds 5221 ** of conversion are done in place when it is possible, but sometimes they 5222 ** are not possible and in those cases prior pointers are invalidated. 5223 ** 5224 ** The safest policy is to invoke these routines 5225 ** in one of the following ways: 5226 ** 5227 ** <ul> 5228 ** <li>sqlite3_column_text() followed by sqlite3_column_bytes()</li> 5229 ** <li>sqlite3_column_blob() followed by sqlite3_column_bytes()</li> 5230 ** <li>sqlite3_column_text16() followed by sqlite3_column_bytes16()</li> 5231 ** </ul> 5232 ** 5233 ** In other words, you should call sqlite3_column_text(), 5234 ** sqlite3_column_blob(), or sqlite3_column_text16() first to force the result 5235 ** into the desired format, then invoke sqlite3_column_bytes() or 5236 ** sqlite3_column_bytes16() to find the size of the result. Do not mix calls 5237 ** to sqlite3_column_text() or sqlite3_column_blob() with calls to 5238 ** sqlite3_column_bytes16(), and do not mix calls to sqlite3_column_text16() 5239 ** with calls to sqlite3_column_bytes(). 5240 ** 5241 ** ^The pointers returned are valid until a type conversion occurs as 5242 ** described above, or until [sqlite3_step()] or [sqlite3_reset()] or 5243 ** [sqlite3_finalize()] is called. ^The memory space used to hold strings 5244 ** and BLOBs is freed automatically. Do not pass the pointers returned 5245 ** from [sqlite3_column_blob()], [sqlite3_column_text()], etc. into 5246 ** [sqlite3_free()]. 5247 ** 5248 ** As long as the input parameters are correct, these routines will only 5249 ** fail if an out-of-memory error occurs during a format conversion. 5250 ** Only the following subset of interfaces are subject to out-of-memory 5251 ** errors: 5252 ** 5253 ** <ul> 5254 ** <li> sqlite3_column_blob() 5255 ** <li> sqlite3_column_text() 5256 ** <li> sqlite3_column_text16() 5257 ** <li> sqlite3_column_bytes() 5258 ** <li> sqlite3_column_bytes16() 5259 ** </ul> 5260 ** 5261 ** If an out-of-memory error occurs, then the return value from these 5262 ** routines is the same as if the column had contained an SQL NULL value. 5263 ** Valid SQL NULL returns can be distinguished from out-of-memory errors 5264 ** by invoking the [sqlite3_errcode()] immediately after the suspect 5265 ** return value is obtained and before any 5266 ** other SQLite interface is called on the same [database connection]. 5267 */ 5268 SQLITE_API const void *sqlite3_column_blob(sqlite3_stmt*, int iCol); 5269 SQLITE_API double sqlite3_column_double(sqlite3_stmt*, int iCol); 5270 SQLITE_API int sqlite3_column_int(sqlite3_stmt*, int iCol); 5271 SQLITE_API sqlite3_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol); 5272 SQLITE_API const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol); 5273 SQLITE_API const void *sqlite3_column_text16(sqlite3_stmt*, int iCol); 5274 SQLITE_API sqlite3_value *sqlite3_column_value(sqlite3_stmt*, int iCol); 5275 SQLITE_API int sqlite3_column_bytes(sqlite3_stmt*, int iCol); 5276 SQLITE_API int sqlite3_column_bytes16(sqlite3_stmt*, int iCol); 5277 SQLITE_API int sqlite3_column_type(sqlite3_stmt*, int iCol); 5278 5279 /* 5280 ** CAPI3REF: Destroy A Prepared Statement Object 5281 ** DESTRUCTOR: sqlite3_stmt 5282 ** 5283 ** ^The sqlite3_finalize() function is called to delete a [prepared statement]. 5284 ** ^If the most recent evaluation of the statement encountered no errors 5285 ** or if the statement is never been evaluated, then sqlite3_finalize() returns 5286 ** SQLITE_OK. ^If the most recent evaluation of statement S failed, then 5287 ** sqlite3_finalize(S) returns the appropriate [error code] or 5288 ** [extended error code]. 5289 ** 5290 ** ^The sqlite3_finalize(S) routine can be called at any point during 5291 ** the life cycle of [prepared statement] S: 5292 ** before statement S is ever evaluated, after 5293 ** one or more calls to [sqlite3_reset()], or after any call 5294 ** to [sqlite3_step()] regardless of whether or not the statement has 5295 ** completed execution. 5296 ** 5297 ** ^Invoking sqlite3_finalize() on a NULL pointer is a harmless no-op. 5298 ** 5299 ** The application must finalize every [prepared statement] in order to avoid 5300 ** resource leaks. It is a grievous error for the application to try to use 5301 ** a prepared statement after it has been finalized. Any use of a prepared 5302 ** statement after it has been finalized can result in undefined and 5303 ** undesirable behavior such as segfaults and heap corruption. 5304 */ 5305 SQLITE_API int sqlite3_finalize(sqlite3_stmt *pStmt); 5306 5307 /* 5308 ** CAPI3REF: Reset A Prepared Statement Object 5309 ** METHOD: sqlite3_stmt 5310 ** 5311 ** The sqlite3_reset() function is called to reset a [prepared statement] 5312 ** object back to its initial state, ready to be re-executed. 5313 ** ^Any SQL statement variables that had values bound to them using 5314 ** the [sqlite3_bind_blob | sqlite3_bind_*() API] retain their values. 5315 ** Use [sqlite3_clear_bindings()] to reset the bindings. 5316 ** 5317 ** ^The [sqlite3_reset(S)] interface resets the [prepared statement] S 5318 ** back to the beginning of its program. 5319 ** 5320 ** ^The return code from [sqlite3_reset(S)] indicates whether or not 5321 ** the previous evaluation of prepared statement S completed successfully. 5322 ** ^If [sqlite3_step(S)] has never before been called on S or if 5323 ** [sqlite3_step(S)] has not been called since the previous call 5324 ** to [sqlite3_reset(S)], then [sqlite3_reset(S)] will return 5325 ** [SQLITE_OK]. 5326 ** 5327 ** ^If the most recent call to [sqlite3_step(S)] for the 5328 ** [prepared statement] S indicated an error, then 5329 ** [sqlite3_reset(S)] returns an appropriate [error code]. 5330 ** ^The [sqlite3_reset(S)] interface might also return an [error code] 5331 ** if there were no prior errors but the process of resetting 5332 ** the prepared statement caused a new error. ^For example, if an 5333 ** [INSERT] statement with a [RETURNING] clause is only stepped one time, 5334 ** that one call to [sqlite3_step(S)] might return SQLITE_ROW but 5335 ** the overall statement might still fail and the [sqlite3_reset(S)] call 5336 ** might return SQLITE_BUSY if locking constraints prevent the 5337 ** database change from committing. Therefore, it is important that 5338 ** applications check the return code from [sqlite3_reset(S)] even if 5339 ** no prior call to [sqlite3_step(S)] indicated a problem. 5340 ** 5341 ** ^The [sqlite3_reset(S)] interface does not change the values 5342 ** of any [sqlite3_bind_blob|bindings] on the [prepared statement] S. 5343 */ 5344 SQLITE_API int sqlite3_reset(sqlite3_stmt *pStmt); 5345 5346 5347 /* 5348 ** CAPI3REF: Create Or Redefine SQL Functions 5349 ** KEYWORDS: {function creation routines} 5350 ** METHOD: sqlite3 5351 ** 5352 ** ^These functions (collectively known as "function creation routines") 5353 ** are used to add SQL functions or aggregates or to redefine the behavior 5354 ** of existing SQL functions or aggregates. The only differences between 5355 ** the three "sqlite3_create_function*" routines are the text encoding 5356 ** expected for the second parameter (the name of the function being 5357 ** created) and the presence or absence of a destructor callback for 5358 ** the application data pointer. Function sqlite3_create_window_function() 5359 ** is similar, but allows the user to supply the extra callback functions 5360 ** needed by [aggregate window functions]. 5361 ** 5362 ** ^The first parameter is the [database connection] to which the SQL 5363 ** function is to be added. ^If an application uses more than one database 5364 ** connection then application-defined SQL functions must be added 5365 ** to each database connection separately. 5366 ** 5367 ** ^The second parameter is the name of the SQL function to be created or 5368 ** redefined. ^The length of the name is limited to 255 bytes in a UTF-8 5369 ** representation, exclusive of the zero-terminator. ^Note that the name 5370 ** length limit is in UTF-8 bytes, not characters nor UTF-16 bytes. 5371 ** ^Any attempt to create a function with a longer name 5372 ** will result in [SQLITE_MISUSE] being returned. 5373 ** 5374 ** ^The third parameter (nArg) 5375 ** is the number of arguments that the SQL function or 5376 ** aggregate takes. ^If this parameter is -1, then the SQL function or 5377 ** aggregate may take any number of arguments between 0 and the limit 5378 ** set by [sqlite3_limit]([SQLITE_LIMIT_FUNCTION_ARG]). If the third 5379 ** parameter is less than -1 or greater than 127 then the behavior is 5380 ** undefined. 5381 ** 5382 ** ^The fourth parameter, eTextRep, specifies what 5383 ** [SQLITE_UTF8 | text encoding] this SQL function prefers for 5384 ** its parameters. The application should set this parameter to 5385 ** [SQLITE_UTF16LE] if the function implementation invokes 5386 ** [sqlite3_value_text16le()] on an input, or [SQLITE_UTF16BE] if the 5387 ** implementation invokes [sqlite3_value_text16be()] on an input, or 5388 ** [SQLITE_UTF16] if [sqlite3_value_text16()] is used, or [SQLITE_UTF8] 5389 ** otherwise. ^The same SQL function may be registered multiple times using 5390 ** different preferred text encodings, with different implementations for 5391 ** each encoding. 5392 ** ^When multiple implementations of the same function are available, SQLite 5393 ** will pick the one that involves the least amount of data conversion. 5394 ** 5395 ** ^The fourth parameter may optionally be ORed with [SQLITE_DETERMINISTIC] 5396 ** to signal that the function will always return the same result given 5397 ** the same inputs within a single SQL statement. Most SQL functions are 5398 ** deterministic. The built-in [random()] SQL function is an example of a 5399 ** function that is not deterministic. The SQLite query planner is able to 5400 ** perform additional optimizations on deterministic functions, so use 5401 ** of the [SQLITE_DETERMINISTIC] flag is recommended where possible. 5402 ** 5403 ** ^The fourth parameter may also optionally include the [SQLITE_DIRECTONLY] 5404 ** flag, which if present prevents the function from being invoked from 5405 ** within VIEWs, TRIGGERs, CHECK constraints, generated column expressions, 5406 ** index expressions, or the WHERE clause of partial indexes. 5407 ** 5408 ** For best security, the [SQLITE_DIRECTONLY] flag is recommended for 5409 ** all application-defined SQL functions that do not need to be 5410 ** used inside of triggers, view, CHECK constraints, or other elements of 5411 ** the database schema. This flags is especially recommended for SQL 5412 ** functions that have side effects or reveal internal application state. 5413 ** Without this flag, an attacker might be able to modify the schema of 5414 ** a database file to include invocations of the function with parameters 5415 ** chosen by the attacker, which the application will then execute when 5416 ** the database file is opened and read. 5417 ** 5418 ** ^(The fifth parameter is an arbitrary pointer. The implementation of the 5419 ** function can gain access to this pointer using [sqlite3_user_data()].)^ 5420 ** 5421 ** ^The sixth, seventh and eighth parameters passed to the three 5422 ** "sqlite3_create_function*" functions, xFunc, xStep and xFinal, are 5423 ** pointers to C-language functions that implement the SQL function or 5424 ** aggregate. ^A scalar SQL function requires an implementation of the xFunc 5425 ** callback only; NULL pointers must be passed as the xStep and xFinal 5426 ** parameters. ^An aggregate SQL function requires an implementation of xStep 5427 ** and xFinal and NULL pointer must be passed for xFunc. ^To delete an existing 5428 ** SQL function or aggregate, pass NULL pointers for all three function 5429 ** callbacks. 5430 ** 5431 ** ^The sixth, seventh, eighth and ninth parameters (xStep, xFinal, xValue 5432 ** and xInverse) passed to sqlite3_create_window_function are pointers to 5433 ** C-language callbacks that implement the new function. xStep and xFinal 5434 ** must both be non-NULL. xValue and xInverse may either both be NULL, in 5435 ** which case a regular aggregate function is created, or must both be 5436 ** non-NULL, in which case the new function may be used as either an aggregate 5437 ** or aggregate window function. More details regarding the implementation 5438 ** of aggregate window functions are 5439 ** [user-defined window functions|available here]. 5440 ** 5441 ** ^(If the final parameter to sqlite3_create_function_v2() or 5442 ** sqlite3_create_window_function() is not NULL, then it is destructor for 5443 ** the application data pointer. The destructor is invoked when the function 5444 ** is deleted, either by being overloaded or when the database connection 5445 ** closes.)^ ^The destructor is also invoked if the call to 5446 ** sqlite3_create_function_v2() fails. ^When the destructor callback is 5447 ** invoked, it is passed a single argument which is a copy of the application 5448 ** data pointer which was the fifth parameter to sqlite3_create_function_v2(). 5449 ** 5450 ** ^It is permitted to register multiple implementations of the same 5451 ** functions with the same name but with either differing numbers of 5452 ** arguments or differing preferred text encodings. ^SQLite will use 5453 ** the implementation that most closely matches the way in which the 5454 ** SQL function is used. ^A function implementation with a non-negative 5455 ** nArg parameter is a better match than a function implementation with 5456 ** a negative nArg. ^A function where the preferred text encoding 5457 ** matches the database encoding is a better 5458 ** match than a function where the encoding is different. 5459 ** ^A function where the encoding difference is between UTF16le and UTF16be 5460 ** is a closer match than a function where the encoding difference is 5461 ** between UTF8 and UTF16. 5462 ** 5463 ** ^Built-in functions may be overloaded by new application-defined functions. 5464 ** 5465 ** ^An application-defined function is permitted to call other 5466 ** SQLite interfaces. However, such calls must not 5467 ** close the database connection nor finalize or reset the prepared 5468 ** statement in which the function is running. 5469 */ 5470 SQLITE_API int sqlite3_create_function( 5471 sqlite3 *db, 5472 const char *zFunctionName, 5473 int nArg, 5474 int eTextRep, 5475 void *pApp, 5476 void (*xFunc)(sqlite3_context*,int,sqlite3_value**), 5477 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 5478 void (*xFinal)(sqlite3_context*) 5479 ); 5480 SQLITE_API int sqlite3_create_function16( 5481 sqlite3 *db, 5482 const void *zFunctionName, 5483 int nArg, 5484 int eTextRep, 5485 void *pApp, 5486 void (*xFunc)(sqlite3_context*,int,sqlite3_value**), 5487 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 5488 void (*xFinal)(sqlite3_context*) 5489 ); 5490 SQLITE_API int sqlite3_create_function_v2( 5491 sqlite3 *db, 5492 const char *zFunctionName, 5493 int nArg, 5494 int eTextRep, 5495 void *pApp, 5496 void (*xFunc)(sqlite3_context*,int,sqlite3_value**), 5497 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 5498 void (*xFinal)(sqlite3_context*), 5499 void(*xDestroy)(void*) 5500 ); 5501 SQLITE_API int sqlite3_create_window_function( 5502 sqlite3 *db, 5503 const char *zFunctionName, 5504 int nArg, 5505 int eTextRep, 5506 void *pApp, 5507 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 5508 void (*xFinal)(sqlite3_context*), 5509 void (*xValue)(sqlite3_context*), 5510 void (*xInverse)(sqlite3_context*,int,sqlite3_value**), 5511 void(*xDestroy)(void*) 5512 ); 5513 5514 /* 5515 ** CAPI3REF: Text Encodings 5516 ** 5517 ** These constant define integer codes that represent the various 5518 ** text encodings supported by SQLite. 5519 */ 5520 #define SQLITE_UTF8 1 /* IMP: R-37514-35566 */ 5521 #define SQLITE_UTF16LE 2 /* IMP: R-03371-37637 */ 5522 #define SQLITE_UTF16BE 3 /* IMP: R-51971-34154 */ 5523 #define SQLITE_UTF16 4 /* Use native byte order */ 5524 #define SQLITE_ANY 5 /* Deprecated */ 5525 #define SQLITE_UTF16_ALIGNED 8 /* sqlite3_create_collation only */ 5526 5527 /* 5528 ** CAPI3REF: Function Flags 5529 ** 5530 ** These constants may be ORed together with the 5531 ** [SQLITE_UTF8 | preferred text encoding] as the fourth argument 5532 ** to [sqlite3_create_function()], [sqlite3_create_function16()], or 5533 ** [sqlite3_create_function_v2()]. 5534 ** 5535 ** <dl> 5536 ** [[SQLITE_DETERMINISTIC]] <dt>SQLITE_DETERMINISTIC</dt><dd> 5537 ** The SQLITE_DETERMINISTIC flag means that the new function always gives 5538 ** the same output when the input parameters are the same. 5539 ** The [abs|abs() function] is deterministic, for example, but 5540 ** [randomblob|randomblob()] is not. Functions must 5541 ** be deterministic in order to be used in certain contexts such as 5542 ** with the WHERE clause of [partial indexes] or in [generated columns]. 5543 ** SQLite might also optimize deterministic functions by factoring them 5544 ** out of inner loops. 5545 ** </dd> 5546 ** 5547 ** [[SQLITE_DIRECTONLY]] <dt>SQLITE_DIRECTONLY</dt><dd> 5548 ** The SQLITE_DIRECTONLY flag means that the function may only be invoked 5549 ** from top-level SQL, and cannot be used in VIEWs or TRIGGERs nor in 5550 ** schema structures such as [CHECK constraints], [DEFAULT clauses], 5551 ** [expression indexes], [partial indexes], or [generated columns]. 5552 ** <p> 5553 ** The SQLITE_DIRECTONLY flag is recommended for any 5554 ** [application-defined SQL function] 5555 ** that has side-effects or that could potentially leak sensitive information. 5556 ** This will prevent attacks in which an application is tricked 5557 ** into using a database file that has had its schema surreptitiously 5558 ** modified to invoke the application-defined function in ways that are 5559 ** harmful. 5560 ** <p> 5561 ** Some people say it is good practice to set SQLITE_DIRECTONLY on all 5562 ** [application-defined SQL functions], regardless of whether or not they 5563 ** are security sensitive, as doing so prevents those functions from being used 5564 ** inside of the database schema, and thus ensures that the database 5565 ** can be inspected and modified using generic tools (such as the [CLI]) 5566 ** that do not have access to the application-defined functions. 5567 ** </dd> 5568 ** 5569 ** [[SQLITE_INNOCUOUS]] <dt>SQLITE_INNOCUOUS</dt><dd> 5570 ** The SQLITE_INNOCUOUS flag means that the function is unlikely 5571 ** to cause problems even if misused. An innocuous function should have 5572 ** no side effects and should not depend on any values other than its 5573 ** input parameters. The [abs|abs() function] is an example of an 5574 ** innocuous function. 5575 ** The [load_extension() SQL function] is not innocuous because of its 5576 ** side effects. 5577 ** <p> SQLITE_INNOCUOUS is similar to SQLITE_DETERMINISTIC, but is not 5578 ** exactly the same. The [random|random() function] is an example of a 5579 ** function that is innocuous but not deterministic. 5580 ** <p>Some heightened security settings 5581 ** ([SQLITE_DBCONFIG_TRUSTED_SCHEMA] and [PRAGMA trusted_schema=OFF]) 5582 ** disable the use of SQL functions inside views and triggers and in 5583 ** schema structures such as [CHECK constraints], [DEFAULT clauses], 5584 ** [expression indexes], [partial indexes], and [generated columns] unless 5585 ** the function is tagged with SQLITE_INNOCUOUS. Most built-in functions 5586 ** are innocuous. Developers are advised to avoid using the 5587 ** SQLITE_INNOCUOUS flag for application-defined functions unless the 5588 ** function has been carefully audited and found to be free of potentially 5589 ** security-adverse side-effects and information-leaks. 5590 ** </dd> 5591 ** 5592 ** [[SQLITE_SUBTYPE]] <dt>SQLITE_SUBTYPE</dt><dd> 5593 ** The SQLITE_SUBTYPE flag indicates to SQLite that a function might call 5594 ** [sqlite3_value_subtype()] to inspect the sub-types of its arguments. 5595 ** This flag instructs SQLite to omit some corner-case optimizations that 5596 ** might disrupt the operation of the [sqlite3_value_subtype()] function, 5597 ** causing it to return zero rather than the correct subtype(). 5598 ** SQL functions that invokes [sqlite3_value_subtype()] should have this 5599 ** property. If the SQLITE_SUBTYPE property is omitted, then the return 5600 ** value from [sqlite3_value_subtype()] might sometimes be zero even though 5601 ** a non-zero subtype was specified by the function argument expression. 5602 ** 5603 ** [[SQLITE_RESULT_SUBTYPE]] <dt>SQLITE_RESULT_SUBTYPE</dt><dd> 5604 ** The SQLITE_RESULT_SUBTYPE flag indicates to SQLite that a function might call 5605 ** [sqlite3_result_subtype()] to cause a sub-type to be associated with its 5606 ** result. 5607 ** Every function that invokes [sqlite3_result_subtype()] should have this 5608 ** property. If it does not, then the call to [sqlite3_result_subtype()] 5609 ** might become a no-op if the function is used as term in an 5610 ** [expression index]. On the other hand, SQL functions that never invoke 5611 ** [sqlite3_result_subtype()] should avoid setting this property, as the 5612 ** purpose of this property is to disable certain optimizations that are 5613 ** incompatible with subtypes. 5614 ** </dd> 5615 ** </dl> 5616 */ 5617 #define SQLITE_DETERMINISTIC 0x000000800 5618 #define SQLITE_DIRECTONLY 0x000080000 5619 #define SQLITE_SUBTYPE 0x000100000 5620 #define SQLITE_INNOCUOUS 0x000200000 5621 #define SQLITE_RESULT_SUBTYPE 0x001000000 5622 5623 /* 5624 ** CAPI3REF: Deprecated Functions 5625 ** DEPRECATED 5626 ** 5627 ** These functions are [deprecated]. In order to maintain 5628 ** backwards compatibility with older code, these functions continue 5629 ** to be supported. However, new applications should avoid 5630 ** the use of these functions. To encourage programmers to avoid 5631 ** these functions, we will not explain what they do. 5632 */ 5633 #ifndef SQLITE_OMIT_DEPRECATED 5634 SQLITE_API SQLITE_DEPRECATED int sqlite3_aggregate_count(sqlite3_context*); 5635 SQLITE_API SQLITE_DEPRECATED int sqlite3_expired(sqlite3_stmt*); 5636 SQLITE_API SQLITE_DEPRECATED int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*); 5637 SQLITE_API SQLITE_DEPRECATED int sqlite3_global_recover(void); 5638 SQLITE_API SQLITE_DEPRECATED void sqlite3_thread_cleanup(void); 5639 SQLITE_API SQLITE_DEPRECATED int sqlite3_memory_alarm(void(*)(void*,sqlite3_int64,int), 5640 void*,sqlite3_int64); 5641 #endif 5642 5643 /* 5644 ** CAPI3REF: Obtaining SQL Values 5645 ** METHOD: sqlite3_value 5646 ** 5647 ** <b>Summary:</b> 5648 ** <blockquote><table border=0 cellpadding=0 cellspacing=0> 5649 ** <tr><td><b>sqlite3_value_blob</b><td>→<td>BLOB value 5650 ** <tr><td><b>sqlite3_value_double</b><td>→<td>REAL value 5651 ** <tr><td><b>sqlite3_value_int</b><td>→<td>32-bit INTEGER value 5652 ** <tr><td><b>sqlite3_value_int64</b><td>→<td>64-bit INTEGER value 5653 ** <tr><td><b>sqlite3_value_pointer</b><td>→<td>Pointer value 5654 ** <tr><td><b>sqlite3_value_text</b><td>→<td>UTF-8 TEXT value 5655 ** <tr><td><b>sqlite3_value_text16</b><td>→<td>UTF-16 TEXT value in 5656 ** the native byteorder 5657 ** <tr><td><b>sqlite3_value_text16be</b><td>→<td>UTF-16be TEXT value 5658 ** <tr><td><b>sqlite3_value_text16le</b><td>→<td>UTF-16le TEXT value 5659 ** <tr><td> <td> <td> 5660 ** <tr><td><b>sqlite3_value_bytes</b><td>→<td>Size of a BLOB 5661 ** or a UTF-8 TEXT in bytes 5662 ** <tr><td><b>sqlite3_value_bytes16 </b> 5663 ** <td>→ <td>Size of UTF-16 5664 ** TEXT in bytes 5665 ** <tr><td><b>sqlite3_value_type</b><td>→<td>Default 5666 ** datatype of the value 5667 ** <tr><td><b>sqlite3_value_numeric_type </b> 5668 ** <td>→ <td>Best numeric datatype of the value 5669 ** <tr><td><b>sqlite3_value_nochange </b> 5670 ** <td>→ <td>True if the column is unchanged in an UPDATE 5671 ** against a virtual table. 5672 ** <tr><td><b>sqlite3_value_frombind </b> 5673 ** <td>→ <td>True if value originated from a [bound parameter] 5674 ** </table></blockquote> 5675 ** 5676 ** <b>Details:</b> 5677 ** 5678 ** These routines extract type, size, and content information from 5679 ** [protected sqlite3_value] objects. Protected sqlite3_value objects 5680 ** are used to pass parameter information into the functions that 5681 ** implement [application-defined SQL functions] and [virtual tables]. 5682 ** 5683 ** These routines work only with [protected sqlite3_value] objects. 5684 ** Any attempt to use these routines on an [unprotected sqlite3_value] 5685 ** is not threadsafe. 5686 ** 5687 ** ^These routines work just like the corresponding [column access functions] 5688 ** except that these routines take a single [protected sqlite3_value] object 5689 ** pointer instead of a [sqlite3_stmt*] pointer and an integer column number. 5690 ** 5691 ** ^The sqlite3_value_text16() interface extracts a UTF-16 string 5692 ** in the native byte-order of the host machine. ^The 5693 ** sqlite3_value_text16be() and sqlite3_value_text16le() interfaces 5694 ** extract UTF-16 strings as big-endian and little-endian respectively. 5695 ** 5696 ** ^If [sqlite3_value] object V was initialized 5697 ** using [sqlite3_bind_pointer(S,I,P,X,D)] or [sqlite3_result_pointer(C,P,X,D)] 5698 ** and if X and Y are strings that compare equal according to strcmp(X,Y), 5699 ** then sqlite3_value_pointer(V,Y) will return the pointer P. ^Otherwise, 5700 ** sqlite3_value_pointer(V,Y) returns a NULL. The sqlite3_bind_pointer() 5701 ** routine is part of the [pointer passing interface] added for SQLite 3.20.0. 5702 ** 5703 ** ^(The sqlite3_value_type(V) interface returns the 5704 ** [SQLITE_INTEGER | datatype code] for the initial datatype of the 5705 ** [sqlite3_value] object V. The returned value is one of [SQLITE_INTEGER], 5706 ** [SQLITE_FLOAT], [SQLITE_TEXT], [SQLITE_BLOB], or [SQLITE_NULL].)^ 5707 ** Other interfaces might change the datatype for an sqlite3_value object. 5708 ** For example, if the datatype is initially SQLITE_INTEGER and 5709 ** sqlite3_value_text(V) is called to extract a text value for that 5710 ** integer, then subsequent calls to sqlite3_value_type(V) might return 5711 ** SQLITE_TEXT. Whether or not a persistent internal datatype conversion 5712 ** occurs is undefined and may change from one release of SQLite to the next. 5713 ** 5714 ** ^(The sqlite3_value_numeric_type() interface attempts to apply 5715 ** numeric affinity to the value. This means that an attempt is 5716 ** made to convert the value to an integer or floating point. If 5717 ** such a conversion is possible without loss of information (in other 5718 ** words, if the value is a string that looks like a number) 5719 ** then the conversion is performed. Otherwise no conversion occurs. 5720 ** The [SQLITE_INTEGER | datatype] after conversion is returned.)^ 5721 ** 5722 ** ^Within the [xUpdate] method of a [virtual table], the 5723 ** sqlite3_value_nochange(X) interface returns true if and only if 5724 ** the column corresponding to X is unchanged by the UPDATE operation 5725 ** that the xUpdate method call was invoked to implement and if 5726 ** and the prior [xColumn] method call that was invoked to extracted 5727 ** the value for that column returned without setting a result (probably 5728 ** because it queried [sqlite3_vtab_nochange()] and found that the column 5729 ** was unchanging). ^Within an [xUpdate] method, any value for which 5730 ** sqlite3_value_nochange(X) is true will in all other respects appear 5731 ** to be a NULL value. If sqlite3_value_nochange(X) is invoked anywhere other 5732 ** than within an [xUpdate] method call for an UPDATE statement, then 5733 ** the return value is arbitrary and meaningless. 5734 ** 5735 ** ^The sqlite3_value_frombind(X) interface returns non-zero if the 5736 ** value X originated from one of the [sqlite3_bind_int|sqlite3_bind()] 5737 ** interfaces. ^If X comes from an SQL literal value, or a table column, 5738 ** or an expression, then sqlite3_value_frombind(X) returns zero. 5739 ** 5740 ** Please pay particular attention to the fact that the pointer returned 5741 ** from [sqlite3_value_blob()], [sqlite3_value_text()], or 5742 ** [sqlite3_value_text16()] can be invalidated by a subsequent call to 5743 ** [sqlite3_value_bytes()], [sqlite3_value_bytes16()], [sqlite3_value_text()], 5744 ** or [sqlite3_value_text16()]. 5745 ** 5746 ** These routines must be called from the same thread as 5747 ** the SQL function that supplied the [sqlite3_value*] parameters. 5748 ** 5749 ** As long as the input parameter is correct, these routines can only 5750 ** fail if an out-of-memory error occurs during a format conversion. 5751 ** Only the following subset of interfaces are subject to out-of-memory 5752 ** errors: 5753 ** 5754 ** <ul> 5755 ** <li> sqlite3_value_blob() 5756 ** <li> sqlite3_value_text() 5757 ** <li> sqlite3_value_text16() 5758 ** <li> sqlite3_value_text16le() 5759 ** <li> sqlite3_value_text16be() 5760 ** <li> sqlite3_value_bytes() 5761 ** <li> sqlite3_value_bytes16() 5762 ** </ul> 5763 ** 5764 ** If an out-of-memory error occurs, then the return value from these 5765 ** routines is the same as if the column had contained an SQL NULL value. 5766 ** Valid SQL NULL returns can be distinguished from out-of-memory errors 5767 ** by invoking the [sqlite3_errcode()] immediately after the suspect 5768 ** return value is obtained and before any 5769 ** other SQLite interface is called on the same [database connection]. 5770 */ 5771 SQLITE_API const void *sqlite3_value_blob(sqlite3_value*); 5772 SQLITE_API double sqlite3_value_double(sqlite3_value*); 5773 SQLITE_API int sqlite3_value_int(sqlite3_value*); 5774 SQLITE_API sqlite3_int64 sqlite3_value_int64(sqlite3_value*); 5775 SQLITE_API void *sqlite3_value_pointer(sqlite3_value*, const char*); 5776 SQLITE_API const unsigned char *sqlite3_value_text(sqlite3_value*); 5777 SQLITE_API const void *sqlite3_value_text16(sqlite3_value*); 5778 SQLITE_API const void *sqlite3_value_text16le(sqlite3_value*); 5779 SQLITE_API const void *sqlite3_value_text16be(sqlite3_value*); 5780 SQLITE_API int sqlite3_value_bytes(sqlite3_value*); 5781 SQLITE_API int sqlite3_value_bytes16(sqlite3_value*); 5782 SQLITE_API int sqlite3_value_type(sqlite3_value*); 5783 SQLITE_API int sqlite3_value_numeric_type(sqlite3_value*); 5784 SQLITE_API int sqlite3_value_nochange(sqlite3_value*); 5785 SQLITE_API int sqlite3_value_frombind(sqlite3_value*); 5786 5787 /* 5788 ** CAPI3REF: Report the internal text encoding state of an sqlite3_value object 5789 ** METHOD: sqlite3_value 5790 ** 5791 ** ^(The sqlite3_value_encoding(X) interface returns one of [SQLITE_UTF8], 5792 ** [SQLITE_UTF16BE], or [SQLITE_UTF16LE] according to the current text encoding 5793 ** of the value X, assuming that X has type TEXT.)^ If sqlite3_value_type(X) 5794 ** returns something other than SQLITE_TEXT, then the return value from 5795 ** sqlite3_value_encoding(X) is meaningless. ^Calls to 5796 ** [sqlite3_value_text(X)], [sqlite3_value_text16(X)], [sqlite3_value_text16be(X)], 5797 ** [sqlite3_value_text16le(X)], [sqlite3_value_bytes(X)], or 5798 ** [sqlite3_value_bytes16(X)] might change the encoding of the value X and 5799 ** thus change the return from subsequent calls to sqlite3_value_encoding(X). 5800 ** 5801 ** This routine is intended for used by applications that test and validate 5802 ** the SQLite implementation. This routine is inquiring about the opaque 5803 ** internal state of an [sqlite3_value] object. Ordinary applications should 5804 ** not need to know what the internal state of an sqlite3_value object is and 5805 ** hence should not need to use this interface. 5806 */ 5807 SQLITE_API int sqlite3_value_encoding(sqlite3_value*); 5808 5809 /* 5810 ** CAPI3REF: Finding The Subtype Of SQL Values 5811 ** METHOD: sqlite3_value 5812 ** 5813 ** The sqlite3_value_subtype(V) function returns the subtype for 5814 ** an [application-defined SQL function] argument V. The subtype 5815 ** information can be used to pass a limited amount of context from 5816 ** one SQL function to another. Use the [sqlite3_result_subtype()] 5817 ** routine to set the subtype for the return value of an SQL function. 5818 ** 5819 ** Every [application-defined SQL function] that invoke this interface 5820 ** should include the [SQLITE_SUBTYPE] property in the text 5821 ** encoding argument when the function is [sqlite3_create_function|registered]. 5822 ** If the [SQLITE_SUBTYPE] property is omitted, then sqlite3_value_subtype() 5823 ** might return zero instead of the upstream subtype in some corner cases. 5824 */ 5825 SQLITE_API unsigned int sqlite3_value_subtype(sqlite3_value*); 5826 5827 /* 5828 ** CAPI3REF: Copy And Free SQL Values 5829 ** METHOD: sqlite3_value 5830 ** 5831 ** ^The sqlite3_value_dup(V) interface makes a copy of the [sqlite3_value] 5832 ** object D and returns a pointer to that copy. ^The [sqlite3_value] returned 5833 ** is a [protected sqlite3_value] object even if the input is not. 5834 ** ^The sqlite3_value_dup(V) interface returns NULL if V is NULL or if a 5835 ** memory allocation fails. ^If V is a [pointer value], then the result 5836 ** of sqlite3_value_dup(V) is a NULL value. 5837 ** 5838 ** ^The sqlite3_value_free(V) interface frees an [sqlite3_value] object 5839 ** previously obtained from [sqlite3_value_dup()]. ^If V is a NULL pointer 5840 ** then sqlite3_value_free(V) is a harmless no-op. 5841 */ 5842 SQLITE_API sqlite3_value *sqlite3_value_dup(const sqlite3_value*); 5843 SQLITE_API void sqlite3_value_free(sqlite3_value*); 5844 5845 /* 5846 ** CAPI3REF: Obtain Aggregate Function Context 5847 ** METHOD: sqlite3_context 5848 ** 5849 ** Implementations of aggregate SQL functions use this 5850 ** routine to allocate memory for storing their state. 5851 ** 5852 ** ^The first time the sqlite3_aggregate_context(C,N) routine is called 5853 ** for a particular aggregate function, SQLite allocates 5854 ** N bytes of memory, zeroes out that memory, and returns a pointer 5855 ** to the new memory. ^On second and subsequent calls to 5856 ** sqlite3_aggregate_context() for the same aggregate function instance, 5857 ** the same buffer is returned. Sqlite3_aggregate_context() is normally 5858 ** called once for each invocation of the xStep callback and then one 5859 ** last time when the xFinal callback is invoked. ^(When no rows match 5860 ** an aggregate query, the xStep() callback of the aggregate function 5861 ** implementation is never called and xFinal() is called exactly once. 5862 ** In those cases, sqlite3_aggregate_context() might be called for the 5863 ** first time from within xFinal().)^ 5864 ** 5865 ** ^The sqlite3_aggregate_context(C,N) routine returns a NULL pointer 5866 ** when first called if N is less than or equal to zero or if a memory 5867 ** allocation error occurs. 5868 ** 5869 ** ^(The amount of space allocated by sqlite3_aggregate_context(C,N) is 5870 ** determined by the N parameter on first successful call. Changing the 5871 ** value of N in any subsequent call to sqlite3_aggregate_context() within 5872 ** the same aggregate function instance will not resize the memory 5873 ** allocation.)^ Within the xFinal callback, it is customary to set 5874 ** N=0 in calls to sqlite3_aggregate_context(C,N) so that no 5875 ** pointless memory allocations occur. 5876 ** 5877 ** ^SQLite automatically frees the memory allocated by 5878 ** sqlite3_aggregate_context() when the aggregate query concludes. 5879 ** 5880 ** The first parameter must be a copy of the 5881 ** [sqlite3_context | SQL function context] that is the first parameter 5882 ** to the xStep or xFinal callback routine that implements the aggregate 5883 ** function. 5884 ** 5885 ** This routine must be called from the same thread in which 5886 ** the aggregate SQL function is running. 5887 */ 5888 SQLITE_API void *sqlite3_aggregate_context(sqlite3_context*, int nBytes); 5889 5890 /* 5891 ** CAPI3REF: User Data For Functions 5892 ** METHOD: sqlite3_context 5893 ** 5894 ** ^The sqlite3_user_data() interface returns a copy of 5895 ** the pointer that was the pUserData parameter (the 5th parameter) 5896 ** of the [sqlite3_create_function()] 5897 ** and [sqlite3_create_function16()] routines that originally 5898 ** registered the application defined function. 5899 ** 5900 ** This routine must be called from the same thread in which 5901 ** the application-defined function is running. 5902 */ 5903 SQLITE_API void *sqlite3_user_data(sqlite3_context*); 5904 5905 /* 5906 ** CAPI3REF: Database Connection For Functions 5907 ** METHOD: sqlite3_context 5908 ** 5909 ** ^The sqlite3_context_db_handle() interface returns a copy of 5910 ** the pointer to the [database connection] (the 1st parameter) 5911 ** of the [sqlite3_create_function()] 5912 ** and [sqlite3_create_function16()] routines that originally 5913 ** registered the application defined function. 5914 */ 5915 SQLITE_API sqlite3 *sqlite3_context_db_handle(sqlite3_context*); 5916 5917 /* 5918 ** CAPI3REF: Function Auxiliary Data 5919 ** METHOD: sqlite3_context 5920 ** 5921 ** These functions may be used by (non-aggregate) SQL functions to 5922 ** associate auxiliary data with argument values. If the same argument 5923 ** value is passed to multiple invocations of the same SQL function during 5924 ** query execution, under some circumstances the associated auxiliary data 5925 ** might be preserved. An example of where this might be useful is in a 5926 ** regular-expression matching function. The compiled version of the regular 5927 ** expression can be stored as auxiliary data associated with the pattern string. 5928 ** Then as long as the pattern string remains the same, 5929 ** the compiled regular expression can be reused on multiple 5930 ** invocations of the same function. 5931 ** 5932 ** ^The sqlite3_get_auxdata(C,N) interface returns a pointer to the auxiliary data 5933 ** associated by the sqlite3_set_auxdata(C,N,P,X) function with the Nth argument 5934 ** value to the application-defined function. ^N is zero for the left-most 5935 ** function argument. ^If there is no auxiliary data 5936 ** associated with the function argument, the sqlite3_get_auxdata(C,N) interface 5937 ** returns a NULL pointer. 5938 ** 5939 ** ^The sqlite3_set_auxdata(C,N,P,X) interface saves P as auxiliary data for the 5940 ** N-th argument of the application-defined function. ^Subsequent 5941 ** calls to sqlite3_get_auxdata(C,N) return P from the most recent 5942 ** sqlite3_set_auxdata(C,N,P,X) call if the auxiliary data is still valid or 5943 ** NULL if the auxiliary data has been discarded. 5944 ** ^After each call to sqlite3_set_auxdata(C,N,P,X) where X is not NULL, 5945 ** SQLite will invoke the destructor function X with parameter P exactly 5946 ** once, when the auxiliary data is discarded. 5947 ** SQLite is free to discard the auxiliary data at any time, including: <ul> 5948 ** <li> ^(when the corresponding function parameter changes)^, or 5949 ** <li> ^(when [sqlite3_reset()] or [sqlite3_finalize()] is called for the 5950 ** SQL statement)^, or 5951 ** <li> ^(when sqlite3_set_auxdata() is invoked again on the same 5952 ** parameter)^, or 5953 ** <li> ^(during the original sqlite3_set_auxdata() call when a memory 5954 ** allocation error occurs.)^ 5955 ** <li> ^(during the original sqlite3_set_auxdata() call if the function 5956 ** is evaluated during query planning instead of during query execution, 5957 ** as sometimes happens with [SQLITE_ENABLE_STAT4].)^ </ul> 5958 ** 5959 ** Note the last two bullets in particular. The destructor X in 5960 ** sqlite3_set_auxdata(C,N,P,X) might be called immediately, before the 5961 ** sqlite3_set_auxdata() interface even returns. Hence sqlite3_set_auxdata() 5962 ** should be called near the end of the function implementation and the 5963 ** function implementation should not make any use of P after 5964 ** sqlite3_set_auxdata() has been called. Furthermore, a call to 5965 ** sqlite3_get_auxdata() that occurs immediately after a corresponding call 5966 ** to sqlite3_set_auxdata() might still return NULL if an out-of-memory 5967 ** condition occurred during the sqlite3_set_auxdata() call or if the 5968 ** function is being evaluated during query planning rather than during 5969 ** query execution. 5970 ** 5971 ** ^(In practice, auxiliary data is preserved between function calls for 5972 ** function parameters that are compile-time constants, including literal 5973 ** values and [parameters] and expressions composed from the same.)^ 5974 ** 5975 ** The value of the N parameter to these interfaces should be non-negative. 5976 ** Future enhancements may make use of negative N values to define new 5977 ** kinds of function caching behavior. 5978 ** 5979 ** These routines must be called from the same thread in which 5980 ** the SQL function is running. 5981 ** 5982 ** See also: [sqlite3_get_clientdata()] and [sqlite3_set_clientdata()]. 5983 */ 5984 SQLITE_API void *sqlite3_get_auxdata(sqlite3_context*, int N); 5985 SQLITE_API void sqlite3_set_auxdata(sqlite3_context*, int N, void*, void (*)(void*)); 5986 5987 /* 5988 ** CAPI3REF: Database Connection Client Data 5989 ** METHOD: sqlite3 5990 ** 5991 ** These functions are used to associate one or more named pointers 5992 ** with a [database connection]. 5993 ** A call to sqlite3_set_clientdata(D,N,P,X) causes the pointer P 5994 ** to be attached to [database connection] D using name N. Subsequent 5995 ** calls to sqlite3_get_clientdata(D,N) will return a copy of pointer P 5996 ** or a NULL pointer if there were no prior calls to 5997 ** sqlite3_set_clientdata() with the same values of D and N. 5998 ** Names are compared using strcmp() and are thus case sensitive. 5999 ** 6000 ** If P and X are both non-NULL, then the destructor X is invoked with 6001 ** argument P on the first of the following occurrences: 6002 ** <ul> 6003 ** <li> An out-of-memory error occurs during the call to 6004 ** sqlite3_set_clientdata() which attempts to register pointer P. 6005 ** <li> A subsequent call to sqlite3_set_clientdata(D,N,P,X) is made 6006 ** with the same D and N parameters. 6007 ** <li> The database connection closes. SQLite does not make any guarantees 6008 ** about the order in which destructors are called, only that all 6009 ** destructors will be called exactly once at some point during the 6010 ** database connection closing process. 6011 ** </ul> 6012 ** 6013 ** SQLite does not do anything with client data other than invoke 6014 ** destructors on the client data at the appropriate time. The intended 6015 ** use for client data is to provide a mechanism for wrapper libraries 6016 ** to store additional information about an SQLite database connection. 6017 ** 6018 ** There is no limit (other than available memory) on the number of different 6019 ** client data pointers (with different names) that can be attached to a 6020 ** single database connection. However, the implementation is optimized 6021 ** for the case of having only one or two different client data names. 6022 ** Applications and wrapper libraries are discouraged from using more than 6023 ** one client data name each. 6024 ** 6025 ** There is no way to enumerate the client data pointers 6026 ** associated with a database connection. The N parameter can be thought 6027 ** of as a secret key such that only code that knows the secret key is able 6028 ** to access the associated data. 6029 ** 6030 ** Security Warning: These interfaces should not be exposed in scripting 6031 ** languages or in other circumstances where it might be possible for an 6032 ** an attacker to invoke them. Any agent that can invoke these interfaces 6033 ** can probably also take control of the process. 6034 ** 6035 ** Database connection client data is only available for SQLite 6036 ** version 3.44.0 ([dateof:3.44.0]) and later. 6037 ** 6038 ** See also: [sqlite3_set_auxdata()] and [sqlite3_get_auxdata()]. 6039 */ 6040 SQLITE_API void *sqlite3_get_clientdata(sqlite3*,const char*); 6041 SQLITE_API int sqlite3_set_clientdata(sqlite3*, const char*, void*, void(*)(void*)); 6042 6043 /* 6044 ** CAPI3REF: Constants Defining Special Destructor Behavior 6045 ** 6046 ** These are special values for the destructor that is passed in as the 6047 ** final argument to routines like [sqlite3_result_blob()]. ^If the destructor 6048 ** argument is SQLITE_STATIC, it means that the content pointer is constant 6049 ** and will never change. It does not need to be destroyed. ^The 6050 ** SQLITE_TRANSIENT value means that the content will likely change in 6051 ** the near future and that SQLite should make its own private copy of 6052 ** the content before returning. 6053 ** 6054 ** The typedef is necessary to work around problems in certain 6055 ** C++ compilers. 6056 */ 6057 typedef void (*sqlite3_destructor_type)(void*); 6058 #define SQLITE_STATIC ((sqlite3_destructor_type)0) 6059 #define SQLITE_TRANSIENT ((sqlite3_destructor_type)-1) 6060 6061 /* 6062 ** CAPI3REF: Setting The Result Of An SQL Function 6063 ** METHOD: sqlite3_context 6064 ** 6065 ** These routines are used by the xFunc or xFinal callbacks that 6066 ** implement SQL functions and aggregates. See 6067 ** [sqlite3_create_function()] and [sqlite3_create_function16()] 6068 ** for additional information. 6069 ** 6070 ** These functions work very much like the [parameter binding] family of 6071 ** functions used to bind values to host parameters in prepared statements. 6072 ** Refer to the [SQL parameter] documentation for additional information. 6073 ** 6074 ** ^The sqlite3_result_blob() interface sets the result from 6075 ** an application-defined function to be the BLOB whose content is pointed 6076 ** to by the second parameter and which is N bytes long where N is the 6077 ** third parameter. 6078 ** 6079 ** ^The sqlite3_result_zeroblob(C,N) and sqlite3_result_zeroblob64(C,N) 6080 ** interfaces set the result of the application-defined function to be 6081 ** a BLOB containing all zero bytes and N bytes in size. 6082 ** 6083 ** ^The sqlite3_result_double() interface sets the result from 6084 ** an application-defined function to be a floating point value specified 6085 ** by its 2nd argument. 6086 ** 6087 ** ^The sqlite3_result_error() and sqlite3_result_error16() functions 6088 ** cause the implemented SQL function to throw an exception. 6089 ** ^SQLite uses the string pointed to by the 6090 ** 2nd parameter of sqlite3_result_error() or sqlite3_result_error16() 6091 ** as the text of an error message. ^SQLite interprets the error 6092 ** message string from sqlite3_result_error() as UTF-8. ^SQLite 6093 ** interprets the string from sqlite3_result_error16() as UTF-16 using 6094 ** the same [byte-order determination rules] as [sqlite3_bind_text16()]. 6095 ** ^If the third parameter to sqlite3_result_error() 6096 ** or sqlite3_result_error16() is negative then SQLite takes as the error 6097 ** message all text up through the first zero character. 6098 ** ^If the third parameter to sqlite3_result_error() or 6099 ** sqlite3_result_error16() is non-negative then SQLite takes that many 6100 ** bytes (not characters) from the 2nd parameter as the error message. 6101 ** ^The sqlite3_result_error() and sqlite3_result_error16() 6102 ** routines make a private copy of the error message text before 6103 ** they return. Hence, the calling function can deallocate or 6104 ** modify the text after they return without harm. 6105 ** ^The sqlite3_result_error_code() function changes the error code 6106 ** returned by SQLite as a result of an error in a function. ^By default, 6107 ** the error code is SQLITE_ERROR. ^A subsequent call to sqlite3_result_error() 6108 ** or sqlite3_result_error16() resets the error code to SQLITE_ERROR. 6109 ** 6110 ** ^The sqlite3_result_error_toobig() interface causes SQLite to throw an 6111 ** error indicating that a string or BLOB is too long to represent. 6112 ** 6113 ** ^The sqlite3_result_error_nomem() interface causes SQLite to throw an 6114 ** error indicating that a memory allocation failed. 6115 ** 6116 ** ^The sqlite3_result_int() interface sets the return value 6117 ** of the application-defined function to be the 32-bit signed integer 6118 ** value given in the 2nd argument. 6119 ** ^The sqlite3_result_int64() interface sets the return value 6120 ** of the application-defined function to be the 64-bit signed integer 6121 ** value given in the 2nd argument. 6122 ** 6123 ** ^The sqlite3_result_null() interface sets the return value 6124 ** of the application-defined function to be NULL. 6125 ** 6126 ** ^The sqlite3_result_text(), sqlite3_result_text16(), 6127 ** sqlite3_result_text16le(), and sqlite3_result_text16be() interfaces 6128 ** set the return value of the application-defined function to be 6129 ** a text string which is represented as UTF-8, UTF-16 native byte order, 6130 ** UTF-16 little endian, or UTF-16 big endian, respectively. 6131 ** ^The sqlite3_result_text64() interface sets the return value of an 6132 ** application-defined function to be a text string in an encoding 6133 ** specified by the fifth (and last) parameter, which must be one 6134 ** of [SQLITE_UTF8], [SQLITE_UTF16], [SQLITE_UTF16BE], or [SQLITE_UTF16LE]. 6135 ** ^SQLite takes the text result from the application from 6136 ** the 2nd parameter of the sqlite3_result_text* interfaces. 6137 ** ^If the 3rd parameter to any of the sqlite3_result_text* interfaces 6138 ** other than sqlite3_result_text64() is negative, then SQLite computes 6139 ** the string length itself by searching the 2nd parameter for the first 6140 ** zero character. 6141 ** ^If the 3rd parameter to the sqlite3_result_text* interfaces 6142 ** is non-negative, then as many bytes (not characters) of the text 6143 ** pointed to by the 2nd parameter are taken as the application-defined 6144 ** function result. If the 3rd parameter is non-negative, then it 6145 ** must be the byte offset into the string where the NUL terminator would 6146 ** appear if the string where NUL terminated. If any NUL characters occur 6147 ** in the string at a byte offset that is less than the value of the 3rd 6148 ** parameter, then the resulting string will contain embedded NULs and the 6149 ** result of expressions operating on strings with embedded NULs is undefined. 6150 ** ^If the 4th parameter to the sqlite3_result_text* interfaces 6151 ** or sqlite3_result_blob is a non-NULL pointer, then SQLite calls that 6152 ** function as the destructor on the text or BLOB result when it has 6153 ** finished using that result. 6154 ** ^If the 4th parameter to the sqlite3_result_text* interfaces or to 6155 ** sqlite3_result_blob is the special constant SQLITE_STATIC, then SQLite 6156 ** assumes that the text or BLOB result is in constant space and does not 6157 ** copy the content of the parameter nor call a destructor on the content 6158 ** when it has finished using that result. 6159 ** ^If the 4th parameter to the sqlite3_result_text* interfaces 6160 ** or sqlite3_result_blob is the special constant SQLITE_TRANSIENT 6161 ** then SQLite makes a copy of the result into space obtained 6162 ** from [sqlite3_malloc()] before it returns. 6163 ** 6164 ** ^For the sqlite3_result_text16(), sqlite3_result_text16le(), and 6165 ** sqlite3_result_text16be() routines, and for sqlite3_result_text64() 6166 ** when the encoding is not UTF8, if the input UTF16 begins with a 6167 ** byte-order mark (BOM, U+FEFF) then the BOM is removed from the 6168 ** string and the rest of the string is interpreted according to the 6169 ** byte-order specified by the BOM. ^The byte-order specified by 6170 ** the BOM at the beginning of the text overrides the byte-order 6171 ** specified by the interface procedure. ^So, for example, if 6172 ** sqlite3_result_text16le() is invoked with text that begins 6173 ** with bytes 0xfe, 0xff (a big-endian byte-order mark) then the 6174 ** first two bytes of input are skipped and the remaining input 6175 ** is interpreted as UTF16BE text. 6176 ** 6177 ** ^For UTF16 input text to the sqlite3_result_text16(), 6178 ** sqlite3_result_text16be(), sqlite3_result_text16le(), and 6179 ** sqlite3_result_text64() routines, if the text contains invalid 6180 ** UTF16 characters, the invalid characters might be converted 6181 ** into the unicode replacement character, U+FFFD. 6182 ** 6183 ** ^The sqlite3_result_value() interface sets the result of 6184 ** the application-defined function to be a copy of the 6185 ** [unprotected sqlite3_value] object specified by the 2nd parameter. ^The 6186 ** sqlite3_result_value() interface makes a copy of the [sqlite3_value] 6187 ** so that the [sqlite3_value] specified in the parameter may change or 6188 ** be deallocated after sqlite3_result_value() returns without harm. 6189 ** ^A [protected sqlite3_value] object may always be used where an 6190 ** [unprotected sqlite3_value] object is required, so either 6191 ** kind of [sqlite3_value] object can be used with this interface. 6192 ** 6193 ** ^The sqlite3_result_pointer(C,P,T,D) interface sets the result to an 6194 ** SQL NULL value, just like [sqlite3_result_null(C)], except that it 6195 ** also associates the host-language pointer P or type T with that 6196 ** NULL value such that the pointer can be retrieved within an 6197 ** [application-defined SQL function] using [sqlite3_value_pointer()]. 6198 ** ^If the D parameter is not NULL, then it is a pointer to a destructor 6199 ** for the P parameter. ^SQLite invokes D with P as its only argument 6200 ** when SQLite is finished with P. The T parameter should be a static 6201 ** string and preferably a string literal. The sqlite3_result_pointer() 6202 ** routine is part of the [pointer passing interface] added for SQLite 3.20.0. 6203 ** 6204 ** If these routines are called from within the different thread 6205 ** than the one containing the application-defined function that received 6206 ** the [sqlite3_context] pointer, the results are undefined. 6207 */ 6208 SQLITE_API void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*)); 6209 SQLITE_API void sqlite3_result_blob64(sqlite3_context*,const void*, 6210 sqlite3_uint64,void(*)(void*)); 6211 SQLITE_API void sqlite3_result_double(sqlite3_context*, double); 6212 SQLITE_API void sqlite3_result_error(sqlite3_context*, const char*, int); 6213 SQLITE_API void sqlite3_result_error16(sqlite3_context*, const void*, int); 6214 SQLITE_API void sqlite3_result_error_toobig(sqlite3_context*); 6215 SQLITE_API void sqlite3_result_error_nomem(sqlite3_context*); 6216 SQLITE_API void sqlite3_result_error_code(sqlite3_context*, int); 6217 SQLITE_API void sqlite3_result_int(sqlite3_context*, int); 6218 SQLITE_API void sqlite3_result_int64(sqlite3_context*, sqlite3_int64); 6219 SQLITE_API void sqlite3_result_null(sqlite3_context*); 6220 SQLITE_API void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*)); 6221 SQLITE_API void sqlite3_result_text64(sqlite3_context*, const char*,sqlite3_uint64, 6222 void(*)(void*), unsigned char encoding); 6223 SQLITE_API void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*)); 6224 SQLITE_API void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*)); 6225 SQLITE_API void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*)); 6226 SQLITE_API void sqlite3_result_value(sqlite3_context*, sqlite3_value*); 6227 SQLITE_API void sqlite3_result_pointer(sqlite3_context*, void*,const char*,void(*)(void*)); 6228 SQLITE_API void sqlite3_result_zeroblob(sqlite3_context*, int n); 6229 SQLITE_API int sqlite3_result_zeroblob64(sqlite3_context*, sqlite3_uint64 n); 6230 6231 6232 /* 6233 ** CAPI3REF: Setting The Subtype Of An SQL Function 6234 ** METHOD: sqlite3_context 6235 ** 6236 ** The sqlite3_result_subtype(C,T) function causes the subtype of 6237 ** the result from the [application-defined SQL function] with 6238 ** [sqlite3_context] C to be the value T. Only the lower 8 bits 6239 ** of the subtype T are preserved in current versions of SQLite; 6240 ** higher order bits are discarded. 6241 ** The number of subtype bytes preserved by SQLite might increase 6242 ** in future releases of SQLite. 6243 ** 6244 ** Every [application-defined SQL function] that invokes this interface 6245 ** should include the [SQLITE_RESULT_SUBTYPE] property in its 6246 ** text encoding argument when the SQL function is 6247 ** [sqlite3_create_function|registered]. If the [SQLITE_RESULT_SUBTYPE] 6248 ** property is omitted from the function that invokes sqlite3_result_subtype(), 6249 ** then in some cases the sqlite3_result_subtype() might fail to set 6250 ** the result subtype. 6251 ** 6252 ** If SQLite is compiled with -DSQLITE_STRICT_SUBTYPE=1, then any 6253 ** SQL function that invokes the sqlite3_result_subtype() interface 6254 ** and that does not have the SQLITE_RESULT_SUBTYPE property will raise 6255 ** an error. Future versions of SQLite might enable -DSQLITE_STRICT_SUBTYPE=1 6256 ** by default. 6257 */ 6258 SQLITE_API void sqlite3_result_subtype(sqlite3_context*,unsigned int); 6259 6260 /* 6261 ** CAPI3REF: Define New Collating Sequences 6262 ** METHOD: sqlite3 6263 ** 6264 ** ^These functions add, remove, or modify a [collation] associated 6265 ** with the [database connection] specified as the first argument. 6266 ** 6267 ** ^The name of the collation is a UTF-8 string 6268 ** for sqlite3_create_collation() and sqlite3_create_collation_v2() 6269 ** and a UTF-16 string in native byte order for sqlite3_create_collation16(). 6270 ** ^Collation names that compare equal according to [sqlite3_strnicmp()] are 6271 ** considered to be the same name. 6272 ** 6273 ** ^(The third argument (eTextRep) must be one of the constants: 6274 ** <ul> 6275 ** <li> [SQLITE_UTF8], 6276 ** <li> [SQLITE_UTF16LE], 6277 ** <li> [SQLITE_UTF16BE], 6278 ** <li> [SQLITE_UTF16], or 6279 ** <li> [SQLITE_UTF16_ALIGNED]. 6280 ** </ul>)^ 6281 ** ^The eTextRep argument determines the encoding of strings passed 6282 ** to the collating function callback, xCompare. 6283 ** ^The [SQLITE_UTF16] and [SQLITE_UTF16_ALIGNED] values for eTextRep 6284 ** force strings to be UTF16 with native byte order. 6285 ** ^The [SQLITE_UTF16_ALIGNED] value for eTextRep forces strings to begin 6286 ** on an even byte address. 6287 ** 6288 ** ^The fourth argument, pArg, is an application data pointer that is passed 6289 ** through as the first argument to the collating function callback. 6290 ** 6291 ** ^The fifth argument, xCompare, is a pointer to the collating function. 6292 ** ^Multiple collating functions can be registered using the same name but 6293 ** with different eTextRep parameters and SQLite will use whichever 6294 ** function requires the least amount of data transformation. 6295 ** ^If the xCompare argument is NULL then the collating function is 6296 ** deleted. ^When all collating functions having the same name are deleted, 6297 ** that collation is no longer usable. 6298 ** 6299 ** ^The collating function callback is invoked with a copy of the pArg 6300 ** application data pointer and with two strings in the encoding specified 6301 ** by the eTextRep argument. The two integer parameters to the collating 6302 ** function callback are the length of the two strings, in bytes. The collating 6303 ** function must return an integer that is negative, zero, or positive 6304 ** if the first string is less than, equal to, or greater than the second, 6305 ** respectively. A collating function must always return the same answer 6306 ** given the same inputs. If two or more collating functions are registered 6307 ** to the same collation name (using different eTextRep values) then all 6308 ** must give an equivalent answer when invoked with equivalent strings. 6309 ** The collating function must obey the following properties for all 6310 ** strings A, B, and C: 6311 ** 6312 ** <ol> 6313 ** <li> If A==B then B==A. 6314 ** <li> If A==B and B==C then A==C. 6315 ** <li> If A<B THEN B>A. 6316 ** <li> If A<B and B<C then A<C. 6317 ** </ol> 6318 ** 6319 ** If a collating function fails any of the above constraints and that 6320 ** collating function is registered and used, then the behavior of SQLite 6321 ** is undefined. 6322 ** 6323 ** ^The sqlite3_create_collation_v2() works like sqlite3_create_collation() 6324 ** with the addition that the xDestroy callback is invoked on pArg when 6325 ** the collating function is deleted. 6326 ** ^Collating functions are deleted when they are overridden by later 6327 ** calls to the collation creation functions or when the 6328 ** [database connection] is closed using [sqlite3_close()]. 6329 ** 6330 ** ^The xDestroy callback is <u>not</u> called if the 6331 ** sqlite3_create_collation_v2() function fails. Applications that invoke 6332 ** sqlite3_create_collation_v2() with a non-NULL xDestroy argument should 6333 ** check the return code and dispose of the application data pointer 6334 ** themselves rather than expecting SQLite to deal with it for them. 6335 ** This is different from every other SQLite interface. The inconsistency 6336 ** is unfortunate but cannot be changed without breaking backwards 6337 ** compatibility. 6338 ** 6339 ** See also: [sqlite3_collation_needed()] and [sqlite3_collation_needed16()]. 6340 */ 6341 SQLITE_API int sqlite3_create_collation( 6342 sqlite3*, 6343 const char *zName, 6344 int eTextRep, 6345 void *pArg, 6346 int(*xCompare)(void*,int,const void*,int,const void*) 6347 ); 6348 SQLITE_API int sqlite3_create_collation_v2( 6349 sqlite3*, 6350 const char *zName, 6351 int eTextRep, 6352 void *pArg, 6353 int(*xCompare)(void*,int,const void*,int,const void*), 6354 void(*xDestroy)(void*) 6355 ); 6356 SQLITE_API int sqlite3_create_collation16( 6357 sqlite3*, 6358 const void *zName, 6359 int eTextRep, 6360 void *pArg, 6361 int(*xCompare)(void*,int,const void*,int,const void*) 6362 ); 6363 6364 /* 6365 ** CAPI3REF: Collation Needed Callbacks 6366 ** METHOD: sqlite3 6367 ** 6368 ** ^To avoid having to register all collation sequences before a database 6369 ** can be used, a single callback function may be registered with the 6370 ** [database connection] to be invoked whenever an undefined collation 6371 ** sequence is required. 6372 ** 6373 ** ^If the function is registered using the sqlite3_collation_needed() API, 6374 ** then it is passed the names of undefined collation sequences as strings 6375 ** encoded in UTF-8. ^If sqlite3_collation_needed16() is used, 6376 ** the names are passed as UTF-16 in machine native byte order. 6377 ** ^A call to either function replaces the existing collation-needed callback. 6378 ** 6379 ** ^(When the callback is invoked, the first argument passed is a copy 6380 ** of the second argument to sqlite3_collation_needed() or 6381 ** sqlite3_collation_needed16(). The second argument is the database 6382 ** connection. The third argument is one of [SQLITE_UTF8], [SQLITE_UTF16BE], 6383 ** or [SQLITE_UTF16LE], indicating the most desirable form of the collation 6384 ** sequence function required. The fourth parameter is the name of the 6385 ** required collation sequence.)^ 6386 ** 6387 ** The callback function should register the desired collation using 6388 ** [sqlite3_create_collation()], [sqlite3_create_collation16()], or 6389 ** [sqlite3_create_collation_v2()]. 6390 */ 6391 SQLITE_API int sqlite3_collation_needed( 6392 sqlite3*, 6393 void*, 6394 void(*)(void*,sqlite3*,int eTextRep,const char*) 6395 ); 6396 SQLITE_API int sqlite3_collation_needed16( 6397 sqlite3*, 6398 void*, 6399 void(*)(void*,sqlite3*,int eTextRep,const void*) 6400 ); 6401 6402 #ifdef SQLITE_ENABLE_CEROD 6403 /* 6404 ** Specify the activation key for a CEROD database. Unless 6405 ** activated, none of the CEROD routines will work. 6406 */ 6407 SQLITE_API void sqlite3_activate_cerod( 6408 const char *zPassPhrase /* Activation phrase */ 6409 ); 6410 #endif 6411 6412 /* 6413 ** CAPI3REF: Suspend Execution For A Short Time 6414 ** 6415 ** The sqlite3_sleep() function causes the current thread to suspend execution 6416 ** for at least a number of milliseconds specified in its parameter. 6417 ** 6418 ** If the operating system does not support sleep requests with 6419 ** millisecond time resolution, then the time will be rounded up to 6420 ** the nearest second. The number of milliseconds of sleep actually 6421 ** requested from the operating system is returned. 6422 ** 6423 ** ^SQLite implements this interface by calling the xSleep() 6424 ** method of the default [sqlite3_vfs] object. If the xSleep() method 6425 ** of the default VFS is not implemented correctly, or not implemented at 6426 ** all, then the behavior of sqlite3_sleep() may deviate from the description 6427 ** in the previous paragraphs. 6428 ** 6429 ** If a negative argument is passed to sqlite3_sleep() the results vary by 6430 ** VFS and operating system. Some system treat a negative argument as an 6431 ** instruction to sleep forever. Others understand it to mean do not sleep 6432 ** at all. ^In SQLite version 3.42.0 and later, a negative 6433 ** argument passed into sqlite3_sleep() is changed to zero before it is relayed 6434 ** down into the xSleep method of the VFS. 6435 */ 6436 SQLITE_API int sqlite3_sleep(int); 6437 6438 /* 6439 ** CAPI3REF: Name Of The Folder Holding Temporary Files 6440 ** 6441 ** ^(If this global variable is made to point to a string which is 6442 ** the name of a folder (a.k.a. directory), then all temporary files 6443 ** created by SQLite when using a built-in [sqlite3_vfs | VFS] 6444 ** will be placed in that directory.)^ ^If this variable 6445 ** is a NULL pointer, then SQLite performs a search for an appropriate 6446 ** temporary file directory. 6447 ** 6448 ** Applications are strongly discouraged from using this global variable. 6449 ** It is required to set a temporary folder on Windows Runtime (WinRT). 6450 ** But for all other platforms, it is highly recommended that applications 6451 ** neither read nor write this variable. This global variable is a relic 6452 ** that exists for backwards compatibility of legacy applications and should 6453 ** be avoided in new projects. 6454 ** 6455 ** It is not safe to read or modify this variable in more than one 6456 ** thread at a time. It is not safe to read or modify this variable 6457 ** if a [database connection] is being used at the same time in a separate 6458 ** thread. 6459 ** It is intended that this variable be set once 6460 ** as part of process initialization and before any SQLite interface 6461 ** routines have been called and that this variable remain unchanged 6462 ** thereafter. 6463 ** 6464 ** ^The [temp_store_directory pragma] may modify this variable and cause 6465 ** it to point to memory obtained from [sqlite3_malloc]. ^Furthermore, 6466 ** the [temp_store_directory pragma] always assumes that any string 6467 ** that this variable points to is held in memory obtained from 6468 ** [sqlite3_malloc] and the pragma may attempt to free that memory 6469 ** using [sqlite3_free]. 6470 ** Hence, if this variable is modified directly, either it should be 6471 ** made NULL or made to point to memory obtained from [sqlite3_malloc] 6472 ** or else the use of the [temp_store_directory pragma] should be avoided. 6473 ** Except when requested by the [temp_store_directory pragma], SQLite 6474 ** does not free the memory that sqlite3_temp_directory points to. If 6475 ** the application wants that memory to be freed, it must do 6476 ** so itself, taking care to only do so after all [database connection] 6477 ** objects have been destroyed. 6478 ** 6479 ** <b>Note to Windows Runtime users:</b> The temporary directory must be set 6480 ** prior to calling [sqlite3_open] or [sqlite3_open_v2]. Otherwise, various 6481 ** features that require the use of temporary files may fail. Here is an 6482 ** example of how to do this using C++ with the Windows Runtime: 6483 ** 6484 ** <blockquote><pre> 6485 ** LPCWSTR zPath = Windows::Storage::ApplicationData::Current-> 6486 ** TemporaryFolder->Path->Data(); 6487 ** char zPathBuf[MAX_PATH + 1]; 6488 ** memset(zPathBuf, 0, sizeof(zPathBuf)); 6489 ** WideCharToMultiByte(CP_UTF8, 0, zPath, -1, zPathBuf, sizeof(zPathBuf), 6490 ** NULL, NULL); 6491 ** sqlite3_temp_directory = sqlite3_mprintf("%s", zPathBuf); 6492 ** </pre></blockquote> 6493 */ 6494 SQLITE_API SQLITE_EXTERN char *sqlite3_temp_directory; 6495 6496 /* 6497 ** CAPI3REF: Name Of The Folder Holding Database Files 6498 ** 6499 ** ^(If this global variable is made to point to a string which is 6500 ** the name of a folder (a.k.a. directory), then all database files 6501 ** specified with a relative pathname and created or accessed by 6502 ** SQLite when using a built-in windows [sqlite3_vfs | VFS] will be assumed 6503 ** to be relative to that directory.)^ ^If this variable is a NULL 6504 ** pointer, then SQLite assumes that all database files specified 6505 ** with a relative pathname are relative to the current directory 6506 ** for the process. Only the windows VFS makes use of this global 6507 ** variable; it is ignored by the unix VFS. 6508 ** 6509 ** Changing the value of this variable while a database connection is 6510 ** open can result in a corrupt database. 6511 ** 6512 ** It is not safe to read or modify this variable in more than one 6513 ** thread at a time. It is not safe to read or modify this variable 6514 ** if a [database connection] is being used at the same time in a separate 6515 ** thread. 6516 ** It is intended that this variable be set once 6517 ** as part of process initialization and before any SQLite interface 6518 ** routines have been called and that this variable remain unchanged 6519 ** thereafter. 6520 ** 6521 ** ^The [data_store_directory pragma] may modify this variable and cause 6522 ** it to point to memory obtained from [sqlite3_malloc]. ^Furthermore, 6523 ** the [data_store_directory pragma] always assumes that any string 6524 ** that this variable points to is held in memory obtained from 6525 ** [sqlite3_malloc] and the pragma may attempt to free that memory 6526 ** using [sqlite3_free]. 6527 ** Hence, if this variable is modified directly, either it should be 6528 ** made NULL or made to point to memory obtained from [sqlite3_malloc] 6529 ** or else the use of the [data_store_directory pragma] should be avoided. 6530 */ 6531 SQLITE_API SQLITE_EXTERN char *sqlite3_data_directory; 6532 6533 /* 6534 ** CAPI3REF: Win32 Specific Interface 6535 ** 6536 ** These interfaces are available only on Windows. The 6537 ** [sqlite3_win32_set_directory] interface is used to set the value associated 6538 ** with the [sqlite3_temp_directory] or [sqlite3_data_directory] variable, to 6539 ** zValue, depending on the value of the type parameter. The zValue parameter 6540 ** should be NULL to cause the previous value to be freed via [sqlite3_free]; 6541 ** a non-NULL value will be copied into memory obtained from [sqlite3_malloc] 6542 ** prior to being used. The [sqlite3_win32_set_directory] interface returns 6543 ** [SQLITE_OK] to indicate success, [SQLITE_ERROR] if the type is unsupported, 6544 ** or [SQLITE_NOMEM] if memory could not be allocated. The value of the 6545 ** [sqlite3_data_directory] variable is intended to act as a replacement for 6546 ** the current directory on the sub-platforms of Win32 where that concept is 6547 ** not present, e.g. WinRT and UWP. The [sqlite3_win32_set_directory8] and 6548 ** [sqlite3_win32_set_directory16] interfaces behave exactly the same as the 6549 ** sqlite3_win32_set_directory interface except the string parameter must be 6550 ** UTF-8 or UTF-16, respectively. 6551 */ 6552 SQLITE_API int sqlite3_win32_set_directory( 6553 unsigned long type, /* Identifier for directory being set or reset */ 6554 void *zValue /* New value for directory being set or reset */ 6555 ); 6556 SQLITE_API int sqlite3_win32_set_directory8(unsigned long type, const char *zValue); 6557 SQLITE_API int sqlite3_win32_set_directory16(unsigned long type, const void *zValue); 6558 6559 /* 6560 ** CAPI3REF: Win32 Directory Types 6561 ** 6562 ** These macros are only available on Windows. They define the allowed values 6563 ** for the type argument to the [sqlite3_win32_set_directory] interface. 6564 */ 6565 #define SQLITE_WIN32_DATA_DIRECTORY_TYPE 1 6566 #define SQLITE_WIN32_TEMP_DIRECTORY_TYPE 2 6567 6568 /* 6569 ** CAPI3REF: Test For Auto-Commit Mode 6570 ** KEYWORDS: {autocommit mode} 6571 ** METHOD: sqlite3 6572 ** 6573 ** ^The sqlite3_get_autocommit() interface returns non-zero or 6574 ** zero if the given database connection is or is not in autocommit mode, 6575 ** respectively. ^Autocommit mode is on by default. 6576 ** ^Autocommit mode is disabled by a [BEGIN] statement. 6577 ** ^Autocommit mode is re-enabled by a [COMMIT] or [ROLLBACK]. 6578 ** 6579 ** If certain kinds of errors occur on a statement within a multi-statement 6580 ** transaction (errors including [SQLITE_FULL], [SQLITE_IOERR], 6581 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the 6582 ** transaction might be rolled back automatically. The only way to 6583 ** find out whether SQLite automatically rolled back the transaction after 6584 ** an error is to use this function. 6585 ** 6586 ** If another thread changes the autocommit status of the database 6587 ** connection while this routine is running, then the return value 6588 ** is undefined. 6589 */ 6590 SQLITE_API int sqlite3_get_autocommit(sqlite3*); 6591 6592 /* 6593 ** CAPI3REF: Find The Database Handle Of A Prepared Statement 6594 ** METHOD: sqlite3_stmt 6595 ** 6596 ** ^The sqlite3_db_handle interface returns the [database connection] handle 6597 ** to which a [prepared statement] belongs. ^The [database connection] 6598 ** returned by sqlite3_db_handle is the same [database connection] 6599 ** that was the first argument 6600 ** to the [sqlite3_prepare_v2()] call (or its variants) that was used to 6601 ** create the statement in the first place. 6602 */ 6603 SQLITE_API sqlite3 *sqlite3_db_handle(sqlite3_stmt*); 6604 6605 /* 6606 ** CAPI3REF: Return The Schema Name For A Database Connection 6607 ** METHOD: sqlite3 6608 ** 6609 ** ^The sqlite3_db_name(D,N) interface returns a pointer to the schema name 6610 ** for the N-th database on database connection D, or a NULL pointer of N is 6611 ** out of range. An N value of 0 means the main database file. An N of 1 is 6612 ** the "temp" schema. Larger values of N correspond to various ATTACH-ed 6613 ** databases. 6614 ** 6615 ** Space to hold the string that is returned by sqlite3_db_name() is managed 6616 ** by SQLite itself. The string might be deallocated by any operation that 6617 ** changes the schema, including [ATTACH] or [DETACH] or calls to 6618 ** [sqlite3_serialize()] or [sqlite3_deserialize()], even operations that 6619 ** occur on a different thread. Applications that need to 6620 ** remember the string long-term should make their own copy. Applications that 6621 ** are accessing the same database connection simultaneously on multiple 6622 ** threads should mutex-protect calls to this API and should make their own 6623 ** private copy of the result prior to releasing the mutex. 6624 */ 6625 SQLITE_API const char *sqlite3_db_name(sqlite3 *db, int N); 6626 6627 /* 6628 ** CAPI3REF: Return The Filename For A Database Connection 6629 ** METHOD: sqlite3 6630 ** 6631 ** ^The sqlite3_db_filename(D,N) interface returns a pointer to the filename 6632 ** associated with database N of connection D. 6633 ** ^If there is no attached database N on the database 6634 ** connection D, or if database N is a temporary or in-memory database, then 6635 ** this function will return either a NULL pointer or an empty string. 6636 ** 6637 ** ^The string value returned by this routine is owned and managed by 6638 ** the database connection. ^The value will be valid until the database N 6639 ** is [DETACH]-ed or until the database connection closes. 6640 ** 6641 ** ^The filename returned by this function is the output of the 6642 ** xFullPathname method of the [VFS]. ^In other words, the filename 6643 ** will be an absolute pathname, even if the filename used 6644 ** to open the database originally was a URI or relative pathname. 6645 ** 6646 ** If the filename pointer returned by this routine is not NULL, then it 6647 ** can be used as the filename input parameter to these routines: 6648 ** <ul> 6649 ** <li> [sqlite3_uri_parameter()] 6650 ** <li> [sqlite3_uri_boolean()] 6651 ** <li> [sqlite3_uri_int64()] 6652 ** <li> [sqlite3_filename_database()] 6653 ** <li> [sqlite3_filename_journal()] 6654 ** <li> [sqlite3_filename_wal()] 6655 ** </ul> 6656 */ 6657 SQLITE_API sqlite3_filename sqlite3_db_filename(sqlite3 *db, const char *zDbName); 6658 6659 /* 6660 ** CAPI3REF: Determine if a database is read-only 6661 ** METHOD: sqlite3 6662 ** 6663 ** ^The sqlite3_db_readonly(D,N) interface returns 1 if the database N 6664 ** of connection D is read-only, 0 if it is read/write, or -1 if N is not 6665 ** the name of a database on connection D. 6666 */ 6667 SQLITE_API int sqlite3_db_readonly(sqlite3 *db, const char *zDbName); 6668 6669 /* 6670 ** CAPI3REF: Determine the transaction state of a database 6671 ** METHOD: sqlite3 6672 ** 6673 ** ^The sqlite3_txn_state(D,S) interface returns the current 6674 ** [transaction state] of schema S in database connection D. ^If S is NULL, 6675 ** then the highest transaction state of any schema on database connection D 6676 ** is returned. Transaction states are (in order of lowest to highest): 6677 ** <ol> 6678 ** <li value="0"> SQLITE_TXN_NONE 6679 ** <li value="1"> SQLITE_TXN_READ 6680 ** <li value="2"> SQLITE_TXN_WRITE 6681 ** </ol> 6682 ** ^If the S argument to sqlite3_txn_state(D,S) is not the name of 6683 ** a valid schema, then -1 is returned. 6684 */ 6685 SQLITE_API int sqlite3_txn_state(sqlite3*,const char *zSchema); 6686 6687 /* 6688 ** CAPI3REF: Allowed return values from sqlite3_txn_state() 6689 ** KEYWORDS: {transaction state} 6690 ** 6691 ** These constants define the current transaction state of a database file. 6692 ** ^The [sqlite3_txn_state(D,S)] interface returns one of these 6693 ** constants in order to describe the transaction state of schema S 6694 ** in [database connection] D. 6695 ** 6696 ** <dl> 6697 ** [[SQLITE_TXN_NONE]] <dt>SQLITE_TXN_NONE</dt> 6698 ** <dd>The SQLITE_TXN_NONE state means that no transaction is currently 6699 ** pending.</dd> 6700 ** 6701 ** [[SQLITE_TXN_READ]] <dt>SQLITE_TXN_READ</dt> 6702 ** <dd>The SQLITE_TXN_READ state means that the database is currently 6703 ** in a read transaction. Content has been read from the database file 6704 ** but nothing in the database file has changed. The transaction state 6705 ** will advanced to SQLITE_TXN_WRITE if any changes occur and there are 6706 ** no other conflicting concurrent write transactions. The transaction 6707 ** state will revert to SQLITE_TXN_NONE following a [ROLLBACK] or 6708 ** [COMMIT].</dd> 6709 ** 6710 ** [[SQLITE_TXN_WRITE]] <dt>SQLITE_TXN_WRITE</dt> 6711 ** <dd>The SQLITE_TXN_WRITE state means that the database is currently 6712 ** in a write transaction. Content has been written to the database file 6713 ** but has not yet committed. The transaction state will change to 6714 ** to SQLITE_TXN_NONE at the next [ROLLBACK] or [COMMIT].</dd> 6715 */ 6716 #define SQLITE_TXN_NONE 0 6717 #define SQLITE_TXN_READ 1 6718 #define SQLITE_TXN_WRITE 2 6719 6720 /* 6721 ** CAPI3REF: Find the next prepared statement 6722 ** METHOD: sqlite3 6723 ** 6724 ** ^This interface returns a pointer to the next [prepared statement] after 6725 ** pStmt associated with the [database connection] pDb. ^If pStmt is NULL 6726 ** then this interface returns a pointer to the first prepared statement 6727 ** associated with the database connection pDb. ^If no prepared statement 6728 ** satisfies the conditions of this routine, it returns NULL. 6729 ** 6730 ** The [database connection] pointer D in a call to 6731 ** [sqlite3_next_stmt(D,S)] must refer to an open database 6732 ** connection and in particular must not be a NULL pointer. 6733 */ 6734 SQLITE_API sqlite3_stmt *sqlite3_next_stmt(sqlite3 *pDb, sqlite3_stmt *pStmt); 6735 6736 /* 6737 ** CAPI3REF: Commit And Rollback Notification Callbacks 6738 ** METHOD: sqlite3 6739 ** 6740 ** ^The sqlite3_commit_hook() interface registers a callback 6741 ** function to be invoked whenever a transaction is [COMMIT | committed]. 6742 ** ^Any callback set by a previous call to sqlite3_commit_hook() 6743 ** for the same database connection is overridden. 6744 ** ^The sqlite3_rollback_hook() interface registers a callback 6745 ** function to be invoked whenever a transaction is [ROLLBACK | rolled back]. 6746 ** ^Any callback set by a previous call to sqlite3_rollback_hook() 6747 ** for the same database connection is overridden. 6748 ** ^The pArg argument is passed through to the callback. 6749 ** ^If the callback on a commit hook function returns non-zero, 6750 ** then the commit is converted into a rollback. 6751 ** 6752 ** ^The sqlite3_commit_hook(D,C,P) and sqlite3_rollback_hook(D,C,P) functions 6753 ** return the P argument from the previous call of the same function 6754 ** on the same [database connection] D, or NULL for 6755 ** the first call for each function on D. 6756 ** 6757 ** The commit and rollback hook callbacks are not reentrant. 6758 ** The callback implementation must not do anything that will modify 6759 ** the database connection that invoked the callback. Any actions 6760 ** to modify the database connection must be deferred until after the 6761 ** completion of the [sqlite3_step()] call that triggered the commit 6762 ** or rollback hook in the first place. 6763 ** Note that running any other SQL statements, including SELECT statements, 6764 ** or merely calling [sqlite3_prepare_v2()] and [sqlite3_step()] will modify 6765 ** the database connections for the meaning of "modify" in this paragraph. 6766 ** 6767 ** ^Registering a NULL function disables the callback. 6768 ** 6769 ** ^When the commit hook callback routine returns zero, the [COMMIT] 6770 ** operation is allowed to continue normally. ^If the commit hook 6771 ** returns non-zero, then the [COMMIT] is converted into a [ROLLBACK]. 6772 ** ^The rollback hook is invoked on a rollback that results from a commit 6773 ** hook returning non-zero, just as it would be with any other rollback. 6774 ** 6775 ** ^For the purposes of this API, a transaction is said to have been 6776 ** rolled back if an explicit "ROLLBACK" statement is executed, or 6777 ** an error or constraint causes an implicit rollback to occur. 6778 ** ^The rollback callback is not invoked if a transaction is 6779 ** automatically rolled back because the database connection is closed. 6780 ** 6781 ** See also the [sqlite3_update_hook()] interface. 6782 */ 6783 SQLITE_API void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*); 6784 SQLITE_API void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*); 6785 6786 /* 6787 ** CAPI3REF: Autovacuum Compaction Amount Callback 6788 ** METHOD: sqlite3 6789 ** 6790 ** ^The sqlite3_autovacuum_pages(D,C,P,X) interface registers a callback 6791 ** function C that is invoked prior to each autovacuum of the database 6792 ** file. ^The callback is passed a copy of the generic data pointer (P), 6793 ** the schema-name of the attached database that is being autovacuumed, 6794 ** the size of the database file in pages, the number of free pages, 6795 ** and the number of bytes per page, respectively. The callback should 6796 ** return the number of free pages that should be removed by the 6797 ** autovacuum. ^If the callback returns zero, then no autovacuum happens. 6798 ** ^If the value returned is greater than or equal to the number of 6799 ** free pages, then a complete autovacuum happens. 6800 ** 6801 ** <p>^If there are multiple ATTACH-ed database files that are being 6802 ** modified as part of a transaction commit, then the autovacuum pages 6803 ** callback is invoked separately for each file. 6804 ** 6805 ** <p><b>The callback is not reentrant.</b> The callback function should 6806 ** not attempt to invoke any other SQLite interface. If it does, bad 6807 ** things may happen, including segmentation faults and corrupt database 6808 ** files. The callback function should be a simple function that 6809 ** does some arithmetic on its input parameters and returns a result. 6810 ** 6811 ** ^The X parameter to sqlite3_autovacuum_pages(D,C,P,X) is an optional 6812 ** destructor for the P parameter. ^If X is not NULL, then X(P) is 6813 ** invoked whenever the database connection closes or when the callback 6814 ** is overwritten by another invocation of sqlite3_autovacuum_pages(). 6815 ** 6816 ** <p>^There is only one autovacuum pages callback per database connection. 6817 ** ^Each call to the sqlite3_autovacuum_pages() interface overrides all 6818 ** previous invocations for that database connection. ^If the callback 6819 ** argument (C) to sqlite3_autovacuum_pages(D,C,P,X) is a NULL pointer, 6820 ** then the autovacuum steps callback is canceled. The return value 6821 ** from sqlite3_autovacuum_pages() is normally SQLITE_OK, but might 6822 ** be some other error code if something goes wrong. The current 6823 ** implementation will only return SQLITE_OK or SQLITE_MISUSE, but other 6824 ** return codes might be added in future releases. 6825 ** 6826 ** <p>If no autovacuum pages callback is specified (the usual case) or 6827 ** a NULL pointer is provided for the callback, 6828 ** then the default behavior is to vacuum all free pages. So, in other 6829 ** words, the default behavior is the same as if the callback function 6830 ** were something like this: 6831 ** 6832 ** <blockquote><pre> 6833 ** unsigned int demonstration_autovac_pages_callback( 6834 ** void *pClientData, 6835 ** const char *zSchema, 6836 ** unsigned int nDbPage, 6837 ** unsigned int nFreePage, 6838 ** unsigned int nBytePerPage 6839 ** ){ 6840 ** return nFreePage; 6841 ** } 6842 ** </pre></blockquote> 6843 */ 6844 SQLITE_API int sqlite3_autovacuum_pages( 6845 sqlite3 *db, 6846 unsigned int(*)(void*,const char*,unsigned int,unsigned int,unsigned int), 6847 void*, 6848 void(*)(void*) 6849 ); 6850 6851 6852 /* 6853 ** CAPI3REF: Data Change Notification Callbacks 6854 ** METHOD: sqlite3 6855 ** 6856 ** ^The sqlite3_update_hook() interface registers a callback function 6857 ** with the [database connection] identified by the first argument 6858 ** to be invoked whenever a row is updated, inserted or deleted in 6859 ** a [rowid table]. 6860 ** ^Any callback set by a previous call to this function 6861 ** for the same database connection is overridden. 6862 ** 6863 ** ^The second argument is a pointer to the function to invoke when a 6864 ** row is updated, inserted or deleted in a rowid table. 6865 ** ^The first argument to the callback is a copy of the third argument 6866 ** to sqlite3_update_hook(). 6867 ** ^The second callback argument is one of [SQLITE_INSERT], [SQLITE_DELETE], 6868 ** or [SQLITE_UPDATE], depending on the operation that caused the callback 6869 ** to be invoked. 6870 ** ^The third and fourth arguments to the callback contain pointers to the 6871 ** database and table name containing the affected row. 6872 ** ^The final callback parameter is the [rowid] of the row. 6873 ** ^In the case of an update, this is the [rowid] after the update takes place. 6874 ** 6875 ** ^(The update hook is not invoked when internal system tables are 6876 ** modified (i.e. sqlite_sequence).)^ 6877 ** ^The update hook is not invoked when [WITHOUT ROWID] tables are modified. 6878 ** 6879 ** ^In the current implementation, the update hook 6880 ** is not invoked when conflicting rows are deleted because of an 6881 ** [ON CONFLICT | ON CONFLICT REPLACE] clause. ^Nor is the update hook 6882 ** invoked when rows are deleted using the [truncate optimization]. 6883 ** The exceptions defined in this paragraph might change in a future 6884 ** release of SQLite. 6885 ** 6886 ** The update hook implementation must not do anything that will modify 6887 ** the database connection that invoked the update hook. Any actions 6888 ** to modify the database connection must be deferred until after the 6889 ** completion of the [sqlite3_step()] call that triggered the update hook. 6890 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their 6891 ** database connections for the meaning of "modify" in this paragraph. 6892 ** 6893 ** ^The sqlite3_update_hook(D,C,P) function 6894 ** returns the P argument from the previous call 6895 ** on the same [database connection] D, or NULL for 6896 ** the first call on D. 6897 ** 6898 ** See also the [sqlite3_commit_hook()], [sqlite3_rollback_hook()], 6899 ** and [sqlite3_preupdate_hook()] interfaces. 6900 */ 6901 SQLITE_API void *sqlite3_update_hook( 6902 sqlite3*, 6903 void(*)(void *,int ,char const *,char const *,sqlite3_int64), 6904 void* 6905 ); 6906 6907 /* 6908 ** CAPI3REF: Enable Or Disable Shared Pager Cache 6909 ** 6910 ** ^(This routine enables or disables the sharing of the database cache 6911 ** and schema data structures between [database connection | connections] 6912 ** to the same database. Sharing is enabled if the argument is true 6913 ** and disabled if the argument is false.)^ 6914 ** 6915 ** This interface is omitted if SQLite is compiled with 6916 ** [-DSQLITE_OMIT_SHARED_CACHE]. The [-DSQLITE_OMIT_SHARED_CACHE] 6917 ** compile-time option is recommended because the 6918 ** [use of shared cache mode is discouraged]. 6919 ** 6920 ** ^Cache sharing is enabled and disabled for an entire process. 6921 ** This is a change as of SQLite [version 3.5.0] ([dateof:3.5.0]). 6922 ** In prior versions of SQLite, 6923 ** sharing was enabled or disabled for each thread separately. 6924 ** 6925 ** ^(The cache sharing mode set by this interface effects all subsequent 6926 ** calls to [sqlite3_open()], [sqlite3_open_v2()], and [sqlite3_open16()]. 6927 ** Existing database connections continue to use the sharing mode 6928 ** that was in effect at the time they were opened.)^ 6929 ** 6930 ** ^(This routine returns [SQLITE_OK] if shared cache was enabled or disabled 6931 ** successfully. An [error code] is returned otherwise.)^ 6932 ** 6933 ** ^Shared cache is disabled by default. It is recommended that it stay 6934 ** that way. In other words, do not use this routine. This interface 6935 ** continues to be provided for historical compatibility, but its use is 6936 ** discouraged. Any use of shared cache is discouraged. If shared cache 6937 ** must be used, it is recommended that shared cache only be enabled for 6938 ** individual database connections using the [sqlite3_open_v2()] interface 6939 ** with the [SQLITE_OPEN_SHAREDCACHE] flag. 6940 ** 6941 ** Note: This method is disabled on MacOS X 10.7 and iOS version 5.0 6942 ** and will always return SQLITE_MISUSE. On those systems, 6943 ** shared cache mode should be enabled per-database connection via 6944 ** [sqlite3_open_v2()] with [SQLITE_OPEN_SHAREDCACHE]. 6945 ** 6946 ** This interface is threadsafe on processors where writing a 6947 ** 32-bit integer is atomic. 6948 ** 6949 ** See Also: [SQLite Shared-Cache Mode] 6950 */ 6951 SQLITE_API int sqlite3_enable_shared_cache(int); 6952 6953 /* 6954 ** CAPI3REF: Attempt To Free Heap Memory 6955 ** 6956 ** ^The sqlite3_release_memory() interface attempts to free N bytes 6957 ** of heap memory by deallocating non-essential memory allocations 6958 ** held by the database library. Memory used to cache database 6959 ** pages to improve performance is an example of non-essential memory. 6960 ** ^sqlite3_release_memory() returns the number of bytes actually freed, 6961 ** which might be more or less than the amount requested. 6962 ** ^The sqlite3_release_memory() routine is a no-op returning zero 6963 ** if SQLite is not compiled with [SQLITE_ENABLE_MEMORY_MANAGEMENT]. 6964 ** 6965 ** See also: [sqlite3_db_release_memory()] 6966 */ 6967 SQLITE_API int sqlite3_release_memory(int); 6968 6969 /* 6970 ** CAPI3REF: Free Memory Used By A Database Connection 6971 ** METHOD: sqlite3 6972 ** 6973 ** ^The sqlite3_db_release_memory(D) interface attempts to free as much heap 6974 ** memory as possible from database connection D. Unlike the 6975 ** [sqlite3_release_memory()] interface, this interface is in effect even 6976 ** when the [SQLITE_ENABLE_MEMORY_MANAGEMENT] compile-time option is 6977 ** omitted. 6978 ** 6979 ** See also: [sqlite3_release_memory()] 6980 */ 6981 SQLITE_API int sqlite3_db_release_memory(sqlite3*); 6982 6983 /* 6984 ** CAPI3REF: Impose A Limit On Heap Size 6985 ** 6986 ** These interfaces impose limits on the amount of heap memory that will be 6987 ** by all database connections within a single process. 6988 ** 6989 ** ^The sqlite3_soft_heap_limit64() interface sets and/or queries the 6990 ** soft limit on the amount of heap memory that may be allocated by SQLite. 6991 ** ^SQLite strives to keep heap memory utilization below the soft heap 6992 ** limit by reducing the number of pages held in the page cache 6993 ** as heap memory usages approaches the limit. 6994 ** ^The soft heap limit is "soft" because even though SQLite strives to stay 6995 ** below the limit, it will exceed the limit rather than generate 6996 ** an [SQLITE_NOMEM] error. In other words, the soft heap limit 6997 ** is advisory only. 6998 ** 6999 ** ^The sqlite3_hard_heap_limit64(N) interface sets a hard upper bound of 7000 ** N bytes on the amount of memory that will be allocated. ^The 7001 ** sqlite3_hard_heap_limit64(N) interface is similar to 7002 ** sqlite3_soft_heap_limit64(N) except that memory allocations will fail 7003 ** when the hard heap limit is reached. 7004 ** 7005 ** ^The return value from both sqlite3_soft_heap_limit64() and 7006 ** sqlite3_hard_heap_limit64() is the size of 7007 ** the heap limit prior to the call, or negative in the case of an 7008 ** error. ^If the argument N is negative 7009 ** then no change is made to the heap limit. Hence, the current 7010 ** size of heap limits can be determined by invoking 7011 ** sqlite3_soft_heap_limit64(-1) or sqlite3_hard_heap_limit(-1). 7012 ** 7013 ** ^Setting the heap limits to zero disables the heap limiter mechanism. 7014 ** 7015 ** ^The soft heap limit may not be greater than the hard heap limit. 7016 ** ^If the hard heap limit is enabled and if sqlite3_soft_heap_limit(N) 7017 ** is invoked with a value of N that is greater than the hard heap limit, 7018 ** the soft heap limit is set to the value of the hard heap limit. 7019 ** ^The soft heap limit is automatically enabled whenever the hard heap 7020 ** limit is enabled. ^When sqlite3_hard_heap_limit64(N) is invoked and 7021 ** the soft heap limit is outside the range of 1..N, then the soft heap 7022 ** limit is set to N. ^Invoking sqlite3_soft_heap_limit64(0) when the 7023 ** hard heap limit is enabled makes the soft heap limit equal to the 7024 ** hard heap limit. 7025 ** 7026 ** The memory allocation limits can also be adjusted using 7027 ** [PRAGMA soft_heap_limit] and [PRAGMA hard_heap_limit]. 7028 ** 7029 ** ^(The heap limits are not enforced in the current implementation 7030 ** if one or more of following conditions are true: 7031 ** 7032 ** <ul> 7033 ** <li> The limit value is set to zero. 7034 ** <li> Memory accounting is disabled using a combination of the 7035 ** [sqlite3_config]([SQLITE_CONFIG_MEMSTATUS],...) start-time option and 7036 ** the [SQLITE_DEFAULT_MEMSTATUS] compile-time option. 7037 ** <li> An alternative page cache implementation is specified using 7038 ** [sqlite3_config]([SQLITE_CONFIG_PCACHE2],...). 7039 ** <li> The page cache allocates from its own memory pool supplied 7040 ** by [sqlite3_config]([SQLITE_CONFIG_PAGECACHE],...) rather than 7041 ** from the heap. 7042 ** </ul>)^ 7043 ** 7044 ** The circumstances under which SQLite will enforce the heap limits may 7045 ** changes in future releases of SQLite. 7046 */ 7047 SQLITE_API sqlite3_int64 sqlite3_soft_heap_limit64(sqlite3_int64 N); 7048 SQLITE_API sqlite3_int64 sqlite3_hard_heap_limit64(sqlite3_int64 N); 7049 7050 /* 7051 ** CAPI3REF: Deprecated Soft Heap Limit Interface 7052 ** DEPRECATED 7053 ** 7054 ** This is a deprecated version of the [sqlite3_soft_heap_limit64()] 7055 ** interface. This routine is provided for historical compatibility 7056 ** only. All new applications should use the 7057 ** [sqlite3_soft_heap_limit64()] interface rather than this one. 7058 */ 7059 SQLITE_API SQLITE_DEPRECATED void sqlite3_soft_heap_limit(int N); 7060 7061 7062 /* 7063 ** CAPI3REF: Extract Metadata About A Column Of A Table 7064 ** METHOD: sqlite3 7065 ** 7066 ** ^(The sqlite3_table_column_metadata(X,D,T,C,....) routine returns 7067 ** information about column C of table T in database D 7068 ** on [database connection] X.)^ ^The sqlite3_table_column_metadata() 7069 ** interface returns SQLITE_OK and fills in the non-NULL pointers in 7070 ** the final five arguments with appropriate values if the specified 7071 ** column exists. ^The sqlite3_table_column_metadata() interface returns 7072 ** SQLITE_ERROR if the specified column does not exist. 7073 ** ^If the column-name parameter to sqlite3_table_column_metadata() is a 7074 ** NULL pointer, then this routine simply checks for the existence of the 7075 ** table and returns SQLITE_OK if the table exists and SQLITE_ERROR if it 7076 ** does not. If the table name parameter T in a call to 7077 ** sqlite3_table_column_metadata(X,D,T,C,...) is NULL then the result is 7078 ** undefined behavior. 7079 ** 7080 ** ^The column is identified by the second, third and fourth parameters to 7081 ** this function. ^(The second parameter is either the name of the database 7082 ** (i.e. "main", "temp", or an attached database) containing the specified 7083 ** table or NULL.)^ ^If it is NULL, then all attached databases are searched 7084 ** for the table using the same algorithm used by the database engine to 7085 ** resolve unqualified table references. 7086 ** 7087 ** ^The third and fourth parameters to this function are the table and column 7088 ** name of the desired column, respectively. 7089 ** 7090 ** ^Metadata is returned by writing to the memory locations passed as the 5th 7091 ** and subsequent parameters to this function. ^Any of these arguments may be 7092 ** NULL, in which case the corresponding element of metadata is omitted. 7093 ** 7094 ** ^(<blockquote> 7095 ** <table border="1"> 7096 ** <tr><th> Parameter <th> Output<br>Type <th> Description 7097 ** 7098 ** <tr><td> 5th <td> const char* <td> Data type 7099 ** <tr><td> 6th <td> const char* <td> Name of default collation sequence 7100 ** <tr><td> 7th <td> int <td> True if column has a NOT NULL constraint 7101 ** <tr><td> 8th <td> int <td> True if column is part of the PRIMARY KEY 7102 ** <tr><td> 9th <td> int <td> True if column is [AUTOINCREMENT] 7103 ** </table> 7104 ** </blockquote>)^ 7105 ** 7106 ** ^The memory pointed to by the character pointers returned for the 7107 ** declaration type and collation sequence is valid until the next 7108 ** call to any SQLite API function. 7109 ** 7110 ** ^If the specified table is actually a view, an [error code] is returned. 7111 ** 7112 ** ^If the specified column is "rowid", "oid" or "_rowid_" and the table 7113 ** is not a [WITHOUT ROWID] table and an 7114 ** [INTEGER PRIMARY KEY] column has been explicitly declared, then the output 7115 ** parameters are set for the explicitly declared column. ^(If there is no 7116 ** [INTEGER PRIMARY KEY] column, then the outputs 7117 ** for the [rowid] are set as follows: 7118 ** 7119 ** <pre> 7120 ** data type: "INTEGER" 7121 ** collation sequence: "BINARY" 7122 ** not null: 0 7123 ** primary key: 1 7124 ** auto increment: 0 7125 ** </pre>)^ 7126 ** 7127 ** ^This function causes all database schemas to be read from disk and 7128 ** parsed, if that has not already been done, and returns an error if 7129 ** any errors are encountered while loading the schema. 7130 */ 7131 SQLITE_API int sqlite3_table_column_metadata( 7132 sqlite3 *db, /* Connection handle */ 7133 const char *zDbName, /* Database name or NULL */ 7134 const char *zTableName, /* Table name */ 7135 const char *zColumnName, /* Column name */ 7136 char const **pzDataType, /* OUTPUT: Declared data type */ 7137 char const **pzCollSeq, /* OUTPUT: Collation sequence name */ 7138 int *pNotNull, /* OUTPUT: True if NOT NULL constraint exists */ 7139 int *pPrimaryKey, /* OUTPUT: True if column part of PK */ 7140 int *pAutoinc /* OUTPUT: True if column is auto-increment */ 7141 ); 7142 7143 /* 7144 ** CAPI3REF: Load An Extension 7145 ** METHOD: sqlite3 7146 ** 7147 ** ^This interface loads an SQLite extension library from the named file. 7148 ** 7149 ** ^The sqlite3_load_extension() interface attempts to load an 7150 ** [SQLite extension] library contained in the file zFile. If 7151 ** the file cannot be loaded directly, attempts are made to load 7152 ** with various operating-system specific extensions added. 7153 ** So for example, if "samplelib" cannot be loaded, then names like 7154 ** "samplelib.so" or "samplelib.dylib" or "samplelib.dll" might 7155 ** be tried also. 7156 ** 7157 ** ^The entry point is zProc. 7158 ** ^(zProc may be 0, in which case SQLite will try to come up with an 7159 ** entry point name on its own. It first tries "sqlite3_extension_init". 7160 ** If that does not work, it constructs a name "sqlite3_X_init" where the 7161 ** X is consists of the lower-case equivalent of all ASCII alphabetic 7162 ** characters in the filename from the last "/" to the first following 7163 ** "." and omitting any initial "lib".)^ 7164 ** ^The sqlite3_load_extension() interface returns 7165 ** [SQLITE_OK] on success and [SQLITE_ERROR] if something goes wrong. 7166 ** ^If an error occurs and pzErrMsg is not 0, then the 7167 ** [sqlite3_load_extension()] interface shall attempt to 7168 ** fill *pzErrMsg with error message text stored in memory 7169 ** obtained from [sqlite3_malloc()]. The calling function 7170 ** should free this memory by calling [sqlite3_free()]. 7171 ** 7172 ** ^Extension loading must be enabled using 7173 ** [sqlite3_enable_load_extension()] or 7174 ** [sqlite3_db_config](db,[SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION],1,NULL) 7175 ** prior to calling this API, 7176 ** otherwise an error will be returned. 7177 ** 7178 ** <b>Security warning:</b> It is recommended that the 7179 ** [SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION] method be used to enable only this 7180 ** interface. The use of the [sqlite3_enable_load_extension()] interface 7181 ** should be avoided. This will keep the SQL function [load_extension()] 7182 ** disabled and prevent SQL injections from giving attackers 7183 ** access to extension loading capabilities. 7184 ** 7185 ** See also the [load_extension() SQL function]. 7186 */ 7187 SQLITE_API int sqlite3_load_extension( 7188 sqlite3 *db, /* Load the extension into this database connection */ 7189 const char *zFile, /* Name of the shared library containing extension */ 7190 const char *zProc, /* Entry point. Derived from zFile if 0 */ 7191 char **pzErrMsg /* Put error message here if not 0 */ 7192 ); 7193 7194 /* 7195 ** CAPI3REF: Enable Or Disable Extension Loading 7196 ** METHOD: sqlite3 7197 ** 7198 ** ^So as not to open security holes in older applications that are 7199 ** unprepared to deal with [extension loading], and as a means of disabling 7200 ** [extension loading] while evaluating user-entered SQL, the following API 7201 ** is provided to turn the [sqlite3_load_extension()] mechanism on and off. 7202 ** 7203 ** ^Extension loading is off by default. 7204 ** ^Call the sqlite3_enable_load_extension() routine with onoff==1 7205 ** to turn extension loading on and call it with onoff==0 to turn 7206 ** it back off again. 7207 ** 7208 ** ^This interface enables or disables both the C-API 7209 ** [sqlite3_load_extension()] and the SQL function [load_extension()]. 7210 ** ^(Use [sqlite3_db_config](db,[SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION],..) 7211 ** to enable or disable only the C-API.)^ 7212 ** 7213 ** <b>Security warning:</b> It is recommended that extension loading 7214 ** be enabled using the [SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION] method 7215 ** rather than this interface, so the [load_extension()] SQL function 7216 ** remains disabled. This will prevent SQL injections from giving attackers 7217 ** access to extension loading capabilities. 7218 */ 7219 SQLITE_API int sqlite3_enable_load_extension(sqlite3 *db, int onoff); 7220 7221 /* 7222 ** CAPI3REF: Automatically Load Statically Linked Extensions 7223 ** 7224 ** ^This interface causes the xEntryPoint() function to be invoked for 7225 ** each new [database connection] that is created. The idea here is that 7226 ** xEntryPoint() is the entry point for a statically linked [SQLite extension] 7227 ** that is to be automatically loaded into all new database connections. 7228 ** 7229 ** ^(Even though the function prototype shows that xEntryPoint() takes 7230 ** no arguments and returns void, SQLite invokes xEntryPoint() with three 7231 ** arguments and expects an integer result as if the signature of the 7232 ** entry point where as follows: 7233 ** 7234 ** <blockquote><pre> 7235 ** int xEntryPoint( 7236 ** sqlite3 *db, 7237 ** const char **pzErrMsg, 7238 ** const struct sqlite3_api_routines *pThunk 7239 ** ); 7240 ** </pre></blockquote>)^ 7241 ** 7242 ** If the xEntryPoint routine encounters an error, it should make *pzErrMsg 7243 ** point to an appropriate error message (obtained from [sqlite3_mprintf()]) 7244 ** and return an appropriate [error code]. ^SQLite ensures that *pzErrMsg 7245 ** is NULL before calling the xEntryPoint(). ^SQLite will invoke 7246 ** [sqlite3_free()] on *pzErrMsg after xEntryPoint() returns. ^If any 7247 ** xEntryPoint() returns an error, the [sqlite3_open()], [sqlite3_open16()], 7248 ** or [sqlite3_open_v2()] call that provoked the xEntryPoint() will fail. 7249 ** 7250 ** ^Calling sqlite3_auto_extension(X) with an entry point X that is already 7251 ** on the list of automatic extensions is a harmless no-op. ^No entry point 7252 ** will be called more than once for each database connection that is opened. 7253 ** 7254 ** See also: [sqlite3_reset_auto_extension()] 7255 ** and [sqlite3_cancel_auto_extension()] 7256 */ 7257 SQLITE_API int sqlite3_auto_extension(void(*xEntryPoint)(void)); 7258 7259 /* 7260 ** CAPI3REF: Cancel Automatic Extension Loading 7261 ** 7262 ** ^The [sqlite3_cancel_auto_extension(X)] interface unregisters the 7263 ** initialization routine X that was registered using a prior call to 7264 ** [sqlite3_auto_extension(X)]. ^The [sqlite3_cancel_auto_extension(X)] 7265 ** routine returns 1 if initialization routine X was successfully 7266 ** unregistered and it returns 0 if X was not on the list of initialization 7267 ** routines. 7268 */ 7269 SQLITE_API int sqlite3_cancel_auto_extension(void(*xEntryPoint)(void)); 7270 7271 /* 7272 ** CAPI3REF: Reset Automatic Extension Loading 7273 ** 7274 ** ^This interface disables all automatic extensions previously 7275 ** registered using [sqlite3_auto_extension()]. 7276 */ 7277 SQLITE_API void sqlite3_reset_auto_extension(void); 7278 7279 /* 7280 ** Structures used by the virtual table interface 7281 */ 7282 typedef struct sqlite3_vtab sqlite3_vtab; 7283 typedef struct sqlite3_index_info sqlite3_index_info; 7284 typedef struct sqlite3_vtab_cursor sqlite3_vtab_cursor; 7285 typedef struct sqlite3_module sqlite3_module; 7286 7287 /* 7288 ** CAPI3REF: Virtual Table Object 7289 ** KEYWORDS: sqlite3_module {virtual table module} 7290 ** 7291 ** This structure, sometimes called a "virtual table module", 7292 ** defines the implementation of a [virtual table]. 7293 ** This structure consists mostly of methods for the module. 7294 ** 7295 ** ^A virtual table module is created by filling in a persistent 7296 ** instance of this structure and passing a pointer to that instance 7297 ** to [sqlite3_create_module()] or [sqlite3_create_module_v2()]. 7298 ** ^The registration remains valid until it is replaced by a different 7299 ** module or until the [database connection] closes. The content 7300 ** of this structure must not change while it is registered with 7301 ** any database connection. 7302 */ 7303 struct sqlite3_module { 7304 int iVersion; 7305 int (*xCreate)(sqlite3*, void *pAux, 7306 int argc, const char *const*argv, 7307 sqlite3_vtab **ppVTab, char**); 7308 int (*xConnect)(sqlite3*, void *pAux, 7309 int argc, const char *const*argv, 7310 sqlite3_vtab **ppVTab, char**); 7311 int (*xBestIndex)(sqlite3_vtab *pVTab, sqlite3_index_info*); 7312 int (*xDisconnect)(sqlite3_vtab *pVTab); 7313 int (*xDestroy)(sqlite3_vtab *pVTab); 7314 int (*xOpen)(sqlite3_vtab *pVTab, sqlite3_vtab_cursor **ppCursor); 7315 int (*xClose)(sqlite3_vtab_cursor*); 7316 int (*xFilter)(sqlite3_vtab_cursor*, int idxNum, const char *idxStr, 7317 int argc, sqlite3_value **argv); 7318 int (*xNext)(sqlite3_vtab_cursor*); 7319 int (*xEof)(sqlite3_vtab_cursor*); 7320 int (*xColumn)(sqlite3_vtab_cursor*, sqlite3_context*, int); 7321 int (*xRowid)(sqlite3_vtab_cursor*, sqlite3_int64 *pRowid); 7322 int (*xUpdate)(sqlite3_vtab *, int, sqlite3_value **, sqlite3_int64 *); 7323 int (*xBegin)(sqlite3_vtab *pVTab); 7324 int (*xSync)(sqlite3_vtab *pVTab); 7325 int (*xCommit)(sqlite3_vtab *pVTab); 7326 int (*xRollback)(sqlite3_vtab *pVTab); 7327 int (*xFindFunction)(sqlite3_vtab *pVtab, int nArg, const char *zName, 7328 void (**pxFunc)(sqlite3_context*,int,sqlite3_value**), 7329 void **ppArg); 7330 int (*xRename)(sqlite3_vtab *pVtab, const char *zNew); 7331 /* The methods above are in version 1 of the sqlite_module object. Those 7332 ** below are for version 2 and greater. */ 7333 int (*xSavepoint)(sqlite3_vtab *pVTab, int); 7334 int (*xRelease)(sqlite3_vtab *pVTab, int); 7335 int (*xRollbackTo)(sqlite3_vtab *pVTab, int); 7336 /* The methods above are in versions 1 and 2 of the sqlite_module object. 7337 ** Those below are for version 3 and greater. */ 7338 int (*xShadowName)(const char*); 7339 /* The methods above are in versions 1 through 3 of the sqlite_module object. 7340 ** Those below are for version 4 and greater. */ 7341 int (*xIntegrity)(sqlite3_vtab *pVTab, const char *zSchema, 7342 const char *zTabName, int mFlags, char **pzErr); 7343 }; 7344 7345 /* 7346 ** CAPI3REF: Virtual Table Indexing Information 7347 ** KEYWORDS: sqlite3_index_info 7348 ** 7349 ** The sqlite3_index_info structure and its substructures is used as part 7350 ** of the [virtual table] interface to 7351 ** pass information into and receive the reply from the [xBestIndex] 7352 ** method of a [virtual table module]. The fields under **Inputs** are the 7353 ** inputs to xBestIndex and are read-only. xBestIndex inserts its 7354 ** results into the **Outputs** fields. 7355 ** 7356 ** ^(The aConstraint[] array records WHERE clause constraints of the form: 7357 ** 7358 ** <blockquote>column OP expr</blockquote> 7359 ** 7360 ** where OP is =, <, <=, >, or >=.)^ ^(The particular operator is 7361 ** stored in aConstraint[].op using one of the 7362 ** [SQLITE_INDEX_CONSTRAINT_EQ | SQLITE_INDEX_CONSTRAINT_ values].)^ 7363 ** ^(The index of the column is stored in 7364 ** aConstraint[].iColumn.)^ ^(aConstraint[].usable is TRUE if the 7365 ** expr on the right-hand side can be evaluated (and thus the constraint 7366 ** is usable) and false if it cannot.)^ 7367 ** 7368 ** ^The optimizer automatically inverts terms of the form "expr OP column" 7369 ** and makes other simplifications to the WHERE clause in an attempt to 7370 ** get as many WHERE clause terms into the form shown above as possible. 7371 ** ^The aConstraint[] array only reports WHERE clause terms that are 7372 ** relevant to the particular virtual table being queried. 7373 ** 7374 ** ^Information about the ORDER BY clause is stored in aOrderBy[]. 7375 ** ^Each term of aOrderBy records a column of the ORDER BY clause. 7376 ** 7377 ** The colUsed field indicates which columns of the virtual table may be 7378 ** required by the current scan. Virtual table columns are numbered from 7379 ** zero in the order in which they appear within the CREATE TABLE statement 7380 ** passed to sqlite3_declare_vtab(). For the first 63 columns (columns 0-62), 7381 ** the corresponding bit is set within the colUsed mask if the column may be 7382 ** required by SQLite. If the table has at least 64 columns and any column 7383 ** to the right of the first 63 is required, then bit 63 of colUsed is also 7384 ** set. In other words, column iCol may be required if the expression 7385 ** (colUsed & ((sqlite3_uint64)1 << (iCol>=63 ? 63 : iCol))) evaluates to 7386 ** non-zero. 7387 ** 7388 ** The [xBestIndex] method must fill aConstraintUsage[] with information 7389 ** about what parameters to pass to xFilter. ^If argvIndex>0 then 7390 ** the right-hand side of the corresponding aConstraint[] is evaluated 7391 ** and becomes the argvIndex-th entry in argv. ^(If aConstraintUsage[].omit 7392 ** is true, then the constraint is assumed to be fully handled by the 7393 ** virtual table and might not be checked again by the byte code.)^ ^(The 7394 ** aConstraintUsage[].omit flag is an optimization hint. When the omit flag 7395 ** is left in its default setting of false, the constraint will always be 7396 ** checked separately in byte code. If the omit flag is change to true, then 7397 ** the constraint may or may not be checked in byte code. In other words, 7398 ** when the omit flag is true there is no guarantee that the constraint will 7399 ** not be checked again using byte code.)^ 7400 ** 7401 ** ^The idxNum and idxStr values are recorded and passed into the 7402 ** [xFilter] method. 7403 ** ^[sqlite3_free()] is used to free idxStr if and only if 7404 ** needToFreeIdxStr is true. 7405 ** 7406 ** ^The orderByConsumed means that output from [xFilter]/[xNext] will occur in 7407 ** the correct order to satisfy the ORDER BY clause so that no separate 7408 ** sorting step is required. 7409 ** 7410 ** ^The estimatedCost value is an estimate of the cost of a particular 7411 ** strategy. A cost of N indicates that the cost of the strategy is similar 7412 ** to a linear scan of an SQLite table with N rows. A cost of log(N) 7413 ** indicates that the expense of the operation is similar to that of a 7414 ** binary search on a unique indexed field of an SQLite table with N rows. 7415 ** 7416 ** ^The estimatedRows value is an estimate of the number of rows that 7417 ** will be returned by the strategy. 7418 ** 7419 ** The xBestIndex method may optionally populate the idxFlags field with a 7420 ** mask of SQLITE_INDEX_SCAN_* flags. Currently there is only one such flag - 7421 ** SQLITE_INDEX_SCAN_UNIQUE. If the xBestIndex method sets this flag, SQLite 7422 ** assumes that the strategy may visit at most one row. 7423 ** 7424 ** Additionally, if xBestIndex sets the SQLITE_INDEX_SCAN_UNIQUE flag, then 7425 ** SQLite also assumes that if a call to the xUpdate() method is made as 7426 ** part of the same statement to delete or update a virtual table row and the 7427 ** implementation returns SQLITE_CONSTRAINT, then there is no need to rollback 7428 ** any database changes. In other words, if the xUpdate() returns 7429 ** SQLITE_CONSTRAINT, the database contents must be exactly as they were 7430 ** before xUpdate was called. By contrast, if SQLITE_INDEX_SCAN_UNIQUE is not 7431 ** set and xUpdate returns SQLITE_CONSTRAINT, any database changes made by 7432 ** the xUpdate method are automatically rolled back by SQLite. 7433 ** 7434 ** IMPORTANT: The estimatedRows field was added to the sqlite3_index_info 7435 ** structure for SQLite [version 3.8.2] ([dateof:3.8.2]). 7436 ** If a virtual table extension is 7437 ** used with an SQLite version earlier than 3.8.2, the results of attempting 7438 ** to read or write the estimatedRows field are undefined (but are likely 7439 ** to include crashing the application). The estimatedRows field should 7440 ** therefore only be used if [sqlite3_libversion_number()] returns a 7441 ** value greater than or equal to 3008002. Similarly, the idxFlags field 7442 ** was added for [version 3.9.0] ([dateof:3.9.0]). 7443 ** It may therefore only be used if 7444 ** sqlite3_libversion_number() returns a value greater than or equal to 7445 ** 3009000. 7446 */ 7447 struct sqlite3_index_info { 7448 /* Inputs */ 7449 int nConstraint; /* Number of entries in aConstraint */ 7450 struct sqlite3_index_constraint { 7451 int iColumn; /* Column constrained. -1 for ROWID */ 7452 unsigned char op; /* Constraint operator */ 7453 unsigned char usable; /* True if this constraint is usable */ 7454 int iTermOffset; /* Used internally - xBestIndex should ignore */ 7455 } *aConstraint; /* Table of WHERE clause constraints */ 7456 int nOrderBy; /* Number of terms in the ORDER BY clause */ 7457 struct sqlite3_index_orderby { 7458 int iColumn; /* Column number */ 7459 unsigned char desc; /* True for DESC. False for ASC. */ 7460 } *aOrderBy; /* The ORDER BY clause */ 7461 /* Outputs */ 7462 struct sqlite3_index_constraint_usage { 7463 int argvIndex; /* if >0, constraint is part of argv to xFilter */ 7464 unsigned char omit; /* Do not code a test for this constraint */ 7465 } *aConstraintUsage; 7466 int idxNum; /* Number used to identify the index */ 7467 char *idxStr; /* String, possibly obtained from sqlite3_malloc */ 7468 int needToFreeIdxStr; /* Free idxStr using sqlite3_free() if true */ 7469 int orderByConsumed; /* True if output is already ordered */ 7470 double estimatedCost; /* Estimated cost of using this index */ 7471 /* Fields below are only available in SQLite 3.8.2 and later */ 7472 sqlite3_int64 estimatedRows; /* Estimated number of rows returned */ 7473 /* Fields below are only available in SQLite 3.9.0 and later */ 7474 int idxFlags; /* Mask of SQLITE_INDEX_SCAN_* flags */ 7475 /* Fields below are only available in SQLite 3.10.0 and later */ 7476 sqlite3_uint64 colUsed; /* Input: Mask of columns used by statement */ 7477 }; 7478 7479 /* 7480 ** CAPI3REF: Virtual Table Scan Flags 7481 ** 7482 ** Virtual table implementations are allowed to set the 7483 ** [sqlite3_index_info].idxFlags field to some combination of 7484 ** these bits. 7485 */ 7486 #define SQLITE_INDEX_SCAN_UNIQUE 1 /* Scan visits at most 1 row */ 7487 7488 /* 7489 ** CAPI3REF: Virtual Table Constraint Operator Codes 7490 ** 7491 ** These macros define the allowed values for the 7492 ** [sqlite3_index_info].aConstraint[].op field. Each value represents 7493 ** an operator that is part of a constraint term in the WHERE clause of 7494 ** a query that uses a [virtual table]. 7495 ** 7496 ** ^The left-hand operand of the operator is given by the corresponding 7497 ** aConstraint[].iColumn field. ^An iColumn of -1 indicates the left-hand 7498 ** operand is the rowid. 7499 ** The SQLITE_INDEX_CONSTRAINT_LIMIT and SQLITE_INDEX_CONSTRAINT_OFFSET 7500 ** operators have no left-hand operand, and so for those operators the 7501 ** corresponding aConstraint[].iColumn is meaningless and should not be 7502 ** used. 7503 ** 7504 ** All operator values from SQLITE_INDEX_CONSTRAINT_FUNCTION through 7505 ** value 255 are reserved to represent functions that are overloaded 7506 ** by the [xFindFunction|xFindFunction method] of the virtual table 7507 ** implementation. 7508 ** 7509 ** The right-hand operands for each constraint might be accessible using 7510 ** the [sqlite3_vtab_rhs_value()] interface. Usually the right-hand 7511 ** operand is only available if it appears as a single constant literal 7512 ** in the input SQL. If the right-hand operand is another column or an 7513 ** expression (even a constant expression) or a parameter, then the 7514 ** sqlite3_vtab_rhs_value() probably will not be able to extract it. 7515 ** ^The SQLITE_INDEX_CONSTRAINT_ISNULL and 7516 ** SQLITE_INDEX_CONSTRAINT_ISNOTNULL operators have no right-hand operand 7517 ** and hence calls to sqlite3_vtab_rhs_value() for those operators will 7518 ** always return SQLITE_NOTFOUND. 7519 ** 7520 ** The collating sequence to be used for comparison can be found using 7521 ** the [sqlite3_vtab_collation()] interface. For most real-world virtual 7522 ** tables, the collating sequence of constraints does not matter (for example 7523 ** because the constraints are numeric) and so the sqlite3_vtab_collation() 7524 ** interface is not commonly needed. 7525 */ 7526 #define SQLITE_INDEX_CONSTRAINT_EQ 2 7527 #define SQLITE_INDEX_CONSTRAINT_GT 4 7528 #define SQLITE_INDEX_CONSTRAINT_LE 8 7529 #define SQLITE_INDEX_CONSTRAINT_LT 16 7530 #define SQLITE_INDEX_CONSTRAINT_GE 32 7531 #define SQLITE_INDEX_CONSTRAINT_MATCH 64 7532 #define SQLITE_INDEX_CONSTRAINT_LIKE 65 7533 #define SQLITE_INDEX_CONSTRAINT_GLOB 66 7534 #define SQLITE_INDEX_CONSTRAINT_REGEXP 67 7535 #define SQLITE_INDEX_CONSTRAINT_NE 68 7536 #define SQLITE_INDEX_CONSTRAINT_ISNOT 69 7537 #define SQLITE_INDEX_CONSTRAINT_ISNOTNULL 70 7538 #define SQLITE_INDEX_CONSTRAINT_ISNULL 71 7539 #define SQLITE_INDEX_CONSTRAINT_IS 72 7540 #define SQLITE_INDEX_CONSTRAINT_LIMIT 73 7541 #define SQLITE_INDEX_CONSTRAINT_OFFSET 74 7542 #define SQLITE_INDEX_CONSTRAINT_FUNCTION 150 7543 7544 /* 7545 ** CAPI3REF: Register A Virtual Table Implementation 7546 ** METHOD: sqlite3 7547 ** 7548 ** ^These routines are used to register a new [virtual table module] name. 7549 ** ^Module names must be registered before 7550 ** creating a new [virtual table] using the module and before using a 7551 ** preexisting [virtual table] for the module. 7552 ** 7553 ** ^The module name is registered on the [database connection] specified 7554 ** by the first parameter. ^The name of the module is given by the 7555 ** second parameter. ^The third parameter is a pointer to 7556 ** the implementation of the [virtual table module]. ^The fourth 7557 ** parameter is an arbitrary client data pointer that is passed through 7558 ** into the [xCreate] and [xConnect] methods of the virtual table module 7559 ** when a new virtual table is be being created or reinitialized. 7560 ** 7561 ** ^The sqlite3_create_module_v2() interface has a fifth parameter which 7562 ** is a pointer to a destructor for the pClientData. ^SQLite will 7563 ** invoke the destructor function (if it is not NULL) when SQLite 7564 ** no longer needs the pClientData pointer. ^The destructor will also 7565 ** be invoked if the call to sqlite3_create_module_v2() fails. 7566 ** ^The sqlite3_create_module() 7567 ** interface is equivalent to sqlite3_create_module_v2() with a NULL 7568 ** destructor. 7569 ** 7570 ** ^If the third parameter (the pointer to the sqlite3_module object) is 7571 ** NULL then no new module is created and any existing modules with the 7572 ** same name are dropped. 7573 ** 7574 ** See also: [sqlite3_drop_modules()] 7575 */ 7576 SQLITE_API int sqlite3_create_module( 7577 sqlite3 *db, /* SQLite connection to register module with */ 7578 const char *zName, /* Name of the module */ 7579 const sqlite3_module *p, /* Methods for the module */ 7580 void *pClientData /* Client data for xCreate/xConnect */ 7581 ); 7582 SQLITE_API int sqlite3_create_module_v2( 7583 sqlite3 *db, /* SQLite connection to register module with */ 7584 const char *zName, /* Name of the module */ 7585 const sqlite3_module *p, /* Methods for the module */ 7586 void *pClientData, /* Client data for xCreate/xConnect */ 7587 void(*xDestroy)(void*) /* Module destructor function */ 7588 ); 7589 7590 /* 7591 ** CAPI3REF: Remove Unnecessary Virtual Table Implementations 7592 ** METHOD: sqlite3 7593 ** 7594 ** ^The sqlite3_drop_modules(D,L) interface removes all virtual 7595 ** table modules from database connection D except those named on list L. 7596 ** The L parameter must be either NULL or a pointer to an array of pointers 7597 ** to strings where the array is terminated by a single NULL pointer. 7598 ** ^If the L parameter is NULL, then all virtual table modules are removed. 7599 ** 7600 ** See also: [sqlite3_create_module()] 7601 */ 7602 SQLITE_API int sqlite3_drop_modules( 7603 sqlite3 *db, /* Remove modules from this connection */ 7604 const char **azKeep /* Except, do not remove the ones named here */ 7605 ); 7606 7607 /* 7608 ** CAPI3REF: Virtual Table Instance Object 7609 ** KEYWORDS: sqlite3_vtab 7610 ** 7611 ** Every [virtual table module] implementation uses a subclass 7612 ** of this object to describe a particular instance 7613 ** of the [virtual table]. Each subclass will 7614 ** be tailored to the specific needs of the module implementation. 7615 ** The purpose of this superclass is to define certain fields that are 7616 ** common to all module implementations. 7617 ** 7618 ** ^Virtual tables methods can set an error message by assigning a 7619 ** string obtained from [sqlite3_mprintf()] to zErrMsg. The method should 7620 ** take care that any prior string is freed by a call to [sqlite3_free()] 7621 ** prior to assigning a new string to zErrMsg. ^After the error message 7622 ** is delivered up to the client application, the string will be automatically 7623 ** freed by sqlite3_free() and the zErrMsg field will be zeroed. 7624 */ 7625 struct sqlite3_vtab { 7626 const sqlite3_module *pModule; /* The module for this virtual table */ 7627 int nRef; /* Number of open cursors */ 7628 char *zErrMsg; /* Error message from sqlite3_mprintf() */ 7629 /* Virtual table implementations will typically add additional fields */ 7630 }; 7631 7632 /* 7633 ** CAPI3REF: Virtual Table Cursor Object 7634 ** KEYWORDS: sqlite3_vtab_cursor {virtual table cursor} 7635 ** 7636 ** Every [virtual table module] implementation uses a subclass of the 7637 ** following structure to describe cursors that point into the 7638 ** [virtual table] and are used 7639 ** to loop through the virtual table. Cursors are created using the 7640 ** [sqlite3_module.xOpen | xOpen] method of the module and are destroyed 7641 ** by the [sqlite3_module.xClose | xClose] method. Cursors are used 7642 ** by the [xFilter], [xNext], [xEof], [xColumn], and [xRowid] methods 7643 ** of the module. Each module implementation will define 7644 ** the content of a cursor structure to suit its own needs. 7645 ** 7646 ** This superclass exists in order to define fields of the cursor that 7647 ** are common to all implementations. 7648 */ 7649 struct sqlite3_vtab_cursor { 7650 sqlite3_vtab *pVtab; /* Virtual table of this cursor */ 7651 /* Virtual table implementations will typically add additional fields */ 7652 }; 7653 7654 /* 7655 ** CAPI3REF: Declare The Schema Of A Virtual Table 7656 ** 7657 ** ^The [xCreate] and [xConnect] methods of a 7658 ** [virtual table module] call this interface 7659 ** to declare the format (the names and datatypes of the columns) of 7660 ** the virtual tables they implement. 7661 */ 7662 SQLITE_API int sqlite3_declare_vtab(sqlite3*, const char *zSQL); 7663 7664 /* 7665 ** CAPI3REF: Overload A Function For A Virtual Table 7666 ** METHOD: sqlite3 7667 ** 7668 ** ^(Virtual tables can provide alternative implementations of functions 7669 ** using the [xFindFunction] method of the [virtual table module]. 7670 ** But global versions of those functions 7671 ** must exist in order to be overloaded.)^ 7672 ** 7673 ** ^(This API makes sure a global version of a function with a particular 7674 ** name and number of parameters exists. If no such function exists 7675 ** before this API is called, a new function is created.)^ ^The implementation 7676 ** of the new function always causes an exception to be thrown. So 7677 ** the new function is not good for anything by itself. Its only 7678 ** purpose is to be a placeholder function that can be overloaded 7679 ** by a [virtual table]. 7680 */ 7681 SQLITE_API int sqlite3_overload_function(sqlite3*, const char *zFuncName, int nArg); 7682 7683 /* 7684 ** CAPI3REF: A Handle To An Open BLOB 7685 ** KEYWORDS: {BLOB handle} {BLOB handles} 7686 ** 7687 ** An instance of this object represents an open BLOB on which 7688 ** [sqlite3_blob_open | incremental BLOB I/O] can be performed. 7689 ** ^Objects of this type are created by [sqlite3_blob_open()] 7690 ** and destroyed by [sqlite3_blob_close()]. 7691 ** ^The [sqlite3_blob_read()] and [sqlite3_blob_write()] interfaces 7692 ** can be used to read or write small subsections of the BLOB. 7693 ** ^The [sqlite3_blob_bytes()] interface returns the size of the BLOB in bytes. 7694 */ 7695 typedef struct sqlite3_blob sqlite3_blob; 7696 7697 /* 7698 ** CAPI3REF: Open A BLOB For Incremental I/O 7699 ** METHOD: sqlite3 7700 ** CONSTRUCTOR: sqlite3_blob 7701 ** 7702 ** ^(This interfaces opens a [BLOB handle | handle] to the BLOB located 7703 ** in row iRow, column zColumn, table zTable in database zDb; 7704 ** in other words, the same BLOB that would be selected by: 7705 ** 7706 ** <pre> 7707 ** SELECT zColumn FROM zDb.zTable WHERE [rowid] = iRow; 7708 ** </pre>)^ 7709 ** 7710 ** ^(Parameter zDb is not the filename that contains the database, but 7711 ** rather the symbolic name of the database. For attached databases, this is 7712 ** the name that appears after the AS keyword in the [ATTACH] statement. 7713 ** For the main database file, the database name is "main". For TEMP 7714 ** tables, the database name is "temp".)^ 7715 ** 7716 ** ^If the flags parameter is non-zero, then the BLOB is opened for read 7717 ** and write access. ^If the flags parameter is zero, the BLOB is opened for 7718 ** read-only access. 7719 ** 7720 ** ^(On success, [SQLITE_OK] is returned and the new [BLOB handle] is stored 7721 ** in *ppBlob. Otherwise an [error code] is returned and, unless the error 7722 ** code is SQLITE_MISUSE, *ppBlob is set to NULL.)^ ^This means that, provided 7723 ** the API is not misused, it is always safe to call [sqlite3_blob_close()] 7724 ** on *ppBlob after this function it returns. 7725 ** 7726 ** This function fails with SQLITE_ERROR if any of the following are true: 7727 ** <ul> 7728 ** <li> ^(Database zDb does not exist)^, 7729 ** <li> ^(Table zTable does not exist within database zDb)^, 7730 ** <li> ^(Table zTable is a WITHOUT ROWID table)^, 7731 ** <li> ^(Column zColumn does not exist)^, 7732 ** <li> ^(Row iRow is not present in the table)^, 7733 ** <li> ^(The specified column of row iRow contains a value that is not 7734 ** a TEXT or BLOB value)^, 7735 ** <li> ^(Column zColumn is part of an index, PRIMARY KEY or UNIQUE 7736 ** constraint and the blob is being opened for read/write access)^, 7737 ** <li> ^([foreign key constraints | Foreign key constraints] are enabled, 7738 ** column zColumn is part of a [child key] definition and the blob is 7739 ** being opened for read/write access)^. 7740 ** </ul> 7741 ** 7742 ** ^Unless it returns SQLITE_MISUSE, this function sets the 7743 ** [database connection] error code and message accessible via 7744 ** [sqlite3_errcode()] and [sqlite3_errmsg()] and related functions. 7745 ** 7746 ** A BLOB referenced by sqlite3_blob_open() may be read using the 7747 ** [sqlite3_blob_read()] interface and modified by using 7748 ** [sqlite3_blob_write()]. The [BLOB handle] can be moved to a 7749 ** different row of the same table using the [sqlite3_blob_reopen()] 7750 ** interface. However, the column, table, or database of a [BLOB handle] 7751 ** cannot be changed after the [BLOB handle] is opened. 7752 ** 7753 ** ^(If the row that a BLOB handle points to is modified by an 7754 ** [UPDATE], [DELETE], or by [ON CONFLICT] side-effects 7755 ** then the BLOB handle is marked as "expired". 7756 ** This is true if any column of the row is changed, even a column 7757 ** other than the one the BLOB handle is open on.)^ 7758 ** ^Calls to [sqlite3_blob_read()] and [sqlite3_blob_write()] for 7759 ** an expired BLOB handle fail with a return code of [SQLITE_ABORT]. 7760 ** ^(Changes written into a BLOB prior to the BLOB expiring are not 7761 ** rolled back by the expiration of the BLOB. Such changes will eventually 7762 ** commit if the transaction continues to completion.)^ 7763 ** 7764 ** ^Use the [sqlite3_blob_bytes()] interface to determine the size of 7765 ** the opened blob. ^The size of a blob may not be changed by this 7766 ** interface. Use the [UPDATE] SQL command to change the size of a 7767 ** blob. 7768 ** 7769 ** ^The [sqlite3_bind_zeroblob()] and [sqlite3_result_zeroblob()] interfaces 7770 ** and the built-in [zeroblob] SQL function may be used to create a 7771 ** zero-filled blob to read or write using the incremental-blob interface. 7772 ** 7773 ** To avoid a resource leak, every open [BLOB handle] should eventually 7774 ** be released by a call to [sqlite3_blob_close()]. 7775 ** 7776 ** See also: [sqlite3_blob_close()], 7777 ** [sqlite3_blob_reopen()], [sqlite3_blob_read()], 7778 ** [sqlite3_blob_bytes()], [sqlite3_blob_write()]. 7779 */ 7780 SQLITE_API int sqlite3_blob_open( 7781 sqlite3*, 7782 const char *zDb, 7783 const char *zTable, 7784 const char *zColumn, 7785 sqlite3_int64 iRow, 7786 int flags, 7787 sqlite3_blob **ppBlob 7788 ); 7789 7790 /* 7791 ** CAPI3REF: Move a BLOB Handle to a New Row 7792 ** METHOD: sqlite3_blob 7793 ** 7794 ** ^This function is used to move an existing [BLOB handle] so that it points 7795 ** to a different row of the same database table. ^The new row is identified 7796 ** by the rowid value passed as the second argument. Only the row can be 7797 ** changed. ^The database, table and column on which the blob handle is open 7798 ** remain the same. Moving an existing [BLOB handle] to a new row is 7799 ** faster than closing the existing handle and opening a new one. 7800 ** 7801 ** ^(The new row must meet the same criteria as for [sqlite3_blob_open()] - 7802 ** it must exist and there must be either a blob or text value stored in 7803 ** the nominated column.)^ ^If the new row is not present in the table, or if 7804 ** it does not contain a blob or text value, or if another error occurs, an 7805 ** SQLite error code is returned and the blob handle is considered aborted. 7806 ** ^All subsequent calls to [sqlite3_blob_read()], [sqlite3_blob_write()] or 7807 ** [sqlite3_blob_reopen()] on an aborted blob handle immediately return 7808 ** SQLITE_ABORT. ^Calling [sqlite3_blob_bytes()] on an aborted blob handle 7809 ** always returns zero. 7810 ** 7811 ** ^This function sets the database handle error code and message. 7812 */ 7813 SQLITE_API int sqlite3_blob_reopen(sqlite3_blob *, sqlite3_int64); 7814 7815 /* 7816 ** CAPI3REF: Close A BLOB Handle 7817 ** DESTRUCTOR: sqlite3_blob 7818 ** 7819 ** ^This function closes an open [BLOB handle]. ^(The BLOB handle is closed 7820 ** unconditionally. Even if this routine returns an error code, the 7821 ** handle is still closed.)^ 7822 ** 7823 ** ^If the blob handle being closed was opened for read-write access, and if 7824 ** the database is in auto-commit mode and there are no other open read-write 7825 ** blob handles or active write statements, the current transaction is 7826 ** committed. ^If an error occurs while committing the transaction, an error 7827 ** code is returned and the transaction rolled back. 7828 ** 7829 ** Calling this function with an argument that is not a NULL pointer or an 7830 ** open blob handle results in undefined behavior. ^Calling this routine 7831 ** with a null pointer (such as would be returned by a failed call to 7832 ** [sqlite3_blob_open()]) is a harmless no-op. ^Otherwise, if this function 7833 ** is passed a valid open blob handle, the values returned by the 7834 ** sqlite3_errcode() and sqlite3_errmsg() functions are set before returning. 7835 */ 7836 SQLITE_API int sqlite3_blob_close(sqlite3_blob *); 7837 7838 /* 7839 ** CAPI3REF: Return The Size Of An Open BLOB 7840 ** METHOD: sqlite3_blob 7841 ** 7842 ** ^Returns the size in bytes of the BLOB accessible via the 7843 ** successfully opened [BLOB handle] in its only argument. ^The 7844 ** incremental blob I/O routines can only read or overwriting existing 7845 ** blob content; they cannot change the size of a blob. 7846 ** 7847 ** This routine only works on a [BLOB handle] which has been created 7848 ** by a prior successful call to [sqlite3_blob_open()] and which has not 7849 ** been closed by [sqlite3_blob_close()]. Passing any other pointer in 7850 ** to this routine results in undefined and probably undesirable behavior. 7851 */ 7852 SQLITE_API int sqlite3_blob_bytes(sqlite3_blob *); 7853 7854 /* 7855 ** CAPI3REF: Read Data From A BLOB Incrementally 7856 ** METHOD: sqlite3_blob 7857 ** 7858 ** ^(This function is used to read data from an open [BLOB handle] into a 7859 ** caller-supplied buffer. N bytes of data are copied into buffer Z 7860 ** from the open BLOB, starting at offset iOffset.)^ 7861 ** 7862 ** ^If offset iOffset is less than N bytes from the end of the BLOB, 7863 ** [SQLITE_ERROR] is returned and no data is read. ^If N or iOffset is 7864 ** less than zero, [SQLITE_ERROR] is returned and no data is read. 7865 ** ^The size of the blob (and hence the maximum value of N+iOffset) 7866 ** can be determined using the [sqlite3_blob_bytes()] interface. 7867 ** 7868 ** ^An attempt to read from an expired [BLOB handle] fails with an 7869 ** error code of [SQLITE_ABORT]. 7870 ** 7871 ** ^(On success, sqlite3_blob_read() returns SQLITE_OK. 7872 ** Otherwise, an [error code] or an [extended error code] is returned.)^ 7873 ** 7874 ** This routine only works on a [BLOB handle] which has been created 7875 ** by a prior successful call to [sqlite3_blob_open()] and which has not 7876 ** been closed by [sqlite3_blob_close()]. Passing any other pointer in 7877 ** to this routine results in undefined and probably undesirable behavior. 7878 ** 7879 ** See also: [sqlite3_blob_write()]. 7880 */ 7881 SQLITE_API int sqlite3_blob_read(sqlite3_blob *, void *Z, int N, int iOffset); 7882 7883 /* 7884 ** CAPI3REF: Write Data Into A BLOB Incrementally 7885 ** METHOD: sqlite3_blob 7886 ** 7887 ** ^(This function is used to write data into an open [BLOB handle] from a 7888 ** caller-supplied buffer. N bytes of data are copied from the buffer Z 7889 ** into the open BLOB, starting at offset iOffset.)^ 7890 ** 7891 ** ^(On success, sqlite3_blob_write() returns SQLITE_OK. 7892 ** Otherwise, an [error code] or an [extended error code] is returned.)^ 7893 ** ^Unless SQLITE_MISUSE is returned, this function sets the 7894 ** [database connection] error code and message accessible via 7895 ** [sqlite3_errcode()] and [sqlite3_errmsg()] and related functions. 7896 ** 7897 ** ^If the [BLOB handle] passed as the first argument was not opened for 7898 ** writing (the flags parameter to [sqlite3_blob_open()] was zero), 7899 ** this function returns [SQLITE_READONLY]. 7900 ** 7901 ** This function may only modify the contents of the BLOB; it is 7902 ** not possible to increase the size of a BLOB using this API. 7903 ** ^If offset iOffset is less than N bytes from the end of the BLOB, 7904 ** [SQLITE_ERROR] is returned and no data is written. The size of the 7905 ** BLOB (and hence the maximum value of N+iOffset) can be determined 7906 ** using the [sqlite3_blob_bytes()] interface. ^If N or iOffset are less 7907 ** than zero [SQLITE_ERROR] is returned and no data is written. 7908 ** 7909 ** ^An attempt to write to an expired [BLOB handle] fails with an 7910 ** error code of [SQLITE_ABORT]. ^Writes to the BLOB that occurred 7911 ** before the [BLOB handle] expired are not rolled back by the 7912 ** expiration of the handle, though of course those changes might 7913 ** have been overwritten by the statement that expired the BLOB handle 7914 ** or by other independent statements. 7915 ** 7916 ** This routine only works on a [BLOB handle] which has been created 7917 ** by a prior successful call to [sqlite3_blob_open()] and which has not 7918 ** been closed by [sqlite3_blob_close()]. Passing any other pointer in 7919 ** to this routine results in undefined and probably undesirable behavior. 7920 ** 7921 ** See also: [sqlite3_blob_read()]. 7922 */ 7923 SQLITE_API int sqlite3_blob_write(sqlite3_blob *, const void *z, int n, int iOffset); 7924 7925 /* 7926 ** CAPI3REF: Virtual File System Objects 7927 ** 7928 ** A virtual filesystem (VFS) is an [sqlite3_vfs] object 7929 ** that SQLite uses to interact 7930 ** with the underlying operating system. Most SQLite builds come with a 7931 ** single default VFS that is appropriate for the host computer. 7932 ** New VFSes can be registered and existing VFSes can be unregistered. 7933 ** The following interfaces are provided. 7934 ** 7935 ** ^The sqlite3_vfs_find() interface returns a pointer to a VFS given its name. 7936 ** ^Names are case sensitive. 7937 ** ^Names are zero-terminated UTF-8 strings. 7938 ** ^If there is no match, a NULL pointer is returned. 7939 ** ^If zVfsName is NULL then the default VFS is returned. 7940 ** 7941 ** ^New VFSes are registered with sqlite3_vfs_register(). 7942 ** ^Each new VFS becomes the default VFS if the makeDflt flag is set. 7943 ** ^The same VFS can be registered multiple times without injury. 7944 ** ^To make an existing VFS into the default VFS, register it again 7945 ** with the makeDflt flag set. If two different VFSes with the 7946 ** same name are registered, the behavior is undefined. If a 7947 ** VFS is registered with a name that is NULL or an empty string, 7948 ** then the behavior is undefined. 7949 ** 7950 ** ^Unregister a VFS with the sqlite3_vfs_unregister() interface. 7951 ** ^(If the default VFS is unregistered, another VFS is chosen as 7952 ** the default. The choice for the new VFS is arbitrary.)^ 7953 */ 7954 SQLITE_API sqlite3_vfs *sqlite3_vfs_find(const char *zVfsName); 7955 SQLITE_API int sqlite3_vfs_register(sqlite3_vfs*, int makeDflt); 7956 SQLITE_API int sqlite3_vfs_unregister(sqlite3_vfs*); 7957 7958 /* 7959 ** CAPI3REF: Mutexes 7960 ** 7961 ** The SQLite core uses these routines for thread 7962 ** synchronization. Though they are intended for internal 7963 ** use by SQLite, code that links against SQLite is 7964 ** permitted to use any of these routines. 7965 ** 7966 ** The SQLite source code contains multiple implementations 7967 ** of these mutex routines. An appropriate implementation 7968 ** is selected automatically at compile-time. The following 7969 ** implementations are available in the SQLite core: 7970 ** 7971 ** <ul> 7972 ** <li> SQLITE_MUTEX_PTHREADS 7973 ** <li> SQLITE_MUTEX_W32 7974 ** <li> SQLITE_MUTEX_NOOP 7975 ** </ul> 7976 ** 7977 ** The SQLITE_MUTEX_NOOP implementation is a set of routines 7978 ** that does no real locking and is appropriate for use in 7979 ** a single-threaded application. The SQLITE_MUTEX_PTHREADS and 7980 ** SQLITE_MUTEX_W32 implementations are appropriate for use on Unix 7981 ** and Windows. 7982 ** 7983 ** If SQLite is compiled with the SQLITE_MUTEX_APPDEF preprocessor 7984 ** macro defined (with "-DSQLITE_MUTEX_APPDEF=1"), then no mutex 7985 ** implementation is included with the library. In this case the 7986 ** application must supply a custom mutex implementation using the 7987 ** [SQLITE_CONFIG_MUTEX] option of the sqlite3_config() function 7988 ** before calling sqlite3_initialize() or any other public sqlite3_ 7989 ** function that calls sqlite3_initialize(). 7990 ** 7991 ** ^The sqlite3_mutex_alloc() routine allocates a new 7992 ** mutex and returns a pointer to it. ^The sqlite3_mutex_alloc() 7993 ** routine returns NULL if it is unable to allocate the requested 7994 ** mutex. The argument to sqlite3_mutex_alloc() must one of these 7995 ** integer constants: 7996 ** 7997 ** <ul> 7998 ** <li> SQLITE_MUTEX_FAST 7999 ** <li> SQLITE_MUTEX_RECURSIVE 8000 ** <li> SQLITE_MUTEX_STATIC_MAIN 8001 ** <li> SQLITE_MUTEX_STATIC_MEM 8002 ** <li> SQLITE_MUTEX_STATIC_OPEN 8003 ** <li> SQLITE_MUTEX_STATIC_PRNG 8004 ** <li> SQLITE_MUTEX_STATIC_LRU 8005 ** <li> SQLITE_MUTEX_STATIC_PMEM 8006 ** <li> SQLITE_MUTEX_STATIC_APP1 8007 ** <li> SQLITE_MUTEX_STATIC_APP2 8008 ** <li> SQLITE_MUTEX_STATIC_APP3 8009 ** <li> SQLITE_MUTEX_STATIC_VFS1 8010 ** <li> SQLITE_MUTEX_STATIC_VFS2 8011 ** <li> SQLITE_MUTEX_STATIC_VFS3 8012 ** </ul> 8013 ** 8014 ** ^The first two constants (SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE) 8015 ** cause sqlite3_mutex_alloc() to create 8016 ** a new mutex. ^The new mutex is recursive when SQLITE_MUTEX_RECURSIVE 8017 ** is used but not necessarily so when SQLITE_MUTEX_FAST is used. 8018 ** The mutex implementation does not need to make a distinction 8019 ** between SQLITE_MUTEX_RECURSIVE and SQLITE_MUTEX_FAST if it does 8020 ** not want to. SQLite will only request a recursive mutex in 8021 ** cases where it really needs one. If a faster non-recursive mutex 8022 ** implementation is available on the host platform, the mutex subsystem 8023 ** might return such a mutex in response to SQLITE_MUTEX_FAST. 8024 ** 8025 ** ^The other allowed parameters to sqlite3_mutex_alloc() (anything other 8026 ** than SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE) each return 8027 ** a pointer to a static preexisting mutex. ^Nine static mutexes are 8028 ** used by the current version of SQLite. Future versions of SQLite 8029 ** may add additional static mutexes. Static mutexes are for internal 8030 ** use by SQLite only. Applications that use SQLite mutexes should 8031 ** use only the dynamic mutexes returned by SQLITE_MUTEX_FAST or 8032 ** SQLITE_MUTEX_RECURSIVE. 8033 ** 8034 ** ^Note that if one of the dynamic mutex parameters (SQLITE_MUTEX_FAST 8035 ** or SQLITE_MUTEX_RECURSIVE) is used then sqlite3_mutex_alloc() 8036 ** returns a different mutex on every call. ^For the static 8037 ** mutex types, the same mutex is returned on every call that has 8038 ** the same type number. 8039 ** 8040 ** ^The sqlite3_mutex_free() routine deallocates a previously 8041 ** allocated dynamic mutex. Attempting to deallocate a static 8042 ** mutex results in undefined behavior. 8043 ** 8044 ** ^The sqlite3_mutex_enter() and sqlite3_mutex_try() routines attempt 8045 ** to enter a mutex. ^If another thread is already within the mutex, 8046 ** sqlite3_mutex_enter() will block and sqlite3_mutex_try() will return 8047 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK] 8048 ** upon successful entry. ^(Mutexes created using 8049 ** SQLITE_MUTEX_RECURSIVE can be entered multiple times by the same thread. 8050 ** In such cases, the 8051 ** mutex must be exited an equal number of times before another thread 8052 ** can enter.)^ If the same thread tries to enter any mutex other 8053 ** than an SQLITE_MUTEX_RECURSIVE more than once, the behavior is undefined. 8054 ** 8055 ** ^(Some systems (for example, Windows 95) do not support the operation 8056 ** implemented by sqlite3_mutex_try(). On those systems, sqlite3_mutex_try() 8057 ** will always return SQLITE_BUSY. The SQLite core only ever uses 8058 ** sqlite3_mutex_try() as an optimization so this is acceptable 8059 ** behavior.)^ 8060 ** 8061 ** ^The sqlite3_mutex_leave() routine exits a mutex that was 8062 ** previously entered by the same thread. The behavior 8063 ** is undefined if the mutex is not currently entered by the 8064 ** calling thread or is not currently allocated. 8065 ** 8066 ** ^If the argument to sqlite3_mutex_enter(), sqlite3_mutex_try(), 8067 ** sqlite3_mutex_leave(), or sqlite3_mutex_free() is a NULL pointer, 8068 ** then any of the four routines behaves as a no-op. 8069 ** 8070 ** See also: [sqlite3_mutex_held()] and [sqlite3_mutex_notheld()]. 8071 */ 8072 SQLITE_API sqlite3_mutex *sqlite3_mutex_alloc(int); 8073 SQLITE_API void sqlite3_mutex_free(sqlite3_mutex*); 8074 SQLITE_API void sqlite3_mutex_enter(sqlite3_mutex*); 8075 SQLITE_API int sqlite3_mutex_try(sqlite3_mutex*); 8076 SQLITE_API void sqlite3_mutex_leave(sqlite3_mutex*); 8077 8078 /* 8079 ** CAPI3REF: Mutex Methods Object 8080 ** 8081 ** An instance of this structure defines the low-level routines 8082 ** used to allocate and use mutexes. 8083 ** 8084 ** Usually, the default mutex implementations provided by SQLite are 8085 ** sufficient, however the application has the option of substituting a custom 8086 ** implementation for specialized deployments or systems for which SQLite 8087 ** does not provide a suitable implementation. In this case, the application 8088 ** creates and populates an instance of this structure to pass 8089 ** to sqlite3_config() along with the [SQLITE_CONFIG_MUTEX] option. 8090 ** Additionally, an instance of this structure can be used as an 8091 ** output variable when querying the system for the current mutex 8092 ** implementation, using the [SQLITE_CONFIG_GETMUTEX] option. 8093 ** 8094 ** ^The xMutexInit method defined by this structure is invoked as 8095 ** part of system initialization by the sqlite3_initialize() function. 8096 ** ^The xMutexInit routine is called by SQLite exactly once for each 8097 ** effective call to [sqlite3_initialize()]. 8098 ** 8099 ** ^The xMutexEnd method defined by this structure is invoked as 8100 ** part of system shutdown by the sqlite3_shutdown() function. The 8101 ** implementation of this method is expected to release all outstanding 8102 ** resources obtained by the mutex methods implementation, especially 8103 ** those obtained by the xMutexInit method. ^The xMutexEnd() 8104 ** interface is invoked exactly once for each call to [sqlite3_shutdown()]. 8105 ** 8106 ** ^(The remaining seven methods defined by this structure (xMutexAlloc, 8107 ** xMutexFree, xMutexEnter, xMutexTry, xMutexLeave, xMutexHeld and 8108 ** xMutexNotheld) implement the following interfaces (respectively): 8109 ** 8110 ** <ul> 8111 ** <li> [sqlite3_mutex_alloc()] </li> 8112 ** <li> [sqlite3_mutex_free()] </li> 8113 ** <li> [sqlite3_mutex_enter()] </li> 8114 ** <li> [sqlite3_mutex_try()] </li> 8115 ** <li> [sqlite3_mutex_leave()] </li> 8116 ** <li> [sqlite3_mutex_held()] </li> 8117 ** <li> [sqlite3_mutex_notheld()] </li> 8118 ** </ul>)^ 8119 ** 8120 ** The only difference is that the public sqlite3_XXX functions enumerated 8121 ** above silently ignore any invocations that pass a NULL pointer instead 8122 ** of a valid mutex handle. The implementations of the methods defined 8123 ** by this structure are not required to handle this case. The results 8124 ** of passing a NULL pointer instead of a valid mutex handle are undefined 8125 ** (i.e. it is acceptable to provide an implementation that segfaults if 8126 ** it is passed a NULL pointer). 8127 ** 8128 ** The xMutexInit() method must be threadsafe. It must be harmless to 8129 ** invoke xMutexInit() multiple times within the same process and without 8130 ** intervening calls to xMutexEnd(). Second and subsequent calls to 8131 ** xMutexInit() must be no-ops. 8132 ** 8133 ** xMutexInit() must not use SQLite memory allocation ([sqlite3_malloc()] 8134 ** and its associates). Similarly, xMutexAlloc() must not use SQLite memory 8135 ** allocation for a static mutex. ^However xMutexAlloc() may use SQLite 8136 ** memory allocation for a fast or recursive mutex. 8137 ** 8138 ** ^SQLite will invoke the xMutexEnd() method when [sqlite3_shutdown()] is 8139 ** called, but only if the prior call to xMutexInit returned SQLITE_OK. 8140 ** If xMutexInit fails in any way, it is expected to clean up after itself 8141 ** prior to returning. 8142 */ 8143 typedef struct sqlite3_mutex_methods sqlite3_mutex_methods; 8144 struct sqlite3_mutex_methods { 8145 int (*xMutexInit)(void); 8146 int (*xMutexEnd)(void); 8147 sqlite3_mutex *(*xMutexAlloc)(int); 8148 void (*xMutexFree)(sqlite3_mutex *); 8149 void (*xMutexEnter)(sqlite3_mutex *); 8150 int (*xMutexTry)(sqlite3_mutex *); 8151 void (*xMutexLeave)(sqlite3_mutex *); 8152 int (*xMutexHeld)(sqlite3_mutex *); 8153 int (*xMutexNotheld)(sqlite3_mutex *); 8154 }; 8155 8156 /* 8157 ** CAPI3REF: Mutex Verification Routines 8158 ** 8159 ** The sqlite3_mutex_held() and sqlite3_mutex_notheld() routines 8160 ** are intended for use inside assert() statements. The SQLite core 8161 ** never uses these routines except inside an assert() and applications 8162 ** are advised to follow the lead of the core. The SQLite core only 8163 ** provides implementations for these routines when it is compiled 8164 ** with the SQLITE_DEBUG flag. External mutex implementations 8165 ** are only required to provide these routines if SQLITE_DEBUG is 8166 ** defined and if NDEBUG is not defined. 8167 ** 8168 ** These routines should return true if the mutex in their argument 8169 ** is held or not held, respectively, by the calling thread. 8170 ** 8171 ** The implementation is not required to provide versions of these 8172 ** routines that actually work. If the implementation does not provide working 8173 ** versions of these routines, it should at least provide stubs that always 8174 ** return true so that one does not get spurious assertion failures. 8175 ** 8176 ** If the argument to sqlite3_mutex_held() is a NULL pointer then 8177 ** the routine should return 1. This seems counter-intuitive since 8178 ** clearly the mutex cannot be held if it does not exist. But 8179 ** the reason the mutex does not exist is because the build is not 8180 ** using mutexes. And we do not want the assert() containing the 8181 ** call to sqlite3_mutex_held() to fail, so a non-zero return is 8182 ** the appropriate thing to do. The sqlite3_mutex_notheld() 8183 ** interface should also return 1 when given a NULL pointer. 8184 */ 8185 #ifndef NDEBUG 8186 SQLITE_API int sqlite3_mutex_held(sqlite3_mutex*); 8187 SQLITE_API int sqlite3_mutex_notheld(sqlite3_mutex*); 8188 #endif 8189 8190 /* 8191 ** CAPI3REF: Mutex Types 8192 ** 8193 ** The [sqlite3_mutex_alloc()] interface takes a single argument 8194 ** which is one of these integer constants. 8195 ** 8196 ** The set of static mutexes may change from one SQLite release to the 8197 ** next. Applications that override the built-in mutex logic must be 8198 ** prepared to accommodate additional static mutexes. 8199 */ 8200 #define SQLITE_MUTEX_FAST 0 8201 #define SQLITE_MUTEX_RECURSIVE 1 8202 #define SQLITE_MUTEX_STATIC_MAIN 2 8203 #define SQLITE_MUTEX_STATIC_MEM 3 /* sqlite3_malloc() */ 8204 #define SQLITE_MUTEX_STATIC_MEM2 4 /* NOT USED */ 8205 #define SQLITE_MUTEX_STATIC_OPEN 4 /* sqlite3BtreeOpen() */ 8206 #define SQLITE_MUTEX_STATIC_PRNG 5 /* sqlite3_randomness() */ 8207 #define SQLITE_MUTEX_STATIC_LRU 6 /* lru page list */ 8208 #define SQLITE_MUTEX_STATIC_LRU2 7 /* NOT USED */ 8209 #define SQLITE_MUTEX_STATIC_PMEM 7 /* sqlite3PageMalloc() */ 8210 #define SQLITE_MUTEX_STATIC_APP1 8 /* For use by application */ 8211 #define SQLITE_MUTEX_STATIC_APP2 9 /* For use by application */ 8212 #define SQLITE_MUTEX_STATIC_APP3 10 /* For use by application */ 8213 #define SQLITE_MUTEX_STATIC_VFS1 11 /* For use by built-in VFS */ 8214 #define SQLITE_MUTEX_STATIC_VFS2 12 /* For use by extension VFS */ 8215 #define SQLITE_MUTEX_STATIC_VFS3 13 /* For use by application VFS */ 8216 8217 /* Legacy compatibility: */ 8218 #define SQLITE_MUTEX_STATIC_MASTER 2 8219 8220 8221 /* 8222 ** CAPI3REF: Retrieve the mutex for a database connection 8223 ** METHOD: sqlite3 8224 ** 8225 ** ^This interface returns a pointer the [sqlite3_mutex] object that 8226 ** serializes access to the [database connection] given in the argument 8227 ** when the [threading mode] is Serialized. 8228 ** ^If the [threading mode] is Single-thread or Multi-thread then this 8229 ** routine returns a NULL pointer. 8230 */ 8231 SQLITE_API sqlite3_mutex *sqlite3_db_mutex(sqlite3*); 8232 8233 /* 8234 ** CAPI3REF: Low-Level Control Of Database Files 8235 ** METHOD: sqlite3 8236 ** KEYWORDS: {file control} 8237 ** 8238 ** ^The [sqlite3_file_control()] interface makes a direct call to the 8239 ** xFileControl method for the [sqlite3_io_methods] object associated 8240 ** with a particular database identified by the second argument. ^The 8241 ** name of the database is "main" for the main database or "temp" for the 8242 ** TEMP database, or the name that appears after the AS keyword for 8243 ** databases that are added using the [ATTACH] SQL command. 8244 ** ^A NULL pointer can be used in place of "main" to refer to the 8245 ** main database file. 8246 ** ^The third and fourth parameters to this routine 8247 ** are passed directly through to the second and third parameters of 8248 ** the xFileControl method. ^The return value of the xFileControl 8249 ** method becomes the return value of this routine. 8250 ** 8251 ** A few opcodes for [sqlite3_file_control()] are handled directly 8252 ** by the SQLite core and never invoke the 8253 ** sqlite3_io_methods.xFileControl method. 8254 ** ^The [SQLITE_FCNTL_FILE_POINTER] value for the op parameter causes 8255 ** a pointer to the underlying [sqlite3_file] object to be written into 8256 ** the space pointed to by the 4th parameter. The 8257 ** [SQLITE_FCNTL_JOURNAL_POINTER] works similarly except that it returns 8258 ** the [sqlite3_file] object associated with the journal file instead of 8259 ** the main database. The [SQLITE_FCNTL_VFS_POINTER] opcode returns 8260 ** a pointer to the underlying [sqlite3_vfs] object for the file. 8261 ** The [SQLITE_FCNTL_DATA_VERSION] returns the data version counter 8262 ** from the pager. 8263 ** 8264 ** ^If the second parameter (zDbName) does not match the name of any 8265 ** open database file, then SQLITE_ERROR is returned. ^This error 8266 ** code is not remembered and will not be recalled by [sqlite3_errcode()] 8267 ** or [sqlite3_errmsg()]. The underlying xFileControl method might 8268 ** also return SQLITE_ERROR. There is no way to distinguish between 8269 ** an incorrect zDbName and an SQLITE_ERROR return from the underlying 8270 ** xFileControl method. 8271 ** 8272 ** See also: [file control opcodes] 8273 */ 8274 SQLITE_API int sqlite3_file_control(sqlite3*, const char *zDbName, int op, void*); 8275 8276 /* 8277 ** CAPI3REF: Testing Interface 8278 ** 8279 ** ^The sqlite3_test_control() interface is used to read out internal 8280 ** state of SQLite and to inject faults into SQLite for testing 8281 ** purposes. ^The first parameter is an operation code that determines 8282 ** the number, meaning, and operation of all subsequent parameters. 8283 ** 8284 ** This interface is not for use by applications. It exists solely 8285 ** for verifying the correct operation of the SQLite library. Depending 8286 ** on how the SQLite library is compiled, this interface might not exist. 8287 ** 8288 ** The details of the operation codes, their meanings, the parameters 8289 ** they take, and what they do are all subject to change without notice. 8290 ** Unlike most of the SQLite API, this function is not guaranteed to 8291 ** operate consistently from one release to the next. 8292 */ 8293 SQLITE_API int sqlite3_test_control(int op, ...); 8294 8295 /* 8296 ** CAPI3REF: Testing Interface Operation Codes 8297 ** 8298 ** These constants are the valid operation code parameters used 8299 ** as the first argument to [sqlite3_test_control()]. 8300 ** 8301 ** These parameters and their meanings are subject to change 8302 ** without notice. These values are for testing purposes only. 8303 ** Applications should not use any of these parameters or the 8304 ** [sqlite3_test_control()] interface. 8305 */ 8306 #define SQLITE_TESTCTRL_FIRST 5 8307 #define SQLITE_TESTCTRL_PRNG_SAVE 5 8308 #define SQLITE_TESTCTRL_PRNG_RESTORE 6 8309 #define SQLITE_TESTCTRL_PRNG_RESET 7 /* NOT USED */ 8310 #define SQLITE_TESTCTRL_FK_NO_ACTION 7 8311 #define SQLITE_TESTCTRL_BITVEC_TEST 8 8312 #define SQLITE_TESTCTRL_FAULT_INSTALL 9 8313 #define SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS 10 8314 #define SQLITE_TESTCTRL_PENDING_BYTE 11 8315 #define SQLITE_TESTCTRL_ASSERT 12 8316 #define SQLITE_TESTCTRL_ALWAYS 13 8317 #define SQLITE_TESTCTRL_RESERVE 14 /* NOT USED */ 8318 #define SQLITE_TESTCTRL_OPTIMIZATIONS 15 8319 #define SQLITE_TESTCTRL_ISKEYWORD 16 /* NOT USED */ 8320 #define SQLITE_TESTCTRL_SCRATCHMALLOC 17 /* NOT USED */ 8321 #define SQLITE_TESTCTRL_INTERNAL_FUNCTIONS 17 8322 #define SQLITE_TESTCTRL_LOCALTIME_FAULT 18 8323 #define SQLITE_TESTCTRL_EXPLAIN_STMT 19 /* NOT USED */ 8324 #define SQLITE_TESTCTRL_ONCE_RESET_THRESHOLD 19 8325 #define SQLITE_TESTCTRL_NEVER_CORRUPT 20 8326 #define SQLITE_TESTCTRL_VDBE_COVERAGE 21 8327 #define SQLITE_TESTCTRL_BYTEORDER 22 8328 #define SQLITE_TESTCTRL_ISINIT 23 8329 #define SQLITE_TESTCTRL_SORTER_MMAP 24 8330 #define SQLITE_TESTCTRL_IMPOSTER 25 8331 #define SQLITE_TESTCTRL_PARSER_COVERAGE 26 8332 #define SQLITE_TESTCTRL_RESULT_INTREAL 27 8333 #define SQLITE_TESTCTRL_PRNG_SEED 28 8334 #define SQLITE_TESTCTRL_EXTRA_SCHEMA_CHECKS 29 8335 #define SQLITE_TESTCTRL_SEEK_COUNT 30 8336 #define SQLITE_TESTCTRL_TRACEFLAGS 31 8337 #define SQLITE_TESTCTRL_TUNE 32 8338 #define SQLITE_TESTCTRL_LOGEST 33 8339 #define SQLITE_TESTCTRL_USELONGDOUBLE 34 8340 #define SQLITE_TESTCTRL_LAST 34 /* Largest TESTCTRL */ 8341 8342 /* 8343 ** CAPI3REF: SQL Keyword Checking 8344 ** 8345 ** These routines provide access to the set of SQL language keywords 8346 ** recognized by SQLite. Applications can uses these routines to determine 8347 ** whether or not a specific identifier needs to be escaped (for example, 8348 ** by enclosing in double-quotes) so as not to confuse the parser. 8349 ** 8350 ** The sqlite3_keyword_count() interface returns the number of distinct 8351 ** keywords understood by SQLite. 8352 ** 8353 ** The sqlite3_keyword_name(N,Z,L) interface finds the N-th keyword and 8354 ** makes *Z point to that keyword expressed as UTF8 and writes the number 8355 ** of bytes in the keyword into *L. The string that *Z points to is not 8356 ** zero-terminated. The sqlite3_keyword_name(N,Z,L) routine returns 8357 ** SQLITE_OK if N is within bounds and SQLITE_ERROR if not. If either Z 8358 ** or L are NULL or invalid pointers then calls to 8359 ** sqlite3_keyword_name(N,Z,L) result in undefined behavior. 8360 ** 8361 ** The sqlite3_keyword_check(Z,L) interface checks to see whether or not 8362 ** the L-byte UTF8 identifier that Z points to is a keyword, returning non-zero 8363 ** if it is and zero if not. 8364 ** 8365 ** The parser used by SQLite is forgiving. It is often possible to use 8366 ** a keyword as an identifier as long as such use does not result in a 8367 ** parsing ambiguity. For example, the statement 8368 ** "CREATE TABLE BEGIN(REPLACE,PRAGMA,END);" is accepted by SQLite, and 8369 ** creates a new table named "BEGIN" with three columns named 8370 ** "REPLACE", "PRAGMA", and "END". Nevertheless, best practice is to avoid 8371 ** using keywords as identifiers. Common techniques used to avoid keyword 8372 ** name collisions include: 8373 ** <ul> 8374 ** <li> Put all identifier names inside double-quotes. This is the official 8375 ** SQL way to escape identifier names. 8376 ** <li> Put identifier names inside [...]. This is not standard SQL, 8377 ** but it is what SQL Server does and so lots of programmers use this 8378 ** technique. 8379 ** <li> Begin every identifier with the letter "Z" as no SQL keywords start 8380 ** with "Z". 8381 ** <li> Include a digit somewhere in every identifier name. 8382 ** </ul> 8383 ** 8384 ** Note that the number of keywords understood by SQLite can depend on 8385 ** compile-time options. For example, "VACUUM" is not a keyword if 8386 ** SQLite is compiled with the [-DSQLITE_OMIT_VACUUM] option. Also, 8387 ** new keywords may be added to future releases of SQLite. 8388 */ 8389 SQLITE_API int sqlite3_keyword_count(void); 8390 SQLITE_API int sqlite3_keyword_name(int,const char**,int*); 8391 SQLITE_API int sqlite3_keyword_check(const char*,int); 8392 8393 /* 8394 ** CAPI3REF: Dynamic String Object 8395 ** KEYWORDS: {dynamic string} 8396 ** 8397 ** An instance of the sqlite3_str object contains a dynamically-sized 8398 ** string under construction. 8399 ** 8400 ** The lifecycle of an sqlite3_str object is as follows: 8401 ** <ol> 8402 ** <li> ^The sqlite3_str object is created using [sqlite3_str_new()]. 8403 ** <li> ^Text is appended to the sqlite3_str object using various 8404 ** methods, such as [sqlite3_str_appendf()]. 8405 ** <li> ^The sqlite3_str object is destroyed and the string it created 8406 ** is returned using the [sqlite3_str_finish()] interface. 8407 ** </ol> 8408 */ 8409 typedef struct sqlite3_str sqlite3_str; 8410 8411 /* 8412 ** CAPI3REF: Create A New Dynamic String Object 8413 ** CONSTRUCTOR: sqlite3_str 8414 ** 8415 ** ^The [sqlite3_str_new(D)] interface allocates and initializes 8416 ** a new [sqlite3_str] object. To avoid memory leaks, the object returned by 8417 ** [sqlite3_str_new()] must be freed by a subsequent call to 8418 ** [sqlite3_str_finish(X)]. 8419 ** 8420 ** ^The [sqlite3_str_new(D)] interface always returns a pointer to a 8421 ** valid [sqlite3_str] object, though in the event of an out-of-memory 8422 ** error the returned object might be a special singleton that will 8423 ** silently reject new text, always return SQLITE_NOMEM from 8424 ** [sqlite3_str_errcode()], always return 0 for 8425 ** [sqlite3_str_length()], and always return NULL from 8426 ** [sqlite3_str_finish(X)]. It is always safe to use the value 8427 ** returned by [sqlite3_str_new(D)] as the sqlite3_str parameter 8428 ** to any of the other [sqlite3_str] methods. 8429 ** 8430 ** The D parameter to [sqlite3_str_new(D)] may be NULL. If the 8431 ** D parameter in [sqlite3_str_new(D)] is not NULL, then the maximum 8432 ** length of the string contained in the [sqlite3_str] object will be 8433 ** the value set for [sqlite3_limit](D,[SQLITE_LIMIT_LENGTH]) instead 8434 ** of [SQLITE_MAX_LENGTH]. 8435 */ 8436 SQLITE_API sqlite3_str *sqlite3_str_new(sqlite3*); 8437 8438 /* 8439 ** CAPI3REF: Finalize A Dynamic String 8440 ** DESTRUCTOR: sqlite3_str 8441 ** 8442 ** ^The [sqlite3_str_finish(X)] interface destroys the sqlite3_str object X 8443 ** and returns a pointer to a memory buffer obtained from [sqlite3_malloc64()] 8444 ** that contains the constructed string. The calling application should 8445 ** pass the returned value to [sqlite3_free()] to avoid a memory leak. 8446 ** ^The [sqlite3_str_finish(X)] interface may return a NULL pointer if any 8447 ** errors were encountered during construction of the string. ^The 8448 ** [sqlite3_str_finish(X)] interface will also return a NULL pointer if the 8449 ** string in [sqlite3_str] object X is zero bytes long. 8450 */ 8451 SQLITE_API char *sqlite3_str_finish(sqlite3_str*); 8452 8453 /* 8454 ** CAPI3REF: Add Content To A Dynamic String 8455 ** METHOD: sqlite3_str 8456 ** 8457 ** These interfaces add content to an sqlite3_str object previously obtained 8458 ** from [sqlite3_str_new()]. 8459 ** 8460 ** ^The [sqlite3_str_appendf(X,F,...)] and 8461 ** [sqlite3_str_vappendf(X,F,V)] interfaces uses the [built-in printf] 8462 ** functionality of SQLite to append formatted text onto the end of 8463 ** [sqlite3_str] object X. 8464 ** 8465 ** ^The [sqlite3_str_append(X,S,N)] method appends exactly N bytes from string S 8466 ** onto the end of the [sqlite3_str] object X. N must be non-negative. 8467 ** S must contain at least N non-zero bytes of content. To append a 8468 ** zero-terminated string in its entirety, use the [sqlite3_str_appendall()] 8469 ** method instead. 8470 ** 8471 ** ^The [sqlite3_str_appendall(X,S)] method appends the complete content of 8472 ** zero-terminated string S onto the end of [sqlite3_str] object X. 8473 ** 8474 ** ^The [sqlite3_str_appendchar(X,N,C)] method appends N copies of the 8475 ** single-byte character C onto the end of [sqlite3_str] object X. 8476 ** ^This method can be used, for example, to add whitespace indentation. 8477 ** 8478 ** ^The [sqlite3_str_reset(X)] method resets the string under construction 8479 ** inside [sqlite3_str] object X back to zero bytes in length. 8480 ** 8481 ** These methods do not return a result code. ^If an error occurs, that fact 8482 ** is recorded in the [sqlite3_str] object and can be recovered by a 8483 ** subsequent call to [sqlite3_str_errcode(X)]. 8484 */ 8485 SQLITE_API void sqlite3_str_appendf(sqlite3_str*, const char *zFormat, ...); 8486 SQLITE_API void sqlite3_str_vappendf(sqlite3_str*, const char *zFormat, va_list); 8487 SQLITE_API void sqlite3_str_append(sqlite3_str*, const char *zIn, int N); 8488 SQLITE_API void sqlite3_str_appendall(sqlite3_str*, const char *zIn); 8489 SQLITE_API void sqlite3_str_appendchar(sqlite3_str*, int N, char C); 8490 SQLITE_API void sqlite3_str_reset(sqlite3_str*); 8491 8492 /* 8493 ** CAPI3REF: Status Of A Dynamic String 8494 ** METHOD: sqlite3_str 8495 ** 8496 ** These interfaces return the current status of an [sqlite3_str] object. 8497 ** 8498 ** ^If any prior errors have occurred while constructing the dynamic string 8499 ** in sqlite3_str X, then the [sqlite3_str_errcode(X)] method will return 8500 ** an appropriate error code. ^The [sqlite3_str_errcode(X)] method returns 8501 ** [SQLITE_NOMEM] following any out-of-memory error, or 8502 ** [SQLITE_TOOBIG] if the size of the dynamic string exceeds 8503 ** [SQLITE_MAX_LENGTH], or [SQLITE_OK] if there have been no errors. 8504 ** 8505 ** ^The [sqlite3_str_length(X)] method returns the current length, in bytes, 8506 ** of the dynamic string under construction in [sqlite3_str] object X. 8507 ** ^The length returned by [sqlite3_str_length(X)] does not include the 8508 ** zero-termination byte. 8509 ** 8510 ** ^The [sqlite3_str_value(X)] method returns a pointer to the current 8511 ** content of the dynamic string under construction in X. The value 8512 ** returned by [sqlite3_str_value(X)] is managed by the sqlite3_str object X 8513 ** and might be freed or altered by any subsequent method on the same 8514 ** [sqlite3_str] object. Applications must not used the pointer returned 8515 ** [sqlite3_str_value(X)] after any subsequent method call on the same 8516 ** object. ^Applications may change the content of the string returned 8517 ** by [sqlite3_str_value(X)] as long as they do not write into any bytes 8518 ** outside the range of 0 to [sqlite3_str_length(X)] and do not read or 8519 ** write any byte after any subsequent sqlite3_str method call. 8520 */ 8521 SQLITE_API int sqlite3_str_errcode(sqlite3_str*); 8522 SQLITE_API int sqlite3_str_length(sqlite3_str*); 8523 SQLITE_API char *sqlite3_str_value(sqlite3_str*); 8524 8525 /* 8526 ** CAPI3REF: SQLite Runtime Status 8527 ** 8528 ** ^These interfaces are used to retrieve runtime status information 8529 ** about the performance of SQLite, and optionally to reset various 8530 ** highwater marks. ^The first argument is an integer code for 8531 ** the specific parameter to measure. ^(Recognized integer codes 8532 ** are of the form [status parameters | SQLITE_STATUS_...].)^ 8533 ** ^The current value of the parameter is returned into *pCurrent. 8534 ** ^The highest recorded value is returned in *pHighwater. ^If the 8535 ** resetFlag is true, then the highest record value is reset after 8536 ** *pHighwater is written. ^(Some parameters do not record the highest 8537 ** value. For those parameters 8538 ** nothing is written into *pHighwater and the resetFlag is ignored.)^ 8539 ** ^(Other parameters record only the highwater mark and not the current 8540 ** value. For these latter parameters nothing is written into *pCurrent.)^ 8541 ** 8542 ** ^The sqlite3_status() and sqlite3_status64() routines return 8543 ** SQLITE_OK on success and a non-zero [error code] on failure. 8544 ** 8545 ** If either the current value or the highwater mark is too large to 8546 ** be represented by a 32-bit integer, then the values returned by 8547 ** sqlite3_status() are undefined. 8548 ** 8549 ** See also: [sqlite3_db_status()] 8550 */ 8551 SQLITE_API int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetFlag); 8552 SQLITE_API int sqlite3_status64( 8553 int op, 8554 sqlite3_int64 *pCurrent, 8555 sqlite3_int64 *pHighwater, 8556 int resetFlag 8557 ); 8558 8559 8560 /* 8561 ** CAPI3REF: Status Parameters 8562 ** KEYWORDS: {status parameters} 8563 ** 8564 ** These integer constants designate various run-time status parameters 8565 ** that can be returned by [sqlite3_status()]. 8566 ** 8567 ** <dl> 8568 ** [[SQLITE_STATUS_MEMORY_USED]] ^(<dt>SQLITE_STATUS_MEMORY_USED</dt> 8569 ** <dd>This parameter is the current amount of memory checked out 8570 ** using [sqlite3_malloc()], either directly or indirectly. The 8571 ** figure includes calls made to [sqlite3_malloc()] by the application 8572 ** and internal memory usage by the SQLite library. Auxiliary page-cache 8573 ** memory controlled by [SQLITE_CONFIG_PAGECACHE] is not included in 8574 ** this parameter. The amount returned is the sum of the allocation 8575 ** sizes as reported by the xSize method in [sqlite3_mem_methods].</dd>)^ 8576 ** 8577 ** [[SQLITE_STATUS_MALLOC_SIZE]] ^(<dt>SQLITE_STATUS_MALLOC_SIZE</dt> 8578 ** <dd>This parameter records the largest memory allocation request 8579 ** handed to [sqlite3_malloc()] or [sqlite3_realloc()] (or their 8580 ** internal equivalents). Only the value returned in the 8581 ** *pHighwater parameter to [sqlite3_status()] is of interest. 8582 ** The value written into the *pCurrent parameter is undefined.</dd>)^ 8583 ** 8584 ** [[SQLITE_STATUS_MALLOC_COUNT]] ^(<dt>SQLITE_STATUS_MALLOC_COUNT</dt> 8585 ** <dd>This parameter records the number of separate memory allocations 8586 ** currently checked out.</dd>)^ 8587 ** 8588 ** [[SQLITE_STATUS_PAGECACHE_USED]] ^(<dt>SQLITE_STATUS_PAGECACHE_USED</dt> 8589 ** <dd>This parameter returns the number of pages used out of the 8590 ** [pagecache memory allocator] that was configured using 8591 ** [SQLITE_CONFIG_PAGECACHE]. The 8592 ** value returned is in pages, not in bytes.</dd>)^ 8593 ** 8594 ** [[SQLITE_STATUS_PAGECACHE_OVERFLOW]] 8595 ** ^(<dt>SQLITE_STATUS_PAGECACHE_OVERFLOW</dt> 8596 ** <dd>This parameter returns the number of bytes of page cache 8597 ** allocation which could not be satisfied by the [SQLITE_CONFIG_PAGECACHE] 8598 ** buffer and where forced to overflow to [sqlite3_malloc()]. The 8599 ** returned value includes allocations that overflowed because they 8600 ** where too large (they were larger than the "sz" parameter to 8601 ** [SQLITE_CONFIG_PAGECACHE]) and allocations that overflowed because 8602 ** no space was left in the page cache.</dd>)^ 8603 ** 8604 ** [[SQLITE_STATUS_PAGECACHE_SIZE]] ^(<dt>SQLITE_STATUS_PAGECACHE_SIZE</dt> 8605 ** <dd>This parameter records the largest memory allocation request 8606 ** handed to the [pagecache memory allocator]. Only the value returned in the 8607 ** *pHighwater parameter to [sqlite3_status()] is of interest. 8608 ** The value written into the *pCurrent parameter is undefined.</dd>)^ 8609 ** 8610 ** [[SQLITE_STATUS_SCRATCH_USED]] <dt>SQLITE_STATUS_SCRATCH_USED</dt> 8611 ** <dd>No longer used.</dd> 8612 ** 8613 ** [[SQLITE_STATUS_SCRATCH_OVERFLOW]] ^(<dt>SQLITE_STATUS_SCRATCH_OVERFLOW</dt> 8614 ** <dd>No longer used.</dd> 8615 ** 8616 ** [[SQLITE_STATUS_SCRATCH_SIZE]] <dt>SQLITE_STATUS_SCRATCH_SIZE</dt> 8617 ** <dd>No longer used.</dd> 8618 ** 8619 ** [[SQLITE_STATUS_PARSER_STACK]] ^(<dt>SQLITE_STATUS_PARSER_STACK</dt> 8620 ** <dd>The *pHighwater parameter records the deepest parser stack. 8621 ** The *pCurrent value is undefined. The *pHighwater value is only 8622 ** meaningful if SQLite is compiled with [YYTRACKMAXSTACKDEPTH].</dd>)^ 8623 ** </dl> 8624 ** 8625 ** New status parameters may be added from time to time. 8626 */ 8627 #define SQLITE_STATUS_MEMORY_USED 0 8628 #define SQLITE_STATUS_PAGECACHE_USED 1 8629 #define SQLITE_STATUS_PAGECACHE_OVERFLOW 2 8630 #define SQLITE_STATUS_SCRATCH_USED 3 /* NOT USED */ 8631 #define SQLITE_STATUS_SCRATCH_OVERFLOW 4 /* NOT USED */ 8632 #define SQLITE_STATUS_MALLOC_SIZE 5 8633 #define SQLITE_STATUS_PARSER_STACK 6 8634 #define SQLITE_STATUS_PAGECACHE_SIZE 7 8635 #define SQLITE_STATUS_SCRATCH_SIZE 8 /* NOT USED */ 8636 #define SQLITE_STATUS_MALLOC_COUNT 9 8637 8638 /* 8639 ** CAPI3REF: Database Connection Status 8640 ** METHOD: sqlite3 8641 ** 8642 ** ^This interface is used to retrieve runtime status information 8643 ** about a single [database connection]. ^The first argument is the 8644 ** database connection object to be interrogated. ^The second argument 8645 ** is an integer constant, taken from the set of 8646 ** [SQLITE_DBSTATUS options], that 8647 ** determines the parameter to interrogate. The set of 8648 ** [SQLITE_DBSTATUS options] is likely 8649 ** to grow in future releases of SQLite. 8650 ** 8651 ** ^The current value of the requested parameter is written into *pCur 8652 ** and the highest instantaneous value is written into *pHiwtr. ^If 8653 ** the resetFlg is true, then the highest instantaneous value is 8654 ** reset back down to the current value. 8655 ** 8656 ** ^The sqlite3_db_status() routine returns SQLITE_OK on success and a 8657 ** non-zero [error code] on failure. 8658 ** 8659 ** See also: [sqlite3_status()] and [sqlite3_stmt_status()]. 8660 */ 8661 SQLITE_API int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int resetFlg); 8662 8663 /* 8664 ** CAPI3REF: Status Parameters for database connections 8665 ** KEYWORDS: {SQLITE_DBSTATUS options} 8666 ** 8667 ** These constants are the available integer "verbs" that can be passed as 8668 ** the second argument to the [sqlite3_db_status()] interface. 8669 ** 8670 ** New verbs may be added in future releases of SQLite. Existing verbs 8671 ** might be discontinued. Applications should check the return code from 8672 ** [sqlite3_db_status()] to make sure that the call worked. 8673 ** The [sqlite3_db_status()] interface will return a non-zero error code 8674 ** if a discontinued or unsupported verb is invoked. 8675 ** 8676 ** <dl> 8677 ** [[SQLITE_DBSTATUS_LOOKASIDE_USED]] ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_USED</dt> 8678 ** <dd>This parameter returns the number of lookaside memory slots currently 8679 ** checked out.</dd>)^ 8680 ** 8681 ** [[SQLITE_DBSTATUS_LOOKASIDE_HIT]] ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_HIT</dt> 8682 ** <dd>This parameter returns the number of malloc attempts that were 8683 ** satisfied using lookaside memory. Only the high-water value is meaningful; 8684 ** the current value is always zero.)^ 8685 ** 8686 ** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE]] 8687 ** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE</dt> 8688 ** <dd>This parameter returns the number malloc attempts that might have 8689 ** been satisfied using lookaside memory but failed due to the amount of 8690 ** memory requested being larger than the lookaside slot size. 8691 ** Only the high-water value is meaningful; 8692 ** the current value is always zero.)^ 8693 ** 8694 ** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL]] 8695 ** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL</dt> 8696 ** <dd>This parameter returns the number malloc attempts that might have 8697 ** been satisfied using lookaside memory but failed due to all lookaside 8698 ** memory already being in use. 8699 ** Only the high-water value is meaningful; 8700 ** the current value is always zero.)^ 8701 ** 8702 ** [[SQLITE_DBSTATUS_CACHE_USED]] ^(<dt>SQLITE_DBSTATUS_CACHE_USED</dt> 8703 ** <dd>This parameter returns the approximate number of bytes of heap 8704 ** memory used by all pager caches associated with the database connection.)^ 8705 ** ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_USED is always 0. 8706 ** 8707 ** [[SQLITE_DBSTATUS_CACHE_USED_SHARED]] 8708 ** ^(<dt>SQLITE_DBSTATUS_CACHE_USED_SHARED</dt> 8709 ** <dd>This parameter is similar to DBSTATUS_CACHE_USED, except that if a 8710 ** pager cache is shared between two or more connections the bytes of heap 8711 ** memory used by that pager cache is divided evenly between the attached 8712 ** connections.)^ In other words, if none of the pager caches associated 8713 ** with the database connection are shared, this request returns the same 8714 ** value as DBSTATUS_CACHE_USED. Or, if one or more or the pager caches are 8715 ** shared, the value returned by this call will be smaller than that returned 8716 ** by DBSTATUS_CACHE_USED. ^The highwater mark associated with 8717 ** SQLITE_DBSTATUS_CACHE_USED_SHARED is always 0. 8718 ** 8719 ** [[SQLITE_DBSTATUS_SCHEMA_USED]] ^(<dt>SQLITE_DBSTATUS_SCHEMA_USED</dt> 8720 ** <dd>This parameter returns the approximate number of bytes of heap 8721 ** memory used to store the schema for all databases associated 8722 ** with the connection - main, temp, and any [ATTACH]-ed databases.)^ 8723 ** ^The full amount of memory used by the schemas is reported, even if the 8724 ** schema memory is shared with other database connections due to 8725 ** [shared cache mode] being enabled. 8726 ** ^The highwater mark associated with SQLITE_DBSTATUS_SCHEMA_USED is always 0. 8727 ** 8728 ** [[SQLITE_DBSTATUS_STMT_USED]] ^(<dt>SQLITE_DBSTATUS_STMT_USED</dt> 8729 ** <dd>This parameter returns the approximate number of bytes of heap 8730 ** and lookaside memory used by all prepared statements associated with 8731 ** the database connection.)^ 8732 ** ^The highwater mark associated with SQLITE_DBSTATUS_STMT_USED is always 0. 8733 ** </dd> 8734 ** 8735 ** [[SQLITE_DBSTATUS_CACHE_HIT]] ^(<dt>SQLITE_DBSTATUS_CACHE_HIT</dt> 8736 ** <dd>This parameter returns the number of pager cache hits that have 8737 ** occurred.)^ ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_HIT 8738 ** is always 0. 8739 ** </dd> 8740 ** 8741 ** [[SQLITE_DBSTATUS_CACHE_MISS]] ^(<dt>SQLITE_DBSTATUS_CACHE_MISS</dt> 8742 ** <dd>This parameter returns the number of pager cache misses that have 8743 ** occurred.)^ ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_MISS 8744 ** is always 0. 8745 ** </dd> 8746 ** 8747 ** [[SQLITE_DBSTATUS_CACHE_WRITE]] ^(<dt>SQLITE_DBSTATUS_CACHE_WRITE</dt> 8748 ** <dd>This parameter returns the number of dirty cache entries that have 8749 ** been written to disk. Specifically, the number of pages written to the 8750 ** wal file in wal mode databases, or the number of pages written to the 8751 ** database file in rollback mode databases. Any pages written as part of 8752 ** transaction rollback or database recovery operations are not included. 8753 ** If an IO or other error occurs while writing a page to disk, the effect 8754 ** on subsequent SQLITE_DBSTATUS_CACHE_WRITE requests is undefined.)^ ^The 8755 ** highwater mark associated with SQLITE_DBSTATUS_CACHE_WRITE is always 0. 8756 ** </dd> 8757 ** 8758 ** [[SQLITE_DBSTATUS_CACHE_SPILL]] ^(<dt>SQLITE_DBSTATUS_CACHE_SPILL</dt> 8759 ** <dd>This parameter returns the number of dirty cache entries that have 8760 ** been written to disk in the middle of a transaction due to the page 8761 ** cache overflowing. Transactions are more efficient if they are written 8762 ** to disk all at once. When pages spill mid-transaction, that introduces 8763 ** additional overhead. This parameter can be used help identify 8764 ** inefficiencies that can be resolved by increasing the cache size. 8765 ** </dd> 8766 ** 8767 ** [[SQLITE_DBSTATUS_DEFERRED_FKS]] ^(<dt>SQLITE_DBSTATUS_DEFERRED_FKS</dt> 8768 ** <dd>This parameter returns zero for the current value if and only if 8769 ** all foreign key constraints (deferred or immediate) have been 8770 ** resolved.)^ ^The highwater mark is always 0. 8771 ** </dd> 8772 ** </dl> 8773 */ 8774 #define SQLITE_DBSTATUS_LOOKASIDE_USED 0 8775 #define SQLITE_DBSTATUS_CACHE_USED 1 8776 #define SQLITE_DBSTATUS_SCHEMA_USED 2 8777 #define SQLITE_DBSTATUS_STMT_USED 3 8778 #define SQLITE_DBSTATUS_LOOKASIDE_HIT 4 8779 #define SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE 5 8780 #define SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL 6 8781 #define SQLITE_DBSTATUS_CACHE_HIT 7 8782 #define SQLITE_DBSTATUS_CACHE_MISS 8 8783 #define SQLITE_DBSTATUS_CACHE_WRITE 9 8784 #define SQLITE_DBSTATUS_DEFERRED_FKS 10 8785 #define SQLITE_DBSTATUS_CACHE_USED_SHARED 11 8786 #define SQLITE_DBSTATUS_CACHE_SPILL 12 8787 #define SQLITE_DBSTATUS_MAX 12 /* Largest defined DBSTATUS */ 8788 8789 8790 /* 8791 ** CAPI3REF: Prepared Statement Status 8792 ** METHOD: sqlite3_stmt 8793 ** 8794 ** ^(Each prepared statement maintains various 8795 ** [SQLITE_STMTSTATUS counters] that measure the number 8796 ** of times it has performed specific operations.)^ These counters can 8797 ** be used to monitor the performance characteristics of the prepared 8798 ** statements. For example, if the number of table steps greatly exceeds 8799 ** the number of table searches or result rows, that would tend to indicate 8800 ** that the prepared statement is using a full table scan rather than 8801 ** an index. 8802 ** 8803 ** ^(This interface is used to retrieve and reset counter values from 8804 ** a [prepared statement]. The first argument is the prepared statement 8805 ** object to be interrogated. The second argument 8806 ** is an integer code for a specific [SQLITE_STMTSTATUS counter] 8807 ** to be interrogated.)^ 8808 ** ^The current value of the requested counter is returned. 8809 ** ^If the resetFlg is true, then the counter is reset to zero after this 8810 ** interface call returns. 8811 ** 8812 ** See also: [sqlite3_status()] and [sqlite3_db_status()]. 8813 */ 8814 SQLITE_API int sqlite3_stmt_status(sqlite3_stmt*, int op,int resetFlg); 8815 8816 /* 8817 ** CAPI3REF: Status Parameters for prepared statements 8818 ** KEYWORDS: {SQLITE_STMTSTATUS counter} {SQLITE_STMTSTATUS counters} 8819 ** 8820 ** These preprocessor macros define integer codes that name counter 8821 ** values associated with the [sqlite3_stmt_status()] interface. 8822 ** The meanings of the various counters are as follows: 8823 ** 8824 ** <dl> 8825 ** [[SQLITE_STMTSTATUS_FULLSCAN_STEP]] <dt>SQLITE_STMTSTATUS_FULLSCAN_STEP</dt> 8826 ** <dd>^This is the number of times that SQLite has stepped forward in 8827 ** a table as part of a full table scan. Large numbers for this counter 8828 ** may indicate opportunities for performance improvement through 8829 ** careful use of indices.</dd> 8830 ** 8831 ** [[SQLITE_STMTSTATUS_SORT]] <dt>SQLITE_STMTSTATUS_SORT</dt> 8832 ** <dd>^This is the number of sort operations that have occurred. 8833 ** A non-zero value in this counter may indicate an opportunity to 8834 ** improvement performance through careful use of indices.</dd> 8835 ** 8836 ** [[SQLITE_STMTSTATUS_AUTOINDEX]] <dt>SQLITE_STMTSTATUS_AUTOINDEX</dt> 8837 ** <dd>^This is the number of rows inserted into transient indices that 8838 ** were created automatically in order to help joins run faster. 8839 ** A non-zero value in this counter may indicate an opportunity to 8840 ** improvement performance by adding permanent indices that do not 8841 ** need to be reinitialized each time the statement is run.</dd> 8842 ** 8843 ** [[SQLITE_STMTSTATUS_VM_STEP]] <dt>SQLITE_STMTSTATUS_VM_STEP</dt> 8844 ** <dd>^This is the number of virtual machine operations executed 8845 ** by the prepared statement if that number is less than or equal 8846 ** to 2147483647. The number of virtual machine operations can be 8847 ** used as a proxy for the total work done by the prepared statement. 8848 ** If the number of virtual machine operations exceeds 2147483647 8849 ** then the value returned by this statement status code is undefined. 8850 ** 8851 ** [[SQLITE_STMTSTATUS_REPREPARE]] <dt>SQLITE_STMTSTATUS_REPREPARE</dt> 8852 ** <dd>^This is the number of times that the prepare statement has been 8853 ** automatically regenerated due to schema changes or changes to 8854 ** [bound parameters] that might affect the query plan. 8855 ** 8856 ** [[SQLITE_STMTSTATUS_RUN]] <dt>SQLITE_STMTSTATUS_RUN</dt> 8857 ** <dd>^This is the number of times that the prepared statement has 8858 ** been run. A single "run" for the purposes of this counter is one 8859 ** or more calls to [sqlite3_step()] followed by a call to [sqlite3_reset()]. 8860 ** The counter is incremented on the first [sqlite3_step()] call of each 8861 ** cycle. 8862 ** 8863 ** [[SQLITE_STMTSTATUS_FILTER_MISS]] 8864 ** [[SQLITE_STMTSTATUS_FILTER HIT]] 8865 ** <dt>SQLITE_STMTSTATUS_FILTER_HIT<br> 8866 ** SQLITE_STMTSTATUS_FILTER_MISS</dt> 8867 ** <dd>^SQLITE_STMTSTATUS_FILTER_HIT is the number of times that a join 8868 ** step was bypassed because a Bloom filter returned not-found. The 8869 ** corresponding SQLITE_STMTSTATUS_FILTER_MISS value is the number of 8870 ** times that the Bloom filter returned a find, and thus the join step 8871 ** had to be processed as normal. 8872 ** 8873 ** [[SQLITE_STMTSTATUS_MEMUSED]] <dt>SQLITE_STMTSTATUS_MEMUSED</dt> 8874 ** <dd>^This is the approximate number of bytes of heap memory 8875 ** used to store the prepared statement. ^This value is not actually 8876 ** a counter, and so the resetFlg parameter to sqlite3_stmt_status() 8877 ** is ignored when the opcode is SQLITE_STMTSTATUS_MEMUSED. 8878 ** </dd> 8879 ** </dl> 8880 */ 8881 #define SQLITE_STMTSTATUS_FULLSCAN_STEP 1 8882 #define SQLITE_STMTSTATUS_SORT 2 8883 #define SQLITE_STMTSTATUS_AUTOINDEX 3 8884 #define SQLITE_STMTSTATUS_VM_STEP 4 8885 #define SQLITE_STMTSTATUS_REPREPARE 5 8886 #define SQLITE_STMTSTATUS_RUN 6 8887 #define SQLITE_STMTSTATUS_FILTER_MISS 7 8888 #define SQLITE_STMTSTATUS_FILTER_HIT 8 8889 #define SQLITE_STMTSTATUS_MEMUSED 99 8890 8891 /* 8892 ** CAPI3REF: Custom Page Cache Object 8893 ** 8894 ** The sqlite3_pcache type is opaque. It is implemented by 8895 ** the pluggable module. The SQLite core has no knowledge of 8896 ** its size or internal structure and never deals with the 8897 ** sqlite3_pcache object except by holding and passing pointers 8898 ** to the object. 8899 ** 8900 ** See [sqlite3_pcache_methods2] for additional information. 8901 */ 8902 typedef struct sqlite3_pcache sqlite3_pcache; 8903 8904 /* 8905 ** CAPI3REF: Custom Page Cache Object 8906 ** 8907 ** The sqlite3_pcache_page object represents a single page in the 8908 ** page cache. The page cache will allocate instances of this 8909 ** object. Various methods of the page cache use pointers to instances 8910 ** of this object as parameters or as their return value. 8911 ** 8912 ** See [sqlite3_pcache_methods2] for additional information. 8913 */ 8914 typedef struct sqlite3_pcache_page sqlite3_pcache_page; 8915 struct sqlite3_pcache_page { 8916 void *pBuf; /* The content of the page */ 8917 void *pExtra; /* Extra information associated with the page */ 8918 }; 8919 8920 /* 8921 ** CAPI3REF: Application Defined Page Cache. 8922 ** KEYWORDS: {page cache} 8923 ** 8924 ** ^(The [sqlite3_config]([SQLITE_CONFIG_PCACHE2], ...) interface can 8925 ** register an alternative page cache implementation by passing in an 8926 ** instance of the sqlite3_pcache_methods2 structure.)^ 8927 ** In many applications, most of the heap memory allocated by 8928 ** SQLite is used for the page cache. 8929 ** By implementing a 8930 ** custom page cache using this API, an application can better control 8931 ** the amount of memory consumed by SQLite, the way in which 8932 ** that memory is allocated and released, and the policies used to 8933 ** determine exactly which parts of a database file are cached and for 8934 ** how long. 8935 ** 8936 ** The alternative page cache mechanism is an 8937 ** extreme measure that is only needed by the most demanding applications. 8938 ** The built-in page cache is recommended for most uses. 8939 ** 8940 ** ^(The contents of the sqlite3_pcache_methods2 structure are copied to an 8941 ** internal buffer by SQLite within the call to [sqlite3_config]. Hence 8942 ** the application may discard the parameter after the call to 8943 ** [sqlite3_config()] returns.)^ 8944 ** 8945 ** [[the xInit() page cache method]] 8946 ** ^(The xInit() method is called once for each effective 8947 ** call to [sqlite3_initialize()])^ 8948 ** (usually only once during the lifetime of the process). ^(The xInit() 8949 ** method is passed a copy of the sqlite3_pcache_methods2.pArg value.)^ 8950 ** The intent of the xInit() method is to set up global data structures 8951 ** required by the custom page cache implementation. 8952 ** ^(If the xInit() method is NULL, then the 8953 ** built-in default page cache is used instead of the application defined 8954 ** page cache.)^ 8955 ** 8956 ** [[the xShutdown() page cache method]] 8957 ** ^The xShutdown() method is called by [sqlite3_shutdown()]. 8958 ** It can be used to clean up 8959 ** any outstanding resources before process shutdown, if required. 8960 ** ^The xShutdown() method may be NULL. 8961 ** 8962 ** ^SQLite automatically serializes calls to the xInit method, 8963 ** so the xInit method need not be threadsafe. ^The 8964 ** xShutdown method is only called from [sqlite3_shutdown()] so it does 8965 ** not need to be threadsafe either. All other methods must be threadsafe 8966 ** in multithreaded applications. 8967 ** 8968 ** ^SQLite will never invoke xInit() more than once without an intervening 8969 ** call to xShutdown(). 8970 ** 8971 ** [[the xCreate() page cache methods]] 8972 ** ^SQLite invokes the xCreate() method to construct a new cache instance. 8973 ** SQLite will typically create one cache instance for each open database file, 8974 ** though this is not guaranteed. ^The 8975 ** first parameter, szPage, is the size in bytes of the pages that must 8976 ** be allocated by the cache. ^szPage will always a power of two. ^The 8977 ** second parameter szExtra is a number of bytes of extra storage 8978 ** associated with each page cache entry. ^The szExtra parameter will 8979 ** a number less than 250. SQLite will use the 8980 ** extra szExtra bytes on each page to store metadata about the underlying 8981 ** database page on disk. The value passed into szExtra depends 8982 ** on the SQLite version, the target platform, and how SQLite was compiled. 8983 ** ^The third argument to xCreate(), bPurgeable, is true if the cache being 8984 ** created will be used to cache database pages of a file stored on disk, or 8985 ** false if it is used for an in-memory database. The cache implementation 8986 ** does not have to do anything special based with the value of bPurgeable; 8987 ** it is purely advisory. ^On a cache where bPurgeable is false, SQLite will 8988 ** never invoke xUnpin() except to deliberately delete a page. 8989 ** ^In other words, calls to xUnpin() on a cache with bPurgeable set to 8990 ** false will always have the "discard" flag set to true. 8991 ** ^Hence, a cache created with bPurgeable false will 8992 ** never contain any unpinned pages. 8993 ** 8994 ** [[the xCachesize() page cache method]] 8995 ** ^(The xCachesize() method may be called at any time by SQLite to set the 8996 ** suggested maximum cache-size (number of pages stored by) the cache 8997 ** instance passed as the first argument. This is the value configured using 8998 ** the SQLite "[PRAGMA cache_size]" command.)^ As with the bPurgeable 8999 ** parameter, the implementation is not required to do anything with this 9000 ** value; it is advisory only. 9001 ** 9002 ** [[the xPagecount() page cache methods]] 9003 ** The xPagecount() method must return the number of pages currently 9004 ** stored in the cache, both pinned and unpinned. 9005 ** 9006 ** [[the xFetch() page cache methods]] 9007 ** The xFetch() method locates a page in the cache and returns a pointer to 9008 ** an sqlite3_pcache_page object associated with that page, or a NULL pointer. 9009 ** The pBuf element of the returned sqlite3_pcache_page object will be a 9010 ** pointer to a buffer of szPage bytes used to store the content of a 9011 ** single database page. The pExtra element of sqlite3_pcache_page will be 9012 ** a pointer to the szExtra bytes of extra storage that SQLite has requested 9013 ** for each entry in the page cache. 9014 ** 9015 ** The page to be fetched is determined by the key. ^The minimum key value 9016 ** is 1. After it has been retrieved using xFetch, the page is considered 9017 ** to be "pinned". 9018 ** 9019 ** If the requested page is already in the page cache, then the page cache 9020 ** implementation must return a pointer to the page buffer with its content 9021 ** intact. If the requested page is not already in the cache, then the 9022 ** cache implementation should use the value of the createFlag 9023 ** parameter to help it determined what action to take: 9024 ** 9025 ** <table border=1 width=85% align=center> 9026 ** <tr><th> createFlag <th> Behavior when page is not already in cache 9027 ** <tr><td> 0 <td> Do not allocate a new page. Return NULL. 9028 ** <tr><td> 1 <td> Allocate a new page if it easy and convenient to do so. 9029 ** Otherwise return NULL. 9030 ** <tr><td> 2 <td> Make every effort to allocate a new page. Only return 9031 ** NULL if allocating a new page is effectively impossible. 9032 ** </table> 9033 ** 9034 ** ^(SQLite will normally invoke xFetch() with a createFlag of 0 or 1. SQLite 9035 ** will only use a createFlag of 2 after a prior call with a createFlag of 1 9036 ** failed.)^ In between the xFetch() calls, SQLite may 9037 ** attempt to unpin one or more cache pages by spilling the content of 9038 ** pinned pages to disk and synching the operating system disk cache. 9039 ** 9040 ** [[the xUnpin() page cache method]] 9041 ** ^xUnpin() is called by SQLite with a pointer to a currently pinned page 9042 ** as its second argument. If the third parameter, discard, is non-zero, 9043 ** then the page must be evicted from the cache. 9044 ** ^If the discard parameter is 9045 ** zero, then the page may be discarded or retained at the discretion of 9046 ** page cache implementation. ^The page cache implementation 9047 ** may choose to evict unpinned pages at any time. 9048 ** 9049 ** The cache must not perform any reference counting. A single 9050 ** call to xUnpin() unpins the page regardless of the number of prior calls 9051 ** to xFetch(). 9052 ** 9053 ** [[the xRekey() page cache methods]] 9054 ** The xRekey() method is used to change the key value associated with the 9055 ** page passed as the second argument. If the cache 9056 ** previously contains an entry associated with newKey, it must be 9057 ** discarded. ^Any prior cache entry associated with newKey is guaranteed not 9058 ** to be pinned. 9059 ** 9060 ** When SQLite calls the xTruncate() method, the cache must discard all 9061 ** existing cache entries with page numbers (keys) greater than or equal 9062 ** to the value of the iLimit parameter passed to xTruncate(). If any 9063 ** of these pages are pinned, they are implicitly unpinned, meaning that 9064 ** they can be safely discarded. 9065 ** 9066 ** [[the xDestroy() page cache method]] 9067 ** ^The xDestroy() method is used to delete a cache allocated by xCreate(). 9068 ** All resources associated with the specified cache should be freed. ^After 9069 ** calling the xDestroy() method, SQLite considers the [sqlite3_pcache*] 9070 ** handle invalid, and will not use it with any other sqlite3_pcache_methods2 9071 ** functions. 9072 ** 9073 ** [[the xShrink() page cache method]] 9074 ** ^SQLite invokes the xShrink() method when it wants the page cache to 9075 ** free up as much of heap memory as possible. The page cache implementation 9076 ** is not obligated to free any memory, but well-behaved implementations should 9077 ** do their best. 9078 */ 9079 typedef struct sqlite3_pcache_methods2 sqlite3_pcache_methods2; 9080 struct sqlite3_pcache_methods2 { 9081 int iVersion; 9082 void *pArg; 9083 int (*xInit)(void*); 9084 void (*xShutdown)(void*); 9085 sqlite3_pcache *(*xCreate)(int szPage, int szExtra, int bPurgeable); 9086 void (*xCachesize)(sqlite3_pcache*, int nCachesize); 9087 int (*xPagecount)(sqlite3_pcache*); 9088 sqlite3_pcache_page *(*xFetch)(sqlite3_pcache*, unsigned key, int createFlag); 9089 void (*xUnpin)(sqlite3_pcache*, sqlite3_pcache_page*, int discard); 9090 void (*xRekey)(sqlite3_pcache*, sqlite3_pcache_page*, 9091 unsigned oldKey, unsigned newKey); 9092 void (*xTruncate)(sqlite3_pcache*, unsigned iLimit); 9093 void (*xDestroy)(sqlite3_pcache*); 9094 void (*xShrink)(sqlite3_pcache*); 9095 }; 9096 9097 /* 9098 ** This is the obsolete pcache_methods object that has now been replaced 9099 ** by sqlite3_pcache_methods2. This object is not used by SQLite. It is 9100 ** retained in the header file for backwards compatibility only. 9101 */ 9102 typedef struct sqlite3_pcache_methods sqlite3_pcache_methods; 9103 struct sqlite3_pcache_methods { 9104 void *pArg; 9105 int (*xInit)(void*); 9106 void (*xShutdown)(void*); 9107 sqlite3_pcache *(*xCreate)(int szPage, int bPurgeable); 9108 void (*xCachesize)(sqlite3_pcache*, int nCachesize); 9109 int (*xPagecount)(sqlite3_pcache*); 9110 void *(*xFetch)(sqlite3_pcache*, unsigned key, int createFlag); 9111 void (*xUnpin)(sqlite3_pcache*, void*, int discard); 9112 void (*xRekey)(sqlite3_pcache*, void*, unsigned oldKey, unsigned newKey); 9113 void (*xTruncate)(sqlite3_pcache*, unsigned iLimit); 9114 void (*xDestroy)(sqlite3_pcache*); 9115 }; 9116 9117 9118 /* 9119 ** CAPI3REF: Online Backup Object 9120 ** 9121 ** The sqlite3_backup object records state information about an ongoing 9122 ** online backup operation. ^The sqlite3_backup object is created by 9123 ** a call to [sqlite3_backup_init()] and is destroyed by a call to 9124 ** [sqlite3_backup_finish()]. 9125 ** 9126 ** See Also: [Using the SQLite Online Backup API] 9127 */ 9128 typedef struct sqlite3_backup sqlite3_backup; 9129 9130 /* 9131 ** CAPI3REF: Online Backup API. 9132 ** 9133 ** The backup API copies the content of one database into another. 9134 ** It is useful either for creating backups of databases or 9135 ** for copying in-memory databases to or from persistent files. 9136 ** 9137 ** See Also: [Using the SQLite Online Backup API] 9138 ** 9139 ** ^SQLite holds a write transaction open on the destination database file 9140 ** for the duration of the backup operation. 9141 ** ^The source database is read-locked only while it is being read; 9142 ** it is not locked continuously for the entire backup operation. 9143 ** ^Thus, the backup may be performed on a live source database without 9144 ** preventing other database connections from 9145 ** reading or writing to the source database while the backup is underway. 9146 ** 9147 ** ^(To perform a backup operation: 9148 ** <ol> 9149 ** <li><b>sqlite3_backup_init()</b> is called once to initialize the 9150 ** backup, 9151 ** <li><b>sqlite3_backup_step()</b> is called one or more times to transfer 9152 ** the data between the two databases, and finally 9153 ** <li><b>sqlite3_backup_finish()</b> is called to release all resources 9154 ** associated with the backup operation. 9155 ** </ol>)^ 9156 ** There should be exactly one call to sqlite3_backup_finish() for each 9157 ** successful call to sqlite3_backup_init(). 9158 ** 9159 ** [[sqlite3_backup_init()]] <b>sqlite3_backup_init()</b> 9160 ** 9161 ** ^The D and N arguments to sqlite3_backup_init(D,N,S,M) are the 9162 ** [database connection] associated with the destination database 9163 ** and the database name, respectively. 9164 ** ^The database name is "main" for the main database, "temp" for the 9165 ** temporary database, or the name specified after the AS keyword in 9166 ** an [ATTACH] statement for an attached database. 9167 ** ^The S and M arguments passed to 9168 ** sqlite3_backup_init(D,N,S,M) identify the [database connection] 9169 ** and database name of the source database, respectively. 9170 ** ^The source and destination [database connections] (parameters S and D) 9171 ** must be different or else sqlite3_backup_init(D,N,S,M) will fail with 9172 ** an error. 9173 ** 9174 ** ^A call to sqlite3_backup_init() will fail, returning NULL, if 9175 ** there is already a read or read-write transaction open on the 9176 ** destination database. 9177 ** 9178 ** ^If an error occurs within sqlite3_backup_init(D,N,S,M), then NULL is 9179 ** returned and an error code and error message are stored in the 9180 ** destination [database connection] D. 9181 ** ^The error code and message for the failed call to sqlite3_backup_init() 9182 ** can be retrieved using the [sqlite3_errcode()], [sqlite3_errmsg()], and/or 9183 ** [sqlite3_errmsg16()] functions. 9184 ** ^A successful call to sqlite3_backup_init() returns a pointer to an 9185 ** [sqlite3_backup] object. 9186 ** ^The [sqlite3_backup] object may be used with the sqlite3_backup_step() and 9187 ** sqlite3_backup_finish() functions to perform the specified backup 9188 ** operation. 9189 ** 9190 ** [[sqlite3_backup_step()]] <b>sqlite3_backup_step()</b> 9191 ** 9192 ** ^Function sqlite3_backup_step(B,N) will copy up to N pages between 9193 ** the source and destination databases specified by [sqlite3_backup] object B. 9194 ** ^If N is negative, all remaining source pages are copied. 9195 ** ^If sqlite3_backup_step(B,N) successfully copies N pages and there 9196 ** are still more pages to be copied, then the function returns [SQLITE_OK]. 9197 ** ^If sqlite3_backup_step(B,N) successfully finishes copying all pages 9198 ** from source to destination, then it returns [SQLITE_DONE]. 9199 ** ^If an error occurs while running sqlite3_backup_step(B,N), 9200 ** then an [error code] is returned. ^As well as [SQLITE_OK] and 9201 ** [SQLITE_DONE], a call to sqlite3_backup_step() may return [SQLITE_READONLY], 9202 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an 9203 ** [SQLITE_IOERR_ACCESS | SQLITE_IOERR_XXX] extended error code. 9204 ** 9205 ** ^(The sqlite3_backup_step() might return [SQLITE_READONLY] if 9206 ** <ol> 9207 ** <li> the destination database was opened read-only, or 9208 ** <li> the destination database is using write-ahead-log journaling 9209 ** and the destination and source page sizes differ, or 9210 ** <li> the destination database is an in-memory database and the 9211 ** destination and source page sizes differ. 9212 ** </ol>)^ 9213 ** 9214 ** ^If sqlite3_backup_step() cannot obtain a required file-system lock, then 9215 ** the [sqlite3_busy_handler | busy-handler function] 9216 ** is invoked (if one is specified). ^If the 9217 ** busy-handler returns non-zero before the lock is available, then 9218 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to 9219 ** sqlite3_backup_step() can be retried later. ^If the source 9220 ** [database connection] 9221 ** is being used to write to the source database when sqlite3_backup_step() 9222 ** is called, then [SQLITE_LOCKED] is returned immediately. ^Again, in this 9223 ** case the call to sqlite3_backup_step() can be retried later on. ^(If 9224 ** [SQLITE_IOERR_ACCESS | SQLITE_IOERR_XXX], [SQLITE_NOMEM], or 9225 ** [SQLITE_READONLY] is returned, then 9226 ** there is no point in retrying the call to sqlite3_backup_step(). These 9227 ** errors are considered fatal.)^ The application must accept 9228 ** that the backup operation has failed and pass the backup operation handle 9229 ** to the sqlite3_backup_finish() to release associated resources. 9230 ** 9231 ** ^The first call to sqlite3_backup_step() obtains an exclusive lock 9232 ** on the destination file. ^The exclusive lock is not released until either 9233 ** sqlite3_backup_finish() is called or the backup operation is complete 9234 ** and sqlite3_backup_step() returns [SQLITE_DONE]. ^Every call to 9235 ** sqlite3_backup_step() obtains a [shared lock] on the source database that 9236 ** lasts for the duration of the sqlite3_backup_step() call. 9237 ** ^Because the source database is not locked between calls to 9238 ** sqlite3_backup_step(), the source database may be modified mid-way 9239 ** through the backup process. ^If the source database is modified by an 9240 ** external process or via a database connection other than the one being 9241 ** used by the backup operation, then the backup will be automatically 9242 ** restarted by the next call to sqlite3_backup_step(). ^If the source 9243 ** database is modified by the using the same database connection as is used 9244 ** by the backup operation, then the backup database is automatically 9245 ** updated at the same time. 9246 ** 9247 ** [[sqlite3_backup_finish()]] <b>sqlite3_backup_finish()</b> 9248 ** 9249 ** When sqlite3_backup_step() has returned [SQLITE_DONE], or when the 9250 ** application wishes to abandon the backup operation, the application 9251 ** should destroy the [sqlite3_backup] by passing it to sqlite3_backup_finish(). 9252 ** ^The sqlite3_backup_finish() interfaces releases all 9253 ** resources associated with the [sqlite3_backup] object. 9254 ** ^If sqlite3_backup_step() has not yet returned [SQLITE_DONE], then any 9255 ** active write-transaction on the destination database is rolled back. 9256 ** The [sqlite3_backup] object is invalid 9257 ** and may not be used following a call to sqlite3_backup_finish(). 9258 ** 9259 ** ^The value returned by sqlite3_backup_finish is [SQLITE_OK] if no 9260 ** sqlite3_backup_step() errors occurred, regardless or whether or not 9261 ** sqlite3_backup_step() completed. 9262 ** ^If an out-of-memory condition or IO error occurred during any prior 9263 ** sqlite3_backup_step() call on the same [sqlite3_backup] object, then 9264 ** sqlite3_backup_finish() returns the corresponding [error code]. 9265 ** 9266 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step() 9267 ** is not a permanent error and does not affect the return value of 9268 ** sqlite3_backup_finish(). 9269 ** 9270 ** [[sqlite3_backup_remaining()]] [[sqlite3_backup_pagecount()]] 9271 ** <b>sqlite3_backup_remaining() and sqlite3_backup_pagecount()</b> 9272 ** 9273 ** ^The sqlite3_backup_remaining() routine returns the number of pages still 9274 ** to be backed up at the conclusion of the most recent sqlite3_backup_step(). 9275 ** ^The sqlite3_backup_pagecount() routine returns the total number of pages 9276 ** in the source database at the conclusion of the most recent 9277 ** sqlite3_backup_step(). 9278 ** ^(The values returned by these functions are only updated by 9279 ** sqlite3_backup_step(). If the source database is modified in a way that 9280 ** changes the size of the source database or the number of pages remaining, 9281 ** those changes are not reflected in the output of sqlite3_backup_pagecount() 9282 ** and sqlite3_backup_remaining() until after the next 9283 ** sqlite3_backup_step().)^ 9284 ** 9285 ** <b>Concurrent Usage of Database Handles</b> 9286 ** 9287 ** ^The source [database connection] may be used by the application for other 9288 ** purposes while a backup operation is underway or being initialized. 9289 ** ^If SQLite is compiled and configured to support threadsafe database 9290 ** connections, then the source database connection may be used concurrently 9291 ** from within other threads. 9292 ** 9293 ** However, the application must guarantee that the destination 9294 ** [database connection] is not passed to any other API (by any thread) after 9295 ** sqlite3_backup_init() is called and before the corresponding call to 9296 ** sqlite3_backup_finish(). SQLite does not currently check to see 9297 ** if the application incorrectly accesses the destination [database connection] 9298 ** and so no error code is reported, but the operations may malfunction 9299 ** nevertheless. Use of the destination database connection while a 9300 ** backup is in progress might also cause a mutex deadlock. 9301 ** 9302 ** If running in [shared cache mode], the application must 9303 ** guarantee that the shared cache used by the destination database 9304 ** is not accessed while the backup is running. In practice this means 9305 ** that the application must guarantee that the disk file being 9306 ** backed up to is not accessed by any connection within the process, 9307 ** not just the specific connection that was passed to sqlite3_backup_init(). 9308 ** 9309 ** The [sqlite3_backup] object itself is partially threadsafe. Multiple 9310 ** threads may safely make multiple concurrent calls to sqlite3_backup_step(). 9311 ** However, the sqlite3_backup_remaining() and sqlite3_backup_pagecount() 9312 ** APIs are not strictly speaking threadsafe. If they are invoked at the 9313 ** same time as another thread is invoking sqlite3_backup_step() it is 9314 ** possible that they return invalid values. 9315 */ 9316 SQLITE_API sqlite3_backup *sqlite3_backup_init( 9317 sqlite3 *pDest, /* Destination database handle */ 9318 const char *zDestName, /* Destination database name */ 9319 sqlite3 *pSource, /* Source database handle */ 9320 const char *zSourceName /* Source database name */ 9321 ); 9322 SQLITE_API int sqlite3_backup_step(sqlite3_backup *p, int nPage); 9323 SQLITE_API int sqlite3_backup_finish(sqlite3_backup *p); 9324 SQLITE_API int sqlite3_backup_remaining(sqlite3_backup *p); 9325 SQLITE_API int sqlite3_backup_pagecount(sqlite3_backup *p); 9326 9327 /* 9328 ** CAPI3REF: Unlock Notification 9329 ** METHOD: sqlite3 9330 ** 9331 ** ^When running in shared-cache mode, a database operation may fail with 9332 ** an [SQLITE_LOCKED] error if the required locks on the shared-cache or 9333 ** individual tables within the shared-cache cannot be obtained. See 9334 ** [SQLite Shared-Cache Mode] for a description of shared-cache locking. 9335 ** ^This API may be used to register a callback that SQLite will invoke 9336 ** when the connection currently holding the required lock relinquishes it. 9337 ** ^This API is only available if the library was compiled with the 9338 ** [SQLITE_ENABLE_UNLOCK_NOTIFY] C-preprocessor symbol defined. 9339 ** 9340 ** See Also: [Using the SQLite Unlock Notification Feature]. 9341 ** 9342 ** ^Shared-cache locks are released when a database connection concludes 9343 ** its current transaction, either by committing it or rolling it back. 9344 ** 9345 ** ^When a connection (known as the blocked connection) fails to obtain a 9346 ** shared-cache lock and SQLITE_LOCKED is returned to the caller, the 9347 ** identity of the database connection (the blocking connection) that 9348 ** has locked the required resource is stored internally. ^After an 9349 ** application receives an SQLITE_LOCKED error, it may call the 9350 ** sqlite3_unlock_notify() method with the blocked connection handle as 9351 ** the first argument to register for a callback that will be invoked 9352 ** when the blocking connections current transaction is concluded. ^The 9353 ** callback is invoked from within the [sqlite3_step] or [sqlite3_close] 9354 ** call that concludes the blocking connection's transaction. 9355 ** 9356 ** ^(If sqlite3_unlock_notify() is called in a multi-threaded application, 9357 ** there is a chance that the blocking connection will have already 9358 ** concluded its transaction by the time sqlite3_unlock_notify() is invoked. 9359 ** If this happens, then the specified callback is invoked immediately, 9360 ** from within the call to sqlite3_unlock_notify().)^ 9361 ** 9362 ** ^If the blocked connection is attempting to obtain a write-lock on a 9363 ** shared-cache table, and more than one other connection currently holds 9364 ** a read-lock on the same table, then SQLite arbitrarily selects one of 9365 ** the other connections to use as the blocking connection. 9366 ** 9367 ** ^(There may be at most one unlock-notify callback registered by a 9368 ** blocked connection. If sqlite3_unlock_notify() is called when the 9369 ** blocked connection already has a registered unlock-notify callback, 9370 ** then the new callback replaces the old.)^ ^If sqlite3_unlock_notify() is 9371 ** called with a NULL pointer as its second argument, then any existing 9372 ** unlock-notify callback is canceled. ^The blocked connections 9373 ** unlock-notify callback may also be canceled by closing the blocked 9374 ** connection using [sqlite3_close()]. 9375 ** 9376 ** The unlock-notify callback is not reentrant. If an application invokes 9377 ** any sqlite3_xxx API functions from within an unlock-notify callback, a 9378 ** crash or deadlock may be the result. 9379 ** 9380 ** ^Unless deadlock is detected (see below), sqlite3_unlock_notify() always 9381 ** returns SQLITE_OK. 9382 ** 9383 ** <b>Callback Invocation Details</b> 9384 ** 9385 ** When an unlock-notify callback is registered, the application provides a 9386 ** single void* pointer that is passed to the callback when it is invoked. 9387 ** However, the signature of the callback function allows SQLite to pass 9388 ** it an array of void* context pointers. The first argument passed to 9389 ** an unlock-notify callback is a pointer to an array of void* pointers, 9390 ** and the second is the number of entries in the array. 9391 ** 9392 ** When a blocking connection's transaction is concluded, there may be 9393 ** more than one blocked connection that has registered for an unlock-notify 9394 ** callback. ^If two or more such blocked connections have specified the 9395 ** same callback function, then instead of invoking the callback function 9396 ** multiple times, it is invoked once with the set of void* context pointers 9397 ** specified by the blocked connections bundled together into an array. 9398 ** This gives the application an opportunity to prioritize any actions 9399 ** related to the set of unblocked database connections. 9400 ** 9401 ** <b>Deadlock Detection</b> 9402 ** 9403 ** Assuming that after registering for an unlock-notify callback a 9404 ** database waits for the callback to be issued before taking any further 9405 ** action (a reasonable assumption), then using this API may cause the 9406 ** application to deadlock. For example, if connection X is waiting for 9407 ** connection Y's transaction to be concluded, and similarly connection 9408 ** Y is waiting on connection X's transaction, then neither connection 9409 ** will proceed and the system may remain deadlocked indefinitely. 9410 ** 9411 ** To avoid this scenario, the sqlite3_unlock_notify() performs deadlock 9412 ** detection. ^If a given call to sqlite3_unlock_notify() would put the 9413 ** system in a deadlocked state, then SQLITE_LOCKED is returned and no 9414 ** unlock-notify callback is registered. The system is said to be in 9415 ** a deadlocked state if connection A has registered for an unlock-notify 9416 ** callback on the conclusion of connection B's transaction, and connection 9417 ** B has itself registered for an unlock-notify callback when connection 9418 ** A's transaction is concluded. ^Indirect deadlock is also detected, so 9419 ** the system is also considered to be deadlocked if connection B has 9420 ** registered for an unlock-notify callback on the conclusion of connection 9421 ** C's transaction, where connection C is waiting on connection A. ^Any 9422 ** number of levels of indirection are allowed. 9423 ** 9424 ** <b>The "DROP TABLE" Exception</b> 9425 ** 9426 ** When a call to [sqlite3_step()] returns SQLITE_LOCKED, it is almost 9427 ** always appropriate to call sqlite3_unlock_notify(). There is however, 9428 ** one exception. When executing a "DROP TABLE" or "DROP INDEX" statement, 9429 ** SQLite checks if there are any currently executing SELECT statements 9430 ** that belong to the same connection. If there are, SQLITE_LOCKED is 9431 ** returned. In this case there is no "blocking connection", so invoking 9432 ** sqlite3_unlock_notify() results in the unlock-notify callback being 9433 ** invoked immediately. If the application then re-attempts the "DROP TABLE" 9434 ** or "DROP INDEX" query, an infinite loop might be the result. 9435 ** 9436 ** One way around this problem is to check the extended error code returned 9437 ** by an sqlite3_step() call. ^(If there is a blocking connection, then the 9438 ** extended error code is set to SQLITE_LOCKED_SHAREDCACHE. Otherwise, in 9439 ** the special "DROP TABLE/INDEX" case, the extended error code is just 9440 ** SQLITE_LOCKED.)^ 9441 */ 9442 SQLITE_API int sqlite3_unlock_notify( 9443 sqlite3 *pBlocked, /* Waiting connection */ 9444 void (*xNotify)(void **apArg, int nArg), /* Callback function to invoke */ 9445 void *pNotifyArg /* Argument to pass to xNotify */ 9446 ); 9447 9448 9449 /* 9450 ** CAPI3REF: String Comparison 9451 ** 9452 ** ^The [sqlite3_stricmp()] and [sqlite3_strnicmp()] APIs allow applications 9453 ** and extensions to compare the contents of two buffers containing UTF-8 9454 ** strings in a case-independent fashion, using the same definition of "case 9455 ** independence" that SQLite uses internally when comparing identifiers. 9456 */ 9457 SQLITE_API int sqlite3_stricmp(const char *, const char *); 9458 SQLITE_API int sqlite3_strnicmp(const char *, const char *, int); 9459 9460 /* 9461 ** CAPI3REF: String Globbing 9462 * 9463 ** ^The [sqlite3_strglob(P,X)] interface returns zero if and only if 9464 ** string X matches the [GLOB] pattern P. 9465 ** ^The definition of [GLOB] pattern matching used in 9466 ** [sqlite3_strglob(P,X)] is the same as for the "X GLOB P" operator in the 9467 ** SQL dialect understood by SQLite. ^The [sqlite3_strglob(P,X)] function 9468 ** is case sensitive. 9469 ** 9470 ** Note that this routine returns zero on a match and non-zero if the strings 9471 ** do not match, the same as [sqlite3_stricmp()] and [sqlite3_strnicmp()]. 9472 ** 9473 ** See also: [sqlite3_strlike()]. 9474 */ 9475 SQLITE_API int sqlite3_strglob(const char *zGlob, const char *zStr); 9476 9477 /* 9478 ** CAPI3REF: String LIKE Matching 9479 * 9480 ** ^The [sqlite3_strlike(P,X,E)] interface returns zero if and only if 9481 ** string X matches the [LIKE] pattern P with escape character E. 9482 ** ^The definition of [LIKE] pattern matching used in 9483 ** [sqlite3_strlike(P,X,E)] is the same as for the "X LIKE P ESCAPE E" 9484 ** operator in the SQL dialect understood by SQLite. ^For "X LIKE P" without 9485 ** the ESCAPE clause, set the E parameter of [sqlite3_strlike(P,X,E)] to 0. 9486 ** ^As with the LIKE operator, the [sqlite3_strlike(P,X,E)] function is case 9487 ** insensitive - equivalent upper and lower case ASCII characters match 9488 ** one another. 9489 ** 9490 ** ^The [sqlite3_strlike(P,X,E)] function matches Unicode characters, though 9491 ** only ASCII characters are case folded. 9492 ** 9493 ** Note that this routine returns zero on a match and non-zero if the strings 9494 ** do not match, the same as [sqlite3_stricmp()] and [sqlite3_strnicmp()]. 9495 ** 9496 ** See also: [sqlite3_strglob()]. 9497 */ 9498 SQLITE_API int sqlite3_strlike(const char *zGlob, const char *zStr, unsigned int cEsc); 9499 9500 /* 9501 ** CAPI3REF: Error Logging Interface 9502 ** 9503 ** ^The [sqlite3_log()] interface writes a message into the [error log] 9504 ** established by the [SQLITE_CONFIG_LOG] option to [sqlite3_config()]. 9505 ** ^If logging is enabled, the zFormat string and subsequent arguments are 9506 ** used with [sqlite3_snprintf()] to generate the final output string. 9507 ** 9508 ** The sqlite3_log() interface is intended for use by extensions such as 9509 ** virtual tables, collating functions, and SQL functions. While there is 9510 ** nothing to prevent an application from calling sqlite3_log(), doing so 9511 ** is considered bad form. 9512 ** 9513 ** The zFormat string must not be NULL. 9514 ** 9515 ** To avoid deadlocks and other threading problems, the sqlite3_log() routine 9516 ** will not use dynamically allocated memory. The log message is stored in 9517 ** a fixed-length buffer on the stack. If the log message is longer than 9518 ** a few hundred characters, it will be truncated to the length of the 9519 ** buffer. 9520 */ 9521 SQLITE_API void sqlite3_log(int iErrCode, const char *zFormat, ...); 9522 9523 /* 9524 ** CAPI3REF: Write-Ahead Log Commit Hook 9525 ** METHOD: sqlite3 9526 ** 9527 ** ^The [sqlite3_wal_hook()] function is used to register a callback that 9528 ** is invoked each time data is committed to a database in wal mode. 9529 ** 9530 ** ^(The callback is invoked by SQLite after the commit has taken place and 9531 ** the associated write-lock on the database released)^, so the implementation 9532 ** may read, write or [checkpoint] the database as required. 9533 ** 9534 ** ^The first parameter passed to the callback function when it is invoked 9535 ** is a copy of the third parameter passed to sqlite3_wal_hook() when 9536 ** registering the callback. ^The second is a copy of the database handle. 9537 ** ^The third parameter is the name of the database that was written to - 9538 ** either "main" or the name of an [ATTACH]-ed database. ^The fourth parameter 9539 ** is the number of pages currently in the write-ahead log file, 9540 ** including those that were just committed. 9541 ** 9542 ** The callback function should normally return [SQLITE_OK]. ^If an error 9543 ** code is returned, that error will propagate back up through the 9544 ** SQLite code base to cause the statement that provoked the callback 9545 ** to report an error, though the commit will have still occurred. If the 9546 ** callback returns [SQLITE_ROW] or [SQLITE_DONE], or if it returns a value 9547 ** that does not correspond to any valid SQLite error code, the results 9548 ** are undefined. 9549 ** 9550 ** A single database handle may have at most a single write-ahead log callback 9551 ** registered at one time. ^Calling [sqlite3_wal_hook()] replaces any 9552 ** previously registered write-ahead log callback. ^The return value is 9553 ** a copy of the third parameter from the previous call, if any, or 0. 9554 ** ^Note that the [sqlite3_wal_autocheckpoint()] interface and the 9555 ** [wal_autocheckpoint pragma] both invoke [sqlite3_wal_hook()] and will 9556 ** overwrite any prior [sqlite3_wal_hook()] settings. 9557 */ 9558 SQLITE_API void *sqlite3_wal_hook( 9559 sqlite3*, 9560 int(*)(void *,sqlite3*,const char*,int), 9561 void* 9562 ); 9563 9564 /* 9565 ** CAPI3REF: Configure an auto-checkpoint 9566 ** METHOD: sqlite3 9567 ** 9568 ** ^The [sqlite3_wal_autocheckpoint(D,N)] is a wrapper around 9569 ** [sqlite3_wal_hook()] that causes any database on [database connection] D 9570 ** to automatically [checkpoint] 9571 ** after committing a transaction if there are N or 9572 ** more frames in the [write-ahead log] file. ^Passing zero or 9573 ** a negative value as the nFrame parameter disables automatic 9574 ** checkpoints entirely. 9575 ** 9576 ** ^The callback registered by this function replaces any existing callback 9577 ** registered using [sqlite3_wal_hook()]. ^Likewise, registering a callback 9578 ** using [sqlite3_wal_hook()] disables the automatic checkpoint mechanism 9579 ** configured by this function. 9580 ** 9581 ** ^The [wal_autocheckpoint pragma] can be used to invoke this interface 9582 ** from SQL. 9583 ** 9584 ** ^Checkpoints initiated by this mechanism are 9585 ** [sqlite3_wal_checkpoint_v2|PASSIVE]. 9586 ** 9587 ** ^Every new [database connection] defaults to having the auto-checkpoint 9588 ** enabled with a threshold of 1000 or [SQLITE_DEFAULT_WAL_AUTOCHECKPOINT] 9589 ** pages. The use of this interface 9590 ** is only necessary if the default setting is found to be suboptimal 9591 ** for a particular application. 9592 */ 9593 SQLITE_API int sqlite3_wal_autocheckpoint(sqlite3 *db, int N); 9594 9595 /* 9596 ** CAPI3REF: Checkpoint a database 9597 ** METHOD: sqlite3 9598 ** 9599 ** ^(The sqlite3_wal_checkpoint(D,X) is equivalent to 9600 ** [sqlite3_wal_checkpoint_v2](D,X,[SQLITE_CHECKPOINT_PASSIVE],0,0).)^ 9601 ** 9602 ** In brief, sqlite3_wal_checkpoint(D,X) causes the content in the 9603 ** [write-ahead log] for database X on [database connection] D to be 9604 ** transferred into the database file and for the write-ahead log to 9605 ** be reset. See the [checkpointing] documentation for addition 9606 ** information. 9607 ** 9608 ** This interface used to be the only way to cause a checkpoint to 9609 ** occur. But then the newer and more powerful [sqlite3_wal_checkpoint_v2()] 9610 ** interface was added. This interface is retained for backwards 9611 ** compatibility and as a convenience for applications that need to manually 9612 ** start a callback but which do not need the full power (and corresponding 9613 ** complication) of [sqlite3_wal_checkpoint_v2()]. 9614 */ 9615 SQLITE_API int sqlite3_wal_checkpoint(sqlite3 *db, const char *zDb); 9616 9617 /* 9618 ** CAPI3REF: Checkpoint a database 9619 ** METHOD: sqlite3 9620 ** 9621 ** ^(The sqlite3_wal_checkpoint_v2(D,X,M,L,C) interface runs a checkpoint 9622 ** operation on database X of [database connection] D in mode M. Status 9623 ** information is written back into integers pointed to by L and C.)^ 9624 ** ^(The M parameter must be a valid [checkpoint mode]:)^ 9625 ** 9626 ** <dl> 9627 ** <dt>SQLITE_CHECKPOINT_PASSIVE<dd> 9628 ** ^Checkpoint as many frames as possible without waiting for any database 9629 ** readers or writers to finish, then sync the database file if all frames 9630 ** in the log were checkpointed. ^The [busy-handler callback] 9631 ** is never invoked in the SQLITE_CHECKPOINT_PASSIVE mode. 9632 ** ^On the other hand, passive mode might leave the checkpoint unfinished 9633 ** if there are concurrent readers or writers. 9634 ** 9635 ** <dt>SQLITE_CHECKPOINT_FULL<dd> 9636 ** ^This mode blocks (it invokes the 9637 ** [sqlite3_busy_handler|busy-handler callback]) until there is no 9638 ** database writer and all readers are reading from the most recent database 9639 ** snapshot. ^It then checkpoints all frames in the log file and syncs the 9640 ** database file. ^This mode blocks new database writers while it is pending, 9641 ** but new database readers are allowed to continue unimpeded. 9642 ** 9643 ** <dt>SQLITE_CHECKPOINT_RESTART<dd> 9644 ** ^This mode works the same way as SQLITE_CHECKPOINT_FULL with the addition 9645 ** that after checkpointing the log file it blocks (calls the 9646 ** [busy-handler callback]) 9647 ** until all readers are reading from the database file only. ^This ensures 9648 ** that the next writer will restart the log file from the beginning. 9649 ** ^Like SQLITE_CHECKPOINT_FULL, this mode blocks new 9650 ** database writer attempts while it is pending, but does not impede readers. 9651 ** 9652 ** <dt>SQLITE_CHECKPOINT_TRUNCATE<dd> 9653 ** ^This mode works the same way as SQLITE_CHECKPOINT_RESTART with the 9654 ** addition that it also truncates the log file to zero bytes just prior 9655 ** to a successful return. 9656 ** </dl> 9657 ** 9658 ** ^If pnLog is not NULL, then *pnLog is set to the total number of frames in 9659 ** the log file or to -1 if the checkpoint could not run because 9660 ** of an error or because the database is not in [WAL mode]. ^If pnCkpt is not 9661 ** NULL,then *pnCkpt is set to the total number of checkpointed frames in the 9662 ** log file (including any that were already checkpointed before the function 9663 ** was called) or to -1 if the checkpoint could not run due to an error or 9664 ** because the database is not in WAL mode. ^Note that upon successful 9665 ** completion of an SQLITE_CHECKPOINT_TRUNCATE, the log file will have been 9666 ** truncated to zero bytes and so both *pnLog and *pnCkpt will be set to zero. 9667 ** 9668 ** ^All calls obtain an exclusive "checkpoint" lock on the database file. ^If 9669 ** any other process is running a checkpoint operation at the same time, the 9670 ** lock cannot be obtained and SQLITE_BUSY is returned. ^Even if there is a 9671 ** busy-handler configured, it will not be invoked in this case. 9672 ** 9673 ** ^The SQLITE_CHECKPOINT_FULL, RESTART and TRUNCATE modes also obtain the 9674 ** exclusive "writer" lock on the database file. ^If the writer lock cannot be 9675 ** obtained immediately, and a busy-handler is configured, it is invoked and 9676 ** the writer lock retried until either the busy-handler returns 0 or the lock 9677 ** is successfully obtained. ^The busy-handler is also invoked while waiting for 9678 ** database readers as described above. ^If the busy-handler returns 0 before 9679 ** the writer lock is obtained or while waiting for database readers, the 9680 ** checkpoint operation proceeds from that point in the same way as 9681 ** SQLITE_CHECKPOINT_PASSIVE - checkpointing as many frames as possible 9682 ** without blocking any further. ^SQLITE_BUSY is returned in this case. 9683 ** 9684 ** ^If parameter zDb is NULL or points to a zero length string, then the 9685 ** specified operation is attempted on all WAL databases [attached] to 9686 ** [database connection] db. In this case the 9687 ** values written to output parameters *pnLog and *pnCkpt are undefined. ^If 9688 ** an SQLITE_BUSY error is encountered when processing one or more of the 9689 ** attached WAL databases, the operation is still attempted on any remaining 9690 ** attached databases and SQLITE_BUSY is returned at the end. ^If any other 9691 ** error occurs while processing an attached database, processing is abandoned 9692 ** and the error code is returned to the caller immediately. ^If no error 9693 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached 9694 ** databases, SQLITE_OK is returned. 9695 ** 9696 ** ^If database zDb is the name of an attached database that is not in WAL 9697 ** mode, SQLITE_OK is returned and both *pnLog and *pnCkpt set to -1. ^If 9698 ** zDb is not NULL (or a zero length string) and is not the name of any 9699 ** attached database, SQLITE_ERROR is returned to the caller. 9700 ** 9701 ** ^Unless it returns SQLITE_MISUSE, 9702 ** the sqlite3_wal_checkpoint_v2() interface 9703 ** sets the error information that is queried by 9704 ** [sqlite3_errcode()] and [sqlite3_errmsg()]. 9705 ** 9706 ** ^The [PRAGMA wal_checkpoint] command can be used to invoke this interface 9707 ** from SQL. 9708 */ 9709 SQLITE_API int sqlite3_wal_checkpoint_v2( 9710 sqlite3 *db, /* Database handle */ 9711 const char *zDb, /* Name of attached database (or NULL) */ 9712 int eMode, /* SQLITE_CHECKPOINT_* value */ 9713 int *pnLog, /* OUT: Size of WAL log in frames */ 9714 int *pnCkpt /* OUT: Total number of frames checkpointed */ 9715 ); 9716 9717 /* 9718 ** CAPI3REF: Checkpoint Mode Values 9719 ** KEYWORDS: {checkpoint mode} 9720 ** 9721 ** These constants define all valid values for the "checkpoint mode" passed 9722 ** as the third parameter to the [sqlite3_wal_checkpoint_v2()] interface. 9723 ** See the [sqlite3_wal_checkpoint_v2()] documentation for details on the 9724 ** meaning of each of these checkpoint modes. 9725 */ 9726 #define SQLITE_CHECKPOINT_PASSIVE 0 /* Do as much as possible w/o blocking */ 9727 #define SQLITE_CHECKPOINT_FULL 1 /* Wait for writers, then checkpoint */ 9728 #define SQLITE_CHECKPOINT_RESTART 2 /* Like FULL but wait for readers */ 9729 #define SQLITE_CHECKPOINT_TRUNCATE 3 /* Like RESTART but also truncate WAL */ 9730 9731 /* 9732 ** CAPI3REF: Virtual Table Interface Configuration 9733 ** 9734 ** This function may be called by either the [xConnect] or [xCreate] method 9735 ** of a [virtual table] implementation to configure 9736 ** various facets of the virtual table interface. 9737 ** 9738 ** If this interface is invoked outside the context of an xConnect or 9739 ** xCreate virtual table method then the behavior is undefined. 9740 ** 9741 ** In the call sqlite3_vtab_config(D,C,...) the D parameter is the 9742 ** [database connection] in which the virtual table is being created and 9743 ** which is passed in as the first argument to the [xConnect] or [xCreate] 9744 ** method that is invoking sqlite3_vtab_config(). The C parameter is one 9745 ** of the [virtual table configuration options]. The presence and meaning 9746 ** of parameters after C depend on which [virtual table configuration option] 9747 ** is used. 9748 */ 9749 SQLITE_API int sqlite3_vtab_config(sqlite3*, int op, ...); 9750 9751 /* 9752 ** CAPI3REF: Virtual Table Configuration Options 9753 ** KEYWORDS: {virtual table configuration options} 9754 ** KEYWORDS: {virtual table configuration option} 9755 ** 9756 ** These macros define the various options to the 9757 ** [sqlite3_vtab_config()] interface that [virtual table] implementations 9758 ** can use to customize and optimize their behavior. 9759 ** 9760 ** <dl> 9761 ** [[SQLITE_VTAB_CONSTRAINT_SUPPORT]] 9762 ** <dt>SQLITE_VTAB_CONSTRAINT_SUPPORT</dt> 9763 ** <dd>Calls of the form 9764 ** [sqlite3_vtab_config](db,SQLITE_VTAB_CONSTRAINT_SUPPORT,X) are supported, 9765 ** where X is an integer. If X is zero, then the [virtual table] whose 9766 ** [xCreate] or [xConnect] method invoked [sqlite3_vtab_config()] does not 9767 ** support constraints. In this configuration (which is the default) if 9768 ** a call to the [xUpdate] method returns [SQLITE_CONSTRAINT], then the entire 9769 ** statement is rolled back as if [ON CONFLICT | OR ABORT] had been 9770 ** specified as part of the users SQL statement, regardless of the actual 9771 ** ON CONFLICT mode specified. 9772 ** 9773 ** If X is non-zero, then the virtual table implementation guarantees 9774 ** that if [xUpdate] returns [SQLITE_CONSTRAINT], it will do so before 9775 ** any modifications to internal or persistent data structures have been made. 9776 ** If the [ON CONFLICT] mode is ABORT, FAIL, IGNORE or ROLLBACK, SQLite 9777 ** is able to roll back a statement or database transaction, and abandon 9778 ** or continue processing the current SQL statement as appropriate. 9779 ** If the ON CONFLICT mode is REPLACE and the [xUpdate] method returns 9780 ** [SQLITE_CONSTRAINT], SQLite handles this as if the ON CONFLICT mode 9781 ** had been ABORT. 9782 ** 9783 ** Virtual table implementations that are required to handle OR REPLACE 9784 ** must do so within the [xUpdate] method. If a call to the 9785 ** [sqlite3_vtab_on_conflict()] function indicates that the current ON 9786 ** CONFLICT policy is REPLACE, the virtual table implementation should 9787 ** silently replace the appropriate rows within the xUpdate callback and 9788 ** return SQLITE_OK. Or, if this is not possible, it may return 9789 ** SQLITE_CONSTRAINT, in which case SQLite falls back to OR ABORT 9790 ** constraint handling. 9791 ** </dd> 9792 ** 9793 ** [[SQLITE_VTAB_DIRECTONLY]]<dt>SQLITE_VTAB_DIRECTONLY</dt> 9794 ** <dd>Calls of the form 9795 ** [sqlite3_vtab_config](db,SQLITE_VTAB_DIRECTONLY) from within the 9796 ** the [xConnect] or [xCreate] methods of a [virtual table] implementation 9797 ** prohibits that virtual table from being used from within triggers and 9798 ** views. 9799 ** </dd> 9800 ** 9801 ** [[SQLITE_VTAB_INNOCUOUS]]<dt>SQLITE_VTAB_INNOCUOUS</dt> 9802 ** <dd>Calls of the form 9803 ** [sqlite3_vtab_config](db,SQLITE_VTAB_INNOCUOUS) from within the 9804 ** the [xConnect] or [xCreate] methods of a [virtual table] implementation 9805 ** identify that virtual table as being safe to use from within triggers 9806 ** and views. Conceptually, the SQLITE_VTAB_INNOCUOUS tag means that the 9807 ** virtual table can do no serious harm even if it is controlled by a 9808 ** malicious hacker. Developers should avoid setting the SQLITE_VTAB_INNOCUOUS 9809 ** flag unless absolutely necessary. 9810 ** </dd> 9811 ** 9812 ** [[SQLITE_VTAB_USES_ALL_SCHEMAS]]<dt>SQLITE_VTAB_USES_ALL_SCHEMAS</dt> 9813 ** <dd>Calls of the form 9814 ** [sqlite3_vtab_config](db,SQLITE_VTAB_USES_ALL_SCHEMA) from within the 9815 ** the [xConnect] or [xCreate] methods of a [virtual table] implementation 9816 ** instruct the query planner to begin at least a read transaction on 9817 ** all schemas ("main", "temp", and any ATTACH-ed databases) whenever the 9818 ** virtual table is used. 9819 ** </dd> 9820 ** </dl> 9821 */ 9822 #define SQLITE_VTAB_CONSTRAINT_SUPPORT 1 9823 #define SQLITE_VTAB_INNOCUOUS 2 9824 #define SQLITE_VTAB_DIRECTONLY 3 9825 #define SQLITE_VTAB_USES_ALL_SCHEMAS 4 9826 9827 /* 9828 ** CAPI3REF: Determine The Virtual Table Conflict Policy 9829 ** 9830 ** This function may only be called from within a call to the [xUpdate] method 9831 ** of a [virtual table] implementation for an INSERT or UPDATE operation. ^The 9832 ** value returned is one of [SQLITE_ROLLBACK], [SQLITE_IGNORE], [SQLITE_FAIL], 9833 ** [SQLITE_ABORT], or [SQLITE_REPLACE], according to the [ON CONFLICT] mode 9834 ** of the SQL statement that triggered the call to the [xUpdate] method of the 9835 ** [virtual table]. 9836 */ 9837 SQLITE_API int sqlite3_vtab_on_conflict(sqlite3 *); 9838 9839 /* 9840 ** CAPI3REF: Determine If Virtual Table Column Access Is For UPDATE 9841 ** 9842 ** If the sqlite3_vtab_nochange(X) routine is called within the [xColumn] 9843 ** method of a [virtual table], then it might return true if the 9844 ** column is being fetched as part of an UPDATE operation during which the 9845 ** column value will not change. The virtual table implementation can use 9846 ** this hint as permission to substitute a return value that is less 9847 ** expensive to compute and that the corresponding 9848 ** [xUpdate] method understands as a "no-change" value. 9849 ** 9850 ** If the [xColumn] method calls sqlite3_vtab_nochange() and finds that 9851 ** the column is not changed by the UPDATE statement, then the xColumn 9852 ** method can optionally return without setting a result, without calling 9853 ** any of the [sqlite3_result_int|sqlite3_result_xxxxx() interfaces]. 9854 ** In that case, [sqlite3_value_nochange(X)] will return true for the 9855 ** same column in the [xUpdate] method. 9856 ** 9857 ** The sqlite3_vtab_nochange() routine is an optimization. Virtual table 9858 ** implementations should continue to give a correct answer even if the 9859 ** sqlite3_vtab_nochange() interface were to always return false. In the 9860 ** current implementation, the sqlite3_vtab_nochange() interface does always 9861 ** returns false for the enhanced [UPDATE FROM] statement. 9862 */ 9863 SQLITE_API int sqlite3_vtab_nochange(sqlite3_context*); 9864 9865 /* 9866 ** CAPI3REF: Determine The Collation For a Virtual Table Constraint 9867 ** METHOD: sqlite3_index_info 9868 ** 9869 ** This function may only be called from within a call to the [xBestIndex] 9870 ** method of a [virtual table]. This function returns a pointer to a string 9871 ** that is the name of the appropriate collation sequence to use for text 9872 ** comparisons on the constraint identified by its arguments. 9873 ** 9874 ** The first argument must be the pointer to the [sqlite3_index_info] object 9875 ** that is the first parameter to the xBestIndex() method. The second argument 9876 ** must be an index into the aConstraint[] array belonging to the 9877 ** sqlite3_index_info structure passed to xBestIndex. 9878 ** 9879 ** Important: 9880 ** The first parameter must be the same pointer that is passed into the 9881 ** xBestMethod() method. The first parameter may not be a pointer to a 9882 ** different [sqlite3_index_info] object, even an exact copy. 9883 ** 9884 ** The return value is computed as follows: 9885 ** 9886 ** <ol> 9887 ** <li><p> If the constraint comes from a WHERE clause expression that contains 9888 ** a [COLLATE operator], then the name of the collation specified by 9889 ** that COLLATE operator is returned. 9890 ** <li><p> If there is no COLLATE operator, but the column that is the subject 9891 ** of the constraint specifies an alternative collating sequence via 9892 ** a [COLLATE clause] on the column definition within the CREATE TABLE 9893 ** statement that was passed into [sqlite3_declare_vtab()], then the 9894 ** name of that alternative collating sequence is returned. 9895 ** <li><p> Otherwise, "BINARY" is returned. 9896 ** </ol> 9897 */ 9898 SQLITE_API const char *sqlite3_vtab_collation(sqlite3_index_info*,int); 9899 9900 /* 9901 ** CAPI3REF: Determine if a virtual table query is DISTINCT 9902 ** METHOD: sqlite3_index_info 9903 ** 9904 ** This API may only be used from within an [xBestIndex|xBestIndex method] 9905 ** of a [virtual table] implementation. The result of calling this 9906 ** interface from outside of xBestIndex() is undefined and probably harmful. 9907 ** 9908 ** ^The sqlite3_vtab_distinct() interface returns an integer between 0 and 9909 ** 3. The integer returned by sqlite3_vtab_distinct() 9910 ** gives the virtual table additional information about how the query 9911 ** planner wants the output to be ordered. As long as the virtual table 9912 ** can meet the ordering requirements of the query planner, it may set 9913 ** the "orderByConsumed" flag. 9914 ** 9915 ** <ol><li value="0"><p> 9916 ** ^If the sqlite3_vtab_distinct() interface returns 0, that means 9917 ** that the query planner needs the virtual table to return all rows in the 9918 ** sort order defined by the "nOrderBy" and "aOrderBy" fields of the 9919 ** [sqlite3_index_info] object. This is the default expectation. If the 9920 ** virtual table outputs all rows in sorted order, then it is always safe for 9921 ** the xBestIndex method to set the "orderByConsumed" flag, regardless of 9922 ** the return value from sqlite3_vtab_distinct(). 9923 ** <li value="1"><p> 9924 ** ^(If the sqlite3_vtab_distinct() interface returns 1, that means 9925 ** that the query planner does not need the rows to be returned in sorted order 9926 ** as long as all rows with the same values in all columns identified by the 9927 ** "aOrderBy" field are adjacent.)^ This mode is used when the query planner 9928 ** is doing a GROUP BY. 9929 ** <li value="2"><p> 9930 ** ^(If the sqlite3_vtab_distinct() interface returns 2, that means 9931 ** that the query planner does not need the rows returned in any particular 9932 ** order, as long as rows with the same values in all "aOrderBy" columns 9933 ** are adjacent.)^ ^(Furthermore, only a single row for each particular 9934 ** combination of values in the columns identified by the "aOrderBy" field 9935 ** needs to be returned.)^ ^It is always ok for two or more rows with the same 9936 ** values in all "aOrderBy" columns to be returned, as long as all such rows 9937 ** are adjacent. ^The virtual table may, if it chooses, omit extra rows 9938 ** that have the same value for all columns identified by "aOrderBy". 9939 ** ^However omitting the extra rows is optional. 9940 ** This mode is used for a DISTINCT query. 9941 ** <li value="3"><p> 9942 ** ^(If the sqlite3_vtab_distinct() interface returns 3, that means 9943 ** that the query planner needs only distinct rows but it does need the 9944 ** rows to be sorted.)^ ^The virtual table implementation is free to omit 9945 ** rows that are identical in all aOrderBy columns, if it wants to, but 9946 ** it is not required to omit any rows. This mode is used for queries 9947 ** that have both DISTINCT and ORDER BY clauses. 9948 ** </ol> 9949 ** 9950 ** ^For the purposes of comparing virtual table output values to see if the 9951 ** values are same value for sorting purposes, two NULL values are considered 9952 ** to be the same. In other words, the comparison operator is "IS" 9953 ** (or "IS NOT DISTINCT FROM") and not "==". 9954 ** 9955 ** If a virtual table implementation is unable to meet the requirements 9956 ** specified above, then it must not set the "orderByConsumed" flag in the 9957 ** [sqlite3_index_info] object or an incorrect answer may result. 9958 ** 9959 ** ^A virtual table implementation is always free to return rows in any order 9960 ** it wants, as long as the "orderByConsumed" flag is not set. ^When the 9961 ** the "orderByConsumed" flag is unset, the query planner will add extra 9962 ** [bytecode] to ensure that the final results returned by the SQL query are 9963 ** ordered correctly. The use of the "orderByConsumed" flag and the 9964 ** sqlite3_vtab_distinct() interface is merely an optimization. ^Careful 9965 ** use of the sqlite3_vtab_distinct() interface and the "orderByConsumed" 9966 ** flag might help queries against a virtual table to run faster. Being 9967 ** overly aggressive and setting the "orderByConsumed" flag when it is not 9968 ** valid to do so, on the other hand, might cause SQLite to return incorrect 9969 ** results. 9970 */ 9971 SQLITE_API int sqlite3_vtab_distinct(sqlite3_index_info*); 9972 9973 /* 9974 ** CAPI3REF: Identify and handle IN constraints in xBestIndex 9975 ** 9976 ** This interface may only be used from within an 9977 ** [xBestIndex|xBestIndex() method] of a [virtual table] implementation. 9978 ** The result of invoking this interface from any other context is 9979 ** undefined and probably harmful. 9980 ** 9981 ** ^(A constraint on a virtual table of the form 9982 ** "[IN operator|column IN (...)]" is 9983 ** communicated to the xBestIndex method as a 9984 ** [SQLITE_INDEX_CONSTRAINT_EQ] constraint.)^ If xBestIndex wants to use 9985 ** this constraint, it must set the corresponding 9986 ** aConstraintUsage[].argvIndex to a positive integer. ^(Then, under 9987 ** the usual mode of handling IN operators, SQLite generates [bytecode] 9988 ** that invokes the [xFilter|xFilter() method] once for each value 9989 ** on the right-hand side of the IN operator.)^ Thus the virtual table 9990 ** only sees a single value from the right-hand side of the IN operator 9991 ** at a time. 9992 ** 9993 ** In some cases, however, it would be advantageous for the virtual 9994 ** table to see all values on the right-hand of the IN operator all at 9995 ** once. The sqlite3_vtab_in() interfaces facilitates this in two ways: 9996 ** 9997 ** <ol> 9998 ** <li><p> 9999 ** ^A call to sqlite3_vtab_in(P,N,-1) will return true (non-zero) 10000 ** if and only if the [sqlite3_index_info|P->aConstraint][N] constraint 10001 ** is an [IN operator] that can be processed all at once. ^In other words, 10002 ** sqlite3_vtab_in() with -1 in the third argument is a mechanism 10003 ** by which the virtual table can ask SQLite if all-at-once processing 10004 ** of the IN operator is even possible. 10005 ** 10006 ** <li><p> 10007 ** ^A call to sqlite3_vtab_in(P,N,F) with F==1 or F==0 indicates 10008 ** to SQLite that the virtual table does or does not want to process 10009 ** the IN operator all-at-once, respectively. ^Thus when the third 10010 ** parameter (F) is non-negative, this interface is the mechanism by 10011 ** which the virtual table tells SQLite how it wants to process the 10012 ** IN operator. 10013 ** </ol> 10014 ** 10015 ** ^The sqlite3_vtab_in(P,N,F) interface can be invoked multiple times 10016 ** within the same xBestIndex method call. ^For any given P,N pair, 10017 ** the return value from sqlite3_vtab_in(P,N,F) will always be the same 10018 ** within the same xBestIndex call. ^If the interface returns true 10019 ** (non-zero), that means that the constraint is an IN operator 10020 ** that can be processed all-at-once. ^If the constraint is not an IN 10021 ** operator or cannot be processed all-at-once, then the interface returns 10022 ** false. 10023 ** 10024 ** ^(All-at-once processing of the IN operator is selected if both of the 10025 ** following conditions are met: 10026 ** 10027 ** <ol> 10028 ** <li><p> The P->aConstraintUsage[N].argvIndex value is set to a positive 10029 ** integer. This is how the virtual table tells SQLite that it wants to 10030 ** use the N-th constraint. 10031 ** 10032 ** <li><p> The last call to sqlite3_vtab_in(P,N,F) for which F was 10033 ** non-negative had F>=1. 10034 ** </ol>)^ 10035 ** 10036 ** ^If either or both of the conditions above are false, then SQLite uses 10037 ** the traditional one-at-a-time processing strategy for the IN constraint. 10038 ** ^If both conditions are true, then the argvIndex-th parameter to the 10039 ** xFilter method will be an [sqlite3_value] that appears to be NULL, 10040 ** but which can be passed to [sqlite3_vtab_in_first()] and 10041 ** [sqlite3_vtab_in_next()] to find all values on the right-hand side 10042 ** of the IN constraint. 10043 */ 10044 SQLITE_API int sqlite3_vtab_in(sqlite3_index_info*, int iCons, int bHandle); 10045 10046 /* 10047 ** CAPI3REF: Find all elements on the right-hand side of an IN constraint. 10048 ** 10049 ** These interfaces are only useful from within the 10050 ** [xFilter|xFilter() method] of a [virtual table] implementation. 10051 ** The result of invoking these interfaces from any other context 10052 ** is undefined and probably harmful. 10053 ** 10054 ** The X parameter in a call to sqlite3_vtab_in_first(X,P) or 10055 ** sqlite3_vtab_in_next(X,P) should be one of the parameters to the 10056 ** xFilter method which invokes these routines, and specifically 10057 ** a parameter that was previously selected for all-at-once IN constraint 10058 ** processing use the [sqlite3_vtab_in()] interface in the 10059 ** [xBestIndex|xBestIndex method]. ^(If the X parameter is not 10060 ** an xFilter argument that was selected for all-at-once IN constraint 10061 ** processing, then these routines return [SQLITE_ERROR].)^ 10062 ** 10063 ** ^(Use these routines to access all values on the right-hand side 10064 ** of the IN constraint using code like the following: 10065 ** 10066 ** <blockquote><pre> 10067 ** for(rc=sqlite3_vtab_in_first(pList, &pVal); 10068 ** rc==SQLITE_OK && pVal; 10069 ** rc=sqlite3_vtab_in_next(pList, &pVal) 10070 ** ){ 10071 ** // do something with pVal 10072 ** } 10073 ** if( rc!=SQLITE_OK ){ 10074 ** // an error has occurred 10075 ** } 10076 ** </pre></blockquote>)^ 10077 ** 10078 ** ^On success, the sqlite3_vtab_in_first(X,P) and sqlite3_vtab_in_next(X,P) 10079 ** routines return SQLITE_OK and set *P to point to the first or next value 10080 ** on the RHS of the IN constraint. ^If there are no more values on the 10081 ** right hand side of the IN constraint, then *P is set to NULL and these 10082 ** routines return [SQLITE_DONE]. ^The return value might be 10083 ** some other value, such as SQLITE_NOMEM, in the event of a malfunction. 10084 ** 10085 ** The *ppOut values returned by these routines are only valid until the 10086 ** next call to either of these routines or until the end of the xFilter 10087 ** method from which these routines were called. If the virtual table 10088 ** implementation needs to retain the *ppOut values for longer, it must make 10089 ** copies. The *ppOut values are [protected sqlite3_value|protected]. 10090 */ 10091 SQLITE_API int sqlite3_vtab_in_first(sqlite3_value *pVal, sqlite3_value **ppOut); 10092 SQLITE_API int sqlite3_vtab_in_next(sqlite3_value *pVal, sqlite3_value **ppOut); 10093 10094 /* 10095 ** CAPI3REF: Constraint values in xBestIndex() 10096 ** METHOD: sqlite3_index_info 10097 ** 10098 ** This API may only be used from within the [xBestIndex|xBestIndex method] 10099 ** of a [virtual table] implementation. The result of calling this interface 10100 ** from outside of an xBestIndex method are undefined and probably harmful. 10101 ** 10102 ** ^When the sqlite3_vtab_rhs_value(P,J,V) interface is invoked from within 10103 ** the [xBestIndex] method of a [virtual table] implementation, with P being 10104 ** a copy of the [sqlite3_index_info] object pointer passed into xBestIndex and 10105 ** J being a 0-based index into P->aConstraint[], then this routine 10106 ** attempts to set *V to the value of the right-hand operand of 10107 ** that constraint if the right-hand operand is known. ^If the 10108 ** right-hand operand is not known, then *V is set to a NULL pointer. 10109 ** ^The sqlite3_vtab_rhs_value(P,J,V) interface returns SQLITE_OK if 10110 ** and only if *V is set to a value. ^The sqlite3_vtab_rhs_value(P,J,V) 10111 ** inteface returns SQLITE_NOTFOUND if the right-hand side of the J-th 10112 ** constraint is not available. ^The sqlite3_vtab_rhs_value() interface 10113 ** can return an result code other than SQLITE_OK or SQLITE_NOTFOUND if 10114 ** something goes wrong. 10115 ** 10116 ** The sqlite3_vtab_rhs_value() interface is usually only successful if 10117 ** the right-hand operand of a constraint is a literal value in the original 10118 ** SQL statement. If the right-hand operand is an expression or a reference 10119 ** to some other column or a [host parameter], then sqlite3_vtab_rhs_value() 10120 ** will probably return [SQLITE_NOTFOUND]. 10121 ** 10122 ** ^(Some constraints, such as [SQLITE_INDEX_CONSTRAINT_ISNULL] and 10123 ** [SQLITE_INDEX_CONSTRAINT_ISNOTNULL], have no right-hand operand. For such 10124 ** constraints, sqlite3_vtab_rhs_value() always returns SQLITE_NOTFOUND.)^ 10125 ** 10126 ** ^The [sqlite3_value] object returned in *V is a protected sqlite3_value 10127 ** and remains valid for the duration of the xBestIndex method call. 10128 ** ^When xBestIndex returns, the sqlite3_value object returned by 10129 ** sqlite3_vtab_rhs_value() is automatically deallocated. 10130 ** 10131 ** The "_rhs_" in the name of this routine is an abbreviation for 10132 ** "Right-Hand Side". 10133 */ 10134 SQLITE_API int sqlite3_vtab_rhs_value(sqlite3_index_info*, int, sqlite3_value **ppVal); 10135 10136 /* 10137 ** CAPI3REF: Conflict resolution modes 10138 ** KEYWORDS: {conflict resolution mode} 10139 ** 10140 ** These constants are returned by [sqlite3_vtab_on_conflict()] to 10141 ** inform a [virtual table] implementation what the [ON CONFLICT] mode 10142 ** is for the SQL statement being evaluated. 10143 ** 10144 ** Note that the [SQLITE_IGNORE] constant is also used as a potential 10145 ** return value from the [sqlite3_set_authorizer()] callback and that 10146 ** [SQLITE_ABORT] is also a [result code]. 10147 */ 10148 #define SQLITE_ROLLBACK 1 10149 /* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback */ 10150 #define SQLITE_FAIL 3 10151 /* #define SQLITE_ABORT 4 // Also an error code */ 10152 #define SQLITE_REPLACE 5 10153 10154 /* 10155 ** CAPI3REF: Prepared Statement Scan Status Opcodes 10156 ** KEYWORDS: {scanstatus options} 10157 ** 10158 ** The following constants can be used for the T parameter to the 10159 ** [sqlite3_stmt_scanstatus(S,X,T,V)] interface. Each constant designates a 10160 ** different metric for sqlite3_stmt_scanstatus() to return. 10161 ** 10162 ** When the value returned to V is a string, space to hold that string is 10163 ** managed by the prepared statement S and will be automatically freed when 10164 ** S is finalized. 10165 ** 10166 ** Not all values are available for all query elements. When a value is 10167 ** not available, the output variable is set to -1 if the value is numeric, 10168 ** or to NULL if it is a string (SQLITE_SCANSTAT_NAME). 10169 ** 10170 ** <dl> 10171 ** [[SQLITE_SCANSTAT_NLOOP]] <dt>SQLITE_SCANSTAT_NLOOP</dt> 10172 ** <dd>^The [sqlite3_int64] variable pointed to by the V parameter will be 10173 ** set to the total number of times that the X-th loop has run.</dd> 10174 ** 10175 ** [[SQLITE_SCANSTAT_NVISIT]] <dt>SQLITE_SCANSTAT_NVISIT</dt> 10176 ** <dd>^The [sqlite3_int64] variable pointed to by the V parameter will be set 10177 ** to the total number of rows examined by all iterations of the X-th loop.</dd> 10178 ** 10179 ** [[SQLITE_SCANSTAT_EST]] <dt>SQLITE_SCANSTAT_EST</dt> 10180 ** <dd>^The "double" variable pointed to by the V parameter will be set to the 10181 ** query planner's estimate for the average number of rows output from each 10182 ** iteration of the X-th loop. If the query planner's estimates was accurate, 10183 ** then this value will approximate the quotient NVISIT/NLOOP and the 10184 ** product of this value for all prior loops with the same SELECTID will 10185 ** be the NLOOP value for the current loop. 10186 ** 10187 ** [[SQLITE_SCANSTAT_NAME]] <dt>SQLITE_SCANSTAT_NAME</dt> 10188 ** <dd>^The "const char *" variable pointed to by the V parameter will be set 10189 ** to a zero-terminated UTF-8 string containing the name of the index or table 10190 ** used for the X-th loop. 10191 ** 10192 ** [[SQLITE_SCANSTAT_EXPLAIN]] <dt>SQLITE_SCANSTAT_EXPLAIN</dt> 10193 ** <dd>^The "const char *" variable pointed to by the V parameter will be set 10194 ** to a zero-terminated UTF-8 string containing the [EXPLAIN QUERY PLAN] 10195 ** description for the X-th loop. 10196 ** 10197 ** [[SQLITE_SCANSTAT_SELECTID]] <dt>SQLITE_SCANSTAT_SELECTID</dt> 10198 ** <dd>^The "int" variable pointed to by the V parameter will be set to the 10199 ** id for the X-th query plan element. The id value is unique within the 10200 ** statement. The select-id is the same value as is output in the first 10201 ** column of an [EXPLAIN QUERY PLAN] query. 10202 ** 10203 ** [[SQLITE_SCANSTAT_PARENTID]] <dt>SQLITE_SCANSTAT_PARENTID</dt> 10204 ** <dd>The "int" variable pointed to by the V parameter will be set to the 10205 ** the id of the parent of the current query element, if applicable, or 10206 ** to zero if the query element has no parent. This is the same value as 10207 ** returned in the second column of an [EXPLAIN QUERY PLAN] query. 10208 ** 10209 ** [[SQLITE_SCANSTAT_NCYCLE]] <dt>SQLITE_SCANSTAT_NCYCLE</dt> 10210 ** <dd>The sqlite3_int64 output value is set to the number of cycles, 10211 ** according to the processor time-stamp counter, that elapsed while the 10212 ** query element was being processed. This value is not available for 10213 ** all query elements - if it is unavailable the output variable is 10214 ** set to -1. 10215 ** </dl> 10216 */ 10217 #define SQLITE_SCANSTAT_NLOOP 0 10218 #define SQLITE_SCANSTAT_NVISIT 1 10219 #define SQLITE_SCANSTAT_EST 2 10220 #define SQLITE_SCANSTAT_NAME 3 10221 #define SQLITE_SCANSTAT_EXPLAIN 4 10222 #define SQLITE_SCANSTAT_SELECTID 5 10223 #define SQLITE_SCANSTAT_PARENTID 6 10224 #define SQLITE_SCANSTAT_NCYCLE 7 10225 10226 /* 10227 ** CAPI3REF: Prepared Statement Scan Status 10228 ** METHOD: sqlite3_stmt 10229 ** 10230 ** These interfaces return information about the predicted and measured 10231 ** performance for pStmt. Advanced applications can use this 10232 ** interface to compare the predicted and the measured performance and 10233 ** issue warnings and/or rerun [ANALYZE] if discrepancies are found. 10234 ** 10235 ** Since this interface is expected to be rarely used, it is only 10236 ** available if SQLite is compiled using the [SQLITE_ENABLE_STMT_SCANSTATUS] 10237 ** compile-time option. 10238 ** 10239 ** The "iScanStatusOp" parameter determines which status information to return. 10240 ** The "iScanStatusOp" must be one of the [scanstatus options] or the behavior 10241 ** of this interface is undefined. ^The requested measurement is written into 10242 ** a variable pointed to by the "pOut" parameter. 10243 ** 10244 ** The "flags" parameter must be passed a mask of flags. At present only 10245 ** one flag is defined - SQLITE_SCANSTAT_COMPLEX. If SQLITE_SCANSTAT_COMPLEX 10246 ** is specified, then status information is available for all elements 10247 ** of a query plan that are reported by "EXPLAIN QUERY PLAN" output. If 10248 ** SQLITE_SCANSTAT_COMPLEX is not specified, then only query plan elements 10249 ** that correspond to query loops (the "SCAN..." and "SEARCH..." elements of 10250 ** the EXPLAIN QUERY PLAN output) are available. Invoking API 10251 ** sqlite3_stmt_scanstatus() is equivalent to calling 10252 ** sqlite3_stmt_scanstatus_v2() with a zeroed flags parameter. 10253 ** 10254 ** Parameter "idx" identifies the specific query element to retrieve statistics 10255 ** for. Query elements are numbered starting from zero. A value of -1 may be 10256 ** to query for statistics regarding the entire query. ^If idx is out of range 10257 ** - less than -1 or greater than or equal to the total number of query 10258 ** elements used to implement the statement - a non-zero value is returned and 10259 ** the variable that pOut points to is unchanged. 10260 ** 10261 ** See also: [sqlite3_stmt_scanstatus_reset()] 10262 */ 10263 SQLITE_API int sqlite3_stmt_scanstatus( 10264 sqlite3_stmt *pStmt, /* Prepared statement for which info desired */ 10265 int idx, /* Index of loop to report on */ 10266 int iScanStatusOp, /* Information desired. SQLITE_SCANSTAT_* */ 10267 void *pOut /* Result written here */ 10268 ); 10269 SQLITE_API int sqlite3_stmt_scanstatus_v2( 10270 sqlite3_stmt *pStmt, /* Prepared statement for which info desired */ 10271 int idx, /* Index of loop to report on */ 10272 int iScanStatusOp, /* Information desired. SQLITE_SCANSTAT_* */ 10273 int flags, /* Mask of flags defined below */ 10274 void *pOut /* Result written here */ 10275 ); 10276 10277 /* 10278 ** CAPI3REF: Prepared Statement Scan Status 10279 ** KEYWORDS: {scan status flags} 10280 */ 10281 #define SQLITE_SCANSTAT_COMPLEX 0x0001 10282 10283 /* 10284 ** CAPI3REF: Zero Scan-Status Counters 10285 ** METHOD: sqlite3_stmt 10286 ** 10287 ** ^Zero all [sqlite3_stmt_scanstatus()] related event counters. 10288 ** 10289 ** This API is only available if the library is built with pre-processor 10290 ** symbol [SQLITE_ENABLE_STMT_SCANSTATUS] defined. 10291 */ 10292 SQLITE_API void sqlite3_stmt_scanstatus_reset(sqlite3_stmt*); 10293 10294 /* 10295 ** CAPI3REF: Flush caches to disk mid-transaction 10296 ** METHOD: sqlite3 10297 ** 10298 ** ^If a write-transaction is open on [database connection] D when the 10299 ** [sqlite3_db_cacheflush(D)] interface invoked, any dirty 10300 ** pages in the pager-cache that are not currently in use are written out 10301 ** to disk. A dirty page may be in use if a database cursor created by an 10302 ** active SQL statement is reading from it, or if it is page 1 of a database 10303 ** file (page 1 is always "in use"). ^The [sqlite3_db_cacheflush(D)] 10304 ** interface flushes caches for all schemas - "main", "temp", and 10305 ** any [attached] databases. 10306 ** 10307 ** ^If this function needs to obtain extra database locks before dirty pages 10308 ** can be flushed to disk, it does so. ^If those locks cannot be obtained 10309 ** immediately and there is a busy-handler callback configured, it is invoked 10310 ** in the usual manner. ^If the required lock still cannot be obtained, then 10311 ** the database is skipped and an attempt made to flush any dirty pages 10312 ** belonging to the next (if any) database. ^If any databases are skipped 10313 ** because locks cannot be obtained, but no other error occurs, this 10314 ** function returns SQLITE_BUSY. 10315 ** 10316 ** ^If any other error occurs while flushing dirty pages to disk (for 10317 ** example an IO error or out-of-memory condition), then processing is 10318 ** abandoned and an SQLite [error code] is returned to the caller immediately. 10319 ** 10320 ** ^Otherwise, if no error occurs, [sqlite3_db_cacheflush()] returns SQLITE_OK. 10321 ** 10322 ** ^This function does not set the database handle error code or message 10323 ** returned by the [sqlite3_errcode()] and [sqlite3_errmsg()] functions. 10324 */ 10325 SQLITE_API int sqlite3_db_cacheflush(sqlite3*); 10326 10327 /* 10328 ** CAPI3REF: The pre-update hook. 10329 ** METHOD: sqlite3 10330 ** 10331 ** ^These interfaces are only available if SQLite is compiled using the 10332 ** [SQLITE_ENABLE_PREUPDATE_HOOK] compile-time option. 10333 ** 10334 ** ^The [sqlite3_preupdate_hook()] interface registers a callback function 10335 ** that is invoked prior to each [INSERT], [UPDATE], and [DELETE] operation 10336 ** on a database table. 10337 ** ^At most one preupdate hook may be registered at a time on a single 10338 ** [database connection]; each call to [sqlite3_preupdate_hook()] overrides 10339 ** the previous setting. 10340 ** ^The preupdate hook is disabled by invoking [sqlite3_preupdate_hook()] 10341 ** with a NULL pointer as the second parameter. 10342 ** ^The third parameter to [sqlite3_preupdate_hook()] is passed through as 10343 ** the first parameter to callbacks. 10344 ** 10345 ** ^The preupdate hook only fires for changes to real database tables; the 10346 ** preupdate hook is not invoked for changes to [virtual tables] or to 10347 ** system tables like sqlite_sequence or sqlite_stat1. 10348 ** 10349 ** ^The second parameter to the preupdate callback is a pointer to 10350 ** the [database connection] that registered the preupdate hook. 10351 ** ^The third parameter to the preupdate callback is one of the constants 10352 ** [SQLITE_INSERT], [SQLITE_DELETE], or [SQLITE_UPDATE] to identify the 10353 ** kind of update operation that is about to occur. 10354 ** ^(The fourth parameter to the preupdate callback is the name of the 10355 ** database within the database connection that is being modified. This 10356 ** will be "main" for the main database or "temp" for TEMP tables or 10357 ** the name given after the AS keyword in the [ATTACH] statement for attached 10358 ** databases.)^ 10359 ** ^The fifth parameter to the preupdate callback is the name of the 10360 ** table that is being modified. 10361 ** 10362 ** For an UPDATE or DELETE operation on a [rowid table], the sixth 10363 ** parameter passed to the preupdate callback is the initial [rowid] of the 10364 ** row being modified or deleted. For an INSERT operation on a rowid table, 10365 ** or any operation on a WITHOUT ROWID table, the value of the sixth 10366 ** parameter is undefined. For an INSERT or UPDATE on a rowid table the 10367 ** seventh parameter is the final rowid value of the row being inserted 10368 ** or updated. The value of the seventh parameter passed to the callback 10369 ** function is not defined for operations on WITHOUT ROWID tables, or for 10370 ** DELETE operations on rowid tables. 10371 ** 10372 ** ^The sqlite3_preupdate_hook(D,C,P) function returns the P argument from 10373 ** the previous call on the same [database connection] D, or NULL for 10374 ** the first call on D. 10375 ** 10376 ** The [sqlite3_preupdate_old()], [sqlite3_preupdate_new()], 10377 ** [sqlite3_preupdate_count()], and [sqlite3_preupdate_depth()] interfaces 10378 ** provide additional information about a preupdate event. These routines 10379 ** may only be called from within a preupdate callback. Invoking any of 10380 ** these routines from outside of a preupdate callback or with a 10381 ** [database connection] pointer that is different from the one supplied 10382 ** to the preupdate callback results in undefined and probably undesirable 10383 ** behavior. 10384 ** 10385 ** ^The [sqlite3_preupdate_count(D)] interface returns the number of columns 10386 ** in the row that is being inserted, updated, or deleted. 10387 ** 10388 ** ^The [sqlite3_preupdate_old(D,N,P)] interface writes into P a pointer to 10389 ** a [protected sqlite3_value] that contains the value of the Nth column of 10390 ** the table row before it is updated. The N parameter must be between 0 10391 ** and one less than the number of columns or the behavior will be 10392 ** undefined. This must only be used within SQLITE_UPDATE and SQLITE_DELETE 10393 ** preupdate callbacks; if it is used by an SQLITE_INSERT callback then the 10394 ** behavior is undefined. The [sqlite3_value] that P points to 10395 ** will be destroyed when the preupdate callback returns. 10396 ** 10397 ** ^The [sqlite3_preupdate_new(D,N,P)] interface writes into P a pointer to 10398 ** a [protected sqlite3_value] that contains the value of the Nth column of 10399 ** the table row after it is updated. The N parameter must be between 0 10400 ** and one less than the number of columns or the behavior will be 10401 ** undefined. This must only be used within SQLITE_INSERT and SQLITE_UPDATE 10402 ** preupdate callbacks; if it is used by an SQLITE_DELETE callback then the 10403 ** behavior is undefined. The [sqlite3_value] that P points to 10404 ** will be destroyed when the preupdate callback returns. 10405 ** 10406 ** ^The [sqlite3_preupdate_depth(D)] interface returns 0 if the preupdate 10407 ** callback was invoked as a result of a direct insert, update, or delete 10408 ** operation; or 1 for inserts, updates, or deletes invoked by top-level 10409 ** triggers; or 2 for changes resulting from triggers called by top-level 10410 ** triggers; and so forth. 10411 ** 10412 ** When the [sqlite3_blob_write()] API is used to update a blob column, 10413 ** the pre-update hook is invoked with SQLITE_DELETE. This is because the 10414 ** in this case the new values are not available. In this case, when a 10415 ** callback made with op==SQLITE_DELETE is actually a write using the 10416 ** sqlite3_blob_write() API, the [sqlite3_preupdate_blobwrite()] returns 10417 ** the index of the column being written. In other cases, where the 10418 ** pre-update hook is being invoked for some other reason, including a 10419 ** regular DELETE, sqlite3_preupdate_blobwrite() returns -1. 10420 ** 10421 ** See also: [sqlite3_update_hook()] 10422 */ 10423 #if defined(SQLITE_ENABLE_PREUPDATE_HOOK) 10424 SQLITE_API void *sqlite3_preupdate_hook( 10425 sqlite3 *db, 10426 void(*xPreUpdate)( 10427 void *pCtx, /* Copy of third arg to preupdate_hook() */ 10428 sqlite3 *db, /* Database handle */ 10429 int op, /* SQLITE_UPDATE, DELETE or INSERT */ 10430 char const *zDb, /* Database name */ 10431 char const *zName, /* Table name */ 10432 sqlite3_int64 iKey1, /* Rowid of row about to be deleted/updated */ 10433 sqlite3_int64 iKey2 /* New rowid value (for a rowid UPDATE) */ 10434 ), 10435 void* 10436 ); 10437 SQLITE_API int sqlite3_preupdate_old(sqlite3 *, int, sqlite3_value **); 10438 SQLITE_API int sqlite3_preupdate_count(sqlite3 *); 10439 SQLITE_API int sqlite3_preupdate_depth(sqlite3 *); 10440 SQLITE_API int sqlite3_preupdate_new(sqlite3 *, int, sqlite3_value **); 10441 SQLITE_API int sqlite3_preupdate_blobwrite(sqlite3 *); 10442 #endif 10443 10444 /* 10445 ** CAPI3REF: Low-level system error code 10446 ** METHOD: sqlite3 10447 ** 10448 ** ^Attempt to return the underlying operating system error code or error 10449 ** number that caused the most recent I/O error or failure to open a file. 10450 ** The return value is OS-dependent. For example, on unix systems, after 10451 ** [sqlite3_open_v2()] returns [SQLITE_CANTOPEN], this interface could be 10452 ** called to get back the underlying "errno" that caused the problem, such 10453 ** as ENOSPC, EAUTH, EISDIR, and so forth. 10454 */ 10455 SQLITE_API int sqlite3_system_errno(sqlite3*); 10456 10457 /* 10458 ** CAPI3REF: Database Snapshot 10459 ** KEYWORDS: {snapshot} {sqlite3_snapshot} 10460 ** 10461 ** An instance of the snapshot object records the state of a [WAL mode] 10462 ** database for some specific point in history. 10463 ** 10464 ** In [WAL mode], multiple [database connections] that are open on the 10465 ** same database file can each be reading a different historical version 10466 ** of the database file. When a [database connection] begins a read 10467 ** transaction, that connection sees an unchanging copy of the database 10468 ** as it existed for the point in time when the transaction first started. 10469 ** Subsequent changes to the database from other connections are not seen 10470 ** by the reader until a new read transaction is started. 10471 ** 10472 ** The sqlite3_snapshot object records state information about an historical 10473 ** version of the database file so that it is possible to later open a new read 10474 ** transaction that sees that historical version of the database rather than 10475 ** the most recent version. 10476 */ 10477 typedef struct sqlite3_snapshot { 10478 unsigned char hidden[48]; 10479 } sqlite3_snapshot; 10480 10481 /* 10482 ** CAPI3REF: Record A Database Snapshot 10483 ** CONSTRUCTOR: sqlite3_snapshot 10484 ** 10485 ** ^The [sqlite3_snapshot_get(D,S,P)] interface attempts to make a 10486 ** new [sqlite3_snapshot] object that records the current state of 10487 ** schema S in database connection D. ^On success, the 10488 ** [sqlite3_snapshot_get(D,S,P)] interface writes a pointer to the newly 10489 ** created [sqlite3_snapshot] object into *P and returns SQLITE_OK. 10490 ** If there is not already a read-transaction open on schema S when 10491 ** this function is called, one is opened automatically. 10492 ** 10493 ** The following must be true for this function to succeed. If any of 10494 ** the following statements are false when sqlite3_snapshot_get() is 10495 ** called, SQLITE_ERROR is returned. The final value of *P is undefined 10496 ** in this case. 10497 ** 10498 ** <ul> 10499 ** <li> The database handle must not be in [autocommit mode]. 10500 ** 10501 ** <li> Schema S of [database connection] D must be a [WAL mode] database. 10502 ** 10503 ** <li> There must not be a write transaction open on schema S of database 10504 ** connection D. 10505 ** 10506 ** <li> One or more transactions must have been written to the current wal 10507 ** file since it was created on disk (by any connection). This means 10508 ** that a snapshot cannot be taken on a wal mode database with no wal 10509 ** file immediately after it is first opened. At least one transaction 10510 ** must be written to it first. 10511 ** </ul> 10512 ** 10513 ** This function may also return SQLITE_NOMEM. If it is called with the 10514 ** database handle in autocommit mode but fails for some other reason, 10515 ** whether or not a read transaction is opened on schema S is undefined. 10516 ** 10517 ** The [sqlite3_snapshot] object returned from a successful call to 10518 ** [sqlite3_snapshot_get()] must be freed using [sqlite3_snapshot_free()] 10519 ** to avoid a memory leak. 10520 ** 10521 ** The [sqlite3_snapshot_get()] interface is only available when the 10522 ** [SQLITE_ENABLE_SNAPSHOT] compile-time option is used. 10523 */ 10524 SQLITE_API SQLITE_EXPERIMENTAL int sqlite3_snapshot_get( 10525 sqlite3 *db, 10526 const char *zSchema, 10527 sqlite3_snapshot **ppSnapshot 10528 ); 10529 10530 /* 10531 ** CAPI3REF: Start a read transaction on an historical snapshot 10532 ** METHOD: sqlite3_snapshot 10533 ** 10534 ** ^The [sqlite3_snapshot_open(D,S,P)] interface either starts a new read 10535 ** transaction or upgrades an existing one for schema S of 10536 ** [database connection] D such that the read transaction refers to 10537 ** historical [snapshot] P, rather than the most recent change to the 10538 ** database. ^The [sqlite3_snapshot_open()] interface returns SQLITE_OK 10539 ** on success or an appropriate [error code] if it fails. 10540 ** 10541 ** ^In order to succeed, the database connection must not be in 10542 ** [autocommit mode] when [sqlite3_snapshot_open(D,S,P)] is called. If there 10543 ** is already a read transaction open on schema S, then the database handle 10544 ** must have no active statements (SELECT statements that have been passed 10545 ** to sqlite3_step() but not sqlite3_reset() or sqlite3_finalize()). 10546 ** SQLITE_ERROR is returned if either of these conditions is violated, or 10547 ** if schema S does not exist, or if the snapshot object is invalid. 10548 ** 10549 ** ^A call to sqlite3_snapshot_open() will fail to open if the specified 10550 ** snapshot has been overwritten by a [checkpoint]. In this case 10551 ** SQLITE_ERROR_SNAPSHOT is returned. 10552 ** 10553 ** If there is already a read transaction open when this function is 10554 ** invoked, then the same read transaction remains open (on the same 10555 ** database snapshot) if SQLITE_ERROR, SQLITE_BUSY or SQLITE_ERROR_SNAPSHOT 10556 ** is returned. If another error code - for example SQLITE_PROTOCOL or an 10557 ** SQLITE_IOERR error code - is returned, then the final state of the 10558 ** read transaction is undefined. If SQLITE_OK is returned, then the 10559 ** read transaction is now open on database snapshot P. 10560 ** 10561 ** ^(A call to [sqlite3_snapshot_open(D,S,P)] will fail if the 10562 ** database connection D does not know that the database file for 10563 ** schema S is in [WAL mode]. A database connection might not know 10564 ** that the database file is in [WAL mode] if there has been no prior 10565 ** I/O on that database connection, or if the database entered [WAL mode] 10566 ** after the most recent I/O on the database connection.)^ 10567 ** (Hint: Run "[PRAGMA application_id]" against a newly opened 10568 ** database connection in order to make it ready to use snapshots.) 10569 ** 10570 ** The [sqlite3_snapshot_open()] interface is only available when the 10571 ** [SQLITE_ENABLE_SNAPSHOT] compile-time option is used. 10572 */ 10573 SQLITE_API SQLITE_EXPERIMENTAL int sqlite3_snapshot_open( 10574 sqlite3 *db, 10575 const char *zSchema, 10576 sqlite3_snapshot *pSnapshot 10577 ); 10578 10579 /* 10580 ** CAPI3REF: Destroy a snapshot 10581 ** DESTRUCTOR: sqlite3_snapshot 10582 ** 10583 ** ^The [sqlite3_snapshot_free(P)] interface destroys [sqlite3_snapshot] P. 10584 ** The application must eventually free every [sqlite3_snapshot] object 10585 ** using this routine to avoid a memory leak. 10586 ** 10587 ** The [sqlite3_snapshot_free()] interface is only available when the 10588 ** [SQLITE_ENABLE_SNAPSHOT] compile-time option is used. 10589 */ 10590 SQLITE_API SQLITE_EXPERIMENTAL void sqlite3_snapshot_free(sqlite3_snapshot*); 10591 10592 /* 10593 ** CAPI3REF: Compare the ages of two snapshot handles. 10594 ** METHOD: sqlite3_snapshot 10595 ** 10596 ** The sqlite3_snapshot_cmp(P1, P2) interface is used to compare the ages 10597 ** of two valid snapshot handles. 10598 ** 10599 ** If the two snapshot handles are not associated with the same database 10600 ** file, the result of the comparison is undefined. 10601 ** 10602 ** Additionally, the result of the comparison is only valid if both of the 10603 ** snapshot handles were obtained by calling sqlite3_snapshot_get() since the 10604 ** last time the wal file was deleted. The wal file is deleted when the 10605 ** database is changed back to rollback mode or when the number of database 10606 ** clients drops to zero. If either snapshot handle was obtained before the 10607 ** wal file was last deleted, the value returned by this function 10608 ** is undefined. 10609 ** 10610 ** Otherwise, this API returns a negative value if P1 refers to an older 10611 ** snapshot than P2, zero if the two handles refer to the same database 10612 ** snapshot, and a positive value if P1 is a newer snapshot than P2. 10613 ** 10614 ** This interface is only available if SQLite is compiled with the 10615 ** [SQLITE_ENABLE_SNAPSHOT] option. 10616 */ 10617 SQLITE_API SQLITE_EXPERIMENTAL int sqlite3_snapshot_cmp( 10618 sqlite3_snapshot *p1, 10619 sqlite3_snapshot *p2 10620 ); 10621 10622 /* 10623 ** CAPI3REF: Recover snapshots from a wal file 10624 ** METHOD: sqlite3_snapshot 10625 ** 10626 ** If a [WAL file] remains on disk after all database connections close 10627 ** (either through the use of the [SQLITE_FCNTL_PERSIST_WAL] [file control] 10628 ** or because the last process to have the database opened exited without 10629 ** calling [sqlite3_close()]) and a new connection is subsequently opened 10630 ** on that database and [WAL file], the [sqlite3_snapshot_open()] interface 10631 ** will only be able to open the last transaction added to the WAL file 10632 ** even though the WAL file contains other valid transactions. 10633 ** 10634 ** This function attempts to scan the WAL file associated with database zDb 10635 ** of database handle db and make all valid snapshots available to 10636 ** sqlite3_snapshot_open(). It is an error if there is already a read 10637 ** transaction open on the database, or if the database is not a WAL mode 10638 ** database. 10639 ** 10640 ** SQLITE_OK is returned if successful, or an SQLite error code otherwise. 10641 ** 10642 ** This interface is only available if SQLite is compiled with the 10643 ** [SQLITE_ENABLE_SNAPSHOT] option. 10644 */ 10645 SQLITE_API SQLITE_EXPERIMENTAL int sqlite3_snapshot_recover(sqlite3 *db, const char *zDb); 10646 10647 /* 10648 ** CAPI3REF: Serialize a database 10649 ** 10650 ** The sqlite3_serialize(D,S,P,F) interface returns a pointer to memory 10651 ** that is a serialization of the S database on [database connection] D. 10652 ** If P is not a NULL pointer, then the size of the database in bytes 10653 ** is written into *P. 10654 ** 10655 ** For an ordinary on-disk database file, the serialization is just a 10656 ** copy of the disk file. For an in-memory database or a "TEMP" database, 10657 ** the serialization is the same sequence of bytes which would be written 10658 ** to disk if that database where backed up to disk. 10659 ** 10660 ** The usual case is that sqlite3_serialize() copies the serialization of 10661 ** the database into memory obtained from [sqlite3_malloc64()] and returns 10662 ** a pointer to that memory. The caller is responsible for freeing the 10663 ** returned value to avoid a memory leak. However, if the F argument 10664 ** contains the SQLITE_SERIALIZE_NOCOPY bit, then no memory allocations 10665 ** are made, and the sqlite3_serialize() function will return a pointer 10666 ** to the contiguous memory representation of the database that SQLite 10667 ** is currently using for that database, or NULL if the no such contiguous 10668 ** memory representation of the database exists. A contiguous memory 10669 ** representation of the database will usually only exist if there has 10670 ** been a prior call to [sqlite3_deserialize(D,S,...)] with the same 10671 ** values of D and S. 10672 ** The size of the database is written into *P even if the 10673 ** SQLITE_SERIALIZE_NOCOPY bit is set but no contiguous copy 10674 ** of the database exists. 10675 ** 10676 ** After the call, if the SQLITE_SERIALIZE_NOCOPY bit had been set, 10677 ** the returned buffer content will remain accessible and unchanged 10678 ** until either the next write operation on the connection or when 10679 ** the connection is closed, and applications must not modify the 10680 ** buffer. If the bit had been clear, the returned buffer will not 10681 ** be accessed by SQLite after the call. 10682 ** 10683 ** A call to sqlite3_serialize(D,S,P,F) might return NULL even if the 10684 ** SQLITE_SERIALIZE_NOCOPY bit is omitted from argument F if a memory 10685 ** allocation error occurs. 10686 ** 10687 ** This interface is omitted if SQLite is compiled with the 10688 ** [SQLITE_OMIT_DESERIALIZE] option. 10689 */ 10690 SQLITE_API unsigned char *sqlite3_serialize( 10691 sqlite3 *db, /* The database connection */ 10692 const char *zSchema, /* Which DB to serialize. ex: "main", "temp", ... */ 10693 sqlite3_int64 *piSize, /* Write size of the DB here, if not NULL */ 10694 unsigned int mFlags /* Zero or more SQLITE_SERIALIZE_* flags */ 10695 ); 10696 10697 /* 10698 ** CAPI3REF: Flags for sqlite3_serialize 10699 ** 10700 ** Zero or more of the following constants can be OR-ed together for 10701 ** the F argument to [sqlite3_serialize(D,S,P,F)]. 10702 ** 10703 ** SQLITE_SERIALIZE_NOCOPY means that [sqlite3_serialize()] will return 10704 ** a pointer to contiguous in-memory database that it is currently using, 10705 ** without making a copy of the database. If SQLite is not currently using 10706 ** a contiguous in-memory database, then this option causes 10707 ** [sqlite3_serialize()] to return a NULL pointer. SQLite will only be 10708 ** using a contiguous in-memory database if it has been initialized by a 10709 ** prior call to [sqlite3_deserialize()]. 10710 */ 10711 #define SQLITE_SERIALIZE_NOCOPY 0x001 /* Do no memory allocations */ 10712 10713 /* 10714 ** CAPI3REF: Deserialize a database 10715 ** 10716 ** The sqlite3_deserialize(D,S,P,N,M,F) interface causes the 10717 ** [database connection] D to disconnect from database S and then 10718 ** reopen S as an in-memory database based on the serialization contained 10719 ** in P. The serialized database P is N bytes in size. M is the size of 10720 ** the buffer P, which might be larger than N. If M is larger than N, and 10721 ** the SQLITE_DESERIALIZE_READONLY bit is not set in F, then SQLite is 10722 ** permitted to add content to the in-memory database as long as the total 10723 ** size does not exceed M bytes. 10724 ** 10725 ** If the SQLITE_DESERIALIZE_FREEONCLOSE bit is set in F, then SQLite will 10726 ** invoke sqlite3_free() on the serialization buffer when the database 10727 ** connection closes. If the SQLITE_DESERIALIZE_RESIZEABLE bit is set, then 10728 ** SQLite will try to increase the buffer size using sqlite3_realloc64() 10729 ** if writes on the database cause it to grow larger than M bytes. 10730 ** 10731 ** Applications must not modify the buffer P or invalidate it before 10732 ** the database connection D is closed. 10733 ** 10734 ** The sqlite3_deserialize() interface will fail with SQLITE_BUSY if the 10735 ** database is currently in a read transaction or is involved in a backup 10736 ** operation. 10737 ** 10738 ** It is not possible to deserialized into the TEMP database. If the 10739 ** S argument to sqlite3_deserialize(D,S,P,N,M,F) is "temp" then the 10740 ** function returns SQLITE_ERROR. 10741 ** 10742 ** The deserialized database should not be in [WAL mode]. If the database 10743 ** is in WAL mode, then any attempt to use the database file will result 10744 ** in an [SQLITE_CANTOPEN] error. The application can set the 10745 ** [file format version numbers] (bytes 18 and 19) of the input database P 10746 ** to 0x01 prior to invoking sqlite3_deserialize(D,S,P,N,M,F) to force the 10747 ** database file into rollback mode and work around this limitation. 10748 ** 10749 ** If sqlite3_deserialize(D,S,P,N,M,F) fails for any reason and if the 10750 ** SQLITE_DESERIALIZE_FREEONCLOSE bit is set in argument F, then 10751 ** [sqlite3_free()] is invoked on argument P prior to returning. 10752 ** 10753 ** This interface is omitted if SQLite is compiled with the 10754 ** [SQLITE_OMIT_DESERIALIZE] option. 10755 */ 10756 SQLITE_API int sqlite3_deserialize( 10757 sqlite3 *db, /* The database connection */ 10758 const char *zSchema, /* Which DB to reopen with the deserialization */ 10759 unsigned char *pData, /* The serialized database content */ 10760 sqlite3_int64 szDb, /* Number bytes in the deserialization */ 10761 sqlite3_int64 szBuf, /* Total size of buffer pData[] */ 10762 unsigned mFlags /* Zero or more SQLITE_DESERIALIZE_* flags */ 10763 ); 10764 10765 /* 10766 ** CAPI3REF: Flags for sqlite3_deserialize() 10767 ** 10768 ** The following are allowed values for 6th argument (the F argument) to 10769 ** the [sqlite3_deserialize(D,S,P,N,M,F)] interface. 10770 ** 10771 ** The SQLITE_DESERIALIZE_FREEONCLOSE means that the database serialization 10772 ** in the P argument is held in memory obtained from [sqlite3_malloc64()] 10773 ** and that SQLite should take ownership of this memory and automatically 10774 ** free it when it has finished using it. Without this flag, the caller 10775 ** is responsible for freeing any dynamically allocated memory. 10776 ** 10777 ** The SQLITE_DESERIALIZE_RESIZEABLE flag means that SQLite is allowed to 10778 ** grow the size of the database using calls to [sqlite3_realloc64()]. This 10779 ** flag should only be used if SQLITE_DESERIALIZE_FREEONCLOSE is also used. 10780 ** Without this flag, the deserialized database cannot increase in size beyond 10781 ** the number of bytes specified by the M parameter. 10782 ** 10783 ** The SQLITE_DESERIALIZE_READONLY flag means that the deserialized database 10784 ** should be treated as read-only. 10785 */ 10786 #define SQLITE_DESERIALIZE_FREEONCLOSE 1 /* Call sqlite3_free() on close */ 10787 #define SQLITE_DESERIALIZE_RESIZEABLE 2 /* Resize using sqlite3_realloc64() */ 10788 #define SQLITE_DESERIALIZE_READONLY 4 /* Database is read-only */ 10789 10790 /* 10791 ** Undo the hack that converts floating point types to integer for 10792 ** builds on processors without floating point support. 10793 */ 10794 #ifdef SQLITE_OMIT_FLOATING_POINT 10795 # undef double 10796 #endif 10797 10798 #if defined(__wasi__) 10799 # undef SQLITE_WASI 10800 # define SQLITE_WASI 1 10801 # undef SQLITE_OMIT_WAL 10802 # define SQLITE_OMIT_WAL 1/* because it requires shared memory APIs */ 10803 # ifndef SQLITE_OMIT_LOAD_EXTENSION 10804 # define SQLITE_OMIT_LOAD_EXTENSION 10805 # endif 10806 # ifndef SQLITE_THREADSAFE 10807 # define SQLITE_THREADSAFE 0 10808 # endif 10809 #endif 10810 10811 #ifdef __cplusplus 10812 } /* End of the 'extern "C"' block */ 10813 #endif 10814 #endif /* SQLITE3_H */ 10815 10816 /******** Begin file sqlite3rtree.h *********/ 10817 /* 10818 ** 2010 August 30 10819 ** 10820 ** The author disclaims copyright to this source code. In place of 10821 ** a legal notice, here is a blessing: 10822 ** 10823 ** May you do good and not evil. 10824 ** May you find forgiveness for yourself and forgive others. 10825 ** May you share freely, never taking more than you give. 10826 ** 10827 ************************************************************************* 10828 */ 10829 10830 #ifndef _SQLITE3RTREE_H_ 10831 #define _SQLITE3RTREE_H_ 10832 10833 10834 #ifdef __cplusplus 10835 extern "C" { 10836 #endif 10837 10838 typedef struct sqlite3_rtree_geometry sqlite3_rtree_geometry; 10839 typedef struct sqlite3_rtree_query_info sqlite3_rtree_query_info; 10840 10841 /* The double-precision datatype used by RTree depends on the 10842 ** SQLITE_RTREE_INT_ONLY compile-time option. 10843 */ 10844 #ifdef SQLITE_RTREE_INT_ONLY 10845 typedef sqlite3_int64 sqlite3_rtree_dbl; 10846 #else 10847 typedef double sqlite3_rtree_dbl; 10848 #endif 10849 10850 /* 10851 ** Register a geometry callback named zGeom that can be used as part of an 10852 ** R-Tree geometry query as follows: 10853 ** 10854 ** SELECT ... FROM <rtree> WHERE <rtree col> MATCH $zGeom(... params ...) 10855 */ 10856 SQLITE_API int sqlite3_rtree_geometry_callback( 10857 sqlite3 *db, 10858 const char *zGeom, 10859 int (*xGeom)(sqlite3_rtree_geometry*, int, sqlite3_rtree_dbl*,int*), 10860 void *pContext 10861 ); 10862 10863 10864 /* 10865 ** A pointer to a structure of the following type is passed as the first 10866 ** argument to callbacks registered using rtree_geometry_callback(). 10867 */ 10868 struct sqlite3_rtree_geometry { 10869 void *pContext; /* Copy of pContext passed to s_r_g_c() */ 10870 int nParam; /* Size of array aParam[] */ 10871 sqlite3_rtree_dbl *aParam; /* Parameters passed to SQL geom function */ 10872 void *pUser; /* Callback implementation user data */ 10873 void (*xDelUser)(void *); /* Called by SQLite to clean up pUser */ 10874 }; 10875 10876 /* 10877 ** Register a 2nd-generation geometry callback named zScore that can be 10878 ** used as part of an R-Tree geometry query as follows: 10879 ** 10880 ** SELECT ... FROM <rtree> WHERE <rtree col> MATCH $zQueryFunc(... params ...) 10881 */ 10882 SQLITE_API int sqlite3_rtree_query_callback( 10883 sqlite3 *db, 10884 const char *zQueryFunc, 10885 int (*xQueryFunc)(sqlite3_rtree_query_info*), 10886 void *pContext, 10887 void (*xDestructor)(void*) 10888 ); 10889 10890 10891 /* 10892 ** A pointer to a structure of the following type is passed as the 10893 ** argument to scored geometry callback registered using 10894 ** sqlite3_rtree_query_callback(). 10895 ** 10896 ** Note that the first 5 fields of this structure are identical to 10897 ** sqlite3_rtree_geometry. This structure is a subclass of 10898 ** sqlite3_rtree_geometry. 10899 */ 10900 struct sqlite3_rtree_query_info { 10901 void *pContext; /* pContext from when function registered */ 10902 int nParam; /* Number of function parameters */ 10903 sqlite3_rtree_dbl *aParam; /* value of function parameters */ 10904 void *pUser; /* callback can use this, if desired */ 10905 void (*xDelUser)(void*); /* function to free pUser */ 10906 sqlite3_rtree_dbl *aCoord; /* Coordinates of node or entry to check */ 10907 unsigned int *anQueue; /* Number of pending entries in the queue */ 10908 int nCoord; /* Number of coordinates */ 10909 int iLevel; /* Level of current node or entry */ 10910 int mxLevel; /* The largest iLevel value in the tree */ 10911 sqlite3_int64 iRowid; /* Rowid for current entry */ 10912 sqlite3_rtree_dbl rParentScore; /* Score of parent node */ 10913 int eParentWithin; /* Visibility of parent node */ 10914 int eWithin; /* OUT: Visibility */ 10915 sqlite3_rtree_dbl rScore; /* OUT: Write the score here */ 10916 /* The following fields are only available in 3.8.11 and later */ 10917 sqlite3_value **apSqlParam; /* Original SQL values of parameters */ 10918 }; 10919 10920 /* 10921 ** Allowed values for sqlite3_rtree_query.eWithin and .eParentWithin. 10922 */ 10923 #define NOT_WITHIN 0 /* Object completely outside of query region */ 10924 #define PARTLY_WITHIN 1 /* Object partially overlaps query region */ 10925 #define FULLY_WITHIN 2 /* Object fully contained within query region */ 10926 10927 10928 #ifdef __cplusplus 10929 } /* end of the 'extern "C"' block */ 10930 #endif 10931 10932 #endif /* ifndef _SQLITE3RTREE_H_ */ 10933 10934 /******** End of sqlite3rtree.h *********/ 10935 /******** Begin file sqlite3session.h *********/ 10936 10937 #if !defined(__SQLITESESSION_H_) && defined(SQLITE_ENABLE_SESSION) 10938 #define __SQLITESESSION_H_ 1 10939 10940 /* 10941 ** Make sure we can call this stuff from C++. 10942 */ 10943 #ifdef __cplusplus 10944 extern "C" { 10945 #endif 10946 10947 10948 /* 10949 ** CAPI3REF: Session Object Handle 10950 ** 10951 ** An instance of this object is a [session] that can be used to 10952 ** record changes to a database. 10953 */ 10954 typedef struct sqlite3_session sqlite3_session; 10955 10956 /* 10957 ** CAPI3REF: Changeset Iterator Handle 10958 ** 10959 ** An instance of this object acts as a cursor for iterating 10960 ** over the elements of a [changeset] or [patchset]. 10961 */ 10962 typedef struct sqlite3_changeset_iter sqlite3_changeset_iter; 10963 10964 /* 10965 ** CAPI3REF: Create A New Session Object 10966 ** CONSTRUCTOR: sqlite3_session 10967 ** 10968 ** Create a new session object attached to database handle db. If successful, 10969 ** a pointer to the new object is written to *ppSession and SQLITE_OK is 10970 ** returned. If an error occurs, *ppSession is set to NULL and an SQLite 10971 ** error code (e.g. SQLITE_NOMEM) is returned. 10972 ** 10973 ** It is possible to create multiple session objects attached to a single 10974 ** database handle. 10975 ** 10976 ** Session objects created using this function should be deleted using the 10977 ** [sqlite3session_delete()] function before the database handle that they 10978 ** are attached to is itself closed. If the database handle is closed before 10979 ** the session object is deleted, then the results of calling any session 10980 ** module function, including [sqlite3session_delete()] on the session object 10981 ** are undefined. 10982 ** 10983 ** Because the session module uses the [sqlite3_preupdate_hook()] API, it 10984 ** is not possible for an application to register a pre-update hook on a 10985 ** database handle that has one or more session objects attached. Nor is 10986 ** it possible to create a session object attached to a database handle for 10987 ** which a pre-update hook is already defined. The results of attempting 10988 ** either of these things are undefined. 10989 ** 10990 ** The session object will be used to create changesets for tables in 10991 ** database zDb, where zDb is either "main", or "temp", or the name of an 10992 ** attached database. It is not an error if database zDb is not attached 10993 ** to the database when the session object is created. 10994 */ 10995 SQLITE_API int sqlite3session_create( 10996 sqlite3 *db, /* Database handle */ 10997 const char *zDb, /* Name of db (e.g. "main") */ 10998 sqlite3_session **ppSession /* OUT: New session object */ 10999 ); 11000 11001 /* 11002 ** CAPI3REF: Delete A Session Object 11003 ** DESTRUCTOR: sqlite3_session 11004 ** 11005 ** Delete a session object previously allocated using 11006 ** [sqlite3session_create()]. Once a session object has been deleted, the 11007 ** results of attempting to use pSession with any other session module 11008 ** function are undefined. 11009 ** 11010 ** Session objects must be deleted before the database handle to which they 11011 ** are attached is closed. Refer to the documentation for 11012 ** [sqlite3session_create()] for details. 11013 */ 11014 SQLITE_API void sqlite3session_delete(sqlite3_session *pSession); 11015 11016 /* 11017 ** CAPI3REF: Configure a Session Object 11018 ** METHOD: sqlite3_session 11019 ** 11020 ** This method is used to configure a session object after it has been 11021 ** created. At present the only valid values for the second parameter are 11022 ** [SQLITE_SESSION_OBJCONFIG_SIZE] and [SQLITE_SESSION_OBJCONFIG_ROWID]. 11023 ** 11024 */ 11025 SQLITE_API int sqlite3session_object_config(sqlite3_session*, int op, void *pArg); 11026 11027 /* 11028 ** CAPI3REF: Options for sqlite3session_object_config 11029 ** 11030 ** The following values may passed as the the 2nd parameter to 11031 ** sqlite3session_object_config(). 11032 ** 11033 ** <dt>SQLITE_SESSION_OBJCONFIG_SIZE <dd> 11034 ** This option is used to set, clear or query the flag that enables 11035 ** the [sqlite3session_changeset_size()] API. Because it imposes some 11036 ** computational overhead, this API is disabled by default. Argument 11037 ** pArg must point to a value of type (int). If the value is initially 11038 ** 0, then the sqlite3session_changeset_size() API is disabled. If it 11039 ** is greater than 0, then the same API is enabled. Or, if the initial 11040 ** value is less than zero, no change is made. In all cases the (int) 11041 ** variable is set to 1 if the sqlite3session_changeset_size() API is 11042 ** enabled following the current call, or 0 otherwise. 11043 ** 11044 ** It is an error (SQLITE_MISUSE) to attempt to modify this setting after 11045 ** the first table has been attached to the session object. 11046 ** 11047 ** <dt>SQLITE_SESSION_OBJCONFIG_ROWID <dd> 11048 ** This option is used to set, clear or query the flag that enables 11049 ** collection of data for tables with no explicit PRIMARY KEY. 11050 ** 11051 ** Normally, tables with no explicit PRIMARY KEY are simply ignored 11052 ** by the sessions module. However, if this flag is set, it behaves 11053 ** as if such tables have a column "_rowid_ INTEGER PRIMARY KEY" inserted 11054 ** as their leftmost columns. 11055 ** 11056 ** It is an error (SQLITE_MISUSE) to attempt to modify this setting after 11057 ** the first table has been attached to the session object. 11058 */ 11059 #define SQLITE_SESSION_OBJCONFIG_SIZE 1 11060 #define SQLITE_SESSION_OBJCONFIG_ROWID 2 11061 11062 /* 11063 ** CAPI3REF: Enable Or Disable A Session Object 11064 ** METHOD: sqlite3_session 11065 ** 11066 ** Enable or disable the recording of changes by a session object. When 11067 ** enabled, a session object records changes made to the database. When 11068 ** disabled - it does not. A newly created session object is enabled. 11069 ** Refer to the documentation for [sqlite3session_changeset()] for further 11070 ** details regarding how enabling and disabling a session object affects 11071 ** the eventual changesets. 11072 ** 11073 ** Passing zero to this function disables the session. Passing a value 11074 ** greater than zero enables it. Passing a value less than zero is a 11075 ** no-op, and may be used to query the current state of the session. 11076 ** 11077 ** The return value indicates the final state of the session object: 0 if 11078 ** the session is disabled, or 1 if it is enabled. 11079 */ 11080 SQLITE_API int sqlite3session_enable(sqlite3_session *pSession, int bEnable); 11081 11082 /* 11083 ** CAPI3REF: Set Or Clear the Indirect Change Flag 11084 ** METHOD: sqlite3_session 11085 ** 11086 ** Each change recorded by a session object is marked as either direct or 11087 ** indirect. A change is marked as indirect if either: 11088 ** 11089 ** <ul> 11090 ** <li> The session object "indirect" flag is set when the change is 11091 ** made, or 11092 ** <li> The change is made by an SQL trigger or foreign key action 11093 ** instead of directly as a result of a users SQL statement. 11094 ** </ul> 11095 ** 11096 ** If a single row is affected by more than one operation within a session, 11097 ** then the change is considered indirect if all operations meet the criteria 11098 ** for an indirect change above, or direct otherwise. 11099 ** 11100 ** This function is used to set, clear or query the session object indirect 11101 ** flag. If the second argument passed to this function is zero, then the 11102 ** indirect flag is cleared. If it is greater than zero, the indirect flag 11103 ** is set. Passing a value less than zero does not modify the current value 11104 ** of the indirect flag, and may be used to query the current state of the 11105 ** indirect flag for the specified session object. 11106 ** 11107 ** The return value indicates the final state of the indirect flag: 0 if 11108 ** it is clear, or 1 if it is set. 11109 */ 11110 SQLITE_API int sqlite3session_indirect(sqlite3_session *pSession, int bIndirect); 11111 11112 /* 11113 ** CAPI3REF: Attach A Table To A Session Object 11114 ** METHOD: sqlite3_session 11115 ** 11116 ** If argument zTab is not NULL, then it is the name of a table to attach 11117 ** to the session object passed as the first argument. All subsequent changes 11118 ** made to the table while the session object is enabled will be recorded. See 11119 ** documentation for [sqlite3session_changeset()] for further details. 11120 ** 11121 ** Or, if argument zTab is NULL, then changes are recorded for all tables 11122 ** in the database. If additional tables are added to the database (by 11123 ** executing "CREATE TABLE" statements) after this call is made, changes for 11124 ** the new tables are also recorded. 11125 ** 11126 ** Changes can only be recorded for tables that have a PRIMARY KEY explicitly 11127 ** defined as part of their CREATE TABLE statement. It does not matter if the 11128 ** PRIMARY KEY is an "INTEGER PRIMARY KEY" (rowid alias) or not. The PRIMARY 11129 ** KEY may consist of a single column, or may be a composite key. 11130 ** 11131 ** It is not an error if the named table does not exist in the database. Nor 11132 ** is it an error if the named table does not have a PRIMARY KEY. However, 11133 ** no changes will be recorded in either of these scenarios. 11134 ** 11135 ** Changes are not recorded for individual rows that have NULL values stored 11136 ** in one or more of their PRIMARY KEY columns. 11137 ** 11138 ** SQLITE_OK is returned if the call completes without error. Or, if an error 11139 ** occurs, an SQLite error code (e.g. SQLITE_NOMEM) is returned. 11140 ** 11141 ** <h3>Special sqlite_stat1 Handling</h3> 11142 ** 11143 ** As of SQLite version 3.22.0, the "sqlite_stat1" table is an exception to 11144 ** some of the rules above. In SQLite, the schema of sqlite_stat1 is: 11145 ** <pre> 11146 ** CREATE TABLE sqlite_stat1(tbl,idx,stat) 11147 ** </pre> 11148 ** 11149 ** Even though sqlite_stat1 does not have a PRIMARY KEY, changes are 11150 ** recorded for it as if the PRIMARY KEY is (tbl,idx). Additionally, changes 11151 ** are recorded for rows for which (idx IS NULL) is true. However, for such 11152 ** rows a zero-length blob (SQL value X'') is stored in the changeset or 11153 ** patchset instead of a NULL value. This allows such changesets to be 11154 ** manipulated by legacy implementations of sqlite3changeset_invert(), 11155 ** concat() and similar. 11156 ** 11157 ** The sqlite3changeset_apply() function automatically converts the 11158 ** zero-length blob back to a NULL value when updating the sqlite_stat1 11159 ** table. However, if the application calls sqlite3changeset_new(), 11160 ** sqlite3changeset_old() or sqlite3changeset_conflict on a changeset 11161 ** iterator directly (including on a changeset iterator passed to a 11162 ** conflict-handler callback) then the X'' value is returned. The application 11163 ** must translate X'' to NULL itself if required. 11164 ** 11165 ** Legacy (older than 3.22.0) versions of the sessions module cannot capture 11166 ** changes made to the sqlite_stat1 table. Legacy versions of the 11167 ** sqlite3changeset_apply() function silently ignore any modifications to the 11168 ** sqlite_stat1 table that are part of a changeset or patchset. 11169 */ 11170 SQLITE_API int sqlite3session_attach( 11171 sqlite3_session *pSession, /* Session object */ 11172 const char *zTab /* Table name */ 11173 ); 11174 11175 /* 11176 ** CAPI3REF: Set a table filter on a Session Object. 11177 ** METHOD: sqlite3_session 11178 ** 11179 ** The second argument (xFilter) is the "filter callback". For changes to rows 11180 ** in tables that are not attached to the Session object, the filter is called 11181 ** to determine whether changes to the table's rows should be tracked or not. 11182 ** If xFilter returns 0, changes are not tracked. Note that once a table is 11183 ** attached, xFilter will not be called again. 11184 */ 11185 SQLITE_API void sqlite3session_table_filter( 11186 sqlite3_session *pSession, /* Session object */ 11187 int(*xFilter)( 11188 void *pCtx, /* Copy of third arg to _filter_table() */ 11189 const char *zTab /* Table name */ 11190 ), 11191 void *pCtx /* First argument passed to xFilter */ 11192 ); 11193 11194 /* 11195 ** CAPI3REF: Generate A Changeset From A Session Object 11196 ** METHOD: sqlite3_session 11197 ** 11198 ** Obtain a changeset containing changes to the tables attached to the 11199 ** session object passed as the first argument. If successful, 11200 ** set *ppChangeset to point to a buffer containing the changeset 11201 ** and *pnChangeset to the size of the changeset in bytes before returning 11202 ** SQLITE_OK. If an error occurs, set both *ppChangeset and *pnChangeset to 11203 ** zero and return an SQLite error code. 11204 ** 11205 ** A changeset consists of zero or more INSERT, UPDATE and/or DELETE changes, 11206 ** each representing a change to a single row of an attached table. An INSERT 11207 ** change contains the values of each field of a new database row. A DELETE 11208 ** contains the original values of each field of a deleted database row. An 11209 ** UPDATE change contains the original values of each field of an updated 11210 ** database row along with the updated values for each updated non-primary-key 11211 ** column. It is not possible for an UPDATE change to represent a change that 11212 ** modifies the values of primary key columns. If such a change is made, it 11213 ** is represented in a changeset as a DELETE followed by an INSERT. 11214 ** 11215 ** Changes are not recorded for rows that have NULL values stored in one or 11216 ** more of their PRIMARY KEY columns. If such a row is inserted or deleted, 11217 ** no corresponding change is present in the changesets returned by this 11218 ** function. If an existing row with one or more NULL values stored in 11219 ** PRIMARY KEY columns is updated so that all PRIMARY KEY columns are non-NULL, 11220 ** only an INSERT is appears in the changeset. Similarly, if an existing row 11221 ** with non-NULL PRIMARY KEY values is updated so that one or more of its 11222 ** PRIMARY KEY columns are set to NULL, the resulting changeset contains a 11223 ** DELETE change only. 11224 ** 11225 ** The contents of a changeset may be traversed using an iterator created 11226 ** using the [sqlite3changeset_start()] API. A changeset may be applied to 11227 ** a database with a compatible schema using the [sqlite3changeset_apply()] 11228 ** API. 11229 ** 11230 ** Within a changeset generated by this function, all changes related to a 11231 ** single table are grouped together. In other words, when iterating through 11232 ** a changeset or when applying a changeset to a database, all changes related 11233 ** to a single table are processed before moving on to the next table. Tables 11234 ** are sorted in the same order in which they were attached (or auto-attached) 11235 ** to the sqlite3_session object. The order in which the changes related to 11236 ** a single table are stored is undefined. 11237 ** 11238 ** Following a successful call to this function, it is the responsibility of 11239 ** the caller to eventually free the buffer that *ppChangeset points to using 11240 ** [sqlite3_free()]. 11241 ** 11242 ** <h3>Changeset Generation</h3> 11243 ** 11244 ** Once a table has been attached to a session object, the session object 11245 ** records the primary key values of all new rows inserted into the table. 11246 ** It also records the original primary key and other column values of any 11247 ** deleted or updated rows. For each unique primary key value, data is only 11248 ** recorded once - the first time a row with said primary key is inserted, 11249 ** updated or deleted in the lifetime of the session. 11250 ** 11251 ** There is one exception to the previous paragraph: when a row is inserted, 11252 ** updated or deleted, if one or more of its primary key columns contain a 11253 ** NULL value, no record of the change is made. 11254 ** 11255 ** The session object therefore accumulates two types of records - those 11256 ** that consist of primary key values only (created when the user inserts 11257 ** a new record) and those that consist of the primary key values and the 11258 ** original values of other table columns (created when the users deletes 11259 ** or updates a record). 11260 ** 11261 ** When this function is called, the requested changeset is created using 11262 ** both the accumulated records and the current contents of the database 11263 ** file. Specifically: 11264 ** 11265 ** <ul> 11266 ** <li> For each record generated by an insert, the database is queried 11267 ** for a row with a matching primary key. If one is found, an INSERT 11268 ** change is added to the changeset. If no such row is found, no change 11269 ** is added to the changeset. 11270 ** 11271 ** <li> For each record generated by an update or delete, the database is 11272 ** queried for a row with a matching primary key. If such a row is 11273 ** found and one or more of the non-primary key fields have been 11274 ** modified from their original values, an UPDATE change is added to 11275 ** the changeset. Or, if no such row is found in the table, a DELETE 11276 ** change is added to the changeset. If there is a row with a matching 11277 ** primary key in the database, but all fields contain their original 11278 ** values, no change is added to the changeset. 11279 ** </ul> 11280 ** 11281 ** This means, amongst other things, that if a row is inserted and then later 11282 ** deleted while a session object is active, neither the insert nor the delete 11283 ** will be present in the changeset. Or if a row is deleted and then later a 11284 ** row with the same primary key values inserted while a session object is 11285 ** active, the resulting changeset will contain an UPDATE change instead of 11286 ** a DELETE and an INSERT. 11287 ** 11288 ** When a session object is disabled (see the [sqlite3session_enable()] API), 11289 ** it does not accumulate records when rows are inserted, updated or deleted. 11290 ** This may appear to have some counter-intuitive effects if a single row 11291 ** is written to more than once during a session. For example, if a row 11292 ** is inserted while a session object is enabled, then later deleted while 11293 ** the same session object is disabled, no INSERT record will appear in the 11294 ** changeset, even though the delete took place while the session was disabled. 11295 ** Or, if one field of a row is updated while a session is disabled, and 11296 ** another field of the same row is updated while the session is enabled, the 11297 ** resulting changeset will contain an UPDATE change that updates both fields. 11298 */ 11299 SQLITE_API int sqlite3session_changeset( 11300 sqlite3_session *pSession, /* Session object */ 11301 int *pnChangeset, /* OUT: Size of buffer at *ppChangeset */ 11302 void **ppChangeset /* OUT: Buffer containing changeset */ 11303 ); 11304 11305 /* 11306 ** CAPI3REF: Return An Upper-limit For The Size Of The Changeset 11307 ** METHOD: sqlite3_session 11308 ** 11309 ** By default, this function always returns 0. For it to return 11310 ** a useful result, the sqlite3_session object must have been configured 11311 ** to enable this API using sqlite3session_object_config() with the 11312 ** SQLITE_SESSION_OBJCONFIG_SIZE verb. 11313 ** 11314 ** When enabled, this function returns an upper limit, in bytes, for the size 11315 ** of the changeset that might be produced if sqlite3session_changeset() were 11316 ** called. The final changeset size might be equal to or smaller than the 11317 ** size in bytes returned by this function. 11318 */ 11319 SQLITE_API sqlite3_int64 sqlite3session_changeset_size(sqlite3_session *pSession); 11320 11321 /* 11322 ** CAPI3REF: Load The Difference Between Tables Into A Session 11323 ** METHOD: sqlite3_session 11324 ** 11325 ** If it is not already attached to the session object passed as the first 11326 ** argument, this function attaches table zTbl in the same manner as the 11327 ** [sqlite3session_attach()] function. If zTbl does not exist, or if it 11328 ** does not have a primary key, this function is a no-op (but does not return 11329 ** an error). 11330 ** 11331 ** Argument zFromDb must be the name of a database ("main", "temp" etc.) 11332 ** attached to the same database handle as the session object that contains 11333 ** a table compatible with the table attached to the session by this function. 11334 ** A table is considered compatible if it: 11335 ** 11336 ** <ul> 11337 ** <li> Has the same name, 11338 ** <li> Has the same set of columns declared in the same order, and 11339 ** <li> Has the same PRIMARY KEY definition. 11340 ** </ul> 11341 ** 11342 ** If the tables are not compatible, SQLITE_SCHEMA is returned. If the tables 11343 ** are compatible but do not have any PRIMARY KEY columns, it is not an error 11344 ** but no changes are added to the session object. As with other session 11345 ** APIs, tables without PRIMARY KEYs are simply ignored. 11346 ** 11347 ** This function adds a set of changes to the session object that could be 11348 ** used to update the table in database zFrom (call this the "from-table") 11349 ** so that its content is the same as the table attached to the session 11350 ** object (call this the "to-table"). Specifically: 11351 ** 11352 ** <ul> 11353 ** <li> For each row (primary key) that exists in the to-table but not in 11354 ** the from-table, an INSERT record is added to the session object. 11355 ** 11356 ** <li> For each row (primary key) that exists in the to-table but not in 11357 ** the from-table, a DELETE record is added to the session object. 11358 ** 11359 ** <li> For each row (primary key) that exists in both tables, but features 11360 ** different non-PK values in each, an UPDATE record is added to the 11361 ** session. 11362 ** </ul> 11363 ** 11364 ** To clarify, if this function is called and then a changeset constructed 11365 ** using [sqlite3session_changeset()], then after applying that changeset to 11366 ** database zFrom the contents of the two compatible tables would be 11367 ** identical. 11368 ** 11369 ** It an error if database zFrom does not exist or does not contain the 11370 ** required compatible table. 11371 ** 11372 ** If the operation is successful, SQLITE_OK is returned. Otherwise, an SQLite 11373 ** error code. In this case, if argument pzErrMsg is not NULL, *pzErrMsg 11374 ** may be set to point to a buffer containing an English language error 11375 ** message. It is the responsibility of the caller to free this buffer using 11376 ** sqlite3_free(). 11377 */ 11378 SQLITE_API int sqlite3session_diff( 11379 sqlite3_session *pSession, 11380 const char *zFromDb, 11381 const char *zTbl, 11382 char **pzErrMsg 11383 ); 11384 11385 11386 /* 11387 ** CAPI3REF: Generate A Patchset From A Session Object 11388 ** METHOD: sqlite3_session 11389 ** 11390 ** The differences between a patchset and a changeset are that: 11391 ** 11392 ** <ul> 11393 ** <li> DELETE records consist of the primary key fields only. The 11394 ** original values of other fields are omitted. 11395 ** <li> The original values of any modified fields are omitted from 11396 ** UPDATE records. 11397 ** </ul> 11398 ** 11399 ** A patchset blob may be used with up to date versions of all 11400 ** sqlite3changeset_xxx API functions except for sqlite3changeset_invert(), 11401 ** which returns SQLITE_CORRUPT if it is passed a patchset. Similarly, 11402 ** attempting to use a patchset blob with old versions of the 11403 ** sqlite3changeset_xxx APIs also provokes an SQLITE_CORRUPT error. 11404 ** 11405 ** Because the non-primary key "old.*" fields are omitted, no 11406 ** SQLITE_CHANGESET_DATA conflicts can be detected or reported if a patchset 11407 ** is passed to the sqlite3changeset_apply() API. Other conflict types work 11408 ** in the same way as for changesets. 11409 ** 11410 ** Changes within a patchset are ordered in the same way as for changesets 11411 ** generated by the sqlite3session_changeset() function (i.e. all changes for 11412 ** a single table are grouped together, tables appear in the order in which 11413 ** they were attached to the session object). 11414 */ 11415 SQLITE_API int sqlite3session_patchset( 11416 sqlite3_session *pSession, /* Session object */ 11417 int *pnPatchset, /* OUT: Size of buffer at *ppPatchset */ 11418 void **ppPatchset /* OUT: Buffer containing patchset */ 11419 ); 11420 11421 /* 11422 ** CAPI3REF: Test if a changeset has recorded any changes. 11423 ** 11424 ** Return non-zero if no changes to attached tables have been recorded by 11425 ** the session object passed as the first argument. Otherwise, if one or 11426 ** more changes have been recorded, return zero. 11427 ** 11428 ** Even if this function returns zero, it is possible that calling 11429 ** [sqlite3session_changeset()] on the session handle may still return a 11430 ** changeset that contains no changes. This can happen when a row in 11431 ** an attached table is modified and then later on the original values 11432 ** are restored. However, if this function returns non-zero, then it is 11433 ** guaranteed that a call to sqlite3session_changeset() will return a 11434 ** changeset containing zero changes. 11435 */ 11436 SQLITE_API int sqlite3session_isempty(sqlite3_session *pSession); 11437 11438 /* 11439 ** CAPI3REF: Query for the amount of heap memory used by a session object. 11440 ** 11441 ** This API returns the total amount of heap memory in bytes currently 11442 ** used by the session object passed as the only argument. 11443 */ 11444 SQLITE_API sqlite3_int64 sqlite3session_memory_used(sqlite3_session *pSession); 11445 11446 /* 11447 ** CAPI3REF: Create An Iterator To Traverse A Changeset 11448 ** CONSTRUCTOR: sqlite3_changeset_iter 11449 ** 11450 ** Create an iterator used to iterate through the contents of a changeset. 11451 ** If successful, *pp is set to point to the iterator handle and SQLITE_OK 11452 ** is returned. Otherwise, if an error occurs, *pp is set to zero and an 11453 ** SQLite error code is returned. 11454 ** 11455 ** The following functions can be used to advance and query a changeset 11456 ** iterator created by this function: 11457 ** 11458 ** <ul> 11459 ** <li> [sqlite3changeset_next()] 11460 ** <li> [sqlite3changeset_op()] 11461 ** <li> [sqlite3changeset_new()] 11462 ** <li> [sqlite3changeset_old()] 11463 ** </ul> 11464 ** 11465 ** It is the responsibility of the caller to eventually destroy the iterator 11466 ** by passing it to [sqlite3changeset_finalize()]. The buffer containing the 11467 ** changeset (pChangeset) must remain valid until after the iterator is 11468 ** destroyed. 11469 ** 11470 ** Assuming the changeset blob was created by one of the 11471 ** [sqlite3session_changeset()], [sqlite3changeset_concat()] or 11472 ** [sqlite3changeset_invert()] functions, all changes within the changeset 11473 ** that apply to a single table are grouped together. This means that when 11474 ** an application iterates through a changeset using an iterator created by 11475 ** this function, all changes that relate to a single table are visited 11476 ** consecutively. There is no chance that the iterator will visit a change 11477 ** the applies to table X, then one for table Y, and then later on visit 11478 ** another change for table X. 11479 ** 11480 ** The behavior of sqlite3changeset_start_v2() and its streaming equivalent 11481 ** may be modified by passing a combination of 11482 ** [SQLITE_CHANGESETSTART_INVERT | supported flags] as the 4th parameter. 11483 ** 11484 ** Note that the sqlite3changeset_start_v2() API is still <b>experimental</b> 11485 ** and therefore subject to change. 11486 */ 11487 SQLITE_API int sqlite3changeset_start( 11488 sqlite3_changeset_iter **pp, /* OUT: New changeset iterator handle */ 11489 int nChangeset, /* Size of changeset blob in bytes */ 11490 void *pChangeset /* Pointer to blob containing changeset */ 11491 ); 11492 SQLITE_API int sqlite3changeset_start_v2( 11493 sqlite3_changeset_iter **pp, /* OUT: New changeset iterator handle */ 11494 int nChangeset, /* Size of changeset blob in bytes */ 11495 void *pChangeset, /* Pointer to blob containing changeset */ 11496 int flags /* SESSION_CHANGESETSTART_* flags */ 11497 ); 11498 11499 /* 11500 ** CAPI3REF: Flags for sqlite3changeset_start_v2 11501 ** 11502 ** The following flags may passed via the 4th parameter to 11503 ** [sqlite3changeset_start_v2] and [sqlite3changeset_start_v2_strm]: 11504 ** 11505 ** <dt>SQLITE_CHANGESETAPPLY_INVERT <dd> 11506 ** Invert the changeset while iterating through it. This is equivalent to 11507 ** inverting a changeset using sqlite3changeset_invert() before applying it. 11508 ** It is an error to specify this flag with a patchset. 11509 */ 11510 #define SQLITE_CHANGESETSTART_INVERT 0x0002 11511 11512 11513 /* 11514 ** CAPI3REF: Advance A Changeset Iterator 11515 ** METHOD: sqlite3_changeset_iter 11516 ** 11517 ** This function may only be used with iterators created by the function 11518 ** [sqlite3changeset_start()]. If it is called on an iterator passed to 11519 ** a conflict-handler callback by [sqlite3changeset_apply()], SQLITE_MISUSE 11520 ** is returned and the call has no effect. 11521 ** 11522 ** Immediately after an iterator is created by sqlite3changeset_start(), it 11523 ** does not point to any change in the changeset. Assuming the changeset 11524 ** is not empty, the first call to this function advances the iterator to 11525 ** point to the first change in the changeset. Each subsequent call advances 11526 ** the iterator to point to the next change in the changeset (if any). If 11527 ** no error occurs and the iterator points to a valid change after a call 11528 ** to sqlite3changeset_next() has advanced it, SQLITE_ROW is returned. 11529 ** Otherwise, if all changes in the changeset have already been visited, 11530 ** SQLITE_DONE is returned. 11531 ** 11532 ** If an error occurs, an SQLite error code is returned. Possible error 11533 ** codes include SQLITE_CORRUPT (if the changeset buffer is corrupt) or 11534 ** SQLITE_NOMEM. 11535 */ 11536 SQLITE_API int sqlite3changeset_next(sqlite3_changeset_iter *pIter); 11537 11538 /* 11539 ** CAPI3REF: Obtain The Current Operation From A Changeset Iterator 11540 ** METHOD: sqlite3_changeset_iter 11541 ** 11542 ** The pIter argument passed to this function may either be an iterator 11543 ** passed to a conflict-handler by [sqlite3changeset_apply()], or an iterator 11544 ** created by [sqlite3changeset_start()]. In the latter case, the most recent 11545 ** call to [sqlite3changeset_next()] must have returned [SQLITE_ROW]. If this 11546 ** is not the case, this function returns [SQLITE_MISUSE]. 11547 ** 11548 ** Arguments pOp, pnCol and pzTab may not be NULL. Upon return, three 11549 ** outputs are set through these pointers: 11550 ** 11551 ** *pOp is set to one of [SQLITE_INSERT], [SQLITE_DELETE] or [SQLITE_UPDATE], 11552 ** depending on the type of change that the iterator currently points to; 11553 ** 11554 ** *pnCol is set to the number of columns in the table affected by the change; and 11555 ** 11556 ** *pzTab is set to point to a nul-terminated utf-8 encoded string containing 11557 ** the name of the table affected by the current change. The buffer remains 11558 ** valid until either sqlite3changeset_next() is called on the iterator 11559 ** or until the conflict-handler function returns. 11560 ** 11561 ** If pbIndirect is not NULL, then *pbIndirect is set to true (1) if the change 11562 ** is an indirect change, or false (0) otherwise. See the documentation for 11563 ** [sqlite3session_indirect()] for a description of direct and indirect 11564 ** changes. 11565 ** 11566 ** If no error occurs, SQLITE_OK is returned. If an error does occur, an 11567 ** SQLite error code is returned. The values of the output variables may not 11568 ** be trusted in this case. 11569 */ 11570 SQLITE_API int sqlite3changeset_op( 11571 sqlite3_changeset_iter *pIter, /* Iterator object */ 11572 const char **pzTab, /* OUT: Pointer to table name */ 11573 int *pnCol, /* OUT: Number of columns in table */ 11574 int *pOp, /* OUT: SQLITE_INSERT, DELETE or UPDATE */ 11575 int *pbIndirect /* OUT: True for an 'indirect' change */ 11576 ); 11577 11578 /* 11579 ** CAPI3REF: Obtain The Primary Key Definition Of A Table 11580 ** METHOD: sqlite3_changeset_iter 11581 ** 11582 ** For each modified table, a changeset includes the following: 11583 ** 11584 ** <ul> 11585 ** <li> The number of columns in the table, and 11586 ** <li> Which of those columns make up the tables PRIMARY KEY. 11587 ** </ul> 11588 ** 11589 ** This function is used to find which columns comprise the PRIMARY KEY of 11590 ** the table modified by the change that iterator pIter currently points to. 11591 ** If successful, *pabPK is set to point to an array of nCol entries, where 11592 ** nCol is the number of columns in the table. Elements of *pabPK are set to 11593 ** 0x01 if the corresponding column is part of the tables primary key, or 11594 ** 0x00 if it is not. 11595 ** 11596 ** If argument pnCol is not NULL, then *pnCol is set to the number of columns 11597 ** in the table. 11598 ** 11599 ** If this function is called when the iterator does not point to a valid 11600 ** entry, SQLITE_MISUSE is returned and the output variables zeroed. Otherwise, 11601 ** SQLITE_OK is returned and the output variables populated as described 11602 ** above. 11603 */ 11604 SQLITE_API int sqlite3changeset_pk( 11605 sqlite3_changeset_iter *pIter, /* Iterator object */ 11606 unsigned char **pabPK, /* OUT: Array of boolean - true for PK cols */ 11607 int *pnCol /* OUT: Number of entries in output array */ 11608 ); 11609 11610 /* 11611 ** CAPI3REF: Obtain old.* Values From A Changeset Iterator 11612 ** METHOD: sqlite3_changeset_iter 11613 ** 11614 ** The pIter argument passed to this function may either be an iterator 11615 ** passed to a conflict-handler by [sqlite3changeset_apply()], or an iterator 11616 ** created by [sqlite3changeset_start()]. In the latter case, the most recent 11617 ** call to [sqlite3changeset_next()] must have returned SQLITE_ROW. 11618 ** Furthermore, it may only be called if the type of change that the iterator 11619 ** currently points to is either [SQLITE_DELETE] or [SQLITE_UPDATE]. Otherwise, 11620 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL. 11621 ** 11622 ** Argument iVal must be greater than or equal to 0, and less than the number 11623 ** of columns in the table affected by the current change. Otherwise, 11624 ** [SQLITE_RANGE] is returned and *ppValue is set to NULL. 11625 ** 11626 ** If successful, this function sets *ppValue to point to a protected 11627 ** sqlite3_value object containing the iVal'th value from the vector of 11628 ** original row values stored as part of the UPDATE or DELETE change and 11629 ** returns SQLITE_OK. The name of the function comes from the fact that this 11630 ** is similar to the "old.*" columns available to update or delete triggers. 11631 ** 11632 ** If some other error occurs (e.g. an OOM condition), an SQLite error code 11633 ** is returned and *ppValue is set to NULL. 11634 */ 11635 SQLITE_API int sqlite3changeset_old( 11636 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 11637 int iVal, /* Column number */ 11638 sqlite3_value **ppValue /* OUT: Old value (or NULL pointer) */ 11639 ); 11640 11641 /* 11642 ** CAPI3REF: Obtain new.* Values From A Changeset Iterator 11643 ** METHOD: sqlite3_changeset_iter 11644 ** 11645 ** The pIter argument passed to this function may either be an iterator 11646 ** passed to a conflict-handler by [sqlite3changeset_apply()], or an iterator 11647 ** created by [sqlite3changeset_start()]. In the latter case, the most recent 11648 ** call to [sqlite3changeset_next()] must have returned SQLITE_ROW. 11649 ** Furthermore, it may only be called if the type of change that the iterator 11650 ** currently points to is either [SQLITE_UPDATE] or [SQLITE_INSERT]. Otherwise, 11651 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL. 11652 ** 11653 ** Argument iVal must be greater than or equal to 0, and less than the number 11654 ** of columns in the table affected by the current change. Otherwise, 11655 ** [SQLITE_RANGE] is returned and *ppValue is set to NULL. 11656 ** 11657 ** If successful, this function sets *ppValue to point to a protected 11658 ** sqlite3_value object containing the iVal'th value from the vector of 11659 ** new row values stored as part of the UPDATE or INSERT change and 11660 ** returns SQLITE_OK. If the change is an UPDATE and does not include 11661 ** a new value for the requested column, *ppValue is set to NULL and 11662 ** SQLITE_OK returned. The name of the function comes from the fact that 11663 ** this is similar to the "new.*" columns available to update or delete 11664 ** triggers. 11665 ** 11666 ** If some other error occurs (e.g. an OOM condition), an SQLite error code 11667 ** is returned and *ppValue is set to NULL. 11668 */ 11669 SQLITE_API int sqlite3changeset_new( 11670 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 11671 int iVal, /* Column number */ 11672 sqlite3_value **ppValue /* OUT: New value (or NULL pointer) */ 11673 ); 11674 11675 /* 11676 ** CAPI3REF: Obtain Conflicting Row Values From A Changeset Iterator 11677 ** METHOD: sqlite3_changeset_iter 11678 ** 11679 ** This function should only be used with iterator objects passed to a 11680 ** conflict-handler callback by [sqlite3changeset_apply()] with either 11681 ** [SQLITE_CHANGESET_DATA] or [SQLITE_CHANGESET_CONFLICT]. If this function 11682 ** is called on any other iterator, [SQLITE_MISUSE] is returned and *ppValue 11683 ** is set to NULL. 11684 ** 11685 ** Argument iVal must be greater than or equal to 0, and less than the number 11686 ** of columns in the table affected by the current change. Otherwise, 11687 ** [SQLITE_RANGE] is returned and *ppValue is set to NULL. 11688 ** 11689 ** If successful, this function sets *ppValue to point to a protected 11690 ** sqlite3_value object containing the iVal'th value from the 11691 ** "conflicting row" associated with the current conflict-handler callback 11692 ** and returns SQLITE_OK. 11693 ** 11694 ** If some other error occurs (e.g. an OOM condition), an SQLite error code 11695 ** is returned and *ppValue is set to NULL. 11696 */ 11697 SQLITE_API int sqlite3changeset_conflict( 11698 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 11699 int iVal, /* Column number */ 11700 sqlite3_value **ppValue /* OUT: Value from conflicting row */ 11701 ); 11702 11703 /* 11704 ** CAPI3REF: Determine The Number Of Foreign Key Constraint Violations 11705 ** METHOD: sqlite3_changeset_iter 11706 ** 11707 ** This function may only be called with an iterator passed to an 11708 ** SQLITE_CHANGESET_FOREIGN_KEY conflict handler callback. In this case 11709 ** it sets the output variable to the total number of known foreign key 11710 ** violations in the destination database and returns SQLITE_OK. 11711 ** 11712 ** In all other cases this function returns SQLITE_MISUSE. 11713 */ 11714 SQLITE_API int sqlite3changeset_fk_conflicts( 11715 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 11716 int *pnOut /* OUT: Number of FK violations */ 11717 ); 11718 11719 11720 /* 11721 ** CAPI3REF: Finalize A Changeset Iterator 11722 ** METHOD: sqlite3_changeset_iter 11723 ** 11724 ** This function is used to finalize an iterator allocated with 11725 ** [sqlite3changeset_start()]. 11726 ** 11727 ** This function should only be called on iterators created using the 11728 ** [sqlite3changeset_start()] function. If an application calls this 11729 ** function with an iterator passed to a conflict-handler by 11730 ** [sqlite3changeset_apply()], [SQLITE_MISUSE] is immediately returned and the 11731 ** call has no effect. 11732 ** 11733 ** If an error was encountered within a call to an sqlite3changeset_xxx() 11734 ** function (for example an [SQLITE_CORRUPT] in [sqlite3changeset_next()] or an 11735 ** [SQLITE_NOMEM] in [sqlite3changeset_new()]) then an error code corresponding 11736 ** to that error is returned by this function. Otherwise, SQLITE_OK is 11737 ** returned. This is to allow the following pattern (pseudo-code): 11738 ** 11739 ** <pre> 11740 ** sqlite3changeset_start(); 11741 ** while( SQLITE_ROW==sqlite3changeset_next() ){ 11742 ** // Do something with change. 11743 ** } 11744 ** rc = sqlite3changeset_finalize(); 11745 ** if( rc!=SQLITE_OK ){ 11746 ** // An error has occurred 11747 ** } 11748 ** </pre> 11749 */ 11750 SQLITE_API int sqlite3changeset_finalize(sqlite3_changeset_iter *pIter); 11751 11752 /* 11753 ** CAPI3REF: Invert A Changeset 11754 ** 11755 ** This function is used to "invert" a changeset object. Applying an inverted 11756 ** changeset to a database reverses the effects of applying the uninverted 11757 ** changeset. Specifically: 11758 ** 11759 ** <ul> 11760 ** <li> Each DELETE change is changed to an INSERT, and 11761 ** <li> Each INSERT change is changed to a DELETE, and 11762 ** <li> For each UPDATE change, the old.* and new.* values are exchanged. 11763 ** </ul> 11764 ** 11765 ** This function does not change the order in which changes appear within 11766 ** the changeset. It merely reverses the sense of each individual change. 11767 ** 11768 ** If successful, a pointer to a buffer containing the inverted changeset 11769 ** is stored in *ppOut, the size of the same buffer is stored in *pnOut, and 11770 ** SQLITE_OK is returned. If an error occurs, both *pnOut and *ppOut are 11771 ** zeroed and an SQLite error code returned. 11772 ** 11773 ** It is the responsibility of the caller to eventually call sqlite3_free() 11774 ** on the *ppOut pointer to free the buffer allocation following a successful 11775 ** call to this function. 11776 ** 11777 ** WARNING/TODO: This function currently assumes that the input is a valid 11778 ** changeset. If it is not, the results are undefined. 11779 */ 11780 SQLITE_API int sqlite3changeset_invert( 11781 int nIn, const void *pIn, /* Input changeset */ 11782 int *pnOut, void **ppOut /* OUT: Inverse of input */ 11783 ); 11784 11785 /* 11786 ** CAPI3REF: Concatenate Two Changeset Objects 11787 ** 11788 ** This function is used to concatenate two changesets, A and B, into a 11789 ** single changeset. The result is a changeset equivalent to applying 11790 ** changeset A followed by changeset B. 11791 ** 11792 ** This function combines the two input changesets using an 11793 ** sqlite3_changegroup object. Calling it produces similar results as the 11794 ** following code fragment: 11795 ** 11796 ** <pre> 11797 ** sqlite3_changegroup *pGrp; 11798 ** rc = sqlite3_changegroup_new(&pGrp); 11799 ** if( rc==SQLITE_OK ) rc = sqlite3changegroup_add(pGrp, nA, pA); 11800 ** if( rc==SQLITE_OK ) rc = sqlite3changegroup_add(pGrp, nB, pB); 11801 ** if( rc==SQLITE_OK ){ 11802 ** rc = sqlite3changegroup_output(pGrp, pnOut, ppOut); 11803 ** }else{ 11804 ** *ppOut = 0; 11805 ** *pnOut = 0; 11806 ** } 11807 ** </pre> 11808 ** 11809 ** Refer to the sqlite3_changegroup documentation below for details. 11810 */ 11811 SQLITE_API int sqlite3changeset_concat( 11812 int nA, /* Number of bytes in buffer pA */ 11813 void *pA, /* Pointer to buffer containing changeset A */ 11814 int nB, /* Number of bytes in buffer pB */ 11815 void *pB, /* Pointer to buffer containing changeset B */ 11816 int *pnOut, /* OUT: Number of bytes in output changeset */ 11817 void **ppOut /* OUT: Buffer containing output changeset */ 11818 ); 11819 11820 11821 /* 11822 ** CAPI3REF: Upgrade the Schema of a Changeset/Patchset 11823 */ 11824 SQLITE_API int sqlite3changeset_upgrade( 11825 sqlite3 *db, 11826 const char *zDb, 11827 int nIn, const void *pIn, /* Input changeset */ 11828 int *pnOut, void **ppOut /* OUT: Inverse of input */ 11829 ); 11830 11831 11832 11833 /* 11834 ** CAPI3REF: Changegroup Handle 11835 ** 11836 ** A changegroup is an object used to combine two or more 11837 ** [changesets] or [patchsets] 11838 */ 11839 typedef struct sqlite3_changegroup sqlite3_changegroup; 11840 11841 /* 11842 ** CAPI3REF: Create A New Changegroup Object 11843 ** CONSTRUCTOR: sqlite3_changegroup 11844 ** 11845 ** An sqlite3_changegroup object is used to combine two or more changesets 11846 ** (or patchsets) into a single changeset (or patchset). A single changegroup 11847 ** object may combine changesets or patchsets, but not both. The output is 11848 ** always in the same format as the input. 11849 ** 11850 ** If successful, this function returns SQLITE_OK and populates (*pp) with 11851 ** a pointer to a new sqlite3_changegroup object before returning. The caller 11852 ** should eventually free the returned object using a call to 11853 ** sqlite3changegroup_delete(). If an error occurs, an SQLite error code 11854 ** (i.e. SQLITE_NOMEM) is returned and *pp is set to NULL. 11855 ** 11856 ** The usual usage pattern for an sqlite3_changegroup object is as follows: 11857 ** 11858 ** <ul> 11859 ** <li> It is created using a call to sqlite3changegroup_new(). 11860 ** 11861 ** <li> Zero or more changesets (or patchsets) are added to the object 11862 ** by calling sqlite3changegroup_add(). 11863 ** 11864 ** <li> The result of combining all input changesets together is obtained 11865 ** by the application via a call to sqlite3changegroup_output(). 11866 ** 11867 ** <li> The object is deleted using a call to sqlite3changegroup_delete(). 11868 ** </ul> 11869 ** 11870 ** Any number of calls to add() and output() may be made between the calls to 11871 ** new() and delete(), and in any order. 11872 ** 11873 ** As well as the regular sqlite3changegroup_add() and 11874 ** sqlite3changegroup_output() functions, also available are the streaming 11875 ** versions sqlite3changegroup_add_strm() and sqlite3changegroup_output_strm(). 11876 */ 11877 SQLITE_API int sqlite3changegroup_new(sqlite3_changegroup **pp); 11878 11879 /* 11880 ** CAPI3REF: Add a Schema to a Changegroup 11881 ** METHOD: sqlite3_changegroup_schema 11882 ** 11883 ** This method may be used to optionally enforce the rule that the changesets 11884 ** added to the changegroup handle must match the schema of database zDb 11885 ** ("main", "temp", or the name of an attached database). If 11886 ** sqlite3changegroup_add() is called to add a changeset that is not compatible 11887 ** with the configured schema, SQLITE_SCHEMA is returned and the changegroup 11888 ** object is left in an undefined state. 11889 ** 11890 ** A changeset schema is considered compatible with the database schema in 11891 ** the same way as for sqlite3changeset_apply(). Specifically, for each 11892 ** table in the changeset, there exists a database table with: 11893 ** 11894 ** <ul> 11895 ** <li> The name identified by the changeset, and 11896 ** <li> at least as many columns as recorded in the changeset, and 11897 ** <li> the primary key columns in the same position as recorded in 11898 ** the changeset. 11899 ** </ul> 11900 ** 11901 ** The output of the changegroup object always has the same schema as the 11902 ** database nominated using this function. In cases where changesets passed 11903 ** to sqlite3changegroup_add() have fewer columns than the corresponding table 11904 ** in the database schema, these are filled in using the default column 11905 ** values from the database schema. This makes it possible to combined 11906 ** changesets that have different numbers of columns for a single table 11907 ** within a changegroup, provided that they are otherwise compatible. 11908 */ 11909 SQLITE_API int sqlite3changegroup_schema(sqlite3_changegroup*, sqlite3*, const char *zDb); 11910 11911 /* 11912 ** CAPI3REF: Add A Changeset To A Changegroup 11913 ** METHOD: sqlite3_changegroup 11914 ** 11915 ** Add all changes within the changeset (or patchset) in buffer pData (size 11916 ** nData bytes) to the changegroup. 11917 ** 11918 ** If the buffer contains a patchset, then all prior calls to this function 11919 ** on the same changegroup object must also have specified patchsets. Or, if 11920 ** the buffer contains a changeset, so must have the earlier calls to this 11921 ** function. Otherwise, SQLITE_ERROR is returned and no changes are added 11922 ** to the changegroup. 11923 ** 11924 ** Rows within the changeset and changegroup are identified by the values in 11925 ** their PRIMARY KEY columns. A change in the changeset is considered to 11926 ** apply to the same row as a change already present in the changegroup if 11927 ** the two rows have the same primary key. 11928 ** 11929 ** Changes to rows that do not already appear in the changegroup are 11930 ** simply copied into it. Or, if both the new changeset and the changegroup 11931 ** contain changes that apply to a single row, the final contents of the 11932 ** changegroup depends on the type of each change, as follows: 11933 ** 11934 ** <table border=1 style="margin-left:8ex;margin-right:8ex"> 11935 ** <tr><th style="white-space:pre">Existing Change </th> 11936 ** <th style="white-space:pre">New Change </th> 11937 ** <th>Output Change 11938 ** <tr><td>INSERT <td>INSERT <td> 11939 ** The new change is ignored. This case does not occur if the new 11940 ** changeset was recorded immediately after the changesets already 11941 ** added to the changegroup. 11942 ** <tr><td>INSERT <td>UPDATE <td> 11943 ** The INSERT change remains in the changegroup. The values in the 11944 ** INSERT change are modified as if the row was inserted by the 11945 ** existing change and then updated according to the new change. 11946 ** <tr><td>INSERT <td>DELETE <td> 11947 ** The existing INSERT is removed from the changegroup. The DELETE is 11948 ** not added. 11949 ** <tr><td>UPDATE <td>INSERT <td> 11950 ** The new change is ignored. This case does not occur if the new 11951 ** changeset was recorded immediately after the changesets already 11952 ** added to the changegroup. 11953 ** <tr><td>UPDATE <td>UPDATE <td> 11954 ** The existing UPDATE remains within the changegroup. It is amended 11955 ** so that the accompanying values are as if the row was updated once 11956 ** by the existing change and then again by the new change. 11957 ** <tr><td>UPDATE <td>DELETE <td> 11958 ** The existing UPDATE is replaced by the new DELETE within the 11959 ** changegroup. 11960 ** <tr><td>DELETE <td>INSERT <td> 11961 ** If one or more of the column values in the row inserted by the 11962 ** new change differ from those in the row deleted by the existing 11963 ** change, the existing DELETE is replaced by an UPDATE within the 11964 ** changegroup. Otherwise, if the inserted row is exactly the same 11965 ** as the deleted row, the existing DELETE is simply discarded. 11966 ** <tr><td>DELETE <td>UPDATE <td> 11967 ** The new change is ignored. This case does not occur if the new 11968 ** changeset was recorded immediately after the changesets already 11969 ** added to the changegroup. 11970 ** <tr><td>DELETE <td>DELETE <td> 11971 ** The new change is ignored. This case does not occur if the new 11972 ** changeset was recorded immediately after the changesets already 11973 ** added to the changegroup. 11974 ** </table> 11975 ** 11976 ** If the new changeset contains changes to a table that is already present 11977 ** in the changegroup, then the number of columns and the position of the 11978 ** primary key columns for the table must be consistent. If this is not the 11979 ** case, this function fails with SQLITE_SCHEMA. Except, if the changegroup 11980 ** object has been configured with a database schema using the 11981 ** sqlite3changegroup_schema() API, then it is possible to combine changesets 11982 ** with different numbers of columns for a single table, provided that 11983 ** they are otherwise compatible. 11984 ** 11985 ** If the input changeset appears to be corrupt and the corruption is 11986 ** detected, SQLITE_CORRUPT is returned. Or, if an out-of-memory condition 11987 ** occurs during processing, this function returns SQLITE_NOMEM. 11988 ** 11989 ** In all cases, if an error occurs the state of the final contents of the 11990 ** changegroup is undefined. If no error occurs, SQLITE_OK is returned. 11991 */ 11992 SQLITE_API int sqlite3changegroup_add(sqlite3_changegroup*, int nData, void *pData); 11993 11994 /* 11995 ** CAPI3REF: Obtain A Composite Changeset From A Changegroup 11996 ** METHOD: sqlite3_changegroup 11997 ** 11998 ** Obtain a buffer containing a changeset (or patchset) representing the 11999 ** current contents of the changegroup. If the inputs to the changegroup 12000 ** were themselves changesets, the output is a changeset. Or, if the 12001 ** inputs were patchsets, the output is also a patchset. 12002 ** 12003 ** As with the output of the sqlite3session_changeset() and 12004 ** sqlite3session_patchset() functions, all changes related to a single 12005 ** table are grouped together in the output of this function. Tables appear 12006 ** in the same order as for the very first changeset added to the changegroup. 12007 ** If the second or subsequent changesets added to the changegroup contain 12008 ** changes for tables that do not appear in the first changeset, they are 12009 ** appended onto the end of the output changeset, again in the order in 12010 ** which they are first encountered. 12011 ** 12012 ** If an error occurs, an SQLite error code is returned and the output 12013 ** variables (*pnData) and (*ppData) are set to 0. Otherwise, SQLITE_OK 12014 ** is returned and the output variables are set to the size of and a 12015 ** pointer to the output buffer, respectively. In this case it is the 12016 ** responsibility of the caller to eventually free the buffer using a 12017 ** call to sqlite3_free(). 12018 */ 12019 SQLITE_API int sqlite3changegroup_output( 12020 sqlite3_changegroup*, 12021 int *pnData, /* OUT: Size of output buffer in bytes */ 12022 void **ppData /* OUT: Pointer to output buffer */ 12023 ); 12024 12025 /* 12026 ** CAPI3REF: Delete A Changegroup Object 12027 ** DESTRUCTOR: sqlite3_changegroup 12028 */ 12029 SQLITE_API void sqlite3changegroup_delete(sqlite3_changegroup*); 12030 12031 /* 12032 ** CAPI3REF: Apply A Changeset To A Database 12033 ** 12034 ** Apply a changeset or patchset to a database. These functions attempt to 12035 ** update the "main" database attached to handle db with the changes found in 12036 ** the changeset passed via the second and third arguments. 12037 ** 12038 ** The fourth argument (xFilter) passed to these functions is the "filter 12039 ** callback". If it is not NULL, then for each table affected by at least one 12040 ** change in the changeset, the filter callback is invoked with 12041 ** the table name as the second argument, and a copy of the context pointer 12042 ** passed as the sixth argument as the first. If the "filter callback" 12043 ** returns zero, then no attempt is made to apply any changes to the table. 12044 ** Otherwise, if the return value is non-zero or the xFilter argument to 12045 ** is NULL, all changes related to the table are attempted. 12046 ** 12047 ** For each table that is not excluded by the filter callback, this function 12048 ** tests that the target database contains a compatible table. A table is 12049 ** considered compatible if all of the following are true: 12050 ** 12051 ** <ul> 12052 ** <li> The table has the same name as the name recorded in the 12053 ** changeset, and 12054 ** <li> The table has at least as many columns as recorded in the 12055 ** changeset, and 12056 ** <li> The table has primary key columns in the same position as 12057 ** recorded in the changeset. 12058 ** </ul> 12059 ** 12060 ** If there is no compatible table, it is not an error, but none of the 12061 ** changes associated with the table are applied. A warning message is issued 12062 ** via the sqlite3_log() mechanism with the error code SQLITE_SCHEMA. At most 12063 ** one such warning is issued for each table in the changeset. 12064 ** 12065 ** For each change for which there is a compatible table, an attempt is made 12066 ** to modify the table contents according to the UPDATE, INSERT or DELETE 12067 ** change. If a change cannot be applied cleanly, the conflict handler 12068 ** function passed as the fifth argument to sqlite3changeset_apply() may be 12069 ** invoked. A description of exactly when the conflict handler is invoked for 12070 ** each type of change is below. 12071 ** 12072 ** Unlike the xFilter argument, xConflict may not be passed NULL. The results 12073 ** of passing anything other than a valid function pointer as the xConflict 12074 ** argument are undefined. 12075 ** 12076 ** Each time the conflict handler function is invoked, it must return one 12077 ** of [SQLITE_CHANGESET_OMIT], [SQLITE_CHANGESET_ABORT] or 12078 ** [SQLITE_CHANGESET_REPLACE]. SQLITE_CHANGESET_REPLACE may only be returned 12079 ** if the second argument passed to the conflict handler is either 12080 ** SQLITE_CHANGESET_DATA or SQLITE_CHANGESET_CONFLICT. If the conflict-handler 12081 ** returns an illegal value, any changes already made are rolled back and 12082 ** the call to sqlite3changeset_apply() returns SQLITE_MISUSE. Different 12083 ** actions are taken by sqlite3changeset_apply() depending on the value 12084 ** returned by each invocation of the conflict-handler function. Refer to 12085 ** the documentation for the three 12086 ** [SQLITE_CHANGESET_OMIT|available return values] for details. 12087 ** 12088 ** <dl> 12089 ** <dt>DELETE Changes<dd> 12090 ** For each DELETE change, the function checks if the target database 12091 ** contains a row with the same primary key value (or values) as the 12092 ** original row values stored in the changeset. If it does, and the values 12093 ** stored in all non-primary key columns also match the values stored in 12094 ** the changeset the row is deleted from the target database. 12095 ** 12096 ** If a row with matching primary key values is found, but one or more of 12097 ** the non-primary key fields contains a value different from the original 12098 ** row value stored in the changeset, the conflict-handler function is 12099 ** invoked with [SQLITE_CHANGESET_DATA] as the second argument. If the 12100 ** database table has more columns than are recorded in the changeset, 12101 ** only the values of those non-primary key fields are compared against 12102 ** the current database contents - any trailing database table columns 12103 ** are ignored. 12104 ** 12105 ** If no row with matching primary key values is found in the database, 12106 ** the conflict-handler function is invoked with [SQLITE_CHANGESET_NOTFOUND] 12107 ** passed as the second argument. 12108 ** 12109 ** If the DELETE operation is attempted, but SQLite returns SQLITE_CONSTRAINT 12110 ** (which can only happen if a foreign key constraint is violated), the 12111 ** conflict-handler function is invoked with [SQLITE_CHANGESET_CONSTRAINT] 12112 ** passed as the second argument. This includes the case where the DELETE 12113 ** operation is attempted because an earlier call to the conflict handler 12114 ** function returned [SQLITE_CHANGESET_REPLACE]. 12115 ** 12116 ** <dt>INSERT Changes<dd> 12117 ** For each INSERT change, an attempt is made to insert the new row into 12118 ** the database. If the changeset row contains fewer fields than the 12119 ** database table, the trailing fields are populated with their default 12120 ** values. 12121 ** 12122 ** If the attempt to insert the row fails because the database already 12123 ** contains a row with the same primary key values, the conflict handler 12124 ** function is invoked with the second argument set to 12125 ** [SQLITE_CHANGESET_CONFLICT]. 12126 ** 12127 ** If the attempt to insert the row fails because of some other constraint 12128 ** violation (e.g. NOT NULL or UNIQUE), the conflict handler function is 12129 ** invoked with the second argument set to [SQLITE_CHANGESET_CONSTRAINT]. 12130 ** This includes the case where the INSERT operation is re-attempted because 12131 ** an earlier call to the conflict handler function returned 12132 ** [SQLITE_CHANGESET_REPLACE]. 12133 ** 12134 ** <dt>UPDATE Changes<dd> 12135 ** For each UPDATE change, the function checks if the target database 12136 ** contains a row with the same primary key value (or values) as the 12137 ** original row values stored in the changeset. If it does, and the values 12138 ** stored in all modified non-primary key columns also match the values 12139 ** stored in the changeset the row is updated within the target database. 12140 ** 12141 ** If a row with matching primary key values is found, but one or more of 12142 ** the modified non-primary key fields contains a value different from an 12143 ** original row value stored in the changeset, the conflict-handler function 12144 ** is invoked with [SQLITE_CHANGESET_DATA] as the second argument. Since 12145 ** UPDATE changes only contain values for non-primary key fields that are 12146 ** to be modified, only those fields need to match the original values to 12147 ** avoid the SQLITE_CHANGESET_DATA conflict-handler callback. 12148 ** 12149 ** If no row with matching primary key values is found in the database, 12150 ** the conflict-handler function is invoked with [SQLITE_CHANGESET_NOTFOUND] 12151 ** passed as the second argument. 12152 ** 12153 ** If the UPDATE operation is attempted, but SQLite returns 12154 ** SQLITE_CONSTRAINT, the conflict-handler function is invoked with 12155 ** [SQLITE_CHANGESET_CONSTRAINT] passed as the second argument. 12156 ** This includes the case where the UPDATE operation is attempted after 12157 ** an earlier call to the conflict handler function returned 12158 ** [SQLITE_CHANGESET_REPLACE]. 12159 ** </dl> 12160 ** 12161 ** It is safe to execute SQL statements, including those that write to the 12162 ** table that the callback related to, from within the xConflict callback. 12163 ** This can be used to further customize the application's conflict 12164 ** resolution strategy. 12165 ** 12166 ** All changes made by these functions are enclosed in a savepoint transaction. 12167 ** If any other error (aside from a constraint failure when attempting to 12168 ** write to the target database) occurs, then the savepoint transaction is 12169 ** rolled back, restoring the target database to its original state, and an 12170 ** SQLite error code returned. 12171 ** 12172 ** If the output parameters (ppRebase) and (pnRebase) are non-NULL and 12173 ** the input is a changeset (not a patchset), then sqlite3changeset_apply_v2() 12174 ** may set (*ppRebase) to point to a "rebase" that may be used with the 12175 ** sqlite3_rebaser APIs buffer before returning. In this case (*pnRebase) 12176 ** is set to the size of the buffer in bytes. It is the responsibility of the 12177 ** caller to eventually free any such buffer using sqlite3_free(). The buffer 12178 ** is only allocated and populated if one or more conflicts were encountered 12179 ** while applying the patchset. See comments surrounding the sqlite3_rebaser 12180 ** APIs for further details. 12181 ** 12182 ** The behavior of sqlite3changeset_apply_v2() and its streaming equivalent 12183 ** may be modified by passing a combination of 12184 ** [SQLITE_CHANGESETAPPLY_NOSAVEPOINT | supported flags] as the 9th parameter. 12185 ** 12186 ** Note that the sqlite3changeset_apply_v2() API is still <b>experimental</b> 12187 ** and therefore subject to change. 12188 */ 12189 SQLITE_API int sqlite3changeset_apply( 12190 sqlite3 *db, /* Apply change to "main" db of this handle */ 12191 int nChangeset, /* Size of changeset in bytes */ 12192 void *pChangeset, /* Changeset blob */ 12193 int(*xFilter)( 12194 void *pCtx, /* Copy of sixth arg to _apply() */ 12195 const char *zTab /* Table name */ 12196 ), 12197 int(*xConflict)( 12198 void *pCtx, /* Copy of sixth arg to _apply() */ 12199 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 12200 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 12201 ), 12202 void *pCtx /* First argument passed to xConflict */ 12203 ); 12204 SQLITE_API int sqlite3changeset_apply_v2( 12205 sqlite3 *db, /* Apply change to "main" db of this handle */ 12206 int nChangeset, /* Size of changeset in bytes */ 12207 void *pChangeset, /* Changeset blob */ 12208 int(*xFilter)( 12209 void *pCtx, /* Copy of sixth arg to _apply() */ 12210 const char *zTab /* Table name */ 12211 ), 12212 int(*xConflict)( 12213 void *pCtx, /* Copy of sixth arg to _apply() */ 12214 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 12215 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 12216 ), 12217 void *pCtx, /* First argument passed to xConflict */ 12218 void **ppRebase, int *pnRebase, /* OUT: Rebase data */ 12219 int flags /* SESSION_CHANGESETAPPLY_* flags */ 12220 ); 12221 12222 /* 12223 ** CAPI3REF: Flags for sqlite3changeset_apply_v2 12224 ** 12225 ** The following flags may passed via the 9th parameter to 12226 ** [sqlite3changeset_apply_v2] and [sqlite3changeset_apply_v2_strm]: 12227 ** 12228 ** <dl> 12229 ** <dt>SQLITE_CHANGESETAPPLY_NOSAVEPOINT <dd> 12230 ** Usually, the sessions module encloses all operations performed by 12231 ** a single call to apply_v2() or apply_v2_strm() in a [SAVEPOINT]. The 12232 ** SAVEPOINT is committed if the changeset or patchset is successfully 12233 ** applied, or rolled back if an error occurs. Specifying this flag 12234 ** causes the sessions module to omit this savepoint. In this case, if the 12235 ** caller has an open transaction or savepoint when apply_v2() is called, 12236 ** it may revert the partially applied changeset by rolling it back. 12237 ** 12238 ** <dt>SQLITE_CHANGESETAPPLY_INVERT <dd> 12239 ** Invert the changeset before applying it. This is equivalent to inverting 12240 ** a changeset using sqlite3changeset_invert() before applying it. It is 12241 ** an error to specify this flag with a patchset. 12242 ** 12243 ** <dt>SQLITE_CHANGESETAPPLY_IGNORENOOP <dd> 12244 ** Do not invoke the conflict handler callback for any changes that 12245 ** would not actually modify the database even if they were applied. 12246 ** Specifically, this means that the conflict handler is not invoked 12247 ** for: 12248 ** <ul> 12249 ** <li>a delete change if the row being deleted cannot be found, 12250 ** <li>an update change if the modified fields are already set to 12251 ** their new values in the conflicting row, or 12252 ** <li>an insert change if all fields of the conflicting row match 12253 ** the row being inserted. 12254 ** </ul> 12255 ** 12256 ** <dt>SQLITE_CHANGESETAPPLY_FKNOACTION <dd> 12257 ** If this flag it set, then all foreign key constraints in the target 12258 ** database behave as if they were declared with "ON UPDATE NO ACTION ON 12259 ** DELETE NO ACTION", even if they are actually CASCADE, RESTRICT, SET NULL 12260 ** or SET DEFAULT. 12261 */ 12262 #define SQLITE_CHANGESETAPPLY_NOSAVEPOINT 0x0001 12263 #define SQLITE_CHANGESETAPPLY_INVERT 0x0002 12264 #define SQLITE_CHANGESETAPPLY_IGNORENOOP 0x0004 12265 #define SQLITE_CHANGESETAPPLY_FKNOACTION 0x0008 12266 12267 /* 12268 ** CAPI3REF: Constants Passed To The Conflict Handler 12269 ** 12270 ** Values that may be passed as the second argument to a conflict-handler. 12271 ** 12272 ** <dl> 12273 ** <dt>SQLITE_CHANGESET_DATA<dd> 12274 ** The conflict handler is invoked with CHANGESET_DATA as the second argument 12275 ** when processing a DELETE or UPDATE change if a row with the required 12276 ** PRIMARY KEY fields is present in the database, but one or more other 12277 ** (non primary-key) fields modified by the update do not contain the 12278 ** expected "before" values. 12279 ** 12280 ** The conflicting row, in this case, is the database row with the matching 12281 ** primary key. 12282 ** 12283 ** <dt>SQLITE_CHANGESET_NOTFOUND<dd> 12284 ** The conflict handler is invoked with CHANGESET_NOTFOUND as the second 12285 ** argument when processing a DELETE or UPDATE change if a row with the 12286 ** required PRIMARY KEY fields is not present in the database. 12287 ** 12288 ** There is no conflicting row in this case. The results of invoking the 12289 ** sqlite3changeset_conflict() API are undefined. 12290 ** 12291 ** <dt>SQLITE_CHANGESET_CONFLICT<dd> 12292 ** CHANGESET_CONFLICT is passed as the second argument to the conflict 12293 ** handler while processing an INSERT change if the operation would result 12294 ** in duplicate primary key values. 12295 ** 12296 ** The conflicting row in this case is the database row with the matching 12297 ** primary key. 12298 ** 12299 ** <dt>SQLITE_CHANGESET_FOREIGN_KEY<dd> 12300 ** If foreign key handling is enabled, and applying a changeset leaves the 12301 ** database in a state containing foreign key violations, the conflict 12302 ** handler is invoked with CHANGESET_FOREIGN_KEY as the second argument 12303 ** exactly once before the changeset is committed. If the conflict handler 12304 ** returns CHANGESET_OMIT, the changes, including those that caused the 12305 ** foreign key constraint violation, are committed. Or, if it returns 12306 ** CHANGESET_ABORT, the changeset is rolled back. 12307 ** 12308 ** No current or conflicting row information is provided. The only function 12309 ** it is possible to call on the supplied sqlite3_changeset_iter handle 12310 ** is sqlite3changeset_fk_conflicts(). 12311 ** 12312 ** <dt>SQLITE_CHANGESET_CONSTRAINT<dd> 12313 ** If any other constraint violation occurs while applying a change (i.e. 12314 ** a UNIQUE, CHECK or NOT NULL constraint), the conflict handler is 12315 ** invoked with CHANGESET_CONSTRAINT as the second argument. 12316 ** 12317 ** There is no conflicting row in this case. The results of invoking the 12318 ** sqlite3changeset_conflict() API are undefined. 12319 ** 12320 ** </dl> 12321 */ 12322 #define SQLITE_CHANGESET_DATA 1 12323 #define SQLITE_CHANGESET_NOTFOUND 2 12324 #define SQLITE_CHANGESET_CONFLICT 3 12325 #define SQLITE_CHANGESET_CONSTRAINT 4 12326 #define SQLITE_CHANGESET_FOREIGN_KEY 5 12327 12328 /* 12329 ** CAPI3REF: Constants Returned By The Conflict Handler 12330 ** 12331 ** A conflict handler callback must return one of the following three values. 12332 ** 12333 ** <dl> 12334 ** <dt>SQLITE_CHANGESET_OMIT<dd> 12335 ** If a conflict handler returns this value no special action is taken. The 12336 ** change that caused the conflict is not applied. The session module 12337 ** continues to the next change in the changeset. 12338 ** 12339 ** <dt>SQLITE_CHANGESET_REPLACE<dd> 12340 ** This value may only be returned if the second argument to the conflict 12341 ** handler was SQLITE_CHANGESET_DATA or SQLITE_CHANGESET_CONFLICT. If this 12342 ** is not the case, any changes applied so far are rolled back and the 12343 ** call to sqlite3changeset_apply() returns SQLITE_MISUSE. 12344 ** 12345 ** If CHANGESET_REPLACE is returned by an SQLITE_CHANGESET_DATA conflict 12346 ** handler, then the conflicting row is either updated or deleted, depending 12347 ** on the type of change. 12348 ** 12349 ** If CHANGESET_REPLACE is returned by an SQLITE_CHANGESET_CONFLICT conflict 12350 ** handler, then the conflicting row is removed from the database and a 12351 ** second attempt to apply the change is made. If this second attempt fails, 12352 ** the original row is restored to the database before continuing. 12353 ** 12354 ** <dt>SQLITE_CHANGESET_ABORT<dd> 12355 ** If this value is returned, any changes applied so far are rolled back 12356 ** and the call to sqlite3changeset_apply() returns SQLITE_ABORT. 12357 ** </dl> 12358 */ 12359 #define SQLITE_CHANGESET_OMIT 0 12360 #define SQLITE_CHANGESET_REPLACE 1 12361 #define SQLITE_CHANGESET_ABORT 2 12362 12363 /* 12364 ** CAPI3REF: Rebasing changesets 12365 ** EXPERIMENTAL 12366 ** 12367 ** Suppose there is a site hosting a database in state S0. And that 12368 ** modifications are made that move that database to state S1 and a 12369 ** changeset recorded (the "local" changeset). Then, a changeset based 12370 ** on S0 is received from another site (the "remote" changeset) and 12371 ** applied to the database. The database is then in state 12372 ** (S1+"remote"), where the exact state depends on any conflict 12373 ** resolution decisions (OMIT or REPLACE) made while applying "remote". 12374 ** Rebasing a changeset is to update it to take those conflict 12375 ** resolution decisions into account, so that the same conflicts 12376 ** do not have to be resolved elsewhere in the network. 12377 ** 12378 ** For example, if both the local and remote changesets contain an 12379 ** INSERT of the same key on "CREATE TABLE t1(a PRIMARY KEY, b)": 12380 ** 12381 ** local: INSERT INTO t1 VALUES(1, 'v1'); 12382 ** remote: INSERT INTO t1 VALUES(1, 'v2'); 12383 ** 12384 ** and the conflict resolution is REPLACE, then the INSERT change is 12385 ** removed from the local changeset (it was overridden). Or, if the 12386 ** conflict resolution was "OMIT", then the local changeset is modified 12387 ** to instead contain: 12388 ** 12389 ** UPDATE t1 SET b = 'v2' WHERE a=1; 12390 ** 12391 ** Changes within the local changeset are rebased as follows: 12392 ** 12393 ** <dl> 12394 ** <dt>Local INSERT<dd> 12395 ** This may only conflict with a remote INSERT. If the conflict 12396 ** resolution was OMIT, then add an UPDATE change to the rebased 12397 ** changeset. Or, if the conflict resolution was REPLACE, add 12398 ** nothing to the rebased changeset. 12399 ** 12400 ** <dt>Local DELETE<dd> 12401 ** This may conflict with a remote UPDATE or DELETE. In both cases the 12402 ** only possible resolution is OMIT. If the remote operation was a 12403 ** DELETE, then add no change to the rebased changeset. If the remote 12404 ** operation was an UPDATE, then the old.* fields of change are updated 12405 ** to reflect the new.* values in the UPDATE. 12406 ** 12407 ** <dt>Local UPDATE<dd> 12408 ** This may conflict with a remote UPDATE or DELETE. If it conflicts 12409 ** with a DELETE, and the conflict resolution was OMIT, then the update 12410 ** is changed into an INSERT. Any undefined values in the new.* record 12411 ** from the update change are filled in using the old.* values from 12412 ** the conflicting DELETE. Or, if the conflict resolution was REPLACE, 12413 ** the UPDATE change is simply omitted from the rebased changeset. 12414 ** 12415 ** If conflict is with a remote UPDATE and the resolution is OMIT, then 12416 ** the old.* values are rebased using the new.* values in the remote 12417 ** change. Or, if the resolution is REPLACE, then the change is copied 12418 ** into the rebased changeset with updates to columns also updated by 12419 ** the conflicting remote UPDATE removed. If this means no columns would 12420 ** be updated, the change is omitted. 12421 ** </dl> 12422 ** 12423 ** A local change may be rebased against multiple remote changes 12424 ** simultaneously. If a single key is modified by multiple remote 12425 ** changesets, they are combined as follows before the local changeset 12426 ** is rebased: 12427 ** 12428 ** <ul> 12429 ** <li> If there has been one or more REPLACE resolutions on a 12430 ** key, it is rebased according to a REPLACE. 12431 ** 12432 ** <li> If there have been no REPLACE resolutions on a key, then 12433 ** the local changeset is rebased according to the most recent 12434 ** of the OMIT resolutions. 12435 ** </ul> 12436 ** 12437 ** Note that conflict resolutions from multiple remote changesets are 12438 ** combined on a per-field basis, not per-row. This means that in the 12439 ** case of multiple remote UPDATE operations, some fields of a single 12440 ** local change may be rebased for REPLACE while others are rebased for 12441 ** OMIT. 12442 ** 12443 ** In order to rebase a local changeset, the remote changeset must first 12444 ** be applied to the local database using sqlite3changeset_apply_v2() and 12445 ** the buffer of rebase information captured. Then: 12446 ** 12447 ** <ol> 12448 ** <li> An sqlite3_rebaser object is created by calling 12449 ** sqlite3rebaser_create(). 12450 ** <li> The new object is configured with the rebase buffer obtained from 12451 ** sqlite3changeset_apply_v2() by calling sqlite3rebaser_configure(). 12452 ** If the local changeset is to be rebased against multiple remote 12453 ** changesets, then sqlite3rebaser_configure() should be called 12454 ** multiple times, in the same order that the multiple 12455 ** sqlite3changeset_apply_v2() calls were made. 12456 ** <li> Each local changeset is rebased by calling sqlite3rebaser_rebase(). 12457 ** <li> The sqlite3_rebaser object is deleted by calling 12458 ** sqlite3rebaser_delete(). 12459 ** </ol> 12460 */ 12461 typedef struct sqlite3_rebaser sqlite3_rebaser; 12462 12463 /* 12464 ** CAPI3REF: Create a changeset rebaser object. 12465 ** EXPERIMENTAL 12466 ** 12467 ** Allocate a new changeset rebaser object. If successful, set (*ppNew) to 12468 ** point to the new object and return SQLITE_OK. Otherwise, if an error 12469 ** occurs, return an SQLite error code (e.g. SQLITE_NOMEM) and set (*ppNew) 12470 ** to NULL. 12471 */ 12472 SQLITE_API int sqlite3rebaser_create(sqlite3_rebaser **ppNew); 12473 12474 /* 12475 ** CAPI3REF: Configure a changeset rebaser object. 12476 ** EXPERIMENTAL 12477 ** 12478 ** Configure the changeset rebaser object to rebase changesets according 12479 ** to the conflict resolutions described by buffer pRebase (size nRebase 12480 ** bytes), which must have been obtained from a previous call to 12481 ** sqlite3changeset_apply_v2(). 12482 */ 12483 SQLITE_API int sqlite3rebaser_configure( 12484 sqlite3_rebaser*, 12485 int nRebase, const void *pRebase 12486 ); 12487 12488 /* 12489 ** CAPI3REF: Rebase a changeset 12490 ** EXPERIMENTAL 12491 ** 12492 ** Argument pIn must point to a buffer containing a changeset nIn bytes 12493 ** in size. This function allocates and populates a buffer with a copy 12494 ** of the changeset rebased according to the configuration of the 12495 ** rebaser object passed as the first argument. If successful, (*ppOut) 12496 ** is set to point to the new buffer containing the rebased changeset and 12497 ** (*pnOut) to its size in bytes and SQLITE_OK returned. It is the 12498 ** responsibility of the caller to eventually free the new buffer using 12499 ** sqlite3_free(). Otherwise, if an error occurs, (*ppOut) and (*pnOut) 12500 ** are set to zero and an SQLite error code returned. 12501 */ 12502 SQLITE_API int sqlite3rebaser_rebase( 12503 sqlite3_rebaser*, 12504 int nIn, const void *pIn, 12505 int *pnOut, void **ppOut 12506 ); 12507 12508 /* 12509 ** CAPI3REF: Delete a changeset rebaser object. 12510 ** EXPERIMENTAL 12511 ** 12512 ** Delete the changeset rebaser object and all associated resources. There 12513 ** should be one call to this function for each successful invocation 12514 ** of sqlite3rebaser_create(). 12515 */ 12516 SQLITE_API void sqlite3rebaser_delete(sqlite3_rebaser *p); 12517 12518 /* 12519 ** CAPI3REF: Streaming Versions of API functions. 12520 ** 12521 ** The six streaming API xxx_strm() functions serve similar purposes to the 12522 ** corresponding non-streaming API functions: 12523 ** 12524 ** <table border=1 style="margin-left:8ex;margin-right:8ex"> 12525 ** <tr><th>Streaming function<th>Non-streaming equivalent</th> 12526 ** <tr><td>sqlite3changeset_apply_strm<td>[sqlite3changeset_apply] 12527 ** <tr><td>sqlite3changeset_apply_strm_v2<td>[sqlite3changeset_apply_v2] 12528 ** <tr><td>sqlite3changeset_concat_strm<td>[sqlite3changeset_concat] 12529 ** <tr><td>sqlite3changeset_invert_strm<td>[sqlite3changeset_invert] 12530 ** <tr><td>sqlite3changeset_start_strm<td>[sqlite3changeset_start] 12531 ** <tr><td>sqlite3session_changeset_strm<td>[sqlite3session_changeset] 12532 ** <tr><td>sqlite3session_patchset_strm<td>[sqlite3session_patchset] 12533 ** </table> 12534 ** 12535 ** Non-streaming functions that accept changesets (or patchsets) as input 12536 ** require that the entire changeset be stored in a single buffer in memory. 12537 ** Similarly, those that return a changeset or patchset do so by returning 12538 ** a pointer to a single large buffer allocated using sqlite3_malloc(). 12539 ** Normally this is convenient. However, if an application running in a 12540 ** low-memory environment is required to handle very large changesets, the 12541 ** large contiguous memory allocations required can become onerous. 12542 ** 12543 ** In order to avoid this problem, instead of a single large buffer, input 12544 ** is passed to a streaming API functions by way of a callback function that 12545 ** the sessions module invokes to incrementally request input data as it is 12546 ** required. In all cases, a pair of API function parameters such as 12547 ** 12548 ** <pre> 12549 ** int nChangeset, 12550 ** void *pChangeset, 12551 ** </pre> 12552 ** 12553 ** Is replaced by: 12554 ** 12555 ** <pre> 12556 ** int (*xInput)(void *pIn, void *pData, int *pnData), 12557 ** void *pIn, 12558 ** </pre> 12559 ** 12560 ** Each time the xInput callback is invoked by the sessions module, the first 12561 ** argument passed is a copy of the supplied pIn context pointer. The second 12562 ** argument, pData, points to a buffer (*pnData) bytes in size. Assuming no 12563 ** error occurs the xInput method should copy up to (*pnData) bytes of data 12564 ** into the buffer and set (*pnData) to the actual number of bytes copied 12565 ** before returning SQLITE_OK. If the input is completely exhausted, (*pnData) 12566 ** should be set to zero to indicate this. Or, if an error occurs, an SQLite 12567 ** error code should be returned. In all cases, if an xInput callback returns 12568 ** an error, all processing is abandoned and the streaming API function 12569 ** returns a copy of the error code to the caller. 12570 ** 12571 ** In the case of sqlite3changeset_start_strm(), the xInput callback may be 12572 ** invoked by the sessions module at any point during the lifetime of the 12573 ** iterator. If such an xInput callback returns an error, the iterator enters 12574 ** an error state, whereby all subsequent calls to iterator functions 12575 ** immediately fail with the same error code as returned by xInput. 12576 ** 12577 ** Similarly, streaming API functions that return changesets (or patchsets) 12578 ** return them in chunks by way of a callback function instead of via a 12579 ** pointer to a single large buffer. In this case, a pair of parameters such 12580 ** as: 12581 ** 12582 ** <pre> 12583 ** int *pnChangeset, 12584 ** void **ppChangeset, 12585 ** </pre> 12586 ** 12587 ** Is replaced by: 12588 ** 12589 ** <pre> 12590 ** int (*xOutput)(void *pOut, const void *pData, int nData), 12591 ** void *pOut 12592 ** </pre> 12593 ** 12594 ** The xOutput callback is invoked zero or more times to return data to 12595 ** the application. The first parameter passed to each call is a copy of the 12596 ** pOut pointer supplied by the application. The second parameter, pData, 12597 ** points to a buffer nData bytes in size containing the chunk of output 12598 ** data being returned. If the xOutput callback successfully processes the 12599 ** supplied data, it should return SQLITE_OK to indicate success. Otherwise, 12600 ** it should return some other SQLite error code. In this case processing 12601 ** is immediately abandoned and the streaming API function returns a copy 12602 ** of the xOutput error code to the application. 12603 ** 12604 ** The sessions module never invokes an xOutput callback with the third 12605 ** parameter set to a value less than or equal to zero. Other than this, 12606 ** no guarantees are made as to the size of the chunks of data returned. 12607 */ 12608 SQLITE_API int sqlite3changeset_apply_strm( 12609 sqlite3 *db, /* Apply change to "main" db of this handle */ 12610 int (*xInput)(void *pIn, void *pData, int *pnData), /* Input function */ 12611 void *pIn, /* First arg for xInput */ 12612 int(*xFilter)( 12613 void *pCtx, /* Copy of sixth arg to _apply() */ 12614 const char *zTab /* Table name */ 12615 ), 12616 int(*xConflict)( 12617 void *pCtx, /* Copy of sixth arg to _apply() */ 12618 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 12619 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 12620 ), 12621 void *pCtx /* First argument passed to xConflict */ 12622 ); 12623 SQLITE_API int sqlite3changeset_apply_v2_strm( 12624 sqlite3 *db, /* Apply change to "main" db of this handle */ 12625 int (*xInput)(void *pIn, void *pData, int *pnData), /* Input function */ 12626 void *pIn, /* First arg for xInput */ 12627 int(*xFilter)( 12628 void *pCtx, /* Copy of sixth arg to _apply() */ 12629 const char *zTab /* Table name */ 12630 ), 12631 int(*xConflict)( 12632 void *pCtx, /* Copy of sixth arg to _apply() */ 12633 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 12634 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 12635 ), 12636 void *pCtx, /* First argument passed to xConflict */ 12637 void **ppRebase, int *pnRebase, 12638 int flags 12639 ); 12640 SQLITE_API int sqlite3changeset_concat_strm( 12641 int (*xInputA)(void *pIn, void *pData, int *pnData), 12642 void *pInA, 12643 int (*xInputB)(void *pIn, void *pData, int *pnData), 12644 void *pInB, 12645 int (*xOutput)(void *pOut, const void *pData, int nData), 12646 void *pOut 12647 ); 12648 SQLITE_API int sqlite3changeset_invert_strm( 12649 int (*xInput)(void *pIn, void *pData, int *pnData), 12650 void *pIn, 12651 int (*xOutput)(void *pOut, const void *pData, int nData), 12652 void *pOut 12653 ); 12654 SQLITE_API int sqlite3changeset_start_strm( 12655 sqlite3_changeset_iter **pp, 12656 int (*xInput)(void *pIn, void *pData, int *pnData), 12657 void *pIn 12658 ); 12659 SQLITE_API int sqlite3changeset_start_v2_strm( 12660 sqlite3_changeset_iter **pp, 12661 int (*xInput)(void *pIn, void *pData, int *pnData), 12662 void *pIn, 12663 int flags 12664 ); 12665 SQLITE_API int sqlite3session_changeset_strm( 12666 sqlite3_session *pSession, 12667 int (*xOutput)(void *pOut, const void *pData, int nData), 12668 void *pOut 12669 ); 12670 SQLITE_API int sqlite3session_patchset_strm( 12671 sqlite3_session *pSession, 12672 int (*xOutput)(void *pOut, const void *pData, int nData), 12673 void *pOut 12674 ); 12675 SQLITE_API int sqlite3changegroup_add_strm(sqlite3_changegroup*, 12676 int (*xInput)(void *pIn, void *pData, int *pnData), 12677 void *pIn 12678 ); 12679 SQLITE_API int sqlite3changegroup_output_strm(sqlite3_changegroup*, 12680 int (*xOutput)(void *pOut, const void *pData, int nData), 12681 void *pOut 12682 ); 12683 SQLITE_API int sqlite3rebaser_rebase_strm( 12684 sqlite3_rebaser *pRebaser, 12685 int (*xInput)(void *pIn, void *pData, int *pnData), 12686 void *pIn, 12687 int (*xOutput)(void *pOut, const void *pData, int nData), 12688 void *pOut 12689 ); 12690 12691 /* 12692 ** CAPI3REF: Configure global parameters 12693 ** 12694 ** The sqlite3session_config() interface is used to make global configuration 12695 ** changes to the sessions module in order to tune it to the specific needs 12696 ** of the application. 12697 ** 12698 ** The sqlite3session_config() interface is not threadsafe. If it is invoked 12699 ** while any other thread is inside any other sessions method then the 12700 ** results are undefined. Furthermore, if it is invoked after any sessions 12701 ** related objects have been created, the results are also undefined. 12702 ** 12703 ** The first argument to the sqlite3session_config() function must be one 12704 ** of the SQLITE_SESSION_CONFIG_XXX constants defined below. The 12705 ** interpretation of the (void*) value passed as the second parameter and 12706 ** the effect of calling this function depends on the value of the first 12707 ** parameter. 12708 ** 12709 ** <dl> 12710 ** <dt>SQLITE_SESSION_CONFIG_STRMSIZE<dd> 12711 ** By default, the sessions module streaming interfaces attempt to input 12712 ** and output data in approximately 1 KiB chunks. This operand may be used 12713 ** to set and query the value of this configuration setting. The pointer 12714 ** passed as the second argument must point to a value of type (int). 12715 ** If this value is greater than 0, it is used as the new streaming data 12716 ** chunk size for both input and output. Before returning, the (int) value 12717 ** pointed to by pArg is set to the final value of the streaming interface 12718 ** chunk size. 12719 ** </dl> 12720 ** 12721 ** This function returns SQLITE_OK if successful, or an SQLite error code 12722 ** otherwise. 12723 */ 12724 SQLITE_API int sqlite3session_config(int op, void *pArg); 12725 12726 /* 12727 ** CAPI3REF: Values for sqlite3session_config(). 12728 */ 12729 #define SQLITE_SESSION_CONFIG_STRMSIZE 1 12730 12731 /* 12732 ** Make sure we can call this stuff from C++. 12733 */ 12734 #ifdef __cplusplus 12735 } 12736 #endif 12737 12738 #endif /* !defined(__SQLITESESSION_H_) && defined(SQLITE_ENABLE_SESSION) */ 12739 12740 /******** End of sqlite3session.h *********/ 12741 /******** Begin file fts5.h *********/ 12742 /* 12743 ** 2014 May 31 12744 ** 12745 ** The author disclaims copyright to this source code. In place of 12746 ** a legal notice, here is a blessing: 12747 ** 12748 ** May you do good and not evil. 12749 ** May you find forgiveness for yourself and forgive others. 12750 ** May you share freely, never taking more than you give. 12751 ** 12752 ****************************************************************************** 12753 ** 12754 ** Interfaces to extend FTS5. Using the interfaces defined in this file, 12755 ** FTS5 may be extended with: 12756 ** 12757 ** * custom tokenizers, and 12758 ** * custom auxiliary functions. 12759 */ 12760 12761 12762 #ifndef _FTS5_H 12763 #define _FTS5_H 12764 12765 12766 #ifdef __cplusplus 12767 extern "C" { 12768 #endif 12769 12770 /************************************************************************* 12771 ** CUSTOM AUXILIARY FUNCTIONS 12772 ** 12773 ** Virtual table implementations may overload SQL functions by implementing 12774 ** the sqlite3_module.xFindFunction() method. 12775 */ 12776 12777 typedef struct Fts5ExtensionApi Fts5ExtensionApi; 12778 typedef struct Fts5Context Fts5Context; 12779 typedef struct Fts5PhraseIter Fts5PhraseIter; 12780 12781 typedef void (*fts5_extension_function)( 12782 const Fts5ExtensionApi *pApi, /* API offered by current FTS version */ 12783 Fts5Context *pFts, /* First arg to pass to pApi functions */ 12784 sqlite3_context *pCtx, /* Context for returning result/error */ 12785 int nVal, /* Number of values in apVal[] array */ 12786 sqlite3_value **apVal /* Array of trailing arguments */ 12787 ); 12788 12789 struct Fts5PhraseIter { 12790 const unsigned char *a; 12791 const unsigned char *b; 12792 }; 12793 12794 /* 12795 ** EXTENSION API FUNCTIONS 12796 ** 12797 ** xUserData(pFts): 12798 ** Return a copy of the context pointer the extension function was 12799 ** registered with. 12800 ** 12801 ** xColumnTotalSize(pFts, iCol, pnToken): 12802 ** If parameter iCol is less than zero, set output variable *pnToken 12803 ** to the total number of tokens in the FTS5 table. Or, if iCol is 12804 ** non-negative but less than the number of columns in the table, return 12805 ** the total number of tokens in column iCol, considering all rows in 12806 ** the FTS5 table. 12807 ** 12808 ** If parameter iCol is greater than or equal to the number of columns 12809 ** in the table, SQLITE_RANGE is returned. Or, if an error occurs (e.g. 12810 ** an OOM condition or IO error), an appropriate SQLite error code is 12811 ** returned. 12812 ** 12813 ** xColumnCount(pFts): 12814 ** Return the number of columns in the table. 12815 ** 12816 ** xColumnSize(pFts, iCol, pnToken): 12817 ** If parameter iCol is less than zero, set output variable *pnToken 12818 ** to the total number of tokens in the current row. Or, if iCol is 12819 ** non-negative but less than the number of columns in the table, set 12820 ** *pnToken to the number of tokens in column iCol of the current row. 12821 ** 12822 ** If parameter iCol is greater than or equal to the number of columns 12823 ** in the table, SQLITE_RANGE is returned. Or, if an error occurs (e.g. 12824 ** an OOM condition or IO error), an appropriate SQLite error code is 12825 ** returned. 12826 ** 12827 ** This function may be quite inefficient if used with an FTS5 table 12828 ** created with the "columnsize=0" option. 12829 ** 12830 ** xColumnText: 12831 ** This function attempts to retrieve the text of column iCol of the 12832 ** current document. If successful, (*pz) is set to point to a buffer 12833 ** containing the text in utf-8 encoding, (*pn) is set to the size in bytes 12834 ** (not characters) of the buffer and SQLITE_OK is returned. Otherwise, 12835 ** if an error occurs, an SQLite error code is returned and the final values 12836 ** of (*pz) and (*pn) are undefined. 12837 ** 12838 ** xPhraseCount: 12839 ** Returns the number of phrases in the current query expression. 12840 ** 12841 ** xPhraseSize: 12842 ** Returns the number of tokens in phrase iPhrase of the query. Phrases 12843 ** are numbered starting from zero. 12844 ** 12845 ** xInstCount: 12846 ** Set *pnInst to the total number of occurrences of all phrases within 12847 ** the query within the current row. Return SQLITE_OK if successful, or 12848 ** an error code (i.e. SQLITE_NOMEM) if an error occurs. 12849 ** 12850 ** This API can be quite slow if used with an FTS5 table created with the 12851 ** "detail=none" or "detail=column" option. If the FTS5 table is created 12852 ** with either "detail=none" or "detail=column" and "content=" option 12853 ** (i.e. if it is a contentless table), then this API always returns 0. 12854 ** 12855 ** xInst: 12856 ** Query for the details of phrase match iIdx within the current row. 12857 ** Phrase matches are numbered starting from zero, so the iIdx argument 12858 ** should be greater than or equal to zero and smaller than the value 12859 ** output by xInstCount(). 12860 ** 12861 ** Usually, output parameter *piPhrase is set to the phrase number, *piCol 12862 ** to the column in which it occurs and *piOff the token offset of the 12863 ** first token of the phrase. Returns SQLITE_OK if successful, or an error 12864 ** code (i.e. SQLITE_NOMEM) if an error occurs. 12865 ** 12866 ** This API can be quite slow if used with an FTS5 table created with the 12867 ** "detail=none" or "detail=column" option. 12868 ** 12869 ** xRowid: 12870 ** Returns the rowid of the current row. 12871 ** 12872 ** xTokenize: 12873 ** Tokenize text using the tokenizer belonging to the FTS5 table. 12874 ** 12875 ** xQueryPhrase(pFts5, iPhrase, pUserData, xCallback): 12876 ** This API function is used to query the FTS table for phrase iPhrase 12877 ** of the current query. Specifically, a query equivalent to: 12878 ** 12879 ** ... FROM ftstable WHERE ftstable MATCH $p ORDER BY rowid 12880 ** 12881 ** with $p set to a phrase equivalent to the phrase iPhrase of the 12882 ** current query is executed. Any column filter that applies to 12883 ** phrase iPhrase of the current query is included in $p. For each 12884 ** row visited, the callback function passed as the fourth argument 12885 ** is invoked. The context and API objects passed to the callback 12886 ** function may be used to access the properties of each matched row. 12887 ** Invoking Api.xUserData() returns a copy of the pointer passed as 12888 ** the third argument to pUserData. 12889 ** 12890 ** If the callback function returns any value other than SQLITE_OK, the 12891 ** query is abandoned and the xQueryPhrase function returns immediately. 12892 ** If the returned value is SQLITE_DONE, xQueryPhrase returns SQLITE_OK. 12893 ** Otherwise, the error code is propagated upwards. 12894 ** 12895 ** If the query runs to completion without incident, SQLITE_OK is returned. 12896 ** Or, if some error occurs before the query completes or is aborted by 12897 ** the callback, an SQLite error code is returned. 12898 ** 12899 ** 12900 ** xSetAuxdata(pFts5, pAux, xDelete) 12901 ** 12902 ** Save the pointer passed as the second argument as the extension function's 12903 ** "auxiliary data". The pointer may then be retrieved by the current or any 12904 ** future invocation of the same fts5 extension function made as part of 12905 ** the same MATCH query using the xGetAuxdata() API. 12906 ** 12907 ** Each extension function is allocated a single auxiliary data slot for 12908 ** each FTS query (MATCH expression). If the extension function is invoked 12909 ** more than once for a single FTS query, then all invocations share a 12910 ** single auxiliary data context. 12911 ** 12912 ** If there is already an auxiliary data pointer when this function is 12913 ** invoked, then it is replaced by the new pointer. If an xDelete callback 12914 ** was specified along with the original pointer, it is invoked at this 12915 ** point. 12916 ** 12917 ** The xDelete callback, if one is specified, is also invoked on the 12918 ** auxiliary data pointer after the FTS5 query has finished. 12919 ** 12920 ** If an error (e.g. an OOM condition) occurs within this function, 12921 ** the auxiliary data is set to NULL and an error code returned. If the 12922 ** xDelete parameter was not NULL, it is invoked on the auxiliary data 12923 ** pointer before returning. 12924 ** 12925 ** 12926 ** xGetAuxdata(pFts5, bClear) 12927 ** 12928 ** Returns the current auxiliary data pointer for the fts5 extension 12929 ** function. See the xSetAuxdata() method for details. 12930 ** 12931 ** If the bClear argument is non-zero, then the auxiliary data is cleared 12932 ** (set to NULL) before this function returns. In this case the xDelete, 12933 ** if any, is not invoked. 12934 ** 12935 ** 12936 ** xRowCount(pFts5, pnRow) 12937 ** 12938 ** This function is used to retrieve the total number of rows in the table. 12939 ** In other words, the same value that would be returned by: 12940 ** 12941 ** SELECT count(*) FROM ftstable; 12942 ** 12943 ** xPhraseFirst() 12944 ** This function is used, along with type Fts5PhraseIter and the xPhraseNext 12945 ** method, to iterate through all instances of a single query phrase within 12946 ** the current row. This is the same information as is accessible via the 12947 ** xInstCount/xInst APIs. While the xInstCount/xInst APIs are more convenient 12948 ** to use, this API may be faster under some circumstances. To iterate 12949 ** through instances of phrase iPhrase, use the following code: 12950 ** 12951 ** Fts5PhraseIter iter; 12952 ** int iCol, iOff; 12953 ** for(pApi->xPhraseFirst(pFts, iPhrase, &iter, &iCol, &iOff); 12954 ** iCol>=0; 12955 ** pApi->xPhraseNext(pFts, &iter, &iCol, &iOff) 12956 ** ){ 12957 ** // An instance of phrase iPhrase at offset iOff of column iCol 12958 ** } 12959 ** 12960 ** The Fts5PhraseIter structure is defined above. Applications should not 12961 ** modify this structure directly - it should only be used as shown above 12962 ** with the xPhraseFirst() and xPhraseNext() API methods (and by 12963 ** xPhraseFirstColumn() and xPhraseNextColumn() as illustrated below). 12964 ** 12965 ** This API can be quite slow if used with an FTS5 table created with the 12966 ** "detail=none" or "detail=column" option. If the FTS5 table is created 12967 ** with either "detail=none" or "detail=column" and "content=" option 12968 ** (i.e. if it is a contentless table), then this API always iterates 12969 ** through an empty set (all calls to xPhraseFirst() set iCol to -1). 12970 ** 12971 ** xPhraseNext() 12972 ** See xPhraseFirst above. 12973 ** 12974 ** xPhraseFirstColumn() 12975 ** This function and xPhraseNextColumn() are similar to the xPhraseFirst() 12976 ** and xPhraseNext() APIs described above. The difference is that instead 12977 ** of iterating through all instances of a phrase in the current row, these 12978 ** APIs are used to iterate through the set of columns in the current row 12979 ** that contain one or more instances of a specified phrase. For example: 12980 ** 12981 ** Fts5PhraseIter iter; 12982 ** int iCol; 12983 ** for(pApi->xPhraseFirstColumn(pFts, iPhrase, &iter, &iCol); 12984 ** iCol>=0; 12985 ** pApi->xPhraseNextColumn(pFts, &iter, &iCol) 12986 ** ){ 12987 ** // Column iCol contains at least one instance of phrase iPhrase 12988 ** } 12989 ** 12990 ** This API can be quite slow if used with an FTS5 table created with the 12991 ** "detail=none" option. If the FTS5 table is created with either 12992 ** "detail=none" "content=" option (i.e. if it is a contentless table), 12993 ** then this API always iterates through an empty set (all calls to 12994 ** xPhraseFirstColumn() set iCol to -1). 12995 ** 12996 ** The information accessed using this API and its companion 12997 ** xPhraseFirstColumn() may also be obtained using xPhraseFirst/xPhraseNext 12998 ** (or xInst/xInstCount). The chief advantage of this API is that it is 12999 ** significantly more efficient than those alternatives when used with 13000 ** "detail=column" tables. 13001 ** 13002 ** xPhraseNextColumn() 13003 ** See xPhraseFirstColumn above. 13004 */ 13005 struct Fts5ExtensionApi { 13006 int iVersion; /* Currently always set to 2 */ 13007 13008 void *(*xUserData)(Fts5Context*); 13009 13010 int (*xColumnCount)(Fts5Context*); 13011 int (*xRowCount)(Fts5Context*, sqlite3_int64 *pnRow); 13012 int (*xColumnTotalSize)(Fts5Context*, int iCol, sqlite3_int64 *pnToken); 13013 13014 int (*xTokenize)(Fts5Context*, 13015 const char *pText, int nText, /* Text to tokenize */ 13016 void *pCtx, /* Context passed to xToken() */ 13017 int (*xToken)(void*, int, const char*, int, int, int) /* Callback */ 13018 ); 13019 13020 int (*xPhraseCount)(Fts5Context*); 13021 int (*xPhraseSize)(Fts5Context*, int iPhrase); 13022 13023 int (*xInstCount)(Fts5Context*, int *pnInst); 13024 int (*xInst)(Fts5Context*, int iIdx, int *piPhrase, int *piCol, int *piOff); 13025 13026 sqlite3_int64 (*xRowid)(Fts5Context*); 13027 int (*xColumnText)(Fts5Context*, int iCol, const char **pz, int *pn); 13028 int (*xColumnSize)(Fts5Context*, int iCol, int *pnToken); 13029 13030 int (*xQueryPhrase)(Fts5Context*, int iPhrase, void *pUserData, 13031 int(*)(const Fts5ExtensionApi*,Fts5Context*,void*) 13032 ); 13033 int (*xSetAuxdata)(Fts5Context*, void *pAux, void(*xDelete)(void*)); 13034 void *(*xGetAuxdata)(Fts5Context*, int bClear); 13035 13036 int (*xPhraseFirst)(Fts5Context*, int iPhrase, Fts5PhraseIter*, int*, int*); 13037 void (*xPhraseNext)(Fts5Context*, Fts5PhraseIter*, int *piCol, int *piOff); 13038 13039 int (*xPhraseFirstColumn)(Fts5Context*, int iPhrase, Fts5PhraseIter*, int*); 13040 void (*xPhraseNextColumn)(Fts5Context*, Fts5PhraseIter*, int *piCol); 13041 }; 13042 13043 /* 13044 ** CUSTOM AUXILIARY FUNCTIONS 13045 *************************************************************************/ 13046 13047 /************************************************************************* 13048 ** CUSTOM TOKENIZERS 13049 ** 13050 ** Applications may also register custom tokenizer types. A tokenizer 13051 ** is registered by providing fts5 with a populated instance of the 13052 ** following structure. All structure methods must be defined, setting 13053 ** any member of the fts5_tokenizer struct to NULL leads to undefined 13054 ** behaviour. The structure methods are expected to function as follows: 13055 ** 13056 ** xCreate: 13057 ** This function is used to allocate and initialize a tokenizer instance. 13058 ** A tokenizer instance is required to actually tokenize text. 13059 ** 13060 ** The first argument passed to this function is a copy of the (void*) 13061 ** pointer provided by the application when the fts5_tokenizer object 13062 ** was registered with FTS5 (the third argument to xCreateTokenizer()). 13063 ** The second and third arguments are an array of nul-terminated strings 13064 ** containing the tokenizer arguments, if any, specified following the 13065 ** tokenizer name as part of the CREATE VIRTUAL TABLE statement used 13066 ** to create the FTS5 table. 13067 ** 13068 ** The final argument is an output variable. If successful, (*ppOut) 13069 ** should be set to point to the new tokenizer handle and SQLITE_OK 13070 ** returned. If an error occurs, some value other than SQLITE_OK should 13071 ** be returned. In this case, fts5 assumes that the final value of *ppOut 13072 ** is undefined. 13073 ** 13074 ** xDelete: 13075 ** This function is invoked to delete a tokenizer handle previously 13076 ** allocated using xCreate(). Fts5 guarantees that this function will 13077 ** be invoked exactly once for each successful call to xCreate(). 13078 ** 13079 ** xTokenize: 13080 ** This function is expected to tokenize the nText byte string indicated 13081 ** by argument pText. pText may or may not be nul-terminated. The first 13082 ** argument passed to this function is a pointer to an Fts5Tokenizer object 13083 ** returned by an earlier call to xCreate(). 13084 ** 13085 ** The second argument indicates the reason that FTS5 is requesting 13086 ** tokenization of the supplied text. This is always one of the following 13087 ** four values: 13088 ** 13089 ** <ul><li> <b>FTS5_TOKENIZE_DOCUMENT</b> - A document is being inserted into 13090 ** or removed from the FTS table. The tokenizer is being invoked to 13091 ** determine the set of tokens to add to (or delete from) the 13092 ** FTS index. 13093 ** 13094 ** <li> <b>FTS5_TOKENIZE_QUERY</b> - A MATCH query is being executed 13095 ** against the FTS index. The tokenizer is being called to tokenize 13096 ** a bareword or quoted string specified as part of the query. 13097 ** 13098 ** <li> <b>(FTS5_TOKENIZE_QUERY | FTS5_TOKENIZE_PREFIX)</b> - Same as 13099 ** FTS5_TOKENIZE_QUERY, except that the bareword or quoted string is 13100 ** followed by a "*" character, indicating that the last token 13101 ** returned by the tokenizer will be treated as a token prefix. 13102 ** 13103 ** <li> <b>FTS5_TOKENIZE_AUX</b> - The tokenizer is being invoked to 13104 ** satisfy an fts5_api.xTokenize() request made by an auxiliary 13105 ** function. Or an fts5_api.xColumnSize() request made by the same 13106 ** on a columnsize=0 database. 13107 ** </ul> 13108 ** 13109 ** For each token in the input string, the supplied callback xToken() must 13110 ** be invoked. The first argument to it should be a copy of the pointer 13111 ** passed as the second argument to xTokenize(). The third and fourth 13112 ** arguments are a pointer to a buffer containing the token text, and the 13113 ** size of the token in bytes. The 4th and 5th arguments are the byte offsets 13114 ** of the first byte of and first byte immediately following the text from 13115 ** which the token is derived within the input. 13116 ** 13117 ** The second argument passed to the xToken() callback ("tflags") should 13118 ** normally be set to 0. The exception is if the tokenizer supports 13119 ** synonyms. In this case see the discussion below for details. 13120 ** 13121 ** FTS5 assumes the xToken() callback is invoked for each token in the 13122 ** order that they occur within the input text. 13123 ** 13124 ** If an xToken() callback returns any value other than SQLITE_OK, then 13125 ** the tokenization should be abandoned and the xTokenize() method should 13126 ** immediately return a copy of the xToken() return value. Or, if the 13127 ** input buffer is exhausted, xTokenize() should return SQLITE_OK. Finally, 13128 ** if an error occurs with the xTokenize() implementation itself, it 13129 ** may abandon the tokenization and return any error code other than 13130 ** SQLITE_OK or SQLITE_DONE. 13131 ** 13132 ** SYNONYM SUPPORT 13133 ** 13134 ** Custom tokenizers may also support synonyms. Consider a case in which a 13135 ** user wishes to query for a phrase such as "first place". Using the 13136 ** built-in tokenizers, the FTS5 query 'first + place' will match instances 13137 ** of "first place" within the document set, but not alternative forms 13138 ** such as "1st place". In some applications, it would be better to match 13139 ** all instances of "first place" or "1st place" regardless of which form 13140 ** the user specified in the MATCH query text. 13141 ** 13142 ** There are several ways to approach this in FTS5: 13143 ** 13144 ** <ol><li> By mapping all synonyms to a single token. In this case, using 13145 ** the above example, this means that the tokenizer returns the 13146 ** same token for inputs "first" and "1st". Say that token is in 13147 ** fact "first", so that when the user inserts the document "I won 13148 ** 1st place" entries are added to the index for tokens "i", "won", 13149 ** "first" and "place". If the user then queries for '1st + place', 13150 ** the tokenizer substitutes "first" for "1st" and the query works 13151 ** as expected. 13152 ** 13153 ** <li> By querying the index for all synonyms of each query term 13154 ** separately. In this case, when tokenizing query text, the 13155 ** tokenizer may provide multiple synonyms for a single term 13156 ** within the document. FTS5 then queries the index for each 13157 ** synonym individually. For example, faced with the query: 13158 ** 13159 ** <codeblock> 13160 ** ... MATCH 'first place'</codeblock> 13161 ** 13162 ** the tokenizer offers both "1st" and "first" as synonyms for the 13163 ** first token in the MATCH query and FTS5 effectively runs a query 13164 ** similar to: 13165 ** 13166 ** <codeblock> 13167 ** ... MATCH '(first OR 1st) place'</codeblock> 13168 ** 13169 ** except that, for the purposes of auxiliary functions, the query 13170 ** still appears to contain just two phrases - "(first OR 1st)" 13171 ** being treated as a single phrase. 13172 ** 13173 ** <li> By adding multiple synonyms for a single term to the FTS index. 13174 ** Using this method, when tokenizing document text, the tokenizer 13175 ** provides multiple synonyms for each token. So that when a 13176 ** document such as "I won first place" is tokenized, entries are 13177 ** added to the FTS index for "i", "won", "first", "1st" and 13178 ** "place". 13179 ** 13180 ** This way, even if the tokenizer does not provide synonyms 13181 ** when tokenizing query text (it should not - to do so would be 13182 ** inefficient), it doesn't matter if the user queries for 13183 ** 'first + place' or '1st + place', as there are entries in the 13184 ** FTS index corresponding to both forms of the first token. 13185 ** </ol> 13186 ** 13187 ** Whether it is parsing document or query text, any call to xToken that 13188 ** specifies a <i>tflags</i> argument with the FTS5_TOKEN_COLOCATED bit 13189 ** is considered to supply a synonym for the previous token. For example, 13190 ** when parsing the document "I won first place", a tokenizer that supports 13191 ** synonyms would call xToken() 5 times, as follows: 13192 ** 13193 ** <codeblock> 13194 ** xToken(pCtx, 0, "i", 1, 0, 1); 13195 ** xToken(pCtx, 0, "won", 3, 2, 5); 13196 ** xToken(pCtx, 0, "first", 5, 6, 11); 13197 ** xToken(pCtx, FTS5_TOKEN_COLOCATED, "1st", 3, 6, 11); 13198 ** xToken(pCtx, 0, "place", 5, 12, 17); 13199 **</codeblock> 13200 ** 13201 ** It is an error to specify the FTS5_TOKEN_COLOCATED flag the first time 13202 ** xToken() is called. Multiple synonyms may be specified for a single token 13203 ** by making multiple calls to xToken(FTS5_TOKEN_COLOCATED) in sequence. 13204 ** There is no limit to the number of synonyms that may be provided for a 13205 ** single token. 13206 ** 13207 ** In many cases, method (1) above is the best approach. It does not add 13208 ** extra data to the FTS index or require FTS5 to query for multiple terms, 13209 ** so it is efficient in terms of disk space and query speed. However, it 13210 ** does not support prefix queries very well. If, as suggested above, the 13211 ** token "first" is substituted for "1st" by the tokenizer, then the query: 13212 ** 13213 ** <codeblock> 13214 ** ... MATCH '1s*'</codeblock> 13215 ** 13216 ** will not match documents that contain the token "1st" (as the tokenizer 13217 ** will probably not map "1s" to any prefix of "first"). 13218 ** 13219 ** For full prefix support, method (3) may be preferred. In this case, 13220 ** because the index contains entries for both "first" and "1st", prefix 13221 ** queries such as 'fi*' or '1s*' will match correctly. However, because 13222 ** extra entries are added to the FTS index, this method uses more space 13223 ** within the database. 13224 ** 13225 ** Method (2) offers a midpoint between (1) and (3). Using this method, 13226 ** a query such as '1s*' will match documents that contain the literal 13227 ** token "1st", but not "first" (assuming the tokenizer is not able to 13228 ** provide synonyms for prefixes). However, a non-prefix query like '1st' 13229 ** will match against "1st" and "first". This method does not require 13230 ** extra disk space, as no extra entries are added to the FTS index. 13231 ** On the other hand, it may require more CPU cycles to run MATCH queries, 13232 ** as separate queries of the FTS index are required for each synonym. 13233 ** 13234 ** When using methods (2) or (3), it is important that the tokenizer only 13235 ** provide synonyms when tokenizing document text (method (3)) or query 13236 ** text (method (2)), not both. Doing so will not cause any errors, but is 13237 ** inefficient. 13238 */ 13239 typedef struct Fts5Tokenizer Fts5Tokenizer; 13240 typedef struct fts5_tokenizer fts5_tokenizer; 13241 struct fts5_tokenizer { 13242 int (*xCreate)(void*, const char **azArg, int nArg, Fts5Tokenizer **ppOut); 13243 void (*xDelete)(Fts5Tokenizer*); 13244 int (*xTokenize)(Fts5Tokenizer*, 13245 void *pCtx, 13246 int flags, /* Mask of FTS5_TOKENIZE_* flags */ 13247 const char *pText, int nText, 13248 int (*xToken)( 13249 void *pCtx, /* Copy of 2nd argument to xTokenize() */ 13250 int tflags, /* Mask of FTS5_TOKEN_* flags */ 13251 const char *pToken, /* Pointer to buffer containing token */ 13252 int nToken, /* Size of token in bytes */ 13253 int iStart, /* Byte offset of token within input text */ 13254 int iEnd /* Byte offset of end of token within input text */ 13255 ) 13256 ); 13257 }; 13258 13259 /* Flags that may be passed as the third argument to xTokenize() */ 13260 #define FTS5_TOKENIZE_QUERY 0x0001 13261 #define FTS5_TOKENIZE_PREFIX 0x0002 13262 #define FTS5_TOKENIZE_DOCUMENT 0x0004 13263 #define FTS5_TOKENIZE_AUX 0x0008 13264 13265 /* Flags that may be passed by the tokenizer implementation back to FTS5 13266 ** as the third argument to the supplied xToken callback. */ 13267 #define FTS5_TOKEN_COLOCATED 0x0001 /* Same position as prev. token */ 13268 13269 /* 13270 ** END OF CUSTOM TOKENIZERS 13271 *************************************************************************/ 13272 13273 /************************************************************************* 13274 ** FTS5 EXTENSION REGISTRATION API 13275 */ 13276 typedef struct fts5_api fts5_api; 13277 struct fts5_api { 13278 int iVersion; /* Currently always set to 2 */ 13279 13280 /* Create a new tokenizer */ 13281 int (*xCreateTokenizer)( 13282 fts5_api *pApi, 13283 const char *zName, 13284 void *pUserData, 13285 fts5_tokenizer *pTokenizer, 13286 void (*xDestroy)(void*) 13287 ); 13288 13289 /* Find an existing tokenizer */ 13290 int (*xFindTokenizer)( 13291 fts5_api *pApi, 13292 const char *zName, 13293 void **ppUserData, 13294 fts5_tokenizer *pTokenizer 13295 ); 13296 13297 /* Create a new auxiliary function */ 13298 int (*xCreateFunction)( 13299 fts5_api *pApi, 13300 const char *zName, 13301 void *pUserData, 13302 fts5_extension_function xFunction, 13303 void (*xDestroy)(void*) 13304 ); 13305 }; 13306 13307 /* 13308 ** END OF REGISTRATION API 13309 *************************************************************************/ 13310 13311 #ifdef __cplusplus 13312 } /* end of the 'extern "C"' block */ 13313 #endif 13314 13315 #endif /* _FTS5_H */ 13316 13317 /******** End of fts5.h *********/ 13318