1 /* 2 ** 2001 September 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 ** Provide the ability to override linkage features of the interface. 47 */ 48 #ifndef SQLITE_EXTERN 49 # define SQLITE_EXTERN extern 50 #endif 51 #ifndef SQLITE_API 52 # define SQLITE_API 53 #endif 54 #ifndef SQLITE_CDECL 55 # define SQLITE_CDECL 56 #endif 57 #ifndef SQLITE_APICALL 58 # define SQLITE_APICALL 59 #endif 60 #ifndef SQLITE_STDCALL 61 # define SQLITE_STDCALL SQLITE_APICALL 62 #endif 63 #ifndef SQLITE_CALLBACK 64 # define SQLITE_CALLBACK 65 #endif 66 #ifndef SQLITE_SYSAPI 67 # define SQLITE_SYSAPI 68 #endif 69 70 /* 71 ** These no-op macros are used in front of interfaces to mark those 72 ** interfaces as either deprecated or experimental. New applications 73 ** should not use deprecated interfaces - they are supported for backwards 74 ** compatibility only. Application writers should be aware that 75 ** experimental interfaces are subject to change in point releases. 76 ** 77 ** These macros used to resolve to various kinds of compiler magic that 78 ** would generate warning messages when they were used. But that 79 ** compiler magic ended up generating such a flurry of bug reports 80 ** that we have taken it all out and gone back to using simple 81 ** noop macros. 82 */ 83 #define SQLITE_DEPRECATED 84 #define SQLITE_EXPERIMENTAL 85 86 /* 87 ** Ensure these symbols were not defined by some previous header file. 88 */ 89 #ifdef SQLITE_VERSION 90 # undef SQLITE_VERSION 91 #endif 92 #ifdef SQLITE_VERSION_NUMBER 93 # undef SQLITE_VERSION_NUMBER 94 #endif 95 96 /* 97 ** CAPI3REF: Compile-Time Library Version Numbers 98 ** 99 ** ^(The [SQLITE_VERSION] C preprocessor macro in the sqlite3.h header 100 ** evaluates to a string literal that is the SQLite version in the 101 ** format "X.Y.Z" where X is the major version number (always 3 for 102 ** SQLite3) and Y is the minor version number and Z is the release number.)^ 103 ** ^(The [SQLITE_VERSION_NUMBER] C preprocessor macro resolves to an integer 104 ** with the value (X*1000000 + Y*1000 + Z) where X, Y, and Z are the same 105 ** numbers used in [SQLITE_VERSION].)^ 106 ** The SQLITE_VERSION_NUMBER for any given release of SQLite will also 107 ** be larger than the release from which it is derived. Either Y will 108 ** be held constant and Z will be incremented or else Y will be incremented 109 ** and Z will be reset to zero. 110 ** 111 ** Since [version 3.6.18] ([dateof:3.6.18]), 112 ** SQLite source code has been stored in the 113 ** <a href="http://www.fossil-scm.org/">Fossil configuration management 114 ** system</a>. ^The SQLITE_SOURCE_ID macro evaluates to 115 ** a string which identifies a particular check-in of SQLite 116 ** within its configuration management system. ^The SQLITE_SOURCE_ID 117 ** string contains the date and time of the check-in (UTC) and a SHA1 118 ** or SHA3-256 hash of the entire source tree. 119 ** 120 ** See also: [sqlite3_libversion()], 121 ** [sqlite3_libversion_number()], [sqlite3_sourceid()], 122 ** [sqlite_version()] and [sqlite_source_id()]. 123 */ 124 #define SQLITE_VERSION "3.18.2" 125 #define SQLITE_VERSION_NUMBER 3018002 126 #define SQLITE_SOURCE_ID "2017-07-21 07:56:09 8201f4e1c566f7223c71c07e6b703d1352801f1b2daa0fd00895a18e1944cb4d" 127 128 /* 129 ** CAPI3REF: Run-Time Library Version Numbers 130 ** KEYWORDS: sqlite3_version sqlite3_sourceid 131 ** 132 ** These interfaces provide the same information as the [SQLITE_VERSION], 133 ** [SQLITE_VERSION_NUMBER], and [SQLITE_SOURCE_ID] C preprocessor macros 134 ** but are associated with the library instead of the header file. ^(Cautious 135 ** programmers might include assert() statements in their application to 136 ** verify that values returned by these interfaces match the macros in 137 ** the header, and thus ensure that the application is 138 ** compiled with matching library and header files. 139 ** 140 ** <blockquote><pre> 141 ** assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER ); 142 ** assert( strcmp(sqlite3_sourceid(),SQLITE_SOURCE_ID)==0 ); 143 ** assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0 ); 144 ** </pre></blockquote>)^ 145 ** 146 ** ^The sqlite3_version[] string constant contains the text of [SQLITE_VERSION] 147 ** macro. ^The sqlite3_libversion() function returns a pointer to the 148 ** to the sqlite3_version[] string constant. The sqlite3_libversion() 149 ** function is provided for use in DLLs since DLL users usually do not have 150 ** direct access to string constants within the DLL. ^The 151 ** sqlite3_libversion_number() function returns an integer equal to 152 ** [SQLITE_VERSION_NUMBER]. ^The sqlite3_sourceid() function returns 153 ** a pointer to a string constant whose value is the same as the 154 ** [SQLITE_SOURCE_ID] C preprocessor macro. 155 ** 156 ** See also: [sqlite_version()] and [sqlite_source_id()]. 157 */ 158 SQLITE_API SQLITE_EXTERN const char sqlite3_version[]; 159 SQLITE_API const char *sqlite3_libversion(void); 160 SQLITE_API const char *sqlite3_sourceid(void); 161 SQLITE_API int sqlite3_libversion_number(void); 162 163 /* 164 ** CAPI3REF: Run-Time Library Compilation Options Diagnostics 165 ** 166 ** ^The sqlite3_compileoption_used() function returns 0 or 1 167 ** indicating whether the specified option was defined at 168 ** compile time. ^The SQLITE_ prefix may be omitted from the 169 ** option name passed to sqlite3_compileoption_used(). 170 ** 171 ** ^The sqlite3_compileoption_get() function allows iterating 172 ** over the list of options that were defined at compile time by 173 ** returning the N-th compile time option string. ^If N is out of range, 174 ** sqlite3_compileoption_get() returns a NULL pointer. ^The SQLITE_ 175 ** prefix is omitted from any strings returned by 176 ** sqlite3_compileoption_get(). 177 ** 178 ** ^Support for the diagnostic functions sqlite3_compileoption_used() 179 ** and sqlite3_compileoption_get() may be omitted by specifying the 180 ** [SQLITE_OMIT_COMPILEOPTION_DIAGS] option at compile time. 181 ** 182 ** See also: SQL functions [sqlite_compileoption_used()] and 183 ** [sqlite_compileoption_get()] and the [compile_options pragma]. 184 */ 185 #ifndef SQLITE_OMIT_COMPILEOPTION_DIAGS 186 SQLITE_API int sqlite3_compileoption_used(const char *zOptName); 187 SQLITE_API const char *sqlite3_compileoption_get(int N); 188 #endif 189 190 /* 191 ** CAPI3REF: Test To See If The Library Is Threadsafe 192 ** 193 ** ^The sqlite3_threadsafe() function returns zero if and only if 194 ** SQLite was compiled with mutexing code omitted due to the 195 ** [SQLITE_THREADSAFE] compile-time option being set to 0. 196 ** 197 ** SQLite can be compiled with or without mutexes. When 198 ** the [SQLITE_THREADSAFE] C preprocessor macro is 1 or 2, mutexes 199 ** are enabled and SQLite is threadsafe. When the 200 ** [SQLITE_THREADSAFE] macro is 0, 201 ** the mutexes are omitted. Without the mutexes, it is not safe 202 ** to use SQLite concurrently from more than one thread. 203 ** 204 ** Enabling mutexes incurs a measurable performance penalty. 205 ** So if speed is of utmost importance, it makes sense to disable 206 ** the mutexes. But for maximum safety, mutexes should be enabled. 207 ** ^The default behavior is for mutexes to be enabled. 208 ** 209 ** This interface can be used by an application to make sure that the 210 ** version of SQLite that it is linking against was compiled with 211 ** the desired setting of the [SQLITE_THREADSAFE] macro. 212 ** 213 ** This interface only reports on the compile-time mutex setting 214 ** of the [SQLITE_THREADSAFE] flag. If SQLite is compiled with 215 ** SQLITE_THREADSAFE=1 or =2 then mutexes are enabled by default but 216 ** can be fully or partially disabled using a call to [sqlite3_config()] 217 ** with the verbs [SQLITE_CONFIG_SINGLETHREAD], [SQLITE_CONFIG_MULTITHREAD], 218 ** or [SQLITE_CONFIG_SERIALIZED]. ^(The return value of the 219 ** sqlite3_threadsafe() function shows only the compile-time setting of 220 ** thread safety, not any run-time changes to that setting made by 221 ** sqlite3_config(). In other words, the return value from sqlite3_threadsafe() 222 ** is unchanged by calls to sqlite3_config().)^ 223 ** 224 ** See the [threading mode] documentation for additional information. 225 */ 226 SQLITE_API int sqlite3_threadsafe(void); 227 228 /* 229 ** CAPI3REF: Database Connection Handle 230 ** KEYWORDS: {database connection} {database connections} 231 ** 232 ** Each open SQLite database is represented by a pointer to an instance of 233 ** the opaque structure named "sqlite3". It is useful to think of an sqlite3 234 ** pointer as an object. The [sqlite3_open()], [sqlite3_open16()], and 235 ** [sqlite3_open_v2()] interfaces are its constructors, and [sqlite3_close()] 236 ** and [sqlite3_close_v2()] are its destructors. There are many other 237 ** interfaces (such as 238 ** [sqlite3_prepare_v2()], [sqlite3_create_function()], and 239 ** [sqlite3_busy_timeout()] to name but three) that are methods on an 240 ** sqlite3 object. 241 */ 242 typedef struct sqlite3 sqlite3; 243 244 /* 245 ** CAPI3REF: 64-Bit Integer Types 246 ** KEYWORDS: sqlite_int64 sqlite_uint64 247 ** 248 ** Because there is no cross-platform way to specify 64-bit integer types 249 ** SQLite includes typedefs for 64-bit signed and unsigned integers. 250 ** 251 ** The sqlite3_int64 and sqlite3_uint64 are the preferred type definitions. 252 ** The sqlite_int64 and sqlite_uint64 types are supported for backwards 253 ** compatibility only. 254 ** 255 ** ^The sqlite3_int64 and sqlite_int64 types can store integer values 256 ** between -9223372036854775808 and +9223372036854775807 inclusive. ^The 257 ** sqlite3_uint64 and sqlite_uint64 types can store integer values 258 ** between 0 and +18446744073709551615 inclusive. 259 */ 260 #ifdef SQLITE_INT64_TYPE 261 typedef SQLITE_INT64_TYPE sqlite_int64; 262 # ifdef SQLITE_UINT64_TYPE 263 typedef SQLITE_UINT64_TYPE sqlite_uint64; 264 # else 265 typedef unsigned SQLITE_INT64_TYPE sqlite_uint64; 266 # endif 267 #elif defined(_MSC_VER) || defined(__BORLANDC__) 268 typedef __int64 sqlite_int64; 269 typedef unsigned __int64 sqlite_uint64; 270 #else 271 typedef long long int sqlite_int64; 272 typedef unsigned long long int sqlite_uint64; 273 #endif 274 typedef sqlite_int64 sqlite3_int64; 275 typedef sqlite_uint64 sqlite3_uint64; 276 277 /* 278 ** If compiling for a processor that lacks floating point support, 279 ** substitute integer for floating-point. 280 */ 281 #ifdef SQLITE_OMIT_FLOATING_POINT 282 # define double sqlite3_int64 283 #endif 284 285 /* 286 ** CAPI3REF: Closing A Database Connection 287 ** DESTRUCTOR: sqlite3 288 ** 289 ** ^The sqlite3_close() and sqlite3_close_v2() routines are destructors 290 ** for the [sqlite3] object. 291 ** ^Calls to sqlite3_close() and sqlite3_close_v2() return [SQLITE_OK] if 292 ** the [sqlite3] object is successfully destroyed and all associated 293 ** resources are deallocated. 294 ** 295 ** ^If the database connection is associated with unfinalized prepared 296 ** statements or unfinished sqlite3_backup objects then sqlite3_close() 297 ** will leave the database connection open and return [SQLITE_BUSY]. 298 ** ^If sqlite3_close_v2() is called with unfinalized prepared statements 299 ** and/or unfinished sqlite3_backups, then the database connection becomes 300 ** an unusable "zombie" which will automatically be deallocated when the 301 ** last prepared statement is finalized or the last sqlite3_backup is 302 ** finished. The sqlite3_close_v2() interface is intended for use with 303 ** host languages that are garbage collected, and where the order in which 304 ** destructors are called is arbitrary. 305 ** 306 ** Applications should [sqlite3_finalize | finalize] all [prepared statements], 307 ** [sqlite3_blob_close | close] all [BLOB handles], and 308 ** [sqlite3_backup_finish | finish] all [sqlite3_backup] objects associated 309 ** with the [sqlite3] object prior to attempting to close the object. ^If 310 ** sqlite3_close_v2() is called on a [database connection] that still has 311 ** outstanding [prepared statements], [BLOB handles], and/or 312 ** [sqlite3_backup] objects then it returns [SQLITE_OK] and the deallocation 313 ** of resources is deferred until all [prepared statements], [BLOB handles], 314 ** and [sqlite3_backup] objects are also destroyed. 315 ** 316 ** ^If an [sqlite3] object is destroyed while a transaction is open, 317 ** the transaction is automatically rolled back. 318 ** 319 ** The C parameter to [sqlite3_close(C)] and [sqlite3_close_v2(C)] 320 ** must be either a NULL 321 ** pointer or an [sqlite3] object pointer obtained 322 ** from [sqlite3_open()], [sqlite3_open16()], or 323 ** [sqlite3_open_v2()], and not previously closed. 324 ** ^Calling sqlite3_close() or sqlite3_close_v2() with a NULL pointer 325 ** argument is a harmless no-op. 326 */ 327 SQLITE_API int sqlite3_close(sqlite3*); 328 SQLITE_API int sqlite3_close_v2(sqlite3*); 329 330 /* 331 ** The type for a callback function. 332 ** This is legacy and deprecated. It is included for historical 333 ** compatibility and is not documented. 334 */ 335 typedef int (*sqlite3_callback)(void*,int,char**, char**); 336 337 /* 338 ** CAPI3REF: One-Step Query Execution Interface 339 ** METHOD: sqlite3 340 ** 341 ** The sqlite3_exec() interface is a convenience wrapper around 342 ** [sqlite3_prepare_v2()], [sqlite3_step()], and [sqlite3_finalize()], 343 ** that allows an application to run multiple statements of SQL 344 ** without having to use a lot of C code. 345 ** 346 ** ^The sqlite3_exec() interface runs zero or more UTF-8 encoded, 347 ** semicolon-separate SQL statements passed into its 2nd argument, 348 ** in the context of the [database connection] passed in as its 1st 349 ** argument. ^If the callback function of the 3rd argument to 350 ** sqlite3_exec() is not NULL, then it is invoked for each result row 351 ** coming out of the evaluated SQL statements. ^The 4th argument to 352 ** sqlite3_exec() is relayed through to the 1st argument of each 353 ** callback invocation. ^If the callback pointer to sqlite3_exec() 354 ** is NULL, then no callback is ever invoked and result rows are 355 ** ignored. 356 ** 357 ** ^If an error occurs while evaluating the SQL statements passed into 358 ** sqlite3_exec(), then execution of the current statement stops and 359 ** subsequent statements are skipped. ^If the 5th parameter to sqlite3_exec() 360 ** is not NULL then any error message is written into memory obtained 361 ** from [sqlite3_malloc()] and passed back through the 5th parameter. 362 ** To avoid memory leaks, the application should invoke [sqlite3_free()] 363 ** on error message strings returned through the 5th parameter of 364 ** sqlite3_exec() after the error message string is no longer needed. 365 ** ^If the 5th parameter to sqlite3_exec() is not NULL and no errors 366 ** occur, then sqlite3_exec() sets the pointer in its 5th parameter to 367 ** NULL before returning. 368 ** 369 ** ^If an sqlite3_exec() callback returns non-zero, the sqlite3_exec() 370 ** routine returns SQLITE_ABORT without invoking the callback again and 371 ** without running any subsequent SQL statements. 372 ** 373 ** ^The 2nd argument to the sqlite3_exec() callback function is the 374 ** number of columns in the result. ^The 3rd argument to the sqlite3_exec() 375 ** callback is an array of pointers to strings obtained as if from 376 ** [sqlite3_column_text()], one for each column. ^If an element of a 377 ** result row is NULL then the corresponding string pointer for the 378 ** sqlite3_exec() callback is a NULL pointer. ^The 4th argument to the 379 ** sqlite3_exec() callback is an array of pointers to strings where each 380 ** entry represents the name of corresponding result column as obtained 381 ** from [sqlite3_column_name()]. 382 ** 383 ** ^If the 2nd parameter to sqlite3_exec() is a NULL pointer, a pointer 384 ** to an empty string, or a pointer that contains only whitespace and/or 385 ** SQL comments, then no SQL statements are evaluated and the database 386 ** is not changed. 387 ** 388 ** Restrictions: 389 ** 390 ** <ul> 391 ** <li> The application must ensure that the 1st parameter to sqlite3_exec() 392 ** is a valid and open [database connection]. 393 ** <li> The application must not close the [database connection] specified by 394 ** the 1st parameter to sqlite3_exec() while sqlite3_exec() is running. 395 ** <li> The application must not modify the SQL statement text passed into 396 ** the 2nd parameter of sqlite3_exec() while sqlite3_exec() is running. 397 ** </ul> 398 */ 399 SQLITE_API int sqlite3_exec( 400 sqlite3*, /* An open database */ 401 const char *sql, /* SQL to be evaluated */ 402 int (*callback)(void*,int,char**,char**), /* Callback function */ 403 void *, /* 1st argument to callback */ 404 char **errmsg /* Error msg written here */ 405 ); 406 407 /* 408 ** CAPI3REF: Result Codes 409 ** KEYWORDS: {result code definitions} 410 ** 411 ** Many SQLite functions return an integer result code from the set shown 412 ** here in order to indicate success or failure. 413 ** 414 ** New error codes may be added in future versions of SQLite. 415 ** 416 ** See also: [extended result code definitions] 417 */ 418 #define SQLITE_OK 0 /* Successful result */ 419 /* beginning-of-error-codes */ 420 #define SQLITE_ERROR 1 /* SQL error or missing database */ 421 #define SQLITE_INTERNAL 2 /* Internal logic error in SQLite */ 422 #define SQLITE_PERM 3 /* Access permission denied */ 423 #define SQLITE_ABORT 4 /* Callback routine requested an abort */ 424 #define SQLITE_BUSY 5 /* The database file is locked */ 425 #define SQLITE_LOCKED 6 /* A table in the database is locked */ 426 #define SQLITE_NOMEM 7 /* A malloc() failed */ 427 #define SQLITE_READONLY 8 /* Attempt to write a readonly database */ 428 #define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/ 429 #define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */ 430 #define SQLITE_CORRUPT 11 /* The database disk image is malformed */ 431 #define SQLITE_NOTFOUND 12 /* Unknown opcode in sqlite3_file_control() */ 432 #define SQLITE_FULL 13 /* Insertion failed because database is full */ 433 #define SQLITE_CANTOPEN 14 /* Unable to open the database file */ 434 #define SQLITE_PROTOCOL 15 /* Database lock protocol error */ 435 #define SQLITE_EMPTY 16 /* Database is empty */ 436 #define SQLITE_SCHEMA 17 /* The database schema changed */ 437 #define SQLITE_TOOBIG 18 /* String or BLOB exceeds size limit */ 438 #define SQLITE_CONSTRAINT 19 /* Abort due to constraint violation */ 439 #define SQLITE_MISMATCH 20 /* Data type mismatch */ 440 #define SQLITE_MISUSE 21 /* Library used incorrectly */ 441 #define SQLITE_NOLFS 22 /* Uses OS features not supported on host */ 442 #define SQLITE_AUTH 23 /* Authorization denied */ 443 #define SQLITE_FORMAT 24 /* Auxiliary database format error */ 444 #define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */ 445 #define SQLITE_NOTADB 26 /* File opened that is not a database file */ 446 #define SQLITE_NOTICE 27 /* Notifications from sqlite3_log() */ 447 #define SQLITE_WARNING 28 /* Warnings from sqlite3_log() */ 448 #define SQLITE_ROW 100 /* sqlite3_step() has another row ready */ 449 #define SQLITE_DONE 101 /* sqlite3_step() has finished executing */ 450 /* end-of-error-codes */ 451 452 /* 453 ** CAPI3REF: Extended Result Codes 454 ** KEYWORDS: {extended result code definitions} 455 ** 456 ** In its default configuration, SQLite API routines return one of 30 integer 457 ** [result codes]. However, experience has shown that many of 458 ** these result codes are too coarse-grained. They do not provide as 459 ** much information about problems as programmers might like. In an effort to 460 ** address this, newer versions of SQLite (version 3.3.8 [dateof:3.3.8] 461 ** and later) include 462 ** support for additional result codes that provide more detailed information 463 ** about errors. These [extended result codes] are enabled or disabled 464 ** on a per database connection basis using the 465 ** [sqlite3_extended_result_codes()] API. Or, the extended code for 466 ** the most recent error can be obtained using 467 ** [sqlite3_extended_errcode()]. 468 */ 469 #define SQLITE_IOERR_READ (SQLITE_IOERR | (1<<8)) 470 #define SQLITE_IOERR_SHORT_READ (SQLITE_IOERR | (2<<8)) 471 #define SQLITE_IOERR_WRITE (SQLITE_IOERR | (3<<8)) 472 #define SQLITE_IOERR_FSYNC (SQLITE_IOERR | (4<<8)) 473 #define SQLITE_IOERR_DIR_FSYNC (SQLITE_IOERR | (5<<8)) 474 #define SQLITE_IOERR_TRUNCATE (SQLITE_IOERR | (6<<8)) 475 #define SQLITE_IOERR_FSTAT (SQLITE_IOERR | (7<<8)) 476 #define SQLITE_IOERR_UNLOCK (SQLITE_IOERR | (8<<8)) 477 #define SQLITE_IOERR_RDLOCK (SQLITE_IOERR | (9<<8)) 478 #define SQLITE_IOERR_DELETE (SQLITE_IOERR | (10<<8)) 479 #define SQLITE_IOERR_BLOCKED (SQLITE_IOERR | (11<<8)) 480 #define SQLITE_IOERR_NOMEM (SQLITE_IOERR | (12<<8)) 481 #define SQLITE_IOERR_ACCESS (SQLITE_IOERR | (13<<8)) 482 #define SQLITE_IOERR_CHECKRESERVEDLOCK (SQLITE_IOERR | (14<<8)) 483 #define SQLITE_IOERR_LOCK (SQLITE_IOERR | (15<<8)) 484 #define SQLITE_IOERR_CLOSE (SQLITE_IOERR | (16<<8)) 485 #define SQLITE_IOERR_DIR_CLOSE (SQLITE_IOERR | (17<<8)) 486 #define SQLITE_IOERR_SHMOPEN (SQLITE_IOERR | (18<<8)) 487 #define SQLITE_IOERR_SHMSIZE (SQLITE_IOERR | (19<<8)) 488 #define SQLITE_IOERR_SHMLOCK (SQLITE_IOERR | (20<<8)) 489 #define SQLITE_IOERR_SHMMAP (SQLITE_IOERR | (21<<8)) 490 #define SQLITE_IOERR_SEEK (SQLITE_IOERR | (22<<8)) 491 #define SQLITE_IOERR_DELETE_NOENT (SQLITE_IOERR | (23<<8)) 492 #define SQLITE_IOERR_MMAP (SQLITE_IOERR | (24<<8)) 493 #define SQLITE_IOERR_GETTEMPPATH (SQLITE_IOERR | (25<<8)) 494 #define SQLITE_IOERR_CONVPATH (SQLITE_IOERR | (26<<8)) 495 #define SQLITE_IOERR_VNODE (SQLITE_IOERR | (27<<8)) 496 #define SQLITE_IOERR_AUTH (SQLITE_IOERR | (28<<8)) 497 #define SQLITE_LOCKED_SHAREDCACHE (SQLITE_LOCKED | (1<<8)) 498 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8)) 499 #define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY | (2<<8)) 500 #define SQLITE_CANTOPEN_NOTEMPDIR (SQLITE_CANTOPEN | (1<<8)) 501 #define SQLITE_CANTOPEN_ISDIR (SQLITE_CANTOPEN | (2<<8)) 502 #define SQLITE_CANTOPEN_FULLPATH (SQLITE_CANTOPEN | (3<<8)) 503 #define SQLITE_CANTOPEN_CONVPATH (SQLITE_CANTOPEN | (4<<8)) 504 #define SQLITE_CORRUPT_VTAB (SQLITE_CORRUPT | (1<<8)) 505 #define SQLITE_READONLY_RECOVERY (SQLITE_READONLY | (1<<8)) 506 #define SQLITE_READONLY_CANTLOCK (SQLITE_READONLY | (2<<8)) 507 #define SQLITE_READONLY_ROLLBACK (SQLITE_READONLY | (3<<8)) 508 #define SQLITE_READONLY_DBMOVED (SQLITE_READONLY | (4<<8)) 509 #define SQLITE_ABORT_ROLLBACK (SQLITE_ABORT | (2<<8)) 510 #define SQLITE_CONSTRAINT_CHECK (SQLITE_CONSTRAINT | (1<<8)) 511 #define SQLITE_CONSTRAINT_COMMITHOOK (SQLITE_CONSTRAINT | (2<<8)) 512 #define SQLITE_CONSTRAINT_FOREIGNKEY (SQLITE_CONSTRAINT | (3<<8)) 513 #define SQLITE_CONSTRAINT_FUNCTION (SQLITE_CONSTRAINT | (4<<8)) 514 #define SQLITE_CONSTRAINT_NOTNULL (SQLITE_CONSTRAINT | (5<<8)) 515 #define SQLITE_CONSTRAINT_PRIMARYKEY (SQLITE_CONSTRAINT | (6<<8)) 516 #define SQLITE_CONSTRAINT_TRIGGER (SQLITE_CONSTRAINT | (7<<8)) 517 #define SQLITE_CONSTRAINT_UNIQUE (SQLITE_CONSTRAINT | (8<<8)) 518 #define SQLITE_CONSTRAINT_VTAB (SQLITE_CONSTRAINT | (9<<8)) 519 #define SQLITE_CONSTRAINT_ROWID (SQLITE_CONSTRAINT |(10<<8)) 520 #define SQLITE_NOTICE_RECOVER_WAL (SQLITE_NOTICE | (1<<8)) 521 #define SQLITE_NOTICE_RECOVER_ROLLBACK (SQLITE_NOTICE | (2<<8)) 522 #define SQLITE_WARNING_AUTOINDEX (SQLITE_WARNING | (1<<8)) 523 #define SQLITE_AUTH_USER (SQLITE_AUTH | (1<<8)) 524 #define SQLITE_OK_LOAD_PERMANENTLY (SQLITE_OK | (1<<8)) 525 526 /* 527 ** CAPI3REF: Flags For File Open Operations 528 ** 529 ** These bit values are intended for use in the 530 ** 3rd parameter to the [sqlite3_open_v2()] interface and 531 ** in the 4th parameter to the [sqlite3_vfs.xOpen] method. 532 */ 533 #define SQLITE_OPEN_READONLY 0x00000001 /* Ok for sqlite3_open_v2() */ 534 #define SQLITE_OPEN_READWRITE 0x00000002 /* Ok for sqlite3_open_v2() */ 535 #define SQLITE_OPEN_CREATE 0x00000004 /* Ok for sqlite3_open_v2() */ 536 #define SQLITE_OPEN_DELETEONCLOSE 0x00000008 /* VFS only */ 537 #define SQLITE_OPEN_EXCLUSIVE 0x00000010 /* VFS only */ 538 #define SQLITE_OPEN_AUTOPROXY 0x00000020 /* VFS only */ 539 #define SQLITE_OPEN_URI 0x00000040 /* Ok for sqlite3_open_v2() */ 540 #define SQLITE_OPEN_MEMORY 0x00000080 /* Ok for sqlite3_open_v2() */ 541 #define SQLITE_OPEN_MAIN_DB 0x00000100 /* VFS only */ 542 #define SQLITE_OPEN_TEMP_DB 0x00000200 /* VFS only */ 543 #define SQLITE_OPEN_TRANSIENT_DB 0x00000400 /* VFS only */ 544 #define SQLITE_OPEN_MAIN_JOURNAL 0x00000800 /* VFS only */ 545 #define SQLITE_OPEN_TEMP_JOURNAL 0x00001000 /* VFS only */ 546 #define SQLITE_OPEN_SUBJOURNAL 0x00002000 /* VFS only */ 547 #define SQLITE_OPEN_MASTER_JOURNAL 0x00004000 /* VFS only */ 548 #define SQLITE_OPEN_NOMUTEX 0x00008000 /* Ok for sqlite3_open_v2() */ 549 #define SQLITE_OPEN_FULLMUTEX 0x00010000 /* Ok for sqlite3_open_v2() */ 550 #define SQLITE_OPEN_SHAREDCACHE 0x00020000 /* Ok for sqlite3_open_v2() */ 551 #define SQLITE_OPEN_PRIVATECACHE 0x00040000 /* Ok for sqlite3_open_v2() */ 552 #define SQLITE_OPEN_WAL 0x00080000 /* VFS only */ 553 554 /* Reserved: 0x00F00000 */ 555 556 /* 557 ** CAPI3REF: Device Characteristics 558 ** 559 ** The xDeviceCharacteristics method of the [sqlite3_io_methods] 560 ** object returns an integer which is a vector of these 561 ** bit values expressing I/O characteristics of the mass storage 562 ** device that holds the file that the [sqlite3_io_methods] 563 ** refers to. 564 ** 565 ** The SQLITE_IOCAP_ATOMIC property means that all writes of 566 ** any size are atomic. The SQLITE_IOCAP_ATOMICnnn values 567 ** mean that writes of blocks that are nnn bytes in size and 568 ** are aligned to an address which is an integer multiple of 569 ** nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means 570 ** that when data is appended to a file, the data is appended 571 ** first then the size of the file is extended, never the other 572 ** way around. The SQLITE_IOCAP_SEQUENTIAL property means that 573 ** information is written to disk in the same order as calls 574 ** to xWrite(). The SQLITE_IOCAP_POWERSAFE_OVERWRITE property means that 575 ** after reboot following a crash or power loss, the only bytes in a 576 ** file that were written at the application level might have changed 577 ** and that adjacent bytes, even bytes within the same sector are 578 ** guaranteed to be unchanged. The SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN 579 ** flag indicates that a file cannot be deleted when open. The 580 ** SQLITE_IOCAP_IMMUTABLE flag indicates that the file is on 581 ** read-only media and cannot be changed even by processes with 582 ** elevated privileges. 583 */ 584 #define SQLITE_IOCAP_ATOMIC 0x00000001 585 #define SQLITE_IOCAP_ATOMIC512 0x00000002 586 #define SQLITE_IOCAP_ATOMIC1K 0x00000004 587 #define SQLITE_IOCAP_ATOMIC2K 0x00000008 588 #define SQLITE_IOCAP_ATOMIC4K 0x00000010 589 #define SQLITE_IOCAP_ATOMIC8K 0x00000020 590 #define SQLITE_IOCAP_ATOMIC16K 0x00000040 591 #define SQLITE_IOCAP_ATOMIC32K 0x00000080 592 #define SQLITE_IOCAP_ATOMIC64K 0x00000100 593 #define SQLITE_IOCAP_SAFE_APPEND 0x00000200 594 #define SQLITE_IOCAP_SEQUENTIAL 0x00000400 595 #define SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN 0x00000800 596 #define SQLITE_IOCAP_POWERSAFE_OVERWRITE 0x00001000 597 #define SQLITE_IOCAP_IMMUTABLE 0x00002000 598 599 /* 600 ** CAPI3REF: File Locking Levels 601 ** 602 ** SQLite uses one of these integer values as the second 603 ** argument to calls it makes to the xLock() and xUnlock() methods 604 ** of an [sqlite3_io_methods] object. 605 */ 606 #define SQLITE_LOCK_NONE 0 607 #define SQLITE_LOCK_SHARED 1 608 #define SQLITE_LOCK_RESERVED 2 609 #define SQLITE_LOCK_PENDING 3 610 #define SQLITE_LOCK_EXCLUSIVE 4 611 612 /* 613 ** CAPI3REF: Synchronization Type Flags 614 ** 615 ** When SQLite invokes the xSync() method of an 616 ** [sqlite3_io_methods] object it uses a combination of 617 ** these integer values as the second argument. 618 ** 619 ** When the SQLITE_SYNC_DATAONLY flag is used, it means that the 620 ** sync operation only needs to flush data to mass storage. Inode 621 ** information need not be flushed. If the lower four bits of the flag 622 ** equal SQLITE_SYNC_NORMAL, that means to use normal fsync() semantics. 623 ** If the lower four bits equal SQLITE_SYNC_FULL, that means 624 ** to use Mac OS X style fullsync instead of fsync(). 625 ** 626 ** Do not confuse the SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags 627 ** with the [PRAGMA synchronous]=NORMAL and [PRAGMA synchronous]=FULL 628 ** settings. The [synchronous pragma] determines when calls to the 629 ** xSync VFS method occur and applies uniformly across all platforms. 630 ** The SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags determine how 631 ** energetic or rigorous or forceful the sync operations are and 632 ** only make a difference on Mac OSX for the default SQLite code. 633 ** (Third-party VFS implementations might also make the distinction 634 ** between SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL, but among the 635 ** operating systems natively supported by SQLite, only Mac OSX 636 ** cares about the difference.) 637 */ 638 #define SQLITE_SYNC_NORMAL 0x00002 639 #define SQLITE_SYNC_FULL 0x00003 640 #define SQLITE_SYNC_DATAONLY 0x00010 641 642 /* 643 ** CAPI3REF: OS Interface Open File Handle 644 ** 645 ** An [sqlite3_file] object represents an open file in the 646 ** [sqlite3_vfs | OS interface layer]. Individual OS interface 647 ** implementations will 648 ** want to subclass this object by appending additional fields 649 ** for their own use. The pMethods entry is a pointer to an 650 ** [sqlite3_io_methods] object that defines methods for performing 651 ** I/O operations on the open file. 652 */ 653 typedef struct sqlite3_file sqlite3_file; 654 struct sqlite3_file { 655 const struct sqlite3_io_methods *pMethods; /* Methods for an open file */ 656 }; 657 658 /* 659 ** CAPI3REF: OS Interface File Virtual Methods Object 660 ** 661 ** Every file opened by the [sqlite3_vfs.xOpen] method populates an 662 ** [sqlite3_file] object (or, more commonly, a subclass of the 663 ** [sqlite3_file] object) with a pointer to an instance of this object. 664 ** This object defines the methods used to perform various operations 665 ** against the open file represented by the [sqlite3_file] object. 666 ** 667 ** If the [sqlite3_vfs.xOpen] method sets the sqlite3_file.pMethods element 668 ** to a non-NULL pointer, then the sqlite3_io_methods.xClose method 669 ** may be invoked even if the [sqlite3_vfs.xOpen] reported that it failed. The 670 ** only way to prevent a call to xClose following a failed [sqlite3_vfs.xOpen] 671 ** is for the [sqlite3_vfs.xOpen] to set the sqlite3_file.pMethods element 672 ** to NULL. 673 ** 674 ** The flags argument to xSync may be one of [SQLITE_SYNC_NORMAL] or 675 ** [SQLITE_SYNC_FULL]. The first choice is the normal fsync(). 676 ** The second choice is a Mac OS X style fullsync. The [SQLITE_SYNC_DATAONLY] 677 ** flag may be ORed in to indicate that only the data of the file 678 ** and not its inode needs to be synced. 679 ** 680 ** The integer values to xLock() and xUnlock() are one of 681 ** <ul> 682 ** <li> [SQLITE_LOCK_NONE], 683 ** <li> [SQLITE_LOCK_SHARED], 684 ** <li> [SQLITE_LOCK_RESERVED], 685 ** <li> [SQLITE_LOCK_PENDING], or 686 ** <li> [SQLITE_LOCK_EXCLUSIVE]. 687 ** </ul> 688 ** xLock() increases the lock. xUnlock() decreases the lock. 689 ** The xCheckReservedLock() method checks whether any database connection, 690 ** either in this process or in some other process, is holding a RESERVED, 691 ** PENDING, or EXCLUSIVE lock on the file. It returns true 692 ** if such a lock exists and false otherwise. 693 ** 694 ** The xFileControl() method is a generic interface that allows custom 695 ** VFS implementations to directly control an open file using the 696 ** [sqlite3_file_control()] interface. The second "op" argument is an 697 ** integer opcode. The third argument is a generic pointer intended to 698 ** point to a structure that may contain arguments or space in which to 699 ** write return values. Potential uses for xFileControl() might be 700 ** functions to enable blocking locks with timeouts, to change the 701 ** locking strategy (for example to use dot-file locks), to inquire 702 ** about the status of a lock, or to break stale locks. The SQLite 703 ** core reserves all opcodes less than 100 for its own use. 704 ** A [file control opcodes | list of opcodes] less than 100 is available. 705 ** Applications that define a custom xFileControl method should use opcodes 706 ** greater than 100 to avoid conflicts. VFS implementations should 707 ** return [SQLITE_NOTFOUND] for file control opcodes that they do not 708 ** recognize. 709 ** 710 ** The xSectorSize() method returns the sector size of the 711 ** device that underlies the file. The sector size is the 712 ** minimum write that can be performed without disturbing 713 ** other bytes in the file. The xDeviceCharacteristics() 714 ** method returns a bit vector describing behaviors of the 715 ** underlying device: 716 ** 717 ** <ul> 718 ** <li> [SQLITE_IOCAP_ATOMIC] 719 ** <li> [SQLITE_IOCAP_ATOMIC512] 720 ** <li> [SQLITE_IOCAP_ATOMIC1K] 721 ** <li> [SQLITE_IOCAP_ATOMIC2K] 722 ** <li> [SQLITE_IOCAP_ATOMIC4K] 723 ** <li> [SQLITE_IOCAP_ATOMIC8K] 724 ** <li> [SQLITE_IOCAP_ATOMIC16K] 725 ** <li> [SQLITE_IOCAP_ATOMIC32K] 726 ** <li> [SQLITE_IOCAP_ATOMIC64K] 727 ** <li> [SQLITE_IOCAP_SAFE_APPEND] 728 ** <li> [SQLITE_IOCAP_SEQUENTIAL] 729 ** <li> [SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN] 730 ** <li> [SQLITE_IOCAP_POWERSAFE_OVERWRITE] 731 ** <li> [SQLITE_IOCAP_IMMUTABLE] 732 ** </ul> 733 ** 734 ** The SQLITE_IOCAP_ATOMIC property means that all writes of 735 ** any size are atomic. The SQLITE_IOCAP_ATOMICnnn values 736 ** mean that writes of blocks that are nnn bytes in size and 737 ** are aligned to an address which is an integer multiple of 738 ** nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means 739 ** that when data is appended to a file, the data is appended 740 ** first then the size of the file is extended, never the other 741 ** way around. The SQLITE_IOCAP_SEQUENTIAL property means that 742 ** information is written to disk in the same order as calls 743 ** to xWrite(). 744 ** 745 ** If xRead() returns SQLITE_IOERR_SHORT_READ it must also fill 746 ** in the unread portions of the buffer with zeros. A VFS that 747 ** fails to zero-fill short reads might seem to work. However, 748 ** failure to zero-fill short reads will eventually lead to 749 ** database corruption. 750 */ 751 typedef struct sqlite3_io_methods sqlite3_io_methods; 752 struct sqlite3_io_methods { 753 int iVersion; 754 int (*xClose)(sqlite3_file*); 755 int (*xRead)(sqlite3_file*, void*, int iAmt, sqlite3_int64 iOfst); 756 int (*xWrite)(sqlite3_file*, const void*, int iAmt, sqlite3_int64 iOfst); 757 int (*xTruncate)(sqlite3_file*, sqlite3_int64 size); 758 int (*xSync)(sqlite3_file*, int flags); 759 int (*xFileSize)(sqlite3_file*, sqlite3_int64 *pSize); 760 int (*xLock)(sqlite3_file*, int); 761 int (*xUnlock)(sqlite3_file*, int); 762 int (*xCheckReservedLock)(sqlite3_file*, int *pResOut); 763 int (*xFileControl)(sqlite3_file*, int op, void *pArg); 764 int (*xSectorSize)(sqlite3_file*); 765 int (*xDeviceCharacteristics)(sqlite3_file*); 766 /* Methods above are valid for version 1 */ 767 int (*xShmMap)(sqlite3_file*, int iPg, int pgsz, int, void volatile**); 768 int (*xShmLock)(sqlite3_file*, int offset, int n, int flags); 769 void (*xShmBarrier)(sqlite3_file*); 770 int (*xShmUnmap)(sqlite3_file*, int deleteFlag); 771 /* Methods above are valid for version 2 */ 772 int (*xFetch)(sqlite3_file*, sqlite3_int64 iOfst, int iAmt, void **pp); 773 int (*xUnfetch)(sqlite3_file*, sqlite3_int64 iOfst, void *p); 774 /* Methods above are valid for version 3 */ 775 /* Additional methods may be added in future releases */ 776 }; 777 778 /* 779 ** CAPI3REF: Standard File Control Opcodes 780 ** KEYWORDS: {file control opcodes} {file control opcode} 781 ** 782 ** These integer constants are opcodes for the xFileControl method 783 ** of the [sqlite3_io_methods] object and for the [sqlite3_file_control()] 784 ** interface. 785 ** 786 ** <ul> 787 ** <li>[[SQLITE_FCNTL_LOCKSTATE]] 788 ** The [SQLITE_FCNTL_LOCKSTATE] opcode is used for debugging. This 789 ** opcode causes the xFileControl method to write the current state of 790 ** the lock (one of [SQLITE_LOCK_NONE], [SQLITE_LOCK_SHARED], 791 ** [SQLITE_LOCK_RESERVED], [SQLITE_LOCK_PENDING], or [SQLITE_LOCK_EXCLUSIVE]) 792 ** into an integer that the pArg argument points to. This capability 793 ** is used during testing and is only available when the SQLITE_TEST 794 ** compile-time option is used. 795 ** 796 ** <li>[[SQLITE_FCNTL_SIZE_HINT]] 797 ** The [SQLITE_FCNTL_SIZE_HINT] opcode is used by SQLite to give the VFS 798 ** layer a hint of how large the database file will grow to be during the 799 ** current transaction. This hint is not guaranteed to be accurate but it 800 ** is often close. The underlying VFS might choose to preallocate database 801 ** file space based on this hint in order to help writes to the database 802 ** file run faster. 803 ** 804 ** <li>[[SQLITE_FCNTL_CHUNK_SIZE]] 805 ** The [SQLITE_FCNTL_CHUNK_SIZE] opcode is used to request that the VFS 806 ** extends and truncates the database file in chunks of a size specified 807 ** by the user. The fourth argument to [sqlite3_file_control()] should 808 ** point to an integer (type int) containing the new chunk-size to use 809 ** for the nominated database. Allocating database file space in large 810 ** chunks (say 1MB at a time), may reduce file-system fragmentation and 811 ** improve performance on some systems. 812 ** 813 ** <li>[[SQLITE_FCNTL_FILE_POINTER]] 814 ** The [SQLITE_FCNTL_FILE_POINTER] opcode is used to obtain a pointer 815 ** to the [sqlite3_file] object associated with a particular database 816 ** connection. See also [SQLITE_FCNTL_JOURNAL_POINTER]. 817 ** 818 ** <li>[[SQLITE_FCNTL_JOURNAL_POINTER]] 819 ** The [SQLITE_FCNTL_JOURNAL_POINTER] opcode is used to obtain a pointer 820 ** to the [sqlite3_file] object associated with the journal file (either 821 ** the [rollback journal] or the [write-ahead log]) for a particular database 822 ** connection. See also [SQLITE_FCNTL_FILE_POINTER]. 823 ** 824 ** <li>[[SQLITE_FCNTL_SYNC_OMITTED]] 825 ** No longer in use. 826 ** 827 ** <li>[[SQLITE_FCNTL_SYNC]] 828 ** The [SQLITE_FCNTL_SYNC] opcode is generated internally by SQLite and 829 ** sent to the VFS immediately before the xSync method is invoked on a 830 ** database file descriptor. Or, if the xSync method is not invoked 831 ** because the user has configured SQLite with 832 ** [PRAGMA synchronous | PRAGMA synchronous=OFF] it is invoked in place 833 ** of the xSync method. In most cases, the pointer argument passed with 834 ** this file-control is NULL. However, if the database file is being synced 835 ** as part of a multi-database commit, the argument points to a nul-terminated 836 ** string containing the transactions master-journal file name. VFSes that 837 ** do not need this signal should silently ignore this opcode. Applications 838 ** should not call [sqlite3_file_control()] with this opcode as doing so may 839 ** disrupt the operation of the specialized VFSes that do require it. 840 ** 841 ** <li>[[SQLITE_FCNTL_COMMIT_PHASETWO]] 842 ** The [SQLITE_FCNTL_COMMIT_PHASETWO] opcode is generated internally by SQLite 843 ** and sent to the VFS after a transaction has been committed immediately 844 ** but before the database is unlocked. VFSes that do not need this signal 845 ** should silently ignore this opcode. Applications should not call 846 ** [sqlite3_file_control()] with this opcode as doing so may disrupt the 847 ** operation of the specialized VFSes that do require it. 848 ** 849 ** <li>[[SQLITE_FCNTL_WIN32_AV_RETRY]] 850 ** ^The [SQLITE_FCNTL_WIN32_AV_RETRY] opcode is used to configure automatic 851 ** retry counts and intervals for certain disk I/O operations for the 852 ** windows [VFS] in order to provide robustness in the presence of 853 ** anti-virus programs. By default, the windows VFS will retry file read, 854 ** file write, and file delete operations up to 10 times, with a delay 855 ** of 25 milliseconds before the first retry and with the delay increasing 856 ** by an additional 25 milliseconds with each subsequent retry. This 857 ** opcode allows these two values (10 retries and 25 milliseconds of delay) 858 ** to be adjusted. The values are changed for all database connections 859 ** within the same process. The argument is a pointer to an array of two 860 ** integers where the first integer i the new retry count and the second 861 ** integer is the delay. If either integer is negative, then the setting 862 ** is not changed but instead the prior value of that setting is written 863 ** into the array entry, allowing the current retry settings to be 864 ** interrogated. The zDbName parameter is ignored. 865 ** 866 ** <li>[[SQLITE_FCNTL_PERSIST_WAL]] 867 ** ^The [SQLITE_FCNTL_PERSIST_WAL] opcode is used to set or query the 868 ** persistent [WAL | Write Ahead Log] setting. By default, the auxiliary 869 ** write ahead log and shared memory files used for transaction control 870 ** are automatically deleted when the latest connection to the database 871 ** closes. Setting persistent WAL mode causes those files to persist after 872 ** close. Persisting the files is useful when other processes that do not 873 ** have write permission on the directory containing the database file want 874 ** to read the database file, as the WAL and shared memory files must exist 875 ** in order for the database to be readable. The fourth parameter to 876 ** [sqlite3_file_control()] for this opcode should be a pointer to an integer. 877 ** That integer is 0 to disable persistent WAL mode or 1 to enable persistent 878 ** WAL mode. If the integer is -1, then it is overwritten with the current 879 ** WAL persistence setting. 880 ** 881 ** <li>[[SQLITE_FCNTL_POWERSAFE_OVERWRITE]] 882 ** ^The [SQLITE_FCNTL_POWERSAFE_OVERWRITE] opcode is used to set or query the 883 ** persistent "powersafe-overwrite" or "PSOW" setting. The PSOW setting 884 ** determines the [SQLITE_IOCAP_POWERSAFE_OVERWRITE] bit of the 885 ** xDeviceCharacteristics methods. The fourth parameter to 886 ** [sqlite3_file_control()] for this opcode should be a pointer to an integer. 887 ** That integer is 0 to disable zero-damage mode or 1 to enable zero-damage 888 ** mode. If the integer is -1, then it is overwritten with the current 889 ** zero-damage mode setting. 890 ** 891 ** <li>[[SQLITE_FCNTL_OVERWRITE]] 892 ** ^The [SQLITE_FCNTL_OVERWRITE] opcode is invoked by SQLite after opening 893 ** a write transaction to indicate that, unless it is rolled back for some 894 ** reason, the entire database file will be overwritten by the current 895 ** transaction. This is used by VACUUM operations. 896 ** 897 ** <li>[[SQLITE_FCNTL_VFSNAME]] 898 ** ^The [SQLITE_FCNTL_VFSNAME] opcode can be used to obtain the names of 899 ** all [VFSes] in the VFS stack. The names are of all VFS shims and the 900 ** final bottom-level VFS are written into memory obtained from 901 ** [sqlite3_malloc()] and the result is stored in the char* variable 902 ** that the fourth parameter of [sqlite3_file_control()] points to. 903 ** The caller is responsible for freeing the memory when done. As with 904 ** all file-control actions, there is no guarantee that this will actually 905 ** do anything. Callers should initialize the char* variable to a NULL 906 ** pointer in case this file-control is not implemented. This file-control 907 ** is intended for diagnostic use only. 908 ** 909 ** <li>[[SQLITE_FCNTL_VFS_POINTER]] 910 ** ^The [SQLITE_FCNTL_VFS_POINTER] opcode finds a pointer to the top-level 911 ** [VFSes] currently in use. ^(The argument X in 912 ** sqlite3_file_control(db,SQLITE_FCNTL_VFS_POINTER,X) must be 913 ** of type "[sqlite3_vfs] **". This opcodes will set *X 914 ** to a pointer to the top-level VFS.)^ 915 ** ^When there are multiple VFS shims in the stack, this opcode finds the 916 ** upper-most shim only. 917 ** 918 ** <li>[[SQLITE_FCNTL_PRAGMA]] 919 ** ^Whenever a [PRAGMA] statement is parsed, an [SQLITE_FCNTL_PRAGMA] 920 ** file control is sent to the open [sqlite3_file] object corresponding 921 ** to the database file to which the pragma statement refers. ^The argument 922 ** to the [SQLITE_FCNTL_PRAGMA] file control is an array of 923 ** pointers to strings (char**) in which the second element of the array 924 ** is the name of the pragma and the third element is the argument to the 925 ** pragma or NULL if the pragma has no argument. ^The handler for an 926 ** [SQLITE_FCNTL_PRAGMA] file control can optionally make the first element 927 ** of the char** argument point to a string obtained from [sqlite3_mprintf()] 928 ** or the equivalent and that string will become the result of the pragma or 929 ** the error message if the pragma fails. ^If the 930 ** [SQLITE_FCNTL_PRAGMA] file control returns [SQLITE_NOTFOUND], then normal 931 ** [PRAGMA] processing continues. ^If the [SQLITE_FCNTL_PRAGMA] 932 ** file control returns [SQLITE_OK], then the parser assumes that the 933 ** VFS has handled the PRAGMA itself and the parser generates a no-op 934 ** prepared statement if result string is NULL, or that returns a copy 935 ** of the result string if the string is non-NULL. 936 ** ^If the [SQLITE_FCNTL_PRAGMA] file control returns 937 ** any result code other than [SQLITE_OK] or [SQLITE_NOTFOUND], that means 938 ** that the VFS encountered an error while handling the [PRAGMA] and the 939 ** compilation of the PRAGMA fails with an error. ^The [SQLITE_FCNTL_PRAGMA] 940 ** file control occurs at the beginning of pragma statement analysis and so 941 ** it is able to override built-in [PRAGMA] statements. 942 ** 943 ** <li>[[SQLITE_FCNTL_BUSYHANDLER]] 944 ** ^The [SQLITE_FCNTL_BUSYHANDLER] 945 ** file-control may be invoked by SQLite on the database file handle 946 ** shortly after it is opened in order to provide a custom VFS with access 947 ** to the connections busy-handler callback. The argument is of type (void **) 948 ** - an array of two (void *) values. The first (void *) actually points 949 ** to a function of type (int (*)(void *)). In order to invoke the connections 950 ** busy-handler, this function should be invoked with the second (void *) in 951 ** the array as the only argument. If it returns non-zero, then the operation 952 ** should be retried. If it returns zero, the custom VFS should abandon the 953 ** current operation. 954 ** 955 ** <li>[[SQLITE_FCNTL_TEMPFILENAME]] 956 ** ^Application can invoke the [SQLITE_FCNTL_TEMPFILENAME] file-control 957 ** to have SQLite generate a 958 ** temporary filename using the same algorithm that is followed to generate 959 ** temporary filenames for TEMP tables and other internal uses. The 960 ** argument should be a char** which will be filled with the filename 961 ** written into memory obtained from [sqlite3_malloc()]. The caller should 962 ** invoke [sqlite3_free()] on the result to avoid a memory leak. 963 ** 964 ** <li>[[SQLITE_FCNTL_MMAP_SIZE]] 965 ** The [SQLITE_FCNTL_MMAP_SIZE] file control is used to query or set the 966 ** maximum number of bytes that will be used for memory-mapped I/O. 967 ** The argument is a pointer to a value of type sqlite3_int64 that 968 ** is an advisory maximum number of bytes in the file to memory map. The 969 ** pointer is overwritten with the old value. The limit is not changed if 970 ** the value originally pointed to is negative, and so the current limit 971 ** can be queried by passing in a pointer to a negative number. This 972 ** file-control is used internally to implement [PRAGMA mmap_size]. 973 ** 974 ** <li>[[SQLITE_FCNTL_TRACE]] 975 ** The [SQLITE_FCNTL_TRACE] file control provides advisory information 976 ** to the VFS about what the higher layers of the SQLite stack are doing. 977 ** This file control is used by some VFS activity tracing [shims]. 978 ** The argument is a zero-terminated string. Higher layers in the 979 ** SQLite stack may generate instances of this file control if 980 ** the [SQLITE_USE_FCNTL_TRACE] compile-time option is enabled. 981 ** 982 ** <li>[[SQLITE_FCNTL_HAS_MOVED]] 983 ** The [SQLITE_FCNTL_HAS_MOVED] file control interprets its argument as a 984 ** pointer to an integer and it writes a boolean into that integer depending 985 ** on whether or not the file has been renamed, moved, or deleted since it 986 ** was first opened. 987 ** 988 ** <li>[[SQLITE_FCNTL_WIN32_GET_HANDLE]] 989 ** The [SQLITE_FCNTL_WIN32_GET_HANDLE] opcode can be used to obtain the 990 ** underlying native file handle associated with a file handle. This file 991 ** control interprets its argument as a pointer to a native file handle and 992 ** writes the resulting value there. 993 ** 994 ** <li>[[SQLITE_FCNTL_WIN32_SET_HANDLE]] 995 ** The [SQLITE_FCNTL_WIN32_SET_HANDLE] opcode is used for debugging. This 996 ** opcode causes the xFileControl method to swap the file handle with the one 997 ** pointed to by the pArg argument. This capability is used during testing 998 ** and only needs to be supported when SQLITE_TEST is defined. 999 ** 1000 ** <li>[[SQLITE_FCNTL_WAL_BLOCK]] 1001 ** The [SQLITE_FCNTL_WAL_BLOCK] is a signal to the VFS layer that it might 1002 ** be advantageous to block on the next WAL lock if the lock is not immediately 1003 ** available. The WAL subsystem issues this signal during rare 1004 ** circumstances in order to fix a problem with priority inversion. 1005 ** Applications should <em>not</em> use this file-control. 1006 ** 1007 ** <li>[[SQLITE_FCNTL_ZIPVFS]] 1008 ** The [SQLITE_FCNTL_ZIPVFS] opcode is implemented by zipvfs only. All other 1009 ** VFS should return SQLITE_NOTFOUND for this opcode. 1010 ** 1011 ** <li>[[SQLITE_FCNTL_RBU]] 1012 ** The [SQLITE_FCNTL_RBU] opcode is implemented by the special VFS used by 1013 ** the RBU extension only. All other VFS should return SQLITE_NOTFOUND for 1014 ** this opcode. 1015 ** </ul> 1016 */ 1017 #define SQLITE_FCNTL_LOCKSTATE 1 1018 #define SQLITE_FCNTL_GET_LOCKPROXYFILE 2 1019 #define SQLITE_FCNTL_SET_LOCKPROXYFILE 3 1020 #define SQLITE_FCNTL_LAST_ERRNO 4 1021 #define SQLITE_FCNTL_SIZE_HINT 5 1022 #define SQLITE_FCNTL_CHUNK_SIZE 6 1023 #define SQLITE_FCNTL_FILE_POINTER 7 1024 #define SQLITE_FCNTL_SYNC_OMITTED 8 1025 #define SQLITE_FCNTL_WIN32_AV_RETRY 9 1026 #define SQLITE_FCNTL_PERSIST_WAL 10 1027 #define SQLITE_FCNTL_OVERWRITE 11 1028 #define SQLITE_FCNTL_VFSNAME 12 1029 #define SQLITE_FCNTL_POWERSAFE_OVERWRITE 13 1030 #define SQLITE_FCNTL_PRAGMA 14 1031 #define SQLITE_FCNTL_BUSYHANDLER 15 1032 #define SQLITE_FCNTL_TEMPFILENAME 16 1033 #define SQLITE_FCNTL_MMAP_SIZE 18 1034 #define SQLITE_FCNTL_TRACE 19 1035 #define SQLITE_FCNTL_HAS_MOVED 20 1036 #define SQLITE_FCNTL_SYNC 21 1037 #define SQLITE_FCNTL_COMMIT_PHASETWO 22 1038 #define SQLITE_FCNTL_WIN32_SET_HANDLE 23 1039 #define SQLITE_FCNTL_WAL_BLOCK 24 1040 #define SQLITE_FCNTL_ZIPVFS 25 1041 #define SQLITE_FCNTL_RBU 26 1042 #define SQLITE_FCNTL_VFS_POINTER 27 1043 #define SQLITE_FCNTL_JOURNAL_POINTER 28 1044 #define SQLITE_FCNTL_WIN32_GET_HANDLE 29 1045 #define SQLITE_FCNTL_PDB 30 1046 1047 /* deprecated names */ 1048 #define SQLITE_GET_LOCKPROXYFILE SQLITE_FCNTL_GET_LOCKPROXYFILE 1049 #define SQLITE_SET_LOCKPROXYFILE SQLITE_FCNTL_SET_LOCKPROXYFILE 1050 #define SQLITE_LAST_ERRNO SQLITE_FCNTL_LAST_ERRNO 1051 1052 1053 /* 1054 ** CAPI3REF: Mutex Handle 1055 ** 1056 ** The mutex module within SQLite defines [sqlite3_mutex] to be an 1057 ** abstract type for a mutex object. The SQLite core never looks 1058 ** at the internal representation of an [sqlite3_mutex]. It only 1059 ** deals with pointers to the [sqlite3_mutex] object. 1060 ** 1061 ** Mutexes are created using [sqlite3_mutex_alloc()]. 1062 */ 1063 typedef struct sqlite3_mutex sqlite3_mutex; 1064 1065 /* 1066 ** CAPI3REF: Loadable Extension Thunk 1067 ** 1068 ** A pointer to the opaque sqlite3_api_routines structure is passed as 1069 ** the third parameter to entry points of [loadable extensions]. This 1070 ** structure must be typedefed in order to work around compiler warnings 1071 ** on some platforms. 1072 */ 1073 typedef struct sqlite3_api_routines sqlite3_api_routines; 1074 1075 /* 1076 ** CAPI3REF: OS Interface Object 1077 ** 1078 ** An instance of the sqlite3_vfs object defines the interface between 1079 ** the SQLite core and the underlying operating system. The "vfs" 1080 ** in the name of the object stands for "virtual file system". See 1081 ** the [VFS | VFS documentation] for further information. 1082 ** 1083 ** The value of the iVersion field is initially 1 but may be larger in 1084 ** future versions of SQLite. Additional fields may be appended to this 1085 ** object when the iVersion value is increased. Note that the structure 1086 ** of the sqlite3_vfs object changes in the transaction between 1087 ** SQLite version 3.5.9 and 3.6.0 and yet the iVersion field was not 1088 ** modified. 1089 ** 1090 ** The szOsFile field is the size of the subclassed [sqlite3_file] 1091 ** structure used by this VFS. mxPathname is the maximum length of 1092 ** a pathname in this VFS. 1093 ** 1094 ** Registered sqlite3_vfs objects are kept on a linked list formed by 1095 ** the pNext pointer. The [sqlite3_vfs_register()] 1096 ** and [sqlite3_vfs_unregister()] interfaces manage this list 1097 ** in a thread-safe way. The [sqlite3_vfs_find()] interface 1098 ** searches the list. Neither the application code nor the VFS 1099 ** implementation should use the pNext pointer. 1100 ** 1101 ** The pNext field is the only field in the sqlite3_vfs 1102 ** structure that SQLite will ever modify. SQLite will only access 1103 ** or modify this field while holding a particular static mutex. 1104 ** The application should never modify anything within the sqlite3_vfs 1105 ** object once the object has been registered. 1106 ** 1107 ** The zName field holds the name of the VFS module. The name must 1108 ** be unique across all VFS modules. 1109 ** 1110 ** [[sqlite3_vfs.xOpen]] 1111 ** ^SQLite guarantees that the zFilename parameter to xOpen 1112 ** is either a NULL pointer or string obtained 1113 ** from xFullPathname() with an optional suffix added. 1114 ** ^If a suffix is added to the zFilename parameter, it will 1115 ** consist of a single "-" character followed by no more than 1116 ** 11 alphanumeric and/or "-" characters. 1117 ** ^SQLite further guarantees that 1118 ** the string will be valid and unchanged until xClose() is 1119 ** called. Because of the previous sentence, 1120 ** the [sqlite3_file] can safely store a pointer to the 1121 ** filename if it needs to remember the filename for some reason. 1122 ** If the zFilename parameter to xOpen is a NULL pointer then xOpen 1123 ** must invent its own temporary name for the file. ^Whenever the 1124 ** xFilename parameter is NULL it will also be the case that the 1125 ** flags parameter will include [SQLITE_OPEN_DELETEONCLOSE]. 1126 ** 1127 ** The flags argument to xOpen() includes all bits set in 1128 ** the flags argument to [sqlite3_open_v2()]. Or if [sqlite3_open()] 1129 ** or [sqlite3_open16()] is used, then flags includes at least 1130 ** [SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE]. 1131 ** If xOpen() opens a file read-only then it sets *pOutFlags to 1132 ** include [SQLITE_OPEN_READONLY]. Other bits in *pOutFlags may be set. 1133 ** 1134 ** ^(SQLite will also add one of the following flags to the xOpen() 1135 ** call, depending on the object being opened: 1136 ** 1137 ** <ul> 1138 ** <li> [SQLITE_OPEN_MAIN_DB] 1139 ** <li> [SQLITE_OPEN_MAIN_JOURNAL] 1140 ** <li> [SQLITE_OPEN_TEMP_DB] 1141 ** <li> [SQLITE_OPEN_TEMP_JOURNAL] 1142 ** <li> [SQLITE_OPEN_TRANSIENT_DB] 1143 ** <li> [SQLITE_OPEN_SUBJOURNAL] 1144 ** <li> [SQLITE_OPEN_MASTER_JOURNAL] 1145 ** <li> [SQLITE_OPEN_WAL] 1146 ** </ul>)^ 1147 ** 1148 ** The file I/O implementation can use the object type flags to 1149 ** change the way it deals with files. For example, an application 1150 ** that does not care about crash recovery or rollback might make 1151 ** the open of a journal file a no-op. Writes to this journal would 1152 ** also be no-ops, and any attempt to read the journal would return 1153 ** SQLITE_IOERR. Or the implementation might recognize that a database 1154 ** file will be doing page-aligned sector reads and writes in a random 1155 ** order and set up its I/O subsystem accordingly. 1156 ** 1157 ** SQLite might also add one of the following flags to the xOpen method: 1158 ** 1159 ** <ul> 1160 ** <li> [SQLITE_OPEN_DELETEONCLOSE] 1161 ** <li> [SQLITE_OPEN_EXCLUSIVE] 1162 ** </ul> 1163 ** 1164 ** The [SQLITE_OPEN_DELETEONCLOSE] flag means the file should be 1165 ** deleted when it is closed. ^The [SQLITE_OPEN_DELETEONCLOSE] 1166 ** will be set for TEMP databases and their journals, transient 1167 ** databases, and subjournals. 1168 ** 1169 ** ^The [SQLITE_OPEN_EXCLUSIVE] flag is always used in conjunction 1170 ** with the [SQLITE_OPEN_CREATE] flag, which are both directly 1171 ** analogous to the O_EXCL and O_CREAT flags of the POSIX open() 1172 ** API. The SQLITE_OPEN_EXCLUSIVE flag, when paired with the 1173 ** SQLITE_OPEN_CREATE, is used to indicate that file should always 1174 ** be created, and that it is an error if it already exists. 1175 ** It is <i>not</i> used to indicate the file should be opened 1176 ** for exclusive access. 1177 ** 1178 ** ^At least szOsFile bytes of memory are allocated by SQLite 1179 ** to hold the [sqlite3_file] structure passed as the third 1180 ** argument to xOpen. The xOpen method does not have to 1181 ** allocate the structure; it should just fill it in. Note that 1182 ** the xOpen method must set the sqlite3_file.pMethods to either 1183 ** a valid [sqlite3_io_methods] object or to NULL. xOpen must do 1184 ** this even if the open fails. SQLite expects that the sqlite3_file.pMethods 1185 ** element will be valid after xOpen returns regardless of the success 1186 ** or failure of the xOpen call. 1187 ** 1188 ** [[sqlite3_vfs.xAccess]] 1189 ** ^The flags argument to xAccess() may be [SQLITE_ACCESS_EXISTS] 1190 ** to test for the existence of a file, or [SQLITE_ACCESS_READWRITE] to 1191 ** test whether a file is readable and writable, or [SQLITE_ACCESS_READ] 1192 ** to test whether a file is at least readable. The file can be a 1193 ** directory. 1194 ** 1195 ** ^SQLite will always allocate at least mxPathname+1 bytes for the 1196 ** output buffer xFullPathname. The exact size of the output buffer 1197 ** is also passed as a parameter to both methods. If the output buffer 1198 ** is not large enough, [SQLITE_CANTOPEN] should be returned. Since this is 1199 ** handled as a fatal error by SQLite, vfs implementations should endeavor 1200 ** to prevent this by setting mxPathname to a sufficiently large value. 1201 ** 1202 ** The xRandomness(), xSleep(), xCurrentTime(), and xCurrentTimeInt64() 1203 ** interfaces are not strictly a part of the filesystem, but they are 1204 ** included in the VFS structure for completeness. 1205 ** The xRandomness() function attempts to return nBytes bytes 1206 ** of good-quality randomness into zOut. The return value is 1207 ** the actual number of bytes of randomness obtained. 1208 ** The xSleep() method causes the calling thread to sleep for at 1209 ** least the number of microseconds given. ^The xCurrentTime() 1210 ** method returns a Julian Day Number for the current date and time as 1211 ** a floating point value. 1212 ** ^The xCurrentTimeInt64() method returns, as an integer, the Julian 1213 ** Day Number multiplied by 86400000 (the number of milliseconds in 1214 ** a 24-hour day). 1215 ** ^SQLite will use the xCurrentTimeInt64() method to get the current 1216 ** date and time if that method is available (if iVersion is 2 or 1217 ** greater and the function pointer is not NULL) and will fall back 1218 ** to xCurrentTime() if xCurrentTimeInt64() is unavailable. 1219 ** 1220 ** ^The xSetSystemCall(), xGetSystemCall(), and xNestSystemCall() interfaces 1221 ** are not used by the SQLite core. These optional interfaces are provided 1222 ** by some VFSes to facilitate testing of the VFS code. By overriding 1223 ** system calls with functions under its control, a test program can 1224 ** simulate faults and error conditions that would otherwise be difficult 1225 ** or impossible to induce. The set of system calls that can be overridden 1226 ** varies from one VFS to another, and from one version of the same VFS to the 1227 ** next. Applications that use these interfaces must be prepared for any 1228 ** or all of these interfaces to be NULL or for their behavior to change 1229 ** from one release to the next. Applications must not attempt to access 1230 ** any of these methods if the iVersion of the VFS is less than 3. 1231 */ 1232 typedef struct sqlite3_vfs sqlite3_vfs; 1233 typedef void (*sqlite3_syscall_ptr)(void); 1234 struct sqlite3_vfs { 1235 int iVersion; /* Structure version number (currently 3) */ 1236 int szOsFile; /* Size of subclassed sqlite3_file */ 1237 int mxPathname; /* Maximum file pathname length */ 1238 sqlite3_vfs *pNext; /* Next registered VFS */ 1239 const char *zName; /* Name of this virtual file system */ 1240 void *pAppData; /* Pointer to application-specific data */ 1241 int (*xOpen)(sqlite3_vfs*, const char *zName, sqlite3_file*, 1242 int flags, int *pOutFlags); 1243 int (*xDelete)(sqlite3_vfs*, const char *zName, int syncDir); 1244 int (*xAccess)(sqlite3_vfs*, const char *zName, int flags, int *pResOut); 1245 int (*xFullPathname)(sqlite3_vfs*, const char *zName, int nOut, char *zOut); 1246 void *(*xDlOpen)(sqlite3_vfs*, const char *zFilename); 1247 void (*xDlError)(sqlite3_vfs*, int nByte, char *zErrMsg); 1248 void (*(*xDlSym)(sqlite3_vfs*,void*, const char *zSymbol))(void); 1249 void (*xDlClose)(sqlite3_vfs*, void*); 1250 int (*xRandomness)(sqlite3_vfs*, int nByte, char *zOut); 1251 int (*xSleep)(sqlite3_vfs*, int microseconds); 1252 int (*xCurrentTime)(sqlite3_vfs*, double*); 1253 int (*xGetLastError)(sqlite3_vfs*, int, char *); 1254 /* 1255 ** The methods above are in version 1 of the sqlite_vfs object 1256 ** definition. Those that follow are added in version 2 or later 1257 */ 1258 int (*xCurrentTimeInt64)(sqlite3_vfs*, sqlite3_int64*); 1259 /* 1260 ** The methods above are in versions 1 and 2 of the sqlite_vfs object. 1261 ** Those below are for version 3 and greater. 1262 */ 1263 int (*xSetSystemCall)(sqlite3_vfs*, const char *zName, sqlite3_syscall_ptr); 1264 sqlite3_syscall_ptr (*xGetSystemCall)(sqlite3_vfs*, const char *zName); 1265 const char *(*xNextSystemCall)(sqlite3_vfs*, const char *zName); 1266 /* 1267 ** The methods above are in versions 1 through 3 of the sqlite_vfs object. 1268 ** New fields may be appended in future versions. The iVersion 1269 ** value will increment whenever this happens. 1270 */ 1271 }; 1272 1273 /* 1274 ** CAPI3REF: Flags for the xAccess VFS method 1275 ** 1276 ** These integer constants can be used as the third parameter to 1277 ** the xAccess method of an [sqlite3_vfs] object. They determine 1278 ** what kind of permissions the xAccess method is looking for. 1279 ** With SQLITE_ACCESS_EXISTS, the xAccess method 1280 ** simply checks whether the file exists. 1281 ** With SQLITE_ACCESS_READWRITE, the xAccess method 1282 ** checks whether the named directory is both readable and writable 1283 ** (in other words, if files can be added, removed, and renamed within 1284 ** the directory). 1285 ** The SQLITE_ACCESS_READWRITE constant is currently used only by the 1286 ** [temp_store_directory pragma], though this could change in a future 1287 ** release of SQLite. 1288 ** With SQLITE_ACCESS_READ, the xAccess method 1289 ** checks whether the file is readable. The SQLITE_ACCESS_READ constant is 1290 ** currently unused, though it might be used in a future release of 1291 ** SQLite. 1292 */ 1293 #define SQLITE_ACCESS_EXISTS 0 1294 #define SQLITE_ACCESS_READWRITE 1 /* Used by PRAGMA temp_store_directory */ 1295 #define SQLITE_ACCESS_READ 2 /* Unused */ 1296 1297 /* 1298 ** CAPI3REF: Flags for the xShmLock VFS method 1299 ** 1300 ** These integer constants define the various locking operations 1301 ** allowed by the xShmLock method of [sqlite3_io_methods]. The 1302 ** following are the only legal combinations of flags to the 1303 ** xShmLock method: 1304 ** 1305 ** <ul> 1306 ** <li> SQLITE_SHM_LOCK | SQLITE_SHM_SHARED 1307 ** <li> SQLITE_SHM_LOCK | SQLITE_SHM_EXCLUSIVE 1308 ** <li> SQLITE_SHM_UNLOCK | SQLITE_SHM_SHARED 1309 ** <li> SQLITE_SHM_UNLOCK | SQLITE_SHM_EXCLUSIVE 1310 ** </ul> 1311 ** 1312 ** When unlocking, the same SHARED or EXCLUSIVE flag must be supplied as 1313 ** was given on the corresponding lock. 1314 ** 1315 ** The xShmLock method can transition between unlocked and SHARED or 1316 ** between unlocked and EXCLUSIVE. It cannot transition between SHARED 1317 ** and EXCLUSIVE. 1318 */ 1319 #define SQLITE_SHM_UNLOCK 1 1320 #define SQLITE_SHM_LOCK 2 1321 #define SQLITE_SHM_SHARED 4 1322 #define SQLITE_SHM_EXCLUSIVE 8 1323 1324 /* 1325 ** CAPI3REF: Maximum xShmLock index 1326 ** 1327 ** The xShmLock method on [sqlite3_io_methods] may use values 1328 ** between 0 and this upper bound as its "offset" argument. 1329 ** The SQLite core will never attempt to acquire or release a 1330 ** lock outside of this range 1331 */ 1332 #define SQLITE_SHM_NLOCK 8 1333 1334 1335 /* 1336 ** CAPI3REF: Initialize The SQLite Library 1337 ** 1338 ** ^The sqlite3_initialize() routine initializes the 1339 ** SQLite library. ^The sqlite3_shutdown() routine 1340 ** deallocates any resources that were allocated by sqlite3_initialize(). 1341 ** These routines are designed to aid in process initialization and 1342 ** shutdown on embedded systems. Workstation applications using 1343 ** SQLite normally do not need to invoke either of these routines. 1344 ** 1345 ** A call to sqlite3_initialize() is an "effective" call if it is 1346 ** the first time sqlite3_initialize() is invoked during the lifetime of 1347 ** the process, or if it is the first time sqlite3_initialize() is invoked 1348 ** following a call to sqlite3_shutdown(). ^(Only an effective call 1349 ** of sqlite3_initialize() does any initialization. All other calls 1350 ** are harmless no-ops.)^ 1351 ** 1352 ** A call to sqlite3_shutdown() is an "effective" call if it is the first 1353 ** call to sqlite3_shutdown() since the last sqlite3_initialize(). ^(Only 1354 ** an effective call to sqlite3_shutdown() does any deinitialization. 1355 ** All other valid calls to sqlite3_shutdown() are harmless no-ops.)^ 1356 ** 1357 ** The sqlite3_initialize() interface is threadsafe, but sqlite3_shutdown() 1358 ** is not. The sqlite3_shutdown() interface must only be called from a 1359 ** single thread. All open [database connections] must be closed and all 1360 ** other SQLite resources must be deallocated prior to invoking 1361 ** sqlite3_shutdown(). 1362 ** 1363 ** Among other things, ^sqlite3_initialize() will invoke 1364 ** sqlite3_os_init(). Similarly, ^sqlite3_shutdown() 1365 ** will invoke sqlite3_os_end(). 1366 ** 1367 ** ^The sqlite3_initialize() routine returns [SQLITE_OK] on success. 1368 ** ^If for some reason, sqlite3_initialize() is unable to initialize 1369 ** the library (perhaps it is unable to allocate a needed resource such 1370 ** as a mutex) it returns an [error code] other than [SQLITE_OK]. 1371 ** 1372 ** ^The sqlite3_initialize() routine is called internally by many other 1373 ** SQLite interfaces so that an application usually does not need to 1374 ** invoke sqlite3_initialize() directly. For example, [sqlite3_open()] 1375 ** calls sqlite3_initialize() so the SQLite library will be automatically 1376 ** initialized when [sqlite3_open()] is called if it has not be initialized 1377 ** already. ^However, if SQLite is compiled with the [SQLITE_OMIT_AUTOINIT] 1378 ** compile-time option, then the automatic calls to sqlite3_initialize() 1379 ** are omitted and the application must call sqlite3_initialize() directly 1380 ** prior to using any other SQLite interface. For maximum portability, 1381 ** it is recommended that applications always invoke sqlite3_initialize() 1382 ** directly prior to using any other SQLite interface. Future releases 1383 ** of SQLite may require this. In other words, the behavior exhibited 1384 ** when SQLite is compiled with [SQLITE_OMIT_AUTOINIT] might become the 1385 ** default behavior in some future release of SQLite. 1386 ** 1387 ** The sqlite3_os_init() routine does operating-system specific 1388 ** initialization of the SQLite library. The sqlite3_os_end() 1389 ** routine undoes the effect of sqlite3_os_init(). Typical tasks 1390 ** performed by these routines include allocation or deallocation 1391 ** of static resources, initialization of global variables, 1392 ** setting up a default [sqlite3_vfs] module, or setting up 1393 ** a default configuration using [sqlite3_config()]. 1394 ** 1395 ** The application should never invoke either sqlite3_os_init() 1396 ** or sqlite3_os_end() directly. The application should only invoke 1397 ** sqlite3_initialize() and sqlite3_shutdown(). The sqlite3_os_init() 1398 ** interface is called automatically by sqlite3_initialize() and 1399 ** sqlite3_os_end() is called by sqlite3_shutdown(). Appropriate 1400 ** implementations for sqlite3_os_init() and sqlite3_os_end() 1401 ** are built into SQLite when it is compiled for Unix, Windows, or OS/2. 1402 ** When [custom builds | built for other platforms] 1403 ** (using the [SQLITE_OS_OTHER=1] compile-time 1404 ** option) the application must supply a suitable implementation for 1405 ** sqlite3_os_init() and sqlite3_os_end(). An application-supplied 1406 ** implementation of sqlite3_os_init() or sqlite3_os_end() 1407 ** must return [SQLITE_OK] on success and some other [error code] upon 1408 ** failure. 1409 */ 1410 SQLITE_API int sqlite3_initialize(void); 1411 SQLITE_API int sqlite3_shutdown(void); 1412 SQLITE_API int sqlite3_os_init(void); 1413 SQLITE_API int sqlite3_os_end(void); 1414 1415 /* 1416 ** CAPI3REF: Configuring The SQLite Library 1417 ** 1418 ** The sqlite3_config() interface is used to make global configuration 1419 ** changes to SQLite in order to tune SQLite to the specific needs of 1420 ** the application. The default configuration is recommended for most 1421 ** applications and so this routine is usually not necessary. It is 1422 ** provided to support rare applications with unusual needs. 1423 ** 1424 ** <b>The sqlite3_config() interface is not threadsafe. The application 1425 ** must ensure that no other SQLite interfaces are invoked by other 1426 ** threads while sqlite3_config() is running.</b> 1427 ** 1428 ** The sqlite3_config() interface 1429 ** may only be invoked prior to library initialization using 1430 ** [sqlite3_initialize()] or after shutdown by [sqlite3_shutdown()]. 1431 ** ^If sqlite3_config() is called after [sqlite3_initialize()] and before 1432 ** [sqlite3_shutdown()] then it will return SQLITE_MISUSE. 1433 ** Note, however, that ^sqlite3_config() can be called as part of the 1434 ** implementation of an application-defined [sqlite3_os_init()]. 1435 ** 1436 ** The first argument to sqlite3_config() is an integer 1437 ** [configuration option] that determines 1438 ** what property of SQLite is to be configured. Subsequent arguments 1439 ** vary depending on the [configuration option] 1440 ** in the first argument. 1441 ** 1442 ** ^When a configuration option is set, sqlite3_config() returns [SQLITE_OK]. 1443 ** ^If the option is unknown or SQLite is unable to set the option 1444 ** then this routine returns a non-zero [error code]. 1445 */ 1446 SQLITE_API int sqlite3_config(int, ...); 1447 1448 /* 1449 ** CAPI3REF: Configure database connections 1450 ** METHOD: sqlite3 1451 ** 1452 ** The sqlite3_db_config() interface is used to make configuration 1453 ** changes to a [database connection]. The interface is similar to 1454 ** [sqlite3_config()] except that the changes apply to a single 1455 ** [database connection] (specified in the first argument). 1456 ** 1457 ** The second argument to sqlite3_db_config(D,V,...) is the 1458 ** [SQLITE_DBCONFIG_LOOKASIDE | configuration verb] - an integer code 1459 ** that indicates what aspect of the [database connection] is being configured. 1460 ** Subsequent arguments vary depending on the configuration verb. 1461 ** 1462 ** ^Calls to sqlite3_db_config() return SQLITE_OK if and only if 1463 ** the call is considered successful. 1464 */ 1465 SQLITE_API int sqlite3_db_config(sqlite3*, int op, ...); 1466 1467 /* 1468 ** CAPI3REF: Memory Allocation Routines 1469 ** 1470 ** An instance of this object defines the interface between SQLite 1471 ** and low-level memory allocation routines. 1472 ** 1473 ** This object is used in only one place in the SQLite interface. 1474 ** A pointer to an instance of this object is the argument to 1475 ** [sqlite3_config()] when the configuration option is 1476 ** [SQLITE_CONFIG_MALLOC] or [SQLITE_CONFIG_GETMALLOC]. 1477 ** By creating an instance of this object 1478 ** and passing it to [sqlite3_config]([SQLITE_CONFIG_MALLOC]) 1479 ** during configuration, an application can specify an alternative 1480 ** memory allocation subsystem for SQLite to use for all of its 1481 ** dynamic memory needs. 1482 ** 1483 ** Note that SQLite comes with several [built-in memory allocators] 1484 ** that are perfectly adequate for the overwhelming majority of applications 1485 ** and that this object is only useful to a tiny minority of applications 1486 ** with specialized memory allocation requirements. This object is 1487 ** also used during testing of SQLite in order to specify an alternative 1488 ** memory allocator that simulates memory out-of-memory conditions in 1489 ** order to verify that SQLite recovers gracefully from such 1490 ** conditions. 1491 ** 1492 ** The xMalloc, xRealloc, and xFree methods must work like the 1493 ** malloc(), realloc() and free() functions from the standard C library. 1494 ** ^SQLite guarantees that the second argument to 1495 ** xRealloc is always a value returned by a prior call to xRoundup. 1496 ** 1497 ** xSize should return the allocated size of a memory allocation 1498 ** previously obtained from xMalloc or xRealloc. The allocated size 1499 ** is always at least as big as the requested size but may be larger. 1500 ** 1501 ** The xRoundup method returns what would be the allocated size of 1502 ** a memory allocation given a particular requested size. Most memory 1503 ** allocators round up memory allocations at least to the next multiple 1504 ** of 8. Some allocators round up to a larger multiple or to a power of 2. 1505 ** Every memory allocation request coming in through [sqlite3_malloc()] 1506 ** or [sqlite3_realloc()] first calls xRoundup. If xRoundup returns 0, 1507 ** that causes the corresponding memory allocation to fail. 1508 ** 1509 ** The xInit method initializes the memory allocator. For example, 1510 ** it might allocate any require mutexes or initialize internal data 1511 ** structures. The xShutdown method is invoked (indirectly) by 1512 ** [sqlite3_shutdown()] and should deallocate any resources acquired 1513 ** by xInit. The pAppData pointer is used as the only parameter to 1514 ** xInit and xShutdown. 1515 ** 1516 ** SQLite holds the [SQLITE_MUTEX_STATIC_MASTER] mutex when it invokes 1517 ** the xInit method, so the xInit method need not be threadsafe. The 1518 ** xShutdown method is only called from [sqlite3_shutdown()] so it does 1519 ** not need to be threadsafe either. For all other methods, SQLite 1520 ** holds the [SQLITE_MUTEX_STATIC_MEM] mutex as long as the 1521 ** [SQLITE_CONFIG_MEMSTATUS] configuration option is turned on (which 1522 ** it is by default) and so the methods are automatically serialized. 1523 ** However, if [SQLITE_CONFIG_MEMSTATUS] is disabled, then the other 1524 ** methods must be threadsafe or else make their own arrangements for 1525 ** serialization. 1526 ** 1527 ** SQLite will never invoke xInit() more than once without an intervening 1528 ** call to xShutdown(). 1529 */ 1530 typedef struct sqlite3_mem_methods sqlite3_mem_methods; 1531 struct sqlite3_mem_methods { 1532 void *(*xMalloc)(int); /* Memory allocation function */ 1533 void (*xFree)(void*); /* Free a prior allocation */ 1534 void *(*xRealloc)(void*,int); /* Resize an allocation */ 1535 int (*xSize)(void*); /* Return the size of an allocation */ 1536 int (*xRoundup)(int); /* Round up request size to allocation size */ 1537 int (*xInit)(void*); /* Initialize the memory allocator */ 1538 void (*xShutdown)(void*); /* Deinitialize the memory allocator */ 1539 void *pAppData; /* Argument to xInit() and xShutdown() */ 1540 }; 1541 1542 /* 1543 ** CAPI3REF: Configuration Options 1544 ** KEYWORDS: {configuration option} 1545 ** 1546 ** These constants are the available integer configuration options that 1547 ** can be passed as the first argument to the [sqlite3_config()] interface. 1548 ** 1549 ** New configuration options may be added in future releases of SQLite. 1550 ** Existing configuration options might be discontinued. Applications 1551 ** should check the return code from [sqlite3_config()] to make sure that 1552 ** the call worked. The [sqlite3_config()] interface will return a 1553 ** non-zero [error code] if a discontinued or unsupported configuration option 1554 ** is invoked. 1555 ** 1556 ** <dl> 1557 ** [[SQLITE_CONFIG_SINGLETHREAD]] <dt>SQLITE_CONFIG_SINGLETHREAD</dt> 1558 ** <dd>There are no arguments to this option. ^This option sets the 1559 ** [threading mode] to Single-thread. In other words, it disables 1560 ** all mutexing and puts SQLite into a mode where it can only be used 1561 ** by a single thread. ^If SQLite is compiled with 1562 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1563 ** it is not possible to change the [threading mode] from its default 1564 ** value of Single-thread and so [sqlite3_config()] will return 1565 ** [SQLITE_ERROR] if called with the SQLITE_CONFIG_SINGLETHREAD 1566 ** configuration option.</dd> 1567 ** 1568 ** [[SQLITE_CONFIG_MULTITHREAD]] <dt>SQLITE_CONFIG_MULTITHREAD</dt> 1569 ** <dd>There are no arguments to this option. ^This option sets the 1570 ** [threading mode] to Multi-thread. In other words, it disables 1571 ** mutexing on [database connection] and [prepared statement] objects. 1572 ** The application is responsible for serializing access to 1573 ** [database connections] and [prepared statements]. But other mutexes 1574 ** are enabled so that SQLite will be safe to use in a multi-threaded 1575 ** environment as long as no two threads attempt to use the same 1576 ** [database connection] at the same time. ^If SQLite is compiled with 1577 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1578 ** it is not possible to set the Multi-thread [threading mode] and 1579 ** [sqlite3_config()] will return [SQLITE_ERROR] if called with the 1580 ** SQLITE_CONFIG_MULTITHREAD configuration option.</dd> 1581 ** 1582 ** [[SQLITE_CONFIG_SERIALIZED]] <dt>SQLITE_CONFIG_SERIALIZED</dt> 1583 ** <dd>There are no arguments to this option. ^This option sets the 1584 ** [threading mode] to Serialized. In other words, this option enables 1585 ** all mutexes including the recursive 1586 ** mutexes on [database connection] and [prepared statement] objects. 1587 ** In this mode (which is the default when SQLite is compiled with 1588 ** [SQLITE_THREADSAFE=1]) the SQLite library will itself serialize access 1589 ** to [database connections] and [prepared statements] so that the 1590 ** application is free to use the same [database connection] or the 1591 ** same [prepared statement] in different threads at the same time. 1592 ** ^If SQLite is compiled with 1593 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1594 ** it is not possible to set the Serialized [threading mode] and 1595 ** [sqlite3_config()] will return [SQLITE_ERROR] if called with the 1596 ** SQLITE_CONFIG_SERIALIZED configuration option.</dd> 1597 ** 1598 ** [[SQLITE_CONFIG_MALLOC]] <dt>SQLITE_CONFIG_MALLOC</dt> 1599 ** <dd> ^(The SQLITE_CONFIG_MALLOC option takes a single argument which is 1600 ** a pointer to an instance of the [sqlite3_mem_methods] structure. 1601 ** The argument specifies 1602 ** alternative low-level memory allocation routines to be used in place of 1603 ** the memory allocation routines built into SQLite.)^ ^SQLite makes 1604 ** its own private copy of the content of the [sqlite3_mem_methods] structure 1605 ** before the [sqlite3_config()] call returns.</dd> 1606 ** 1607 ** [[SQLITE_CONFIG_GETMALLOC]] <dt>SQLITE_CONFIG_GETMALLOC</dt> 1608 ** <dd> ^(The SQLITE_CONFIG_GETMALLOC option takes a single argument which 1609 ** is a pointer to an instance of the [sqlite3_mem_methods] structure. 1610 ** The [sqlite3_mem_methods] 1611 ** structure is filled with the currently defined memory allocation routines.)^ 1612 ** This option can be used to overload the default memory allocation 1613 ** routines with a wrapper that simulations memory allocation failure or 1614 ** tracks memory usage, for example. </dd> 1615 ** 1616 ** [[SQLITE_CONFIG_MEMSTATUS]] <dt>SQLITE_CONFIG_MEMSTATUS</dt> 1617 ** <dd> ^The SQLITE_CONFIG_MEMSTATUS option takes single argument of type int, 1618 ** interpreted as a boolean, which enables or disables the collection of 1619 ** memory allocation statistics. ^(When memory allocation statistics are 1620 ** disabled, the following SQLite interfaces become non-operational: 1621 ** <ul> 1622 ** <li> [sqlite3_memory_used()] 1623 ** <li> [sqlite3_memory_highwater()] 1624 ** <li> [sqlite3_soft_heap_limit64()] 1625 ** <li> [sqlite3_status64()] 1626 ** </ul>)^ 1627 ** ^Memory allocation statistics are enabled by default unless SQLite is 1628 ** compiled with [SQLITE_DEFAULT_MEMSTATUS]=0 in which case memory 1629 ** allocation statistics are disabled by default. 1630 ** </dd> 1631 ** 1632 ** [[SQLITE_CONFIG_SCRATCH]] <dt>SQLITE_CONFIG_SCRATCH</dt> 1633 ** <dd> ^The SQLITE_CONFIG_SCRATCH option specifies a static memory buffer 1634 ** that SQLite can use for scratch memory. ^(There are three arguments 1635 ** to SQLITE_CONFIG_SCRATCH: A pointer an 8-byte 1636 ** aligned memory buffer from which the scratch allocations will be 1637 ** drawn, the size of each scratch allocation (sz), 1638 ** and the maximum number of scratch allocations (N).)^ 1639 ** The first argument must be a pointer to an 8-byte aligned buffer 1640 ** of at least sz*N bytes of memory. 1641 ** ^SQLite will not use more than one scratch buffers per thread. 1642 ** ^SQLite will never request a scratch buffer that is more than 6 1643 ** times the database page size. 1644 ** ^If SQLite needs needs additional 1645 ** scratch memory beyond what is provided by this configuration option, then 1646 ** [sqlite3_malloc()] will be used to obtain the memory needed.<p> 1647 ** ^When the application provides any amount of scratch memory using 1648 ** SQLITE_CONFIG_SCRATCH, SQLite avoids unnecessary large 1649 ** [sqlite3_malloc|heap allocations]. 1650 ** This can help [Robson proof|prevent memory allocation failures] due to heap 1651 ** fragmentation in low-memory embedded systems. 1652 ** </dd> 1653 ** 1654 ** [[SQLITE_CONFIG_PAGECACHE]] <dt>SQLITE_CONFIG_PAGECACHE</dt> 1655 ** <dd> ^The SQLITE_CONFIG_PAGECACHE option specifies a memory pool 1656 ** that SQLite can use for the database page cache with the default page 1657 ** cache implementation. 1658 ** This configuration option is a no-op if an application-define page 1659 ** cache implementation is loaded using the [SQLITE_CONFIG_PCACHE2]. 1660 ** ^There are three arguments to SQLITE_CONFIG_PAGECACHE: A pointer to 1661 ** 8-byte aligned memory (pMem), the size of each page cache line (sz), 1662 ** and the number of cache lines (N). 1663 ** The sz argument should be the size of the largest database page 1664 ** (a power of two between 512 and 65536) plus some extra bytes for each 1665 ** page header. ^The number of extra bytes needed by the page header 1666 ** can be determined using [SQLITE_CONFIG_PCACHE_HDRSZ]. 1667 ** ^It is harmless, apart from the wasted memory, 1668 ** for the sz parameter to be larger than necessary. The pMem 1669 ** argument must be either a NULL pointer or a pointer to an 8-byte 1670 ** aligned block of memory of at least sz*N bytes, otherwise 1671 ** subsequent behavior is undefined. 1672 ** ^When pMem is not NULL, SQLite will strive to use the memory provided 1673 ** to satisfy page cache needs, falling back to [sqlite3_malloc()] if 1674 ** a page cache line is larger than sz bytes or if all of the pMem buffer 1675 ** is exhausted. 1676 ** ^If pMem is NULL and N is non-zero, then each database connection 1677 ** does an initial bulk allocation for page cache memory 1678 ** from [sqlite3_malloc()] sufficient for N cache lines if N is positive or 1679 ** of -1024*N bytes if N is negative, . ^If additional 1680 ** page cache memory is needed beyond what is provided by the initial 1681 ** allocation, then SQLite goes to [sqlite3_malloc()] separately for each 1682 ** additional cache line. </dd> 1683 ** 1684 ** [[SQLITE_CONFIG_HEAP]] <dt>SQLITE_CONFIG_HEAP</dt> 1685 ** <dd> ^The SQLITE_CONFIG_HEAP option specifies a static memory buffer 1686 ** that SQLite will use for all of its dynamic memory allocation needs 1687 ** beyond those provided for by [SQLITE_CONFIG_SCRATCH] and 1688 ** [SQLITE_CONFIG_PAGECACHE]. 1689 ** ^The SQLITE_CONFIG_HEAP option is only available if SQLite is compiled 1690 ** with either [SQLITE_ENABLE_MEMSYS3] or [SQLITE_ENABLE_MEMSYS5] and returns 1691 ** [SQLITE_ERROR] if invoked otherwise. 1692 ** ^There are three arguments to SQLITE_CONFIG_HEAP: 1693 ** An 8-byte aligned pointer to the memory, 1694 ** the number of bytes in the memory buffer, and the minimum allocation size. 1695 ** ^If the first pointer (the memory pointer) is NULL, then SQLite reverts 1696 ** to using its default memory allocator (the system malloc() implementation), 1697 ** undoing any prior invocation of [SQLITE_CONFIG_MALLOC]. ^If the 1698 ** memory pointer is not NULL then the alternative memory 1699 ** allocator is engaged to handle all of SQLites memory allocation needs. 1700 ** The first pointer (the memory pointer) must be aligned to an 8-byte 1701 ** boundary or subsequent behavior of SQLite will be undefined. 1702 ** The minimum allocation size is capped at 2**12. Reasonable values 1703 ** for the minimum allocation size are 2**5 through 2**8.</dd> 1704 ** 1705 ** [[SQLITE_CONFIG_MUTEX]] <dt>SQLITE_CONFIG_MUTEX</dt> 1706 ** <dd> ^(The SQLITE_CONFIG_MUTEX option takes a single argument which is a 1707 ** pointer to an instance of the [sqlite3_mutex_methods] structure. 1708 ** The argument specifies alternative low-level mutex routines to be used 1709 ** in place the mutex routines built into SQLite.)^ ^SQLite makes a copy of 1710 ** the content of the [sqlite3_mutex_methods] structure before the call to 1711 ** [sqlite3_config()] returns. ^If SQLite is compiled with 1712 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1713 ** the entire mutexing subsystem is omitted from the build and hence calls to 1714 ** [sqlite3_config()] with the SQLITE_CONFIG_MUTEX configuration option will 1715 ** return [SQLITE_ERROR].</dd> 1716 ** 1717 ** [[SQLITE_CONFIG_GETMUTEX]] <dt>SQLITE_CONFIG_GETMUTEX</dt> 1718 ** <dd> ^(The SQLITE_CONFIG_GETMUTEX option takes a single argument which 1719 ** is a pointer to an instance of the [sqlite3_mutex_methods] structure. The 1720 ** [sqlite3_mutex_methods] 1721 ** structure is filled with the currently defined mutex routines.)^ 1722 ** This option can be used to overload the default mutex allocation 1723 ** routines with a wrapper used to track mutex usage for performance 1724 ** profiling or testing, for example. ^If SQLite is compiled with 1725 ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1726 ** the entire mutexing subsystem is omitted from the build and hence calls to 1727 ** [sqlite3_config()] with the SQLITE_CONFIG_GETMUTEX configuration option will 1728 ** return [SQLITE_ERROR].</dd> 1729 ** 1730 ** [[SQLITE_CONFIG_LOOKASIDE]] <dt>SQLITE_CONFIG_LOOKASIDE</dt> 1731 ** <dd> ^(The SQLITE_CONFIG_LOOKASIDE option takes two arguments that determine 1732 ** the default size of lookaside memory on each [database connection]. 1733 ** The first argument is the 1734 ** size of each lookaside buffer slot and the second is the number of 1735 ** slots allocated to each database connection.)^ ^(SQLITE_CONFIG_LOOKASIDE 1736 ** sets the <i>default</i> lookaside size. The [SQLITE_DBCONFIG_LOOKASIDE] 1737 ** option to [sqlite3_db_config()] can be used to change the lookaside 1738 ** configuration on individual connections.)^ </dd> 1739 ** 1740 ** [[SQLITE_CONFIG_PCACHE2]] <dt>SQLITE_CONFIG_PCACHE2</dt> 1741 ** <dd> ^(The SQLITE_CONFIG_PCACHE2 option takes a single argument which is 1742 ** a pointer to an [sqlite3_pcache_methods2] object. This object specifies 1743 ** the interface to a custom page cache implementation.)^ 1744 ** ^SQLite makes a copy of the [sqlite3_pcache_methods2] object.</dd> 1745 ** 1746 ** [[SQLITE_CONFIG_GETPCACHE2]] <dt>SQLITE_CONFIG_GETPCACHE2</dt> 1747 ** <dd> ^(The SQLITE_CONFIG_GETPCACHE2 option takes a single argument which 1748 ** is a pointer to an [sqlite3_pcache_methods2] object. SQLite copies of 1749 ** the current page cache implementation into that object.)^ </dd> 1750 ** 1751 ** [[SQLITE_CONFIG_LOG]] <dt>SQLITE_CONFIG_LOG</dt> 1752 ** <dd> The SQLITE_CONFIG_LOG option is used to configure the SQLite 1753 ** global [error log]. 1754 ** (^The SQLITE_CONFIG_LOG option takes two arguments: a pointer to a 1755 ** function with a call signature of void(*)(void*,int,const char*), 1756 ** and a pointer to void. ^If the function pointer is not NULL, it is 1757 ** invoked by [sqlite3_log()] to process each logging event. ^If the 1758 ** function pointer is NULL, the [sqlite3_log()] interface becomes a no-op. 1759 ** ^The void pointer that is the second argument to SQLITE_CONFIG_LOG is 1760 ** passed through as the first parameter to the application-defined logger 1761 ** function whenever that function is invoked. ^The second parameter to 1762 ** the logger function is a copy of the first parameter to the corresponding 1763 ** [sqlite3_log()] call and is intended to be a [result code] or an 1764 ** [extended result code]. ^The third parameter passed to the logger is 1765 ** log message after formatting via [sqlite3_snprintf()]. 1766 ** The SQLite logging interface is not reentrant; the logger function 1767 ** supplied by the application must not invoke any SQLite interface. 1768 ** In a multi-threaded application, the application-defined logger 1769 ** function must be threadsafe. </dd> 1770 ** 1771 ** [[SQLITE_CONFIG_URI]] <dt>SQLITE_CONFIG_URI 1772 ** <dd>^(The SQLITE_CONFIG_URI option takes a single argument of type int. 1773 ** If non-zero, then URI handling is globally enabled. If the parameter is zero, 1774 ** then URI handling is globally disabled.)^ ^If URI handling is globally 1775 ** enabled, all filenames passed to [sqlite3_open()], [sqlite3_open_v2()], 1776 ** [sqlite3_open16()] or 1777 ** specified as part of [ATTACH] commands are interpreted as URIs, regardless 1778 ** of whether or not the [SQLITE_OPEN_URI] flag is set when the database 1779 ** connection is opened. ^If it is globally disabled, filenames are 1780 ** only interpreted as URIs if the SQLITE_OPEN_URI flag is set when the 1781 ** database connection is opened. ^(By default, URI handling is globally 1782 ** disabled. The default value may be changed by compiling with the 1783 ** [SQLITE_USE_URI] symbol defined.)^ 1784 ** 1785 ** [[SQLITE_CONFIG_COVERING_INDEX_SCAN]] <dt>SQLITE_CONFIG_COVERING_INDEX_SCAN 1786 ** <dd>^The SQLITE_CONFIG_COVERING_INDEX_SCAN option takes a single integer 1787 ** argument which is interpreted as a boolean in order to enable or disable 1788 ** the use of covering indices for full table scans in the query optimizer. 1789 ** ^The default setting is determined 1790 ** by the [SQLITE_ALLOW_COVERING_INDEX_SCAN] compile-time option, or is "on" 1791 ** if that compile-time option is omitted. 1792 ** The ability to disable the use of covering indices for full table scans 1793 ** is because some incorrectly coded legacy applications might malfunction 1794 ** when the optimization is enabled. Providing the ability to 1795 ** disable the optimization allows the older, buggy application code to work 1796 ** without change even with newer versions of SQLite. 1797 ** 1798 ** [[SQLITE_CONFIG_PCACHE]] [[SQLITE_CONFIG_GETPCACHE]] 1799 ** <dt>SQLITE_CONFIG_PCACHE and SQLITE_CONFIG_GETPCACHE 1800 ** <dd> These options are obsolete and should not be used by new code. 1801 ** They are retained for backwards compatibility but are now no-ops. 1802 ** </dd> 1803 ** 1804 ** [[SQLITE_CONFIG_SQLLOG]] 1805 ** <dt>SQLITE_CONFIG_SQLLOG 1806 ** <dd>This option is only available if sqlite is compiled with the 1807 ** [SQLITE_ENABLE_SQLLOG] pre-processor macro defined. The first argument should 1808 ** be a pointer to a function of type void(*)(void*,sqlite3*,const char*, int). 1809 ** The second should be of type (void*). The callback is invoked by the library 1810 ** in three separate circumstances, identified by the value passed as the 1811 ** fourth parameter. If the fourth parameter is 0, then the database connection 1812 ** passed as the second argument has just been opened. The third argument 1813 ** points to a buffer containing the name of the main database file. If the 1814 ** fourth parameter is 1, then the SQL statement that the third parameter 1815 ** points to has just been executed. Or, if the fourth parameter is 2, then 1816 ** the connection being passed as the second parameter is being closed. The 1817 ** third parameter is passed NULL In this case. An example of using this 1818 ** configuration option can be seen in the "test_sqllog.c" source file in 1819 ** the canonical SQLite source tree.</dd> 1820 ** 1821 ** [[SQLITE_CONFIG_MMAP_SIZE]] 1822 ** <dt>SQLITE_CONFIG_MMAP_SIZE 1823 ** <dd>^SQLITE_CONFIG_MMAP_SIZE takes two 64-bit integer (sqlite3_int64) values 1824 ** that are the default mmap size limit (the default setting for 1825 ** [PRAGMA mmap_size]) and the maximum allowed mmap size limit. 1826 ** ^The default setting can be overridden by each database connection using 1827 ** either the [PRAGMA mmap_size] command, or by using the 1828 ** [SQLITE_FCNTL_MMAP_SIZE] file control. ^(The maximum allowed mmap size 1829 ** will be silently truncated if necessary so that it does not exceed the 1830 ** compile-time maximum mmap size set by the 1831 ** [SQLITE_MAX_MMAP_SIZE] compile-time option.)^ 1832 ** ^If either argument to this option is negative, then that argument is 1833 ** changed to its compile-time default. 1834 ** 1835 ** [[SQLITE_CONFIG_WIN32_HEAPSIZE]] 1836 ** <dt>SQLITE_CONFIG_WIN32_HEAPSIZE 1837 ** <dd>^The SQLITE_CONFIG_WIN32_HEAPSIZE option is only available if SQLite is 1838 ** compiled for Windows with the [SQLITE_WIN32_MALLOC] pre-processor macro 1839 ** defined. ^SQLITE_CONFIG_WIN32_HEAPSIZE takes a 32-bit unsigned integer value 1840 ** that specifies the maximum size of the created heap. 1841 ** 1842 ** [[SQLITE_CONFIG_PCACHE_HDRSZ]] 1843 ** <dt>SQLITE_CONFIG_PCACHE_HDRSZ 1844 ** <dd>^The SQLITE_CONFIG_PCACHE_HDRSZ option takes a single parameter which 1845 ** is a pointer to an integer and writes into that integer the number of extra 1846 ** bytes per page required for each page in [SQLITE_CONFIG_PAGECACHE]. 1847 ** The amount of extra space required can change depending on the compiler, 1848 ** target platform, and SQLite version. 1849 ** 1850 ** [[SQLITE_CONFIG_PMASZ]] 1851 ** <dt>SQLITE_CONFIG_PMASZ 1852 ** <dd>^The SQLITE_CONFIG_PMASZ option takes a single parameter which 1853 ** is an unsigned integer and sets the "Minimum PMA Size" for the multithreaded 1854 ** sorter to that integer. The default minimum PMA Size is set by the 1855 ** [SQLITE_SORTER_PMASZ] compile-time option. New threads are launched 1856 ** to help with sort operations when multithreaded sorting 1857 ** is enabled (using the [PRAGMA threads] command) and the amount of content 1858 ** to be sorted exceeds the page size times the minimum of the 1859 ** [PRAGMA cache_size] setting and this value. 1860 ** 1861 ** [[SQLITE_CONFIG_STMTJRNL_SPILL]] 1862 ** <dt>SQLITE_CONFIG_STMTJRNL_SPILL 1863 ** <dd>^The SQLITE_CONFIG_STMTJRNL_SPILL option takes a single parameter which 1864 ** becomes the [statement journal] spill-to-disk threshold. 1865 ** [Statement journals] are held in memory until their size (in bytes) 1866 ** exceeds this threshold, at which point they are written to disk. 1867 ** Or if the threshold is -1, statement journals are always held 1868 ** exclusively in memory. 1869 ** Since many statement journals never become large, setting the spill 1870 ** threshold to a value such as 64KiB can greatly reduce the amount of 1871 ** I/O required to support statement rollback. 1872 ** The default value for this setting is controlled by the 1873 ** [SQLITE_STMTJRNL_SPILL] compile-time option. 1874 ** </dl> 1875 */ 1876 #define SQLITE_CONFIG_SINGLETHREAD 1 /* nil */ 1877 #define SQLITE_CONFIG_MULTITHREAD 2 /* nil */ 1878 #define SQLITE_CONFIG_SERIALIZED 3 /* nil */ 1879 #define SQLITE_CONFIG_MALLOC 4 /* sqlite3_mem_methods* */ 1880 #define SQLITE_CONFIG_GETMALLOC 5 /* sqlite3_mem_methods* */ 1881 #define SQLITE_CONFIG_SCRATCH 6 /* void*, int sz, int N */ 1882 #define SQLITE_CONFIG_PAGECACHE 7 /* void*, int sz, int N */ 1883 #define SQLITE_CONFIG_HEAP 8 /* void*, int nByte, int min */ 1884 #define SQLITE_CONFIG_MEMSTATUS 9 /* boolean */ 1885 #define SQLITE_CONFIG_MUTEX 10 /* sqlite3_mutex_methods* */ 1886 #define SQLITE_CONFIG_GETMUTEX 11 /* sqlite3_mutex_methods* */ 1887 /* previously SQLITE_CONFIG_CHUNKALLOC 12 which is now unused. */ 1888 #define SQLITE_CONFIG_LOOKASIDE 13 /* int int */ 1889 #define SQLITE_CONFIG_PCACHE 14 /* no-op */ 1890 #define SQLITE_CONFIG_GETPCACHE 15 /* no-op */ 1891 #define SQLITE_CONFIG_LOG 16 /* xFunc, void* */ 1892 #define SQLITE_CONFIG_URI 17 /* int */ 1893 #define SQLITE_CONFIG_PCACHE2 18 /* sqlite3_pcache_methods2* */ 1894 #define SQLITE_CONFIG_GETPCACHE2 19 /* sqlite3_pcache_methods2* */ 1895 #define SQLITE_CONFIG_COVERING_INDEX_SCAN 20 /* int */ 1896 #define SQLITE_CONFIG_SQLLOG 21 /* xSqllog, void* */ 1897 #define SQLITE_CONFIG_MMAP_SIZE 22 /* sqlite3_int64, sqlite3_int64 */ 1898 #define SQLITE_CONFIG_WIN32_HEAPSIZE 23 /* int nByte */ 1899 #define SQLITE_CONFIG_PCACHE_HDRSZ 24 /* int *psz */ 1900 #define SQLITE_CONFIG_PMASZ 25 /* unsigned int szPma */ 1901 #define SQLITE_CONFIG_STMTJRNL_SPILL 26 /* int nByte */ 1902 1903 /* 1904 ** CAPI3REF: Database Connection Configuration Options 1905 ** 1906 ** These constants are the available integer configuration options that 1907 ** can be passed as the second argument to the [sqlite3_db_config()] interface. 1908 ** 1909 ** New configuration options may be added in future releases of SQLite. 1910 ** Existing configuration options might be discontinued. Applications 1911 ** should check the return code from [sqlite3_db_config()] to make sure that 1912 ** the call worked. ^The [sqlite3_db_config()] interface will return a 1913 ** non-zero [error code] if a discontinued or unsupported configuration option 1914 ** is invoked. 1915 ** 1916 ** <dl> 1917 ** <dt>SQLITE_DBCONFIG_LOOKASIDE</dt> 1918 ** <dd> ^This option takes three additional arguments that determine the 1919 ** [lookaside memory allocator] configuration for the [database connection]. 1920 ** ^The first argument (the third parameter to [sqlite3_db_config()] is a 1921 ** pointer to a memory buffer to use for lookaside memory. 1922 ** ^The first argument after the SQLITE_DBCONFIG_LOOKASIDE verb 1923 ** may be NULL in which case SQLite will allocate the 1924 ** lookaside buffer itself using [sqlite3_malloc()]. ^The second argument is the 1925 ** size of each lookaside buffer slot. ^The third argument is the number of 1926 ** slots. The size of the buffer in the first argument must be greater than 1927 ** or equal to the product of the second and third arguments. The buffer 1928 ** must be aligned to an 8-byte boundary. ^If the second argument to 1929 ** SQLITE_DBCONFIG_LOOKASIDE is not a multiple of 8, it is internally 1930 ** rounded down to the next smaller multiple of 8. ^(The lookaside memory 1931 ** configuration for a database connection can only be changed when that 1932 ** connection is not currently using lookaside memory, or in other words 1933 ** when the "current value" returned by 1934 ** [sqlite3_db_status](D,[SQLITE_CONFIG_LOOKASIDE],...) is zero. 1935 ** Any attempt to change the lookaside memory configuration when lookaside 1936 ** memory is in use leaves the configuration unchanged and returns 1937 ** [SQLITE_BUSY].)^</dd> 1938 ** 1939 ** <dt>SQLITE_DBCONFIG_ENABLE_FKEY</dt> 1940 ** <dd> ^This option is used to enable or disable the enforcement of 1941 ** [foreign key constraints]. There should be two additional arguments. 1942 ** The first argument is an integer which is 0 to disable FK enforcement, 1943 ** positive to enable FK enforcement or negative to leave FK enforcement 1944 ** unchanged. The second parameter is a pointer to an integer into which 1945 ** is written 0 or 1 to indicate whether FK enforcement is off or on 1946 ** following this call. The second parameter may be a NULL pointer, in 1947 ** which case the FK enforcement setting is not reported back. </dd> 1948 ** 1949 ** <dt>SQLITE_DBCONFIG_ENABLE_TRIGGER</dt> 1950 ** <dd> ^This option is used to enable or disable [CREATE TRIGGER | triggers]. 1951 ** There should be two additional arguments. 1952 ** The first argument is an integer which is 0 to disable triggers, 1953 ** positive to enable triggers or negative to leave the setting unchanged. 1954 ** The second parameter is a pointer to an integer into which 1955 ** is written 0 or 1 to indicate whether triggers are disabled or enabled 1956 ** following this call. The second parameter may be a NULL pointer, in 1957 ** which case the trigger setting is not reported back. </dd> 1958 ** 1959 ** <dt>SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER</dt> 1960 ** <dd> ^This option is used to enable or disable the two-argument 1961 ** version of the [fts3_tokenizer()] function which is part of the 1962 ** [FTS3] full-text search engine extension. 1963 ** There should be two additional arguments. 1964 ** The first argument is an integer which is 0 to disable fts3_tokenizer() or 1965 ** positive to enable fts3_tokenizer() or negative to leave the setting 1966 ** unchanged. 1967 ** The second parameter is a pointer to an integer into which 1968 ** is written 0 or 1 to indicate whether fts3_tokenizer is disabled or enabled 1969 ** following this call. The second parameter may be a NULL pointer, in 1970 ** which case the new setting is not reported back. </dd> 1971 ** 1972 ** <dt>SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION</dt> 1973 ** <dd> ^This option is used to enable or disable the [sqlite3_load_extension()] 1974 ** interface independently of the [load_extension()] SQL function. 1975 ** The [sqlite3_enable_load_extension()] API enables or disables both the 1976 ** C-API [sqlite3_load_extension()] and the SQL function [load_extension()]. 1977 ** There should be two additional arguments. 1978 ** When the first argument to this interface is 1, then only the C-API is 1979 ** enabled and the SQL function remains disabled. If the first argument to 1980 ** this interface is 0, then both the C-API and the SQL function are disabled. 1981 ** If the first argument is -1, then no changes are made to state of either the 1982 ** C-API or the SQL function. 1983 ** The second parameter is a pointer to an integer into which 1984 ** is written 0 or 1 to indicate whether [sqlite3_load_extension()] interface 1985 ** is disabled or enabled following this call. The second parameter may 1986 ** be a NULL pointer, in which case the new setting is not reported back. 1987 ** </dd> 1988 ** 1989 ** <dt>SQLITE_DBCONFIG_MAINDBNAME</dt> 1990 ** <dd> ^This option is used to change the name of the "main" database 1991 ** schema. ^The sole argument is a pointer to a constant UTF8 string 1992 ** which will become the new schema name in place of "main". ^SQLite 1993 ** does not make a copy of the new main schema name string, so the application 1994 ** must ensure that the argument passed into this DBCONFIG option is unchanged 1995 ** until after the database connection closes. 1996 ** </dd> 1997 ** 1998 ** <dt>SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE</dt> 1999 ** <dd> Usually, when a database in wal mode is closed or detached from a 2000 ** database handle, SQLite checks if this will mean that there are now no 2001 ** connections at all to the database. If so, it performs a checkpoint 2002 ** operation before closing the connection. This option may be used to 2003 ** override this behaviour. The first parameter passed to this operation 2004 ** is an integer - non-zero to disable checkpoints-on-close, or zero (the 2005 ** default) to enable them. The second parameter is a pointer to an integer 2006 ** into which is written 0 or 1 to indicate whether checkpoints-on-close 2007 ** have been disabled - 0 if they are not disabled, 1 if they are. 2008 ** </dd> 2009 ** 2010 ** </dl> 2011 */ 2012 #define SQLITE_DBCONFIG_MAINDBNAME 1000 /* const char* */ 2013 #define SQLITE_DBCONFIG_LOOKASIDE 1001 /* void* int int */ 2014 #define SQLITE_DBCONFIG_ENABLE_FKEY 1002 /* int int* */ 2015 #define SQLITE_DBCONFIG_ENABLE_TRIGGER 1003 /* int int* */ 2016 #define SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER 1004 /* int int* */ 2017 #define SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION 1005 /* int int* */ 2018 #define SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE 1006 /* int int* */ 2019 2020 2021 /* 2022 ** CAPI3REF: Enable Or Disable Extended Result Codes 2023 ** METHOD: sqlite3 2024 ** 2025 ** ^The sqlite3_extended_result_codes() routine enables or disables the 2026 ** [extended result codes] feature of SQLite. ^The extended result 2027 ** codes are disabled by default for historical compatibility. 2028 */ 2029 SQLITE_API int sqlite3_extended_result_codes(sqlite3*, int onoff); 2030 2031 /* 2032 ** CAPI3REF: Last Insert Rowid 2033 ** METHOD: sqlite3 2034 ** 2035 ** ^Each entry in most SQLite tables (except for [WITHOUT ROWID] tables) 2036 ** has a unique 64-bit signed 2037 ** integer key called the [ROWID | "rowid"]. ^The rowid is always available 2038 ** as an undeclared column named ROWID, OID, or _ROWID_ as long as those 2039 ** names are not also used by explicitly declared columns. ^If 2040 ** the table has a column of type [INTEGER PRIMARY KEY] then that column 2041 ** is another alias for the rowid. 2042 ** 2043 ** ^The sqlite3_last_insert_rowid(D) interface usually returns the [rowid] of 2044 ** the most recent successful [INSERT] into a rowid table or [virtual table] 2045 ** on database connection D. ^Inserts into [WITHOUT ROWID] tables are not 2046 ** recorded. ^If no successful [INSERT]s into rowid tables have ever occurred 2047 ** on the database connection D, then sqlite3_last_insert_rowid(D) returns 2048 ** zero. 2049 ** 2050 ** As well as being set automatically as rows are inserted into database 2051 ** tables, the value returned by this function may be set explicitly by 2052 ** [sqlite3_set_last_insert_rowid()] 2053 ** 2054 ** Some virtual table implementations may INSERT rows into rowid tables as 2055 ** part of committing a transaction (e.g. to flush data accumulated in memory 2056 ** to disk). In this case subsequent calls to this function return the rowid 2057 ** associated with these internal INSERT operations, which leads to 2058 ** unintuitive results. Virtual table implementations that do write to rowid 2059 ** tables in this way can avoid this problem by restoring the original 2060 ** rowid value using [sqlite3_set_last_insert_rowid()] before returning 2061 ** control to the user. 2062 ** 2063 ** ^(If an [INSERT] occurs within a trigger then this routine will 2064 ** return the [rowid] of the inserted row as long as the trigger is 2065 ** running. Once the trigger program ends, the value returned 2066 ** by this routine reverts to what it was before the trigger was fired.)^ 2067 ** 2068 ** ^An [INSERT] that fails due to a constraint violation is not a 2069 ** successful [INSERT] and does not change the value returned by this 2070 ** routine. ^Thus INSERT OR FAIL, INSERT OR IGNORE, INSERT OR ROLLBACK, 2071 ** and INSERT OR ABORT make no changes to the return value of this 2072 ** routine when their insertion fails. ^(When INSERT OR REPLACE 2073 ** encounters a constraint violation, it does not fail. The 2074 ** INSERT continues to completion after deleting rows that caused 2075 ** the constraint problem so INSERT OR REPLACE will always change 2076 ** the return value of this interface.)^ 2077 ** 2078 ** ^For the purposes of this routine, an [INSERT] is considered to 2079 ** be successful even if it is subsequently rolled back. 2080 ** 2081 ** This function is accessible to SQL statements via the 2082 ** [last_insert_rowid() SQL function]. 2083 ** 2084 ** If a separate thread performs a new [INSERT] on the same 2085 ** database connection while the [sqlite3_last_insert_rowid()] 2086 ** function is running and thus changes the last insert [rowid], 2087 ** then the value returned by [sqlite3_last_insert_rowid()] is 2088 ** unpredictable and might not equal either the old or the new 2089 ** last insert [rowid]. 2090 */ 2091 SQLITE_API sqlite3_int64 sqlite3_last_insert_rowid(sqlite3*); 2092 2093 /* 2094 ** CAPI3REF: Set the Last Insert Rowid value. 2095 ** METHOD: sqlite3 2096 ** 2097 ** The sqlite3_set_last_insert_rowid(D, R) method allows the application to 2098 ** set the value returned by calling sqlite3_last_insert_rowid(D) to R 2099 ** without inserting a row into the database. 2100 */ 2101 SQLITE_API void sqlite3_set_last_insert_rowid(sqlite3*,sqlite3_int64); 2102 2103 /* 2104 ** CAPI3REF: Count The Number Of Rows Modified 2105 ** METHOD: sqlite3 2106 ** 2107 ** ^This function returns the number of rows modified, inserted or 2108 ** deleted by the most recently completed INSERT, UPDATE or DELETE 2109 ** statement on the database connection specified by the only parameter. 2110 ** ^Executing any other type of SQL statement does not modify the value 2111 ** returned by this function. 2112 ** 2113 ** ^Only changes made directly by the INSERT, UPDATE or DELETE statement are 2114 ** considered - auxiliary changes caused by [CREATE TRIGGER | triggers], 2115 ** [foreign key actions] or [REPLACE] constraint resolution are not counted. 2116 ** 2117 ** Changes to a view that are intercepted by 2118 ** [INSTEAD OF trigger | INSTEAD OF triggers] are not counted. ^The value 2119 ** returned by sqlite3_changes() immediately after an INSERT, UPDATE or 2120 ** DELETE statement run on a view is always zero. Only changes made to real 2121 ** tables are counted. 2122 ** 2123 ** Things are more complicated if the sqlite3_changes() function is 2124 ** executed while a trigger program is running. This may happen if the 2125 ** program uses the [changes() SQL function], or if some other callback 2126 ** function invokes sqlite3_changes() directly. Essentially: 2127 ** 2128 ** <ul> 2129 ** <li> ^(Before entering a trigger program the value returned by 2130 ** sqlite3_changes() function is saved. After the trigger program 2131 ** has finished, the original value is restored.)^ 2132 ** 2133 ** <li> ^(Within a trigger program each INSERT, UPDATE and DELETE 2134 ** statement sets the value returned by sqlite3_changes() 2135 ** upon completion as normal. Of course, this value will not include 2136 ** any changes performed by sub-triggers, as the sqlite3_changes() 2137 ** value will be saved and restored after each sub-trigger has run.)^ 2138 ** </ul> 2139 ** 2140 ** ^This means that if the changes() SQL function (or similar) is used 2141 ** by the first INSERT, UPDATE or DELETE statement within a trigger, it 2142 ** returns the value as set when the calling statement began executing. 2143 ** ^If it is used by the second or subsequent such statement within a trigger 2144 ** program, the value returned reflects the number of rows modified by the 2145 ** previous INSERT, UPDATE or DELETE statement within the same trigger. 2146 ** 2147 ** See also the [sqlite3_total_changes()] interface, the 2148 ** [count_changes pragma], and the [changes() SQL function]. 2149 ** 2150 ** If a separate thread makes changes on the same database connection 2151 ** while [sqlite3_changes()] is running then the value returned 2152 ** is unpredictable and not meaningful. 2153 */ 2154 SQLITE_API int sqlite3_changes(sqlite3*); 2155 2156 /* 2157 ** CAPI3REF: Total Number Of Rows Modified 2158 ** METHOD: sqlite3 2159 ** 2160 ** ^This function returns the total number of rows inserted, modified or 2161 ** deleted by all [INSERT], [UPDATE] or [DELETE] statements completed 2162 ** since the database connection was opened, including those executed as 2163 ** part of trigger programs. ^Executing any other type of SQL statement 2164 ** does not affect the value returned by sqlite3_total_changes(). 2165 ** 2166 ** ^Changes made as part of [foreign key actions] are included in the 2167 ** count, but those made as part of REPLACE constraint resolution are 2168 ** not. ^Changes to a view that are intercepted by INSTEAD OF triggers 2169 ** are not counted. 2170 ** 2171 ** See also the [sqlite3_changes()] interface, the 2172 ** [count_changes pragma], and the [total_changes() SQL function]. 2173 ** 2174 ** If a separate thread makes changes on the same database connection 2175 ** while [sqlite3_total_changes()] is running then the value 2176 ** returned is unpredictable and not meaningful. 2177 */ 2178 SQLITE_API int sqlite3_total_changes(sqlite3*); 2179 2180 /* 2181 ** CAPI3REF: Interrupt A Long-Running Query 2182 ** METHOD: sqlite3 2183 ** 2184 ** ^This function causes any pending database operation to abort and 2185 ** return at its earliest opportunity. This routine is typically 2186 ** called in response to a user action such as pressing "Cancel" 2187 ** or Ctrl-C where the user wants a long query operation to halt 2188 ** immediately. 2189 ** 2190 ** ^It is safe to call this routine from a thread different from the 2191 ** thread that is currently running the database operation. But it 2192 ** is not safe to call this routine with a [database connection] that 2193 ** is closed or might close before sqlite3_interrupt() returns. 2194 ** 2195 ** ^If an SQL operation is very nearly finished at the time when 2196 ** sqlite3_interrupt() is called, then it might not have an opportunity 2197 ** to be interrupted and might continue to completion. 2198 ** 2199 ** ^An SQL operation that is interrupted will return [SQLITE_INTERRUPT]. 2200 ** ^If the interrupted SQL operation is an INSERT, UPDATE, or DELETE 2201 ** that is inside an explicit transaction, then the entire transaction 2202 ** will be rolled back automatically. 2203 ** 2204 ** ^The sqlite3_interrupt(D) call is in effect until all currently running 2205 ** SQL statements on [database connection] D complete. ^Any new SQL statements 2206 ** that are started after the sqlite3_interrupt() call and before the 2207 ** running statements reaches zero are interrupted as if they had been 2208 ** running prior to the sqlite3_interrupt() call. ^New SQL statements 2209 ** that are started after the running statement count reaches zero are 2210 ** not effected by the sqlite3_interrupt(). 2211 ** ^A call to sqlite3_interrupt(D) that occurs when there are no running 2212 ** SQL statements is a no-op and has no effect on SQL statements 2213 ** that are started after the sqlite3_interrupt() call returns. 2214 ** 2215 ** If the database connection closes while [sqlite3_interrupt()] 2216 ** is running then bad things will likely happen. 2217 */ 2218 SQLITE_API void sqlite3_interrupt(sqlite3*); 2219 2220 /* 2221 ** CAPI3REF: Determine If An SQL Statement Is Complete 2222 ** 2223 ** These routines are useful during command-line input to determine if the 2224 ** currently entered text seems to form a complete SQL statement or 2225 ** if additional input is needed before sending the text into 2226 ** SQLite for parsing. ^These routines return 1 if the input string 2227 ** appears to be a complete SQL statement. ^A statement is judged to be 2228 ** complete if it ends with a semicolon token and is not a prefix of a 2229 ** well-formed CREATE TRIGGER statement. ^Semicolons that are embedded within 2230 ** string literals or quoted identifier names or comments are not 2231 ** independent tokens (they are part of the token in which they are 2232 ** embedded) and thus do not count as a statement terminator. ^Whitespace 2233 ** and comments that follow the final semicolon are ignored. 2234 ** 2235 ** ^These routines return 0 if the statement is incomplete. ^If a 2236 ** memory allocation fails, then SQLITE_NOMEM is returned. 2237 ** 2238 ** ^These routines do not parse the SQL statements thus 2239 ** will not detect syntactically incorrect SQL. 2240 ** 2241 ** ^(If SQLite has not been initialized using [sqlite3_initialize()] prior 2242 ** to invoking sqlite3_complete16() then sqlite3_initialize() is invoked 2243 ** automatically by sqlite3_complete16(). If that initialization fails, 2244 ** then the return value from sqlite3_complete16() will be non-zero 2245 ** regardless of whether or not the input SQL is complete.)^ 2246 ** 2247 ** The input to [sqlite3_complete()] must be a zero-terminated 2248 ** UTF-8 string. 2249 ** 2250 ** The input to [sqlite3_complete16()] must be a zero-terminated 2251 ** UTF-16 string in native byte order. 2252 */ 2253 SQLITE_API int sqlite3_complete(const char *sql); 2254 SQLITE_API int sqlite3_complete16(const void *sql); 2255 2256 /* 2257 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors 2258 ** KEYWORDS: {busy-handler callback} {busy handler} 2259 ** METHOD: sqlite3 2260 ** 2261 ** ^The sqlite3_busy_handler(D,X,P) routine sets a callback function X 2262 ** that might be invoked with argument P whenever 2263 ** an attempt is made to access a database table associated with 2264 ** [database connection] D when another thread 2265 ** or process has the table locked. 2266 ** The sqlite3_busy_handler() interface is used to implement 2267 ** [sqlite3_busy_timeout()] and [PRAGMA busy_timeout]. 2268 ** 2269 ** ^If the busy callback is NULL, then [SQLITE_BUSY] 2270 ** is returned immediately upon encountering the lock. ^If the busy callback 2271 ** is not NULL, then the callback might be invoked with two arguments. 2272 ** 2273 ** ^The first argument to the busy handler is a copy of the void* pointer which 2274 ** is the third argument to sqlite3_busy_handler(). ^The second argument to 2275 ** the busy handler callback is the number of times that the busy handler has 2276 ** been invoked previously for the same locking event. ^If the 2277 ** busy callback returns 0, then no additional attempts are made to 2278 ** access the database and [SQLITE_BUSY] is returned 2279 ** to the application. 2280 ** ^If the callback returns non-zero, then another attempt 2281 ** is made to access the database and the cycle repeats. 2282 ** 2283 ** The presence of a busy handler does not guarantee that it will be invoked 2284 ** when there is lock contention. ^If SQLite determines that invoking the busy 2285 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY] 2286 ** to the application instead of invoking the 2287 ** busy handler. 2288 ** Consider a scenario where one process is holding a read lock that 2289 ** it is trying to promote to a reserved lock and 2290 ** a second process is holding a reserved lock that it is trying 2291 ** to promote to an exclusive lock. The first process cannot proceed 2292 ** because it is blocked by the second and the second process cannot 2293 ** proceed because it is blocked by the first. If both processes 2294 ** invoke the busy handlers, neither will make any progress. Therefore, 2295 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this 2296 ** will induce the first process to release its read lock and allow 2297 ** the second process to proceed. 2298 ** 2299 ** ^The default busy callback is NULL. 2300 ** 2301 ** ^(There can only be a single busy handler defined for each 2302 ** [database connection]. Setting a new busy handler clears any 2303 ** previously set handler.)^ ^Note that calling [sqlite3_busy_timeout()] 2304 ** or evaluating [PRAGMA busy_timeout=N] will change the 2305 ** busy handler and thus clear any previously set busy handler. 2306 ** 2307 ** The busy callback should not take any actions which modify the 2308 ** database connection that invoked the busy handler. In other words, 2309 ** the busy handler is not reentrant. Any such actions 2310 ** result in undefined behavior. 2311 ** 2312 ** A busy handler must not close the database connection 2313 ** or [prepared statement] that invoked the busy handler. 2314 */ 2315 SQLITE_API int sqlite3_busy_handler(sqlite3*,int(*)(void*,int),void*); 2316 2317 /* 2318 ** CAPI3REF: Set A Busy Timeout 2319 ** METHOD: sqlite3 2320 ** 2321 ** ^This routine sets a [sqlite3_busy_handler | busy handler] that sleeps 2322 ** for a specified amount of time when a table is locked. ^The handler 2323 ** will sleep multiple times until at least "ms" milliseconds of sleeping 2324 ** have accumulated. ^After at least "ms" milliseconds of sleeping, 2325 ** the handler returns 0 which causes [sqlite3_step()] to return 2326 ** [SQLITE_BUSY]. 2327 ** 2328 ** ^Calling this routine with an argument less than or equal to zero 2329 ** turns off all busy handlers. 2330 ** 2331 ** ^(There can only be a single busy handler for a particular 2332 ** [database connection] at any given moment. If another busy handler 2333 ** was defined (using [sqlite3_busy_handler()]) prior to calling 2334 ** this routine, that other busy handler is cleared.)^ 2335 ** 2336 ** See also: [PRAGMA busy_timeout] 2337 */ 2338 SQLITE_API int sqlite3_busy_timeout(sqlite3*, int ms); 2339 2340 /* 2341 ** CAPI3REF: Convenience Routines For Running Queries 2342 ** METHOD: sqlite3 2343 ** 2344 ** This is a legacy interface that is preserved for backwards compatibility. 2345 ** Use of this interface is not recommended. 2346 ** 2347 ** Definition: A <b>result table</b> is memory data structure created by the 2348 ** [sqlite3_get_table()] interface. A result table records the 2349 ** complete query results from one or more queries. 2350 ** 2351 ** The table conceptually has a number of rows and columns. But 2352 ** these numbers are not part of the result table itself. These 2353 ** numbers are obtained separately. Let N be the number of rows 2354 ** and M be the number of columns. 2355 ** 2356 ** A result table is an array of pointers to zero-terminated UTF-8 strings. 2357 ** There are (N+1)*M elements in the array. The first M pointers point 2358 ** to zero-terminated strings that contain the names of the columns. 2359 ** The remaining entries all point to query results. NULL values result 2360 ** in NULL pointers. All other values are in their UTF-8 zero-terminated 2361 ** string representation as returned by [sqlite3_column_text()]. 2362 ** 2363 ** A result table might consist of one or more memory allocations. 2364 ** It is not safe to pass a result table directly to [sqlite3_free()]. 2365 ** A result table should be deallocated using [sqlite3_free_table()]. 2366 ** 2367 ** ^(As an example of the result table format, suppose a query result 2368 ** is as follows: 2369 ** 2370 ** <blockquote><pre> 2371 ** Name | Age 2372 ** ----------------------- 2373 ** Alice | 43 2374 ** Bob | 28 2375 ** Cindy | 21 2376 ** </pre></blockquote> 2377 ** 2378 ** There are two column (M==2) and three rows (N==3). Thus the 2379 ** result table has 8 entries. Suppose the result table is stored 2380 ** in an array names azResult. Then azResult holds this content: 2381 ** 2382 ** <blockquote><pre> 2383 ** azResult[0] = "Name"; 2384 ** azResult[1] = "Age"; 2385 ** azResult[2] = "Alice"; 2386 ** azResult[3] = "43"; 2387 ** azResult[4] = "Bob"; 2388 ** azResult[5] = "28"; 2389 ** azResult[6] = "Cindy"; 2390 ** azResult[7] = "21"; 2391 ** </pre></blockquote>)^ 2392 ** 2393 ** ^The sqlite3_get_table() function evaluates one or more 2394 ** semicolon-separated SQL statements in the zero-terminated UTF-8 2395 ** string of its 2nd parameter and returns a result table to the 2396 ** pointer given in its 3rd parameter. 2397 ** 2398 ** After the application has finished with the result from sqlite3_get_table(), 2399 ** it must pass the result table pointer to sqlite3_free_table() in order to 2400 ** release the memory that was malloced. Because of the way the 2401 ** [sqlite3_malloc()] happens within sqlite3_get_table(), the calling 2402 ** function must not try to call [sqlite3_free()] directly. Only 2403 ** [sqlite3_free_table()] is able to release the memory properly and safely. 2404 ** 2405 ** The sqlite3_get_table() interface is implemented as a wrapper around 2406 ** [sqlite3_exec()]. The sqlite3_get_table() routine does not have access 2407 ** to any internal data structures of SQLite. It uses only the public 2408 ** interface defined here. As a consequence, errors that occur in the 2409 ** wrapper layer outside of the internal [sqlite3_exec()] call are not 2410 ** reflected in subsequent calls to [sqlite3_errcode()] or 2411 ** [sqlite3_errmsg()]. 2412 */ 2413 SQLITE_API int sqlite3_get_table( 2414 sqlite3 *db, /* An open database */ 2415 const char *zSql, /* SQL to be evaluated */ 2416 char ***pazResult, /* Results of the query */ 2417 int *pnRow, /* Number of result rows written here */ 2418 int *pnColumn, /* Number of result columns written here */ 2419 char **pzErrmsg /* Error msg written here */ 2420 ); 2421 SQLITE_API void sqlite3_free_table(char **result); 2422 2423 /* 2424 ** CAPI3REF: Formatted String Printing Functions 2425 ** 2426 ** These routines are work-alikes of the "printf()" family of functions 2427 ** from the standard C library. 2428 ** These routines understand most of the common K&R formatting options, 2429 ** plus some additional non-standard formats, detailed below. 2430 ** Note that some of the more obscure formatting options from recent 2431 ** C-library standards are omitted from this implementation. 2432 ** 2433 ** ^The sqlite3_mprintf() and sqlite3_vmprintf() routines write their 2434 ** results into memory obtained from [sqlite3_malloc()]. 2435 ** The strings returned by these two routines should be 2436 ** released by [sqlite3_free()]. ^Both routines return a 2437 ** NULL pointer if [sqlite3_malloc()] is unable to allocate enough 2438 ** memory to hold the resulting string. 2439 ** 2440 ** ^(The sqlite3_snprintf() routine is similar to "snprintf()" from 2441 ** the standard C library. The result is written into the 2442 ** buffer supplied as the second parameter whose size is given by 2443 ** the first parameter. Note that the order of the 2444 ** first two parameters is reversed from snprintf().)^ This is an 2445 ** historical accident that cannot be fixed without breaking 2446 ** backwards compatibility. ^(Note also that sqlite3_snprintf() 2447 ** returns a pointer to its buffer instead of the number of 2448 ** characters actually written into the buffer.)^ We admit that 2449 ** the number of characters written would be a more useful return 2450 ** value but we cannot change the implementation of sqlite3_snprintf() 2451 ** now without breaking compatibility. 2452 ** 2453 ** ^As long as the buffer size is greater than zero, sqlite3_snprintf() 2454 ** guarantees that the buffer is always zero-terminated. ^The first 2455 ** parameter "n" is the total size of the buffer, including space for 2456 ** the zero terminator. So the longest string that can be completely 2457 ** written will be n-1 characters. 2458 ** 2459 ** ^The sqlite3_vsnprintf() routine is a varargs version of sqlite3_snprintf(). 2460 ** 2461 ** These routines all implement some additional formatting 2462 ** options that are useful for constructing SQL statements. 2463 ** All of the usual printf() formatting options apply. In addition, there 2464 ** is are "%q", "%Q", "%w" and "%z" options. 2465 ** 2466 ** ^(The %q option works like %s in that it substitutes a nul-terminated 2467 ** string from the argument list. But %q also doubles every '\'' character. 2468 ** %q is designed for use inside a string literal.)^ By doubling each '\'' 2469 ** character it escapes that character and allows it to be inserted into 2470 ** the string. 2471 ** 2472 ** For example, assume the string variable zText contains text as follows: 2473 ** 2474 ** <blockquote><pre> 2475 ** char *zText = "It's a happy day!"; 2476 ** </pre></blockquote> 2477 ** 2478 ** One can use this text in an SQL statement as follows: 2479 ** 2480 ** <blockquote><pre> 2481 ** char *zSQL = sqlite3_mprintf("INSERT INTO table VALUES('%q')", zText); 2482 ** sqlite3_exec(db, zSQL, 0, 0, 0); 2483 ** sqlite3_free(zSQL); 2484 ** </pre></blockquote> 2485 ** 2486 ** Because the %q format string is used, the '\'' character in zText 2487 ** is escaped and the SQL generated is as follows: 2488 ** 2489 ** <blockquote><pre> 2490 ** INSERT INTO table1 VALUES('It''s a happy day!') 2491 ** </pre></blockquote> 2492 ** 2493 ** This is correct. Had we used %s instead of %q, the generated SQL 2494 ** would have looked like this: 2495 ** 2496 ** <blockquote><pre> 2497 ** INSERT INTO table1 VALUES('It's a happy day!'); 2498 ** </pre></blockquote> 2499 ** 2500 ** This second example is an SQL syntax error. As a general rule you should 2501 ** always use %q instead of %s when inserting text into a string literal. 2502 ** 2503 ** ^(The %Q option works like %q except it also adds single quotes around 2504 ** the outside of the total string. Additionally, if the parameter in the 2505 ** argument list is a NULL pointer, %Q substitutes the text "NULL" (without 2506 ** single quotes).)^ So, for example, one could say: 2507 ** 2508 ** <blockquote><pre> 2509 ** char *zSQL = sqlite3_mprintf("INSERT INTO table VALUES(%Q)", zText); 2510 ** sqlite3_exec(db, zSQL, 0, 0, 0); 2511 ** sqlite3_free(zSQL); 2512 ** </pre></blockquote> 2513 ** 2514 ** The code above will render a correct SQL statement in the zSQL 2515 ** variable even if the zText variable is a NULL pointer. 2516 ** 2517 ** ^(The "%w" formatting option is like "%q" except that it expects to 2518 ** be contained within double-quotes instead of single quotes, and it 2519 ** escapes the double-quote character instead of the single-quote 2520 ** character.)^ The "%w" formatting option is intended for safely inserting 2521 ** table and column names into a constructed SQL statement. 2522 ** 2523 ** ^(The "%z" formatting option works like "%s" but with the 2524 ** addition that after the string has been read and copied into 2525 ** the result, [sqlite3_free()] is called on the input string.)^ 2526 */ 2527 SQLITE_API char *sqlite3_mprintf(const char*,...); 2528 SQLITE_API char *sqlite3_vmprintf(const char*, va_list); 2529 SQLITE_API char *sqlite3_snprintf(int,char*,const char*, ...); 2530 SQLITE_API char *sqlite3_vsnprintf(int,char*,const char*, va_list); 2531 2532 /* 2533 ** CAPI3REF: Memory Allocation Subsystem 2534 ** 2535 ** The SQLite core uses these three routines for all of its own 2536 ** internal memory allocation needs. "Core" in the previous sentence 2537 ** does not include operating-system specific VFS implementation. The 2538 ** Windows VFS uses native malloc() and free() for some operations. 2539 ** 2540 ** ^The sqlite3_malloc() routine returns a pointer to a block 2541 ** of memory at least N bytes in length, where N is the parameter. 2542 ** ^If sqlite3_malloc() is unable to obtain sufficient free 2543 ** memory, it returns a NULL pointer. ^If the parameter N to 2544 ** sqlite3_malloc() is zero or negative then sqlite3_malloc() returns 2545 ** a NULL pointer. 2546 ** 2547 ** ^The sqlite3_malloc64(N) routine works just like 2548 ** sqlite3_malloc(N) except that N is an unsigned 64-bit integer instead 2549 ** of a signed 32-bit integer. 2550 ** 2551 ** ^Calling sqlite3_free() with a pointer previously returned 2552 ** by sqlite3_malloc() or sqlite3_realloc() releases that memory so 2553 ** that it might be reused. ^The sqlite3_free() routine is 2554 ** a no-op if is called with a NULL pointer. Passing a NULL pointer 2555 ** to sqlite3_free() is harmless. After being freed, memory 2556 ** should neither be read nor written. Even reading previously freed 2557 ** memory might result in a segmentation fault or other severe error. 2558 ** Memory corruption, a segmentation fault, or other severe error 2559 ** might result if sqlite3_free() is called with a non-NULL pointer that 2560 ** was not obtained from sqlite3_malloc() or sqlite3_realloc(). 2561 ** 2562 ** ^The sqlite3_realloc(X,N) interface attempts to resize a 2563 ** prior memory allocation X to be at least N bytes. 2564 ** ^If the X parameter to sqlite3_realloc(X,N) 2565 ** is a NULL pointer then its behavior is identical to calling 2566 ** sqlite3_malloc(N). 2567 ** ^If the N parameter to sqlite3_realloc(X,N) is zero or 2568 ** negative then the behavior is exactly the same as calling 2569 ** sqlite3_free(X). 2570 ** ^sqlite3_realloc(X,N) returns a pointer to a memory allocation 2571 ** of at least N bytes in size or NULL if insufficient memory is available. 2572 ** ^If M is the size of the prior allocation, then min(N,M) bytes 2573 ** of the prior allocation are copied into the beginning of buffer returned 2574 ** by sqlite3_realloc(X,N) and the prior allocation is freed. 2575 ** ^If sqlite3_realloc(X,N) returns NULL and N is positive, then the 2576 ** prior allocation is not freed. 2577 ** 2578 ** ^The sqlite3_realloc64(X,N) interfaces works the same as 2579 ** sqlite3_realloc(X,N) except that N is a 64-bit unsigned integer instead 2580 ** of a 32-bit signed integer. 2581 ** 2582 ** ^If X is a memory allocation previously obtained from sqlite3_malloc(), 2583 ** sqlite3_malloc64(), sqlite3_realloc(), or sqlite3_realloc64(), then 2584 ** sqlite3_msize(X) returns the size of that memory allocation in bytes. 2585 ** ^The value returned by sqlite3_msize(X) might be larger than the number 2586 ** of bytes requested when X was allocated. ^If X is a NULL pointer then 2587 ** sqlite3_msize(X) returns zero. If X points to something that is not 2588 ** the beginning of memory allocation, or if it points to a formerly 2589 ** valid memory allocation that has now been freed, then the behavior 2590 ** of sqlite3_msize(X) is undefined and possibly harmful. 2591 ** 2592 ** ^The memory returned by sqlite3_malloc(), sqlite3_realloc(), 2593 ** sqlite3_malloc64(), and sqlite3_realloc64() 2594 ** is always aligned to at least an 8 byte boundary, or to a 2595 ** 4 byte boundary if the [SQLITE_4_BYTE_ALIGNED_MALLOC] compile-time 2596 ** option is used. 2597 ** 2598 ** In SQLite version 3.5.0 and 3.5.1, it was possible to define 2599 ** the SQLITE_OMIT_MEMORY_ALLOCATION which would cause the built-in 2600 ** implementation of these routines to be omitted. That capability 2601 ** is no longer provided. Only built-in memory allocators can be used. 2602 ** 2603 ** Prior to SQLite version 3.7.10, the Windows OS interface layer called 2604 ** the system malloc() and free() directly when converting 2605 ** filenames between the UTF-8 encoding used by SQLite 2606 ** and whatever filename encoding is used by the particular Windows 2607 ** installation. Memory allocation errors were detected, but 2608 ** they were reported back as [SQLITE_CANTOPEN] or 2609 ** [SQLITE_IOERR] rather than [SQLITE_NOMEM]. 2610 ** 2611 ** The pointer arguments to [sqlite3_free()] and [sqlite3_realloc()] 2612 ** must be either NULL or else pointers obtained from a prior 2613 ** invocation of [sqlite3_malloc()] or [sqlite3_realloc()] that have 2614 ** not yet been released. 2615 ** 2616 ** The application must not read or write any part of 2617 ** a block of memory after it has been released using 2618 ** [sqlite3_free()] or [sqlite3_realloc()]. 2619 */ 2620 SQLITE_API void *sqlite3_malloc(int); 2621 SQLITE_API void *sqlite3_malloc64(sqlite3_uint64); 2622 SQLITE_API void *sqlite3_realloc(void*, int); 2623 SQLITE_API void *sqlite3_realloc64(void*, sqlite3_uint64); 2624 SQLITE_API void sqlite3_free(void*); 2625 SQLITE_API sqlite3_uint64 sqlite3_msize(void*); 2626 2627 /* 2628 ** CAPI3REF: Memory Allocator Statistics 2629 ** 2630 ** SQLite provides these two interfaces for reporting on the status 2631 ** of the [sqlite3_malloc()], [sqlite3_free()], and [sqlite3_realloc()] 2632 ** routines, which form the built-in memory allocation subsystem. 2633 ** 2634 ** ^The [sqlite3_memory_used()] routine returns the number of bytes 2635 ** of memory currently outstanding (malloced but not freed). 2636 ** ^The [sqlite3_memory_highwater()] routine returns the maximum 2637 ** value of [sqlite3_memory_used()] since the high-water mark 2638 ** was last reset. ^The values returned by [sqlite3_memory_used()] and 2639 ** [sqlite3_memory_highwater()] include any overhead 2640 ** added by SQLite in its implementation of [sqlite3_malloc()], 2641 ** but not overhead added by the any underlying system library 2642 ** routines that [sqlite3_malloc()] may call. 2643 ** 2644 ** ^The memory high-water mark is reset to the current value of 2645 ** [sqlite3_memory_used()] if and only if the parameter to 2646 ** [sqlite3_memory_highwater()] is true. ^The value returned 2647 ** by [sqlite3_memory_highwater(1)] is the high-water mark 2648 ** prior to the reset. 2649 */ 2650 SQLITE_API sqlite3_int64 sqlite3_memory_used(void); 2651 SQLITE_API sqlite3_int64 sqlite3_memory_highwater(int resetFlag); 2652 2653 /* 2654 ** CAPI3REF: Pseudo-Random Number Generator 2655 ** 2656 ** SQLite contains a high-quality pseudo-random number generator (PRNG) used to 2657 ** select random [ROWID | ROWIDs] when inserting new records into a table that 2658 ** already uses the largest possible [ROWID]. The PRNG is also used for 2659 ** the build-in random() and randomblob() SQL functions. This interface allows 2660 ** applications to access the same PRNG for other purposes. 2661 ** 2662 ** ^A call to this routine stores N bytes of randomness into buffer P. 2663 ** ^The P parameter can be a NULL pointer. 2664 ** 2665 ** ^If this routine has not been previously called or if the previous 2666 ** call had N less than one or a NULL pointer for P, then the PRNG is 2667 ** seeded using randomness obtained from the xRandomness method of 2668 ** the default [sqlite3_vfs] object. 2669 ** ^If the previous call to this routine had an N of 1 or more and a 2670 ** non-NULL P then the pseudo-randomness is generated 2671 ** internally and without recourse to the [sqlite3_vfs] xRandomness 2672 ** method. 2673 */ 2674 SQLITE_API void sqlite3_randomness(int N, void *P); 2675 2676 /* 2677 ** CAPI3REF: Compile-Time Authorization Callbacks 2678 ** METHOD: sqlite3 2679 ** 2680 ** ^This routine registers an authorizer callback with a particular 2681 ** [database connection], supplied in the first argument. 2682 ** ^The authorizer callback is invoked as SQL statements are being compiled 2683 ** by [sqlite3_prepare()] or its variants [sqlite3_prepare_v2()], 2684 ** [sqlite3_prepare16()] and [sqlite3_prepare16_v2()]. ^At various 2685 ** points during the compilation process, as logic is being created 2686 ** to perform various actions, the authorizer callback is invoked to 2687 ** see if those actions are allowed. ^The authorizer callback should 2688 ** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the 2689 ** specific action but allow the SQL statement to continue to be 2690 ** compiled, or [SQLITE_DENY] to cause the entire SQL statement to be 2691 ** rejected with an error. ^If the authorizer callback returns 2692 ** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY] 2693 ** then the [sqlite3_prepare_v2()] or equivalent call that triggered 2694 ** the authorizer will fail with an error message. 2695 ** 2696 ** When the callback returns [SQLITE_OK], that means the operation 2697 ** requested is ok. ^When the callback returns [SQLITE_DENY], the 2698 ** [sqlite3_prepare_v2()] or equivalent call that triggered the 2699 ** authorizer will fail with an error message explaining that 2700 ** access is denied. 2701 ** 2702 ** ^The first parameter to the authorizer callback is a copy of the third 2703 ** parameter to the sqlite3_set_authorizer() interface. ^The second parameter 2704 ** to the callback is an integer [SQLITE_COPY | action code] that specifies 2705 ** the particular action to be authorized. ^The third through sixth parameters 2706 ** to the callback are zero-terminated strings that contain additional 2707 ** details about the action to be authorized. 2708 ** 2709 ** ^If the action code is [SQLITE_READ] 2710 ** and the callback returns [SQLITE_IGNORE] then the 2711 ** [prepared statement] statement is constructed to substitute 2712 ** a NULL value in place of the table column that would have 2713 ** been read if [SQLITE_OK] had been returned. The [SQLITE_IGNORE] 2714 ** return can be used to deny an untrusted user access to individual 2715 ** columns of a table. 2716 ** ^If the action code is [SQLITE_DELETE] and the callback returns 2717 ** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the 2718 ** [truncate optimization] is disabled and all rows are deleted individually. 2719 ** 2720 ** An authorizer is used when [sqlite3_prepare | preparing] 2721 ** SQL statements from an untrusted source, to ensure that the SQL statements 2722 ** do not try to access data they are not allowed to see, or that they do not 2723 ** try to execute malicious statements that damage the database. For 2724 ** example, an application may allow a user to enter arbitrary 2725 ** SQL queries for evaluation by a database. But the application does 2726 ** not want the user to be able to make arbitrary changes to the 2727 ** database. An authorizer could then be put in place while the 2728 ** user-entered SQL is being [sqlite3_prepare | prepared] that 2729 ** disallows everything except [SELECT] statements. 2730 ** 2731 ** Applications that need to process SQL from untrusted sources 2732 ** might also consider lowering resource limits using [sqlite3_limit()] 2733 ** and limiting database size using the [max_page_count] [PRAGMA] 2734 ** in addition to using an authorizer. 2735 ** 2736 ** ^(Only a single authorizer can be in place on a database connection 2737 ** at a time. Each call to sqlite3_set_authorizer overrides the 2738 ** previous call.)^ ^Disable the authorizer by installing a NULL callback. 2739 ** The authorizer is disabled by default. 2740 ** 2741 ** The authorizer callback must not do anything that will modify 2742 ** the database connection that invoked the authorizer callback. 2743 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their 2744 ** database connections for the meaning of "modify" in this paragraph. 2745 ** 2746 ** ^When [sqlite3_prepare_v2()] is used to prepare a statement, the 2747 ** statement might be re-prepared during [sqlite3_step()] due to a 2748 ** schema change. Hence, the application should ensure that the 2749 ** correct authorizer callback remains in place during the [sqlite3_step()]. 2750 ** 2751 ** ^Note that the authorizer callback is invoked only during 2752 ** [sqlite3_prepare()] or its variants. Authorization is not 2753 ** performed during statement evaluation in [sqlite3_step()], unless 2754 ** as stated in the previous paragraph, sqlite3_step() invokes 2755 ** sqlite3_prepare_v2() to reprepare a statement after a schema change. 2756 */ 2757 SQLITE_API int sqlite3_set_authorizer( 2758 sqlite3*, 2759 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*), 2760 void *pUserData 2761 ); 2762 2763 /* 2764 ** CAPI3REF: Authorizer Return Codes 2765 ** 2766 ** The [sqlite3_set_authorizer | authorizer callback function] must 2767 ** return either [SQLITE_OK] or one of these two constants in order 2768 ** to signal SQLite whether or not the action is permitted. See the 2769 ** [sqlite3_set_authorizer | authorizer documentation] for additional 2770 ** information. 2771 ** 2772 ** Note that SQLITE_IGNORE is also used as a [conflict resolution mode] 2773 ** returned from the [sqlite3_vtab_on_conflict()] interface. 2774 */ 2775 #define SQLITE_DENY 1 /* Abort the SQL statement with an error */ 2776 #define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */ 2777 2778 /* 2779 ** CAPI3REF: Authorizer Action Codes 2780 ** 2781 ** The [sqlite3_set_authorizer()] interface registers a callback function 2782 ** that is invoked to authorize certain SQL statement actions. The 2783 ** second parameter to the callback is an integer code that specifies 2784 ** what action is being authorized. These are the integer action codes that 2785 ** the authorizer callback may be passed. 2786 ** 2787 ** These action code values signify what kind of operation is to be 2788 ** authorized. The 3rd and 4th parameters to the authorization 2789 ** callback function will be parameters or NULL depending on which of these 2790 ** codes is used as the second parameter. ^(The 5th parameter to the 2791 ** authorizer callback is the name of the database ("main", "temp", 2792 ** etc.) if applicable.)^ ^The 6th parameter to the authorizer callback 2793 ** is the name of the inner-most trigger or view that is responsible for 2794 ** the access attempt or NULL if this access attempt is directly from 2795 ** top-level SQL code. 2796 */ 2797 /******************************************* 3rd ************ 4th ***********/ 2798 #define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */ 2799 #define SQLITE_CREATE_TABLE 2 /* Table Name NULL */ 2800 #define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */ 2801 #define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */ 2802 #define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */ 2803 #define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */ 2804 #define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */ 2805 #define SQLITE_CREATE_VIEW 8 /* View Name NULL */ 2806 #define SQLITE_DELETE 9 /* Table Name NULL */ 2807 #define SQLITE_DROP_INDEX 10 /* Index Name Table Name */ 2808 #define SQLITE_DROP_TABLE 11 /* Table Name NULL */ 2809 #define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */ 2810 #define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */ 2811 #define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */ 2812 #define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */ 2813 #define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */ 2814 #define SQLITE_DROP_VIEW 17 /* View Name NULL */ 2815 #define SQLITE_INSERT 18 /* Table Name NULL */ 2816 #define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */ 2817 #define SQLITE_READ 20 /* Table Name Column Name */ 2818 #define SQLITE_SELECT 21 /* NULL NULL */ 2819 #define SQLITE_TRANSACTION 22 /* Operation NULL */ 2820 #define SQLITE_UPDATE 23 /* Table Name Column Name */ 2821 #define SQLITE_ATTACH 24 /* Filename NULL */ 2822 #define SQLITE_DETACH 25 /* Database Name NULL */ 2823 #define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */ 2824 #define SQLITE_REINDEX 27 /* Index Name NULL */ 2825 #define SQLITE_ANALYZE 28 /* Table Name NULL */ 2826 #define SQLITE_CREATE_VTABLE 29 /* Table Name Module Name */ 2827 #define SQLITE_DROP_VTABLE 30 /* Table Name Module Name */ 2828 #define SQLITE_FUNCTION 31 /* NULL Function Name */ 2829 #define SQLITE_SAVEPOINT 32 /* Operation Savepoint Name */ 2830 #define SQLITE_COPY 0 /* No longer used */ 2831 #define SQLITE_RECURSIVE 33 /* NULL NULL */ 2832 2833 /* 2834 ** CAPI3REF: Tracing And Profiling Functions 2835 ** METHOD: sqlite3 2836 ** 2837 ** These routines are deprecated. Use the [sqlite3_trace_v2()] interface 2838 ** instead of the routines described here. 2839 ** 2840 ** These routines register callback functions that can be used for 2841 ** tracing and profiling the execution of SQL statements. 2842 ** 2843 ** ^The callback function registered by sqlite3_trace() is invoked at 2844 ** various times when an SQL statement is being run by [sqlite3_step()]. 2845 ** ^The sqlite3_trace() callback is invoked with a UTF-8 rendering of the 2846 ** SQL statement text as the statement first begins executing. 2847 ** ^(Additional sqlite3_trace() callbacks might occur 2848 ** as each triggered subprogram is entered. The callbacks for triggers 2849 ** contain a UTF-8 SQL comment that identifies the trigger.)^ 2850 ** 2851 ** The [SQLITE_TRACE_SIZE_LIMIT] compile-time option can be used to limit 2852 ** the length of [bound parameter] expansion in the output of sqlite3_trace(). 2853 ** 2854 ** ^The callback function registered by sqlite3_profile() is invoked 2855 ** as each SQL statement finishes. ^The profile callback contains 2856 ** the original statement text and an estimate of wall-clock time 2857 ** of how long that statement took to run. ^The profile callback 2858 ** time is in units of nanoseconds, however the current implementation 2859 ** is only capable of millisecond resolution so the six least significant 2860 ** digits in the time are meaningless. Future versions of SQLite 2861 ** might provide greater resolution on the profiler callback. The 2862 ** sqlite3_profile() function is considered experimental and is 2863 ** subject to change in future versions of SQLite. 2864 */ 2865 SQLITE_API SQLITE_DEPRECATED void *sqlite3_trace(sqlite3*, 2866 void(*xTrace)(void*,const char*), void*); 2867 SQLITE_API SQLITE_DEPRECATED void *sqlite3_profile(sqlite3*, 2868 void(*xProfile)(void*,const char*,sqlite3_uint64), void*); 2869 2870 /* 2871 ** CAPI3REF: SQL Trace Event Codes 2872 ** KEYWORDS: SQLITE_TRACE 2873 ** 2874 ** These constants identify classes of events that can be monitored 2875 ** using the [sqlite3_trace_v2()] tracing logic. The third argument 2876 ** to [sqlite3_trace_v2()] is an OR-ed combination of one or more of 2877 ** the following constants. ^The first argument to the trace callback 2878 ** is one of the following constants. 2879 ** 2880 ** New tracing constants may be added in future releases. 2881 ** 2882 ** ^A trace callback has four arguments: xCallback(T,C,P,X). 2883 ** ^The T argument is one of the integer type codes above. 2884 ** ^The C argument is a copy of the context pointer passed in as the 2885 ** fourth argument to [sqlite3_trace_v2()]. 2886 ** The P and X arguments are pointers whose meanings depend on T. 2887 ** 2888 ** <dl> 2889 ** [[SQLITE_TRACE_STMT]] <dt>SQLITE_TRACE_STMT</dt> 2890 ** <dd>^An SQLITE_TRACE_STMT callback is invoked when a prepared statement 2891 ** first begins running and possibly at other times during the 2892 ** execution of the prepared statement, such as at the start of each 2893 ** trigger subprogram. ^The P argument is a pointer to the 2894 ** [prepared statement]. ^The X argument is a pointer to a string which 2895 ** is the unexpanded SQL text of the prepared statement or an SQL comment 2896 ** that indicates the invocation of a trigger. ^The callback can compute 2897 ** the same text that would have been returned by the legacy [sqlite3_trace()] 2898 ** interface by using the X argument when X begins with "--" and invoking 2899 ** [sqlite3_expanded_sql(P)] otherwise. 2900 ** 2901 ** [[SQLITE_TRACE_PROFILE]] <dt>SQLITE_TRACE_PROFILE</dt> 2902 ** <dd>^An SQLITE_TRACE_PROFILE callback provides approximately the same 2903 ** information as is provided by the [sqlite3_profile()] callback. 2904 ** ^The P argument is a pointer to the [prepared statement] and the 2905 ** X argument points to a 64-bit integer which is the estimated of 2906 ** the number of nanosecond that the prepared statement took to run. 2907 ** ^The SQLITE_TRACE_PROFILE callback is invoked when the statement finishes. 2908 ** 2909 ** [[SQLITE_TRACE_ROW]] <dt>SQLITE_TRACE_ROW</dt> 2910 ** <dd>^An SQLITE_TRACE_ROW callback is invoked whenever a prepared 2911 ** statement generates a single row of result. 2912 ** ^The P argument is a pointer to the [prepared statement] and the 2913 ** X argument is unused. 2914 ** 2915 ** [[SQLITE_TRACE_CLOSE]] <dt>SQLITE_TRACE_CLOSE</dt> 2916 ** <dd>^An SQLITE_TRACE_CLOSE callback is invoked when a database 2917 ** connection closes. 2918 ** ^The P argument is a pointer to the [database connection] object 2919 ** and the X argument is unused. 2920 ** </dl> 2921 */ 2922 #define SQLITE_TRACE_STMT 0x01 2923 #define SQLITE_TRACE_PROFILE 0x02 2924 #define SQLITE_TRACE_ROW 0x04 2925 #define SQLITE_TRACE_CLOSE 0x08 2926 2927 /* 2928 ** CAPI3REF: SQL Trace Hook 2929 ** METHOD: sqlite3 2930 ** 2931 ** ^The sqlite3_trace_v2(D,M,X,P) interface registers a trace callback 2932 ** function X against [database connection] D, using property mask M 2933 ** and context pointer P. ^If the X callback is 2934 ** NULL or if the M mask is zero, then tracing is disabled. The 2935 ** M argument should be the bitwise OR-ed combination of 2936 ** zero or more [SQLITE_TRACE] constants. 2937 ** 2938 ** ^Each call to either sqlite3_trace() or sqlite3_trace_v2() overrides 2939 ** (cancels) any prior calls to sqlite3_trace() or sqlite3_trace_v2(). 2940 ** 2941 ** ^The X callback is invoked whenever any of the events identified by 2942 ** mask M occur. ^The integer return value from the callback is currently 2943 ** ignored, though this may change in future releases. Callback 2944 ** implementations should return zero to ensure future compatibility. 2945 ** 2946 ** ^A trace callback is invoked with four arguments: callback(T,C,P,X). 2947 ** ^The T argument is one of the [SQLITE_TRACE] 2948 ** constants to indicate why the callback was invoked. 2949 ** ^The C argument is a copy of the context pointer. 2950 ** The P and X arguments are pointers whose meanings depend on T. 2951 ** 2952 ** The sqlite3_trace_v2() interface is intended to replace the legacy 2953 ** interfaces [sqlite3_trace()] and [sqlite3_profile()], both of which 2954 ** are deprecated. 2955 */ 2956 SQLITE_API int sqlite3_trace_v2( 2957 sqlite3*, 2958 unsigned uMask, 2959 int(*xCallback)(unsigned,void*,void*,void*), 2960 void *pCtx 2961 ); 2962 2963 /* 2964 ** CAPI3REF: Query Progress Callbacks 2965 ** METHOD: sqlite3 2966 ** 2967 ** ^The sqlite3_progress_handler(D,N,X,P) interface causes the callback 2968 ** function X to be invoked periodically during long running calls to 2969 ** [sqlite3_exec()], [sqlite3_step()] and [sqlite3_get_table()] for 2970 ** database connection D. An example use for this 2971 ** interface is to keep a GUI updated during a large query. 2972 ** 2973 ** ^The parameter P is passed through as the only parameter to the 2974 ** callback function X. ^The parameter N is the approximate number of 2975 ** [virtual machine instructions] that are evaluated between successive 2976 ** invocations of the callback X. ^If N is less than one then the progress 2977 ** handler is disabled. 2978 ** 2979 ** ^Only a single progress handler may be defined at one time per 2980 ** [database connection]; setting a new progress handler cancels the 2981 ** old one. ^Setting parameter X to NULL disables the progress handler. 2982 ** ^The progress handler is also disabled by setting N to a value less 2983 ** than 1. 2984 ** 2985 ** ^If the progress callback returns non-zero, the operation is 2986 ** interrupted. This feature can be used to implement a 2987 ** "Cancel" button on a GUI progress dialog box. 2988 ** 2989 ** The progress handler callback must not do anything that will modify 2990 ** the database connection that invoked the progress handler. 2991 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their 2992 ** database connections for the meaning of "modify" in this paragraph. 2993 ** 2994 */ 2995 SQLITE_API void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*); 2996 2997 /* 2998 ** CAPI3REF: Opening A New Database Connection 2999 ** CONSTRUCTOR: sqlite3 3000 ** 3001 ** ^These routines open an SQLite database file as specified by the 3002 ** filename argument. ^The filename argument is interpreted as UTF-8 for 3003 ** sqlite3_open() and sqlite3_open_v2() and as UTF-16 in the native byte 3004 ** order for sqlite3_open16(). ^(A [database connection] handle is usually 3005 ** returned in *ppDb, even if an error occurs. The only exception is that 3006 ** if SQLite is unable to allocate memory to hold the [sqlite3] object, 3007 ** a NULL will be written into *ppDb instead of a pointer to the [sqlite3] 3008 ** object.)^ ^(If the database is opened (and/or created) successfully, then 3009 ** [SQLITE_OK] is returned. Otherwise an [error code] is returned.)^ ^The 3010 ** [sqlite3_errmsg()] or [sqlite3_errmsg16()] routines can be used to obtain 3011 ** an English language description of the error following a failure of any 3012 ** of the sqlite3_open() routines. 3013 ** 3014 ** ^The default encoding will be UTF-8 for databases created using 3015 ** sqlite3_open() or sqlite3_open_v2(). ^The default encoding for databases 3016 ** created using sqlite3_open16() will be UTF-16 in the native byte order. 3017 ** 3018 ** Whether or not an error occurs when it is opened, resources 3019 ** associated with the [database connection] handle should be released by 3020 ** passing it to [sqlite3_close()] when it is no longer required. 3021 ** 3022 ** The sqlite3_open_v2() interface works like sqlite3_open() 3023 ** except that it accepts two additional parameters for additional control 3024 ** over the new database connection. ^(The flags parameter to 3025 ** sqlite3_open_v2() can take one of 3026 ** the following three values, optionally combined with the 3027 ** [SQLITE_OPEN_NOMUTEX], [SQLITE_OPEN_FULLMUTEX], [SQLITE_OPEN_SHAREDCACHE], 3028 ** [SQLITE_OPEN_PRIVATECACHE], and/or [SQLITE_OPEN_URI] flags:)^ 3029 ** 3030 ** <dl> 3031 ** ^(<dt>[SQLITE_OPEN_READONLY]</dt> 3032 ** <dd>The database is opened in read-only mode. If the database does not 3033 ** already exist, an error is returned.</dd>)^ 3034 ** 3035 ** ^(<dt>[SQLITE_OPEN_READWRITE]</dt> 3036 ** <dd>The database is opened for reading and writing if possible, or reading 3037 ** only if the file is write protected by the operating system. In either 3038 ** case the database must already exist, otherwise an error is returned.</dd>)^ 3039 ** 3040 ** ^(<dt>[SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE]</dt> 3041 ** <dd>The database is opened for reading and writing, and is created if 3042 ** it does not already exist. This is the behavior that is always used for 3043 ** sqlite3_open() and sqlite3_open16().</dd>)^ 3044 ** </dl> 3045 ** 3046 ** If the 3rd parameter to sqlite3_open_v2() is not one of the 3047 ** combinations shown above optionally combined with other 3048 ** [SQLITE_OPEN_READONLY | SQLITE_OPEN_* bits] 3049 ** then the behavior is undefined. 3050 ** 3051 ** ^If the [SQLITE_OPEN_NOMUTEX] flag is set, then the database connection 3052 ** opens in the multi-thread [threading mode] as long as the single-thread 3053 ** mode has not been set at compile-time or start-time. ^If the 3054 ** [SQLITE_OPEN_FULLMUTEX] flag is set then the database connection opens 3055 ** in the serialized [threading mode] unless single-thread was 3056 ** previously selected at compile-time or start-time. 3057 ** ^The [SQLITE_OPEN_SHAREDCACHE] flag causes the database connection to be 3058 ** eligible to use [shared cache mode], regardless of whether or not shared 3059 ** cache is enabled using [sqlite3_enable_shared_cache()]. ^The 3060 ** [SQLITE_OPEN_PRIVATECACHE] flag causes the database connection to not 3061 ** participate in [shared cache mode] even if it is enabled. 3062 ** 3063 ** ^The fourth parameter to sqlite3_open_v2() is the name of the 3064 ** [sqlite3_vfs] object that defines the operating system interface that 3065 ** the new database connection should use. ^If the fourth parameter is 3066 ** a NULL pointer then the default [sqlite3_vfs] object is used. 3067 ** 3068 ** ^If the filename is ":memory:", then a private, temporary in-memory database 3069 ** is created for the connection. ^This in-memory database will vanish when 3070 ** the database connection is closed. Future versions of SQLite might 3071 ** make use of additional special filenames that begin with the ":" character. 3072 ** It is recommended that when a database filename actually does begin with 3073 ** a ":" character you should prefix the filename with a pathname such as 3074 ** "./" to avoid ambiguity. 3075 ** 3076 ** ^If the filename is an empty string, then a private, temporary 3077 ** on-disk database will be created. ^This private database will be 3078 ** automatically deleted as soon as the database connection is closed. 3079 ** 3080 ** [[URI filenames in sqlite3_open()]] <h3>URI Filenames</h3> 3081 ** 3082 ** ^If [URI filename] interpretation is enabled, and the filename argument 3083 ** begins with "file:", then the filename is interpreted as a URI. ^URI 3084 ** filename interpretation is enabled if the [SQLITE_OPEN_URI] flag is 3085 ** set in the fourth argument to sqlite3_open_v2(), or if it has 3086 ** been enabled globally using the [SQLITE_CONFIG_URI] option with the 3087 ** [sqlite3_config()] method or by the [SQLITE_USE_URI] compile-time option. 3088 ** As of SQLite version 3.7.7, URI filename interpretation is turned off 3089 ** by default, but future releases of SQLite might enable URI filename 3090 ** interpretation by default. See "[URI filenames]" for additional 3091 ** information. 3092 ** 3093 ** URI filenames are parsed according to RFC 3986. ^If the URI contains an 3094 ** authority, then it must be either an empty string or the string 3095 ** "localhost". ^If the authority is not an empty string or "localhost", an 3096 ** error is returned to the caller. ^The fragment component of a URI, if 3097 ** present, is ignored. 3098 ** 3099 ** ^SQLite uses the path component of the URI as the name of the disk file 3100 ** which contains the database. ^If the path begins with a '/' character, 3101 ** then it is interpreted as an absolute path. ^If the path does not begin 3102 ** with a '/' (meaning that the authority section is omitted from the URI) 3103 ** then the path is interpreted as a relative path. 3104 ** ^(On windows, the first component of an absolute path 3105 ** is a drive specification (e.g. "C:").)^ 3106 ** 3107 ** [[core URI query parameters]] 3108 ** The query component of a URI may contain parameters that are interpreted 3109 ** either by SQLite itself, or by a [VFS | custom VFS implementation]. 3110 ** SQLite and its built-in [VFSes] interpret the 3111 ** following query parameters: 3112 ** 3113 ** <ul> 3114 ** <li> <b>vfs</b>: ^The "vfs" parameter may be used to specify the name of 3115 ** a VFS object that provides the operating system interface that should 3116 ** be used to access the database file on disk. ^If this option is set to 3117 ** an empty string the default VFS object is used. ^Specifying an unknown 3118 ** VFS is an error. ^If sqlite3_open_v2() is used and the vfs option is 3119 ** present, then the VFS specified by the option takes precedence over 3120 ** the value passed as the fourth parameter to sqlite3_open_v2(). 3121 ** 3122 ** <li> <b>mode</b>: ^(The mode parameter may be set to either "ro", "rw", 3123 ** "rwc", or "memory". Attempting to set it to any other value is 3124 ** an error)^. 3125 ** ^If "ro" is specified, then the database is opened for read-only 3126 ** access, just as if the [SQLITE_OPEN_READONLY] flag had been set in the 3127 ** third argument to sqlite3_open_v2(). ^If the mode option is set to 3128 ** "rw", then the database is opened for read-write (but not create) 3129 ** access, as if SQLITE_OPEN_READWRITE (but not SQLITE_OPEN_CREATE) had 3130 ** been set. ^Value "rwc" is equivalent to setting both 3131 ** SQLITE_OPEN_READWRITE and SQLITE_OPEN_CREATE. ^If the mode option is 3132 ** set to "memory" then a pure [in-memory database] that never reads 3133 ** or writes from disk is used. ^It is an error to specify a value for 3134 ** the mode parameter that is less restrictive than that specified by 3135 ** the flags passed in the third parameter to sqlite3_open_v2(). 3136 ** 3137 ** <li> <b>cache</b>: ^The cache parameter may be set to either "shared" or 3138 ** "private". ^Setting it to "shared" is equivalent to setting the 3139 ** SQLITE_OPEN_SHAREDCACHE bit in the flags argument passed to 3140 ** sqlite3_open_v2(). ^Setting the cache parameter to "private" is 3141 ** equivalent to setting the SQLITE_OPEN_PRIVATECACHE bit. 3142 ** ^If sqlite3_open_v2() is used and the "cache" parameter is present in 3143 ** a URI filename, its value overrides any behavior requested by setting 3144 ** SQLITE_OPEN_PRIVATECACHE or SQLITE_OPEN_SHAREDCACHE flag. 3145 ** 3146 ** <li> <b>psow</b>: ^The psow parameter indicates whether or not the 3147 ** [powersafe overwrite] property does or does not apply to the 3148 ** storage media on which the database file resides. 3149 ** 3150 ** <li> <b>nolock</b>: ^The nolock parameter is a boolean query parameter 3151 ** which if set disables file locking in rollback journal modes. This 3152 ** is useful for accessing a database on a filesystem that does not 3153 ** support locking. Caution: Database corruption might result if two 3154 ** or more processes write to the same database and any one of those 3155 ** processes uses nolock=1. 3156 ** 3157 ** <li> <b>immutable</b>: ^The immutable parameter is a boolean query 3158 ** parameter that indicates that the database file is stored on 3159 ** read-only media. ^When immutable is set, SQLite assumes that the 3160 ** database file cannot be changed, even by a process with higher 3161 ** privilege, and so the database is opened read-only and all locking 3162 ** and change detection is disabled. Caution: Setting the immutable 3163 ** property on a database file that does in fact change can result 3164 ** in incorrect query results and/or [SQLITE_CORRUPT] errors. 3165 ** See also: [SQLITE_IOCAP_IMMUTABLE]. 3166 ** 3167 ** </ul> 3168 ** 3169 ** ^Specifying an unknown parameter in the query component of a URI is not an 3170 ** error. Future versions of SQLite might understand additional query 3171 ** parameters. See "[query parameters with special meaning to SQLite]" for 3172 ** additional information. 3173 ** 3174 ** [[URI filename examples]] <h3>URI filename examples</h3> 3175 ** 3176 ** <table border="1" align=center cellpadding=5> 3177 ** <tr><th> URI filenames <th> Results 3178 ** <tr><td> file:data.db <td> 3179 ** Open the file "data.db" in the current directory. 3180 ** <tr><td> file:/home/fred/data.db<br> 3181 ** file:///home/fred/data.db <br> 3182 ** file://localhost/home/fred/data.db <br> <td> 3183 ** Open the database file "/home/fred/data.db". 3184 ** <tr><td> file://darkstar/home/fred/data.db <td> 3185 ** An error. "darkstar" is not a recognized authority. 3186 ** <tr><td style="white-space:nowrap"> 3187 ** file:///C:/Documents%20and%20Settings/fred/Desktop/data.db 3188 ** <td> Windows only: Open the file "data.db" on fred's desktop on drive 3189 ** C:. Note that the %20 escaping in this example is not strictly 3190 ** necessary - space characters can be used literally 3191 ** in URI filenames. 3192 ** <tr><td> file:data.db?mode=ro&cache=private <td> 3193 ** Open file "data.db" in the current directory for read-only access. 3194 ** Regardless of whether or not shared-cache mode is enabled by 3195 ** default, use a private cache. 3196 ** <tr><td> file:/home/fred/data.db?vfs=unix-dotfile <td> 3197 ** Open file "/home/fred/data.db". Use the special VFS "unix-dotfile" 3198 ** that uses dot-files in place of posix advisory locking. 3199 ** <tr><td> file:data.db?mode=readonly <td> 3200 ** An error. "readonly" is not a valid option for the "mode" parameter. 3201 ** </table> 3202 ** 3203 ** ^URI hexadecimal escape sequences (%HH) are supported within the path and 3204 ** query components of a URI. A hexadecimal escape sequence consists of a 3205 ** percent sign - "%" - followed by exactly two hexadecimal digits 3206 ** specifying an octet value. ^Before the path or query components of a 3207 ** URI filename are interpreted, they are encoded using UTF-8 and all 3208 ** hexadecimal escape sequences replaced by a single byte containing the 3209 ** corresponding octet. If this process generates an invalid UTF-8 encoding, 3210 ** the results are undefined. 3211 ** 3212 ** <b>Note to Windows users:</b> The encoding used for the filename argument 3213 ** of sqlite3_open() and sqlite3_open_v2() must be UTF-8, not whatever 3214 ** codepage is currently defined. Filenames containing international 3215 ** characters must be converted to UTF-8 prior to passing them into 3216 ** sqlite3_open() or sqlite3_open_v2(). 3217 ** 3218 ** <b>Note to Windows Runtime users:</b> The temporary directory must be set 3219 ** prior to calling sqlite3_open() or sqlite3_open_v2(). Otherwise, various 3220 ** features that require the use of temporary files may fail. 3221 ** 3222 ** See also: [sqlite3_temp_directory] 3223 */ 3224 SQLITE_API int sqlite3_open( 3225 const char *filename, /* Database filename (UTF-8) */ 3226 sqlite3 **ppDb /* OUT: SQLite db handle */ 3227 ); 3228 SQLITE_API int sqlite3_open16( 3229 const void *filename, /* Database filename (UTF-16) */ 3230 sqlite3 **ppDb /* OUT: SQLite db handle */ 3231 ); 3232 SQLITE_API int sqlite3_open_v2( 3233 const char *filename, /* Database filename (UTF-8) */ 3234 sqlite3 **ppDb, /* OUT: SQLite db handle */ 3235 int flags, /* Flags */ 3236 const char *zVfs /* Name of VFS module to use */ 3237 ); 3238 3239 /* 3240 ** CAPI3REF: Obtain Values For URI Parameters 3241 ** 3242 ** These are utility routines, useful to VFS implementations, that check 3243 ** to see if a database file was a URI that contained a specific query 3244 ** parameter, and if so obtains the value of that query parameter. 3245 ** 3246 ** If F is the database filename pointer passed into the xOpen() method of 3247 ** a VFS implementation when the flags parameter to xOpen() has one or 3248 ** more of the [SQLITE_OPEN_URI] or [SQLITE_OPEN_MAIN_DB] bits set and 3249 ** P is the name of the query parameter, then 3250 ** sqlite3_uri_parameter(F,P) returns the value of the P 3251 ** parameter if it exists or a NULL pointer if P does not appear as a 3252 ** query parameter on F. If P is a query parameter of F 3253 ** has no explicit value, then sqlite3_uri_parameter(F,P) returns 3254 ** a pointer to an empty string. 3255 ** 3256 ** The sqlite3_uri_boolean(F,P,B) routine assumes that P is a boolean 3257 ** parameter and returns true (1) or false (0) according to the value 3258 ** of P. The sqlite3_uri_boolean(F,P,B) routine returns true (1) if the 3259 ** value of query parameter P is one of "yes", "true", or "on" in any 3260 ** case or if the value begins with a non-zero number. The 3261 ** sqlite3_uri_boolean(F,P,B) routines returns false (0) if the value of 3262 ** query parameter P is one of "no", "false", or "off" in any case or 3263 ** if the value begins with a numeric zero. If P is not a query 3264 ** parameter on F or if the value of P is does not match any of the 3265 ** above, then sqlite3_uri_boolean(F,P,B) returns (B!=0). 3266 ** 3267 ** The sqlite3_uri_int64(F,P,D) routine converts the value of P into a 3268 ** 64-bit signed integer and returns that integer, or D if P does not 3269 ** exist. If the value of P is something other than an integer, then 3270 ** zero is returned. 3271 ** 3272 ** If F is a NULL pointer, then sqlite3_uri_parameter(F,P) returns NULL and 3273 ** sqlite3_uri_boolean(F,P,B) returns B. If F is not a NULL pointer and 3274 ** is not a database file pathname pointer that SQLite passed into the xOpen 3275 ** VFS method, then the behavior of this routine is undefined and probably 3276 ** undesirable. 3277 */ 3278 SQLITE_API const char *sqlite3_uri_parameter(const char *zFilename, const char *zParam); 3279 SQLITE_API int sqlite3_uri_boolean(const char *zFile, const char *zParam, int bDefault); 3280 SQLITE_API sqlite3_int64 sqlite3_uri_int64(const char*, const char*, sqlite3_int64); 3281 3282 3283 /* 3284 ** CAPI3REF: Error Codes And Messages 3285 ** METHOD: sqlite3 3286 ** 3287 ** ^If the most recent sqlite3_* API call associated with 3288 ** [database connection] D failed, then the sqlite3_errcode(D) interface 3289 ** returns the numeric [result code] or [extended result code] for that 3290 ** API call. 3291 ** If the most recent API call was successful, 3292 ** then the return value from sqlite3_errcode() is undefined. 3293 ** ^The sqlite3_extended_errcode() 3294 ** interface is the same except that it always returns the 3295 ** [extended result code] even when extended result codes are 3296 ** disabled. 3297 ** 3298 ** ^The sqlite3_errmsg() and sqlite3_errmsg16() return English-language 3299 ** text that describes the error, as either UTF-8 or UTF-16 respectively. 3300 ** ^(Memory to hold the error message string is managed internally. 3301 ** The application does not need to worry about freeing the result. 3302 ** However, the error string might be overwritten or deallocated by 3303 ** subsequent calls to other SQLite interface functions.)^ 3304 ** 3305 ** ^The sqlite3_errstr() interface returns the English-language text 3306 ** that describes the [result code], as UTF-8. 3307 ** ^(Memory to hold the error message string is managed internally 3308 ** and must not be freed by the application)^. 3309 ** 3310 ** When the serialized [threading mode] is in use, it might be the 3311 ** case that a second error occurs on a separate thread in between 3312 ** the time of the first error and the call to these interfaces. 3313 ** When that happens, the second error will be reported since these 3314 ** interfaces always report the most recent result. To avoid 3315 ** this, each thread can obtain exclusive use of the [database connection] D 3316 ** by invoking [sqlite3_mutex_enter]([sqlite3_db_mutex](D)) before beginning 3317 ** to use D and invoking [sqlite3_mutex_leave]([sqlite3_db_mutex](D)) after 3318 ** all calls to the interfaces listed here are completed. 3319 ** 3320 ** If an interface fails with SQLITE_MISUSE, that means the interface 3321 ** was invoked incorrectly by the application. In that case, the 3322 ** error code and message may or may not be set. 3323 */ 3324 SQLITE_API int sqlite3_errcode(sqlite3 *db); 3325 SQLITE_API int sqlite3_extended_errcode(sqlite3 *db); 3326 SQLITE_API const char *sqlite3_errmsg(sqlite3*); 3327 SQLITE_API const void *sqlite3_errmsg16(sqlite3*); 3328 SQLITE_API const char *sqlite3_errstr(int); 3329 3330 /* 3331 ** CAPI3REF: Prepared Statement Object 3332 ** KEYWORDS: {prepared statement} {prepared statements} 3333 ** 3334 ** An instance of this object represents a single SQL statement that 3335 ** has been compiled into binary form and is ready to be evaluated. 3336 ** 3337 ** Think of each SQL statement as a separate computer program. The 3338 ** original SQL text is source code. A prepared statement object 3339 ** is the compiled object code. All SQL must be converted into a 3340 ** prepared statement before it can be run. 3341 ** 3342 ** The life-cycle of a prepared statement object usually goes like this: 3343 ** 3344 ** <ol> 3345 ** <li> Create the prepared statement object using [sqlite3_prepare_v2()]. 3346 ** <li> Bind values to [parameters] using the sqlite3_bind_*() 3347 ** interfaces. 3348 ** <li> Run the SQL by calling [sqlite3_step()] one or more times. 3349 ** <li> Reset the prepared statement using [sqlite3_reset()] then go back 3350 ** to step 2. Do this zero or more times. 3351 ** <li> Destroy the object using [sqlite3_finalize()]. 3352 ** </ol> 3353 */ 3354 typedef struct sqlite3_stmt sqlite3_stmt; 3355 3356 /* 3357 ** CAPI3REF: Run-time Limits 3358 ** METHOD: sqlite3 3359 ** 3360 ** ^(This interface allows the size of various constructs to be limited 3361 ** on a connection by connection basis. The first parameter is the 3362 ** [database connection] whose limit is to be set or queried. The 3363 ** second parameter is one of the [limit categories] that define a 3364 ** class of constructs to be size limited. The third parameter is the 3365 ** new limit for that construct.)^ 3366 ** 3367 ** ^If the new limit is a negative number, the limit is unchanged. 3368 ** ^(For each limit category SQLITE_LIMIT_<i>NAME</i> there is a 3369 ** [limits | hard upper bound] 3370 ** set at compile-time by a C preprocessor macro called 3371 ** [limits | SQLITE_MAX_<i>NAME</i>]. 3372 ** (The "_LIMIT_" in the name is changed to "_MAX_".))^ 3373 ** ^Attempts to increase a limit above its hard upper bound are 3374 ** silently truncated to the hard upper bound. 3375 ** 3376 ** ^Regardless of whether or not the limit was changed, the 3377 ** [sqlite3_limit()] interface returns the prior value of the limit. 3378 ** ^Hence, to find the current value of a limit without changing it, 3379 ** simply invoke this interface with the third parameter set to -1. 3380 ** 3381 ** Run-time limits are intended for use in applications that manage 3382 ** both their own internal database and also databases that are controlled 3383 ** by untrusted external sources. An example application might be a 3384 ** web browser that has its own databases for storing history and 3385 ** separate databases controlled by JavaScript applications downloaded 3386 ** off the Internet. The internal databases can be given the 3387 ** large, default limits. Databases managed by external sources can 3388 ** be given much smaller limits designed to prevent a denial of service 3389 ** attack. Developers might also want to use the [sqlite3_set_authorizer()] 3390 ** interface to further control untrusted SQL. The size of the database 3391 ** created by an untrusted script can be contained using the 3392 ** [max_page_count] [PRAGMA]. 3393 ** 3394 ** New run-time limit categories may be added in future releases. 3395 */ 3396 SQLITE_API int sqlite3_limit(sqlite3*, int id, int newVal); 3397 3398 /* 3399 ** CAPI3REF: Run-Time Limit Categories 3400 ** KEYWORDS: {limit category} {*limit categories} 3401 ** 3402 ** These constants define various performance limits 3403 ** that can be lowered at run-time using [sqlite3_limit()]. 3404 ** The synopsis of the meanings of the various limits is shown below. 3405 ** Additional information is available at [limits | Limits in SQLite]. 3406 ** 3407 ** <dl> 3408 ** [[SQLITE_LIMIT_LENGTH]] ^(<dt>SQLITE_LIMIT_LENGTH</dt> 3409 ** <dd>The maximum size of any string or BLOB or table row, in bytes.<dd>)^ 3410 ** 3411 ** [[SQLITE_LIMIT_SQL_LENGTH]] ^(<dt>SQLITE_LIMIT_SQL_LENGTH</dt> 3412 ** <dd>The maximum length of an SQL statement, in bytes.</dd>)^ 3413 ** 3414 ** [[SQLITE_LIMIT_COLUMN]] ^(<dt>SQLITE_LIMIT_COLUMN</dt> 3415 ** <dd>The maximum number of columns in a table definition or in the 3416 ** result set of a [SELECT] or the maximum number of columns in an index 3417 ** or in an ORDER BY or GROUP BY clause.</dd>)^ 3418 ** 3419 ** [[SQLITE_LIMIT_EXPR_DEPTH]] ^(<dt>SQLITE_LIMIT_EXPR_DEPTH</dt> 3420 ** <dd>The maximum depth of the parse tree on any expression.</dd>)^ 3421 ** 3422 ** [[SQLITE_LIMIT_COMPOUND_SELECT]] ^(<dt>SQLITE_LIMIT_COMPOUND_SELECT</dt> 3423 ** <dd>The maximum number of terms in a compound SELECT statement.</dd>)^ 3424 ** 3425 ** [[SQLITE_LIMIT_VDBE_OP]] ^(<dt>SQLITE_LIMIT_VDBE_OP</dt> 3426 ** <dd>The maximum number of instructions in a virtual machine program 3427 ** used to implement an SQL statement. If [sqlite3_prepare_v2()] or 3428 ** the equivalent tries to allocate space for more than this many opcodes 3429 ** in a single prepared statement, an SQLITE_NOMEM error is returned.</dd>)^ 3430 ** 3431 ** [[SQLITE_LIMIT_FUNCTION_ARG]] ^(<dt>SQLITE_LIMIT_FUNCTION_ARG</dt> 3432 ** <dd>The maximum number of arguments on a function.</dd>)^ 3433 ** 3434 ** [[SQLITE_LIMIT_ATTACHED]] ^(<dt>SQLITE_LIMIT_ATTACHED</dt> 3435 ** <dd>The maximum number of [ATTACH | attached databases].)^</dd> 3436 ** 3437 ** [[SQLITE_LIMIT_LIKE_PATTERN_LENGTH]] 3438 ** ^(<dt>SQLITE_LIMIT_LIKE_PATTERN_LENGTH</dt> 3439 ** <dd>The maximum length of the pattern argument to the [LIKE] or 3440 ** [GLOB] operators.</dd>)^ 3441 ** 3442 ** [[SQLITE_LIMIT_VARIABLE_NUMBER]] 3443 ** ^(<dt>SQLITE_LIMIT_VARIABLE_NUMBER</dt> 3444 ** <dd>The maximum index number of any [parameter] in an SQL statement.)^ 3445 ** 3446 ** [[SQLITE_LIMIT_TRIGGER_DEPTH]] ^(<dt>SQLITE_LIMIT_TRIGGER_DEPTH</dt> 3447 ** <dd>The maximum depth of recursion for triggers.</dd>)^ 3448 ** 3449 ** [[SQLITE_LIMIT_WORKER_THREADS]] ^(<dt>SQLITE_LIMIT_WORKER_THREADS</dt> 3450 ** <dd>The maximum number of auxiliary worker threads that a single 3451 ** [prepared statement] may start.</dd>)^ 3452 ** </dl> 3453 */ 3454 #define SQLITE_LIMIT_LENGTH 0 3455 #define SQLITE_LIMIT_SQL_LENGTH 1 3456 #define SQLITE_LIMIT_COLUMN 2 3457 #define SQLITE_LIMIT_EXPR_DEPTH 3 3458 #define SQLITE_LIMIT_COMPOUND_SELECT 4 3459 #define SQLITE_LIMIT_VDBE_OP 5 3460 #define SQLITE_LIMIT_FUNCTION_ARG 6 3461 #define SQLITE_LIMIT_ATTACHED 7 3462 #define SQLITE_LIMIT_LIKE_PATTERN_LENGTH 8 3463 #define SQLITE_LIMIT_VARIABLE_NUMBER 9 3464 #define SQLITE_LIMIT_TRIGGER_DEPTH 10 3465 #define SQLITE_LIMIT_WORKER_THREADS 11 3466 3467 3468 /* 3469 ** CAPI3REF: Compiling An SQL Statement 3470 ** KEYWORDS: {SQL statement compiler} 3471 ** METHOD: sqlite3 3472 ** CONSTRUCTOR: sqlite3_stmt 3473 ** 3474 ** To execute an SQL query, it must first be compiled into a byte-code 3475 ** program using one of these routines. 3476 ** 3477 ** The first argument, "db", is a [database connection] obtained from a 3478 ** prior successful call to [sqlite3_open()], [sqlite3_open_v2()] or 3479 ** [sqlite3_open16()]. The database connection must not have been closed. 3480 ** 3481 ** The second argument, "zSql", is the statement to be compiled, encoded 3482 ** as either UTF-8 or UTF-16. The sqlite3_prepare() and sqlite3_prepare_v2() 3483 ** interfaces use UTF-8, and sqlite3_prepare16() and sqlite3_prepare16_v2() 3484 ** use UTF-16. 3485 ** 3486 ** ^If the nByte argument is negative, then zSql is read up to the 3487 ** first zero terminator. ^If nByte is positive, then it is the 3488 ** number of bytes read from zSql. ^If nByte is zero, then no prepared 3489 ** statement is generated. 3490 ** If the caller knows that the supplied string is nul-terminated, then 3491 ** there is a small performance advantage to passing an nByte parameter that 3492 ** is the number of bytes in the input string <i>including</i> 3493 ** the nul-terminator. 3494 ** 3495 ** ^If pzTail is not NULL then *pzTail is made to point to the first byte 3496 ** past the end of the first SQL statement in zSql. These routines only 3497 ** compile the first statement in zSql, so *pzTail is left pointing to 3498 ** what remains uncompiled. 3499 ** 3500 ** ^*ppStmt is left pointing to a compiled [prepared statement] that can be 3501 ** executed using [sqlite3_step()]. ^If there is an error, *ppStmt is set 3502 ** to NULL. ^If the input text contains no SQL (if the input is an empty 3503 ** string or a comment) then *ppStmt is set to NULL. 3504 ** The calling procedure is responsible for deleting the compiled 3505 ** SQL statement using [sqlite3_finalize()] after it has finished with it. 3506 ** ppStmt may not be NULL. 3507 ** 3508 ** ^On success, the sqlite3_prepare() family of routines return [SQLITE_OK]; 3509 ** otherwise an [error code] is returned. 3510 ** 3511 ** The sqlite3_prepare_v2() and sqlite3_prepare16_v2() interfaces are 3512 ** recommended for all new programs. The two older interfaces are retained 3513 ** for backwards compatibility, but their use is discouraged. 3514 ** ^In the "v2" interfaces, the prepared statement 3515 ** that is returned (the [sqlite3_stmt] object) contains a copy of the 3516 ** original SQL text. This causes the [sqlite3_step()] interface to 3517 ** behave differently in three ways: 3518 ** 3519 ** <ol> 3520 ** <li> 3521 ** ^If the database schema changes, instead of returning [SQLITE_SCHEMA] as it 3522 ** always used to do, [sqlite3_step()] will automatically recompile the SQL 3523 ** statement and try to run it again. As many as [SQLITE_MAX_SCHEMA_RETRY] 3524 ** retries will occur before sqlite3_step() gives up and returns an error. 3525 ** </li> 3526 ** 3527 ** <li> 3528 ** ^When an error occurs, [sqlite3_step()] will return one of the detailed 3529 ** [error codes] or [extended error codes]. ^The legacy behavior was that 3530 ** [sqlite3_step()] would only return a generic [SQLITE_ERROR] result code 3531 ** and the application would have to make a second call to [sqlite3_reset()] 3532 ** in order to find the underlying cause of the problem. With the "v2" prepare 3533 ** interfaces, the underlying reason for the error is returned immediately. 3534 ** </li> 3535 ** 3536 ** <li> 3537 ** ^If the specific value bound to [parameter | host parameter] in the 3538 ** WHERE clause might influence the choice of query plan for a statement, 3539 ** then the statement will be automatically recompiled, as if there had been 3540 ** a schema change, on the first [sqlite3_step()] call following any change 3541 ** to the [sqlite3_bind_text | bindings] of that [parameter]. 3542 ** ^The specific value of WHERE-clause [parameter] might influence the 3543 ** choice of query plan if the parameter is the left-hand side of a [LIKE] 3544 ** or [GLOB] operator or if the parameter is compared to an indexed column 3545 ** and the [SQLITE_ENABLE_STAT3] compile-time option is enabled. 3546 ** </li> 3547 ** </ol> 3548 */ 3549 SQLITE_API int sqlite3_prepare( 3550 sqlite3 *db, /* Database handle */ 3551 const char *zSql, /* SQL statement, UTF-8 encoded */ 3552 int nByte, /* Maximum length of zSql in bytes. */ 3553 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 3554 const char **pzTail /* OUT: Pointer to unused portion of zSql */ 3555 ); 3556 SQLITE_API int sqlite3_prepare_v2( 3557 sqlite3 *db, /* Database handle */ 3558 const char *zSql, /* SQL statement, UTF-8 encoded */ 3559 int nByte, /* Maximum length of zSql in bytes. */ 3560 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 3561 const char **pzTail /* OUT: Pointer to unused portion of zSql */ 3562 ); 3563 SQLITE_API int sqlite3_prepare16( 3564 sqlite3 *db, /* Database handle */ 3565 const void *zSql, /* SQL statement, UTF-16 encoded */ 3566 int nByte, /* Maximum length of zSql in bytes. */ 3567 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 3568 const void **pzTail /* OUT: Pointer to unused portion of zSql */ 3569 ); 3570 SQLITE_API int sqlite3_prepare16_v2( 3571 sqlite3 *db, /* Database handle */ 3572 const void *zSql, /* SQL statement, UTF-16 encoded */ 3573 int nByte, /* Maximum length of zSql in bytes. */ 3574 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 3575 const void **pzTail /* OUT: Pointer to unused portion of zSql */ 3576 ); 3577 3578 /* 3579 ** CAPI3REF: Retrieving Statement SQL 3580 ** METHOD: sqlite3_stmt 3581 ** 3582 ** ^The sqlite3_sql(P) interface returns a pointer to a copy of the UTF-8 3583 ** SQL text used to create [prepared statement] P if P was 3584 ** created by either [sqlite3_prepare_v2()] or [sqlite3_prepare16_v2()]. 3585 ** ^The sqlite3_expanded_sql(P) interface returns a pointer to a UTF-8 3586 ** string containing the SQL text of prepared statement P with 3587 ** [bound parameters] expanded. 3588 ** 3589 ** ^(For example, if a prepared statement is created using the SQL 3590 ** text "SELECT $abc,:xyz" and if parameter $abc is bound to integer 2345 3591 ** and parameter :xyz is unbound, then sqlite3_sql() will return 3592 ** the original string, "SELECT $abc,:xyz" but sqlite3_expanded_sql() 3593 ** will return "SELECT 2345,NULL".)^ 3594 ** 3595 ** ^The sqlite3_expanded_sql() interface returns NULL if insufficient memory 3596 ** is available to hold the result, or if the result would exceed the 3597 ** the maximum string length determined by the [SQLITE_LIMIT_LENGTH]. 3598 ** 3599 ** ^The [SQLITE_TRACE_SIZE_LIMIT] compile-time option limits the size of 3600 ** bound parameter expansions. ^The [SQLITE_OMIT_TRACE] compile-time 3601 ** option causes sqlite3_expanded_sql() to always return NULL. 3602 ** 3603 ** ^The string returned by sqlite3_sql(P) is managed by SQLite and is 3604 ** automatically freed when the prepared statement is finalized. 3605 ** ^The string returned by sqlite3_expanded_sql(P), on the other hand, 3606 ** is obtained from [sqlite3_malloc()] and must be free by the application 3607 ** by passing it to [sqlite3_free()]. 3608 */ 3609 SQLITE_API const char *sqlite3_sql(sqlite3_stmt *pStmt); 3610 SQLITE_API char *sqlite3_expanded_sql(sqlite3_stmt *pStmt); 3611 3612 /* 3613 ** CAPI3REF: Determine If An SQL Statement Writes The Database 3614 ** METHOD: sqlite3_stmt 3615 ** 3616 ** ^The sqlite3_stmt_readonly(X) interface returns true (non-zero) if 3617 ** and only if the [prepared statement] X makes no direct changes to 3618 ** the content of the database file. 3619 ** 3620 ** Note that [application-defined SQL functions] or 3621 ** [virtual tables] might change the database indirectly as a side effect. 3622 ** ^(For example, if an application defines a function "eval()" that 3623 ** calls [sqlite3_exec()], then the following SQL statement would 3624 ** change the database file through side-effects: 3625 ** 3626 ** <blockquote><pre> 3627 ** SELECT eval('DELETE FROM t1') FROM t2; 3628 ** </pre></blockquote> 3629 ** 3630 ** But because the [SELECT] statement does not change the database file 3631 ** directly, sqlite3_stmt_readonly() would still return true.)^ 3632 ** 3633 ** ^Transaction control statements such as [BEGIN], [COMMIT], [ROLLBACK], 3634 ** [SAVEPOINT], and [RELEASE] cause sqlite3_stmt_readonly() to return true, 3635 ** since the statements themselves do not actually modify the database but 3636 ** rather they control the timing of when other statements modify the 3637 ** database. ^The [ATTACH] and [DETACH] statements also cause 3638 ** sqlite3_stmt_readonly() to return true since, while those statements 3639 ** change the configuration of a database connection, they do not make 3640 ** changes to the content of the database files on disk. 3641 ** ^The sqlite3_stmt_readonly() interface returns true for [BEGIN] since 3642 ** [BEGIN] merely sets internal flags, but the [BEGIN|BEGIN IMMEDIATE] and 3643 ** [BEGIN|BEGIN EXCLUSIVE] commands do touch the database and so 3644 ** sqlite3_stmt_readonly() returns false for those commands. 3645 */ 3646 SQLITE_API int sqlite3_stmt_readonly(sqlite3_stmt *pStmt); 3647 3648 /* 3649 ** CAPI3REF: Determine If A Prepared Statement Has Been Reset 3650 ** METHOD: sqlite3_stmt 3651 ** 3652 ** ^The sqlite3_stmt_busy(S) interface returns true (non-zero) if the 3653 ** [prepared statement] S has been stepped at least once using 3654 ** [sqlite3_step(S)] but has neither run to completion (returned 3655 ** [SQLITE_DONE] from [sqlite3_step(S)]) nor 3656 ** been reset using [sqlite3_reset(S)]. ^The sqlite3_stmt_busy(S) 3657 ** interface returns false if S is a NULL pointer. If S is not a 3658 ** NULL pointer and is not a pointer to a valid [prepared statement] 3659 ** object, then the behavior is undefined and probably undesirable. 3660 ** 3661 ** This interface can be used in combination [sqlite3_next_stmt()] 3662 ** to locate all prepared statements associated with a database 3663 ** connection that are in need of being reset. This can be used, 3664 ** for example, in diagnostic routines to search for prepared 3665 ** statements that are holding a transaction open. 3666 */ 3667 SQLITE_API int sqlite3_stmt_busy(sqlite3_stmt*); 3668 3669 /* 3670 ** CAPI3REF: Dynamically Typed Value Object 3671 ** KEYWORDS: {protected sqlite3_value} {unprotected sqlite3_value} 3672 ** 3673 ** SQLite uses the sqlite3_value object to represent all values 3674 ** that can be stored in a database table. SQLite uses dynamic typing 3675 ** for the values it stores. ^Values stored in sqlite3_value objects 3676 ** can be integers, floating point values, strings, BLOBs, or NULL. 3677 ** 3678 ** An sqlite3_value object may be either "protected" or "unprotected". 3679 ** Some interfaces require a protected sqlite3_value. Other interfaces 3680 ** will accept either a protected or an unprotected sqlite3_value. 3681 ** Every interface that accepts sqlite3_value arguments specifies 3682 ** whether or not it requires a protected sqlite3_value. The 3683 ** [sqlite3_value_dup()] interface can be used to construct a new 3684 ** protected sqlite3_value from an unprotected sqlite3_value. 3685 ** 3686 ** The terms "protected" and "unprotected" refer to whether or not 3687 ** a mutex is held. An internal mutex is held for a protected 3688 ** sqlite3_value object but no mutex is held for an unprotected 3689 ** sqlite3_value object. If SQLite is compiled to be single-threaded 3690 ** (with [SQLITE_THREADSAFE=0] and with [sqlite3_threadsafe()] returning 0) 3691 ** or if SQLite is run in one of reduced mutex modes 3692 ** [SQLITE_CONFIG_SINGLETHREAD] or [SQLITE_CONFIG_MULTITHREAD] 3693 ** then there is no distinction between protected and unprotected 3694 ** sqlite3_value objects and they can be used interchangeably. However, 3695 ** for maximum code portability it is recommended that applications 3696 ** still make the distinction between protected and unprotected 3697 ** sqlite3_value objects even when not strictly required. 3698 ** 3699 ** ^The sqlite3_value objects that are passed as parameters into the 3700 ** implementation of [application-defined SQL functions] are protected. 3701 ** ^The sqlite3_value object returned by 3702 ** [sqlite3_column_value()] is unprotected. 3703 ** Unprotected sqlite3_value objects may only be used with 3704 ** [sqlite3_result_value()] and [sqlite3_bind_value()]. 3705 ** The [sqlite3_value_blob | sqlite3_value_type()] family of 3706 ** interfaces require protected sqlite3_value objects. 3707 */ 3708 typedef struct Mem sqlite3_value; 3709 3710 /* 3711 ** CAPI3REF: SQL Function Context Object 3712 ** 3713 ** The context in which an SQL function executes is stored in an 3714 ** sqlite3_context object. ^A pointer to an sqlite3_context object 3715 ** is always first parameter to [application-defined SQL functions]. 3716 ** The application-defined SQL function implementation will pass this 3717 ** pointer through into calls to [sqlite3_result_int | sqlite3_result()], 3718 ** [sqlite3_aggregate_context()], [sqlite3_user_data()], 3719 ** [sqlite3_context_db_handle()], [sqlite3_get_auxdata()], 3720 ** and/or [sqlite3_set_auxdata()]. 3721 */ 3722 typedef struct sqlite3_context sqlite3_context; 3723 3724 /* 3725 ** CAPI3REF: Binding Values To Prepared Statements 3726 ** KEYWORDS: {host parameter} {host parameters} {host parameter name} 3727 ** KEYWORDS: {SQL parameter} {SQL parameters} {parameter binding} 3728 ** METHOD: sqlite3_stmt 3729 ** 3730 ** ^(In the SQL statement text input to [sqlite3_prepare_v2()] and its variants, 3731 ** literals may be replaced by a [parameter] that matches one of following 3732 ** templates: 3733 ** 3734 ** <ul> 3735 ** <li> ? 3736 ** <li> ?NNN 3737 ** <li> :VVV 3738 ** <li> @VVV 3739 ** <li> $VVV 3740 ** </ul> 3741 ** 3742 ** In the templates above, NNN represents an integer literal, 3743 ** and VVV represents an alphanumeric identifier.)^ ^The values of these 3744 ** parameters (also called "host parameter names" or "SQL parameters") 3745 ** can be set using the sqlite3_bind_*() routines defined here. 3746 ** 3747 ** ^The first argument to the sqlite3_bind_*() routines is always 3748 ** a pointer to the [sqlite3_stmt] object returned from 3749 ** [sqlite3_prepare_v2()] or its variants. 3750 ** 3751 ** ^The second argument is the index of the SQL parameter to be set. 3752 ** ^The leftmost SQL parameter has an index of 1. ^When the same named 3753 ** SQL parameter is used more than once, second and subsequent 3754 ** occurrences have the same index as the first occurrence. 3755 ** ^The index for named parameters can be looked up using the 3756 ** [sqlite3_bind_parameter_index()] API if desired. ^The index 3757 ** for "?NNN" parameters is the value of NNN. 3758 ** ^The NNN value must be between 1 and the [sqlite3_limit()] 3759 ** parameter [SQLITE_LIMIT_VARIABLE_NUMBER] (default value: 999). 3760 ** 3761 ** ^The third argument is the value to bind to the parameter. 3762 ** ^If the third parameter to sqlite3_bind_text() or sqlite3_bind_text16() 3763 ** or sqlite3_bind_blob() is a NULL pointer then the fourth parameter 3764 ** is ignored and the end result is the same as sqlite3_bind_null(). 3765 ** 3766 ** ^(In those routines that have a fourth argument, its value is the 3767 ** number of bytes in the parameter. To be clear: the value is the 3768 ** number of <u>bytes</u> in the value, not the number of characters.)^ 3769 ** ^If the fourth parameter to sqlite3_bind_text() or sqlite3_bind_text16() 3770 ** is negative, then the length of the string is 3771 ** the number of bytes up to the first zero terminator. 3772 ** If the fourth parameter to sqlite3_bind_blob() is negative, then 3773 ** the behavior is undefined. 3774 ** If a non-negative fourth parameter is provided to sqlite3_bind_text() 3775 ** or sqlite3_bind_text16() or sqlite3_bind_text64() then 3776 ** that parameter must be the byte offset 3777 ** where the NUL terminator would occur assuming the string were NUL 3778 ** terminated. If any NUL characters occur at byte offsets less than 3779 ** the value of the fourth parameter then the resulting string value will 3780 ** contain embedded NULs. The result of expressions involving strings 3781 ** with embedded NULs is undefined. 3782 ** 3783 ** ^The fifth argument to the BLOB and string binding interfaces 3784 ** is a destructor used to dispose of the BLOB or 3785 ** string after SQLite has finished with it. ^The destructor is called 3786 ** to dispose of the BLOB or string even if the call to bind API fails. 3787 ** ^If the fifth argument is 3788 ** the special value [SQLITE_STATIC], then SQLite assumes that the 3789 ** information is in static, unmanaged space and does not need to be freed. 3790 ** ^If the fifth argument has the value [SQLITE_TRANSIENT], then 3791 ** SQLite makes its own private copy of the data immediately, before 3792 ** the sqlite3_bind_*() routine returns. 3793 ** 3794 ** ^The sixth argument to sqlite3_bind_text64() must be one of 3795 ** [SQLITE_UTF8], [SQLITE_UTF16], [SQLITE_UTF16BE], or [SQLITE_UTF16LE] 3796 ** to specify the encoding of the text in the third parameter. If 3797 ** the sixth argument to sqlite3_bind_text64() is not one of the 3798 ** allowed values shown above, or if the text encoding is different 3799 ** from the encoding specified by the sixth parameter, then the behavior 3800 ** is undefined. 3801 ** 3802 ** ^The sqlite3_bind_zeroblob() routine binds a BLOB of length N that 3803 ** is filled with zeroes. ^A zeroblob uses a fixed amount of memory 3804 ** (just an integer to hold its size) while it is being processed. 3805 ** Zeroblobs are intended to serve as placeholders for BLOBs whose 3806 ** content is later written using 3807 ** [sqlite3_blob_open | incremental BLOB I/O] routines. 3808 ** ^A negative value for the zeroblob results in a zero-length BLOB. 3809 ** 3810 ** ^If any of the sqlite3_bind_*() routines are called with a NULL pointer 3811 ** for the [prepared statement] or with a prepared statement for which 3812 ** [sqlite3_step()] has been called more recently than [sqlite3_reset()], 3813 ** then the call will return [SQLITE_MISUSE]. If any sqlite3_bind_() 3814 ** routine is passed a [prepared statement] that has been finalized, the 3815 ** result is undefined and probably harmful. 3816 ** 3817 ** ^Bindings are not cleared by the [sqlite3_reset()] routine. 3818 ** ^Unbound parameters are interpreted as NULL. 3819 ** 3820 ** ^The sqlite3_bind_* routines return [SQLITE_OK] on success or an 3821 ** [error code] if anything goes wrong. 3822 ** ^[SQLITE_TOOBIG] might be returned if the size of a string or BLOB 3823 ** exceeds limits imposed by [sqlite3_limit]([SQLITE_LIMIT_LENGTH]) or 3824 ** [SQLITE_MAX_LENGTH]. 3825 ** ^[SQLITE_RANGE] is returned if the parameter 3826 ** index is out of range. ^[SQLITE_NOMEM] is returned if malloc() fails. 3827 ** 3828 ** See also: [sqlite3_bind_parameter_count()], 3829 ** [sqlite3_bind_parameter_name()], and [sqlite3_bind_parameter_index()]. 3830 */ 3831 SQLITE_API int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*)); 3832 SQLITE_API int sqlite3_bind_blob64(sqlite3_stmt*, int, const void*, sqlite3_uint64, 3833 void(*)(void*)); 3834 SQLITE_API int sqlite3_bind_double(sqlite3_stmt*, int, double); 3835 SQLITE_API int sqlite3_bind_int(sqlite3_stmt*, int, int); 3836 SQLITE_API int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite3_int64); 3837 SQLITE_API int sqlite3_bind_null(sqlite3_stmt*, int); 3838 SQLITE_API int sqlite3_bind_text(sqlite3_stmt*,int,const char*,int,void(*)(void*)); 3839 SQLITE_API int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*)); 3840 SQLITE_API int sqlite3_bind_text64(sqlite3_stmt*, int, const char*, sqlite3_uint64, 3841 void(*)(void*), unsigned char encoding); 3842 SQLITE_API int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*); 3843 SQLITE_API int sqlite3_bind_zeroblob(sqlite3_stmt*, int, int n); 3844 SQLITE_API int sqlite3_bind_zeroblob64(sqlite3_stmt*, int, sqlite3_uint64); 3845 3846 /* 3847 ** CAPI3REF: Number Of SQL Parameters 3848 ** METHOD: sqlite3_stmt 3849 ** 3850 ** ^This routine can be used to find the number of [SQL parameters] 3851 ** in a [prepared statement]. SQL parameters are tokens of the 3852 ** form "?", "?NNN", ":AAA", "$AAA", or "@AAA" that serve as 3853 ** placeholders for values that are [sqlite3_bind_blob | bound] 3854 ** to the parameters at a later time. 3855 ** 3856 ** ^(This routine actually returns the index of the largest (rightmost) 3857 ** parameter. For all forms except ?NNN, this will correspond to the 3858 ** number of unique parameters. If parameters of the ?NNN form are used, 3859 ** there may be gaps in the list.)^ 3860 ** 3861 ** See also: [sqlite3_bind_blob|sqlite3_bind()], 3862 ** [sqlite3_bind_parameter_name()], and 3863 ** [sqlite3_bind_parameter_index()]. 3864 */ 3865 SQLITE_API int sqlite3_bind_parameter_count(sqlite3_stmt*); 3866 3867 /* 3868 ** CAPI3REF: Name Of A Host Parameter 3869 ** METHOD: sqlite3_stmt 3870 ** 3871 ** ^The sqlite3_bind_parameter_name(P,N) interface returns 3872 ** the name of the N-th [SQL parameter] in the [prepared statement] P. 3873 ** ^(SQL parameters of the form "?NNN" or ":AAA" or "@AAA" or "$AAA" 3874 ** have a name which is the string "?NNN" or ":AAA" or "@AAA" or "$AAA" 3875 ** respectively. 3876 ** In other words, the initial ":" or "$" or "@" or "?" 3877 ** is included as part of the name.)^ 3878 ** ^Parameters of the form "?" without a following integer have no name 3879 ** and are referred to as "nameless" or "anonymous parameters". 3880 ** 3881 ** ^The first host parameter has an index of 1, not 0. 3882 ** 3883 ** ^If the value N is out of range or if the N-th parameter is 3884 ** nameless, then NULL is returned. ^The returned string is 3885 ** always in UTF-8 encoding even if the named parameter was 3886 ** originally specified as UTF-16 in [sqlite3_prepare16()] or 3887 ** [sqlite3_prepare16_v2()]. 3888 ** 3889 ** See also: [sqlite3_bind_blob|sqlite3_bind()], 3890 ** [sqlite3_bind_parameter_count()], and 3891 ** [sqlite3_bind_parameter_index()]. 3892 */ 3893 SQLITE_API const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int); 3894 3895 /* 3896 ** CAPI3REF: Index Of A Parameter With A Given Name 3897 ** METHOD: sqlite3_stmt 3898 ** 3899 ** ^Return the index of an SQL parameter given its name. ^The 3900 ** index value returned is suitable for use as the second 3901 ** parameter to [sqlite3_bind_blob|sqlite3_bind()]. ^A zero 3902 ** is returned if no matching parameter is found. ^The parameter 3903 ** name must be given in UTF-8 even if the original statement 3904 ** was prepared from UTF-16 text using [sqlite3_prepare16_v2()]. 3905 ** 3906 ** See also: [sqlite3_bind_blob|sqlite3_bind()], 3907 ** [sqlite3_bind_parameter_count()], and 3908 ** [sqlite3_bind_parameter_name()]. 3909 */ 3910 SQLITE_API int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName); 3911 3912 /* 3913 ** CAPI3REF: Reset All Bindings On A Prepared Statement 3914 ** METHOD: sqlite3_stmt 3915 ** 3916 ** ^Contrary to the intuition of many, [sqlite3_reset()] does not reset 3917 ** the [sqlite3_bind_blob | bindings] on a [prepared statement]. 3918 ** ^Use this routine to reset all host parameters to NULL. 3919 */ 3920 SQLITE_API int sqlite3_clear_bindings(sqlite3_stmt*); 3921 3922 /* 3923 ** CAPI3REF: Number Of Columns In A Result Set 3924 ** METHOD: sqlite3_stmt 3925 ** 3926 ** ^Return the number of columns in the result set returned by the 3927 ** [prepared statement]. ^If this routine returns 0, that means the 3928 ** [prepared statement] returns no data (for example an [UPDATE]). 3929 ** ^However, just because this routine returns a positive number does not 3930 ** mean that one or more rows of data will be returned. ^A SELECT statement 3931 ** will always have a positive sqlite3_column_count() but depending on the 3932 ** WHERE clause constraints and the table content, it might return no rows. 3933 ** 3934 ** See also: [sqlite3_data_count()] 3935 */ 3936 SQLITE_API int sqlite3_column_count(sqlite3_stmt *pStmt); 3937 3938 /* 3939 ** CAPI3REF: Column Names In A Result Set 3940 ** METHOD: sqlite3_stmt 3941 ** 3942 ** ^These routines return the name assigned to a particular column 3943 ** in the result set of a [SELECT] statement. ^The sqlite3_column_name() 3944 ** interface returns a pointer to a zero-terminated UTF-8 string 3945 ** and sqlite3_column_name16() returns a pointer to a zero-terminated 3946 ** UTF-16 string. ^The first parameter is the [prepared statement] 3947 ** that implements the [SELECT] statement. ^The second parameter is the 3948 ** column number. ^The leftmost column is number 0. 3949 ** 3950 ** ^The returned string pointer is valid until either the [prepared statement] 3951 ** is destroyed by [sqlite3_finalize()] or until the statement is automatically 3952 ** reprepared by the first call to [sqlite3_step()] for a particular run 3953 ** or until the next call to 3954 ** sqlite3_column_name() or sqlite3_column_name16() on the same column. 3955 ** 3956 ** ^If sqlite3_malloc() fails during the processing of either routine 3957 ** (for example during a conversion from UTF-8 to UTF-16) then a 3958 ** NULL pointer is returned. 3959 ** 3960 ** ^The name of a result column is the value of the "AS" clause for 3961 ** that column, if there is an AS clause. If there is no AS clause 3962 ** then the name of the column is unspecified and may change from 3963 ** one release of SQLite to the next. 3964 */ 3965 SQLITE_API const char *sqlite3_column_name(sqlite3_stmt*, int N); 3966 SQLITE_API const void *sqlite3_column_name16(sqlite3_stmt*, int N); 3967 3968 /* 3969 ** CAPI3REF: Source Of Data In A Query Result 3970 ** METHOD: sqlite3_stmt 3971 ** 3972 ** ^These routines provide a means to determine the database, table, and 3973 ** table column that is the origin of a particular result column in 3974 ** [SELECT] statement. 3975 ** ^The name of the database or table or column can be returned as 3976 ** either a UTF-8 or UTF-16 string. ^The _database_ routines return 3977 ** the database name, the _table_ routines return the table name, and 3978 ** the origin_ routines return the column name. 3979 ** ^The returned string is valid until the [prepared statement] is destroyed 3980 ** using [sqlite3_finalize()] or until the statement is automatically 3981 ** reprepared by the first call to [sqlite3_step()] for a particular run 3982 ** or until the same information is requested 3983 ** again in a different encoding. 3984 ** 3985 ** ^The names returned are the original un-aliased names of the 3986 ** database, table, and column. 3987 ** 3988 ** ^The first argument to these interfaces is a [prepared statement]. 3989 ** ^These functions return information about the Nth result column returned by 3990 ** the statement, where N is the second function argument. 3991 ** ^The left-most column is column 0 for these routines. 3992 ** 3993 ** ^If the Nth column returned by the statement is an expression or 3994 ** subquery and is not a column value, then all of these functions return 3995 ** NULL. ^These routine might also return NULL if a memory allocation error 3996 ** occurs. ^Otherwise, they return the name of the attached database, table, 3997 ** or column that query result column was extracted from. 3998 ** 3999 ** ^As with all other SQLite APIs, those whose names end with "16" return 4000 ** UTF-16 encoded strings and the other functions return UTF-8. 4001 ** 4002 ** ^These APIs are only available if the library was compiled with the 4003 ** [SQLITE_ENABLE_COLUMN_METADATA] C-preprocessor symbol. 4004 ** 4005 ** If two or more threads call one or more of these routines against the same 4006 ** prepared statement and column at the same time then the results are 4007 ** undefined. 4008 ** 4009 ** If two or more threads call one or more 4010 ** [sqlite3_column_database_name | column metadata interfaces] 4011 ** for the same [prepared statement] and result column 4012 ** at the same time then the results are undefined. 4013 */ 4014 SQLITE_API const char *sqlite3_column_database_name(sqlite3_stmt*,int); 4015 SQLITE_API const void *sqlite3_column_database_name16(sqlite3_stmt*,int); 4016 SQLITE_API const char *sqlite3_column_table_name(sqlite3_stmt*,int); 4017 SQLITE_API const void *sqlite3_column_table_name16(sqlite3_stmt*,int); 4018 SQLITE_API const char *sqlite3_column_origin_name(sqlite3_stmt*,int); 4019 SQLITE_API const void *sqlite3_column_origin_name16(sqlite3_stmt*,int); 4020 4021 /* 4022 ** CAPI3REF: Declared Datatype Of A Query Result 4023 ** METHOD: sqlite3_stmt 4024 ** 4025 ** ^(The first parameter is a [prepared statement]. 4026 ** If this statement is a [SELECT] statement and the Nth column of the 4027 ** returned result set of that [SELECT] is a table column (not an 4028 ** expression or subquery) then the declared type of the table 4029 ** column is returned.)^ ^If the Nth column of the result set is an 4030 ** expression or subquery, then a NULL pointer is returned. 4031 ** ^The returned string is always UTF-8 encoded. 4032 ** 4033 ** ^(For example, given the database schema: 4034 ** 4035 ** CREATE TABLE t1(c1 VARIANT); 4036 ** 4037 ** and the following statement to be compiled: 4038 ** 4039 ** SELECT c1 + 1, c1 FROM t1; 4040 ** 4041 ** this routine would return the string "VARIANT" for the second result 4042 ** column (i==1), and a NULL pointer for the first result column (i==0).)^ 4043 ** 4044 ** ^SQLite uses dynamic run-time typing. ^So just because a column 4045 ** is declared to contain a particular type does not mean that the 4046 ** data stored in that column is of the declared type. SQLite is 4047 ** strongly typed, but the typing is dynamic not static. ^Type 4048 ** is associated with individual values, not with the containers 4049 ** used to hold those values. 4050 */ 4051 SQLITE_API const char *sqlite3_column_decltype(sqlite3_stmt*,int); 4052 SQLITE_API const void *sqlite3_column_decltype16(sqlite3_stmt*,int); 4053 4054 /* 4055 ** CAPI3REF: Evaluate An SQL Statement 4056 ** METHOD: sqlite3_stmt 4057 ** 4058 ** After a [prepared statement] has been prepared using either 4059 ** [sqlite3_prepare_v2()] or [sqlite3_prepare16_v2()] or one of the legacy 4060 ** interfaces [sqlite3_prepare()] or [sqlite3_prepare16()], this function 4061 ** must be called one or more times to evaluate the statement. 4062 ** 4063 ** The details of the behavior of the sqlite3_step() interface depend 4064 ** on whether the statement was prepared using the newer "v2" interface 4065 ** [sqlite3_prepare_v2()] and [sqlite3_prepare16_v2()] or the older legacy 4066 ** interface [sqlite3_prepare()] and [sqlite3_prepare16()]. The use of the 4067 ** new "v2" interface is recommended for new applications but the legacy 4068 ** interface will continue to be supported. 4069 ** 4070 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY], 4071 ** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE]. 4072 ** ^With the "v2" interface, any of the other [result codes] or 4073 ** [extended result codes] might be returned as well. 4074 ** 4075 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the 4076 ** database locks it needs to do its job. ^If the statement is a [COMMIT] 4077 ** or occurs outside of an explicit transaction, then you can retry the 4078 ** statement. If the statement is not a [COMMIT] and occurs within an 4079 ** explicit transaction then you should rollback the transaction before 4080 ** continuing. 4081 ** 4082 ** ^[SQLITE_DONE] means that the statement has finished executing 4083 ** successfully. sqlite3_step() should not be called again on this virtual 4084 ** machine without first calling [sqlite3_reset()] to reset the virtual 4085 ** machine back to its initial state. 4086 ** 4087 ** ^If the SQL statement being executed returns any data, then [SQLITE_ROW] 4088 ** is returned each time a new row of data is ready for processing by the 4089 ** caller. The values may be accessed using the [column access functions]. 4090 ** sqlite3_step() is called again to retrieve the next row of data. 4091 ** 4092 ** ^[SQLITE_ERROR] means that a run-time error (such as a constraint 4093 ** violation) has occurred. sqlite3_step() should not be called again on 4094 ** the VM. More information may be found by calling [sqlite3_errmsg()]. 4095 ** ^With the legacy interface, a more specific error code (for example, 4096 ** [SQLITE_INTERRUPT], [SQLITE_SCHEMA], [SQLITE_CORRUPT], and so forth) 4097 ** can be obtained by calling [sqlite3_reset()] on the 4098 ** [prepared statement]. ^In the "v2" interface, 4099 ** the more specific error code is returned directly by sqlite3_step(). 4100 ** 4101 ** [SQLITE_MISUSE] means that the this routine was called inappropriately. 4102 ** Perhaps it was called on a [prepared statement] that has 4103 ** already been [sqlite3_finalize | finalized] or on one that had 4104 ** previously returned [SQLITE_ERROR] or [SQLITE_DONE]. Or it could 4105 ** be the case that the same database connection is being used by two or 4106 ** more threads at the same moment in time. 4107 ** 4108 ** For all versions of SQLite up to and including 3.6.23.1, a call to 4109 ** [sqlite3_reset()] was required after sqlite3_step() returned anything 4110 ** other than [SQLITE_ROW] before any subsequent invocation of 4111 ** sqlite3_step(). Failure to reset the prepared statement using 4112 ** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from 4113 ** sqlite3_step(). But after [version 3.6.23.1] ([dateof:3.6.23.1], 4114 ** sqlite3_step() began 4115 ** calling [sqlite3_reset()] automatically in this circumstance rather 4116 ** than returning [SQLITE_MISUSE]. This is not considered a compatibility 4117 ** break because any application that ever receives an SQLITE_MISUSE error 4118 ** is broken by definition. The [SQLITE_OMIT_AUTORESET] compile-time option 4119 ** can be used to restore the legacy behavior. 4120 ** 4121 ** <b>Goofy Interface Alert:</b> In the legacy interface, the sqlite3_step() 4122 ** API always returns a generic error code, [SQLITE_ERROR], following any 4123 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call 4124 ** [sqlite3_reset()] or [sqlite3_finalize()] in order to find one of the 4125 ** specific [error codes] that better describes the error. 4126 ** We admit that this is a goofy design. The problem has been fixed 4127 ** with the "v2" interface. If you prepare all of your SQL statements 4128 ** using either [sqlite3_prepare_v2()] or [sqlite3_prepare16_v2()] instead 4129 ** of the legacy [sqlite3_prepare()] and [sqlite3_prepare16()] interfaces, 4130 ** then the more specific [error codes] are returned directly 4131 ** by sqlite3_step(). The use of the "v2" interface is recommended. 4132 */ 4133 SQLITE_API int sqlite3_step(sqlite3_stmt*); 4134 4135 /* 4136 ** CAPI3REF: Number of columns in a result set 4137 ** METHOD: sqlite3_stmt 4138 ** 4139 ** ^The sqlite3_data_count(P) interface returns the number of columns in the 4140 ** current row of the result set of [prepared statement] P. 4141 ** ^If prepared statement P does not have results ready to return 4142 ** (via calls to the [sqlite3_column_int | sqlite3_column_*()] of 4143 ** interfaces) then sqlite3_data_count(P) returns 0. 4144 ** ^The sqlite3_data_count(P) routine also returns 0 if P is a NULL pointer. 4145 ** ^The sqlite3_data_count(P) routine returns 0 if the previous call to 4146 ** [sqlite3_step](P) returned [SQLITE_DONE]. ^The sqlite3_data_count(P) 4147 ** will return non-zero if previous call to [sqlite3_step](P) returned 4148 ** [SQLITE_ROW], except in the case of the [PRAGMA incremental_vacuum] 4149 ** where it always returns zero since each step of that multi-step 4150 ** pragma returns 0 columns of data. 4151 ** 4152 ** See also: [sqlite3_column_count()] 4153 */ 4154 SQLITE_API int sqlite3_data_count(sqlite3_stmt *pStmt); 4155 4156 /* 4157 ** CAPI3REF: Fundamental Datatypes 4158 ** KEYWORDS: SQLITE_TEXT 4159 ** 4160 ** ^(Every value in SQLite has one of five fundamental datatypes: 4161 ** 4162 ** <ul> 4163 ** <li> 64-bit signed integer 4164 ** <li> 64-bit IEEE floating point number 4165 ** <li> string 4166 ** <li> BLOB 4167 ** <li> NULL 4168 ** </ul>)^ 4169 ** 4170 ** These constants are codes for each of those types. 4171 ** 4172 ** Note that the SQLITE_TEXT constant was also used in SQLite version 2 4173 ** for a completely different meaning. Software that links against both 4174 ** SQLite version 2 and SQLite version 3 should use SQLITE3_TEXT, not 4175 ** SQLITE_TEXT. 4176 */ 4177 #define SQLITE_INTEGER 1 4178 #define SQLITE_FLOAT 2 4179 #define SQLITE_BLOB 4 4180 #define SQLITE_NULL 5 4181 #ifdef SQLITE_TEXT 4182 # undef SQLITE_TEXT 4183 #else 4184 # define SQLITE_TEXT 3 4185 #endif 4186 #define SQLITE3_TEXT 3 4187 4188 /* 4189 ** CAPI3REF: Result Values From A Query 4190 ** KEYWORDS: {column access functions} 4191 ** METHOD: sqlite3_stmt 4192 ** 4193 ** ^These routines return information about a single column of the current 4194 ** result row of a query. ^In every case the first argument is a pointer 4195 ** to the [prepared statement] that is being evaluated (the [sqlite3_stmt*] 4196 ** that was returned from [sqlite3_prepare_v2()] or one of its variants) 4197 ** and the second argument is the index of the column for which information 4198 ** should be returned. ^The leftmost column of the result set has the index 0. 4199 ** ^The number of columns in the result can be determined using 4200 ** [sqlite3_column_count()]. 4201 ** 4202 ** If the SQL statement does not currently point to a valid row, or if the 4203 ** column index is out of range, the result is undefined. 4204 ** These routines may only be called when the most recent call to 4205 ** [sqlite3_step()] has returned [SQLITE_ROW] and neither 4206 ** [sqlite3_reset()] nor [sqlite3_finalize()] have been called subsequently. 4207 ** If any of these routines are called after [sqlite3_reset()] or 4208 ** [sqlite3_finalize()] or after [sqlite3_step()] has returned 4209 ** something other than [SQLITE_ROW], the results are undefined. 4210 ** If [sqlite3_step()] or [sqlite3_reset()] or [sqlite3_finalize()] 4211 ** are called from a different thread while any of these routines 4212 ** are pending, then the results are undefined. 4213 ** 4214 ** ^The sqlite3_column_type() routine returns the 4215 ** [SQLITE_INTEGER | datatype code] for the initial data type 4216 ** of the result column. ^The returned value is one of [SQLITE_INTEGER], 4217 ** [SQLITE_FLOAT], [SQLITE_TEXT], [SQLITE_BLOB], or [SQLITE_NULL]. The value 4218 ** returned by sqlite3_column_type() is only meaningful if no type 4219 ** conversions have occurred as described below. After a type conversion, 4220 ** the value returned by sqlite3_column_type() is undefined. Future 4221 ** versions of SQLite may change the behavior of sqlite3_column_type() 4222 ** following a type conversion. 4223 ** 4224 ** ^If the result is a BLOB or UTF-8 string then the sqlite3_column_bytes() 4225 ** routine returns the number of bytes in that BLOB or string. 4226 ** ^If the result is a UTF-16 string, then sqlite3_column_bytes() converts 4227 ** the string to UTF-8 and then returns the number of bytes. 4228 ** ^If the result is a numeric value then sqlite3_column_bytes() uses 4229 ** [sqlite3_snprintf()] to convert that value to a UTF-8 string and returns 4230 ** the number of bytes in that string. 4231 ** ^If the result is NULL, then sqlite3_column_bytes() returns zero. 4232 ** 4233 ** ^If the result is a BLOB or UTF-16 string then the sqlite3_column_bytes16() 4234 ** routine returns the number of bytes in that BLOB or string. 4235 ** ^If the result is a UTF-8 string, then sqlite3_column_bytes16() converts 4236 ** the string to UTF-16 and then returns the number of bytes. 4237 ** ^If the result is a numeric value then sqlite3_column_bytes16() uses 4238 ** [sqlite3_snprintf()] to convert that value to a UTF-16 string and returns 4239 ** the number of bytes in that string. 4240 ** ^If the result is NULL, then sqlite3_column_bytes16() returns zero. 4241 ** 4242 ** ^The values returned by [sqlite3_column_bytes()] and 4243 ** [sqlite3_column_bytes16()] do not include the zero terminators at the end 4244 ** of the string. ^For clarity: the values returned by 4245 ** [sqlite3_column_bytes()] and [sqlite3_column_bytes16()] are the number of 4246 ** bytes in the string, not the number of characters. 4247 ** 4248 ** ^Strings returned by sqlite3_column_text() and sqlite3_column_text16(), 4249 ** even empty strings, are always zero-terminated. ^The return 4250 ** value from sqlite3_column_blob() for a zero-length BLOB is a NULL pointer. 4251 ** 4252 ** <b>Warning:</b> ^The object returned by [sqlite3_column_value()] is an 4253 ** [unprotected sqlite3_value] object. In a multithreaded environment, 4254 ** an unprotected sqlite3_value object may only be used safely with 4255 ** [sqlite3_bind_value()] and [sqlite3_result_value()]. 4256 ** If the [unprotected sqlite3_value] object returned by 4257 ** [sqlite3_column_value()] is used in any other way, including calls 4258 ** to routines like [sqlite3_value_int()], [sqlite3_value_text()], 4259 ** or [sqlite3_value_bytes()], the behavior is not threadsafe. 4260 ** 4261 ** These routines attempt to convert the value where appropriate. ^For 4262 ** example, if the internal representation is FLOAT and a text result 4263 ** is requested, [sqlite3_snprintf()] is used internally to perform the 4264 ** conversion automatically. ^(The following table details the conversions 4265 ** that are applied: 4266 ** 4267 ** <blockquote> 4268 ** <table border="1"> 4269 ** <tr><th> Internal<br>Type <th> Requested<br>Type <th> Conversion 4270 ** 4271 ** <tr><td> NULL <td> INTEGER <td> Result is 0 4272 ** <tr><td> NULL <td> FLOAT <td> Result is 0.0 4273 ** <tr><td> NULL <td> TEXT <td> Result is a NULL pointer 4274 ** <tr><td> NULL <td> BLOB <td> Result is a NULL pointer 4275 ** <tr><td> INTEGER <td> FLOAT <td> Convert from integer to float 4276 ** <tr><td> INTEGER <td> TEXT <td> ASCII rendering of the integer 4277 ** <tr><td> INTEGER <td> BLOB <td> Same as INTEGER->TEXT 4278 ** <tr><td> FLOAT <td> INTEGER <td> [CAST] to INTEGER 4279 ** <tr><td> FLOAT <td> TEXT <td> ASCII rendering of the float 4280 ** <tr><td> FLOAT <td> BLOB <td> [CAST] to BLOB 4281 ** <tr><td> TEXT <td> INTEGER <td> [CAST] to INTEGER 4282 ** <tr><td> TEXT <td> FLOAT <td> [CAST] to REAL 4283 ** <tr><td> TEXT <td> BLOB <td> No change 4284 ** <tr><td> BLOB <td> INTEGER <td> [CAST] to INTEGER 4285 ** <tr><td> BLOB <td> FLOAT <td> [CAST] to REAL 4286 ** <tr><td> BLOB <td> TEXT <td> Add a zero terminator if needed 4287 ** </table> 4288 ** </blockquote>)^ 4289 ** 4290 ** Note that when type conversions occur, pointers returned by prior 4291 ** calls to sqlite3_column_blob(), sqlite3_column_text(), and/or 4292 ** sqlite3_column_text16() may be invalidated. 4293 ** Type conversions and pointer invalidations might occur 4294 ** in the following cases: 4295 ** 4296 ** <ul> 4297 ** <li> The initial content is a BLOB and sqlite3_column_text() or 4298 ** sqlite3_column_text16() is called. A zero-terminator might 4299 ** need to be added to the string.</li> 4300 ** <li> The initial content is UTF-8 text and sqlite3_column_bytes16() or 4301 ** sqlite3_column_text16() is called. The content must be converted 4302 ** to UTF-16.</li> 4303 ** <li> The initial content is UTF-16 text and sqlite3_column_bytes() or 4304 ** sqlite3_column_text() is called. The content must be converted 4305 ** to UTF-8.</li> 4306 ** </ul> 4307 ** 4308 ** ^Conversions between UTF-16be and UTF-16le are always done in place and do 4309 ** not invalidate a prior pointer, though of course the content of the buffer 4310 ** that the prior pointer references will have been modified. Other kinds 4311 ** of conversion are done in place when it is possible, but sometimes they 4312 ** are not possible and in those cases prior pointers are invalidated. 4313 ** 4314 ** The safest policy is to invoke these routines 4315 ** in one of the following ways: 4316 ** 4317 ** <ul> 4318 ** <li>sqlite3_column_text() followed by sqlite3_column_bytes()</li> 4319 ** <li>sqlite3_column_blob() followed by sqlite3_column_bytes()</li> 4320 ** <li>sqlite3_column_text16() followed by sqlite3_column_bytes16()</li> 4321 ** </ul> 4322 ** 4323 ** In other words, you should call sqlite3_column_text(), 4324 ** sqlite3_column_blob(), or sqlite3_column_text16() first to force the result 4325 ** into the desired format, then invoke sqlite3_column_bytes() or 4326 ** sqlite3_column_bytes16() to find the size of the result. Do not mix calls 4327 ** to sqlite3_column_text() or sqlite3_column_blob() with calls to 4328 ** sqlite3_column_bytes16(), and do not mix calls to sqlite3_column_text16() 4329 ** with calls to sqlite3_column_bytes(). 4330 ** 4331 ** ^The pointers returned are valid until a type conversion occurs as 4332 ** described above, or until [sqlite3_step()] or [sqlite3_reset()] or 4333 ** [sqlite3_finalize()] is called. ^The memory space used to hold strings 4334 ** and BLOBs is freed automatically. Do <em>not</em> pass the pointers returned 4335 ** from [sqlite3_column_blob()], [sqlite3_column_text()], etc. into 4336 ** [sqlite3_free()]. 4337 ** 4338 ** ^(If a memory allocation error occurs during the evaluation of any 4339 ** of these routines, a default value is returned. The default value 4340 ** is either the integer 0, the floating point number 0.0, or a NULL 4341 ** pointer. Subsequent calls to [sqlite3_errcode()] will return 4342 ** [SQLITE_NOMEM].)^ 4343 */ 4344 SQLITE_API const void *sqlite3_column_blob(sqlite3_stmt*, int iCol); 4345 SQLITE_API int sqlite3_column_bytes(sqlite3_stmt*, int iCol); 4346 SQLITE_API int sqlite3_column_bytes16(sqlite3_stmt*, int iCol); 4347 SQLITE_API double sqlite3_column_double(sqlite3_stmt*, int iCol); 4348 SQLITE_API int sqlite3_column_int(sqlite3_stmt*, int iCol); 4349 SQLITE_API sqlite3_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol); 4350 SQLITE_API const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol); 4351 SQLITE_API const void *sqlite3_column_text16(sqlite3_stmt*, int iCol); 4352 SQLITE_API int sqlite3_column_type(sqlite3_stmt*, int iCol); 4353 SQLITE_API sqlite3_value *sqlite3_column_value(sqlite3_stmt*, int iCol); 4354 4355 /* 4356 ** CAPI3REF: Destroy A Prepared Statement Object 4357 ** DESTRUCTOR: sqlite3_stmt 4358 ** 4359 ** ^The sqlite3_finalize() function is called to delete a [prepared statement]. 4360 ** ^If the most recent evaluation of the statement encountered no errors 4361 ** or if the statement is never been evaluated, then sqlite3_finalize() returns 4362 ** SQLITE_OK. ^If the most recent evaluation of statement S failed, then 4363 ** sqlite3_finalize(S) returns the appropriate [error code] or 4364 ** [extended error code]. 4365 ** 4366 ** ^The sqlite3_finalize(S) routine can be called at any point during 4367 ** the life cycle of [prepared statement] S: 4368 ** before statement S is ever evaluated, after 4369 ** one or more calls to [sqlite3_reset()], or after any call 4370 ** to [sqlite3_step()] regardless of whether or not the statement has 4371 ** completed execution. 4372 ** 4373 ** ^Invoking sqlite3_finalize() on a NULL pointer is a harmless no-op. 4374 ** 4375 ** The application must finalize every [prepared statement] in order to avoid 4376 ** resource leaks. It is a grievous error for the application to try to use 4377 ** a prepared statement after it has been finalized. Any use of a prepared 4378 ** statement after it has been finalized can result in undefined and 4379 ** undesirable behavior such as segfaults and heap corruption. 4380 */ 4381 SQLITE_API int sqlite3_finalize(sqlite3_stmt *pStmt); 4382 4383 /* 4384 ** CAPI3REF: Reset A Prepared Statement Object 4385 ** METHOD: sqlite3_stmt 4386 ** 4387 ** The sqlite3_reset() function is called to reset a [prepared statement] 4388 ** object back to its initial state, ready to be re-executed. 4389 ** ^Any SQL statement variables that had values bound to them using 4390 ** the [sqlite3_bind_blob | sqlite3_bind_*() API] retain their values. 4391 ** Use [sqlite3_clear_bindings()] to reset the bindings. 4392 ** 4393 ** ^The [sqlite3_reset(S)] interface resets the [prepared statement] S 4394 ** back to the beginning of its program. 4395 ** 4396 ** ^If the most recent call to [sqlite3_step(S)] for the 4397 ** [prepared statement] S returned [SQLITE_ROW] or [SQLITE_DONE], 4398 ** or if [sqlite3_step(S)] has never before been called on S, 4399 ** then [sqlite3_reset(S)] returns [SQLITE_OK]. 4400 ** 4401 ** ^If the most recent call to [sqlite3_step(S)] for the 4402 ** [prepared statement] S indicated an error, then 4403 ** [sqlite3_reset(S)] returns an appropriate [error code]. 4404 ** 4405 ** ^The [sqlite3_reset(S)] interface does not change the values 4406 ** of any [sqlite3_bind_blob|bindings] on the [prepared statement] S. 4407 */ 4408 SQLITE_API int sqlite3_reset(sqlite3_stmt *pStmt); 4409 4410 /* 4411 ** CAPI3REF: Create Or Redefine SQL Functions 4412 ** KEYWORDS: {function creation routines} 4413 ** KEYWORDS: {application-defined SQL function} 4414 ** KEYWORDS: {application-defined SQL functions} 4415 ** METHOD: sqlite3 4416 ** 4417 ** ^These functions (collectively known as "function creation routines") 4418 ** are used to add SQL functions or aggregates or to redefine the behavior 4419 ** of existing SQL functions or aggregates. The only differences between 4420 ** these routines are the text encoding expected for 4421 ** the second parameter (the name of the function being created) 4422 ** and the presence or absence of a destructor callback for 4423 ** the application data pointer. 4424 ** 4425 ** ^The first parameter is the [database connection] to which the SQL 4426 ** function is to be added. ^If an application uses more than one database 4427 ** connection then application-defined SQL functions must be added 4428 ** to each database connection separately. 4429 ** 4430 ** ^The second parameter is the name of the SQL function to be created or 4431 ** redefined. ^The length of the name is limited to 255 bytes in a UTF-8 4432 ** representation, exclusive of the zero-terminator. ^Note that the name 4433 ** length limit is in UTF-8 bytes, not characters nor UTF-16 bytes. 4434 ** ^Any attempt to create a function with a longer name 4435 ** will result in [SQLITE_MISUSE] being returned. 4436 ** 4437 ** ^The third parameter (nArg) 4438 ** is the number of arguments that the SQL function or 4439 ** aggregate takes. ^If this parameter is -1, then the SQL function or 4440 ** aggregate may take any number of arguments between 0 and the limit 4441 ** set by [sqlite3_limit]([SQLITE_LIMIT_FUNCTION_ARG]). If the third 4442 ** parameter is less than -1 or greater than 127 then the behavior is 4443 ** undefined. 4444 ** 4445 ** ^The fourth parameter, eTextRep, specifies what 4446 ** [SQLITE_UTF8 | text encoding] this SQL function prefers for 4447 ** its parameters. The application should set this parameter to 4448 ** [SQLITE_UTF16LE] if the function implementation invokes 4449 ** [sqlite3_value_text16le()] on an input, or [SQLITE_UTF16BE] if the 4450 ** implementation invokes [sqlite3_value_text16be()] on an input, or 4451 ** [SQLITE_UTF16] if [sqlite3_value_text16()] is used, or [SQLITE_UTF8] 4452 ** otherwise. ^The same SQL function may be registered multiple times using 4453 ** different preferred text encodings, with different implementations for 4454 ** each encoding. 4455 ** ^When multiple implementations of the same function are available, SQLite 4456 ** will pick the one that involves the least amount of data conversion. 4457 ** 4458 ** ^The fourth parameter may optionally be ORed with [SQLITE_DETERMINISTIC] 4459 ** to signal that the function will always return the same result given 4460 ** the same inputs within a single SQL statement. Most SQL functions are 4461 ** deterministic. The built-in [random()] SQL function is an example of a 4462 ** function that is not deterministic. The SQLite query planner is able to 4463 ** perform additional optimizations on deterministic functions, so use 4464 ** of the [SQLITE_DETERMINISTIC] flag is recommended where possible. 4465 ** 4466 ** ^(The fifth parameter is an arbitrary pointer. The implementation of the 4467 ** function can gain access to this pointer using [sqlite3_user_data()].)^ 4468 ** 4469 ** ^The sixth, seventh and eighth parameters, xFunc, xStep and xFinal, are 4470 ** pointers to C-language functions that implement the SQL function or 4471 ** aggregate. ^A scalar SQL function requires an implementation of the xFunc 4472 ** callback only; NULL pointers must be passed as the xStep and xFinal 4473 ** parameters. ^An aggregate SQL function requires an implementation of xStep 4474 ** and xFinal and NULL pointer must be passed for xFunc. ^To delete an existing 4475 ** SQL function or aggregate, pass NULL pointers for all three function 4476 ** callbacks. 4477 ** 4478 ** ^(If the ninth parameter to sqlite3_create_function_v2() is not NULL, 4479 ** then it is destructor for the application data pointer. 4480 ** The destructor is invoked when the function is deleted, either by being 4481 ** overloaded or when the database connection closes.)^ 4482 ** ^The destructor is also invoked if the call to 4483 ** sqlite3_create_function_v2() fails. 4484 ** ^When the destructor callback of the tenth parameter is invoked, it 4485 ** is passed a single argument which is a copy of the application data 4486 ** pointer which was the fifth parameter to sqlite3_create_function_v2(). 4487 ** 4488 ** ^It is permitted to register multiple implementations of the same 4489 ** functions with the same name but with either differing numbers of 4490 ** arguments or differing preferred text encodings. ^SQLite will use 4491 ** the implementation that most closely matches the way in which the 4492 ** SQL function is used. ^A function implementation with a non-negative 4493 ** nArg parameter is a better match than a function implementation with 4494 ** a negative nArg. ^A function where the preferred text encoding 4495 ** matches the database encoding is a better 4496 ** match than a function where the encoding is different. 4497 ** ^A function where the encoding difference is between UTF16le and UTF16be 4498 ** is a closer match than a function where the encoding difference is 4499 ** between UTF8 and UTF16. 4500 ** 4501 ** ^Built-in functions may be overloaded by new application-defined functions. 4502 ** 4503 ** ^An application-defined function is permitted to call other 4504 ** SQLite interfaces. However, such calls must not 4505 ** close the database connection nor finalize or reset the prepared 4506 ** statement in which the function is running. 4507 */ 4508 SQLITE_API int sqlite3_create_function( 4509 sqlite3 *db, 4510 const char *zFunctionName, 4511 int nArg, 4512 int eTextRep, 4513 void *pApp, 4514 void (*xFunc)(sqlite3_context*,int,sqlite3_value**), 4515 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 4516 void (*xFinal)(sqlite3_context*) 4517 ); 4518 SQLITE_API int sqlite3_create_function16( 4519 sqlite3 *db, 4520 const void *zFunctionName, 4521 int nArg, 4522 int eTextRep, 4523 void *pApp, 4524 void (*xFunc)(sqlite3_context*,int,sqlite3_value**), 4525 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 4526 void (*xFinal)(sqlite3_context*) 4527 ); 4528 SQLITE_API int sqlite3_create_function_v2( 4529 sqlite3 *db, 4530 const char *zFunctionName, 4531 int nArg, 4532 int eTextRep, 4533 void *pApp, 4534 void (*xFunc)(sqlite3_context*,int,sqlite3_value**), 4535 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 4536 void (*xFinal)(sqlite3_context*), 4537 void(*xDestroy)(void*) 4538 ); 4539 4540 /* 4541 ** CAPI3REF: Text Encodings 4542 ** 4543 ** These constant define integer codes that represent the various 4544 ** text encodings supported by SQLite. 4545 */ 4546 #define SQLITE_UTF8 1 /* IMP: R-37514-35566 */ 4547 #define SQLITE_UTF16LE 2 /* IMP: R-03371-37637 */ 4548 #define SQLITE_UTF16BE 3 /* IMP: R-51971-34154 */ 4549 #define SQLITE_UTF16 4 /* Use native byte order */ 4550 #define SQLITE_ANY 5 /* Deprecated */ 4551 #define SQLITE_UTF16_ALIGNED 8 /* sqlite3_create_collation only */ 4552 4553 /* 4554 ** CAPI3REF: Function Flags 4555 ** 4556 ** These constants may be ORed together with the 4557 ** [SQLITE_UTF8 | preferred text encoding] as the fourth argument 4558 ** to [sqlite3_create_function()], [sqlite3_create_function16()], or 4559 ** [sqlite3_create_function_v2()]. 4560 */ 4561 #define SQLITE_DETERMINISTIC 0x800 4562 4563 /* 4564 ** CAPI3REF: Deprecated Functions 4565 ** DEPRECATED 4566 ** 4567 ** These functions are [deprecated]. In order to maintain 4568 ** backwards compatibility with older code, these functions continue 4569 ** to be supported. However, new applications should avoid 4570 ** the use of these functions. To encourage programmers to avoid 4571 ** these functions, we will not explain what they do. 4572 */ 4573 #ifndef SQLITE_OMIT_DEPRECATED 4574 SQLITE_API SQLITE_DEPRECATED int sqlite3_aggregate_count(sqlite3_context*); 4575 SQLITE_API SQLITE_DEPRECATED int sqlite3_expired(sqlite3_stmt*); 4576 SQLITE_API SQLITE_DEPRECATED int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*); 4577 SQLITE_API SQLITE_DEPRECATED int sqlite3_global_recover(void); 4578 SQLITE_API SQLITE_DEPRECATED void sqlite3_thread_cleanup(void); 4579 SQLITE_API SQLITE_DEPRECATED int sqlite3_memory_alarm(void(*)(void*,sqlite3_int64,int), 4580 void*,sqlite3_int64); 4581 #endif 4582 4583 /* 4584 ** CAPI3REF: Obtaining SQL Values 4585 ** METHOD: sqlite3_value 4586 ** 4587 ** The C-language implementation of SQL functions and aggregates uses 4588 ** this set of interface routines to access the parameter values on 4589 ** the function or aggregate. 4590 ** 4591 ** The xFunc (for scalar functions) or xStep (for aggregates) parameters 4592 ** to [sqlite3_create_function()] and [sqlite3_create_function16()] 4593 ** define callbacks that implement the SQL functions and aggregates. 4594 ** The 3rd parameter to these callbacks is an array of pointers to 4595 ** [protected sqlite3_value] objects. There is one [sqlite3_value] object for 4596 ** each parameter to the SQL function. These routines are used to 4597 ** extract values from the [sqlite3_value] objects. 4598 ** 4599 ** These routines work only with [protected sqlite3_value] objects. 4600 ** Any attempt to use these routines on an [unprotected sqlite3_value] 4601 ** object results in undefined behavior. 4602 ** 4603 ** ^These routines work just like the corresponding [column access functions] 4604 ** except that these routines take a single [protected sqlite3_value] object 4605 ** pointer instead of a [sqlite3_stmt*] pointer and an integer column number. 4606 ** 4607 ** ^The sqlite3_value_text16() interface extracts a UTF-16 string 4608 ** in the native byte-order of the host machine. ^The 4609 ** sqlite3_value_text16be() and sqlite3_value_text16le() interfaces 4610 ** extract UTF-16 strings as big-endian and little-endian respectively. 4611 ** 4612 ** ^(The sqlite3_value_numeric_type() interface attempts to apply 4613 ** numeric affinity to the value. This means that an attempt is 4614 ** made to convert the value to an integer or floating point. If 4615 ** such a conversion is possible without loss of information (in other 4616 ** words, if the value is a string that looks like a number) 4617 ** then the conversion is performed. Otherwise no conversion occurs. 4618 ** The [SQLITE_INTEGER | datatype] after conversion is returned.)^ 4619 ** 4620 ** Please pay particular attention to the fact that the pointer returned 4621 ** from [sqlite3_value_blob()], [sqlite3_value_text()], or 4622 ** [sqlite3_value_text16()] can be invalidated by a subsequent call to 4623 ** [sqlite3_value_bytes()], [sqlite3_value_bytes16()], [sqlite3_value_text()], 4624 ** or [sqlite3_value_text16()]. 4625 ** 4626 ** These routines must be called from the same thread as 4627 ** the SQL function that supplied the [sqlite3_value*] parameters. 4628 */ 4629 SQLITE_API const void *sqlite3_value_blob(sqlite3_value*); 4630 SQLITE_API int sqlite3_value_bytes(sqlite3_value*); 4631 SQLITE_API int sqlite3_value_bytes16(sqlite3_value*); 4632 SQLITE_API double sqlite3_value_double(sqlite3_value*); 4633 SQLITE_API int sqlite3_value_int(sqlite3_value*); 4634 SQLITE_API sqlite3_int64 sqlite3_value_int64(sqlite3_value*); 4635 SQLITE_API void *sqlite3_value_pointer(sqlite3_value*); 4636 SQLITE_API const unsigned char *sqlite3_value_text(sqlite3_value*); 4637 SQLITE_API const void *sqlite3_value_text16(sqlite3_value*); 4638 SQLITE_API const void *sqlite3_value_text16le(sqlite3_value*); 4639 SQLITE_API const void *sqlite3_value_text16be(sqlite3_value*); 4640 SQLITE_API int sqlite3_value_type(sqlite3_value*); 4641 SQLITE_API int sqlite3_value_numeric_type(sqlite3_value*); 4642 4643 /* 4644 ** CAPI3REF: Finding The Subtype Of SQL Values 4645 ** METHOD: sqlite3_value 4646 ** 4647 ** The sqlite3_value_subtype(V) function returns the subtype for 4648 ** an [application-defined SQL function] argument V. The subtype 4649 ** information can be used to pass a limited amount of context from 4650 ** one SQL function to another. Use the [sqlite3_result_subtype()] 4651 ** routine to set the subtype for the return value of an SQL function. 4652 ** 4653 ** SQLite makes no use of subtype itself. It merely passes the subtype 4654 ** from the result of one [application-defined SQL function] into the 4655 ** input of another. 4656 */ 4657 SQLITE_API unsigned int sqlite3_value_subtype(sqlite3_value*); 4658 4659 /* 4660 ** CAPI3REF: Copy And Free SQL Values 4661 ** METHOD: sqlite3_value 4662 ** 4663 ** ^The sqlite3_value_dup(V) interface makes a copy of the [sqlite3_value] 4664 ** object D and returns a pointer to that copy. ^The [sqlite3_value] returned 4665 ** is a [protected sqlite3_value] object even if the input is not. 4666 ** ^The sqlite3_value_dup(V) interface returns NULL if V is NULL or if a 4667 ** memory allocation fails. 4668 ** 4669 ** ^The sqlite3_value_free(V) interface frees an [sqlite3_value] object 4670 ** previously obtained from [sqlite3_value_dup()]. ^If V is a NULL pointer 4671 ** then sqlite3_value_free(V) is a harmless no-op. 4672 */ 4673 SQLITE_API sqlite3_value *sqlite3_value_dup(const sqlite3_value*); 4674 SQLITE_API void sqlite3_value_free(sqlite3_value*); 4675 4676 /* 4677 ** CAPI3REF: Obtain Aggregate Function Context 4678 ** METHOD: sqlite3_context 4679 ** 4680 ** Implementations of aggregate SQL functions use this 4681 ** routine to allocate memory for storing their state. 4682 ** 4683 ** ^The first time the sqlite3_aggregate_context(C,N) routine is called 4684 ** for a particular aggregate function, SQLite 4685 ** allocates N of memory, zeroes out that memory, and returns a pointer 4686 ** to the new memory. ^On second and subsequent calls to 4687 ** sqlite3_aggregate_context() for the same aggregate function instance, 4688 ** the same buffer is returned. Sqlite3_aggregate_context() is normally 4689 ** called once for each invocation of the xStep callback and then one 4690 ** last time when the xFinal callback is invoked. ^(When no rows match 4691 ** an aggregate query, the xStep() callback of the aggregate function 4692 ** implementation is never called and xFinal() is called exactly once. 4693 ** In those cases, sqlite3_aggregate_context() might be called for the 4694 ** first time from within xFinal().)^ 4695 ** 4696 ** ^The sqlite3_aggregate_context(C,N) routine returns a NULL pointer 4697 ** when first called if N is less than or equal to zero or if a memory 4698 ** allocate error occurs. 4699 ** 4700 ** ^(The amount of space allocated by sqlite3_aggregate_context(C,N) is 4701 ** determined by the N parameter on first successful call. Changing the 4702 ** value of N in subsequent call to sqlite3_aggregate_context() within 4703 ** the same aggregate function instance will not resize the memory 4704 ** allocation.)^ Within the xFinal callback, it is customary to set 4705 ** N=0 in calls to sqlite3_aggregate_context(C,N) so that no 4706 ** pointless memory allocations occur. 4707 ** 4708 ** ^SQLite automatically frees the memory allocated by 4709 ** sqlite3_aggregate_context() when the aggregate query concludes. 4710 ** 4711 ** The first parameter must be a copy of the 4712 ** [sqlite3_context | SQL function context] that is the first parameter 4713 ** to the xStep or xFinal callback routine that implements the aggregate 4714 ** function. 4715 ** 4716 ** This routine must be called from the same thread in which 4717 ** the aggregate SQL function is running. 4718 */ 4719 SQLITE_API void *sqlite3_aggregate_context(sqlite3_context*, int nBytes); 4720 4721 /* 4722 ** CAPI3REF: User Data For Functions 4723 ** METHOD: sqlite3_context 4724 ** 4725 ** ^The sqlite3_user_data() interface returns a copy of 4726 ** the pointer that was the pUserData parameter (the 5th parameter) 4727 ** of the [sqlite3_create_function()] 4728 ** and [sqlite3_create_function16()] routines that originally 4729 ** registered the application defined function. 4730 ** 4731 ** This routine must be called from the same thread in which 4732 ** the application-defined function is running. 4733 */ 4734 SQLITE_API void *sqlite3_user_data(sqlite3_context*); 4735 4736 /* 4737 ** CAPI3REF: Database Connection For Functions 4738 ** METHOD: sqlite3_context 4739 ** 4740 ** ^The sqlite3_context_db_handle() interface returns a copy of 4741 ** the pointer to the [database connection] (the 1st parameter) 4742 ** of the [sqlite3_create_function()] 4743 ** and [sqlite3_create_function16()] routines that originally 4744 ** registered the application defined function. 4745 */ 4746 SQLITE_API sqlite3 *sqlite3_context_db_handle(sqlite3_context*); 4747 4748 /* 4749 ** CAPI3REF: Function Auxiliary Data 4750 ** METHOD: sqlite3_context 4751 ** 4752 ** These functions may be used by (non-aggregate) SQL functions to 4753 ** associate metadata with argument values. If the same value is passed to 4754 ** multiple invocations of the same SQL function during query execution, under 4755 ** some circumstances the associated metadata may be preserved. An example 4756 ** of where this might be useful is in a regular-expression matching 4757 ** function. The compiled version of the regular expression can be stored as 4758 ** metadata associated with the pattern string. 4759 ** Then as long as the pattern string remains the same, 4760 ** the compiled regular expression can be reused on multiple 4761 ** invocations of the same function. 4762 ** 4763 ** ^The sqlite3_get_auxdata() interface returns a pointer to the metadata 4764 ** associated by the sqlite3_set_auxdata() function with the Nth argument 4765 ** value to the application-defined function. ^If there is no metadata 4766 ** associated with the function argument, this sqlite3_get_auxdata() interface 4767 ** returns a NULL pointer. 4768 ** 4769 ** ^The sqlite3_set_auxdata(C,N,P,X) interface saves P as metadata for the N-th 4770 ** argument of the application-defined function. ^Subsequent 4771 ** calls to sqlite3_get_auxdata(C,N) return P from the most recent 4772 ** sqlite3_set_auxdata(C,N,P,X) call if the metadata is still valid or 4773 ** NULL if the metadata has been discarded. 4774 ** ^After each call to sqlite3_set_auxdata(C,N,P,X) where X is not NULL, 4775 ** SQLite will invoke the destructor function X with parameter P exactly 4776 ** once, when the metadata is discarded. 4777 ** SQLite is free to discard the metadata at any time, including: <ul> 4778 ** <li> ^(when the corresponding function parameter changes)^, or 4779 ** <li> ^(when [sqlite3_reset()] or [sqlite3_finalize()] is called for the 4780 ** SQL statement)^, or 4781 ** <li> ^(when sqlite3_set_auxdata() is invoked again on the same 4782 ** parameter)^, or 4783 ** <li> ^(during the original sqlite3_set_auxdata() call when a memory 4784 ** allocation error occurs.)^ </ul> 4785 ** 4786 ** Note the last bullet in particular. The destructor X in 4787 ** sqlite3_set_auxdata(C,N,P,X) might be called immediately, before the 4788 ** sqlite3_set_auxdata() interface even returns. Hence sqlite3_set_auxdata() 4789 ** should be called near the end of the function implementation and the 4790 ** function implementation should not make any use of P after 4791 ** sqlite3_set_auxdata() has been called. 4792 ** 4793 ** ^(In practice, metadata is preserved between function calls for 4794 ** function parameters that are compile-time constants, including literal 4795 ** values and [parameters] and expressions composed from the same.)^ 4796 ** 4797 ** These routines must be called from the same thread in which 4798 ** the SQL function is running. 4799 */ 4800 SQLITE_API void *sqlite3_get_auxdata(sqlite3_context*, int N); 4801 SQLITE_API void sqlite3_set_auxdata(sqlite3_context*, int N, void*, void (*)(void*)); 4802 4803 4804 /* 4805 ** CAPI3REF: Constants Defining Special Destructor Behavior 4806 ** 4807 ** These are special values for the destructor that is passed in as the 4808 ** final argument to routines like [sqlite3_result_blob()]. ^If the destructor 4809 ** argument is SQLITE_STATIC, it means that the content pointer is constant 4810 ** and will never change. It does not need to be destroyed. ^The 4811 ** SQLITE_TRANSIENT value means that the content will likely change in 4812 ** the near future and that SQLite should make its own private copy of 4813 ** the content before returning. 4814 ** 4815 ** The typedef is necessary to work around problems in certain 4816 ** C++ compilers. 4817 */ 4818 typedef void (*sqlite3_destructor_type)(void*); 4819 #define SQLITE_STATIC ((sqlite3_destructor_type)0) 4820 #define SQLITE_TRANSIENT ((sqlite3_destructor_type)-1) 4821 4822 /* 4823 ** CAPI3REF: Setting The Result Of An SQL Function 4824 ** METHOD: sqlite3_context 4825 ** 4826 ** These routines are used by the xFunc or xFinal callbacks that 4827 ** implement SQL functions and aggregates. See 4828 ** [sqlite3_create_function()] and [sqlite3_create_function16()] 4829 ** for additional information. 4830 ** 4831 ** These functions work very much like the [parameter binding] family of 4832 ** functions used to bind values to host parameters in prepared statements. 4833 ** Refer to the [SQL parameter] documentation for additional information. 4834 ** 4835 ** ^The sqlite3_result_blob() interface sets the result from 4836 ** an application-defined function to be the BLOB whose content is pointed 4837 ** to by the second parameter and which is N bytes long where N is the 4838 ** third parameter. 4839 ** 4840 ** ^The sqlite3_result_zeroblob(C,N) and sqlite3_result_zeroblob64(C,N) 4841 ** interfaces set the result of the application-defined function to be 4842 ** a BLOB containing all zero bytes and N bytes in size. 4843 ** 4844 ** ^The sqlite3_result_double() interface sets the result from 4845 ** an application-defined function to be a floating point value specified 4846 ** by its 2nd argument. 4847 ** 4848 ** ^The sqlite3_result_error() and sqlite3_result_error16() functions 4849 ** cause the implemented SQL function to throw an exception. 4850 ** ^SQLite uses the string pointed to by the 4851 ** 2nd parameter of sqlite3_result_error() or sqlite3_result_error16() 4852 ** as the text of an error message. ^SQLite interprets the error 4853 ** message string from sqlite3_result_error() as UTF-8. ^SQLite 4854 ** interprets the string from sqlite3_result_error16() as UTF-16 in native 4855 ** byte order. ^If the third parameter to sqlite3_result_error() 4856 ** or sqlite3_result_error16() is negative then SQLite takes as the error 4857 ** message all text up through the first zero character. 4858 ** ^If the third parameter to sqlite3_result_error() or 4859 ** sqlite3_result_error16() is non-negative then SQLite takes that many 4860 ** bytes (not characters) from the 2nd parameter as the error message. 4861 ** ^The sqlite3_result_error() and sqlite3_result_error16() 4862 ** routines make a private copy of the error message text before 4863 ** they return. Hence, the calling function can deallocate or 4864 ** modify the text after they return without harm. 4865 ** ^The sqlite3_result_error_code() function changes the error code 4866 ** returned by SQLite as a result of an error in a function. ^By default, 4867 ** the error code is SQLITE_ERROR. ^A subsequent call to sqlite3_result_error() 4868 ** or sqlite3_result_error16() resets the error code to SQLITE_ERROR. 4869 ** 4870 ** ^The sqlite3_result_error_toobig() interface causes SQLite to throw an 4871 ** error indicating that a string or BLOB is too long to represent. 4872 ** 4873 ** ^The sqlite3_result_error_nomem() interface causes SQLite to throw an 4874 ** error indicating that a memory allocation failed. 4875 ** 4876 ** ^The sqlite3_result_int() interface sets the return value 4877 ** of the application-defined function to be the 32-bit signed integer 4878 ** value given in the 2nd argument. 4879 ** ^The sqlite3_result_int64() interface sets the return value 4880 ** of the application-defined function to be the 64-bit signed integer 4881 ** value given in the 2nd argument. 4882 ** 4883 ** ^The sqlite3_result_null() interface sets the return value 4884 ** of the application-defined function to be NULL. 4885 ** 4886 ** ^The sqlite3_result_text(), sqlite3_result_text16(), 4887 ** sqlite3_result_text16le(), and sqlite3_result_text16be() interfaces 4888 ** set the return value of the application-defined function to be 4889 ** a text string which is represented as UTF-8, UTF-16 native byte order, 4890 ** UTF-16 little endian, or UTF-16 big endian, respectively. 4891 ** ^The sqlite3_result_text64() interface sets the return value of an 4892 ** application-defined function to be a text string in an encoding 4893 ** specified by the fifth (and last) parameter, which must be one 4894 ** of [SQLITE_UTF8], [SQLITE_UTF16], [SQLITE_UTF16BE], or [SQLITE_UTF16LE]. 4895 ** ^SQLite takes the text result from the application from 4896 ** the 2nd parameter of the sqlite3_result_text* interfaces. 4897 ** ^If the 3rd parameter to the sqlite3_result_text* interfaces 4898 ** is negative, then SQLite takes result text from the 2nd parameter 4899 ** through the first zero character. 4900 ** ^If the 3rd parameter to the sqlite3_result_text* interfaces 4901 ** is non-negative, then as many bytes (not characters) of the text 4902 ** pointed to by the 2nd parameter are taken as the application-defined 4903 ** function result. If the 3rd parameter is non-negative, then it 4904 ** must be the byte offset into the string where the NUL terminator would 4905 ** appear if the string where NUL terminated. If any NUL characters occur 4906 ** in the string at a byte offset that is less than the value of the 3rd 4907 ** parameter, then the resulting string will contain embedded NULs and the 4908 ** result of expressions operating on strings with embedded NULs is undefined. 4909 ** ^If the 4th parameter to the sqlite3_result_text* interfaces 4910 ** or sqlite3_result_blob is a non-NULL pointer, then SQLite calls that 4911 ** function as the destructor on the text or BLOB result when it has 4912 ** finished using that result. 4913 ** ^If the 4th parameter to the sqlite3_result_text* interfaces or to 4914 ** sqlite3_result_blob is the special constant SQLITE_STATIC, then SQLite 4915 ** assumes that the text or BLOB result is in constant space and does not 4916 ** copy the content of the parameter nor call a destructor on the content 4917 ** when it has finished using that result. 4918 ** ^If the 4th parameter to the sqlite3_result_text* interfaces 4919 ** or sqlite3_result_blob is the special constant SQLITE_TRANSIENT 4920 ** then SQLite makes a copy of the result into space obtained from 4921 ** from [sqlite3_malloc()] before it returns. 4922 ** 4923 ** ^The sqlite3_result_value() interface sets the result of 4924 ** the application-defined function to be a copy of the 4925 ** [unprotected sqlite3_value] object specified by the 2nd parameter. ^The 4926 ** sqlite3_result_value() interface makes a copy of the [sqlite3_value] 4927 ** so that the [sqlite3_value] specified in the parameter may change or 4928 ** be deallocated after sqlite3_result_value() returns without harm. 4929 ** ^A [protected sqlite3_value] object may always be used where an 4930 ** [unprotected sqlite3_value] object is required, so either 4931 ** kind of [sqlite3_value] object can be used with this interface. 4932 ** 4933 ** If these routines are called from within the different thread 4934 ** than the one containing the application-defined function that received 4935 ** the [sqlite3_context] pointer, the results are undefined. 4936 */ 4937 SQLITE_API void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*)); 4938 SQLITE_API void sqlite3_result_blob64(sqlite3_context*,const void*, 4939 sqlite3_uint64,void(*)(void*)); 4940 SQLITE_API void sqlite3_result_double(sqlite3_context*, double); 4941 SQLITE_API void sqlite3_result_error(sqlite3_context*, const char*, int); 4942 SQLITE_API void sqlite3_result_error16(sqlite3_context*, const void*, int); 4943 SQLITE_API void sqlite3_result_error_toobig(sqlite3_context*); 4944 SQLITE_API void sqlite3_result_error_nomem(sqlite3_context*); 4945 SQLITE_API void sqlite3_result_error_code(sqlite3_context*, int); 4946 SQLITE_API void sqlite3_result_int(sqlite3_context*, int); 4947 SQLITE_API void sqlite3_result_int64(sqlite3_context*, sqlite3_int64); 4948 SQLITE_API void sqlite3_result_null(sqlite3_context*); 4949 SQLITE_API void sqlite3_result_pointer(sqlite3_context*, void*); 4950 SQLITE_API void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*)); 4951 SQLITE_API void sqlite3_result_text64(sqlite3_context*, const char*,sqlite3_uint64, 4952 void(*)(void*), unsigned char encoding); 4953 SQLITE_API void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*)); 4954 SQLITE_API void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*)); 4955 SQLITE_API void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*)); 4956 SQLITE_API void sqlite3_result_value(sqlite3_context*, sqlite3_value*); 4957 SQLITE_API void sqlite3_result_zeroblob(sqlite3_context*, int n); 4958 SQLITE_API int sqlite3_result_zeroblob64(sqlite3_context*, sqlite3_uint64 n); 4959 4960 4961 /* 4962 ** CAPI3REF: Setting The Subtype Of An SQL Function 4963 ** METHOD: sqlite3_context 4964 ** 4965 ** The sqlite3_result_subtype(C,T) function causes the subtype of 4966 ** the result from the [application-defined SQL function] with 4967 ** [sqlite3_context] C to be the value T. Only the lower 8 bits 4968 ** of the subtype T are preserved in current versions of SQLite; 4969 ** higher order bits are discarded. 4970 ** The number of subtype bytes preserved by SQLite might increase 4971 ** in future releases of SQLite. 4972 */ 4973 SQLITE_API void sqlite3_result_subtype(sqlite3_context*,unsigned int); 4974 4975 /* 4976 ** CAPI3REF: Define New Collating Sequences 4977 ** METHOD: sqlite3 4978 ** 4979 ** ^These functions add, remove, or modify a [collation] associated 4980 ** with the [database connection] specified as the first argument. 4981 ** 4982 ** ^The name of the collation is a UTF-8 string 4983 ** for sqlite3_create_collation() and sqlite3_create_collation_v2() 4984 ** and a UTF-16 string in native byte order for sqlite3_create_collation16(). 4985 ** ^Collation names that compare equal according to [sqlite3_strnicmp()] are 4986 ** considered to be the same name. 4987 ** 4988 ** ^(The third argument (eTextRep) must be one of the constants: 4989 ** <ul> 4990 ** <li> [SQLITE_UTF8], 4991 ** <li> [SQLITE_UTF16LE], 4992 ** <li> [SQLITE_UTF16BE], 4993 ** <li> [SQLITE_UTF16], or 4994 ** <li> [SQLITE_UTF16_ALIGNED]. 4995 ** </ul>)^ 4996 ** ^The eTextRep argument determines the encoding of strings passed 4997 ** to the collating function callback, xCallback. 4998 ** ^The [SQLITE_UTF16] and [SQLITE_UTF16_ALIGNED] values for eTextRep 4999 ** force strings to be UTF16 with native byte order. 5000 ** ^The [SQLITE_UTF16_ALIGNED] value for eTextRep forces strings to begin 5001 ** on an even byte address. 5002 ** 5003 ** ^The fourth argument, pArg, is an application data pointer that is passed 5004 ** through as the first argument to the collating function callback. 5005 ** 5006 ** ^The fifth argument, xCallback, is a pointer to the collating function. 5007 ** ^Multiple collating functions can be registered using the same name but 5008 ** with different eTextRep parameters and SQLite will use whichever 5009 ** function requires the least amount of data transformation. 5010 ** ^If the xCallback argument is NULL then the collating function is 5011 ** deleted. ^When all collating functions having the same name are deleted, 5012 ** that collation is no longer usable. 5013 ** 5014 ** ^The collating function callback is invoked with a copy of the pArg 5015 ** application data pointer and with two strings in the encoding specified 5016 ** by the eTextRep argument. The collating function must return an 5017 ** integer that is negative, zero, or positive 5018 ** if the first string is less than, equal to, or greater than the second, 5019 ** respectively. A collating function must always return the same answer 5020 ** given the same inputs. If two or more collating functions are registered 5021 ** to the same collation name (using different eTextRep values) then all 5022 ** must give an equivalent answer when invoked with equivalent strings. 5023 ** The collating function must obey the following properties for all 5024 ** strings A, B, and C: 5025 ** 5026 ** <ol> 5027 ** <li> If A==B then B==A. 5028 ** <li> If A==B and B==C then A==C. 5029 ** <li> If A<B THEN B>A. 5030 ** <li> If A<B and B<C then A<C. 5031 ** </ol> 5032 ** 5033 ** If a collating function fails any of the above constraints and that 5034 ** collating function is registered and used, then the behavior of SQLite 5035 ** is undefined. 5036 ** 5037 ** ^The sqlite3_create_collation_v2() works like sqlite3_create_collation() 5038 ** with the addition that the xDestroy callback is invoked on pArg when 5039 ** the collating function is deleted. 5040 ** ^Collating functions are deleted when they are overridden by later 5041 ** calls to the collation creation functions or when the 5042 ** [database connection] is closed using [sqlite3_close()]. 5043 ** 5044 ** ^The xDestroy callback is <u>not</u> called if the 5045 ** sqlite3_create_collation_v2() function fails. Applications that invoke 5046 ** sqlite3_create_collation_v2() with a non-NULL xDestroy argument should 5047 ** check the return code and dispose of the application data pointer 5048 ** themselves rather than expecting SQLite to deal with it for them. 5049 ** This is different from every other SQLite interface. The inconsistency 5050 ** is unfortunate but cannot be changed without breaking backwards 5051 ** compatibility. 5052 ** 5053 ** See also: [sqlite3_collation_needed()] and [sqlite3_collation_needed16()]. 5054 */ 5055 SQLITE_API int sqlite3_create_collation( 5056 sqlite3*, 5057 const char *zName, 5058 int eTextRep, 5059 void *pArg, 5060 int(*xCompare)(void*,int,const void*,int,const void*) 5061 ); 5062 SQLITE_API int sqlite3_create_collation_v2( 5063 sqlite3*, 5064 const char *zName, 5065 int eTextRep, 5066 void *pArg, 5067 int(*xCompare)(void*,int,const void*,int,const void*), 5068 void(*xDestroy)(void*) 5069 ); 5070 SQLITE_API int sqlite3_create_collation16( 5071 sqlite3*, 5072 const void *zName, 5073 int eTextRep, 5074 void *pArg, 5075 int(*xCompare)(void*,int,const void*,int,const void*) 5076 ); 5077 5078 /* 5079 ** CAPI3REF: Collation Needed Callbacks 5080 ** METHOD: sqlite3 5081 ** 5082 ** ^To avoid having to register all collation sequences before a database 5083 ** can be used, a single callback function may be registered with the 5084 ** [database connection] to be invoked whenever an undefined collation 5085 ** sequence is required. 5086 ** 5087 ** ^If the function is registered using the sqlite3_collation_needed() API, 5088 ** then it is passed the names of undefined collation sequences as strings 5089 ** encoded in UTF-8. ^If sqlite3_collation_needed16() is used, 5090 ** the names are passed as UTF-16 in machine native byte order. 5091 ** ^A call to either function replaces the existing collation-needed callback. 5092 ** 5093 ** ^(When the callback is invoked, the first argument passed is a copy 5094 ** of the second argument to sqlite3_collation_needed() or 5095 ** sqlite3_collation_needed16(). The second argument is the database 5096 ** connection. The third argument is one of [SQLITE_UTF8], [SQLITE_UTF16BE], 5097 ** or [SQLITE_UTF16LE], indicating the most desirable form of the collation 5098 ** sequence function required. The fourth parameter is the name of the 5099 ** required collation sequence.)^ 5100 ** 5101 ** The callback function should register the desired collation using 5102 ** [sqlite3_create_collation()], [sqlite3_create_collation16()], or 5103 ** [sqlite3_create_collation_v2()]. 5104 */ 5105 SQLITE_API int sqlite3_collation_needed( 5106 sqlite3*, 5107 void*, 5108 void(*)(void*,sqlite3*,int eTextRep,const char*) 5109 ); 5110 SQLITE_API int sqlite3_collation_needed16( 5111 sqlite3*, 5112 void*, 5113 void(*)(void*,sqlite3*,int eTextRep,const void*) 5114 ); 5115 5116 #ifdef SQLITE_HAS_CODEC 5117 /* 5118 ** Specify the key for an encrypted database. This routine should be 5119 ** called right after sqlite3_open(). 5120 ** 5121 ** The code to implement this API is not available in the public release 5122 ** of SQLite. 5123 */ 5124 SQLITE_API int sqlite3_key( 5125 sqlite3 *db, /* Database to be rekeyed */ 5126 const void *pKey, int nKey /* The key */ 5127 ); 5128 SQLITE_API int sqlite3_key_v2( 5129 sqlite3 *db, /* Database to be rekeyed */ 5130 const char *zDbName, /* Name of the database */ 5131 const void *pKey, int nKey /* The key */ 5132 ); 5133 5134 /* 5135 ** Change the key on an open database. If the current database is not 5136 ** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the 5137 ** database is decrypted. 5138 ** 5139 ** The code to implement this API is not available in the public release 5140 ** of SQLite. 5141 */ 5142 SQLITE_API int sqlite3_rekey( 5143 sqlite3 *db, /* Database to be rekeyed */ 5144 const void *pKey, int nKey /* The new key */ 5145 ); 5146 SQLITE_API int sqlite3_rekey_v2( 5147 sqlite3 *db, /* Database to be rekeyed */ 5148 const char *zDbName, /* Name of the database */ 5149 const void *pKey, int nKey /* The new key */ 5150 ); 5151 5152 /* 5153 ** Specify the activation key for a SEE database. Unless 5154 ** activated, none of the SEE routines will work. 5155 */ 5156 SQLITE_API void sqlite3_activate_see( 5157 const char *zPassPhrase /* Activation phrase */ 5158 ); 5159 #endif 5160 5161 #ifdef SQLITE_ENABLE_CEROD 5162 /* 5163 ** Specify the activation key for a CEROD database. Unless 5164 ** activated, none of the CEROD routines will work. 5165 */ 5166 SQLITE_API void sqlite3_activate_cerod( 5167 const char *zPassPhrase /* Activation phrase */ 5168 ); 5169 #endif 5170 5171 /* 5172 ** CAPI3REF: Suspend Execution For A Short Time 5173 ** 5174 ** The sqlite3_sleep() function causes the current thread to suspend execution 5175 ** for at least a number of milliseconds specified in its parameter. 5176 ** 5177 ** If the operating system does not support sleep requests with 5178 ** millisecond time resolution, then the time will be rounded up to 5179 ** the nearest second. The number of milliseconds of sleep actually 5180 ** requested from the operating system is returned. 5181 ** 5182 ** ^SQLite implements this interface by calling the xSleep() 5183 ** method of the default [sqlite3_vfs] object. If the xSleep() method 5184 ** of the default VFS is not implemented correctly, or not implemented at 5185 ** all, then the behavior of sqlite3_sleep() may deviate from the description 5186 ** in the previous paragraphs. 5187 */ 5188 SQLITE_API int sqlite3_sleep(int); 5189 5190 /* 5191 ** CAPI3REF: Name Of The Folder Holding Temporary Files 5192 ** 5193 ** ^(If this global variable is made to point to a string which is 5194 ** the name of a folder (a.k.a. directory), then all temporary files 5195 ** created by SQLite when using a built-in [sqlite3_vfs | VFS] 5196 ** will be placed in that directory.)^ ^If this variable 5197 ** is a NULL pointer, then SQLite performs a search for an appropriate 5198 ** temporary file directory. 5199 ** 5200 ** Applications are strongly discouraged from using this global variable. 5201 ** It is required to set a temporary folder on Windows Runtime (WinRT). 5202 ** But for all other platforms, it is highly recommended that applications 5203 ** neither read nor write this variable. This global variable is a relic 5204 ** that exists for backwards compatibility of legacy applications and should 5205 ** be avoided in new projects. 5206 ** 5207 ** It is not safe to read or modify this variable in more than one 5208 ** thread at a time. It is not safe to read or modify this variable 5209 ** if a [database connection] is being used at the same time in a separate 5210 ** thread. 5211 ** It is intended that this variable be set once 5212 ** as part of process initialization and before any SQLite interface 5213 ** routines have been called and that this variable remain unchanged 5214 ** thereafter. 5215 ** 5216 ** ^The [temp_store_directory pragma] may modify this variable and cause 5217 ** it to point to memory obtained from [sqlite3_malloc]. ^Furthermore, 5218 ** the [temp_store_directory pragma] always assumes that any string 5219 ** that this variable points to is held in memory obtained from 5220 ** [sqlite3_malloc] and the pragma may attempt to free that memory 5221 ** using [sqlite3_free]. 5222 ** Hence, if this variable is modified directly, either it should be 5223 ** made NULL or made to point to memory obtained from [sqlite3_malloc] 5224 ** or else the use of the [temp_store_directory pragma] should be avoided. 5225 ** Except when requested by the [temp_store_directory pragma], SQLite 5226 ** does not free the memory that sqlite3_temp_directory points to. If 5227 ** the application wants that memory to be freed, it must do 5228 ** so itself, taking care to only do so after all [database connection] 5229 ** objects have been destroyed. 5230 ** 5231 ** <b>Note to Windows Runtime users:</b> The temporary directory must be set 5232 ** prior to calling [sqlite3_open] or [sqlite3_open_v2]. Otherwise, various 5233 ** features that require the use of temporary files may fail. Here is an 5234 ** example of how to do this using C++ with the Windows Runtime: 5235 ** 5236 ** <blockquote><pre> 5237 ** LPCWSTR zPath = Windows::Storage::ApplicationData::Current-> 5238 ** TemporaryFolder->Path->Data(); 5239 ** char zPathBuf[MAX_PATH + 1]; 5240 ** memset(zPathBuf, 0, sizeof(zPathBuf)); 5241 ** WideCharToMultiByte(CP_UTF8, 0, zPath, -1, zPathBuf, sizeof(zPathBuf), 5242 ** NULL, NULL); 5243 ** sqlite3_temp_directory = sqlite3_mprintf("%s", zPathBuf); 5244 ** </pre></blockquote> 5245 */ 5246 SQLITE_API SQLITE_EXTERN char *sqlite3_temp_directory; 5247 5248 /* 5249 ** CAPI3REF: Name Of The Folder Holding Database Files 5250 ** 5251 ** ^(If this global variable is made to point to a string which is 5252 ** the name of a folder (a.k.a. directory), then all database files 5253 ** specified with a relative pathname and created or accessed by 5254 ** SQLite when using a built-in windows [sqlite3_vfs | VFS] will be assumed 5255 ** to be relative to that directory.)^ ^If this variable is a NULL 5256 ** pointer, then SQLite assumes that all database files specified 5257 ** with a relative pathname are relative to the current directory 5258 ** for the process. Only the windows VFS makes use of this global 5259 ** variable; it is ignored by the unix VFS. 5260 ** 5261 ** Changing the value of this variable while a database connection is 5262 ** open can result in a corrupt database. 5263 ** 5264 ** It is not safe to read or modify this variable in more than one 5265 ** thread at a time. It is not safe to read or modify this variable 5266 ** if a [database connection] is being used at the same time in a separate 5267 ** thread. 5268 ** It is intended that this variable be set once 5269 ** as part of process initialization and before any SQLite interface 5270 ** routines have been called and that this variable remain unchanged 5271 ** thereafter. 5272 ** 5273 ** ^The [data_store_directory pragma] may modify this variable and cause 5274 ** it to point to memory obtained from [sqlite3_malloc]. ^Furthermore, 5275 ** the [data_store_directory pragma] always assumes that any string 5276 ** that this variable points to is held in memory obtained from 5277 ** [sqlite3_malloc] and the pragma may attempt to free that memory 5278 ** using [sqlite3_free]. 5279 ** Hence, if this variable is modified directly, either it should be 5280 ** made NULL or made to point to memory obtained from [sqlite3_malloc] 5281 ** or else the use of the [data_store_directory pragma] should be avoided. 5282 */ 5283 SQLITE_API SQLITE_EXTERN char *sqlite3_data_directory; 5284 5285 /* 5286 ** CAPI3REF: Test For Auto-Commit Mode 5287 ** KEYWORDS: {autocommit mode} 5288 ** METHOD: sqlite3 5289 ** 5290 ** ^The sqlite3_get_autocommit() interface returns non-zero or 5291 ** zero if the given database connection is or is not in autocommit mode, 5292 ** respectively. ^Autocommit mode is on by default. 5293 ** ^Autocommit mode is disabled by a [BEGIN] statement. 5294 ** ^Autocommit mode is re-enabled by a [COMMIT] or [ROLLBACK]. 5295 ** 5296 ** If certain kinds of errors occur on a statement within a multi-statement 5297 ** transaction (errors including [SQLITE_FULL], [SQLITE_IOERR], 5298 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the 5299 ** transaction might be rolled back automatically. The only way to 5300 ** find out whether SQLite automatically rolled back the transaction after 5301 ** an error is to use this function. 5302 ** 5303 ** If another thread changes the autocommit status of the database 5304 ** connection while this routine is running, then the return value 5305 ** is undefined. 5306 */ 5307 SQLITE_API int sqlite3_get_autocommit(sqlite3*); 5308 5309 /* 5310 ** CAPI3REF: Find The Database Handle Of A Prepared Statement 5311 ** METHOD: sqlite3_stmt 5312 ** 5313 ** ^The sqlite3_db_handle interface returns the [database connection] handle 5314 ** to which a [prepared statement] belongs. ^The [database connection] 5315 ** returned by sqlite3_db_handle is the same [database connection] 5316 ** that was the first argument 5317 ** to the [sqlite3_prepare_v2()] call (or its variants) that was used to 5318 ** create the statement in the first place. 5319 */ 5320 SQLITE_API sqlite3 *sqlite3_db_handle(sqlite3_stmt*); 5321 5322 /* 5323 ** CAPI3REF: Return The Filename For A Database Connection 5324 ** METHOD: sqlite3 5325 ** 5326 ** ^The sqlite3_db_filename(D,N) interface returns a pointer to a filename 5327 ** associated with database N of connection D. ^The main database file 5328 ** has the name "main". If there is no attached database N on the database 5329 ** connection D, or if database N is a temporary or in-memory database, then 5330 ** a NULL pointer is returned. 5331 ** 5332 ** ^The filename returned by this function is the output of the 5333 ** xFullPathname method of the [VFS]. ^In other words, the filename 5334 ** will be an absolute pathname, even if the filename used 5335 ** to open the database originally was a URI or relative pathname. 5336 */ 5337 SQLITE_API const char *sqlite3_db_filename(sqlite3 *db, const char *zDbName); 5338 5339 /* 5340 ** CAPI3REF: Determine if a database is read-only 5341 ** METHOD: sqlite3 5342 ** 5343 ** ^The sqlite3_db_readonly(D,N) interface returns 1 if the database N 5344 ** of connection D is read-only, 0 if it is read/write, or -1 if N is not 5345 ** the name of a database on connection D. 5346 */ 5347 SQLITE_API int sqlite3_db_readonly(sqlite3 *db, const char *zDbName); 5348 5349 /* 5350 ** CAPI3REF: Find the next prepared statement 5351 ** METHOD: sqlite3 5352 ** 5353 ** ^This interface returns a pointer to the next [prepared statement] after 5354 ** pStmt associated with the [database connection] pDb. ^If pStmt is NULL 5355 ** then this interface returns a pointer to the first prepared statement 5356 ** associated with the database connection pDb. ^If no prepared statement 5357 ** satisfies the conditions of this routine, it returns NULL. 5358 ** 5359 ** The [database connection] pointer D in a call to 5360 ** [sqlite3_next_stmt(D,S)] must refer to an open database 5361 ** connection and in particular must not be a NULL pointer. 5362 */ 5363 SQLITE_API sqlite3_stmt *sqlite3_next_stmt(sqlite3 *pDb, sqlite3_stmt *pStmt); 5364 5365 /* 5366 ** CAPI3REF: Commit And Rollback Notification Callbacks 5367 ** METHOD: sqlite3 5368 ** 5369 ** ^The sqlite3_commit_hook() interface registers a callback 5370 ** function to be invoked whenever a transaction is [COMMIT | committed]. 5371 ** ^Any callback set by a previous call to sqlite3_commit_hook() 5372 ** for the same database connection is overridden. 5373 ** ^The sqlite3_rollback_hook() interface registers a callback 5374 ** function to be invoked whenever a transaction is [ROLLBACK | rolled back]. 5375 ** ^Any callback set by a previous call to sqlite3_rollback_hook() 5376 ** for the same database connection is overridden. 5377 ** ^The pArg argument is passed through to the callback. 5378 ** ^If the callback on a commit hook function returns non-zero, 5379 ** then the commit is converted into a rollback. 5380 ** 5381 ** ^The sqlite3_commit_hook(D,C,P) and sqlite3_rollback_hook(D,C,P) functions 5382 ** return the P argument from the previous call of the same function 5383 ** on the same [database connection] D, or NULL for 5384 ** the first call for each function on D. 5385 ** 5386 ** The commit and rollback hook callbacks are not reentrant. 5387 ** The callback implementation must not do anything that will modify 5388 ** the database connection that invoked the callback. Any actions 5389 ** to modify the database connection must be deferred until after the 5390 ** completion of the [sqlite3_step()] call that triggered the commit 5391 ** or rollback hook in the first place. 5392 ** Note that running any other SQL statements, including SELECT statements, 5393 ** or merely calling [sqlite3_prepare_v2()] and [sqlite3_step()] will modify 5394 ** the database connections for the meaning of "modify" in this paragraph. 5395 ** 5396 ** ^Registering a NULL function disables the callback. 5397 ** 5398 ** ^When the commit hook callback routine returns zero, the [COMMIT] 5399 ** operation is allowed to continue normally. ^If the commit hook 5400 ** returns non-zero, then the [COMMIT] is converted into a [ROLLBACK]. 5401 ** ^The rollback hook is invoked on a rollback that results from a commit 5402 ** hook returning non-zero, just as it would be with any other rollback. 5403 ** 5404 ** ^For the purposes of this API, a transaction is said to have been 5405 ** rolled back if an explicit "ROLLBACK" statement is executed, or 5406 ** an error or constraint causes an implicit rollback to occur. 5407 ** ^The rollback callback is not invoked if a transaction is 5408 ** automatically rolled back because the database connection is closed. 5409 ** 5410 ** See also the [sqlite3_update_hook()] interface. 5411 */ 5412 SQLITE_API void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*); 5413 SQLITE_API void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*); 5414 5415 /* 5416 ** CAPI3REF: Data Change Notification Callbacks 5417 ** METHOD: sqlite3 5418 ** 5419 ** ^The sqlite3_update_hook() interface registers a callback function 5420 ** with the [database connection] identified by the first argument 5421 ** to be invoked whenever a row is updated, inserted or deleted in 5422 ** a [rowid table]. 5423 ** ^Any callback set by a previous call to this function 5424 ** for the same database connection is overridden. 5425 ** 5426 ** ^The second argument is a pointer to the function to invoke when a 5427 ** row is updated, inserted or deleted in a rowid table. 5428 ** ^The first argument to the callback is a copy of the third argument 5429 ** to sqlite3_update_hook(). 5430 ** ^The second callback argument is one of [SQLITE_INSERT], [SQLITE_DELETE], 5431 ** or [SQLITE_UPDATE], depending on the operation that caused the callback 5432 ** to be invoked. 5433 ** ^The third and fourth arguments to the callback contain pointers to the 5434 ** database and table name containing the affected row. 5435 ** ^The final callback parameter is the [rowid] of the row. 5436 ** ^In the case of an update, this is the [rowid] after the update takes place. 5437 ** 5438 ** ^(The update hook is not invoked when internal system tables are 5439 ** modified (i.e. sqlite_master and sqlite_sequence).)^ 5440 ** ^The update hook is not invoked when [WITHOUT ROWID] tables are modified. 5441 ** 5442 ** ^In the current implementation, the update hook 5443 ** is not invoked when conflicting rows are deleted because of an 5444 ** [ON CONFLICT | ON CONFLICT REPLACE] clause. ^Nor is the update hook 5445 ** invoked when rows are deleted using the [truncate optimization]. 5446 ** The exceptions defined in this paragraph might change in a future 5447 ** release of SQLite. 5448 ** 5449 ** The update hook implementation must not do anything that will modify 5450 ** the database connection that invoked the update hook. Any actions 5451 ** to modify the database connection must be deferred until after the 5452 ** completion of the [sqlite3_step()] call that triggered the update hook. 5453 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their 5454 ** database connections for the meaning of "modify" in this paragraph. 5455 ** 5456 ** ^The sqlite3_update_hook(D,C,P) function 5457 ** returns the P argument from the previous call 5458 ** on the same [database connection] D, or NULL for 5459 ** the first call on D. 5460 ** 5461 ** See also the [sqlite3_commit_hook()], [sqlite3_rollback_hook()], 5462 ** and [sqlite3_preupdate_hook()] interfaces. 5463 */ 5464 SQLITE_API void *sqlite3_update_hook( 5465 sqlite3*, 5466 void(*)(void *,int ,char const *,char const *,sqlite3_int64), 5467 void* 5468 ); 5469 5470 /* 5471 ** CAPI3REF: Enable Or Disable Shared Pager Cache 5472 ** 5473 ** ^(This routine enables or disables the sharing of the database cache 5474 ** and schema data structures between [database connection | connections] 5475 ** to the same database. Sharing is enabled if the argument is true 5476 ** and disabled if the argument is false.)^ 5477 ** 5478 ** ^Cache sharing is enabled and disabled for an entire process. 5479 ** This is a change as of SQLite [version 3.5.0] ([dateof:3.5.0]). 5480 ** In prior versions of SQLite, 5481 ** sharing was enabled or disabled for each thread separately. 5482 ** 5483 ** ^(The cache sharing mode set by this interface effects all subsequent 5484 ** calls to [sqlite3_open()], [sqlite3_open_v2()], and [sqlite3_open16()]. 5485 ** Existing database connections continue use the sharing mode 5486 ** that was in effect at the time they were opened.)^ 5487 ** 5488 ** ^(This routine returns [SQLITE_OK] if shared cache was enabled or disabled 5489 ** successfully. An [error code] is returned otherwise.)^ 5490 ** 5491 ** ^Shared cache is disabled by default. But this might change in 5492 ** future releases of SQLite. Applications that care about shared 5493 ** cache setting should set it explicitly. 5494 ** 5495 ** Note: This method is disabled on MacOS X 10.7 and iOS version 5.0 5496 ** and will always return SQLITE_MISUSE. On those systems, 5497 ** shared cache mode should be enabled per-database connection via 5498 ** [sqlite3_open_v2()] with [SQLITE_OPEN_SHAREDCACHE]. 5499 ** 5500 ** This interface is threadsafe on processors where writing a 5501 ** 32-bit integer is atomic. 5502 ** 5503 ** See Also: [SQLite Shared-Cache Mode] 5504 */ 5505 SQLITE_API int sqlite3_enable_shared_cache(int); 5506 5507 /* 5508 ** CAPI3REF: Attempt To Free Heap Memory 5509 ** 5510 ** ^The sqlite3_release_memory() interface attempts to free N bytes 5511 ** of heap memory by deallocating non-essential memory allocations 5512 ** held by the database library. Memory used to cache database 5513 ** pages to improve performance is an example of non-essential memory. 5514 ** ^sqlite3_release_memory() returns the number of bytes actually freed, 5515 ** which might be more or less than the amount requested. 5516 ** ^The sqlite3_release_memory() routine is a no-op returning zero 5517 ** if SQLite is not compiled with [SQLITE_ENABLE_MEMORY_MANAGEMENT]. 5518 ** 5519 ** See also: [sqlite3_db_release_memory()] 5520 */ 5521 SQLITE_API int sqlite3_release_memory(int); 5522 5523 /* 5524 ** CAPI3REF: Free Memory Used By A Database Connection 5525 ** METHOD: sqlite3 5526 ** 5527 ** ^The sqlite3_db_release_memory(D) interface attempts to free as much heap 5528 ** memory as possible from database connection D. Unlike the 5529 ** [sqlite3_release_memory()] interface, this interface is in effect even 5530 ** when the [SQLITE_ENABLE_MEMORY_MANAGEMENT] compile-time option is 5531 ** omitted. 5532 ** 5533 ** See also: [sqlite3_release_memory()] 5534 */ 5535 SQLITE_API int sqlite3_db_release_memory(sqlite3*); 5536 5537 /* 5538 ** CAPI3REF: Impose A Limit On Heap Size 5539 ** 5540 ** ^The sqlite3_soft_heap_limit64() interface sets and/or queries the 5541 ** soft limit on the amount of heap memory that may be allocated by SQLite. 5542 ** ^SQLite strives to keep heap memory utilization below the soft heap 5543 ** limit by reducing the number of pages held in the page cache 5544 ** as heap memory usages approaches the limit. 5545 ** ^The soft heap limit is "soft" because even though SQLite strives to stay 5546 ** below the limit, it will exceed the limit rather than generate 5547 ** an [SQLITE_NOMEM] error. In other words, the soft heap limit 5548 ** is advisory only. 5549 ** 5550 ** ^The return value from sqlite3_soft_heap_limit64() is the size of 5551 ** the soft heap limit prior to the call, or negative in the case of an 5552 ** error. ^If the argument N is negative 5553 ** then no change is made to the soft heap limit. Hence, the current 5554 ** size of the soft heap limit can be determined by invoking 5555 ** sqlite3_soft_heap_limit64() with a negative argument. 5556 ** 5557 ** ^If the argument N is zero then the soft heap limit is disabled. 5558 ** 5559 ** ^(The soft heap limit is not enforced in the current implementation 5560 ** if one or more of following conditions are true: 5561 ** 5562 ** <ul> 5563 ** <li> The soft heap limit is set to zero. 5564 ** <li> Memory accounting is disabled using a combination of the 5565 ** [sqlite3_config]([SQLITE_CONFIG_MEMSTATUS],...) start-time option and 5566 ** the [SQLITE_DEFAULT_MEMSTATUS] compile-time option. 5567 ** <li> An alternative page cache implementation is specified using 5568 ** [sqlite3_config]([SQLITE_CONFIG_PCACHE2],...). 5569 ** <li> The page cache allocates from its own memory pool supplied 5570 ** by [sqlite3_config]([SQLITE_CONFIG_PAGECACHE],...) rather than 5571 ** from the heap. 5572 ** </ul>)^ 5573 ** 5574 ** Beginning with SQLite [version 3.7.3] ([dateof:3.7.3]), 5575 ** the soft heap limit is enforced 5576 ** regardless of whether or not the [SQLITE_ENABLE_MEMORY_MANAGEMENT] 5577 ** compile-time option is invoked. With [SQLITE_ENABLE_MEMORY_MANAGEMENT], 5578 ** the soft heap limit is enforced on every memory allocation. Without 5579 ** [SQLITE_ENABLE_MEMORY_MANAGEMENT], the soft heap limit is only enforced 5580 ** when memory is allocated by the page cache. Testing suggests that because 5581 ** the page cache is the predominate memory user in SQLite, most 5582 ** applications will achieve adequate soft heap limit enforcement without 5583 ** the use of [SQLITE_ENABLE_MEMORY_MANAGEMENT]. 5584 ** 5585 ** The circumstances under which SQLite will enforce the soft heap limit may 5586 ** changes in future releases of SQLite. 5587 */ 5588 SQLITE_API sqlite3_int64 sqlite3_soft_heap_limit64(sqlite3_int64 N); 5589 5590 /* 5591 ** CAPI3REF: Deprecated Soft Heap Limit Interface 5592 ** DEPRECATED 5593 ** 5594 ** This is a deprecated version of the [sqlite3_soft_heap_limit64()] 5595 ** interface. This routine is provided for historical compatibility 5596 ** only. All new applications should use the 5597 ** [sqlite3_soft_heap_limit64()] interface rather than this one. 5598 */ 5599 SQLITE_API SQLITE_DEPRECATED void sqlite3_soft_heap_limit(int N); 5600 5601 5602 /* 5603 ** CAPI3REF: Extract Metadata About A Column Of A Table 5604 ** METHOD: sqlite3 5605 ** 5606 ** ^(The sqlite3_table_column_metadata(X,D,T,C,....) routine returns 5607 ** information about column C of table T in database D 5608 ** on [database connection] X.)^ ^The sqlite3_table_column_metadata() 5609 ** interface returns SQLITE_OK and fills in the non-NULL pointers in 5610 ** the final five arguments with appropriate values if the specified 5611 ** column exists. ^The sqlite3_table_column_metadata() interface returns 5612 ** SQLITE_ERROR and if the specified column does not exist. 5613 ** ^If the column-name parameter to sqlite3_table_column_metadata() is a 5614 ** NULL pointer, then this routine simply checks for the existence of the 5615 ** table and returns SQLITE_OK if the table exists and SQLITE_ERROR if it 5616 ** does not. 5617 ** 5618 ** ^The column is identified by the second, third and fourth parameters to 5619 ** this function. ^(The second parameter is either the name of the database 5620 ** (i.e. "main", "temp", or an attached database) containing the specified 5621 ** table or NULL.)^ ^If it is NULL, then all attached databases are searched 5622 ** for the table using the same algorithm used by the database engine to 5623 ** resolve unqualified table references. 5624 ** 5625 ** ^The third and fourth parameters to this function are the table and column 5626 ** name of the desired column, respectively. 5627 ** 5628 ** ^Metadata is returned by writing to the memory locations passed as the 5th 5629 ** and subsequent parameters to this function. ^Any of these arguments may be 5630 ** NULL, in which case the corresponding element of metadata is omitted. 5631 ** 5632 ** ^(<blockquote> 5633 ** <table border="1"> 5634 ** <tr><th> Parameter <th> Output<br>Type <th> Description 5635 ** 5636 ** <tr><td> 5th <td> const char* <td> Data type 5637 ** <tr><td> 6th <td> const char* <td> Name of default collation sequence 5638 ** <tr><td> 7th <td> int <td> True if column has a NOT NULL constraint 5639 ** <tr><td> 8th <td> int <td> True if column is part of the PRIMARY KEY 5640 ** <tr><td> 9th <td> int <td> True if column is [AUTOINCREMENT] 5641 ** </table> 5642 ** </blockquote>)^ 5643 ** 5644 ** ^The memory pointed to by the character pointers returned for the 5645 ** declaration type and collation sequence is valid until the next 5646 ** call to any SQLite API function. 5647 ** 5648 ** ^If the specified table is actually a view, an [error code] is returned. 5649 ** 5650 ** ^If the specified column is "rowid", "oid" or "_rowid_" and the table 5651 ** is not a [WITHOUT ROWID] table and an 5652 ** [INTEGER PRIMARY KEY] column has been explicitly declared, then the output 5653 ** parameters are set for the explicitly declared column. ^(If there is no 5654 ** [INTEGER PRIMARY KEY] column, then the outputs 5655 ** for the [rowid] are set as follows: 5656 ** 5657 ** <pre> 5658 ** data type: "INTEGER" 5659 ** collation sequence: "BINARY" 5660 ** not null: 0 5661 ** primary key: 1 5662 ** auto increment: 0 5663 ** </pre>)^ 5664 ** 5665 ** ^This function causes all database schemas to be read from disk and 5666 ** parsed, if that has not already been done, and returns an error if 5667 ** any errors are encountered while loading the schema. 5668 */ 5669 SQLITE_API int sqlite3_table_column_metadata( 5670 sqlite3 *db, /* Connection handle */ 5671 const char *zDbName, /* Database name or NULL */ 5672 const char *zTableName, /* Table name */ 5673 const char *zColumnName, /* Column name */ 5674 char const **pzDataType, /* OUTPUT: Declared data type */ 5675 char const **pzCollSeq, /* OUTPUT: Collation sequence name */ 5676 int *pNotNull, /* OUTPUT: True if NOT NULL constraint exists */ 5677 int *pPrimaryKey, /* OUTPUT: True if column part of PK */ 5678 int *pAutoinc /* OUTPUT: True if column is auto-increment */ 5679 ); 5680 5681 /* 5682 ** CAPI3REF: Load An Extension 5683 ** METHOD: sqlite3 5684 ** 5685 ** ^This interface loads an SQLite extension library from the named file. 5686 ** 5687 ** ^The sqlite3_load_extension() interface attempts to load an 5688 ** [SQLite extension] library contained in the file zFile. If 5689 ** the file cannot be loaded directly, attempts are made to load 5690 ** with various operating-system specific extensions added. 5691 ** So for example, if "samplelib" cannot be loaded, then names like 5692 ** "samplelib.so" or "samplelib.dylib" or "samplelib.dll" might 5693 ** be tried also. 5694 ** 5695 ** ^The entry point is zProc. 5696 ** ^(zProc may be 0, in which case SQLite will try to come up with an 5697 ** entry point name on its own. It first tries "sqlite3_extension_init". 5698 ** If that does not work, it constructs a name "sqlite3_X_init" where the 5699 ** X is consists of the lower-case equivalent of all ASCII alphabetic 5700 ** characters in the filename from the last "/" to the first following 5701 ** "." and omitting any initial "lib".)^ 5702 ** ^The sqlite3_load_extension() interface returns 5703 ** [SQLITE_OK] on success and [SQLITE_ERROR] if something goes wrong. 5704 ** ^If an error occurs and pzErrMsg is not 0, then the 5705 ** [sqlite3_load_extension()] interface shall attempt to 5706 ** fill *pzErrMsg with error message text stored in memory 5707 ** obtained from [sqlite3_malloc()]. The calling function 5708 ** should free this memory by calling [sqlite3_free()]. 5709 ** 5710 ** ^Extension loading must be enabled using 5711 ** [sqlite3_enable_load_extension()] or 5712 ** [sqlite3_db_config](db,[SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION],1,NULL) 5713 ** prior to calling this API, 5714 ** otherwise an error will be returned. 5715 ** 5716 ** <b>Security warning:</b> It is recommended that the 5717 ** [SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION] method be used to enable only this 5718 ** interface. The use of the [sqlite3_enable_load_extension()] interface 5719 ** should be avoided. This will keep the SQL function [load_extension()] 5720 ** disabled and prevent SQL injections from giving attackers 5721 ** access to extension loading capabilities. 5722 ** 5723 ** See also the [load_extension() SQL function]. 5724 */ 5725 SQLITE_API int sqlite3_load_extension( 5726 sqlite3 *db, /* Load the extension into this database connection */ 5727 const char *zFile, /* Name of the shared library containing extension */ 5728 const char *zProc, /* Entry point. Derived from zFile if 0 */ 5729 char **pzErrMsg /* Put error message here if not 0 */ 5730 ); 5731 5732 /* 5733 ** CAPI3REF: Enable Or Disable Extension Loading 5734 ** METHOD: sqlite3 5735 ** 5736 ** ^So as not to open security holes in older applications that are 5737 ** unprepared to deal with [extension loading], and as a means of disabling 5738 ** [extension loading] while evaluating user-entered SQL, the following API 5739 ** is provided to turn the [sqlite3_load_extension()] mechanism on and off. 5740 ** 5741 ** ^Extension loading is off by default. 5742 ** ^Call the sqlite3_enable_load_extension() routine with onoff==1 5743 ** to turn extension loading on and call it with onoff==0 to turn 5744 ** it back off again. 5745 ** 5746 ** ^This interface enables or disables both the C-API 5747 ** [sqlite3_load_extension()] and the SQL function [load_extension()]. 5748 ** ^(Use [sqlite3_db_config](db,[SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION],..) 5749 ** to enable or disable only the C-API.)^ 5750 ** 5751 ** <b>Security warning:</b> It is recommended that extension loading 5752 ** be disabled using the [SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION] method 5753 ** rather than this interface, so the [load_extension()] SQL function 5754 ** remains disabled. This will prevent SQL injections from giving attackers 5755 ** access to extension loading capabilities. 5756 */ 5757 SQLITE_API int sqlite3_enable_load_extension(sqlite3 *db, int onoff); 5758 5759 /* 5760 ** CAPI3REF: Automatically Load Statically Linked Extensions 5761 ** 5762 ** ^This interface causes the xEntryPoint() function to be invoked for 5763 ** each new [database connection] that is created. The idea here is that 5764 ** xEntryPoint() is the entry point for a statically linked [SQLite extension] 5765 ** that is to be automatically loaded into all new database connections. 5766 ** 5767 ** ^(Even though the function prototype shows that xEntryPoint() takes 5768 ** no arguments and returns void, SQLite invokes xEntryPoint() with three 5769 ** arguments and expects an integer result as if the signature of the 5770 ** entry point where as follows: 5771 ** 5772 ** <blockquote><pre> 5773 ** int xEntryPoint( 5774 ** sqlite3 *db, 5775 ** const char **pzErrMsg, 5776 ** const struct sqlite3_api_routines *pThunk 5777 ** ); 5778 ** </pre></blockquote>)^ 5779 ** 5780 ** If the xEntryPoint routine encounters an error, it should make *pzErrMsg 5781 ** point to an appropriate error message (obtained from [sqlite3_mprintf()]) 5782 ** and return an appropriate [error code]. ^SQLite ensures that *pzErrMsg 5783 ** is NULL before calling the xEntryPoint(). ^SQLite will invoke 5784 ** [sqlite3_free()] on *pzErrMsg after xEntryPoint() returns. ^If any 5785 ** xEntryPoint() returns an error, the [sqlite3_open()], [sqlite3_open16()], 5786 ** or [sqlite3_open_v2()] call that provoked the xEntryPoint() will fail. 5787 ** 5788 ** ^Calling sqlite3_auto_extension(X) with an entry point X that is already 5789 ** on the list of automatic extensions is a harmless no-op. ^No entry point 5790 ** will be called more than once for each database connection that is opened. 5791 ** 5792 ** See also: [sqlite3_reset_auto_extension()] 5793 ** and [sqlite3_cancel_auto_extension()] 5794 */ 5795 SQLITE_API int sqlite3_auto_extension(void(*xEntryPoint)(void)); 5796 5797 /* 5798 ** CAPI3REF: Cancel Automatic Extension Loading 5799 ** 5800 ** ^The [sqlite3_cancel_auto_extension(X)] interface unregisters the 5801 ** initialization routine X that was registered using a prior call to 5802 ** [sqlite3_auto_extension(X)]. ^The [sqlite3_cancel_auto_extension(X)] 5803 ** routine returns 1 if initialization routine X was successfully 5804 ** unregistered and it returns 0 if X was not on the list of initialization 5805 ** routines. 5806 */ 5807 SQLITE_API int sqlite3_cancel_auto_extension(void(*xEntryPoint)(void)); 5808 5809 /* 5810 ** CAPI3REF: Reset Automatic Extension Loading 5811 ** 5812 ** ^This interface disables all automatic extensions previously 5813 ** registered using [sqlite3_auto_extension()]. 5814 */ 5815 SQLITE_API void sqlite3_reset_auto_extension(void); 5816 5817 /* 5818 ** The interface to the virtual-table mechanism is currently considered 5819 ** to be experimental. The interface might change in incompatible ways. 5820 ** If this is a problem for you, do not use the interface at this time. 5821 ** 5822 ** When the virtual-table mechanism stabilizes, we will declare the 5823 ** interface fixed, support it indefinitely, and remove this comment. 5824 */ 5825 5826 /* 5827 ** Structures used by the virtual table interface 5828 */ 5829 typedef struct sqlite3_vtab sqlite3_vtab; 5830 typedef struct sqlite3_index_info sqlite3_index_info; 5831 typedef struct sqlite3_vtab_cursor sqlite3_vtab_cursor; 5832 typedef struct sqlite3_module sqlite3_module; 5833 5834 /* 5835 ** CAPI3REF: Virtual Table Object 5836 ** KEYWORDS: sqlite3_module {virtual table module} 5837 ** 5838 ** This structure, sometimes called a "virtual table module", 5839 ** defines the implementation of a [virtual tables]. 5840 ** This structure consists mostly of methods for the module. 5841 ** 5842 ** ^A virtual table module is created by filling in a persistent 5843 ** instance of this structure and passing a pointer to that instance 5844 ** to [sqlite3_create_module()] or [sqlite3_create_module_v2()]. 5845 ** ^The registration remains valid until it is replaced by a different 5846 ** module or until the [database connection] closes. The content 5847 ** of this structure must not change while it is registered with 5848 ** any database connection. 5849 */ 5850 struct sqlite3_module { 5851 int iVersion; 5852 int (*xCreate)(sqlite3*, void *pAux, 5853 int argc, const char *const*argv, 5854 sqlite3_vtab **ppVTab, char**); 5855 int (*xConnect)(sqlite3*, void *pAux, 5856 int argc, const char *const*argv, 5857 sqlite3_vtab **ppVTab, char**); 5858 int (*xBestIndex)(sqlite3_vtab *pVTab, sqlite3_index_info*); 5859 int (*xDisconnect)(sqlite3_vtab *pVTab); 5860 int (*xDestroy)(sqlite3_vtab *pVTab); 5861 int (*xOpen)(sqlite3_vtab *pVTab, sqlite3_vtab_cursor **ppCursor); 5862 int (*xClose)(sqlite3_vtab_cursor*); 5863 int (*xFilter)(sqlite3_vtab_cursor*, int idxNum, const char *idxStr, 5864 int argc, sqlite3_value **argv); 5865 int (*xNext)(sqlite3_vtab_cursor*); 5866 int (*xEof)(sqlite3_vtab_cursor*); 5867 int (*xColumn)(sqlite3_vtab_cursor*, sqlite3_context*, int); 5868 int (*xRowid)(sqlite3_vtab_cursor*, sqlite3_int64 *pRowid); 5869 int (*xUpdate)(sqlite3_vtab *, int, sqlite3_value **, sqlite3_int64 *); 5870 int (*xBegin)(sqlite3_vtab *pVTab); 5871 int (*xSync)(sqlite3_vtab *pVTab); 5872 int (*xCommit)(sqlite3_vtab *pVTab); 5873 int (*xRollback)(sqlite3_vtab *pVTab); 5874 int (*xFindFunction)(sqlite3_vtab *pVtab, int nArg, const char *zName, 5875 void (**pxFunc)(sqlite3_context*,int,sqlite3_value**), 5876 void **ppArg); 5877 int (*xRename)(sqlite3_vtab *pVtab, const char *zNew); 5878 /* The methods above are in version 1 of the sqlite_module object. Those 5879 ** below are for version 2 and greater. */ 5880 int (*xSavepoint)(sqlite3_vtab *pVTab, int); 5881 int (*xRelease)(sqlite3_vtab *pVTab, int); 5882 int (*xRollbackTo)(sqlite3_vtab *pVTab, int); 5883 }; 5884 5885 /* 5886 ** CAPI3REF: Virtual Table Indexing Information 5887 ** KEYWORDS: sqlite3_index_info 5888 ** 5889 ** The sqlite3_index_info structure and its substructures is used as part 5890 ** of the [virtual table] interface to 5891 ** pass information into and receive the reply from the [xBestIndex] 5892 ** method of a [virtual table module]. The fields under **Inputs** are the 5893 ** inputs to xBestIndex and are read-only. xBestIndex inserts its 5894 ** results into the **Outputs** fields. 5895 ** 5896 ** ^(The aConstraint[] array records WHERE clause constraints of the form: 5897 ** 5898 ** <blockquote>column OP expr</blockquote> 5899 ** 5900 ** where OP is =, <, <=, >, or >=.)^ ^(The particular operator is 5901 ** stored in aConstraint[].op using one of the 5902 ** [SQLITE_INDEX_CONSTRAINT_EQ | SQLITE_INDEX_CONSTRAINT_ values].)^ 5903 ** ^(The index of the column is stored in 5904 ** aConstraint[].iColumn.)^ ^(aConstraint[].usable is TRUE if the 5905 ** expr on the right-hand side can be evaluated (and thus the constraint 5906 ** is usable) and false if it cannot.)^ 5907 ** 5908 ** ^The optimizer automatically inverts terms of the form "expr OP column" 5909 ** and makes other simplifications to the WHERE clause in an attempt to 5910 ** get as many WHERE clause terms into the form shown above as possible. 5911 ** ^The aConstraint[] array only reports WHERE clause terms that are 5912 ** relevant to the particular virtual table being queried. 5913 ** 5914 ** ^Information about the ORDER BY clause is stored in aOrderBy[]. 5915 ** ^Each term of aOrderBy records a column of the ORDER BY clause. 5916 ** 5917 ** The colUsed field indicates which columns of the virtual table may be 5918 ** required by the current scan. Virtual table columns are numbered from 5919 ** zero in the order in which they appear within the CREATE TABLE statement 5920 ** passed to sqlite3_declare_vtab(). For the first 63 columns (columns 0-62), 5921 ** the corresponding bit is set within the colUsed mask if the column may be 5922 ** required by SQLite. If the table has at least 64 columns and any column 5923 ** to the right of the first 63 is required, then bit 63 of colUsed is also 5924 ** set. In other words, column iCol may be required if the expression 5925 ** (colUsed & ((sqlite3_uint64)1 << (iCol>=63 ? 63 : iCol))) evaluates to 5926 ** non-zero. 5927 ** 5928 ** The [xBestIndex] method must fill aConstraintUsage[] with information 5929 ** about what parameters to pass to xFilter. ^If argvIndex>0 then 5930 ** the right-hand side of the corresponding aConstraint[] is evaluated 5931 ** and becomes the argvIndex-th entry in argv. ^(If aConstraintUsage[].omit 5932 ** is true, then the constraint is assumed to be fully handled by the 5933 ** virtual table and is not checked again by SQLite.)^ 5934 ** 5935 ** ^The idxNum and idxPtr values are recorded and passed into the 5936 ** [xFilter] method. 5937 ** ^[sqlite3_free()] is used to free idxPtr if and only if 5938 ** needToFreeIdxPtr is true. 5939 ** 5940 ** ^The orderByConsumed means that output from [xFilter]/[xNext] will occur in 5941 ** the correct order to satisfy the ORDER BY clause so that no separate 5942 ** sorting step is required. 5943 ** 5944 ** ^The estimatedCost value is an estimate of the cost of a particular 5945 ** strategy. A cost of N indicates that the cost of the strategy is similar 5946 ** to a linear scan of an SQLite table with N rows. A cost of log(N) 5947 ** indicates that the expense of the operation is similar to that of a 5948 ** binary search on a unique indexed field of an SQLite table with N rows. 5949 ** 5950 ** ^The estimatedRows value is an estimate of the number of rows that 5951 ** will be returned by the strategy. 5952 ** 5953 ** The xBestIndex method may optionally populate the idxFlags field with a 5954 ** mask of SQLITE_INDEX_SCAN_* flags. Currently there is only one such flag - 5955 ** SQLITE_INDEX_SCAN_UNIQUE. If the xBestIndex method sets this flag, SQLite 5956 ** assumes that the strategy may visit at most one row. 5957 ** 5958 ** Additionally, if xBestIndex sets the SQLITE_INDEX_SCAN_UNIQUE flag, then 5959 ** SQLite also assumes that if a call to the xUpdate() method is made as 5960 ** part of the same statement to delete or update a virtual table row and the 5961 ** implementation returns SQLITE_CONSTRAINT, then there is no need to rollback 5962 ** any database changes. In other words, if the xUpdate() returns 5963 ** SQLITE_CONSTRAINT, the database contents must be exactly as they were 5964 ** before xUpdate was called. By contrast, if SQLITE_INDEX_SCAN_UNIQUE is not 5965 ** set and xUpdate returns SQLITE_CONSTRAINT, any database changes made by 5966 ** the xUpdate method are automatically rolled back by SQLite. 5967 ** 5968 ** IMPORTANT: The estimatedRows field was added to the sqlite3_index_info 5969 ** structure for SQLite [version 3.8.2] ([dateof:3.8.2]). 5970 ** If a virtual table extension is 5971 ** used with an SQLite version earlier than 3.8.2, the results of attempting 5972 ** to read or write the estimatedRows field are undefined (but are likely 5973 ** to included crashing the application). The estimatedRows field should 5974 ** therefore only be used if [sqlite3_libversion_number()] returns a 5975 ** value greater than or equal to 3008002. Similarly, the idxFlags field 5976 ** was added for [version 3.9.0] ([dateof:3.9.0]). 5977 ** It may therefore only be used if 5978 ** sqlite3_libversion_number() returns a value greater than or equal to 5979 ** 3009000. 5980 */ 5981 struct sqlite3_index_info { 5982 /* Inputs */ 5983 int nConstraint; /* Number of entries in aConstraint */ 5984 struct sqlite3_index_constraint { 5985 int iColumn; /* Column constrained. -1 for ROWID */ 5986 unsigned char op; /* Constraint operator */ 5987 unsigned char usable; /* True if this constraint is usable */ 5988 int iTermOffset; /* Used internally - xBestIndex should ignore */ 5989 } *aConstraint; /* Table of WHERE clause constraints */ 5990 int nOrderBy; /* Number of terms in the ORDER BY clause */ 5991 struct sqlite3_index_orderby { 5992 int iColumn; /* Column number */ 5993 unsigned char desc; /* True for DESC. False for ASC. */ 5994 } *aOrderBy; /* The ORDER BY clause */ 5995 /* Outputs */ 5996 struct sqlite3_index_constraint_usage { 5997 int argvIndex; /* if >0, constraint is part of argv to xFilter */ 5998 unsigned char omit; /* Do not code a test for this constraint */ 5999 } *aConstraintUsage; 6000 int idxNum; /* Number used to identify the index */ 6001 char *idxStr; /* String, possibly obtained from sqlite3_malloc */ 6002 int needToFreeIdxStr; /* Free idxStr using sqlite3_free() if true */ 6003 int orderByConsumed; /* True if output is already ordered */ 6004 double estimatedCost; /* Estimated cost of using this index */ 6005 /* Fields below are only available in SQLite 3.8.2 and later */ 6006 sqlite3_int64 estimatedRows; /* Estimated number of rows returned */ 6007 /* Fields below are only available in SQLite 3.9.0 and later */ 6008 int idxFlags; /* Mask of SQLITE_INDEX_SCAN_* flags */ 6009 /* Fields below are only available in SQLite 3.10.0 and later */ 6010 sqlite3_uint64 colUsed; /* Input: Mask of columns used by statement */ 6011 }; 6012 6013 /* 6014 ** CAPI3REF: Virtual Table Scan Flags 6015 */ 6016 #define SQLITE_INDEX_SCAN_UNIQUE 1 /* Scan visits at most 1 row */ 6017 6018 /* 6019 ** CAPI3REF: Virtual Table Constraint Operator Codes 6020 ** 6021 ** These macros defined the allowed values for the 6022 ** [sqlite3_index_info].aConstraint[].op field. Each value represents 6023 ** an operator that is part of a constraint term in the wHERE clause of 6024 ** a query that uses a [virtual table]. 6025 */ 6026 #define SQLITE_INDEX_CONSTRAINT_EQ 2 6027 #define SQLITE_INDEX_CONSTRAINT_GT 4 6028 #define SQLITE_INDEX_CONSTRAINT_LE 8 6029 #define SQLITE_INDEX_CONSTRAINT_LT 16 6030 #define SQLITE_INDEX_CONSTRAINT_GE 32 6031 #define SQLITE_INDEX_CONSTRAINT_MATCH 64 6032 #define SQLITE_INDEX_CONSTRAINT_LIKE 65 6033 #define SQLITE_INDEX_CONSTRAINT_GLOB 66 6034 #define SQLITE_INDEX_CONSTRAINT_REGEXP 67 6035 6036 /* 6037 ** CAPI3REF: Register A Virtual Table Implementation 6038 ** METHOD: sqlite3 6039 ** 6040 ** ^These routines are used to register a new [virtual table module] name. 6041 ** ^Module names must be registered before 6042 ** creating a new [virtual table] using the module and before using a 6043 ** preexisting [virtual table] for the module. 6044 ** 6045 ** ^The module name is registered on the [database connection] specified 6046 ** by the first parameter. ^The name of the module is given by the 6047 ** second parameter. ^The third parameter is a pointer to 6048 ** the implementation of the [virtual table module]. ^The fourth 6049 ** parameter is an arbitrary client data pointer that is passed through 6050 ** into the [xCreate] and [xConnect] methods of the virtual table module 6051 ** when a new virtual table is be being created or reinitialized. 6052 ** 6053 ** ^The sqlite3_create_module_v2() interface has a fifth parameter which 6054 ** is a pointer to a destructor for the pClientData. ^SQLite will 6055 ** invoke the destructor function (if it is not NULL) when SQLite 6056 ** no longer needs the pClientData pointer. ^The destructor will also 6057 ** be invoked if the call to sqlite3_create_module_v2() fails. 6058 ** ^The sqlite3_create_module() 6059 ** interface is equivalent to sqlite3_create_module_v2() with a NULL 6060 ** destructor. 6061 */ 6062 SQLITE_API int sqlite3_create_module( 6063 sqlite3 *db, /* SQLite connection to register module with */ 6064 const char *zName, /* Name of the module */ 6065 const sqlite3_module *p, /* Methods for the module */ 6066 void *pClientData /* Client data for xCreate/xConnect */ 6067 ); 6068 SQLITE_API int sqlite3_create_module_v2( 6069 sqlite3 *db, /* SQLite connection to register module with */ 6070 const char *zName, /* Name of the module */ 6071 const sqlite3_module *p, /* Methods for the module */ 6072 void *pClientData, /* Client data for xCreate/xConnect */ 6073 void(*xDestroy)(void*) /* Module destructor function */ 6074 ); 6075 6076 /* 6077 ** CAPI3REF: Virtual Table Instance Object 6078 ** KEYWORDS: sqlite3_vtab 6079 ** 6080 ** Every [virtual table module] implementation uses a subclass 6081 ** of this object to describe a particular instance 6082 ** of the [virtual table]. Each subclass will 6083 ** be tailored to the specific needs of the module implementation. 6084 ** The purpose of this superclass is to define certain fields that are 6085 ** common to all module implementations. 6086 ** 6087 ** ^Virtual tables methods can set an error message by assigning a 6088 ** string obtained from [sqlite3_mprintf()] to zErrMsg. The method should 6089 ** take care that any prior string is freed by a call to [sqlite3_free()] 6090 ** prior to assigning a new string to zErrMsg. ^After the error message 6091 ** is delivered up to the client application, the string will be automatically 6092 ** freed by sqlite3_free() and the zErrMsg field will be zeroed. 6093 */ 6094 struct sqlite3_vtab { 6095 const sqlite3_module *pModule; /* The module for this virtual table */ 6096 int nRef; /* Number of open cursors */ 6097 char *zErrMsg; /* Error message from sqlite3_mprintf() */ 6098 /* Virtual table implementations will typically add additional fields */ 6099 }; 6100 6101 /* 6102 ** CAPI3REF: Virtual Table Cursor Object 6103 ** KEYWORDS: sqlite3_vtab_cursor {virtual table cursor} 6104 ** 6105 ** Every [virtual table module] implementation uses a subclass of the 6106 ** following structure to describe cursors that point into the 6107 ** [virtual table] and are used 6108 ** to loop through the virtual table. Cursors are created using the 6109 ** [sqlite3_module.xOpen | xOpen] method of the module and are destroyed 6110 ** by the [sqlite3_module.xClose | xClose] method. Cursors are used 6111 ** by the [xFilter], [xNext], [xEof], [xColumn], and [xRowid] methods 6112 ** of the module. Each module implementation will define 6113 ** the content of a cursor structure to suit its own needs. 6114 ** 6115 ** This superclass exists in order to define fields of the cursor that 6116 ** are common to all implementations. 6117 */ 6118 struct sqlite3_vtab_cursor { 6119 sqlite3_vtab *pVtab; /* Virtual table of this cursor */ 6120 /* Virtual table implementations will typically add additional fields */ 6121 }; 6122 6123 /* 6124 ** CAPI3REF: Declare The Schema Of A Virtual Table 6125 ** 6126 ** ^The [xCreate] and [xConnect] methods of a 6127 ** [virtual table module] call this interface 6128 ** to declare the format (the names and datatypes of the columns) of 6129 ** the virtual tables they implement. 6130 */ 6131 SQLITE_API int sqlite3_declare_vtab(sqlite3*, const char *zSQL); 6132 6133 /* 6134 ** CAPI3REF: Overload A Function For A Virtual Table 6135 ** METHOD: sqlite3 6136 ** 6137 ** ^(Virtual tables can provide alternative implementations of functions 6138 ** using the [xFindFunction] method of the [virtual table module]. 6139 ** But global versions of those functions 6140 ** must exist in order to be overloaded.)^ 6141 ** 6142 ** ^(This API makes sure a global version of a function with a particular 6143 ** name and number of parameters exists. If no such function exists 6144 ** before this API is called, a new function is created.)^ ^The implementation 6145 ** of the new function always causes an exception to be thrown. So 6146 ** the new function is not good for anything by itself. Its only 6147 ** purpose is to be a placeholder function that can be overloaded 6148 ** by a [virtual table]. 6149 */ 6150 SQLITE_API int sqlite3_overload_function(sqlite3*, const char *zFuncName, int nArg); 6151 6152 /* 6153 ** The interface to the virtual-table mechanism defined above (back up 6154 ** to a comment remarkably similar to this one) is currently considered 6155 ** to be experimental. The interface might change in incompatible ways. 6156 ** If this is a problem for you, do not use the interface at this time. 6157 ** 6158 ** When the virtual-table mechanism stabilizes, we will declare the 6159 ** interface fixed, support it indefinitely, and remove this comment. 6160 */ 6161 6162 /* 6163 ** CAPI3REF: A Handle To An Open BLOB 6164 ** KEYWORDS: {BLOB handle} {BLOB handles} 6165 ** 6166 ** An instance of this object represents an open BLOB on which 6167 ** [sqlite3_blob_open | incremental BLOB I/O] can be performed. 6168 ** ^Objects of this type are created by [sqlite3_blob_open()] 6169 ** and destroyed by [sqlite3_blob_close()]. 6170 ** ^The [sqlite3_blob_read()] and [sqlite3_blob_write()] interfaces 6171 ** can be used to read or write small subsections of the BLOB. 6172 ** ^The [sqlite3_blob_bytes()] interface returns the size of the BLOB in bytes. 6173 */ 6174 typedef struct sqlite3_blob sqlite3_blob; 6175 6176 /* 6177 ** CAPI3REF: Open A BLOB For Incremental I/O 6178 ** METHOD: sqlite3 6179 ** CONSTRUCTOR: sqlite3_blob 6180 ** 6181 ** ^(This interfaces opens a [BLOB handle | handle] to the BLOB located 6182 ** in row iRow, column zColumn, table zTable in database zDb; 6183 ** in other words, the same BLOB that would be selected by: 6184 ** 6185 ** <pre> 6186 ** SELECT zColumn FROM zDb.zTable WHERE [rowid] = iRow; 6187 ** </pre>)^ 6188 ** 6189 ** ^(Parameter zDb is not the filename that contains the database, but 6190 ** rather the symbolic name of the database. For attached databases, this is 6191 ** the name that appears after the AS keyword in the [ATTACH] statement. 6192 ** For the main database file, the database name is "main". For TEMP 6193 ** tables, the database name is "temp".)^ 6194 ** 6195 ** ^If the flags parameter is non-zero, then the BLOB is opened for read 6196 ** and write access. ^If the flags parameter is zero, the BLOB is opened for 6197 ** read-only access. 6198 ** 6199 ** ^(On success, [SQLITE_OK] is returned and the new [BLOB handle] is stored 6200 ** in *ppBlob. Otherwise an [error code] is returned and, unless the error 6201 ** code is SQLITE_MISUSE, *ppBlob is set to NULL.)^ ^This means that, provided 6202 ** the API is not misused, it is always safe to call [sqlite3_blob_close()] 6203 ** on *ppBlob after this function it returns. 6204 ** 6205 ** This function fails with SQLITE_ERROR if any of the following are true: 6206 ** <ul> 6207 ** <li> ^(Database zDb does not exist)^, 6208 ** <li> ^(Table zTable does not exist within database zDb)^, 6209 ** <li> ^(Table zTable is a WITHOUT ROWID table)^, 6210 ** <li> ^(Column zColumn does not exist)^, 6211 ** <li> ^(Row iRow is not present in the table)^, 6212 ** <li> ^(The specified column of row iRow contains a value that is not 6213 ** a TEXT or BLOB value)^, 6214 ** <li> ^(Column zColumn is part of an index, PRIMARY KEY or UNIQUE 6215 ** constraint and the blob is being opened for read/write access)^, 6216 ** <li> ^([foreign key constraints | Foreign key constraints] are enabled, 6217 ** column zColumn is part of a [child key] definition and the blob is 6218 ** being opened for read/write access)^. 6219 ** </ul> 6220 ** 6221 ** ^Unless it returns SQLITE_MISUSE, this function sets the 6222 ** [database connection] error code and message accessible via 6223 ** [sqlite3_errcode()] and [sqlite3_errmsg()] and related functions. 6224 ** 6225 ** A BLOB referenced by sqlite3_blob_open() may be read using the 6226 ** [sqlite3_blob_read()] interface and modified by using 6227 ** [sqlite3_blob_write()]. The [BLOB handle] can be moved to a 6228 ** different row of the same table using the [sqlite3_blob_reopen()] 6229 ** interface. However, the column, table, or database of a [BLOB handle] 6230 ** cannot be changed after the [BLOB handle] is opened. 6231 ** 6232 ** ^(If the row that a BLOB handle points to is modified by an 6233 ** [UPDATE], [DELETE], or by [ON CONFLICT] side-effects 6234 ** then the BLOB handle is marked as "expired". 6235 ** This is true if any column of the row is changed, even a column 6236 ** other than the one the BLOB handle is open on.)^ 6237 ** ^Calls to [sqlite3_blob_read()] and [sqlite3_blob_write()] for 6238 ** an expired BLOB handle fail with a return code of [SQLITE_ABORT]. 6239 ** ^(Changes written into a BLOB prior to the BLOB expiring are not 6240 ** rolled back by the expiration of the BLOB. Such changes will eventually 6241 ** commit if the transaction continues to completion.)^ 6242 ** 6243 ** ^Use the [sqlite3_blob_bytes()] interface to determine the size of 6244 ** the opened blob. ^The size of a blob may not be changed by this 6245 ** interface. Use the [UPDATE] SQL command to change the size of a 6246 ** blob. 6247 ** 6248 ** ^The [sqlite3_bind_zeroblob()] and [sqlite3_result_zeroblob()] interfaces 6249 ** and the built-in [zeroblob] SQL function may be used to create a 6250 ** zero-filled blob to read or write using the incremental-blob interface. 6251 ** 6252 ** To avoid a resource leak, every open [BLOB handle] should eventually 6253 ** be released by a call to [sqlite3_blob_close()]. 6254 ** 6255 ** See also: [sqlite3_blob_close()], 6256 ** [sqlite3_blob_reopen()], [sqlite3_blob_read()], 6257 ** [sqlite3_blob_bytes()], [sqlite3_blob_write()]. 6258 */ 6259 SQLITE_API int sqlite3_blob_open( 6260 sqlite3*, 6261 const char *zDb, 6262 const char *zTable, 6263 const char *zColumn, 6264 sqlite3_int64 iRow, 6265 int flags, 6266 sqlite3_blob **ppBlob 6267 ); 6268 6269 /* 6270 ** CAPI3REF: Move a BLOB Handle to a New Row 6271 ** METHOD: sqlite3_blob 6272 ** 6273 ** ^This function is used to move an existing [BLOB handle] so that it points 6274 ** to a different row of the same database table. ^The new row is identified 6275 ** by the rowid value passed as the second argument. Only the row can be 6276 ** changed. ^The database, table and column on which the blob handle is open 6277 ** remain the same. Moving an existing [BLOB handle] to a new row is 6278 ** faster than closing the existing handle and opening a new one. 6279 ** 6280 ** ^(The new row must meet the same criteria as for [sqlite3_blob_open()] - 6281 ** it must exist and there must be either a blob or text value stored in 6282 ** the nominated column.)^ ^If the new row is not present in the table, or if 6283 ** it does not contain a blob or text value, or if another error occurs, an 6284 ** SQLite error code is returned and the blob handle is considered aborted. 6285 ** ^All subsequent calls to [sqlite3_blob_read()], [sqlite3_blob_write()] or 6286 ** [sqlite3_blob_reopen()] on an aborted blob handle immediately return 6287 ** SQLITE_ABORT. ^Calling [sqlite3_blob_bytes()] on an aborted blob handle 6288 ** always returns zero. 6289 ** 6290 ** ^This function sets the database handle error code and message. 6291 */ 6292 SQLITE_API int sqlite3_blob_reopen(sqlite3_blob *, sqlite3_int64); 6293 6294 /* 6295 ** CAPI3REF: Close A BLOB Handle 6296 ** DESTRUCTOR: sqlite3_blob 6297 ** 6298 ** ^This function closes an open [BLOB handle]. ^(The BLOB handle is closed 6299 ** unconditionally. Even if this routine returns an error code, the 6300 ** handle is still closed.)^ 6301 ** 6302 ** ^If the blob handle being closed was opened for read-write access, and if 6303 ** the database is in auto-commit mode and there are no other open read-write 6304 ** blob handles or active write statements, the current transaction is 6305 ** committed. ^If an error occurs while committing the transaction, an error 6306 ** code is returned and the transaction rolled back. 6307 ** 6308 ** Calling this function with an argument that is not a NULL pointer or an 6309 ** open blob handle results in undefined behaviour. ^Calling this routine 6310 ** with a null pointer (such as would be returned by a failed call to 6311 ** [sqlite3_blob_open()]) is a harmless no-op. ^Otherwise, if this function 6312 ** is passed a valid open blob handle, the values returned by the 6313 ** sqlite3_errcode() and sqlite3_errmsg() functions are set before returning. 6314 */ 6315 SQLITE_API int sqlite3_blob_close(sqlite3_blob *); 6316 6317 /* 6318 ** CAPI3REF: Return The Size Of An Open BLOB 6319 ** METHOD: sqlite3_blob 6320 ** 6321 ** ^Returns the size in bytes of the BLOB accessible via the 6322 ** successfully opened [BLOB handle] in its only argument. ^The 6323 ** incremental blob I/O routines can only read or overwriting existing 6324 ** blob content; they cannot change the size of a blob. 6325 ** 6326 ** This routine only works on a [BLOB handle] which has been created 6327 ** by a prior successful call to [sqlite3_blob_open()] and which has not 6328 ** been closed by [sqlite3_blob_close()]. Passing any other pointer in 6329 ** to this routine results in undefined and probably undesirable behavior. 6330 */ 6331 SQLITE_API int sqlite3_blob_bytes(sqlite3_blob *); 6332 6333 /* 6334 ** CAPI3REF: Read Data From A BLOB Incrementally 6335 ** METHOD: sqlite3_blob 6336 ** 6337 ** ^(This function is used to read data from an open [BLOB handle] into a 6338 ** caller-supplied buffer. N bytes of data are copied into buffer Z 6339 ** from the open BLOB, starting at offset iOffset.)^ 6340 ** 6341 ** ^If offset iOffset is less than N bytes from the end of the BLOB, 6342 ** [SQLITE_ERROR] is returned and no data is read. ^If N or iOffset is 6343 ** less than zero, [SQLITE_ERROR] is returned and no data is read. 6344 ** ^The size of the blob (and hence the maximum value of N+iOffset) 6345 ** can be determined using the [sqlite3_blob_bytes()] interface. 6346 ** 6347 ** ^An attempt to read from an expired [BLOB handle] fails with an 6348 ** error code of [SQLITE_ABORT]. 6349 ** 6350 ** ^(On success, sqlite3_blob_read() returns SQLITE_OK. 6351 ** Otherwise, an [error code] or an [extended error code] is returned.)^ 6352 ** 6353 ** This routine only works on a [BLOB handle] which has been created 6354 ** by a prior successful call to [sqlite3_blob_open()] and which has not 6355 ** been closed by [sqlite3_blob_close()]. Passing any other pointer in 6356 ** to this routine results in undefined and probably undesirable behavior. 6357 ** 6358 ** See also: [sqlite3_blob_write()]. 6359 */ 6360 SQLITE_API int sqlite3_blob_read(sqlite3_blob *, void *Z, int N, int iOffset); 6361 6362 /* 6363 ** CAPI3REF: Write Data Into A BLOB Incrementally 6364 ** METHOD: sqlite3_blob 6365 ** 6366 ** ^(This function is used to write data into an open [BLOB handle] from a 6367 ** caller-supplied buffer. N bytes of data are copied from the buffer Z 6368 ** into the open BLOB, starting at offset iOffset.)^ 6369 ** 6370 ** ^(On success, sqlite3_blob_write() returns SQLITE_OK. 6371 ** Otherwise, an [error code] or an [extended error code] is returned.)^ 6372 ** ^Unless SQLITE_MISUSE is returned, this function sets the 6373 ** [database connection] error code and message accessible via 6374 ** [sqlite3_errcode()] and [sqlite3_errmsg()] and related functions. 6375 ** 6376 ** ^If the [BLOB handle] passed as the first argument was not opened for 6377 ** writing (the flags parameter to [sqlite3_blob_open()] was zero), 6378 ** this function returns [SQLITE_READONLY]. 6379 ** 6380 ** This function may only modify the contents of the BLOB; it is 6381 ** not possible to increase the size of a BLOB using this API. 6382 ** ^If offset iOffset is less than N bytes from the end of the BLOB, 6383 ** [SQLITE_ERROR] is returned and no data is written. The size of the 6384 ** BLOB (and hence the maximum value of N+iOffset) can be determined 6385 ** using the [sqlite3_blob_bytes()] interface. ^If N or iOffset are less 6386 ** than zero [SQLITE_ERROR] is returned and no data is written. 6387 ** 6388 ** ^An attempt to write to an expired [BLOB handle] fails with an 6389 ** error code of [SQLITE_ABORT]. ^Writes to the BLOB that occurred 6390 ** before the [BLOB handle] expired are not rolled back by the 6391 ** expiration of the handle, though of course those changes might 6392 ** have been overwritten by the statement that expired the BLOB handle 6393 ** or by other independent statements. 6394 ** 6395 ** This routine only works on a [BLOB handle] which has been created 6396 ** by a prior successful call to [sqlite3_blob_open()] and which has not 6397 ** been closed by [sqlite3_blob_close()]. Passing any other pointer in 6398 ** to this routine results in undefined and probably undesirable behavior. 6399 ** 6400 ** See also: [sqlite3_blob_read()]. 6401 */ 6402 SQLITE_API int sqlite3_blob_write(sqlite3_blob *, const void *z, int n, int iOffset); 6403 6404 /* 6405 ** CAPI3REF: Virtual File System Objects 6406 ** 6407 ** A virtual filesystem (VFS) is an [sqlite3_vfs] object 6408 ** that SQLite uses to interact 6409 ** with the underlying operating system. Most SQLite builds come with a 6410 ** single default VFS that is appropriate for the host computer. 6411 ** New VFSes can be registered and existing VFSes can be unregistered. 6412 ** The following interfaces are provided. 6413 ** 6414 ** ^The sqlite3_vfs_find() interface returns a pointer to a VFS given its name. 6415 ** ^Names are case sensitive. 6416 ** ^Names are zero-terminated UTF-8 strings. 6417 ** ^If there is no match, a NULL pointer is returned. 6418 ** ^If zVfsName is NULL then the default VFS is returned. 6419 ** 6420 ** ^New VFSes are registered with sqlite3_vfs_register(). 6421 ** ^Each new VFS becomes the default VFS if the makeDflt flag is set. 6422 ** ^The same VFS can be registered multiple times without injury. 6423 ** ^To make an existing VFS into the default VFS, register it again 6424 ** with the makeDflt flag set. If two different VFSes with the 6425 ** same name are registered, the behavior is undefined. If a 6426 ** VFS is registered with a name that is NULL or an empty string, 6427 ** then the behavior is undefined. 6428 ** 6429 ** ^Unregister a VFS with the sqlite3_vfs_unregister() interface. 6430 ** ^(If the default VFS is unregistered, another VFS is chosen as 6431 ** the default. The choice for the new VFS is arbitrary.)^ 6432 */ 6433 SQLITE_API sqlite3_vfs *sqlite3_vfs_find(const char *zVfsName); 6434 SQLITE_API int sqlite3_vfs_register(sqlite3_vfs*, int makeDflt); 6435 SQLITE_API int sqlite3_vfs_unregister(sqlite3_vfs*); 6436 6437 /* 6438 ** CAPI3REF: Mutexes 6439 ** 6440 ** The SQLite core uses these routines for thread 6441 ** synchronization. Though they are intended for internal 6442 ** use by SQLite, code that links against SQLite is 6443 ** permitted to use any of these routines. 6444 ** 6445 ** The SQLite source code contains multiple implementations 6446 ** of these mutex routines. An appropriate implementation 6447 ** is selected automatically at compile-time. The following 6448 ** implementations are available in the SQLite core: 6449 ** 6450 ** <ul> 6451 ** <li> SQLITE_MUTEX_PTHREADS 6452 ** <li> SQLITE_MUTEX_W32 6453 ** <li> SQLITE_MUTEX_NOOP 6454 ** </ul> 6455 ** 6456 ** The SQLITE_MUTEX_NOOP implementation is a set of routines 6457 ** that does no real locking and is appropriate for use in 6458 ** a single-threaded application. The SQLITE_MUTEX_PTHREADS and 6459 ** SQLITE_MUTEX_W32 implementations are appropriate for use on Unix 6460 ** and Windows. 6461 ** 6462 ** If SQLite is compiled with the SQLITE_MUTEX_APPDEF preprocessor 6463 ** macro defined (with "-DSQLITE_MUTEX_APPDEF=1"), then no mutex 6464 ** implementation is included with the library. In this case the 6465 ** application must supply a custom mutex implementation using the 6466 ** [SQLITE_CONFIG_MUTEX] option of the sqlite3_config() function 6467 ** before calling sqlite3_initialize() or any other public sqlite3_ 6468 ** function that calls sqlite3_initialize(). 6469 ** 6470 ** ^The sqlite3_mutex_alloc() routine allocates a new 6471 ** mutex and returns a pointer to it. ^The sqlite3_mutex_alloc() 6472 ** routine returns NULL if it is unable to allocate the requested 6473 ** mutex. The argument to sqlite3_mutex_alloc() must one of these 6474 ** integer constants: 6475 ** 6476 ** <ul> 6477 ** <li> SQLITE_MUTEX_FAST 6478 ** <li> SQLITE_MUTEX_RECURSIVE 6479 ** <li> SQLITE_MUTEX_STATIC_MASTER 6480 ** <li> SQLITE_MUTEX_STATIC_MEM 6481 ** <li> SQLITE_MUTEX_STATIC_OPEN 6482 ** <li> SQLITE_MUTEX_STATIC_PRNG 6483 ** <li> SQLITE_MUTEX_STATIC_LRU 6484 ** <li> SQLITE_MUTEX_STATIC_PMEM 6485 ** <li> SQLITE_MUTEX_STATIC_APP1 6486 ** <li> SQLITE_MUTEX_STATIC_APP2 6487 ** <li> SQLITE_MUTEX_STATIC_APP3 6488 ** <li> SQLITE_MUTEX_STATIC_VFS1 6489 ** <li> SQLITE_MUTEX_STATIC_VFS2 6490 ** <li> SQLITE_MUTEX_STATIC_VFS3 6491 ** </ul> 6492 ** 6493 ** ^The first two constants (SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE) 6494 ** cause sqlite3_mutex_alloc() to create 6495 ** a new mutex. ^The new mutex is recursive when SQLITE_MUTEX_RECURSIVE 6496 ** is used but not necessarily so when SQLITE_MUTEX_FAST is used. 6497 ** The mutex implementation does not need to make a distinction 6498 ** between SQLITE_MUTEX_RECURSIVE and SQLITE_MUTEX_FAST if it does 6499 ** not want to. SQLite will only request a recursive mutex in 6500 ** cases where it really needs one. If a faster non-recursive mutex 6501 ** implementation is available on the host platform, the mutex subsystem 6502 ** might return such a mutex in response to SQLITE_MUTEX_FAST. 6503 ** 6504 ** ^The other allowed parameters to sqlite3_mutex_alloc() (anything other 6505 ** than SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE) each return 6506 ** a pointer to a static preexisting mutex. ^Nine static mutexes are 6507 ** used by the current version of SQLite. Future versions of SQLite 6508 ** may add additional static mutexes. Static mutexes are for internal 6509 ** use by SQLite only. Applications that use SQLite mutexes should 6510 ** use only the dynamic mutexes returned by SQLITE_MUTEX_FAST or 6511 ** SQLITE_MUTEX_RECURSIVE. 6512 ** 6513 ** ^Note that if one of the dynamic mutex parameters (SQLITE_MUTEX_FAST 6514 ** or SQLITE_MUTEX_RECURSIVE) is used then sqlite3_mutex_alloc() 6515 ** returns a different mutex on every call. ^For the static 6516 ** mutex types, the same mutex is returned on every call that has 6517 ** the same type number. 6518 ** 6519 ** ^The sqlite3_mutex_free() routine deallocates a previously 6520 ** allocated dynamic mutex. Attempting to deallocate a static 6521 ** mutex results in undefined behavior. 6522 ** 6523 ** ^The sqlite3_mutex_enter() and sqlite3_mutex_try() routines attempt 6524 ** to enter a mutex. ^If another thread is already within the mutex, 6525 ** sqlite3_mutex_enter() will block and sqlite3_mutex_try() will return 6526 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK] 6527 ** upon successful entry. ^(Mutexes created using 6528 ** SQLITE_MUTEX_RECURSIVE can be entered multiple times by the same thread. 6529 ** In such cases, the 6530 ** mutex must be exited an equal number of times before another thread 6531 ** can enter.)^ If the same thread tries to enter any mutex other 6532 ** than an SQLITE_MUTEX_RECURSIVE more than once, the behavior is undefined. 6533 ** 6534 ** ^(Some systems (for example, Windows 95) do not support the operation 6535 ** implemented by sqlite3_mutex_try(). On those systems, sqlite3_mutex_try() 6536 ** will always return SQLITE_BUSY. The SQLite core only ever uses 6537 ** sqlite3_mutex_try() as an optimization so this is acceptable 6538 ** behavior.)^ 6539 ** 6540 ** ^The sqlite3_mutex_leave() routine exits a mutex that was 6541 ** previously entered by the same thread. The behavior 6542 ** is undefined if the mutex is not currently entered by the 6543 ** calling thread or is not currently allocated. 6544 ** 6545 ** ^If the argument to sqlite3_mutex_enter(), sqlite3_mutex_try(), or 6546 ** sqlite3_mutex_leave() is a NULL pointer, then all three routines 6547 ** behave as no-ops. 6548 ** 6549 ** See also: [sqlite3_mutex_held()] and [sqlite3_mutex_notheld()]. 6550 */ 6551 SQLITE_API sqlite3_mutex *sqlite3_mutex_alloc(int); 6552 SQLITE_API void sqlite3_mutex_free(sqlite3_mutex*); 6553 SQLITE_API void sqlite3_mutex_enter(sqlite3_mutex*); 6554 SQLITE_API int sqlite3_mutex_try(sqlite3_mutex*); 6555 SQLITE_API void sqlite3_mutex_leave(sqlite3_mutex*); 6556 6557 /* 6558 ** CAPI3REF: Mutex Methods Object 6559 ** 6560 ** An instance of this structure defines the low-level routines 6561 ** used to allocate and use mutexes. 6562 ** 6563 ** Usually, the default mutex implementations provided by SQLite are 6564 ** sufficient, however the application has the option of substituting a custom 6565 ** implementation for specialized deployments or systems for which SQLite 6566 ** does not provide a suitable implementation. In this case, the application 6567 ** creates and populates an instance of this structure to pass 6568 ** to sqlite3_config() along with the [SQLITE_CONFIG_MUTEX] option. 6569 ** Additionally, an instance of this structure can be used as an 6570 ** output variable when querying the system for the current mutex 6571 ** implementation, using the [SQLITE_CONFIG_GETMUTEX] option. 6572 ** 6573 ** ^The xMutexInit method defined by this structure is invoked as 6574 ** part of system initialization by the sqlite3_initialize() function. 6575 ** ^The xMutexInit routine is called by SQLite exactly once for each 6576 ** effective call to [sqlite3_initialize()]. 6577 ** 6578 ** ^The xMutexEnd method defined by this structure is invoked as 6579 ** part of system shutdown by the sqlite3_shutdown() function. The 6580 ** implementation of this method is expected to release all outstanding 6581 ** resources obtained by the mutex methods implementation, especially 6582 ** those obtained by the xMutexInit method. ^The xMutexEnd() 6583 ** interface is invoked exactly once for each call to [sqlite3_shutdown()]. 6584 ** 6585 ** ^(The remaining seven methods defined by this structure (xMutexAlloc, 6586 ** xMutexFree, xMutexEnter, xMutexTry, xMutexLeave, xMutexHeld and 6587 ** xMutexNotheld) implement the following interfaces (respectively): 6588 ** 6589 ** <ul> 6590 ** <li> [sqlite3_mutex_alloc()] </li> 6591 ** <li> [sqlite3_mutex_free()] </li> 6592 ** <li> [sqlite3_mutex_enter()] </li> 6593 ** <li> [sqlite3_mutex_try()] </li> 6594 ** <li> [sqlite3_mutex_leave()] </li> 6595 ** <li> [sqlite3_mutex_held()] </li> 6596 ** <li> [sqlite3_mutex_notheld()] </li> 6597 ** </ul>)^ 6598 ** 6599 ** The only difference is that the public sqlite3_XXX functions enumerated 6600 ** above silently ignore any invocations that pass a NULL pointer instead 6601 ** of a valid mutex handle. The implementations of the methods defined 6602 ** by this structure are not required to handle this case, the results 6603 ** of passing a NULL pointer instead of a valid mutex handle are undefined 6604 ** (i.e. it is acceptable to provide an implementation that segfaults if 6605 ** it is passed a NULL pointer). 6606 ** 6607 ** The xMutexInit() method must be threadsafe. It must be harmless to 6608 ** invoke xMutexInit() multiple times within the same process and without 6609 ** intervening calls to xMutexEnd(). Second and subsequent calls to 6610 ** xMutexInit() must be no-ops. 6611 ** 6612 ** xMutexInit() must not use SQLite memory allocation ([sqlite3_malloc()] 6613 ** and its associates). Similarly, xMutexAlloc() must not use SQLite memory 6614 ** allocation for a static mutex. ^However xMutexAlloc() may use SQLite 6615 ** memory allocation for a fast or recursive mutex. 6616 ** 6617 ** ^SQLite will invoke the xMutexEnd() method when [sqlite3_shutdown()] is 6618 ** called, but only if the prior call to xMutexInit returned SQLITE_OK. 6619 ** If xMutexInit fails in any way, it is expected to clean up after itself 6620 ** prior to returning. 6621 */ 6622 typedef struct sqlite3_mutex_methods sqlite3_mutex_methods; 6623 struct sqlite3_mutex_methods { 6624 int (*xMutexInit)(void); 6625 int (*xMutexEnd)(void); 6626 sqlite3_mutex *(*xMutexAlloc)(int); 6627 void (*xMutexFree)(sqlite3_mutex *); 6628 void (*xMutexEnter)(sqlite3_mutex *); 6629 int (*xMutexTry)(sqlite3_mutex *); 6630 void (*xMutexLeave)(sqlite3_mutex *); 6631 int (*xMutexHeld)(sqlite3_mutex *); 6632 int (*xMutexNotheld)(sqlite3_mutex *); 6633 }; 6634 6635 /* 6636 ** CAPI3REF: Mutex Verification Routines 6637 ** 6638 ** The sqlite3_mutex_held() and sqlite3_mutex_notheld() routines 6639 ** are intended for use inside assert() statements. The SQLite core 6640 ** never uses these routines except inside an assert() and applications 6641 ** are advised to follow the lead of the core. The SQLite core only 6642 ** provides implementations for these routines when it is compiled 6643 ** with the SQLITE_DEBUG flag. External mutex implementations 6644 ** are only required to provide these routines if SQLITE_DEBUG is 6645 ** defined and if NDEBUG is not defined. 6646 ** 6647 ** These routines should return true if the mutex in their argument 6648 ** is held or not held, respectively, by the calling thread. 6649 ** 6650 ** The implementation is not required to provide versions of these 6651 ** routines that actually work. If the implementation does not provide working 6652 ** versions of these routines, it should at least provide stubs that always 6653 ** return true so that one does not get spurious assertion failures. 6654 ** 6655 ** If the argument to sqlite3_mutex_held() is a NULL pointer then 6656 ** the routine should return 1. This seems counter-intuitive since 6657 ** clearly the mutex cannot be held if it does not exist. But 6658 ** the reason the mutex does not exist is because the build is not 6659 ** using mutexes. And we do not want the assert() containing the 6660 ** call to sqlite3_mutex_held() to fail, so a non-zero return is 6661 ** the appropriate thing to do. The sqlite3_mutex_notheld() 6662 ** interface should also return 1 when given a NULL pointer. 6663 */ 6664 #ifndef NDEBUG 6665 SQLITE_API int sqlite3_mutex_held(sqlite3_mutex*); 6666 SQLITE_API int sqlite3_mutex_notheld(sqlite3_mutex*); 6667 #endif 6668 6669 /* 6670 ** CAPI3REF: Mutex Types 6671 ** 6672 ** The [sqlite3_mutex_alloc()] interface takes a single argument 6673 ** which is one of these integer constants. 6674 ** 6675 ** The set of static mutexes may change from one SQLite release to the 6676 ** next. Applications that override the built-in mutex logic must be 6677 ** prepared to accommodate additional static mutexes. 6678 */ 6679 #define SQLITE_MUTEX_FAST 0 6680 #define SQLITE_MUTEX_RECURSIVE 1 6681 #define SQLITE_MUTEX_STATIC_MASTER 2 6682 #define SQLITE_MUTEX_STATIC_MEM 3 /* sqlite3_malloc() */ 6683 #define SQLITE_MUTEX_STATIC_MEM2 4 /* NOT USED */ 6684 #define SQLITE_MUTEX_STATIC_OPEN 4 /* sqlite3BtreeOpen() */ 6685 #define SQLITE_MUTEX_STATIC_PRNG 5 /* sqlite3_randomness() */ 6686 #define SQLITE_MUTEX_STATIC_LRU 6 /* lru page list */ 6687 #define SQLITE_MUTEX_STATIC_LRU2 7 /* NOT USED */ 6688 #define SQLITE_MUTEX_STATIC_PMEM 7 /* sqlite3PageMalloc() */ 6689 #define SQLITE_MUTEX_STATIC_APP1 8 /* For use by application */ 6690 #define SQLITE_MUTEX_STATIC_APP2 9 /* For use by application */ 6691 #define SQLITE_MUTEX_STATIC_APP3 10 /* For use by application */ 6692 #define SQLITE_MUTEX_STATIC_VFS1 11 /* For use by built-in VFS */ 6693 #define SQLITE_MUTEX_STATIC_VFS2 12 /* For use by extension VFS */ 6694 #define SQLITE_MUTEX_STATIC_VFS3 13 /* For use by application VFS */ 6695 6696 /* 6697 ** CAPI3REF: Retrieve the mutex for a database connection 6698 ** METHOD: sqlite3 6699 ** 6700 ** ^This interface returns a pointer the [sqlite3_mutex] object that 6701 ** serializes access to the [database connection] given in the argument 6702 ** when the [threading mode] is Serialized. 6703 ** ^If the [threading mode] is Single-thread or Multi-thread then this 6704 ** routine returns a NULL pointer. 6705 */ 6706 SQLITE_API sqlite3_mutex *sqlite3_db_mutex(sqlite3*); 6707 6708 /* 6709 ** CAPI3REF: Low-Level Control Of Database Files 6710 ** METHOD: sqlite3 6711 ** 6712 ** ^The [sqlite3_file_control()] interface makes a direct call to the 6713 ** xFileControl method for the [sqlite3_io_methods] object associated 6714 ** with a particular database identified by the second argument. ^The 6715 ** name of the database is "main" for the main database or "temp" for the 6716 ** TEMP database, or the name that appears after the AS keyword for 6717 ** databases that are added using the [ATTACH] SQL command. 6718 ** ^A NULL pointer can be used in place of "main" to refer to the 6719 ** main database file. 6720 ** ^The third and fourth parameters to this routine 6721 ** are passed directly through to the second and third parameters of 6722 ** the xFileControl method. ^The return value of the xFileControl 6723 ** method becomes the return value of this routine. 6724 ** 6725 ** ^The SQLITE_FCNTL_FILE_POINTER value for the op parameter causes 6726 ** a pointer to the underlying [sqlite3_file] object to be written into 6727 ** the space pointed to by the 4th parameter. ^The SQLITE_FCNTL_FILE_POINTER 6728 ** case is a short-circuit path which does not actually invoke the 6729 ** underlying sqlite3_io_methods.xFileControl method. 6730 ** 6731 ** ^If the second parameter (zDbName) does not match the name of any 6732 ** open database file, then SQLITE_ERROR is returned. ^This error 6733 ** code is not remembered and will not be recalled by [sqlite3_errcode()] 6734 ** or [sqlite3_errmsg()]. The underlying xFileControl method might 6735 ** also return SQLITE_ERROR. There is no way to distinguish between 6736 ** an incorrect zDbName and an SQLITE_ERROR return from the underlying 6737 ** xFileControl method. 6738 ** 6739 ** See also: [SQLITE_FCNTL_LOCKSTATE] 6740 */ 6741 SQLITE_API int sqlite3_file_control(sqlite3*, const char *zDbName, int op, void*); 6742 6743 /* 6744 ** CAPI3REF: Testing Interface 6745 ** 6746 ** ^The sqlite3_test_control() interface is used to read out internal 6747 ** state of SQLite and to inject faults into SQLite for testing 6748 ** purposes. ^The first parameter is an operation code that determines 6749 ** the number, meaning, and operation of all subsequent parameters. 6750 ** 6751 ** This interface is not for use by applications. It exists solely 6752 ** for verifying the correct operation of the SQLite library. Depending 6753 ** on how the SQLite library is compiled, this interface might not exist. 6754 ** 6755 ** The details of the operation codes, their meanings, the parameters 6756 ** they take, and what they do are all subject to change without notice. 6757 ** Unlike most of the SQLite API, this function is not guaranteed to 6758 ** operate consistently from one release to the next. 6759 */ 6760 SQLITE_API int sqlite3_test_control(int op, ...); 6761 6762 /* 6763 ** CAPI3REF: Testing Interface Operation Codes 6764 ** 6765 ** These constants are the valid operation code parameters used 6766 ** as the first argument to [sqlite3_test_control()]. 6767 ** 6768 ** These parameters and their meanings are subject to change 6769 ** without notice. These values are for testing purposes only. 6770 ** Applications should not use any of these parameters or the 6771 ** [sqlite3_test_control()] interface. 6772 */ 6773 #define SQLITE_TESTCTRL_FIRST 5 6774 #define SQLITE_TESTCTRL_PRNG_SAVE 5 6775 #define SQLITE_TESTCTRL_PRNG_RESTORE 6 6776 #define SQLITE_TESTCTRL_PRNG_RESET 7 6777 #define SQLITE_TESTCTRL_BITVEC_TEST 8 6778 #define SQLITE_TESTCTRL_FAULT_INSTALL 9 6779 #define SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS 10 6780 #define SQLITE_TESTCTRL_PENDING_BYTE 11 6781 #define SQLITE_TESTCTRL_ASSERT 12 6782 #define SQLITE_TESTCTRL_ALWAYS 13 6783 #define SQLITE_TESTCTRL_RESERVE 14 6784 #define SQLITE_TESTCTRL_OPTIMIZATIONS 15 6785 #define SQLITE_TESTCTRL_ISKEYWORD 16 6786 #define SQLITE_TESTCTRL_SCRATCHMALLOC 17 6787 #define SQLITE_TESTCTRL_LOCALTIME_FAULT 18 6788 #define SQLITE_TESTCTRL_EXPLAIN_STMT 19 /* NOT USED */ 6789 #define SQLITE_TESTCTRL_ONCE_RESET_THRESHOLD 19 6790 #define SQLITE_TESTCTRL_NEVER_CORRUPT 20 6791 #define SQLITE_TESTCTRL_VDBE_COVERAGE 21 6792 #define SQLITE_TESTCTRL_BYTEORDER 22 6793 #define SQLITE_TESTCTRL_ISINIT 23 6794 #define SQLITE_TESTCTRL_SORTER_MMAP 24 6795 #define SQLITE_TESTCTRL_IMPOSTER 25 6796 #define SQLITE_TESTCTRL_LAST 25 6797 6798 /* 6799 ** CAPI3REF: SQLite Runtime Status 6800 ** 6801 ** ^These interfaces are used to retrieve runtime status information 6802 ** about the performance of SQLite, and optionally to reset various 6803 ** highwater marks. ^The first argument is an integer code for 6804 ** the specific parameter to measure. ^(Recognized integer codes 6805 ** are of the form [status parameters | SQLITE_STATUS_...].)^ 6806 ** ^The current value of the parameter is returned into *pCurrent. 6807 ** ^The highest recorded value is returned in *pHighwater. ^If the 6808 ** resetFlag is true, then the highest record value is reset after 6809 ** *pHighwater is written. ^(Some parameters do not record the highest 6810 ** value. For those parameters 6811 ** nothing is written into *pHighwater and the resetFlag is ignored.)^ 6812 ** ^(Other parameters record only the highwater mark and not the current 6813 ** value. For these latter parameters nothing is written into *pCurrent.)^ 6814 ** 6815 ** ^The sqlite3_status() and sqlite3_status64() routines return 6816 ** SQLITE_OK on success and a non-zero [error code] on failure. 6817 ** 6818 ** If either the current value or the highwater mark is too large to 6819 ** be represented by a 32-bit integer, then the values returned by 6820 ** sqlite3_status() are undefined. 6821 ** 6822 ** See also: [sqlite3_db_status()] 6823 */ 6824 SQLITE_API int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetFlag); 6825 SQLITE_API int sqlite3_status64( 6826 int op, 6827 sqlite3_int64 *pCurrent, 6828 sqlite3_int64 *pHighwater, 6829 int resetFlag 6830 ); 6831 6832 6833 /* 6834 ** CAPI3REF: Status Parameters 6835 ** KEYWORDS: {status parameters} 6836 ** 6837 ** These integer constants designate various run-time status parameters 6838 ** that can be returned by [sqlite3_status()]. 6839 ** 6840 ** <dl> 6841 ** [[SQLITE_STATUS_MEMORY_USED]] ^(<dt>SQLITE_STATUS_MEMORY_USED</dt> 6842 ** <dd>This parameter is the current amount of memory checked out 6843 ** using [sqlite3_malloc()], either directly or indirectly. The 6844 ** figure includes calls made to [sqlite3_malloc()] by the application 6845 ** and internal memory usage by the SQLite library. Scratch memory 6846 ** controlled by [SQLITE_CONFIG_SCRATCH] and auxiliary page-cache 6847 ** memory controlled by [SQLITE_CONFIG_PAGECACHE] is not included in 6848 ** this parameter. The amount returned is the sum of the allocation 6849 ** sizes as reported by the xSize method in [sqlite3_mem_methods].</dd>)^ 6850 ** 6851 ** [[SQLITE_STATUS_MALLOC_SIZE]] ^(<dt>SQLITE_STATUS_MALLOC_SIZE</dt> 6852 ** <dd>This parameter records the largest memory allocation request 6853 ** handed to [sqlite3_malloc()] or [sqlite3_realloc()] (or their 6854 ** internal equivalents). Only the value returned in the 6855 ** *pHighwater parameter to [sqlite3_status()] is of interest. 6856 ** The value written into the *pCurrent parameter is undefined.</dd>)^ 6857 ** 6858 ** [[SQLITE_STATUS_MALLOC_COUNT]] ^(<dt>SQLITE_STATUS_MALLOC_COUNT</dt> 6859 ** <dd>This parameter records the number of separate memory allocations 6860 ** currently checked out.</dd>)^ 6861 ** 6862 ** [[SQLITE_STATUS_PAGECACHE_USED]] ^(<dt>SQLITE_STATUS_PAGECACHE_USED</dt> 6863 ** <dd>This parameter returns the number of pages used out of the 6864 ** [pagecache memory allocator] that was configured using 6865 ** [SQLITE_CONFIG_PAGECACHE]. The 6866 ** value returned is in pages, not in bytes.</dd>)^ 6867 ** 6868 ** [[SQLITE_STATUS_PAGECACHE_OVERFLOW]] 6869 ** ^(<dt>SQLITE_STATUS_PAGECACHE_OVERFLOW</dt> 6870 ** <dd>This parameter returns the number of bytes of page cache 6871 ** allocation which could not be satisfied by the [SQLITE_CONFIG_PAGECACHE] 6872 ** buffer and where forced to overflow to [sqlite3_malloc()]. The 6873 ** returned value includes allocations that overflowed because they 6874 ** where too large (they were larger than the "sz" parameter to 6875 ** [SQLITE_CONFIG_PAGECACHE]) and allocations that overflowed because 6876 ** no space was left in the page cache.</dd>)^ 6877 ** 6878 ** [[SQLITE_STATUS_PAGECACHE_SIZE]] ^(<dt>SQLITE_STATUS_PAGECACHE_SIZE</dt> 6879 ** <dd>This parameter records the largest memory allocation request 6880 ** handed to [pagecache memory allocator]. Only the value returned in the 6881 ** *pHighwater parameter to [sqlite3_status()] is of interest. 6882 ** The value written into the *pCurrent parameter is undefined.</dd>)^ 6883 ** 6884 ** [[SQLITE_STATUS_SCRATCH_USED]] ^(<dt>SQLITE_STATUS_SCRATCH_USED</dt> 6885 ** <dd>This parameter returns the number of allocations used out of the 6886 ** [scratch memory allocator] configured using 6887 ** [SQLITE_CONFIG_SCRATCH]. The value returned is in allocations, not 6888 ** in bytes. Since a single thread may only have one scratch allocation 6889 ** outstanding at time, this parameter also reports the number of threads 6890 ** using scratch memory at the same time.</dd>)^ 6891 ** 6892 ** [[SQLITE_STATUS_SCRATCH_OVERFLOW]] ^(<dt>SQLITE_STATUS_SCRATCH_OVERFLOW</dt> 6893 ** <dd>This parameter returns the number of bytes of scratch memory 6894 ** allocation which could not be satisfied by the [SQLITE_CONFIG_SCRATCH] 6895 ** buffer and where forced to overflow to [sqlite3_malloc()]. The values 6896 ** returned include overflows because the requested allocation was too 6897 ** larger (that is, because the requested allocation was larger than the 6898 ** "sz" parameter to [SQLITE_CONFIG_SCRATCH]) and because no scratch buffer 6899 ** slots were available. 6900 ** </dd>)^ 6901 ** 6902 ** [[SQLITE_STATUS_SCRATCH_SIZE]] ^(<dt>SQLITE_STATUS_SCRATCH_SIZE</dt> 6903 ** <dd>This parameter records the largest memory allocation request 6904 ** handed to [scratch memory allocator]. Only the value returned in the 6905 ** *pHighwater parameter to [sqlite3_status()] is of interest. 6906 ** The value written into the *pCurrent parameter is undefined.</dd>)^ 6907 ** 6908 ** [[SQLITE_STATUS_PARSER_STACK]] ^(<dt>SQLITE_STATUS_PARSER_STACK</dt> 6909 ** <dd>The *pHighwater parameter records the deepest parser stack. 6910 ** The *pCurrent value is undefined. The *pHighwater value is only 6911 ** meaningful if SQLite is compiled with [YYTRACKMAXSTACKDEPTH].</dd>)^ 6912 ** </dl> 6913 ** 6914 ** New status parameters may be added from time to time. 6915 */ 6916 #define SQLITE_STATUS_MEMORY_USED 0 6917 #define SQLITE_STATUS_PAGECACHE_USED 1 6918 #define SQLITE_STATUS_PAGECACHE_OVERFLOW 2 6919 #define SQLITE_STATUS_SCRATCH_USED 3 6920 #define SQLITE_STATUS_SCRATCH_OVERFLOW 4 6921 #define SQLITE_STATUS_MALLOC_SIZE 5 6922 #define SQLITE_STATUS_PARSER_STACK 6 6923 #define SQLITE_STATUS_PAGECACHE_SIZE 7 6924 #define SQLITE_STATUS_SCRATCH_SIZE 8 6925 #define SQLITE_STATUS_MALLOC_COUNT 9 6926 6927 /* 6928 ** CAPI3REF: Database Connection Status 6929 ** METHOD: sqlite3 6930 ** 6931 ** ^This interface is used to retrieve runtime status information 6932 ** about a single [database connection]. ^The first argument is the 6933 ** database connection object to be interrogated. ^The second argument 6934 ** is an integer constant, taken from the set of 6935 ** [SQLITE_DBSTATUS options], that 6936 ** determines the parameter to interrogate. The set of 6937 ** [SQLITE_DBSTATUS options] is likely 6938 ** to grow in future releases of SQLite. 6939 ** 6940 ** ^The current value of the requested parameter is written into *pCur 6941 ** and the highest instantaneous value is written into *pHiwtr. ^If 6942 ** the resetFlg is true, then the highest instantaneous value is 6943 ** reset back down to the current value. 6944 ** 6945 ** ^The sqlite3_db_status() routine returns SQLITE_OK on success and a 6946 ** non-zero [error code] on failure. 6947 ** 6948 ** See also: [sqlite3_status()] and [sqlite3_stmt_status()]. 6949 */ 6950 SQLITE_API int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int resetFlg); 6951 6952 /* 6953 ** CAPI3REF: Status Parameters for database connections 6954 ** KEYWORDS: {SQLITE_DBSTATUS options} 6955 ** 6956 ** These constants are the available integer "verbs" that can be passed as 6957 ** the second argument to the [sqlite3_db_status()] interface. 6958 ** 6959 ** New verbs may be added in future releases of SQLite. Existing verbs 6960 ** might be discontinued. Applications should check the return code from 6961 ** [sqlite3_db_status()] to make sure that the call worked. 6962 ** The [sqlite3_db_status()] interface will return a non-zero error code 6963 ** if a discontinued or unsupported verb is invoked. 6964 ** 6965 ** <dl> 6966 ** [[SQLITE_DBSTATUS_LOOKASIDE_USED]] ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_USED</dt> 6967 ** <dd>This parameter returns the number of lookaside memory slots currently 6968 ** checked out.</dd>)^ 6969 ** 6970 ** [[SQLITE_DBSTATUS_LOOKASIDE_HIT]] ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_HIT</dt> 6971 ** <dd>This parameter returns the number malloc attempts that were 6972 ** satisfied using lookaside memory. Only the high-water value is meaningful; 6973 ** the current value is always zero.)^ 6974 ** 6975 ** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE]] 6976 ** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE</dt> 6977 ** <dd>This parameter returns the number malloc attempts that might have 6978 ** been satisfied using lookaside memory but failed due to the amount of 6979 ** memory requested being larger than the lookaside slot size. 6980 ** Only the high-water value is meaningful; 6981 ** the current value is always zero.)^ 6982 ** 6983 ** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL]] 6984 ** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL</dt> 6985 ** <dd>This parameter returns the number malloc attempts that might have 6986 ** been satisfied using lookaside memory but failed due to all lookaside 6987 ** memory already being in use. 6988 ** Only the high-water value is meaningful; 6989 ** the current value is always zero.)^ 6990 ** 6991 ** [[SQLITE_DBSTATUS_CACHE_USED]] ^(<dt>SQLITE_DBSTATUS_CACHE_USED</dt> 6992 ** <dd>This parameter returns the approximate number of bytes of heap 6993 ** memory used by all pager caches associated with the database connection.)^ 6994 ** ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_USED is always 0. 6995 ** 6996 ** [[SQLITE_DBSTATUS_CACHE_USED_SHARED]] 6997 ** ^(<dt>SQLITE_DBSTATUS_CACHE_USED_SHARED</dt> 6998 ** <dd>This parameter is similar to DBSTATUS_CACHE_USED, except that if a 6999 ** pager cache is shared between two or more connections the bytes of heap 7000 ** memory used by that pager cache is divided evenly between the attached 7001 ** connections.)^ In other words, if none of the pager caches associated 7002 ** with the database connection are shared, this request returns the same 7003 ** value as DBSTATUS_CACHE_USED. Or, if one or more or the pager caches are 7004 ** shared, the value returned by this call will be smaller than that returned 7005 ** by DBSTATUS_CACHE_USED. ^The highwater mark associated with 7006 ** SQLITE_DBSTATUS_CACHE_USED_SHARED is always 0. 7007 ** 7008 ** [[SQLITE_DBSTATUS_SCHEMA_USED]] ^(<dt>SQLITE_DBSTATUS_SCHEMA_USED</dt> 7009 ** <dd>This parameter returns the approximate number of bytes of heap 7010 ** memory used to store the schema for all databases associated 7011 ** with the connection - main, temp, and any [ATTACH]-ed databases.)^ 7012 ** ^The full amount of memory used by the schemas is reported, even if the 7013 ** schema memory is shared with other database connections due to 7014 ** [shared cache mode] being enabled. 7015 ** ^The highwater mark associated with SQLITE_DBSTATUS_SCHEMA_USED is always 0. 7016 ** 7017 ** [[SQLITE_DBSTATUS_STMT_USED]] ^(<dt>SQLITE_DBSTATUS_STMT_USED</dt> 7018 ** <dd>This parameter returns the approximate number of bytes of heap 7019 ** and lookaside memory used by all prepared statements associated with 7020 ** the database connection.)^ 7021 ** ^The highwater mark associated with SQLITE_DBSTATUS_STMT_USED is always 0. 7022 ** </dd> 7023 ** 7024 ** [[SQLITE_DBSTATUS_CACHE_HIT]] ^(<dt>SQLITE_DBSTATUS_CACHE_HIT</dt> 7025 ** <dd>This parameter returns the number of pager cache hits that have 7026 ** occurred.)^ ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_HIT 7027 ** is always 0. 7028 ** </dd> 7029 ** 7030 ** [[SQLITE_DBSTATUS_CACHE_MISS]] ^(<dt>SQLITE_DBSTATUS_CACHE_MISS</dt> 7031 ** <dd>This parameter returns the number of pager cache misses that have 7032 ** occurred.)^ ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_MISS 7033 ** is always 0. 7034 ** </dd> 7035 ** 7036 ** [[SQLITE_DBSTATUS_CACHE_WRITE]] ^(<dt>SQLITE_DBSTATUS_CACHE_WRITE</dt> 7037 ** <dd>This parameter returns the number of dirty cache entries that have 7038 ** been written to disk. Specifically, the number of pages written to the 7039 ** wal file in wal mode databases, or the number of pages written to the 7040 ** database file in rollback mode databases. Any pages written as part of 7041 ** transaction rollback or database recovery operations are not included. 7042 ** If an IO or other error occurs while writing a page to disk, the effect 7043 ** on subsequent SQLITE_DBSTATUS_CACHE_WRITE requests is undefined.)^ ^The 7044 ** highwater mark associated with SQLITE_DBSTATUS_CACHE_WRITE is always 0. 7045 ** </dd> 7046 ** 7047 ** [[SQLITE_DBSTATUS_DEFERRED_FKS]] ^(<dt>SQLITE_DBSTATUS_DEFERRED_FKS</dt> 7048 ** <dd>This parameter returns zero for the current value if and only if 7049 ** all foreign key constraints (deferred or immediate) have been 7050 ** resolved.)^ ^The highwater mark is always 0. 7051 ** </dd> 7052 ** </dl> 7053 */ 7054 #define SQLITE_DBSTATUS_LOOKASIDE_USED 0 7055 #define SQLITE_DBSTATUS_CACHE_USED 1 7056 #define SQLITE_DBSTATUS_SCHEMA_USED 2 7057 #define SQLITE_DBSTATUS_STMT_USED 3 7058 #define SQLITE_DBSTATUS_LOOKASIDE_HIT 4 7059 #define SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE 5 7060 #define SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL 6 7061 #define SQLITE_DBSTATUS_CACHE_HIT 7 7062 #define SQLITE_DBSTATUS_CACHE_MISS 8 7063 #define SQLITE_DBSTATUS_CACHE_WRITE 9 7064 #define SQLITE_DBSTATUS_DEFERRED_FKS 10 7065 #define SQLITE_DBSTATUS_CACHE_USED_SHARED 11 7066 #define SQLITE_DBSTATUS_MAX 11 /* Largest defined DBSTATUS */ 7067 7068 7069 /* 7070 ** CAPI3REF: Prepared Statement Status 7071 ** METHOD: sqlite3_stmt 7072 ** 7073 ** ^(Each prepared statement maintains various 7074 ** [SQLITE_STMTSTATUS counters] that measure the number 7075 ** of times it has performed specific operations.)^ These counters can 7076 ** be used to monitor the performance characteristics of the prepared 7077 ** statements. For example, if the number of table steps greatly exceeds 7078 ** the number of table searches or result rows, that would tend to indicate 7079 ** that the prepared statement is using a full table scan rather than 7080 ** an index. 7081 ** 7082 ** ^(This interface is used to retrieve and reset counter values from 7083 ** a [prepared statement]. The first argument is the prepared statement 7084 ** object to be interrogated. The second argument 7085 ** is an integer code for a specific [SQLITE_STMTSTATUS counter] 7086 ** to be interrogated.)^ 7087 ** ^The current value of the requested counter is returned. 7088 ** ^If the resetFlg is true, then the counter is reset to zero after this 7089 ** interface call returns. 7090 ** 7091 ** See also: [sqlite3_status()] and [sqlite3_db_status()]. 7092 */ 7093 SQLITE_API int sqlite3_stmt_status(sqlite3_stmt*, int op,int resetFlg); 7094 7095 /* 7096 ** CAPI3REF: Status Parameters for prepared statements 7097 ** KEYWORDS: {SQLITE_STMTSTATUS counter} {SQLITE_STMTSTATUS counters} 7098 ** 7099 ** These preprocessor macros define integer codes that name counter 7100 ** values associated with the [sqlite3_stmt_status()] interface. 7101 ** The meanings of the various counters are as follows: 7102 ** 7103 ** <dl> 7104 ** [[SQLITE_STMTSTATUS_FULLSCAN_STEP]] <dt>SQLITE_STMTSTATUS_FULLSCAN_STEP</dt> 7105 ** <dd>^This is the number of times that SQLite has stepped forward in 7106 ** a table as part of a full table scan. Large numbers for this counter 7107 ** may indicate opportunities for performance improvement through 7108 ** careful use of indices.</dd> 7109 ** 7110 ** [[SQLITE_STMTSTATUS_SORT]] <dt>SQLITE_STMTSTATUS_SORT</dt> 7111 ** <dd>^This is the number of sort operations that have occurred. 7112 ** A non-zero value in this counter may indicate an opportunity to 7113 ** improvement performance through careful use of indices.</dd> 7114 ** 7115 ** [[SQLITE_STMTSTATUS_AUTOINDEX]] <dt>SQLITE_STMTSTATUS_AUTOINDEX</dt> 7116 ** <dd>^This is the number of rows inserted into transient indices that 7117 ** were created automatically in order to help joins run faster. 7118 ** A non-zero value in this counter may indicate an opportunity to 7119 ** improvement performance by adding permanent indices that do not 7120 ** need to be reinitialized each time the statement is run.</dd> 7121 ** 7122 ** [[SQLITE_STMTSTATUS_VM_STEP]] <dt>SQLITE_STMTSTATUS_VM_STEP</dt> 7123 ** <dd>^This is the number of virtual machine operations executed 7124 ** by the prepared statement if that number is less than or equal 7125 ** to 2147483647. The number of virtual machine operations can be 7126 ** used as a proxy for the total work done by the prepared statement. 7127 ** If the number of virtual machine operations exceeds 2147483647 7128 ** then the value returned by this statement status code is undefined. 7129 ** </dd> 7130 ** </dl> 7131 */ 7132 #define SQLITE_STMTSTATUS_FULLSCAN_STEP 1 7133 #define SQLITE_STMTSTATUS_SORT 2 7134 #define SQLITE_STMTSTATUS_AUTOINDEX 3 7135 #define SQLITE_STMTSTATUS_VM_STEP 4 7136 7137 /* 7138 ** CAPI3REF: Custom Page Cache Object 7139 ** 7140 ** The sqlite3_pcache type is opaque. It is implemented by 7141 ** the pluggable module. The SQLite core has no knowledge of 7142 ** its size or internal structure and never deals with the 7143 ** sqlite3_pcache object except by holding and passing pointers 7144 ** to the object. 7145 ** 7146 ** See [sqlite3_pcache_methods2] for additional information. 7147 */ 7148 typedef struct sqlite3_pcache sqlite3_pcache; 7149 7150 /* 7151 ** CAPI3REF: Custom Page Cache Object 7152 ** 7153 ** The sqlite3_pcache_page object represents a single page in the 7154 ** page cache. The page cache will allocate instances of this 7155 ** object. Various methods of the page cache use pointers to instances 7156 ** of this object as parameters or as their return value. 7157 ** 7158 ** See [sqlite3_pcache_methods2] for additional information. 7159 */ 7160 typedef struct sqlite3_pcache_page sqlite3_pcache_page; 7161 struct sqlite3_pcache_page { 7162 void *pBuf; /* The content of the page */ 7163 void *pExtra; /* Extra information associated with the page */ 7164 }; 7165 7166 /* 7167 ** CAPI3REF: Application Defined Page Cache. 7168 ** KEYWORDS: {page cache} 7169 ** 7170 ** ^(The [sqlite3_config]([SQLITE_CONFIG_PCACHE2], ...) interface can 7171 ** register an alternative page cache implementation by passing in an 7172 ** instance of the sqlite3_pcache_methods2 structure.)^ 7173 ** In many applications, most of the heap memory allocated by 7174 ** SQLite is used for the page cache. 7175 ** By implementing a 7176 ** custom page cache using this API, an application can better control 7177 ** the amount of memory consumed by SQLite, the way in which 7178 ** that memory is allocated and released, and the policies used to 7179 ** determine exactly which parts of a database file are cached and for 7180 ** how long. 7181 ** 7182 ** The alternative page cache mechanism is an 7183 ** extreme measure that is only needed by the most demanding applications. 7184 ** The built-in page cache is recommended for most uses. 7185 ** 7186 ** ^(The contents of the sqlite3_pcache_methods2 structure are copied to an 7187 ** internal buffer by SQLite within the call to [sqlite3_config]. Hence 7188 ** the application may discard the parameter after the call to 7189 ** [sqlite3_config()] returns.)^ 7190 ** 7191 ** [[the xInit() page cache method]] 7192 ** ^(The xInit() method is called once for each effective 7193 ** call to [sqlite3_initialize()])^ 7194 ** (usually only once during the lifetime of the process). ^(The xInit() 7195 ** method is passed a copy of the sqlite3_pcache_methods2.pArg value.)^ 7196 ** The intent of the xInit() method is to set up global data structures 7197 ** required by the custom page cache implementation. 7198 ** ^(If the xInit() method is NULL, then the 7199 ** built-in default page cache is used instead of the application defined 7200 ** page cache.)^ 7201 ** 7202 ** [[the xShutdown() page cache method]] 7203 ** ^The xShutdown() method is called by [sqlite3_shutdown()]. 7204 ** It can be used to clean up 7205 ** any outstanding resources before process shutdown, if required. 7206 ** ^The xShutdown() method may be NULL. 7207 ** 7208 ** ^SQLite automatically serializes calls to the xInit method, 7209 ** so the xInit method need not be threadsafe. ^The 7210 ** xShutdown method is only called from [sqlite3_shutdown()] so it does 7211 ** not need to be threadsafe either. All other methods must be threadsafe 7212 ** in multithreaded applications. 7213 ** 7214 ** ^SQLite will never invoke xInit() more than once without an intervening 7215 ** call to xShutdown(). 7216 ** 7217 ** [[the xCreate() page cache methods]] 7218 ** ^SQLite invokes the xCreate() method to construct a new cache instance. 7219 ** SQLite will typically create one cache instance for each open database file, 7220 ** though this is not guaranteed. ^The 7221 ** first parameter, szPage, is the size in bytes of the pages that must 7222 ** be allocated by the cache. ^szPage will always a power of two. ^The 7223 ** second parameter szExtra is a number of bytes of extra storage 7224 ** associated with each page cache entry. ^The szExtra parameter will 7225 ** a number less than 250. SQLite will use the 7226 ** extra szExtra bytes on each page to store metadata about the underlying 7227 ** database page on disk. The value passed into szExtra depends 7228 ** on the SQLite version, the target platform, and how SQLite was compiled. 7229 ** ^The third argument to xCreate(), bPurgeable, is true if the cache being 7230 ** created will be used to cache database pages of a file stored on disk, or 7231 ** false if it is used for an in-memory database. The cache implementation 7232 ** does not have to do anything special based with the value of bPurgeable; 7233 ** it is purely advisory. ^On a cache where bPurgeable is false, SQLite will 7234 ** never invoke xUnpin() except to deliberately delete a page. 7235 ** ^In other words, calls to xUnpin() on a cache with bPurgeable set to 7236 ** false will always have the "discard" flag set to true. 7237 ** ^Hence, a cache created with bPurgeable false will 7238 ** never contain any unpinned pages. 7239 ** 7240 ** [[the xCachesize() page cache method]] 7241 ** ^(The xCachesize() method may be called at any time by SQLite to set the 7242 ** suggested maximum cache-size (number of pages stored by) the cache 7243 ** instance passed as the first argument. This is the value configured using 7244 ** the SQLite "[PRAGMA cache_size]" command.)^ As with the bPurgeable 7245 ** parameter, the implementation is not required to do anything with this 7246 ** value; it is advisory only. 7247 ** 7248 ** [[the xPagecount() page cache methods]] 7249 ** The xPagecount() method must return the number of pages currently 7250 ** stored in the cache, both pinned and unpinned. 7251 ** 7252 ** [[the xFetch() page cache methods]] 7253 ** The xFetch() method locates a page in the cache and returns a pointer to 7254 ** an sqlite3_pcache_page object associated with that page, or a NULL pointer. 7255 ** The pBuf element of the returned sqlite3_pcache_page object will be a 7256 ** pointer to a buffer of szPage bytes used to store the content of a 7257 ** single database page. The pExtra element of sqlite3_pcache_page will be 7258 ** a pointer to the szExtra bytes of extra storage that SQLite has requested 7259 ** for each entry in the page cache. 7260 ** 7261 ** The page to be fetched is determined by the key. ^The minimum key value 7262 ** is 1. After it has been retrieved using xFetch, the page is considered 7263 ** to be "pinned". 7264 ** 7265 ** If the requested page is already in the page cache, then the page cache 7266 ** implementation must return a pointer to the page buffer with its content 7267 ** intact. If the requested page is not already in the cache, then the 7268 ** cache implementation should use the value of the createFlag 7269 ** parameter to help it determined what action to take: 7270 ** 7271 ** <table border=1 width=85% align=center> 7272 ** <tr><th> createFlag <th> Behavior when page is not already in cache 7273 ** <tr><td> 0 <td> Do not allocate a new page. Return NULL. 7274 ** <tr><td> 1 <td> Allocate a new page if it easy and convenient to do so. 7275 ** Otherwise return NULL. 7276 ** <tr><td> 2 <td> Make every effort to allocate a new page. Only return 7277 ** NULL if allocating a new page is effectively impossible. 7278 ** </table> 7279 ** 7280 ** ^(SQLite will normally invoke xFetch() with a createFlag of 0 or 1. SQLite 7281 ** will only use a createFlag of 2 after a prior call with a createFlag of 1 7282 ** failed.)^ In between the to xFetch() calls, SQLite may 7283 ** attempt to unpin one or more cache pages by spilling the content of 7284 ** pinned pages to disk and synching the operating system disk cache. 7285 ** 7286 ** [[the xUnpin() page cache method]] 7287 ** ^xUnpin() is called by SQLite with a pointer to a currently pinned page 7288 ** as its second argument. If the third parameter, discard, is non-zero, 7289 ** then the page must be evicted from the cache. 7290 ** ^If the discard parameter is 7291 ** zero, then the page may be discarded or retained at the discretion of 7292 ** page cache implementation. ^The page cache implementation 7293 ** may choose to evict unpinned pages at any time. 7294 ** 7295 ** The cache must not perform any reference counting. A single 7296 ** call to xUnpin() unpins the page regardless of the number of prior calls 7297 ** to xFetch(). 7298 ** 7299 ** [[the xRekey() page cache methods]] 7300 ** The xRekey() method is used to change the key value associated with the 7301 ** page passed as the second argument. If the cache 7302 ** previously contains an entry associated with newKey, it must be 7303 ** discarded. ^Any prior cache entry associated with newKey is guaranteed not 7304 ** to be pinned. 7305 ** 7306 ** When SQLite calls the xTruncate() method, the cache must discard all 7307 ** existing cache entries with page numbers (keys) greater than or equal 7308 ** to the value of the iLimit parameter passed to xTruncate(). If any 7309 ** of these pages are pinned, they are implicitly unpinned, meaning that 7310 ** they can be safely discarded. 7311 ** 7312 ** [[the xDestroy() page cache method]] 7313 ** ^The xDestroy() method is used to delete a cache allocated by xCreate(). 7314 ** All resources associated with the specified cache should be freed. ^After 7315 ** calling the xDestroy() method, SQLite considers the [sqlite3_pcache*] 7316 ** handle invalid, and will not use it with any other sqlite3_pcache_methods2 7317 ** functions. 7318 ** 7319 ** [[the xShrink() page cache method]] 7320 ** ^SQLite invokes the xShrink() method when it wants the page cache to 7321 ** free up as much of heap memory as possible. The page cache implementation 7322 ** is not obligated to free any memory, but well-behaved implementations should 7323 ** do their best. 7324 */ 7325 typedef struct sqlite3_pcache_methods2 sqlite3_pcache_methods2; 7326 struct sqlite3_pcache_methods2 { 7327 int iVersion; 7328 void *pArg; 7329 int (*xInit)(void*); 7330 void (*xShutdown)(void*); 7331 sqlite3_pcache *(*xCreate)(int szPage, int szExtra, int bPurgeable); 7332 void (*xCachesize)(sqlite3_pcache*, int nCachesize); 7333 int (*xPagecount)(sqlite3_pcache*); 7334 sqlite3_pcache_page *(*xFetch)(sqlite3_pcache*, unsigned key, int createFlag); 7335 void (*xUnpin)(sqlite3_pcache*, sqlite3_pcache_page*, int discard); 7336 void (*xRekey)(sqlite3_pcache*, sqlite3_pcache_page*, 7337 unsigned oldKey, unsigned newKey); 7338 void (*xTruncate)(sqlite3_pcache*, unsigned iLimit); 7339 void (*xDestroy)(sqlite3_pcache*); 7340 void (*xShrink)(sqlite3_pcache*); 7341 }; 7342 7343 /* 7344 ** This is the obsolete pcache_methods object that has now been replaced 7345 ** by sqlite3_pcache_methods2. This object is not used by SQLite. It is 7346 ** retained in the header file for backwards compatibility only. 7347 */ 7348 typedef struct sqlite3_pcache_methods sqlite3_pcache_methods; 7349 struct sqlite3_pcache_methods { 7350 void *pArg; 7351 int (*xInit)(void*); 7352 void (*xShutdown)(void*); 7353 sqlite3_pcache *(*xCreate)(int szPage, int bPurgeable); 7354 void (*xCachesize)(sqlite3_pcache*, int nCachesize); 7355 int (*xPagecount)(sqlite3_pcache*); 7356 void *(*xFetch)(sqlite3_pcache*, unsigned key, int createFlag); 7357 void (*xUnpin)(sqlite3_pcache*, void*, int discard); 7358 void (*xRekey)(sqlite3_pcache*, void*, unsigned oldKey, unsigned newKey); 7359 void (*xTruncate)(sqlite3_pcache*, unsigned iLimit); 7360 void (*xDestroy)(sqlite3_pcache*); 7361 }; 7362 7363 7364 /* 7365 ** CAPI3REF: Online Backup Object 7366 ** 7367 ** The sqlite3_backup object records state information about an ongoing 7368 ** online backup operation. ^The sqlite3_backup object is created by 7369 ** a call to [sqlite3_backup_init()] and is destroyed by a call to 7370 ** [sqlite3_backup_finish()]. 7371 ** 7372 ** See Also: [Using the SQLite Online Backup API] 7373 */ 7374 typedef struct sqlite3_backup sqlite3_backup; 7375 7376 /* 7377 ** CAPI3REF: Online Backup API. 7378 ** 7379 ** The backup API copies the content of one database into another. 7380 ** It is useful either for creating backups of databases or 7381 ** for copying in-memory databases to or from persistent files. 7382 ** 7383 ** See Also: [Using the SQLite Online Backup API] 7384 ** 7385 ** ^SQLite holds a write transaction open on the destination database file 7386 ** for the duration of the backup operation. 7387 ** ^The source database is read-locked only while it is being read; 7388 ** it is not locked continuously for the entire backup operation. 7389 ** ^Thus, the backup may be performed on a live source database without 7390 ** preventing other database connections from 7391 ** reading or writing to the source database while the backup is underway. 7392 ** 7393 ** ^(To perform a backup operation: 7394 ** <ol> 7395 ** <li><b>sqlite3_backup_init()</b> is called once to initialize the 7396 ** backup, 7397 ** <li><b>sqlite3_backup_step()</b> is called one or more times to transfer 7398 ** the data between the two databases, and finally 7399 ** <li><b>sqlite3_backup_finish()</b> is called to release all resources 7400 ** associated with the backup operation. 7401 ** </ol>)^ 7402 ** There should be exactly one call to sqlite3_backup_finish() for each 7403 ** successful call to sqlite3_backup_init(). 7404 ** 7405 ** [[sqlite3_backup_init()]] <b>sqlite3_backup_init()</b> 7406 ** 7407 ** ^The D and N arguments to sqlite3_backup_init(D,N,S,M) are the 7408 ** [database connection] associated with the destination database 7409 ** and the database name, respectively. 7410 ** ^The database name is "main" for the main database, "temp" for the 7411 ** temporary database, or the name specified after the AS keyword in 7412 ** an [ATTACH] statement for an attached database. 7413 ** ^The S and M arguments passed to 7414 ** sqlite3_backup_init(D,N,S,M) identify the [database connection] 7415 ** and database name of the source database, respectively. 7416 ** ^The source and destination [database connections] (parameters S and D) 7417 ** must be different or else sqlite3_backup_init(D,N,S,M) will fail with 7418 ** an error. 7419 ** 7420 ** ^A call to sqlite3_backup_init() will fail, returning NULL, if 7421 ** there is already a read or read-write transaction open on the 7422 ** destination database. 7423 ** 7424 ** ^If an error occurs within sqlite3_backup_init(D,N,S,M), then NULL is 7425 ** returned and an error code and error message are stored in the 7426 ** destination [database connection] D. 7427 ** ^The error code and message for the failed call to sqlite3_backup_init() 7428 ** can be retrieved using the [sqlite3_errcode()], [sqlite3_errmsg()], and/or 7429 ** [sqlite3_errmsg16()] functions. 7430 ** ^A successful call to sqlite3_backup_init() returns a pointer to an 7431 ** [sqlite3_backup] object. 7432 ** ^The [sqlite3_backup] object may be used with the sqlite3_backup_step() and 7433 ** sqlite3_backup_finish() functions to perform the specified backup 7434 ** operation. 7435 ** 7436 ** [[sqlite3_backup_step()]] <b>sqlite3_backup_step()</b> 7437 ** 7438 ** ^Function sqlite3_backup_step(B,N) will copy up to N pages between 7439 ** the source and destination databases specified by [sqlite3_backup] object B. 7440 ** ^If N is negative, all remaining source pages are copied. 7441 ** ^If sqlite3_backup_step(B,N) successfully copies N pages and there 7442 ** are still more pages to be copied, then the function returns [SQLITE_OK]. 7443 ** ^If sqlite3_backup_step(B,N) successfully finishes copying all pages 7444 ** from source to destination, then it returns [SQLITE_DONE]. 7445 ** ^If an error occurs while running sqlite3_backup_step(B,N), 7446 ** then an [error code] is returned. ^As well as [SQLITE_OK] and 7447 ** [SQLITE_DONE], a call to sqlite3_backup_step() may return [SQLITE_READONLY], 7448 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an 7449 ** [SQLITE_IOERR_ACCESS | SQLITE_IOERR_XXX] extended error code. 7450 ** 7451 ** ^(The sqlite3_backup_step() might return [SQLITE_READONLY] if 7452 ** <ol> 7453 ** <li> the destination database was opened read-only, or 7454 ** <li> the destination database is using write-ahead-log journaling 7455 ** and the destination and source page sizes differ, or 7456 ** <li> the destination database is an in-memory database and the 7457 ** destination and source page sizes differ. 7458 ** </ol>)^ 7459 ** 7460 ** ^If sqlite3_backup_step() cannot obtain a required file-system lock, then 7461 ** the [sqlite3_busy_handler | busy-handler function] 7462 ** is invoked (if one is specified). ^If the 7463 ** busy-handler returns non-zero before the lock is available, then 7464 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to 7465 ** sqlite3_backup_step() can be retried later. ^If the source 7466 ** [database connection] 7467 ** is being used to write to the source database when sqlite3_backup_step() 7468 ** is called, then [SQLITE_LOCKED] is returned immediately. ^Again, in this 7469 ** case the call to sqlite3_backup_step() can be retried later on. ^(If 7470 ** [SQLITE_IOERR_ACCESS | SQLITE_IOERR_XXX], [SQLITE_NOMEM], or 7471 ** [SQLITE_READONLY] is returned, then 7472 ** there is no point in retrying the call to sqlite3_backup_step(). These 7473 ** errors are considered fatal.)^ The application must accept 7474 ** that the backup operation has failed and pass the backup operation handle 7475 ** to the sqlite3_backup_finish() to release associated resources. 7476 ** 7477 ** ^The first call to sqlite3_backup_step() obtains an exclusive lock 7478 ** on the destination file. ^The exclusive lock is not released until either 7479 ** sqlite3_backup_finish() is called or the backup operation is complete 7480 ** and sqlite3_backup_step() returns [SQLITE_DONE]. ^Every call to 7481 ** sqlite3_backup_step() obtains a [shared lock] on the source database that 7482 ** lasts for the duration of the sqlite3_backup_step() call. 7483 ** ^Because the source database is not locked between calls to 7484 ** sqlite3_backup_step(), the source database may be modified mid-way 7485 ** through the backup process. ^If the source database is modified by an 7486 ** external process or via a database connection other than the one being 7487 ** used by the backup operation, then the backup will be automatically 7488 ** restarted by the next call to sqlite3_backup_step(). ^If the source 7489 ** database is modified by the using the same database connection as is used 7490 ** by the backup operation, then the backup database is automatically 7491 ** updated at the same time. 7492 ** 7493 ** [[sqlite3_backup_finish()]] <b>sqlite3_backup_finish()</b> 7494 ** 7495 ** When sqlite3_backup_step() has returned [SQLITE_DONE], or when the 7496 ** application wishes to abandon the backup operation, the application 7497 ** should destroy the [sqlite3_backup] by passing it to sqlite3_backup_finish(). 7498 ** ^The sqlite3_backup_finish() interfaces releases all 7499 ** resources associated with the [sqlite3_backup] object. 7500 ** ^If sqlite3_backup_step() has not yet returned [SQLITE_DONE], then any 7501 ** active write-transaction on the destination database is rolled back. 7502 ** The [sqlite3_backup] object is invalid 7503 ** and may not be used following a call to sqlite3_backup_finish(). 7504 ** 7505 ** ^The value returned by sqlite3_backup_finish is [SQLITE_OK] if no 7506 ** sqlite3_backup_step() errors occurred, regardless or whether or not 7507 ** sqlite3_backup_step() completed. 7508 ** ^If an out-of-memory condition or IO error occurred during any prior 7509 ** sqlite3_backup_step() call on the same [sqlite3_backup] object, then 7510 ** sqlite3_backup_finish() returns the corresponding [error code]. 7511 ** 7512 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step() 7513 ** is not a permanent error and does not affect the return value of 7514 ** sqlite3_backup_finish(). 7515 ** 7516 ** [[sqlite3_backup_remaining()]] [[sqlite3_backup_pagecount()]] 7517 ** <b>sqlite3_backup_remaining() and sqlite3_backup_pagecount()</b> 7518 ** 7519 ** ^The sqlite3_backup_remaining() routine returns the number of pages still 7520 ** to be backed up at the conclusion of the most recent sqlite3_backup_step(). 7521 ** ^The sqlite3_backup_pagecount() routine returns the total number of pages 7522 ** in the source database at the conclusion of the most recent 7523 ** sqlite3_backup_step(). 7524 ** ^(The values returned by these functions are only updated by 7525 ** sqlite3_backup_step(). If the source database is modified in a way that 7526 ** changes the size of the source database or the number of pages remaining, 7527 ** those changes are not reflected in the output of sqlite3_backup_pagecount() 7528 ** and sqlite3_backup_remaining() until after the next 7529 ** sqlite3_backup_step().)^ 7530 ** 7531 ** <b>Concurrent Usage of Database Handles</b> 7532 ** 7533 ** ^The source [database connection] may be used by the application for other 7534 ** purposes while a backup operation is underway or being initialized. 7535 ** ^If SQLite is compiled and configured to support threadsafe database 7536 ** connections, then the source database connection may be used concurrently 7537 ** from within other threads. 7538 ** 7539 ** However, the application must guarantee that the destination 7540 ** [database connection] is not passed to any other API (by any thread) after 7541 ** sqlite3_backup_init() is called and before the corresponding call to 7542 ** sqlite3_backup_finish(). SQLite does not currently check to see 7543 ** if the application incorrectly accesses the destination [database connection] 7544 ** and so no error code is reported, but the operations may malfunction 7545 ** nevertheless. Use of the destination database connection while a 7546 ** backup is in progress might also also cause a mutex deadlock. 7547 ** 7548 ** If running in [shared cache mode], the application must 7549 ** guarantee that the shared cache used by the destination database 7550 ** is not accessed while the backup is running. In practice this means 7551 ** that the application must guarantee that the disk file being 7552 ** backed up to is not accessed by any connection within the process, 7553 ** not just the specific connection that was passed to sqlite3_backup_init(). 7554 ** 7555 ** The [sqlite3_backup] object itself is partially threadsafe. Multiple 7556 ** threads may safely make multiple concurrent calls to sqlite3_backup_step(). 7557 ** However, the sqlite3_backup_remaining() and sqlite3_backup_pagecount() 7558 ** APIs are not strictly speaking threadsafe. If they are invoked at the 7559 ** same time as another thread is invoking sqlite3_backup_step() it is 7560 ** possible that they return invalid values. 7561 */ 7562 SQLITE_API sqlite3_backup *sqlite3_backup_init( 7563 sqlite3 *pDest, /* Destination database handle */ 7564 const char *zDestName, /* Destination database name */ 7565 sqlite3 *pSource, /* Source database handle */ 7566 const char *zSourceName /* Source database name */ 7567 ); 7568 SQLITE_API int sqlite3_backup_step(sqlite3_backup *p, int nPage); 7569 SQLITE_API int sqlite3_backup_finish(sqlite3_backup *p); 7570 SQLITE_API int sqlite3_backup_remaining(sqlite3_backup *p); 7571 SQLITE_API int sqlite3_backup_pagecount(sqlite3_backup *p); 7572 7573 /* 7574 ** CAPI3REF: Unlock Notification 7575 ** METHOD: sqlite3 7576 ** 7577 ** ^When running in shared-cache mode, a database operation may fail with 7578 ** an [SQLITE_LOCKED] error if the required locks on the shared-cache or 7579 ** individual tables within the shared-cache cannot be obtained. See 7580 ** [SQLite Shared-Cache Mode] for a description of shared-cache locking. 7581 ** ^This API may be used to register a callback that SQLite will invoke 7582 ** when the connection currently holding the required lock relinquishes it. 7583 ** ^This API is only available if the library was compiled with the 7584 ** [SQLITE_ENABLE_UNLOCK_NOTIFY] C-preprocessor symbol defined. 7585 ** 7586 ** See Also: [Using the SQLite Unlock Notification Feature]. 7587 ** 7588 ** ^Shared-cache locks are released when a database connection concludes 7589 ** its current transaction, either by committing it or rolling it back. 7590 ** 7591 ** ^When a connection (known as the blocked connection) fails to obtain a 7592 ** shared-cache lock and SQLITE_LOCKED is returned to the caller, the 7593 ** identity of the database connection (the blocking connection) that 7594 ** has locked the required resource is stored internally. ^After an 7595 ** application receives an SQLITE_LOCKED error, it may call the 7596 ** sqlite3_unlock_notify() method with the blocked connection handle as 7597 ** the first argument to register for a callback that will be invoked 7598 ** when the blocking connections current transaction is concluded. ^The 7599 ** callback is invoked from within the [sqlite3_step] or [sqlite3_close] 7600 ** call that concludes the blocking connections transaction. 7601 ** 7602 ** ^(If sqlite3_unlock_notify() is called in a multi-threaded application, 7603 ** there is a chance that the blocking connection will have already 7604 ** concluded its transaction by the time sqlite3_unlock_notify() is invoked. 7605 ** If this happens, then the specified callback is invoked immediately, 7606 ** from within the call to sqlite3_unlock_notify().)^ 7607 ** 7608 ** ^If the blocked connection is attempting to obtain a write-lock on a 7609 ** shared-cache table, and more than one other connection currently holds 7610 ** a read-lock on the same table, then SQLite arbitrarily selects one of 7611 ** the other connections to use as the blocking connection. 7612 ** 7613 ** ^(There may be at most one unlock-notify callback registered by a 7614 ** blocked connection. If sqlite3_unlock_notify() is called when the 7615 ** blocked connection already has a registered unlock-notify callback, 7616 ** then the new callback replaces the old.)^ ^If sqlite3_unlock_notify() is 7617 ** called with a NULL pointer as its second argument, then any existing 7618 ** unlock-notify callback is canceled. ^The blocked connections 7619 ** unlock-notify callback may also be canceled by closing the blocked 7620 ** connection using [sqlite3_close()]. 7621 ** 7622 ** The unlock-notify callback is not reentrant. If an application invokes 7623 ** any sqlite3_xxx API functions from within an unlock-notify callback, a 7624 ** crash or deadlock may be the result. 7625 ** 7626 ** ^Unless deadlock is detected (see below), sqlite3_unlock_notify() always 7627 ** returns SQLITE_OK. 7628 ** 7629 ** <b>Callback Invocation Details</b> 7630 ** 7631 ** When an unlock-notify callback is registered, the application provides a 7632 ** single void* pointer that is passed to the callback when it is invoked. 7633 ** However, the signature of the callback function allows SQLite to pass 7634 ** it an array of void* context pointers. The first argument passed to 7635 ** an unlock-notify callback is a pointer to an array of void* pointers, 7636 ** and the second is the number of entries in the array. 7637 ** 7638 ** When a blocking connections transaction is concluded, there may be 7639 ** more than one blocked connection that has registered for an unlock-notify 7640 ** callback. ^If two or more such blocked connections have specified the 7641 ** same callback function, then instead of invoking the callback function 7642 ** multiple times, it is invoked once with the set of void* context pointers 7643 ** specified by the blocked connections bundled together into an array. 7644 ** This gives the application an opportunity to prioritize any actions 7645 ** related to the set of unblocked database connections. 7646 ** 7647 ** <b>Deadlock Detection</b> 7648 ** 7649 ** Assuming that after registering for an unlock-notify callback a 7650 ** database waits for the callback to be issued before taking any further 7651 ** action (a reasonable assumption), then using this API may cause the 7652 ** application to deadlock. For example, if connection X is waiting for 7653 ** connection Y's transaction to be concluded, and similarly connection 7654 ** Y is waiting on connection X's transaction, then neither connection 7655 ** will proceed and the system may remain deadlocked indefinitely. 7656 ** 7657 ** To avoid this scenario, the sqlite3_unlock_notify() performs deadlock 7658 ** detection. ^If a given call to sqlite3_unlock_notify() would put the 7659 ** system in a deadlocked state, then SQLITE_LOCKED is returned and no 7660 ** unlock-notify callback is registered. The system is said to be in 7661 ** a deadlocked state if connection A has registered for an unlock-notify 7662 ** callback on the conclusion of connection B's transaction, and connection 7663 ** B has itself registered for an unlock-notify callback when connection 7664 ** A's transaction is concluded. ^Indirect deadlock is also detected, so 7665 ** the system is also considered to be deadlocked if connection B has 7666 ** registered for an unlock-notify callback on the conclusion of connection 7667 ** C's transaction, where connection C is waiting on connection A. ^Any 7668 ** number of levels of indirection are allowed. 7669 ** 7670 ** <b>The "DROP TABLE" Exception</b> 7671 ** 7672 ** When a call to [sqlite3_step()] returns SQLITE_LOCKED, it is almost 7673 ** always appropriate to call sqlite3_unlock_notify(). There is however, 7674 ** one exception. When executing a "DROP TABLE" or "DROP INDEX" statement, 7675 ** SQLite checks if there are any currently executing SELECT statements 7676 ** that belong to the same connection. If there are, SQLITE_LOCKED is 7677 ** returned. In this case there is no "blocking connection", so invoking 7678 ** sqlite3_unlock_notify() results in the unlock-notify callback being 7679 ** invoked immediately. If the application then re-attempts the "DROP TABLE" 7680 ** or "DROP INDEX" query, an infinite loop might be the result. 7681 ** 7682 ** One way around this problem is to check the extended error code returned 7683 ** by an sqlite3_step() call. ^(If there is a blocking connection, then the 7684 ** extended error code is set to SQLITE_LOCKED_SHAREDCACHE. Otherwise, in 7685 ** the special "DROP TABLE/INDEX" case, the extended error code is just 7686 ** SQLITE_LOCKED.)^ 7687 */ 7688 SQLITE_API int sqlite3_unlock_notify( 7689 sqlite3 *pBlocked, /* Waiting connection */ 7690 void (*xNotify)(void **apArg, int nArg), /* Callback function to invoke */ 7691 void *pNotifyArg /* Argument to pass to xNotify */ 7692 ); 7693 7694 7695 /* 7696 ** CAPI3REF: String Comparison 7697 ** 7698 ** ^The [sqlite3_stricmp()] and [sqlite3_strnicmp()] APIs allow applications 7699 ** and extensions to compare the contents of two buffers containing UTF-8 7700 ** strings in a case-independent fashion, using the same definition of "case 7701 ** independence" that SQLite uses internally when comparing identifiers. 7702 */ 7703 SQLITE_API int sqlite3_stricmp(const char *, const char *); 7704 SQLITE_API int sqlite3_strnicmp(const char *, const char *, int); 7705 7706 /* 7707 ** CAPI3REF: String Globbing 7708 * 7709 ** ^The [sqlite3_strglob(P,X)] interface returns zero if and only if 7710 ** string X matches the [GLOB] pattern P. 7711 ** ^The definition of [GLOB] pattern matching used in 7712 ** [sqlite3_strglob(P,X)] is the same as for the "X GLOB P" operator in the 7713 ** SQL dialect understood by SQLite. ^The [sqlite3_strglob(P,X)] function 7714 ** is case sensitive. 7715 ** 7716 ** Note that this routine returns zero on a match and non-zero if the strings 7717 ** do not match, the same as [sqlite3_stricmp()] and [sqlite3_strnicmp()]. 7718 ** 7719 ** See also: [sqlite3_strlike()]. 7720 */ 7721 SQLITE_API int sqlite3_strglob(const char *zGlob, const char *zStr); 7722 7723 /* 7724 ** CAPI3REF: String LIKE Matching 7725 * 7726 ** ^The [sqlite3_strlike(P,X,E)] interface returns zero if and only if 7727 ** string X matches the [LIKE] pattern P with escape character E. 7728 ** ^The definition of [LIKE] pattern matching used in 7729 ** [sqlite3_strlike(P,X,E)] is the same as for the "X LIKE P ESCAPE E" 7730 ** operator in the SQL dialect understood by SQLite. ^For "X LIKE P" without 7731 ** the ESCAPE clause, set the E parameter of [sqlite3_strlike(P,X,E)] to 0. 7732 ** ^As with the LIKE operator, the [sqlite3_strlike(P,X,E)] function is case 7733 ** insensitive - equivalent upper and lower case ASCII characters match 7734 ** one another. 7735 ** 7736 ** ^The [sqlite3_strlike(P,X,E)] function matches Unicode characters, though 7737 ** only ASCII characters are case folded. 7738 ** 7739 ** Note that this routine returns zero on a match and non-zero if the strings 7740 ** do not match, the same as [sqlite3_stricmp()] and [sqlite3_strnicmp()]. 7741 ** 7742 ** See also: [sqlite3_strglob()]. 7743 */ 7744 SQLITE_API int sqlite3_strlike(const char *zGlob, const char *zStr, unsigned int cEsc); 7745 7746 /* 7747 ** CAPI3REF: Error Logging Interface 7748 ** 7749 ** ^The [sqlite3_log()] interface writes a message into the [error log] 7750 ** established by the [SQLITE_CONFIG_LOG] option to [sqlite3_config()]. 7751 ** ^If logging is enabled, the zFormat string and subsequent arguments are 7752 ** used with [sqlite3_snprintf()] to generate the final output string. 7753 ** 7754 ** The sqlite3_log() interface is intended for use by extensions such as 7755 ** virtual tables, collating functions, and SQL functions. While there is 7756 ** nothing to prevent an application from calling sqlite3_log(), doing so 7757 ** is considered bad form. 7758 ** 7759 ** The zFormat string must not be NULL. 7760 ** 7761 ** To avoid deadlocks and other threading problems, the sqlite3_log() routine 7762 ** will not use dynamically allocated memory. The log message is stored in 7763 ** a fixed-length buffer on the stack. If the log message is longer than 7764 ** a few hundred characters, it will be truncated to the length of the 7765 ** buffer. 7766 */ 7767 SQLITE_API void sqlite3_log(int iErrCode, const char *zFormat, ...); 7768 7769 /* 7770 ** CAPI3REF: Write-Ahead Log Commit Hook 7771 ** METHOD: sqlite3 7772 ** 7773 ** ^The [sqlite3_wal_hook()] function is used to register a callback that 7774 ** is invoked each time data is committed to a database in wal mode. 7775 ** 7776 ** ^(The callback is invoked by SQLite after the commit has taken place and 7777 ** the associated write-lock on the database released)^, so the implementation 7778 ** may read, write or [checkpoint] the database as required. 7779 ** 7780 ** ^The first parameter passed to the callback function when it is invoked 7781 ** is a copy of the third parameter passed to sqlite3_wal_hook() when 7782 ** registering the callback. ^The second is a copy of the database handle. 7783 ** ^The third parameter is the name of the database that was written to - 7784 ** either "main" or the name of an [ATTACH]-ed database. ^The fourth parameter 7785 ** is the number of pages currently in the write-ahead log file, 7786 ** including those that were just committed. 7787 ** 7788 ** The callback function should normally return [SQLITE_OK]. ^If an error 7789 ** code is returned, that error will propagate back up through the 7790 ** SQLite code base to cause the statement that provoked the callback 7791 ** to report an error, though the commit will have still occurred. If the 7792 ** callback returns [SQLITE_ROW] or [SQLITE_DONE], or if it returns a value 7793 ** that does not correspond to any valid SQLite error code, the results 7794 ** are undefined. 7795 ** 7796 ** A single database handle may have at most a single write-ahead log callback 7797 ** registered at one time. ^Calling [sqlite3_wal_hook()] replaces any 7798 ** previously registered write-ahead log callback. ^Note that the 7799 ** [sqlite3_wal_autocheckpoint()] interface and the 7800 ** [wal_autocheckpoint pragma] both invoke [sqlite3_wal_hook()] and will 7801 ** overwrite any prior [sqlite3_wal_hook()] settings. 7802 */ 7803 SQLITE_API void *sqlite3_wal_hook( 7804 sqlite3*, 7805 int(*)(void *,sqlite3*,const char*,int), 7806 void* 7807 ); 7808 7809 /* 7810 ** CAPI3REF: Configure an auto-checkpoint 7811 ** METHOD: sqlite3 7812 ** 7813 ** ^The [sqlite3_wal_autocheckpoint(D,N)] is a wrapper around 7814 ** [sqlite3_wal_hook()] that causes any database on [database connection] D 7815 ** to automatically [checkpoint] 7816 ** after committing a transaction if there are N or 7817 ** more frames in the [write-ahead log] file. ^Passing zero or 7818 ** a negative value as the nFrame parameter disables automatic 7819 ** checkpoints entirely. 7820 ** 7821 ** ^The callback registered by this function replaces any existing callback 7822 ** registered using [sqlite3_wal_hook()]. ^Likewise, registering a callback 7823 ** using [sqlite3_wal_hook()] disables the automatic checkpoint mechanism 7824 ** configured by this function. 7825 ** 7826 ** ^The [wal_autocheckpoint pragma] can be used to invoke this interface 7827 ** from SQL. 7828 ** 7829 ** ^Checkpoints initiated by this mechanism are 7830 ** [sqlite3_wal_checkpoint_v2|PASSIVE]. 7831 ** 7832 ** ^Every new [database connection] defaults to having the auto-checkpoint 7833 ** enabled with a threshold of 1000 or [SQLITE_DEFAULT_WAL_AUTOCHECKPOINT] 7834 ** pages. The use of this interface 7835 ** is only necessary if the default setting is found to be suboptimal 7836 ** for a particular application. 7837 */ 7838 SQLITE_API int sqlite3_wal_autocheckpoint(sqlite3 *db, int N); 7839 7840 /* 7841 ** CAPI3REF: Checkpoint a database 7842 ** METHOD: sqlite3 7843 ** 7844 ** ^(The sqlite3_wal_checkpoint(D,X) is equivalent to 7845 ** [sqlite3_wal_checkpoint_v2](D,X,[SQLITE_CHECKPOINT_PASSIVE],0,0).)^ 7846 ** 7847 ** In brief, sqlite3_wal_checkpoint(D,X) causes the content in the 7848 ** [write-ahead log] for database X on [database connection] D to be 7849 ** transferred into the database file and for the write-ahead log to 7850 ** be reset. See the [checkpointing] documentation for addition 7851 ** information. 7852 ** 7853 ** This interface used to be the only way to cause a checkpoint to 7854 ** occur. But then the newer and more powerful [sqlite3_wal_checkpoint_v2()] 7855 ** interface was added. This interface is retained for backwards 7856 ** compatibility and as a convenience for applications that need to manually 7857 ** start a callback but which do not need the full power (and corresponding 7858 ** complication) of [sqlite3_wal_checkpoint_v2()]. 7859 */ 7860 SQLITE_API int sqlite3_wal_checkpoint(sqlite3 *db, const char *zDb); 7861 7862 /* 7863 ** CAPI3REF: Checkpoint a database 7864 ** METHOD: sqlite3 7865 ** 7866 ** ^(The sqlite3_wal_checkpoint_v2(D,X,M,L,C) interface runs a checkpoint 7867 ** operation on database X of [database connection] D in mode M. Status 7868 ** information is written back into integers pointed to by L and C.)^ 7869 ** ^(The M parameter must be a valid [checkpoint mode]:)^ 7870 ** 7871 ** <dl> 7872 ** <dt>SQLITE_CHECKPOINT_PASSIVE<dd> 7873 ** ^Checkpoint as many frames as possible without waiting for any database 7874 ** readers or writers to finish, then sync the database file if all frames 7875 ** in the log were checkpointed. ^The [busy-handler callback] 7876 ** is never invoked in the SQLITE_CHECKPOINT_PASSIVE mode. 7877 ** ^On the other hand, passive mode might leave the checkpoint unfinished 7878 ** if there are concurrent readers or writers. 7879 ** 7880 ** <dt>SQLITE_CHECKPOINT_FULL<dd> 7881 ** ^This mode blocks (it invokes the 7882 ** [sqlite3_busy_handler|busy-handler callback]) until there is no 7883 ** database writer and all readers are reading from the most recent database 7884 ** snapshot. ^It then checkpoints all frames in the log file and syncs the 7885 ** database file. ^This mode blocks new database writers while it is pending, 7886 ** but new database readers are allowed to continue unimpeded. 7887 ** 7888 ** <dt>SQLITE_CHECKPOINT_RESTART<dd> 7889 ** ^This mode works the same way as SQLITE_CHECKPOINT_FULL with the addition 7890 ** that after checkpointing the log file it blocks (calls the 7891 ** [busy-handler callback]) 7892 ** until all readers are reading from the database file only. ^This ensures 7893 ** that the next writer will restart the log file from the beginning. 7894 ** ^Like SQLITE_CHECKPOINT_FULL, this mode blocks new 7895 ** database writer attempts while it is pending, but does not impede readers. 7896 ** 7897 ** <dt>SQLITE_CHECKPOINT_TRUNCATE<dd> 7898 ** ^This mode works the same way as SQLITE_CHECKPOINT_RESTART with the 7899 ** addition that it also truncates the log file to zero bytes just prior 7900 ** to a successful return. 7901 ** </dl> 7902 ** 7903 ** ^If pnLog is not NULL, then *pnLog is set to the total number of frames in 7904 ** the log file or to -1 if the checkpoint could not run because 7905 ** of an error or because the database is not in [WAL mode]. ^If pnCkpt is not 7906 ** NULL,then *pnCkpt is set to the total number of checkpointed frames in the 7907 ** log file (including any that were already checkpointed before the function 7908 ** was called) or to -1 if the checkpoint could not run due to an error or 7909 ** because the database is not in WAL mode. ^Note that upon successful 7910 ** completion of an SQLITE_CHECKPOINT_TRUNCATE, the log file will have been 7911 ** truncated to zero bytes and so both *pnLog and *pnCkpt will be set to zero. 7912 ** 7913 ** ^All calls obtain an exclusive "checkpoint" lock on the database file. ^If 7914 ** any other process is running a checkpoint operation at the same time, the 7915 ** lock cannot be obtained and SQLITE_BUSY is returned. ^Even if there is a 7916 ** busy-handler configured, it will not be invoked in this case. 7917 ** 7918 ** ^The SQLITE_CHECKPOINT_FULL, RESTART and TRUNCATE modes also obtain the 7919 ** exclusive "writer" lock on the database file. ^If the writer lock cannot be 7920 ** obtained immediately, and a busy-handler is configured, it is invoked and 7921 ** the writer lock retried until either the busy-handler returns 0 or the lock 7922 ** is successfully obtained. ^The busy-handler is also invoked while waiting for 7923 ** database readers as described above. ^If the busy-handler returns 0 before 7924 ** the writer lock is obtained or while waiting for database readers, the 7925 ** checkpoint operation proceeds from that point in the same way as 7926 ** SQLITE_CHECKPOINT_PASSIVE - checkpointing as many frames as possible 7927 ** without blocking any further. ^SQLITE_BUSY is returned in this case. 7928 ** 7929 ** ^If parameter zDb is NULL or points to a zero length string, then the 7930 ** specified operation is attempted on all WAL databases [attached] to 7931 ** [database connection] db. In this case the 7932 ** values written to output parameters *pnLog and *pnCkpt are undefined. ^If 7933 ** an SQLITE_BUSY error is encountered when processing one or more of the 7934 ** attached WAL databases, the operation is still attempted on any remaining 7935 ** attached databases and SQLITE_BUSY is returned at the end. ^If any other 7936 ** error occurs while processing an attached database, processing is abandoned 7937 ** and the error code is returned to the caller immediately. ^If no error 7938 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached 7939 ** databases, SQLITE_OK is returned. 7940 ** 7941 ** ^If database zDb is the name of an attached database that is not in WAL 7942 ** mode, SQLITE_OK is returned and both *pnLog and *pnCkpt set to -1. ^If 7943 ** zDb is not NULL (or a zero length string) and is not the name of any 7944 ** attached database, SQLITE_ERROR is returned to the caller. 7945 ** 7946 ** ^Unless it returns SQLITE_MISUSE, 7947 ** the sqlite3_wal_checkpoint_v2() interface 7948 ** sets the error information that is queried by 7949 ** [sqlite3_errcode()] and [sqlite3_errmsg()]. 7950 ** 7951 ** ^The [PRAGMA wal_checkpoint] command can be used to invoke this interface 7952 ** from SQL. 7953 */ 7954 SQLITE_API int sqlite3_wal_checkpoint_v2( 7955 sqlite3 *db, /* Database handle */ 7956 const char *zDb, /* Name of attached database (or NULL) */ 7957 int eMode, /* SQLITE_CHECKPOINT_* value */ 7958 int *pnLog, /* OUT: Size of WAL log in frames */ 7959 int *pnCkpt /* OUT: Total number of frames checkpointed */ 7960 ); 7961 7962 /* 7963 ** CAPI3REF: Checkpoint Mode Values 7964 ** KEYWORDS: {checkpoint mode} 7965 ** 7966 ** These constants define all valid values for the "checkpoint mode" passed 7967 ** as the third parameter to the [sqlite3_wal_checkpoint_v2()] interface. 7968 ** See the [sqlite3_wal_checkpoint_v2()] documentation for details on the 7969 ** meaning of each of these checkpoint modes. 7970 */ 7971 #define SQLITE_CHECKPOINT_PASSIVE 0 /* Do as much as possible w/o blocking */ 7972 #define SQLITE_CHECKPOINT_FULL 1 /* Wait for writers, then checkpoint */ 7973 #define SQLITE_CHECKPOINT_RESTART 2 /* Like FULL but wait for for readers */ 7974 #define SQLITE_CHECKPOINT_TRUNCATE 3 /* Like RESTART but also truncate WAL */ 7975 7976 /* 7977 ** CAPI3REF: Virtual Table Interface Configuration 7978 ** 7979 ** This function may be called by either the [xConnect] or [xCreate] method 7980 ** of a [virtual table] implementation to configure 7981 ** various facets of the virtual table interface. 7982 ** 7983 ** If this interface is invoked outside the context of an xConnect or 7984 ** xCreate virtual table method then the behavior is undefined. 7985 ** 7986 ** At present, there is only one option that may be configured using 7987 ** this function. (See [SQLITE_VTAB_CONSTRAINT_SUPPORT].) Further options 7988 ** may be added in the future. 7989 */ 7990 SQLITE_API int sqlite3_vtab_config(sqlite3*, int op, ...); 7991 7992 /* 7993 ** CAPI3REF: Virtual Table Configuration Options 7994 ** 7995 ** These macros define the various options to the 7996 ** [sqlite3_vtab_config()] interface that [virtual table] implementations 7997 ** can use to customize and optimize their behavior. 7998 ** 7999 ** <dl> 8000 ** <dt>SQLITE_VTAB_CONSTRAINT_SUPPORT 8001 ** <dd>Calls of the form 8002 ** [sqlite3_vtab_config](db,SQLITE_VTAB_CONSTRAINT_SUPPORT,X) are supported, 8003 ** where X is an integer. If X is zero, then the [virtual table] whose 8004 ** [xCreate] or [xConnect] method invoked [sqlite3_vtab_config()] does not 8005 ** support constraints. In this configuration (which is the default) if 8006 ** a call to the [xUpdate] method returns [SQLITE_CONSTRAINT], then the entire 8007 ** statement is rolled back as if [ON CONFLICT | OR ABORT] had been 8008 ** specified as part of the users SQL statement, regardless of the actual 8009 ** ON CONFLICT mode specified. 8010 ** 8011 ** If X is non-zero, then the virtual table implementation guarantees 8012 ** that if [xUpdate] returns [SQLITE_CONSTRAINT], it will do so before 8013 ** any modifications to internal or persistent data structures have been made. 8014 ** If the [ON CONFLICT] mode is ABORT, FAIL, IGNORE or ROLLBACK, SQLite 8015 ** is able to roll back a statement or database transaction, and abandon 8016 ** or continue processing the current SQL statement as appropriate. 8017 ** If the ON CONFLICT mode is REPLACE and the [xUpdate] method returns 8018 ** [SQLITE_CONSTRAINT], SQLite handles this as if the ON CONFLICT mode 8019 ** had been ABORT. 8020 ** 8021 ** Virtual table implementations that are required to handle OR REPLACE 8022 ** must do so within the [xUpdate] method. If a call to the 8023 ** [sqlite3_vtab_on_conflict()] function indicates that the current ON 8024 ** CONFLICT policy is REPLACE, the virtual table implementation should 8025 ** silently replace the appropriate rows within the xUpdate callback and 8026 ** return SQLITE_OK. Or, if this is not possible, it may return 8027 ** SQLITE_CONSTRAINT, in which case SQLite falls back to OR ABORT 8028 ** constraint handling. 8029 ** </dl> 8030 */ 8031 #define SQLITE_VTAB_CONSTRAINT_SUPPORT 1 8032 8033 /* 8034 ** CAPI3REF: Determine The Virtual Table Conflict Policy 8035 ** 8036 ** This function may only be called from within a call to the [xUpdate] method 8037 ** of a [virtual table] implementation for an INSERT or UPDATE operation. ^The 8038 ** value returned is one of [SQLITE_ROLLBACK], [SQLITE_IGNORE], [SQLITE_FAIL], 8039 ** [SQLITE_ABORT], or [SQLITE_REPLACE], according to the [ON CONFLICT] mode 8040 ** of the SQL statement that triggered the call to the [xUpdate] method of the 8041 ** [virtual table]. 8042 */ 8043 SQLITE_API int sqlite3_vtab_on_conflict(sqlite3 *); 8044 8045 /* 8046 ** CAPI3REF: Conflict resolution modes 8047 ** KEYWORDS: {conflict resolution mode} 8048 ** 8049 ** These constants are returned by [sqlite3_vtab_on_conflict()] to 8050 ** inform a [virtual table] implementation what the [ON CONFLICT] mode 8051 ** is for the SQL statement being evaluated. 8052 ** 8053 ** Note that the [SQLITE_IGNORE] constant is also used as a potential 8054 ** return value from the [sqlite3_set_authorizer()] callback and that 8055 ** [SQLITE_ABORT] is also a [result code]. 8056 */ 8057 #define SQLITE_ROLLBACK 1 8058 /* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback */ 8059 #define SQLITE_FAIL 3 8060 /* #define SQLITE_ABORT 4 // Also an error code */ 8061 #define SQLITE_REPLACE 5 8062 8063 /* 8064 ** CAPI3REF: Prepared Statement Scan Status Opcodes 8065 ** KEYWORDS: {scanstatus options} 8066 ** 8067 ** The following constants can be used for the T parameter to the 8068 ** [sqlite3_stmt_scanstatus(S,X,T,V)] interface. Each constant designates a 8069 ** different metric for sqlite3_stmt_scanstatus() to return. 8070 ** 8071 ** When the value returned to V is a string, space to hold that string is 8072 ** managed by the prepared statement S and will be automatically freed when 8073 ** S is finalized. 8074 ** 8075 ** <dl> 8076 ** [[SQLITE_SCANSTAT_NLOOP]] <dt>SQLITE_SCANSTAT_NLOOP</dt> 8077 ** <dd>^The [sqlite3_int64] variable pointed to by the T parameter will be 8078 ** set to the total number of times that the X-th loop has run.</dd> 8079 ** 8080 ** [[SQLITE_SCANSTAT_NVISIT]] <dt>SQLITE_SCANSTAT_NVISIT</dt> 8081 ** <dd>^The [sqlite3_int64] variable pointed to by the T parameter will be set 8082 ** to the total number of rows examined by all iterations of the X-th loop.</dd> 8083 ** 8084 ** [[SQLITE_SCANSTAT_EST]] <dt>SQLITE_SCANSTAT_EST</dt> 8085 ** <dd>^The "double" variable pointed to by the T parameter will be set to the 8086 ** query planner's estimate for the average number of rows output from each 8087 ** iteration of the X-th loop. If the query planner's estimates was accurate, 8088 ** then this value will approximate the quotient NVISIT/NLOOP and the 8089 ** product of this value for all prior loops with the same SELECTID will 8090 ** be the NLOOP value for the current loop. 8091 ** 8092 ** [[SQLITE_SCANSTAT_NAME]] <dt>SQLITE_SCANSTAT_NAME</dt> 8093 ** <dd>^The "const char *" variable pointed to by the T parameter will be set 8094 ** to a zero-terminated UTF-8 string containing the name of the index or table 8095 ** used for the X-th loop. 8096 ** 8097 ** [[SQLITE_SCANSTAT_EXPLAIN]] <dt>SQLITE_SCANSTAT_EXPLAIN</dt> 8098 ** <dd>^The "const char *" variable pointed to by the T parameter will be set 8099 ** to a zero-terminated UTF-8 string containing the [EXPLAIN QUERY PLAN] 8100 ** description for the X-th loop. 8101 ** 8102 ** [[SQLITE_SCANSTAT_SELECTID]] <dt>SQLITE_SCANSTAT_SELECT</dt> 8103 ** <dd>^The "int" variable pointed to by the T parameter will be set to the 8104 ** "select-id" for the X-th loop. The select-id identifies which query or 8105 ** subquery the loop is part of. The main query has a select-id of zero. 8106 ** The select-id is the same value as is output in the first column 8107 ** of an [EXPLAIN QUERY PLAN] query. 8108 ** </dl> 8109 */ 8110 #define SQLITE_SCANSTAT_NLOOP 0 8111 #define SQLITE_SCANSTAT_NVISIT 1 8112 #define SQLITE_SCANSTAT_EST 2 8113 #define SQLITE_SCANSTAT_NAME 3 8114 #define SQLITE_SCANSTAT_EXPLAIN 4 8115 #define SQLITE_SCANSTAT_SELECTID 5 8116 8117 /* 8118 ** CAPI3REF: Prepared Statement Scan Status 8119 ** METHOD: sqlite3_stmt 8120 ** 8121 ** This interface returns information about the predicted and measured 8122 ** performance for pStmt. Advanced applications can use this 8123 ** interface to compare the predicted and the measured performance and 8124 ** issue warnings and/or rerun [ANALYZE] if discrepancies are found. 8125 ** 8126 ** Since this interface is expected to be rarely used, it is only 8127 ** available if SQLite is compiled using the [SQLITE_ENABLE_STMT_SCANSTATUS] 8128 ** compile-time option. 8129 ** 8130 ** The "iScanStatusOp" parameter determines which status information to return. 8131 ** The "iScanStatusOp" must be one of the [scanstatus options] or the behavior 8132 ** of this interface is undefined. 8133 ** ^The requested measurement is written into a variable pointed to by 8134 ** the "pOut" parameter. 8135 ** Parameter "idx" identifies the specific loop to retrieve statistics for. 8136 ** Loops are numbered starting from zero. ^If idx is out of range - less than 8137 ** zero or greater than or equal to the total number of loops used to implement 8138 ** the statement - a non-zero value is returned and the variable that pOut 8139 ** points to is unchanged. 8140 ** 8141 ** ^Statistics might not be available for all loops in all statements. ^In cases 8142 ** where there exist loops with no available statistics, this function behaves 8143 ** as if the loop did not exist - it returns non-zero and leave the variable 8144 ** that pOut points to unchanged. 8145 ** 8146 ** See also: [sqlite3_stmt_scanstatus_reset()] 8147 */ 8148 SQLITE_API int sqlite3_stmt_scanstatus( 8149 sqlite3_stmt *pStmt, /* Prepared statement for which info desired */ 8150 int idx, /* Index of loop to report on */ 8151 int iScanStatusOp, /* Information desired. SQLITE_SCANSTAT_* */ 8152 void *pOut /* Result written here */ 8153 ); 8154 8155 /* 8156 ** CAPI3REF: Zero Scan-Status Counters 8157 ** METHOD: sqlite3_stmt 8158 ** 8159 ** ^Zero all [sqlite3_stmt_scanstatus()] related event counters. 8160 ** 8161 ** This API is only available if the library is built with pre-processor 8162 ** symbol [SQLITE_ENABLE_STMT_SCANSTATUS] defined. 8163 */ 8164 SQLITE_API void sqlite3_stmt_scanstatus_reset(sqlite3_stmt*); 8165 8166 /* 8167 ** CAPI3REF: Flush caches to disk mid-transaction 8168 ** 8169 ** ^If a write-transaction is open on [database connection] D when the 8170 ** [sqlite3_db_cacheflush(D)] interface invoked, any dirty 8171 ** pages in the pager-cache that are not currently in use are written out 8172 ** to disk. A dirty page may be in use if a database cursor created by an 8173 ** active SQL statement is reading from it, or if it is page 1 of a database 8174 ** file (page 1 is always "in use"). ^The [sqlite3_db_cacheflush(D)] 8175 ** interface flushes caches for all schemas - "main", "temp", and 8176 ** any [attached] databases. 8177 ** 8178 ** ^If this function needs to obtain extra database locks before dirty pages 8179 ** can be flushed to disk, it does so. ^If those locks cannot be obtained 8180 ** immediately and there is a busy-handler callback configured, it is invoked 8181 ** in the usual manner. ^If the required lock still cannot be obtained, then 8182 ** the database is skipped and an attempt made to flush any dirty pages 8183 ** belonging to the next (if any) database. ^If any databases are skipped 8184 ** because locks cannot be obtained, but no other error occurs, this 8185 ** function returns SQLITE_BUSY. 8186 ** 8187 ** ^If any other error occurs while flushing dirty pages to disk (for 8188 ** example an IO error or out-of-memory condition), then processing is 8189 ** abandoned and an SQLite [error code] is returned to the caller immediately. 8190 ** 8191 ** ^Otherwise, if no error occurs, [sqlite3_db_cacheflush()] returns SQLITE_OK. 8192 ** 8193 ** ^This function does not set the database handle error code or message 8194 ** returned by the [sqlite3_errcode()] and [sqlite3_errmsg()] functions. 8195 */ 8196 SQLITE_API int sqlite3_db_cacheflush(sqlite3*); 8197 8198 /* 8199 ** CAPI3REF: The pre-update hook. 8200 ** 8201 ** ^These interfaces are only available if SQLite is compiled using the 8202 ** [SQLITE_ENABLE_PREUPDATE_HOOK] compile-time option. 8203 ** 8204 ** ^The [sqlite3_preupdate_hook()] interface registers a callback function 8205 ** that is invoked prior to each [INSERT], [UPDATE], and [DELETE] operation 8206 ** on a database table. 8207 ** ^At most one preupdate hook may be registered at a time on a single 8208 ** [database connection]; each call to [sqlite3_preupdate_hook()] overrides 8209 ** the previous setting. 8210 ** ^The preupdate hook is disabled by invoking [sqlite3_preupdate_hook()] 8211 ** with a NULL pointer as the second parameter. 8212 ** ^The third parameter to [sqlite3_preupdate_hook()] is passed through as 8213 ** the first parameter to callbacks. 8214 ** 8215 ** ^The preupdate hook only fires for changes to real database tables; the 8216 ** preupdate hook is not invoked for changes to [virtual tables] or to 8217 ** system tables like sqlite_master or sqlite_stat1. 8218 ** 8219 ** ^The second parameter to the preupdate callback is a pointer to 8220 ** the [database connection] that registered the preupdate hook. 8221 ** ^The third parameter to the preupdate callback is one of the constants 8222 ** [SQLITE_INSERT], [SQLITE_DELETE], or [SQLITE_UPDATE] to identify the 8223 ** kind of update operation that is about to occur. 8224 ** ^(The fourth parameter to the preupdate callback is the name of the 8225 ** database within the database connection that is being modified. This 8226 ** will be "main" for the main database or "temp" for TEMP tables or 8227 ** the name given after the AS keyword in the [ATTACH] statement for attached 8228 ** databases.)^ 8229 ** ^The fifth parameter to the preupdate callback is the name of the 8230 ** table that is being modified. 8231 ** 8232 ** For an UPDATE or DELETE operation on a [rowid table], the sixth 8233 ** parameter passed to the preupdate callback is the initial [rowid] of the 8234 ** row being modified or deleted. For an INSERT operation on a rowid table, 8235 ** or any operation on a WITHOUT ROWID table, the value of the sixth 8236 ** parameter is undefined. For an INSERT or UPDATE on a rowid table the 8237 ** seventh parameter is the final rowid value of the row being inserted 8238 ** or updated. The value of the seventh parameter passed to the callback 8239 ** function is not defined for operations on WITHOUT ROWID tables, or for 8240 ** INSERT operations on rowid tables. 8241 ** 8242 ** The [sqlite3_preupdate_old()], [sqlite3_preupdate_new()], 8243 ** [sqlite3_preupdate_count()], and [sqlite3_preupdate_depth()] interfaces 8244 ** provide additional information about a preupdate event. These routines 8245 ** may only be called from within a preupdate callback. Invoking any of 8246 ** these routines from outside of a preupdate callback or with a 8247 ** [database connection] pointer that is different from the one supplied 8248 ** to the preupdate callback results in undefined and probably undesirable 8249 ** behavior. 8250 ** 8251 ** ^The [sqlite3_preupdate_count(D)] interface returns the number of columns 8252 ** in the row that is being inserted, updated, or deleted. 8253 ** 8254 ** ^The [sqlite3_preupdate_old(D,N,P)] interface writes into P a pointer to 8255 ** a [protected sqlite3_value] that contains the value of the Nth column of 8256 ** the table row before it is updated. The N parameter must be between 0 8257 ** and one less than the number of columns or the behavior will be 8258 ** undefined. This must only be used within SQLITE_UPDATE and SQLITE_DELETE 8259 ** preupdate callbacks; if it is used by an SQLITE_INSERT callback then the 8260 ** behavior is undefined. The [sqlite3_value] that P points to 8261 ** will be destroyed when the preupdate callback returns. 8262 ** 8263 ** ^The [sqlite3_preupdate_new(D,N,P)] interface writes into P a pointer to 8264 ** a [protected sqlite3_value] that contains the value of the Nth column of 8265 ** the table row after it is updated. The N parameter must be between 0 8266 ** and one less than the number of columns or the behavior will be 8267 ** undefined. This must only be used within SQLITE_INSERT and SQLITE_UPDATE 8268 ** preupdate callbacks; if it is used by an SQLITE_DELETE callback then the 8269 ** behavior is undefined. The [sqlite3_value] that P points to 8270 ** will be destroyed when the preupdate callback returns. 8271 ** 8272 ** ^The [sqlite3_preupdate_depth(D)] interface returns 0 if the preupdate 8273 ** callback was invoked as a result of a direct insert, update, or delete 8274 ** operation; or 1 for inserts, updates, or deletes invoked by top-level 8275 ** triggers; or 2 for changes resulting from triggers called by top-level 8276 ** triggers; and so forth. 8277 ** 8278 ** See also: [sqlite3_update_hook()] 8279 */ 8280 #if defined(SQLITE_ENABLE_PREUPDATE_HOOK) 8281 SQLITE_API void *sqlite3_preupdate_hook( 8282 sqlite3 *db, 8283 void(*xPreUpdate)( 8284 void *pCtx, /* Copy of third arg to preupdate_hook() */ 8285 sqlite3 *db, /* Database handle */ 8286 int op, /* SQLITE_UPDATE, DELETE or INSERT */ 8287 char const *zDb, /* Database name */ 8288 char const *zName, /* Table name */ 8289 sqlite3_int64 iKey1, /* Rowid of row about to be deleted/updated */ 8290 sqlite3_int64 iKey2 /* New rowid value (for a rowid UPDATE) */ 8291 ), 8292 void* 8293 ); 8294 SQLITE_API int sqlite3_preupdate_old(sqlite3 *, int, sqlite3_value **); 8295 SQLITE_API int sqlite3_preupdate_count(sqlite3 *); 8296 SQLITE_API int sqlite3_preupdate_depth(sqlite3 *); 8297 SQLITE_API int sqlite3_preupdate_new(sqlite3 *, int, sqlite3_value **); 8298 #endif 8299 8300 /* 8301 ** CAPI3REF: Low-level system error code 8302 ** 8303 ** ^Attempt to return the underlying operating system error code or error 8304 ** number that caused the most recent I/O error or failure to open a file. 8305 ** The return value is OS-dependent. For example, on unix systems, after 8306 ** [sqlite3_open_v2()] returns [SQLITE_CANTOPEN], this interface could be 8307 ** called to get back the underlying "errno" that caused the problem, such 8308 ** as ENOSPC, EAUTH, EISDIR, and so forth. 8309 */ 8310 SQLITE_API int sqlite3_system_errno(sqlite3*); 8311 8312 /* 8313 ** CAPI3REF: Database Snapshot 8314 ** KEYWORDS: {snapshot} {sqlite3_snapshot} 8315 ** EXPERIMENTAL 8316 ** 8317 ** An instance of the snapshot object records the state of a [WAL mode] 8318 ** database for some specific point in history. 8319 ** 8320 ** In [WAL mode], multiple [database connections] that are open on the 8321 ** same database file can each be reading a different historical version 8322 ** of the database file. When a [database connection] begins a read 8323 ** transaction, that connection sees an unchanging copy of the database 8324 ** as it existed for the point in time when the transaction first started. 8325 ** Subsequent changes to the database from other connections are not seen 8326 ** by the reader until a new read transaction is started. 8327 ** 8328 ** The sqlite3_snapshot object records state information about an historical 8329 ** version of the database file so that it is possible to later open a new read 8330 ** transaction that sees that historical version of the database rather than 8331 ** the most recent version. 8332 ** 8333 ** The constructor for this object is [sqlite3_snapshot_get()]. The 8334 ** [sqlite3_snapshot_open()] method causes a fresh read transaction to refer 8335 ** to an historical snapshot (if possible). The destructor for 8336 ** sqlite3_snapshot objects is [sqlite3_snapshot_free()]. 8337 */ 8338 typedef struct sqlite3_snapshot { 8339 unsigned char hidden[48]; 8340 } sqlite3_snapshot; 8341 8342 /* 8343 ** CAPI3REF: Record A Database Snapshot 8344 ** EXPERIMENTAL 8345 ** 8346 ** ^The [sqlite3_snapshot_get(D,S,P)] interface attempts to make a 8347 ** new [sqlite3_snapshot] object that records the current state of 8348 ** schema S in database connection D. ^On success, the 8349 ** [sqlite3_snapshot_get(D,S,P)] interface writes a pointer to the newly 8350 ** created [sqlite3_snapshot] object into *P and returns SQLITE_OK. 8351 ** If there is not already a read-transaction open on schema S when 8352 ** this function is called, one is opened automatically. 8353 ** 8354 ** The following must be true for this function to succeed. If any of 8355 ** the following statements are false when sqlite3_snapshot_get() is 8356 ** called, SQLITE_ERROR is returned. The final value of *P is undefined 8357 ** in this case. 8358 ** 8359 ** <ul> 8360 ** <li> The database handle must be in [autocommit mode]. 8361 ** 8362 ** <li> Schema S of [database connection] D must be a [WAL mode] database. 8363 ** 8364 ** <li> There must not be a write transaction open on schema S of database 8365 ** connection D. 8366 ** 8367 ** <li> One or more transactions must have been written to the current wal 8368 ** file since it was created on disk (by any connection). This means 8369 ** that a snapshot cannot be taken on a wal mode database with no wal 8370 ** file immediately after it is first opened. At least one transaction 8371 ** must be written to it first. 8372 ** </ul> 8373 ** 8374 ** This function may also return SQLITE_NOMEM. If it is called with the 8375 ** database handle in autocommit mode but fails for some other reason, 8376 ** whether or not a read transaction is opened on schema S is undefined. 8377 ** 8378 ** The [sqlite3_snapshot] object returned from a successful call to 8379 ** [sqlite3_snapshot_get()] must be freed using [sqlite3_snapshot_free()] 8380 ** to avoid a memory leak. 8381 ** 8382 ** The [sqlite3_snapshot_get()] interface is only available when the 8383 ** SQLITE_ENABLE_SNAPSHOT compile-time option is used. 8384 */ 8385 SQLITE_API SQLITE_EXPERIMENTAL int sqlite3_snapshot_get( 8386 sqlite3 *db, 8387 const char *zSchema, 8388 sqlite3_snapshot **ppSnapshot 8389 ); 8390 8391 /* 8392 ** CAPI3REF: Start a read transaction on an historical snapshot 8393 ** EXPERIMENTAL 8394 ** 8395 ** ^The [sqlite3_snapshot_open(D,S,P)] interface starts a 8396 ** read transaction for schema S of 8397 ** [database connection] D such that the read transaction 8398 ** refers to historical [snapshot] P, rather than the most 8399 ** recent change to the database. 8400 ** ^The [sqlite3_snapshot_open()] interface returns SQLITE_OK on success 8401 ** or an appropriate [error code] if it fails. 8402 ** 8403 ** ^In order to succeed, a call to [sqlite3_snapshot_open(D,S,P)] must be 8404 ** the first operation following the [BEGIN] that takes the schema S 8405 ** out of [autocommit mode]. 8406 ** ^In other words, schema S must not currently be in 8407 ** a transaction for [sqlite3_snapshot_open(D,S,P)] to work, but the 8408 ** database connection D must be out of [autocommit mode]. 8409 ** ^A [snapshot] will fail to open if it has been overwritten by a 8410 ** [checkpoint]. 8411 ** ^(A call to [sqlite3_snapshot_open(D,S,P)] will fail if the 8412 ** database connection D does not know that the database file for 8413 ** schema S is in [WAL mode]. A database connection might not know 8414 ** that the database file is in [WAL mode] if there has been no prior 8415 ** I/O on that database connection, or if the database entered [WAL mode] 8416 ** after the most recent I/O on the database connection.)^ 8417 ** (Hint: Run "[PRAGMA application_id]" against a newly opened 8418 ** database connection in order to make it ready to use snapshots.) 8419 ** 8420 ** The [sqlite3_snapshot_open()] interface is only available when the 8421 ** SQLITE_ENABLE_SNAPSHOT compile-time option is used. 8422 */ 8423 SQLITE_API SQLITE_EXPERIMENTAL int sqlite3_snapshot_open( 8424 sqlite3 *db, 8425 const char *zSchema, 8426 sqlite3_snapshot *pSnapshot 8427 ); 8428 8429 /* 8430 ** CAPI3REF: Destroy a snapshot 8431 ** EXPERIMENTAL 8432 ** 8433 ** ^The [sqlite3_snapshot_free(P)] interface destroys [sqlite3_snapshot] P. 8434 ** The application must eventually free every [sqlite3_snapshot] object 8435 ** using this routine to avoid a memory leak. 8436 ** 8437 ** The [sqlite3_snapshot_free()] interface is only available when the 8438 ** SQLITE_ENABLE_SNAPSHOT compile-time option is used. 8439 */ 8440 SQLITE_API SQLITE_EXPERIMENTAL void sqlite3_snapshot_free(sqlite3_snapshot*); 8441 8442 /* 8443 ** CAPI3REF: Compare the ages of two snapshot handles. 8444 ** EXPERIMENTAL 8445 ** 8446 ** The sqlite3_snapshot_cmp(P1, P2) interface is used to compare the ages 8447 ** of two valid snapshot handles. 8448 ** 8449 ** If the two snapshot handles are not associated with the same database 8450 ** file, the result of the comparison is undefined. 8451 ** 8452 ** Additionally, the result of the comparison is only valid if both of the 8453 ** snapshot handles were obtained by calling sqlite3_snapshot_get() since the 8454 ** last time the wal file was deleted. The wal file is deleted when the 8455 ** database is changed back to rollback mode or when the number of database 8456 ** clients drops to zero. If either snapshot handle was obtained before the 8457 ** wal file was last deleted, the value returned by this function 8458 ** is undefined. 8459 ** 8460 ** Otherwise, this API returns a negative value if P1 refers to an older 8461 ** snapshot than P2, zero if the two handles refer to the same database 8462 ** snapshot, and a positive value if P1 is a newer snapshot than P2. 8463 */ 8464 SQLITE_API SQLITE_EXPERIMENTAL int sqlite3_snapshot_cmp( 8465 sqlite3_snapshot *p1, 8466 sqlite3_snapshot *p2 8467 ); 8468 8469 /* 8470 ** CAPI3REF: Recover snapshots from a wal file 8471 ** EXPERIMENTAL 8472 ** 8473 ** If all connections disconnect from a database file but do not perform 8474 ** a checkpoint, the existing wal file is opened along with the database 8475 ** file the next time the database is opened. At this point it is only 8476 ** possible to successfully call sqlite3_snapshot_open() to open the most 8477 ** recent snapshot of the database (the one at the head of the wal file), 8478 ** even though the wal file may contain other valid snapshots for which 8479 ** clients have sqlite3_snapshot handles. 8480 ** 8481 ** This function attempts to scan the wal file associated with database zDb 8482 ** of database handle db and make all valid snapshots available to 8483 ** sqlite3_snapshot_open(). It is an error if there is already a read 8484 ** transaction open on the database, or if the database is not a wal mode 8485 ** database. 8486 ** 8487 ** SQLITE_OK is returned if successful, or an SQLite error code otherwise. 8488 */ 8489 SQLITE_API SQLITE_EXPERIMENTAL int sqlite3_snapshot_recover(sqlite3 *db, const char *zDb); 8490 8491 /* 8492 ** Undo the hack that converts floating point types to integer for 8493 ** builds on processors without floating point support. 8494 */ 8495 #ifdef SQLITE_OMIT_FLOATING_POINT 8496 # undef double 8497 #endif 8498 8499 #ifdef __cplusplus 8500 } /* End of the 'extern "C"' block */ 8501 #endif 8502 #endif /* SQLITE3_H */ 8503 8504 /******** Begin file sqlite3rtree.h *********/ 8505 /* 8506 ** 2010 August 30 8507 ** 8508 ** The author disclaims copyright to this source code. In place of 8509 ** a legal notice, here is a blessing: 8510 ** 8511 ** May you do good and not evil. 8512 ** May you find forgiveness for yourself and forgive others. 8513 ** May you share freely, never taking more than you give. 8514 ** 8515 ************************************************************************* 8516 */ 8517 8518 #ifndef _SQLITE3RTREE_H_ 8519 #define _SQLITE3RTREE_H_ 8520 8521 8522 #ifdef __cplusplus 8523 extern "C" { 8524 #endif 8525 8526 typedef struct sqlite3_rtree_geometry sqlite3_rtree_geometry; 8527 typedef struct sqlite3_rtree_query_info sqlite3_rtree_query_info; 8528 8529 /* The double-precision datatype used by RTree depends on the 8530 ** SQLITE_RTREE_INT_ONLY compile-time option. 8531 */ 8532 #ifdef SQLITE_RTREE_INT_ONLY 8533 typedef sqlite3_int64 sqlite3_rtree_dbl; 8534 #else 8535 typedef double sqlite3_rtree_dbl; 8536 #endif 8537 8538 /* 8539 ** Register a geometry callback named zGeom that can be used as part of an 8540 ** R-Tree geometry query as follows: 8541 ** 8542 ** SELECT ... FROM <rtree> WHERE <rtree col> MATCH $zGeom(... params ...) 8543 */ 8544 SQLITE_API int sqlite3_rtree_geometry_callback( 8545 sqlite3 *db, 8546 const char *zGeom, 8547 int (*xGeom)(sqlite3_rtree_geometry*, int, sqlite3_rtree_dbl*,int*), 8548 void *pContext 8549 ); 8550 8551 8552 /* 8553 ** A pointer to a structure of the following type is passed as the first 8554 ** argument to callbacks registered using rtree_geometry_callback(). 8555 */ 8556 struct sqlite3_rtree_geometry { 8557 void *pContext; /* Copy of pContext passed to s_r_g_c() */ 8558 int nParam; /* Size of array aParam[] */ 8559 sqlite3_rtree_dbl *aParam; /* Parameters passed to SQL geom function */ 8560 void *pUser; /* Callback implementation user data */ 8561 void (*xDelUser)(void *); /* Called by SQLite to clean up pUser */ 8562 }; 8563 8564 /* 8565 ** Register a 2nd-generation geometry callback named zScore that can be 8566 ** used as part of an R-Tree geometry query as follows: 8567 ** 8568 ** SELECT ... FROM <rtree> WHERE <rtree col> MATCH $zQueryFunc(... params ...) 8569 */ 8570 SQLITE_API int sqlite3_rtree_query_callback( 8571 sqlite3 *db, 8572 const char *zQueryFunc, 8573 int (*xQueryFunc)(sqlite3_rtree_query_info*), 8574 void *pContext, 8575 void (*xDestructor)(void*) 8576 ); 8577 8578 8579 /* 8580 ** A pointer to a structure of the following type is passed as the 8581 ** argument to scored geometry callback registered using 8582 ** sqlite3_rtree_query_callback(). 8583 ** 8584 ** Note that the first 5 fields of this structure are identical to 8585 ** sqlite3_rtree_geometry. This structure is a subclass of 8586 ** sqlite3_rtree_geometry. 8587 */ 8588 struct sqlite3_rtree_query_info { 8589 void *pContext; /* pContext from when function registered */ 8590 int nParam; /* Number of function parameters */ 8591 sqlite3_rtree_dbl *aParam; /* value of function parameters */ 8592 void *pUser; /* callback can use this, if desired */ 8593 void (*xDelUser)(void*); /* function to free pUser */ 8594 sqlite3_rtree_dbl *aCoord; /* Coordinates of node or entry to check */ 8595 unsigned int *anQueue; /* Number of pending entries in the queue */ 8596 int nCoord; /* Number of coordinates */ 8597 int iLevel; /* Level of current node or entry */ 8598 int mxLevel; /* The largest iLevel value in the tree */ 8599 sqlite3_int64 iRowid; /* Rowid for current entry */ 8600 sqlite3_rtree_dbl rParentScore; /* Score of parent node */ 8601 int eParentWithin; /* Visibility of parent node */ 8602 int eWithin; /* OUT: Visiblity */ 8603 sqlite3_rtree_dbl rScore; /* OUT: Write the score here */ 8604 /* The following fields are only available in 3.8.11 and later */ 8605 sqlite3_value **apSqlParam; /* Original SQL values of parameters */ 8606 }; 8607 8608 /* 8609 ** Allowed values for sqlite3_rtree_query.eWithin and .eParentWithin. 8610 */ 8611 #define NOT_WITHIN 0 /* Object completely outside of query region */ 8612 #define PARTLY_WITHIN 1 /* Object partially overlaps query region */ 8613 #define FULLY_WITHIN 2 /* Object fully contained within query region */ 8614 8615 8616 #ifdef __cplusplus 8617 } /* end of the 'extern "C"' block */ 8618 #endif 8619 8620 #endif /* ifndef _SQLITE3RTREE_H_ */ 8621 8622 /******** End of sqlite3rtree.h *********/ 8623 /******** Begin file sqlite3session.h *********/ 8624 8625 #if !defined(__SQLITESESSION_H_) && defined(SQLITE_ENABLE_SESSION) 8626 #define __SQLITESESSION_H_ 1 8627 8628 /* 8629 ** Make sure we can call this stuff from C++. 8630 */ 8631 #ifdef __cplusplus 8632 extern "C" { 8633 #endif 8634 8635 8636 /* 8637 ** CAPI3REF: Session Object Handle 8638 */ 8639 typedef struct sqlite3_session sqlite3_session; 8640 8641 /* 8642 ** CAPI3REF: Changeset Iterator Handle 8643 */ 8644 typedef struct sqlite3_changeset_iter sqlite3_changeset_iter; 8645 8646 /* 8647 ** CAPI3REF: Create A New Session Object 8648 ** 8649 ** Create a new session object attached to database handle db. If successful, 8650 ** a pointer to the new object is written to *ppSession and SQLITE_OK is 8651 ** returned. If an error occurs, *ppSession is set to NULL and an SQLite 8652 ** error code (e.g. SQLITE_NOMEM) is returned. 8653 ** 8654 ** It is possible to create multiple session objects attached to a single 8655 ** database handle. 8656 ** 8657 ** Session objects created using this function should be deleted using the 8658 ** [sqlite3session_delete()] function before the database handle that they 8659 ** are attached to is itself closed. If the database handle is closed before 8660 ** the session object is deleted, then the results of calling any session 8661 ** module function, including [sqlite3session_delete()] on the session object 8662 ** are undefined. 8663 ** 8664 ** Because the session module uses the [sqlite3_preupdate_hook()] API, it 8665 ** is not possible for an application to register a pre-update hook on a 8666 ** database handle that has one or more session objects attached. Nor is 8667 ** it possible to create a session object attached to a database handle for 8668 ** which a pre-update hook is already defined. The results of attempting 8669 ** either of these things are undefined. 8670 ** 8671 ** The session object will be used to create changesets for tables in 8672 ** database zDb, where zDb is either "main", or "temp", or the name of an 8673 ** attached database. It is not an error if database zDb is not attached 8674 ** to the database when the session object is created. 8675 */ 8676 SQLITE_API int sqlite3session_create( 8677 sqlite3 *db, /* Database handle */ 8678 const char *zDb, /* Name of db (e.g. "main") */ 8679 sqlite3_session **ppSession /* OUT: New session object */ 8680 ); 8681 8682 /* 8683 ** CAPI3REF: Delete A Session Object 8684 ** 8685 ** Delete a session object previously allocated using 8686 ** [sqlite3session_create()]. Once a session object has been deleted, the 8687 ** results of attempting to use pSession with any other session module 8688 ** function are undefined. 8689 ** 8690 ** Session objects must be deleted before the database handle to which they 8691 ** are attached is closed. Refer to the documentation for 8692 ** [sqlite3session_create()] for details. 8693 */ 8694 SQLITE_API void sqlite3session_delete(sqlite3_session *pSession); 8695 8696 8697 /* 8698 ** CAPI3REF: Enable Or Disable A Session Object 8699 ** 8700 ** Enable or disable the recording of changes by a session object. When 8701 ** enabled, a session object records changes made to the database. When 8702 ** disabled - it does not. A newly created session object is enabled. 8703 ** Refer to the documentation for [sqlite3session_changeset()] for further 8704 ** details regarding how enabling and disabling a session object affects 8705 ** the eventual changesets. 8706 ** 8707 ** Passing zero to this function disables the session. Passing a value 8708 ** greater than zero enables it. Passing a value less than zero is a 8709 ** no-op, and may be used to query the current state of the session. 8710 ** 8711 ** The return value indicates the final state of the session object: 0 if 8712 ** the session is disabled, or 1 if it is enabled. 8713 */ 8714 SQLITE_API int sqlite3session_enable(sqlite3_session *pSession, int bEnable); 8715 8716 /* 8717 ** CAPI3REF: Set Or Clear the Indirect Change Flag 8718 ** 8719 ** Each change recorded by a session object is marked as either direct or 8720 ** indirect. A change is marked as indirect if either: 8721 ** 8722 ** <ul> 8723 ** <li> The session object "indirect" flag is set when the change is 8724 ** made, or 8725 ** <li> The change is made by an SQL trigger or foreign key action 8726 ** instead of directly as a result of a users SQL statement. 8727 ** </ul> 8728 ** 8729 ** If a single row is affected by more than one operation within a session, 8730 ** then the change is considered indirect if all operations meet the criteria 8731 ** for an indirect change above, or direct otherwise. 8732 ** 8733 ** This function is used to set, clear or query the session object indirect 8734 ** flag. If the second argument passed to this function is zero, then the 8735 ** indirect flag is cleared. If it is greater than zero, the indirect flag 8736 ** is set. Passing a value less than zero does not modify the current value 8737 ** of the indirect flag, and may be used to query the current state of the 8738 ** indirect flag for the specified session object. 8739 ** 8740 ** The return value indicates the final state of the indirect flag: 0 if 8741 ** it is clear, or 1 if it is set. 8742 */ 8743 SQLITE_API int sqlite3session_indirect(sqlite3_session *pSession, int bIndirect); 8744 8745 /* 8746 ** CAPI3REF: Attach A Table To A Session Object 8747 ** 8748 ** If argument zTab is not NULL, then it is the name of a table to attach 8749 ** to the session object passed as the first argument. All subsequent changes 8750 ** made to the table while the session object is enabled will be recorded. See 8751 ** documentation for [sqlite3session_changeset()] for further details. 8752 ** 8753 ** Or, if argument zTab is NULL, then changes are recorded for all tables 8754 ** in the database. If additional tables are added to the database (by 8755 ** executing "CREATE TABLE" statements) after this call is made, changes for 8756 ** the new tables are also recorded. 8757 ** 8758 ** Changes can only be recorded for tables that have a PRIMARY KEY explicitly 8759 ** defined as part of their CREATE TABLE statement. It does not matter if the 8760 ** PRIMARY KEY is an "INTEGER PRIMARY KEY" (rowid alias) or not. The PRIMARY 8761 ** KEY may consist of a single column, or may be a composite key. 8762 ** 8763 ** It is not an error if the named table does not exist in the database. Nor 8764 ** is it an error if the named table does not have a PRIMARY KEY. However, 8765 ** no changes will be recorded in either of these scenarios. 8766 ** 8767 ** Changes are not recorded for individual rows that have NULL values stored 8768 ** in one or more of their PRIMARY KEY columns. 8769 ** 8770 ** SQLITE_OK is returned if the call completes without error. Or, if an error 8771 ** occurs, an SQLite error code (e.g. SQLITE_NOMEM) is returned. 8772 */ 8773 SQLITE_API int sqlite3session_attach( 8774 sqlite3_session *pSession, /* Session object */ 8775 const char *zTab /* Table name */ 8776 ); 8777 8778 /* 8779 ** CAPI3REF: Set a table filter on a Session Object. 8780 ** 8781 ** The second argument (xFilter) is the "filter callback". For changes to rows 8782 ** in tables that are not attached to the Session object, the filter is called 8783 ** to determine whether changes to the table's rows should be tracked or not. 8784 ** If xFilter returns 0, changes is not tracked. Note that once a table is 8785 ** attached, xFilter will not be called again. 8786 */ 8787 SQLITE_API void sqlite3session_table_filter( 8788 sqlite3_session *pSession, /* Session object */ 8789 int(*xFilter)( 8790 void *pCtx, /* Copy of third arg to _filter_table() */ 8791 const char *zTab /* Table name */ 8792 ), 8793 void *pCtx /* First argument passed to xFilter */ 8794 ); 8795 8796 /* 8797 ** CAPI3REF: Generate A Changeset From A Session Object 8798 ** 8799 ** Obtain a changeset containing changes to the tables attached to the 8800 ** session object passed as the first argument. If successful, 8801 ** set *ppChangeset to point to a buffer containing the changeset 8802 ** and *pnChangeset to the size of the changeset in bytes before returning 8803 ** SQLITE_OK. If an error occurs, set both *ppChangeset and *pnChangeset to 8804 ** zero and return an SQLite error code. 8805 ** 8806 ** A changeset consists of zero or more INSERT, UPDATE and/or DELETE changes, 8807 ** each representing a change to a single row of an attached table. An INSERT 8808 ** change contains the values of each field of a new database row. A DELETE 8809 ** contains the original values of each field of a deleted database row. An 8810 ** UPDATE change contains the original values of each field of an updated 8811 ** database row along with the updated values for each updated non-primary-key 8812 ** column. It is not possible for an UPDATE change to represent a change that 8813 ** modifies the values of primary key columns. If such a change is made, it 8814 ** is represented in a changeset as a DELETE followed by an INSERT. 8815 ** 8816 ** Changes are not recorded for rows that have NULL values stored in one or 8817 ** more of their PRIMARY KEY columns. If such a row is inserted or deleted, 8818 ** no corresponding change is present in the changesets returned by this 8819 ** function. If an existing row with one or more NULL values stored in 8820 ** PRIMARY KEY columns is updated so that all PRIMARY KEY columns are non-NULL, 8821 ** only an INSERT is appears in the changeset. Similarly, if an existing row 8822 ** with non-NULL PRIMARY KEY values is updated so that one or more of its 8823 ** PRIMARY KEY columns are set to NULL, the resulting changeset contains a 8824 ** DELETE change only. 8825 ** 8826 ** The contents of a changeset may be traversed using an iterator created 8827 ** using the [sqlite3changeset_start()] API. A changeset may be applied to 8828 ** a database with a compatible schema using the [sqlite3changeset_apply()] 8829 ** API. 8830 ** 8831 ** Within a changeset generated by this function, all changes related to a 8832 ** single table are grouped together. In other words, when iterating through 8833 ** a changeset or when applying a changeset to a database, all changes related 8834 ** to a single table are processed before moving on to the next table. Tables 8835 ** are sorted in the same order in which they were attached (or auto-attached) 8836 ** to the sqlite3_session object. The order in which the changes related to 8837 ** a single table are stored is undefined. 8838 ** 8839 ** Following a successful call to this function, it is the responsibility of 8840 ** the caller to eventually free the buffer that *ppChangeset points to using 8841 ** [sqlite3_free()]. 8842 ** 8843 ** <h3>Changeset Generation</h3> 8844 ** 8845 ** Once a table has been attached to a session object, the session object 8846 ** records the primary key values of all new rows inserted into the table. 8847 ** It also records the original primary key and other column values of any 8848 ** deleted or updated rows. For each unique primary key value, data is only 8849 ** recorded once - the first time a row with said primary key is inserted, 8850 ** updated or deleted in the lifetime of the session. 8851 ** 8852 ** There is one exception to the previous paragraph: when a row is inserted, 8853 ** updated or deleted, if one or more of its primary key columns contain a 8854 ** NULL value, no record of the change is made. 8855 ** 8856 ** The session object therefore accumulates two types of records - those 8857 ** that consist of primary key values only (created when the user inserts 8858 ** a new record) and those that consist of the primary key values and the 8859 ** original values of other table columns (created when the users deletes 8860 ** or updates a record). 8861 ** 8862 ** When this function is called, the requested changeset is created using 8863 ** both the accumulated records and the current contents of the database 8864 ** file. Specifically: 8865 ** 8866 ** <ul> 8867 ** <li> For each record generated by an insert, the database is queried 8868 ** for a row with a matching primary key. If one is found, an INSERT 8869 ** change is added to the changeset. If no such row is found, no change 8870 ** is added to the changeset. 8871 ** 8872 ** <li> For each record generated by an update or delete, the database is 8873 ** queried for a row with a matching primary key. If such a row is 8874 ** found and one or more of the non-primary key fields have been 8875 ** modified from their original values, an UPDATE change is added to 8876 ** the changeset. Or, if no such row is found in the table, a DELETE 8877 ** change is added to the changeset. If there is a row with a matching 8878 ** primary key in the database, but all fields contain their original 8879 ** values, no change is added to the changeset. 8880 ** </ul> 8881 ** 8882 ** This means, amongst other things, that if a row is inserted and then later 8883 ** deleted while a session object is active, neither the insert nor the delete 8884 ** will be present in the changeset. Or if a row is deleted and then later a 8885 ** row with the same primary key values inserted while a session object is 8886 ** active, the resulting changeset will contain an UPDATE change instead of 8887 ** a DELETE and an INSERT. 8888 ** 8889 ** When a session object is disabled (see the [sqlite3session_enable()] API), 8890 ** it does not accumulate records when rows are inserted, updated or deleted. 8891 ** This may appear to have some counter-intuitive effects if a single row 8892 ** is written to more than once during a session. For example, if a row 8893 ** is inserted while a session object is enabled, then later deleted while 8894 ** the same session object is disabled, no INSERT record will appear in the 8895 ** changeset, even though the delete took place while the session was disabled. 8896 ** Or, if one field of a row is updated while a session is disabled, and 8897 ** another field of the same row is updated while the session is enabled, the 8898 ** resulting changeset will contain an UPDATE change that updates both fields. 8899 */ 8900 SQLITE_API int sqlite3session_changeset( 8901 sqlite3_session *pSession, /* Session object */ 8902 int *pnChangeset, /* OUT: Size of buffer at *ppChangeset */ 8903 void **ppChangeset /* OUT: Buffer containing changeset */ 8904 ); 8905 8906 /* 8907 ** CAPI3REF: Load The Difference Between Tables Into A Session 8908 ** 8909 ** If it is not already attached to the session object passed as the first 8910 ** argument, this function attaches table zTbl in the same manner as the 8911 ** [sqlite3session_attach()] function. If zTbl does not exist, or if it 8912 ** does not have a primary key, this function is a no-op (but does not return 8913 ** an error). 8914 ** 8915 ** Argument zFromDb must be the name of a database ("main", "temp" etc.) 8916 ** attached to the same database handle as the session object that contains 8917 ** a table compatible with the table attached to the session by this function. 8918 ** A table is considered compatible if it: 8919 ** 8920 ** <ul> 8921 ** <li> Has the same name, 8922 ** <li> Has the same set of columns declared in the same order, and 8923 ** <li> Has the same PRIMARY KEY definition. 8924 ** </ul> 8925 ** 8926 ** If the tables are not compatible, SQLITE_SCHEMA is returned. If the tables 8927 ** are compatible but do not have any PRIMARY KEY columns, it is not an error 8928 ** but no changes are added to the session object. As with other session 8929 ** APIs, tables without PRIMARY KEYs are simply ignored. 8930 ** 8931 ** This function adds a set of changes to the session object that could be 8932 ** used to update the table in database zFrom (call this the "from-table") 8933 ** so that its content is the same as the table attached to the session 8934 ** object (call this the "to-table"). Specifically: 8935 ** 8936 ** <ul> 8937 ** <li> For each row (primary key) that exists in the to-table but not in 8938 ** the from-table, an INSERT record is added to the session object. 8939 ** 8940 ** <li> For each row (primary key) that exists in the to-table but not in 8941 ** the from-table, a DELETE record is added to the session object. 8942 ** 8943 ** <li> For each row (primary key) that exists in both tables, but features 8944 ** different non-PK values in each, an UPDATE record is added to the 8945 ** session. 8946 ** </ul> 8947 ** 8948 ** To clarify, if this function is called and then a changeset constructed 8949 ** using [sqlite3session_changeset()], then after applying that changeset to 8950 ** database zFrom the contents of the two compatible tables would be 8951 ** identical. 8952 ** 8953 ** It an error if database zFrom does not exist or does not contain the 8954 ** required compatible table. 8955 ** 8956 ** If the operation successful, SQLITE_OK is returned. Otherwise, an SQLite 8957 ** error code. In this case, if argument pzErrMsg is not NULL, *pzErrMsg 8958 ** may be set to point to a buffer containing an English language error 8959 ** message. It is the responsibility of the caller to free this buffer using 8960 ** sqlite3_free(). 8961 */ 8962 SQLITE_API int sqlite3session_diff( 8963 sqlite3_session *pSession, 8964 const char *zFromDb, 8965 const char *zTbl, 8966 char **pzErrMsg 8967 ); 8968 8969 8970 /* 8971 ** CAPI3REF: Generate A Patchset From A Session Object 8972 ** 8973 ** The differences between a patchset and a changeset are that: 8974 ** 8975 ** <ul> 8976 ** <li> DELETE records consist of the primary key fields only. The 8977 ** original values of other fields are omitted. 8978 ** <li> The original values of any modified fields are omitted from 8979 ** UPDATE records. 8980 ** </ul> 8981 ** 8982 ** A patchset blob may be used with up to date versions of all 8983 ** sqlite3changeset_xxx API functions except for sqlite3changeset_invert(), 8984 ** which returns SQLITE_CORRUPT if it is passed a patchset. Similarly, 8985 ** attempting to use a patchset blob with old versions of the 8986 ** sqlite3changeset_xxx APIs also provokes an SQLITE_CORRUPT error. 8987 ** 8988 ** Because the non-primary key "old.*" fields are omitted, no 8989 ** SQLITE_CHANGESET_DATA conflicts can be detected or reported if a patchset 8990 ** is passed to the sqlite3changeset_apply() API. Other conflict types work 8991 ** in the same way as for changesets. 8992 ** 8993 ** Changes within a patchset are ordered in the same way as for changesets 8994 ** generated by the sqlite3session_changeset() function (i.e. all changes for 8995 ** a single table are grouped together, tables appear in the order in which 8996 ** they were attached to the session object). 8997 */ 8998 SQLITE_API int sqlite3session_patchset( 8999 sqlite3_session *pSession, /* Session object */ 9000 int *pnPatchset, /* OUT: Size of buffer at *ppChangeset */ 9001 void **ppPatchset /* OUT: Buffer containing changeset */ 9002 ); 9003 9004 /* 9005 ** CAPI3REF: Test if a changeset has recorded any changes. 9006 ** 9007 ** Return non-zero if no changes to attached tables have been recorded by 9008 ** the session object passed as the first argument. Otherwise, if one or 9009 ** more changes have been recorded, return zero. 9010 ** 9011 ** Even if this function returns zero, it is possible that calling 9012 ** [sqlite3session_changeset()] on the session handle may still return a 9013 ** changeset that contains no changes. This can happen when a row in 9014 ** an attached table is modified and then later on the original values 9015 ** are restored. However, if this function returns non-zero, then it is 9016 ** guaranteed that a call to sqlite3session_changeset() will return a 9017 ** changeset containing zero changes. 9018 */ 9019 SQLITE_API int sqlite3session_isempty(sqlite3_session *pSession); 9020 9021 /* 9022 ** CAPI3REF: Create An Iterator To Traverse A Changeset 9023 ** 9024 ** Create an iterator used to iterate through the contents of a changeset. 9025 ** If successful, *pp is set to point to the iterator handle and SQLITE_OK 9026 ** is returned. Otherwise, if an error occurs, *pp is set to zero and an 9027 ** SQLite error code is returned. 9028 ** 9029 ** The following functions can be used to advance and query a changeset 9030 ** iterator created by this function: 9031 ** 9032 ** <ul> 9033 ** <li> [sqlite3changeset_next()] 9034 ** <li> [sqlite3changeset_op()] 9035 ** <li> [sqlite3changeset_new()] 9036 ** <li> [sqlite3changeset_old()] 9037 ** </ul> 9038 ** 9039 ** It is the responsibility of the caller to eventually destroy the iterator 9040 ** by passing it to [sqlite3changeset_finalize()]. The buffer containing the 9041 ** changeset (pChangeset) must remain valid until after the iterator is 9042 ** destroyed. 9043 ** 9044 ** Assuming the changeset blob was created by one of the 9045 ** [sqlite3session_changeset()], [sqlite3changeset_concat()] or 9046 ** [sqlite3changeset_invert()] functions, all changes within the changeset 9047 ** that apply to a single table are grouped together. This means that when 9048 ** an application iterates through a changeset using an iterator created by 9049 ** this function, all changes that relate to a single table are visited 9050 ** consecutively. There is no chance that the iterator will visit a change 9051 ** the applies to table X, then one for table Y, and then later on visit 9052 ** another change for table X. 9053 */ 9054 SQLITE_API int sqlite3changeset_start( 9055 sqlite3_changeset_iter **pp, /* OUT: New changeset iterator handle */ 9056 int nChangeset, /* Size of changeset blob in bytes */ 9057 void *pChangeset /* Pointer to blob containing changeset */ 9058 ); 9059 9060 9061 /* 9062 ** CAPI3REF: Advance A Changeset Iterator 9063 ** 9064 ** This function may only be used with iterators created by function 9065 ** [sqlite3changeset_start()]. If it is called on an iterator passed to 9066 ** a conflict-handler callback by [sqlite3changeset_apply()], SQLITE_MISUSE 9067 ** is returned and the call has no effect. 9068 ** 9069 ** Immediately after an iterator is created by sqlite3changeset_start(), it 9070 ** does not point to any change in the changeset. Assuming the changeset 9071 ** is not empty, the first call to this function advances the iterator to 9072 ** point to the first change in the changeset. Each subsequent call advances 9073 ** the iterator to point to the next change in the changeset (if any). If 9074 ** no error occurs and the iterator points to a valid change after a call 9075 ** to sqlite3changeset_next() has advanced it, SQLITE_ROW is returned. 9076 ** Otherwise, if all changes in the changeset have already been visited, 9077 ** SQLITE_DONE is returned. 9078 ** 9079 ** If an error occurs, an SQLite error code is returned. Possible error 9080 ** codes include SQLITE_CORRUPT (if the changeset buffer is corrupt) or 9081 ** SQLITE_NOMEM. 9082 */ 9083 SQLITE_API int sqlite3changeset_next(sqlite3_changeset_iter *pIter); 9084 9085 /* 9086 ** CAPI3REF: Obtain The Current Operation From A Changeset Iterator 9087 ** 9088 ** The pIter argument passed to this function may either be an iterator 9089 ** passed to a conflict-handler by [sqlite3changeset_apply()], or an iterator 9090 ** created by [sqlite3changeset_start()]. In the latter case, the most recent 9091 ** call to [sqlite3changeset_next()] must have returned [SQLITE_ROW]. If this 9092 ** is not the case, this function returns [SQLITE_MISUSE]. 9093 ** 9094 ** If argument pzTab is not NULL, then *pzTab is set to point to a 9095 ** nul-terminated utf-8 encoded string containing the name of the table 9096 ** affected by the current change. The buffer remains valid until either 9097 ** sqlite3changeset_next() is called on the iterator or until the 9098 ** conflict-handler function returns. If pnCol is not NULL, then *pnCol is 9099 ** set to the number of columns in the table affected by the change. If 9100 ** pbIncorrect is not NULL, then *pbIndirect is set to true (1) if the change 9101 ** is an indirect change, or false (0) otherwise. See the documentation for 9102 ** [sqlite3session_indirect()] for a description of direct and indirect 9103 ** changes. Finally, if pOp is not NULL, then *pOp is set to one of 9104 ** [SQLITE_INSERT], [SQLITE_DELETE] or [SQLITE_UPDATE], depending on the 9105 ** type of change that the iterator currently points to. 9106 ** 9107 ** If no error occurs, SQLITE_OK is returned. If an error does occur, an 9108 ** SQLite error code is returned. The values of the output variables may not 9109 ** be trusted in this case. 9110 */ 9111 SQLITE_API int sqlite3changeset_op( 9112 sqlite3_changeset_iter *pIter, /* Iterator object */ 9113 const char **pzTab, /* OUT: Pointer to table name */ 9114 int *pnCol, /* OUT: Number of columns in table */ 9115 int *pOp, /* OUT: SQLITE_INSERT, DELETE or UPDATE */ 9116 int *pbIndirect /* OUT: True for an 'indirect' change */ 9117 ); 9118 9119 /* 9120 ** CAPI3REF: Obtain The Primary Key Definition Of A Table 9121 ** 9122 ** For each modified table, a changeset includes the following: 9123 ** 9124 ** <ul> 9125 ** <li> The number of columns in the table, and 9126 ** <li> Which of those columns make up the tables PRIMARY KEY. 9127 ** </ul> 9128 ** 9129 ** This function is used to find which columns comprise the PRIMARY KEY of 9130 ** the table modified by the change that iterator pIter currently points to. 9131 ** If successful, *pabPK is set to point to an array of nCol entries, where 9132 ** nCol is the number of columns in the table. Elements of *pabPK are set to 9133 ** 0x01 if the corresponding column is part of the tables primary key, or 9134 ** 0x00 if it is not. 9135 ** 9136 ** If argument pnCol is not NULL, then *pnCol is set to the number of columns 9137 ** in the table. 9138 ** 9139 ** If this function is called when the iterator does not point to a valid 9140 ** entry, SQLITE_MISUSE is returned and the output variables zeroed. Otherwise, 9141 ** SQLITE_OK is returned and the output variables populated as described 9142 ** above. 9143 */ 9144 SQLITE_API int sqlite3changeset_pk( 9145 sqlite3_changeset_iter *pIter, /* Iterator object */ 9146 unsigned char **pabPK, /* OUT: Array of boolean - true for PK cols */ 9147 int *pnCol /* OUT: Number of entries in output array */ 9148 ); 9149 9150 /* 9151 ** CAPI3REF: Obtain old.* Values From A Changeset Iterator 9152 ** 9153 ** The pIter argument passed to this function may either be an iterator 9154 ** passed to a conflict-handler by [sqlite3changeset_apply()], or an iterator 9155 ** created by [sqlite3changeset_start()]. In the latter case, the most recent 9156 ** call to [sqlite3changeset_next()] must have returned SQLITE_ROW. 9157 ** Furthermore, it may only be called if the type of change that the iterator 9158 ** currently points to is either [SQLITE_DELETE] or [SQLITE_UPDATE]. Otherwise, 9159 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL. 9160 ** 9161 ** Argument iVal must be greater than or equal to 0, and less than the number 9162 ** of columns in the table affected by the current change. Otherwise, 9163 ** [SQLITE_RANGE] is returned and *ppValue is set to NULL. 9164 ** 9165 ** If successful, this function sets *ppValue to point to a protected 9166 ** sqlite3_value object containing the iVal'th value from the vector of 9167 ** original row values stored as part of the UPDATE or DELETE change and 9168 ** returns SQLITE_OK. The name of the function comes from the fact that this 9169 ** is similar to the "old.*" columns available to update or delete triggers. 9170 ** 9171 ** If some other error occurs (e.g. an OOM condition), an SQLite error code 9172 ** is returned and *ppValue is set to NULL. 9173 */ 9174 SQLITE_API int sqlite3changeset_old( 9175 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 9176 int iVal, /* Column number */ 9177 sqlite3_value **ppValue /* OUT: Old value (or NULL pointer) */ 9178 ); 9179 9180 /* 9181 ** CAPI3REF: Obtain new.* Values From A Changeset Iterator 9182 ** 9183 ** The pIter argument passed to this function may either be an iterator 9184 ** passed to a conflict-handler by [sqlite3changeset_apply()], or an iterator 9185 ** created by [sqlite3changeset_start()]. In the latter case, the most recent 9186 ** call to [sqlite3changeset_next()] must have returned SQLITE_ROW. 9187 ** Furthermore, it may only be called if the type of change that the iterator 9188 ** currently points to is either [SQLITE_UPDATE] or [SQLITE_INSERT]. Otherwise, 9189 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL. 9190 ** 9191 ** Argument iVal must be greater than or equal to 0, and less than the number 9192 ** of columns in the table affected by the current change. Otherwise, 9193 ** [SQLITE_RANGE] is returned and *ppValue is set to NULL. 9194 ** 9195 ** If successful, this function sets *ppValue to point to a protected 9196 ** sqlite3_value object containing the iVal'th value from the vector of 9197 ** new row values stored as part of the UPDATE or INSERT change and 9198 ** returns SQLITE_OK. If the change is an UPDATE and does not include 9199 ** a new value for the requested column, *ppValue is set to NULL and 9200 ** SQLITE_OK returned. The name of the function comes from the fact that 9201 ** this is similar to the "new.*" columns available to update or delete 9202 ** triggers. 9203 ** 9204 ** If some other error occurs (e.g. an OOM condition), an SQLite error code 9205 ** is returned and *ppValue is set to NULL. 9206 */ 9207 SQLITE_API int sqlite3changeset_new( 9208 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 9209 int iVal, /* Column number */ 9210 sqlite3_value **ppValue /* OUT: New value (or NULL pointer) */ 9211 ); 9212 9213 /* 9214 ** CAPI3REF: Obtain Conflicting Row Values From A Changeset Iterator 9215 ** 9216 ** This function should only be used with iterator objects passed to a 9217 ** conflict-handler callback by [sqlite3changeset_apply()] with either 9218 ** [SQLITE_CHANGESET_DATA] or [SQLITE_CHANGESET_CONFLICT]. If this function 9219 ** is called on any other iterator, [SQLITE_MISUSE] is returned and *ppValue 9220 ** is set to NULL. 9221 ** 9222 ** Argument iVal must be greater than or equal to 0, and less than the number 9223 ** of columns in the table affected by the current change. Otherwise, 9224 ** [SQLITE_RANGE] is returned and *ppValue is set to NULL. 9225 ** 9226 ** If successful, this function sets *ppValue to point to a protected 9227 ** sqlite3_value object containing the iVal'th value from the 9228 ** "conflicting row" associated with the current conflict-handler callback 9229 ** and returns SQLITE_OK. 9230 ** 9231 ** If some other error occurs (e.g. an OOM condition), an SQLite error code 9232 ** is returned and *ppValue is set to NULL. 9233 */ 9234 SQLITE_API int sqlite3changeset_conflict( 9235 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 9236 int iVal, /* Column number */ 9237 sqlite3_value **ppValue /* OUT: Value from conflicting row */ 9238 ); 9239 9240 /* 9241 ** CAPI3REF: Determine The Number Of Foreign Key Constraint Violations 9242 ** 9243 ** This function may only be called with an iterator passed to an 9244 ** SQLITE_CHANGESET_FOREIGN_KEY conflict handler callback. In this case 9245 ** it sets the output variable to the total number of known foreign key 9246 ** violations in the destination database and returns SQLITE_OK. 9247 ** 9248 ** In all other cases this function returns SQLITE_MISUSE. 9249 */ 9250 SQLITE_API int sqlite3changeset_fk_conflicts( 9251 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 9252 int *pnOut /* OUT: Number of FK violations */ 9253 ); 9254 9255 9256 /* 9257 ** CAPI3REF: Finalize A Changeset Iterator 9258 ** 9259 ** This function is used to finalize an iterator allocated with 9260 ** [sqlite3changeset_start()]. 9261 ** 9262 ** This function should only be called on iterators created using the 9263 ** [sqlite3changeset_start()] function. If an application calls this 9264 ** function with an iterator passed to a conflict-handler by 9265 ** [sqlite3changeset_apply()], [SQLITE_MISUSE] is immediately returned and the 9266 ** call has no effect. 9267 ** 9268 ** If an error was encountered within a call to an sqlite3changeset_xxx() 9269 ** function (for example an [SQLITE_CORRUPT] in [sqlite3changeset_next()] or an 9270 ** [SQLITE_NOMEM] in [sqlite3changeset_new()]) then an error code corresponding 9271 ** to that error is returned by this function. Otherwise, SQLITE_OK is 9272 ** returned. This is to allow the following pattern (pseudo-code): 9273 ** 9274 ** sqlite3changeset_start(); 9275 ** while( SQLITE_ROW==sqlite3changeset_next() ){ 9276 ** // Do something with change. 9277 ** } 9278 ** rc = sqlite3changeset_finalize(); 9279 ** if( rc!=SQLITE_OK ){ 9280 ** // An error has occurred 9281 ** } 9282 */ 9283 SQLITE_API int sqlite3changeset_finalize(sqlite3_changeset_iter *pIter); 9284 9285 /* 9286 ** CAPI3REF: Invert A Changeset 9287 ** 9288 ** This function is used to "invert" a changeset object. Applying an inverted 9289 ** changeset to a database reverses the effects of applying the uninverted 9290 ** changeset. Specifically: 9291 ** 9292 ** <ul> 9293 ** <li> Each DELETE change is changed to an INSERT, and 9294 ** <li> Each INSERT change is changed to a DELETE, and 9295 ** <li> For each UPDATE change, the old.* and new.* values are exchanged. 9296 ** </ul> 9297 ** 9298 ** This function does not change the order in which changes appear within 9299 ** the changeset. It merely reverses the sense of each individual change. 9300 ** 9301 ** If successful, a pointer to a buffer containing the inverted changeset 9302 ** is stored in *ppOut, the size of the same buffer is stored in *pnOut, and 9303 ** SQLITE_OK is returned. If an error occurs, both *pnOut and *ppOut are 9304 ** zeroed and an SQLite error code returned. 9305 ** 9306 ** It is the responsibility of the caller to eventually call sqlite3_free() 9307 ** on the *ppOut pointer to free the buffer allocation following a successful 9308 ** call to this function. 9309 ** 9310 ** WARNING/TODO: This function currently assumes that the input is a valid 9311 ** changeset. If it is not, the results are undefined. 9312 */ 9313 SQLITE_API int sqlite3changeset_invert( 9314 int nIn, const void *pIn, /* Input changeset */ 9315 int *pnOut, void **ppOut /* OUT: Inverse of input */ 9316 ); 9317 9318 /* 9319 ** CAPI3REF: Concatenate Two Changeset Objects 9320 ** 9321 ** This function is used to concatenate two changesets, A and B, into a 9322 ** single changeset. The result is a changeset equivalent to applying 9323 ** changeset A followed by changeset B. 9324 ** 9325 ** This function combines the two input changesets using an 9326 ** sqlite3_changegroup object. Calling it produces similar results as the 9327 ** following code fragment: 9328 ** 9329 ** sqlite3_changegroup *pGrp; 9330 ** rc = sqlite3_changegroup_new(&pGrp); 9331 ** if( rc==SQLITE_OK ) rc = sqlite3changegroup_add(pGrp, nA, pA); 9332 ** if( rc==SQLITE_OK ) rc = sqlite3changegroup_add(pGrp, nB, pB); 9333 ** if( rc==SQLITE_OK ){ 9334 ** rc = sqlite3changegroup_output(pGrp, pnOut, ppOut); 9335 ** }else{ 9336 ** *ppOut = 0; 9337 ** *pnOut = 0; 9338 ** } 9339 ** 9340 ** Refer to the sqlite3_changegroup documentation below for details. 9341 */ 9342 SQLITE_API int sqlite3changeset_concat( 9343 int nA, /* Number of bytes in buffer pA */ 9344 void *pA, /* Pointer to buffer containing changeset A */ 9345 int nB, /* Number of bytes in buffer pB */ 9346 void *pB, /* Pointer to buffer containing changeset B */ 9347 int *pnOut, /* OUT: Number of bytes in output changeset */ 9348 void **ppOut /* OUT: Buffer containing output changeset */ 9349 ); 9350 9351 9352 /* 9353 ** CAPI3REF: Changegroup Handle 9354 */ 9355 typedef struct sqlite3_changegroup sqlite3_changegroup; 9356 9357 /* 9358 ** CAPI3REF: Create A New Changegroup Object 9359 ** 9360 ** An sqlite3_changegroup object is used to combine two or more changesets 9361 ** (or patchsets) into a single changeset (or patchset). A single changegroup 9362 ** object may combine changesets or patchsets, but not both. The output is 9363 ** always in the same format as the input. 9364 ** 9365 ** If successful, this function returns SQLITE_OK and populates (*pp) with 9366 ** a pointer to a new sqlite3_changegroup object before returning. The caller 9367 ** should eventually free the returned object using a call to 9368 ** sqlite3changegroup_delete(). If an error occurs, an SQLite error code 9369 ** (i.e. SQLITE_NOMEM) is returned and *pp is set to NULL. 9370 ** 9371 ** The usual usage pattern for an sqlite3_changegroup object is as follows: 9372 ** 9373 ** <ul> 9374 ** <li> It is created using a call to sqlite3changegroup_new(). 9375 ** 9376 ** <li> Zero or more changesets (or patchsets) are added to the object 9377 ** by calling sqlite3changegroup_add(). 9378 ** 9379 ** <li> The result of combining all input changesets together is obtained 9380 ** by the application via a call to sqlite3changegroup_output(). 9381 ** 9382 ** <li> The object is deleted using a call to sqlite3changegroup_delete(). 9383 ** </ul> 9384 ** 9385 ** Any number of calls to add() and output() may be made between the calls to 9386 ** new() and delete(), and in any order. 9387 ** 9388 ** As well as the regular sqlite3changegroup_add() and 9389 ** sqlite3changegroup_output() functions, also available are the streaming 9390 ** versions sqlite3changegroup_add_strm() and sqlite3changegroup_output_strm(). 9391 */ 9392 int sqlite3changegroup_new(sqlite3_changegroup **pp); 9393 9394 /* 9395 ** CAPI3REF: Add A Changeset To A Changegroup 9396 ** 9397 ** Add all changes within the changeset (or patchset) in buffer pData (size 9398 ** nData bytes) to the changegroup. 9399 ** 9400 ** If the buffer contains a patchset, then all prior calls to this function 9401 ** on the same changegroup object must also have specified patchsets. Or, if 9402 ** the buffer contains a changeset, so must have the earlier calls to this 9403 ** function. Otherwise, SQLITE_ERROR is returned and no changes are added 9404 ** to the changegroup. 9405 ** 9406 ** Rows within the changeset and changegroup are identified by the values in 9407 ** their PRIMARY KEY columns. A change in the changeset is considered to 9408 ** apply to the same row as a change already present in the changegroup if 9409 ** the two rows have the same primary key. 9410 ** 9411 ** Changes to rows that do not already appear in the changegroup are 9412 ** simply copied into it. Or, if both the new changeset and the changegroup 9413 ** contain changes that apply to a single row, the final contents of the 9414 ** changegroup depends on the type of each change, as follows: 9415 ** 9416 ** <table border=1 style="margin-left:8ex;margin-right:8ex"> 9417 ** <tr><th style="white-space:pre">Existing Change </th> 9418 ** <th style="white-space:pre">New Change </th> 9419 ** <th>Output Change 9420 ** <tr><td>INSERT <td>INSERT <td> 9421 ** The new change is ignored. This case does not occur if the new 9422 ** changeset was recorded immediately after the changesets already 9423 ** added to the changegroup. 9424 ** <tr><td>INSERT <td>UPDATE <td> 9425 ** The INSERT change remains in the changegroup. The values in the 9426 ** INSERT change are modified as if the row was inserted by the 9427 ** existing change and then updated according to the new change. 9428 ** <tr><td>INSERT <td>DELETE <td> 9429 ** The existing INSERT is removed from the changegroup. The DELETE is 9430 ** not added. 9431 ** <tr><td>UPDATE <td>INSERT <td> 9432 ** The new change is ignored. This case does not occur if the new 9433 ** changeset was recorded immediately after the changesets already 9434 ** added to the changegroup. 9435 ** <tr><td>UPDATE <td>UPDATE <td> 9436 ** The existing UPDATE remains within the changegroup. It is amended 9437 ** so that the accompanying values are as if the row was updated once 9438 ** by the existing change and then again by the new change. 9439 ** <tr><td>UPDATE <td>DELETE <td> 9440 ** The existing UPDATE is replaced by the new DELETE within the 9441 ** changegroup. 9442 ** <tr><td>DELETE <td>INSERT <td> 9443 ** If one or more of the column values in the row inserted by the 9444 ** new change differ from those in the row deleted by the existing 9445 ** change, the existing DELETE is replaced by an UPDATE within the 9446 ** changegroup. Otherwise, if the inserted row is exactly the same 9447 ** as the deleted row, the existing DELETE is simply discarded. 9448 ** <tr><td>DELETE <td>UPDATE <td> 9449 ** The new change is ignored. This case does not occur if the new 9450 ** changeset was recorded immediately after the changesets already 9451 ** added to the changegroup. 9452 ** <tr><td>DELETE <td>DELETE <td> 9453 ** The new change is ignored. This case does not occur if the new 9454 ** changeset was recorded immediately after the changesets already 9455 ** added to the changegroup. 9456 ** </table> 9457 ** 9458 ** If the new changeset contains changes to a table that is already present 9459 ** in the changegroup, then the number of columns and the position of the 9460 ** primary key columns for the table must be consistent. If this is not the 9461 ** case, this function fails with SQLITE_SCHEMA. If the input changeset 9462 ** appears to be corrupt and the corruption is detected, SQLITE_CORRUPT is 9463 ** returned. Or, if an out-of-memory condition occurs during processing, this 9464 ** function returns SQLITE_NOMEM. In all cases, if an error occurs the 9465 ** final contents of the changegroup is undefined. 9466 ** 9467 ** If no error occurs, SQLITE_OK is returned. 9468 */ 9469 int sqlite3changegroup_add(sqlite3_changegroup*, int nData, void *pData); 9470 9471 /* 9472 ** CAPI3REF: Obtain A Composite Changeset From A Changegroup 9473 ** 9474 ** Obtain a buffer containing a changeset (or patchset) representing the 9475 ** current contents of the changegroup. If the inputs to the changegroup 9476 ** were themselves changesets, the output is a changeset. Or, if the 9477 ** inputs were patchsets, the output is also a patchset. 9478 ** 9479 ** As with the output of the sqlite3session_changeset() and 9480 ** sqlite3session_patchset() functions, all changes related to a single 9481 ** table are grouped together in the output of this function. Tables appear 9482 ** in the same order as for the very first changeset added to the changegroup. 9483 ** If the second or subsequent changesets added to the changegroup contain 9484 ** changes for tables that do not appear in the first changeset, they are 9485 ** appended onto the end of the output changeset, again in the order in 9486 ** which they are first encountered. 9487 ** 9488 ** If an error occurs, an SQLite error code is returned and the output 9489 ** variables (*pnData) and (*ppData) are set to 0. Otherwise, SQLITE_OK 9490 ** is returned and the output variables are set to the size of and a 9491 ** pointer to the output buffer, respectively. In this case it is the 9492 ** responsibility of the caller to eventually free the buffer using a 9493 ** call to sqlite3_free(). 9494 */ 9495 int sqlite3changegroup_output( 9496 sqlite3_changegroup*, 9497 int *pnData, /* OUT: Size of output buffer in bytes */ 9498 void **ppData /* OUT: Pointer to output buffer */ 9499 ); 9500 9501 /* 9502 ** CAPI3REF: Delete A Changegroup Object 9503 */ 9504 void sqlite3changegroup_delete(sqlite3_changegroup*); 9505 9506 /* 9507 ** CAPI3REF: Apply A Changeset To A Database 9508 ** 9509 ** Apply a changeset to a database. This function attempts to update the 9510 ** "main" database attached to handle db with the changes found in the 9511 ** changeset passed via the second and third arguments. 9512 ** 9513 ** The fourth argument (xFilter) passed to this function is the "filter 9514 ** callback". If it is not NULL, then for each table affected by at least one 9515 ** change in the changeset, the filter callback is invoked with 9516 ** the table name as the second argument, and a copy of the context pointer 9517 ** passed as the sixth argument to this function as the first. If the "filter 9518 ** callback" returns zero, then no attempt is made to apply any changes to 9519 ** the table. Otherwise, if the return value is non-zero or the xFilter 9520 ** argument to this function is NULL, all changes related to the table are 9521 ** attempted. 9522 ** 9523 ** For each table that is not excluded by the filter callback, this function 9524 ** tests that the target database contains a compatible table. A table is 9525 ** considered compatible if all of the following are true: 9526 ** 9527 ** <ul> 9528 ** <li> The table has the same name as the name recorded in the 9529 ** changeset, and 9530 ** <li> The table has at least as many columns as recorded in the 9531 ** changeset, and 9532 ** <li> The table has primary key columns in the same position as 9533 ** recorded in the changeset. 9534 ** </ul> 9535 ** 9536 ** If there is no compatible table, it is not an error, but none of the 9537 ** changes associated with the table are applied. A warning message is issued 9538 ** via the sqlite3_log() mechanism with the error code SQLITE_SCHEMA. At most 9539 ** one such warning is issued for each table in the changeset. 9540 ** 9541 ** For each change for which there is a compatible table, an attempt is made 9542 ** to modify the table contents according to the UPDATE, INSERT or DELETE 9543 ** change. If a change cannot be applied cleanly, the conflict handler 9544 ** function passed as the fifth argument to sqlite3changeset_apply() may be 9545 ** invoked. A description of exactly when the conflict handler is invoked for 9546 ** each type of change is below. 9547 ** 9548 ** Unlike the xFilter argument, xConflict may not be passed NULL. The results 9549 ** of passing anything other than a valid function pointer as the xConflict 9550 ** argument are undefined. 9551 ** 9552 ** Each time the conflict handler function is invoked, it must return one 9553 ** of [SQLITE_CHANGESET_OMIT], [SQLITE_CHANGESET_ABORT] or 9554 ** [SQLITE_CHANGESET_REPLACE]. SQLITE_CHANGESET_REPLACE may only be returned 9555 ** if the second argument passed to the conflict handler is either 9556 ** SQLITE_CHANGESET_DATA or SQLITE_CHANGESET_CONFLICT. If the conflict-handler 9557 ** returns an illegal value, any changes already made are rolled back and 9558 ** the call to sqlite3changeset_apply() returns SQLITE_MISUSE. Different 9559 ** actions are taken by sqlite3changeset_apply() depending on the value 9560 ** returned by each invocation of the conflict-handler function. Refer to 9561 ** the documentation for the three 9562 ** [SQLITE_CHANGESET_OMIT|available return values] for details. 9563 ** 9564 ** <dl> 9565 ** <dt>DELETE Changes<dd> 9566 ** For each DELETE change, this function checks if the target database 9567 ** contains a row with the same primary key value (or values) as the 9568 ** original row values stored in the changeset. If it does, and the values 9569 ** stored in all non-primary key columns also match the values stored in 9570 ** the changeset the row is deleted from the target database. 9571 ** 9572 ** If a row with matching primary key values is found, but one or more of 9573 ** the non-primary key fields contains a value different from the original 9574 ** row value stored in the changeset, the conflict-handler function is 9575 ** invoked with [SQLITE_CHANGESET_DATA] as the second argument. If the 9576 ** database table has more columns than are recorded in the changeset, 9577 ** only the values of those non-primary key fields are compared against 9578 ** the current database contents - any trailing database table columns 9579 ** are ignored. 9580 ** 9581 ** If no row with matching primary key values is found in the database, 9582 ** the conflict-handler function is invoked with [SQLITE_CHANGESET_NOTFOUND] 9583 ** passed as the second argument. 9584 ** 9585 ** If the DELETE operation is attempted, but SQLite returns SQLITE_CONSTRAINT 9586 ** (which can only happen if a foreign key constraint is violated), the 9587 ** conflict-handler function is invoked with [SQLITE_CHANGESET_CONSTRAINT] 9588 ** passed as the second argument. This includes the case where the DELETE 9589 ** operation is attempted because an earlier call to the conflict handler 9590 ** function returned [SQLITE_CHANGESET_REPLACE]. 9591 ** 9592 ** <dt>INSERT Changes<dd> 9593 ** For each INSERT change, an attempt is made to insert the new row into 9594 ** the database. If the changeset row contains fewer fields than the 9595 ** database table, the trailing fields are populated with their default 9596 ** values. 9597 ** 9598 ** If the attempt to insert the row fails because the database already 9599 ** contains a row with the same primary key values, the conflict handler 9600 ** function is invoked with the second argument set to 9601 ** [SQLITE_CHANGESET_CONFLICT]. 9602 ** 9603 ** If the attempt to insert the row fails because of some other constraint 9604 ** violation (e.g. NOT NULL or UNIQUE), the conflict handler function is 9605 ** invoked with the second argument set to [SQLITE_CHANGESET_CONSTRAINT]. 9606 ** This includes the case where the INSERT operation is re-attempted because 9607 ** an earlier call to the conflict handler function returned 9608 ** [SQLITE_CHANGESET_REPLACE]. 9609 ** 9610 ** <dt>UPDATE Changes<dd> 9611 ** For each UPDATE change, this function checks if the target database 9612 ** contains a row with the same primary key value (or values) as the 9613 ** original row values stored in the changeset. If it does, and the values 9614 ** stored in all modified non-primary key columns also match the values 9615 ** stored in the changeset the row is updated within the target database. 9616 ** 9617 ** If a row with matching primary key values is found, but one or more of 9618 ** the modified non-primary key fields contains a value different from an 9619 ** original row value stored in the changeset, the conflict-handler function 9620 ** is invoked with [SQLITE_CHANGESET_DATA] as the second argument. Since 9621 ** UPDATE changes only contain values for non-primary key fields that are 9622 ** to be modified, only those fields need to match the original values to 9623 ** avoid the SQLITE_CHANGESET_DATA conflict-handler callback. 9624 ** 9625 ** If no row with matching primary key values is found in the database, 9626 ** the conflict-handler function is invoked with [SQLITE_CHANGESET_NOTFOUND] 9627 ** passed as the second argument. 9628 ** 9629 ** If the UPDATE operation is attempted, but SQLite returns 9630 ** SQLITE_CONSTRAINT, the conflict-handler function is invoked with 9631 ** [SQLITE_CHANGESET_CONSTRAINT] passed as the second argument. 9632 ** This includes the case where the UPDATE operation is attempted after 9633 ** an earlier call to the conflict handler function returned 9634 ** [SQLITE_CHANGESET_REPLACE]. 9635 ** </dl> 9636 ** 9637 ** It is safe to execute SQL statements, including those that write to the 9638 ** table that the callback related to, from within the xConflict callback. 9639 ** This can be used to further customize the applications conflict 9640 ** resolution strategy. 9641 ** 9642 ** All changes made by this function are enclosed in a savepoint transaction. 9643 ** If any other error (aside from a constraint failure when attempting to 9644 ** write to the target database) occurs, then the savepoint transaction is 9645 ** rolled back, restoring the target database to its original state, and an 9646 ** SQLite error code returned. 9647 */ 9648 SQLITE_API int sqlite3changeset_apply( 9649 sqlite3 *db, /* Apply change to "main" db of this handle */ 9650 int nChangeset, /* Size of changeset in bytes */ 9651 void *pChangeset, /* Changeset blob */ 9652 int(*xFilter)( 9653 void *pCtx, /* Copy of sixth arg to _apply() */ 9654 const char *zTab /* Table name */ 9655 ), 9656 int(*xConflict)( 9657 void *pCtx, /* Copy of sixth arg to _apply() */ 9658 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 9659 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 9660 ), 9661 void *pCtx /* First argument passed to xConflict */ 9662 ); 9663 9664 /* 9665 ** CAPI3REF: Constants Passed To The Conflict Handler 9666 ** 9667 ** Values that may be passed as the second argument to a conflict-handler. 9668 ** 9669 ** <dl> 9670 ** <dt>SQLITE_CHANGESET_DATA<dd> 9671 ** The conflict handler is invoked with CHANGESET_DATA as the second argument 9672 ** when processing a DELETE or UPDATE change if a row with the required 9673 ** PRIMARY KEY fields is present in the database, but one or more other 9674 ** (non primary-key) fields modified by the update do not contain the 9675 ** expected "before" values. 9676 ** 9677 ** The conflicting row, in this case, is the database row with the matching 9678 ** primary key. 9679 ** 9680 ** <dt>SQLITE_CHANGESET_NOTFOUND<dd> 9681 ** The conflict handler is invoked with CHANGESET_NOTFOUND as the second 9682 ** argument when processing a DELETE or UPDATE change if a row with the 9683 ** required PRIMARY KEY fields is not present in the database. 9684 ** 9685 ** There is no conflicting row in this case. The results of invoking the 9686 ** sqlite3changeset_conflict() API are undefined. 9687 ** 9688 ** <dt>SQLITE_CHANGESET_CONFLICT<dd> 9689 ** CHANGESET_CONFLICT is passed as the second argument to the conflict 9690 ** handler while processing an INSERT change if the operation would result 9691 ** in duplicate primary key values. 9692 ** 9693 ** The conflicting row in this case is the database row with the matching 9694 ** primary key. 9695 ** 9696 ** <dt>SQLITE_CHANGESET_FOREIGN_KEY<dd> 9697 ** If foreign key handling is enabled, and applying a changeset leaves the 9698 ** database in a state containing foreign key violations, the conflict 9699 ** handler is invoked with CHANGESET_FOREIGN_KEY as the second argument 9700 ** exactly once before the changeset is committed. If the conflict handler 9701 ** returns CHANGESET_OMIT, the changes, including those that caused the 9702 ** foreign key constraint violation, are committed. Or, if it returns 9703 ** CHANGESET_ABORT, the changeset is rolled back. 9704 ** 9705 ** No current or conflicting row information is provided. The only function 9706 ** it is possible to call on the supplied sqlite3_changeset_iter handle 9707 ** is sqlite3changeset_fk_conflicts(). 9708 ** 9709 ** <dt>SQLITE_CHANGESET_CONSTRAINT<dd> 9710 ** If any other constraint violation occurs while applying a change (i.e. 9711 ** a UNIQUE, CHECK or NOT NULL constraint), the conflict handler is 9712 ** invoked with CHANGESET_CONSTRAINT as the second argument. 9713 ** 9714 ** There is no conflicting row in this case. The results of invoking the 9715 ** sqlite3changeset_conflict() API are undefined. 9716 ** 9717 ** </dl> 9718 */ 9719 #define SQLITE_CHANGESET_DATA 1 9720 #define SQLITE_CHANGESET_NOTFOUND 2 9721 #define SQLITE_CHANGESET_CONFLICT 3 9722 #define SQLITE_CHANGESET_CONSTRAINT 4 9723 #define SQLITE_CHANGESET_FOREIGN_KEY 5 9724 9725 /* 9726 ** CAPI3REF: Constants Returned By The Conflict Handler 9727 ** 9728 ** A conflict handler callback must return one of the following three values. 9729 ** 9730 ** <dl> 9731 ** <dt>SQLITE_CHANGESET_OMIT<dd> 9732 ** If a conflict handler returns this value no special action is taken. The 9733 ** change that caused the conflict is not applied. The session module 9734 ** continues to the next change in the changeset. 9735 ** 9736 ** <dt>SQLITE_CHANGESET_REPLACE<dd> 9737 ** This value may only be returned if the second argument to the conflict 9738 ** handler was SQLITE_CHANGESET_DATA or SQLITE_CHANGESET_CONFLICT. If this 9739 ** is not the case, any changes applied so far are rolled back and the 9740 ** call to sqlite3changeset_apply() returns SQLITE_MISUSE. 9741 ** 9742 ** If CHANGESET_REPLACE is returned by an SQLITE_CHANGESET_DATA conflict 9743 ** handler, then the conflicting row is either updated or deleted, depending 9744 ** on the type of change. 9745 ** 9746 ** If CHANGESET_REPLACE is returned by an SQLITE_CHANGESET_CONFLICT conflict 9747 ** handler, then the conflicting row is removed from the database and a 9748 ** second attempt to apply the change is made. If this second attempt fails, 9749 ** the original row is restored to the database before continuing. 9750 ** 9751 ** <dt>SQLITE_CHANGESET_ABORT<dd> 9752 ** If this value is returned, any changes applied so far are rolled back 9753 ** and the call to sqlite3changeset_apply() returns SQLITE_ABORT. 9754 ** </dl> 9755 */ 9756 #define SQLITE_CHANGESET_OMIT 0 9757 #define SQLITE_CHANGESET_REPLACE 1 9758 #define SQLITE_CHANGESET_ABORT 2 9759 9760 /* 9761 ** CAPI3REF: Streaming Versions of API functions. 9762 ** 9763 ** The six streaming API xxx_strm() functions serve similar purposes to the 9764 ** corresponding non-streaming API functions: 9765 ** 9766 ** <table border=1 style="margin-left:8ex;margin-right:8ex"> 9767 ** <tr><th>Streaming function<th>Non-streaming equivalent</th> 9768 ** <tr><td>sqlite3changeset_apply_str<td>[sqlite3changeset_apply] 9769 ** <tr><td>sqlite3changeset_concat_str<td>[sqlite3changeset_concat] 9770 ** <tr><td>sqlite3changeset_invert_str<td>[sqlite3changeset_invert] 9771 ** <tr><td>sqlite3changeset_start_str<td>[sqlite3changeset_start] 9772 ** <tr><td>sqlite3session_changeset_str<td>[sqlite3session_changeset] 9773 ** <tr><td>sqlite3session_patchset_str<td>[sqlite3session_patchset] 9774 ** </table> 9775 ** 9776 ** Non-streaming functions that accept changesets (or patchsets) as input 9777 ** require that the entire changeset be stored in a single buffer in memory. 9778 ** Similarly, those that return a changeset or patchset do so by returning 9779 ** a pointer to a single large buffer allocated using sqlite3_malloc(). 9780 ** Normally this is convenient. However, if an application running in a 9781 ** low-memory environment is required to handle very large changesets, the 9782 ** large contiguous memory allocations required can become onerous. 9783 ** 9784 ** In order to avoid this problem, instead of a single large buffer, input 9785 ** is passed to a streaming API functions by way of a callback function that 9786 ** the sessions module invokes to incrementally request input data as it is 9787 ** required. In all cases, a pair of API function parameters such as 9788 ** 9789 ** <pre> 9790 ** int nChangeset, 9791 ** void *pChangeset, 9792 ** </pre> 9793 ** 9794 ** Is replaced by: 9795 ** 9796 ** <pre> 9797 ** int (*xInput)(void *pIn, void *pData, int *pnData), 9798 ** void *pIn, 9799 ** </pre> 9800 ** 9801 ** Each time the xInput callback is invoked by the sessions module, the first 9802 ** argument passed is a copy of the supplied pIn context pointer. The second 9803 ** argument, pData, points to a buffer (*pnData) bytes in size. Assuming no 9804 ** error occurs the xInput method should copy up to (*pnData) bytes of data 9805 ** into the buffer and set (*pnData) to the actual number of bytes copied 9806 ** before returning SQLITE_OK. If the input is completely exhausted, (*pnData) 9807 ** should be set to zero to indicate this. Or, if an error occurs, an SQLite 9808 ** error code should be returned. In all cases, if an xInput callback returns 9809 ** an error, all processing is abandoned and the streaming API function 9810 ** returns a copy of the error code to the caller. 9811 ** 9812 ** In the case of sqlite3changeset_start_strm(), the xInput callback may be 9813 ** invoked by the sessions module at any point during the lifetime of the 9814 ** iterator. If such an xInput callback returns an error, the iterator enters 9815 ** an error state, whereby all subsequent calls to iterator functions 9816 ** immediately fail with the same error code as returned by xInput. 9817 ** 9818 ** Similarly, streaming API functions that return changesets (or patchsets) 9819 ** return them in chunks by way of a callback function instead of via a 9820 ** pointer to a single large buffer. In this case, a pair of parameters such 9821 ** as: 9822 ** 9823 ** <pre> 9824 ** int *pnChangeset, 9825 ** void **ppChangeset, 9826 ** </pre> 9827 ** 9828 ** Is replaced by: 9829 ** 9830 ** <pre> 9831 ** int (*xOutput)(void *pOut, const void *pData, int nData), 9832 ** void *pOut 9833 ** </pre> 9834 ** 9835 ** The xOutput callback is invoked zero or more times to return data to 9836 ** the application. The first parameter passed to each call is a copy of the 9837 ** pOut pointer supplied by the application. The second parameter, pData, 9838 ** points to a buffer nData bytes in size containing the chunk of output 9839 ** data being returned. If the xOutput callback successfully processes the 9840 ** supplied data, it should return SQLITE_OK to indicate success. Otherwise, 9841 ** it should return some other SQLite error code. In this case processing 9842 ** is immediately abandoned and the streaming API function returns a copy 9843 ** of the xOutput error code to the application. 9844 ** 9845 ** The sessions module never invokes an xOutput callback with the third 9846 ** parameter set to a value less than or equal to zero. Other than this, 9847 ** no guarantees are made as to the size of the chunks of data returned. 9848 */ 9849 SQLITE_API int sqlite3changeset_apply_strm( 9850 sqlite3 *db, /* Apply change to "main" db of this handle */ 9851 int (*xInput)(void *pIn, void *pData, int *pnData), /* Input function */ 9852 void *pIn, /* First arg for xInput */ 9853 int(*xFilter)( 9854 void *pCtx, /* Copy of sixth arg to _apply() */ 9855 const char *zTab /* Table name */ 9856 ), 9857 int(*xConflict)( 9858 void *pCtx, /* Copy of sixth arg to _apply() */ 9859 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 9860 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 9861 ), 9862 void *pCtx /* First argument passed to xConflict */ 9863 ); 9864 SQLITE_API int sqlite3changeset_concat_strm( 9865 int (*xInputA)(void *pIn, void *pData, int *pnData), 9866 void *pInA, 9867 int (*xInputB)(void *pIn, void *pData, int *pnData), 9868 void *pInB, 9869 int (*xOutput)(void *pOut, const void *pData, int nData), 9870 void *pOut 9871 ); 9872 SQLITE_API int sqlite3changeset_invert_strm( 9873 int (*xInput)(void *pIn, void *pData, int *pnData), 9874 void *pIn, 9875 int (*xOutput)(void *pOut, const void *pData, int nData), 9876 void *pOut 9877 ); 9878 SQLITE_API int sqlite3changeset_start_strm( 9879 sqlite3_changeset_iter **pp, 9880 int (*xInput)(void *pIn, void *pData, int *pnData), 9881 void *pIn 9882 ); 9883 SQLITE_API int sqlite3session_changeset_strm( 9884 sqlite3_session *pSession, 9885 int (*xOutput)(void *pOut, const void *pData, int nData), 9886 void *pOut 9887 ); 9888 SQLITE_API int sqlite3session_patchset_strm( 9889 sqlite3_session *pSession, 9890 int (*xOutput)(void *pOut, const void *pData, int nData), 9891 void *pOut 9892 ); 9893 int sqlite3changegroup_add_strm(sqlite3_changegroup*, 9894 int (*xInput)(void *pIn, void *pData, int *pnData), 9895 void *pIn 9896 ); 9897 int sqlite3changegroup_output_strm(sqlite3_changegroup*, 9898 int (*xOutput)(void *pOut, const void *pData, int nData), 9899 void *pOut 9900 ); 9901 9902 9903 /* 9904 ** Make sure we can call this stuff from C++. 9905 */ 9906 #ifdef __cplusplus 9907 } 9908 #endif 9909 9910 #endif /* !defined(__SQLITESESSION_H_) && defined(SQLITE_ENABLE_SESSION) */ 9911 9912 /******** End of sqlite3session.h *********/ 9913 /******** Begin file fts5.h *********/ 9914 /* 9915 ** 2014 May 31 9916 ** 9917 ** The author disclaims copyright to this source code. In place of 9918 ** a legal notice, here is a blessing: 9919 ** 9920 ** May you do good and not evil. 9921 ** May you find forgiveness for yourself and forgive others. 9922 ** May you share freely, never taking more than you give. 9923 ** 9924 ****************************************************************************** 9925 ** 9926 ** Interfaces to extend FTS5. Using the interfaces defined in this file, 9927 ** FTS5 may be extended with: 9928 ** 9929 ** * custom tokenizers, and 9930 ** * custom auxiliary functions. 9931 */ 9932 9933 9934 #ifndef _FTS5_H 9935 #define _FTS5_H 9936 9937 9938 #ifdef __cplusplus 9939 extern "C" { 9940 #endif 9941 9942 /************************************************************************* 9943 ** CUSTOM AUXILIARY FUNCTIONS 9944 ** 9945 ** Virtual table implementations may overload SQL functions by implementing 9946 ** the sqlite3_module.xFindFunction() method. 9947 */ 9948 9949 typedef struct Fts5ExtensionApi Fts5ExtensionApi; 9950 typedef struct Fts5Context Fts5Context; 9951 typedef struct Fts5PhraseIter Fts5PhraseIter; 9952 9953 typedef void (*fts5_extension_function)( 9954 const Fts5ExtensionApi *pApi, /* API offered by current FTS version */ 9955 Fts5Context *pFts, /* First arg to pass to pApi functions */ 9956 sqlite3_context *pCtx, /* Context for returning result/error */ 9957 int nVal, /* Number of values in apVal[] array */ 9958 sqlite3_value **apVal /* Array of trailing arguments */ 9959 ); 9960 9961 struct Fts5PhraseIter { 9962 const unsigned char *a; 9963 const unsigned char *b; 9964 }; 9965 9966 /* 9967 ** EXTENSION API FUNCTIONS 9968 ** 9969 ** xUserData(pFts): 9970 ** Return a copy of the context pointer the extension function was 9971 ** registered with. 9972 ** 9973 ** xColumnTotalSize(pFts, iCol, pnToken): 9974 ** If parameter iCol is less than zero, set output variable *pnToken 9975 ** to the total number of tokens in the FTS5 table. Or, if iCol is 9976 ** non-negative but less than the number of columns in the table, return 9977 ** the total number of tokens in column iCol, considering all rows in 9978 ** the FTS5 table. 9979 ** 9980 ** If parameter iCol is greater than or equal to the number of columns 9981 ** in the table, SQLITE_RANGE is returned. Or, if an error occurs (e.g. 9982 ** an OOM condition or IO error), an appropriate SQLite error code is 9983 ** returned. 9984 ** 9985 ** xColumnCount(pFts): 9986 ** Return the number of columns in the table. 9987 ** 9988 ** xColumnSize(pFts, iCol, pnToken): 9989 ** If parameter iCol is less than zero, set output variable *pnToken 9990 ** to the total number of tokens in the current row. Or, if iCol is 9991 ** non-negative but less than the number of columns in the table, set 9992 ** *pnToken to the number of tokens in column iCol of the current row. 9993 ** 9994 ** If parameter iCol is greater than or equal to the number of columns 9995 ** in the table, SQLITE_RANGE is returned. Or, if an error occurs (e.g. 9996 ** an OOM condition or IO error), an appropriate SQLite error code is 9997 ** returned. 9998 ** 9999 ** This function may be quite inefficient if used with an FTS5 table 10000 ** created with the "columnsize=0" option. 10001 ** 10002 ** xColumnText: 10003 ** This function attempts to retrieve the text of column iCol of the 10004 ** current document. If successful, (*pz) is set to point to a buffer 10005 ** containing the text in utf-8 encoding, (*pn) is set to the size in bytes 10006 ** (not characters) of the buffer and SQLITE_OK is returned. Otherwise, 10007 ** if an error occurs, an SQLite error code is returned and the final values 10008 ** of (*pz) and (*pn) are undefined. 10009 ** 10010 ** xPhraseCount: 10011 ** Returns the number of phrases in the current query expression. 10012 ** 10013 ** xPhraseSize: 10014 ** Returns the number of tokens in phrase iPhrase of the query. Phrases 10015 ** are numbered starting from zero. 10016 ** 10017 ** xInstCount: 10018 ** Set *pnInst to the total number of occurrences of all phrases within 10019 ** the query within the current row. Return SQLITE_OK if successful, or 10020 ** an error code (i.e. SQLITE_NOMEM) if an error occurs. 10021 ** 10022 ** This API can be quite slow if used with an FTS5 table created with the 10023 ** "detail=none" or "detail=column" option. If the FTS5 table is created 10024 ** with either "detail=none" or "detail=column" and "content=" option 10025 ** (i.e. if it is a contentless table), then this API always returns 0. 10026 ** 10027 ** xInst: 10028 ** Query for the details of phrase match iIdx within the current row. 10029 ** Phrase matches are numbered starting from zero, so the iIdx argument 10030 ** should be greater than or equal to zero and smaller than the value 10031 ** output by xInstCount(). 10032 ** 10033 ** Usually, output parameter *piPhrase is set to the phrase number, *piCol 10034 ** to the column in which it occurs and *piOff the token offset of the 10035 ** first token of the phrase. The exception is if the table was created 10036 ** with the offsets=0 option specified. In this case *piOff is always 10037 ** set to -1. 10038 ** 10039 ** Returns SQLITE_OK if successful, or an error code (i.e. SQLITE_NOMEM) 10040 ** if an error occurs. 10041 ** 10042 ** This API can be quite slow if used with an FTS5 table created with the 10043 ** "detail=none" or "detail=column" option. 10044 ** 10045 ** xRowid: 10046 ** Returns the rowid of the current row. 10047 ** 10048 ** xTokenize: 10049 ** Tokenize text using the tokenizer belonging to the FTS5 table. 10050 ** 10051 ** xQueryPhrase(pFts5, iPhrase, pUserData, xCallback): 10052 ** This API function is used to query the FTS table for phrase iPhrase 10053 ** of the current query. Specifically, a query equivalent to: 10054 ** 10055 ** ... FROM ftstable WHERE ftstable MATCH $p ORDER BY rowid 10056 ** 10057 ** with $p set to a phrase equivalent to the phrase iPhrase of the 10058 ** current query is executed. Any column filter that applies to 10059 ** phrase iPhrase of the current query is included in $p. For each 10060 ** row visited, the callback function passed as the fourth argument 10061 ** is invoked. The context and API objects passed to the callback 10062 ** function may be used to access the properties of each matched row. 10063 ** Invoking Api.xUserData() returns a copy of the pointer passed as 10064 ** the third argument to pUserData. 10065 ** 10066 ** If the callback function returns any value other than SQLITE_OK, the 10067 ** query is abandoned and the xQueryPhrase function returns immediately. 10068 ** If the returned value is SQLITE_DONE, xQueryPhrase returns SQLITE_OK. 10069 ** Otherwise, the error code is propagated upwards. 10070 ** 10071 ** If the query runs to completion without incident, SQLITE_OK is returned. 10072 ** Or, if some error occurs before the query completes or is aborted by 10073 ** the callback, an SQLite error code is returned. 10074 ** 10075 ** 10076 ** xSetAuxdata(pFts5, pAux, xDelete) 10077 ** 10078 ** Save the pointer passed as the second argument as the extension functions 10079 ** "auxiliary data". The pointer may then be retrieved by the current or any 10080 ** future invocation of the same fts5 extension function made as part of 10081 ** of the same MATCH query using the xGetAuxdata() API. 10082 ** 10083 ** Each extension function is allocated a single auxiliary data slot for 10084 ** each FTS query (MATCH expression). If the extension function is invoked 10085 ** more than once for a single FTS query, then all invocations share a 10086 ** single auxiliary data context. 10087 ** 10088 ** If there is already an auxiliary data pointer when this function is 10089 ** invoked, then it is replaced by the new pointer. If an xDelete callback 10090 ** was specified along with the original pointer, it is invoked at this 10091 ** point. 10092 ** 10093 ** The xDelete callback, if one is specified, is also invoked on the 10094 ** auxiliary data pointer after the FTS5 query has finished. 10095 ** 10096 ** If an error (e.g. an OOM condition) occurs within this function, an 10097 ** the auxiliary data is set to NULL and an error code returned. If the 10098 ** xDelete parameter was not NULL, it is invoked on the auxiliary data 10099 ** pointer before returning. 10100 ** 10101 ** 10102 ** xGetAuxdata(pFts5, bClear) 10103 ** 10104 ** Returns the current auxiliary data pointer for the fts5 extension 10105 ** function. See the xSetAuxdata() method for details. 10106 ** 10107 ** If the bClear argument is non-zero, then the auxiliary data is cleared 10108 ** (set to NULL) before this function returns. In this case the xDelete, 10109 ** if any, is not invoked. 10110 ** 10111 ** 10112 ** xRowCount(pFts5, pnRow) 10113 ** 10114 ** This function is used to retrieve the total number of rows in the table. 10115 ** In other words, the same value that would be returned by: 10116 ** 10117 ** SELECT count(*) FROM ftstable; 10118 ** 10119 ** xPhraseFirst() 10120 ** This function is used, along with type Fts5PhraseIter and the xPhraseNext 10121 ** method, to iterate through all instances of a single query phrase within 10122 ** the current row. This is the same information as is accessible via the 10123 ** xInstCount/xInst APIs. While the xInstCount/xInst APIs are more convenient 10124 ** to use, this API may be faster under some circumstances. To iterate 10125 ** through instances of phrase iPhrase, use the following code: 10126 ** 10127 ** Fts5PhraseIter iter; 10128 ** int iCol, iOff; 10129 ** for(pApi->xPhraseFirst(pFts, iPhrase, &iter, &iCol, &iOff); 10130 ** iCol>=0; 10131 ** pApi->xPhraseNext(pFts, &iter, &iCol, &iOff) 10132 ** ){ 10133 ** // An instance of phrase iPhrase at offset iOff of column iCol 10134 ** } 10135 ** 10136 ** The Fts5PhraseIter structure is defined above. Applications should not 10137 ** modify this structure directly - it should only be used as shown above 10138 ** with the xPhraseFirst() and xPhraseNext() API methods (and by 10139 ** xPhraseFirstColumn() and xPhraseNextColumn() as illustrated below). 10140 ** 10141 ** This API can be quite slow if used with an FTS5 table created with the 10142 ** "detail=none" or "detail=column" option. If the FTS5 table is created 10143 ** with either "detail=none" or "detail=column" and "content=" option 10144 ** (i.e. if it is a contentless table), then this API always iterates 10145 ** through an empty set (all calls to xPhraseFirst() set iCol to -1). 10146 ** 10147 ** xPhraseNext() 10148 ** See xPhraseFirst above. 10149 ** 10150 ** xPhraseFirstColumn() 10151 ** This function and xPhraseNextColumn() are similar to the xPhraseFirst() 10152 ** and xPhraseNext() APIs described above. The difference is that instead 10153 ** of iterating through all instances of a phrase in the current row, these 10154 ** APIs are used to iterate through the set of columns in the current row 10155 ** that contain one or more instances of a specified phrase. For example: 10156 ** 10157 ** Fts5PhraseIter iter; 10158 ** int iCol; 10159 ** for(pApi->xPhraseFirstColumn(pFts, iPhrase, &iter, &iCol); 10160 ** iCol>=0; 10161 ** pApi->xPhraseNextColumn(pFts, &iter, &iCol) 10162 ** ){ 10163 ** // Column iCol contains at least one instance of phrase iPhrase 10164 ** } 10165 ** 10166 ** This API can be quite slow if used with an FTS5 table created with the 10167 ** "detail=none" option. If the FTS5 table is created with either 10168 ** "detail=none" "content=" option (i.e. if it is a contentless table), 10169 ** then this API always iterates through an empty set (all calls to 10170 ** xPhraseFirstColumn() set iCol to -1). 10171 ** 10172 ** The information accessed using this API and its companion 10173 ** xPhraseFirstColumn() may also be obtained using xPhraseFirst/xPhraseNext 10174 ** (or xInst/xInstCount). The chief advantage of this API is that it is 10175 ** significantly more efficient than those alternatives when used with 10176 ** "detail=column" tables. 10177 ** 10178 ** xPhraseNextColumn() 10179 ** See xPhraseFirstColumn above. 10180 */ 10181 struct Fts5ExtensionApi { 10182 int iVersion; /* Currently always set to 3 */ 10183 10184 void *(*xUserData)(Fts5Context*); 10185 10186 int (*xColumnCount)(Fts5Context*); 10187 int (*xRowCount)(Fts5Context*, sqlite3_int64 *pnRow); 10188 int (*xColumnTotalSize)(Fts5Context*, int iCol, sqlite3_int64 *pnToken); 10189 10190 int (*xTokenize)(Fts5Context*, 10191 const char *pText, int nText, /* Text to tokenize */ 10192 void *pCtx, /* Context passed to xToken() */ 10193 int (*xToken)(void*, int, const char*, int, int, int) /* Callback */ 10194 ); 10195 10196 int (*xPhraseCount)(Fts5Context*); 10197 int (*xPhraseSize)(Fts5Context*, int iPhrase); 10198 10199 int (*xInstCount)(Fts5Context*, int *pnInst); 10200 int (*xInst)(Fts5Context*, int iIdx, int *piPhrase, int *piCol, int *piOff); 10201 10202 sqlite3_int64 (*xRowid)(Fts5Context*); 10203 int (*xColumnText)(Fts5Context*, int iCol, const char **pz, int *pn); 10204 int (*xColumnSize)(Fts5Context*, int iCol, int *pnToken); 10205 10206 int (*xQueryPhrase)(Fts5Context*, int iPhrase, void *pUserData, 10207 int(*)(const Fts5ExtensionApi*,Fts5Context*,void*) 10208 ); 10209 int (*xSetAuxdata)(Fts5Context*, void *pAux, void(*xDelete)(void*)); 10210 void *(*xGetAuxdata)(Fts5Context*, int bClear); 10211 10212 int (*xPhraseFirst)(Fts5Context*, int iPhrase, Fts5PhraseIter*, int*, int*); 10213 void (*xPhraseNext)(Fts5Context*, Fts5PhraseIter*, int *piCol, int *piOff); 10214 10215 int (*xPhraseFirstColumn)(Fts5Context*, int iPhrase, Fts5PhraseIter*, int*); 10216 void (*xPhraseNextColumn)(Fts5Context*, Fts5PhraseIter*, int *piCol); 10217 }; 10218 10219 /* 10220 ** CUSTOM AUXILIARY FUNCTIONS 10221 *************************************************************************/ 10222 10223 /************************************************************************* 10224 ** CUSTOM TOKENIZERS 10225 ** 10226 ** Applications may also register custom tokenizer types. A tokenizer 10227 ** is registered by providing fts5 with a populated instance of the 10228 ** following structure. All structure methods must be defined, setting 10229 ** any member of the fts5_tokenizer struct to NULL leads to undefined 10230 ** behaviour. The structure methods are expected to function as follows: 10231 ** 10232 ** xCreate: 10233 ** This function is used to allocate and initialize a tokenizer instance. 10234 ** A tokenizer instance is required to actually tokenize text. 10235 ** 10236 ** The first argument passed to this function is a copy of the (void*) 10237 ** pointer provided by the application when the fts5_tokenizer object 10238 ** was registered with FTS5 (the third argument to xCreateTokenizer()). 10239 ** The second and third arguments are an array of nul-terminated strings 10240 ** containing the tokenizer arguments, if any, specified following the 10241 ** tokenizer name as part of the CREATE VIRTUAL TABLE statement used 10242 ** to create the FTS5 table. 10243 ** 10244 ** The final argument is an output variable. If successful, (*ppOut) 10245 ** should be set to point to the new tokenizer handle and SQLITE_OK 10246 ** returned. If an error occurs, some value other than SQLITE_OK should 10247 ** be returned. In this case, fts5 assumes that the final value of *ppOut 10248 ** is undefined. 10249 ** 10250 ** xDelete: 10251 ** This function is invoked to delete a tokenizer handle previously 10252 ** allocated using xCreate(). Fts5 guarantees that this function will 10253 ** be invoked exactly once for each successful call to xCreate(). 10254 ** 10255 ** xTokenize: 10256 ** This function is expected to tokenize the nText byte string indicated 10257 ** by argument pText. pText may or may not be nul-terminated. The first 10258 ** argument passed to this function is a pointer to an Fts5Tokenizer object 10259 ** returned by an earlier call to xCreate(). 10260 ** 10261 ** The second argument indicates the reason that FTS5 is requesting 10262 ** tokenization of the supplied text. This is always one of the following 10263 ** four values: 10264 ** 10265 ** <ul><li> <b>FTS5_TOKENIZE_DOCUMENT</b> - A document is being inserted into 10266 ** or removed from the FTS table. The tokenizer is being invoked to 10267 ** determine the set of tokens to add to (or delete from) the 10268 ** FTS index. 10269 ** 10270 ** <li> <b>FTS5_TOKENIZE_QUERY</b> - A MATCH query is being executed 10271 ** against the FTS index. The tokenizer is being called to tokenize 10272 ** a bareword or quoted string specified as part of the query. 10273 ** 10274 ** <li> <b>(FTS5_TOKENIZE_QUERY | FTS5_TOKENIZE_PREFIX)</b> - Same as 10275 ** FTS5_TOKENIZE_QUERY, except that the bareword or quoted string is 10276 ** followed by a "*" character, indicating that the last token 10277 ** returned by the tokenizer will be treated as a token prefix. 10278 ** 10279 ** <li> <b>FTS5_TOKENIZE_AUX</b> - The tokenizer is being invoked to 10280 ** satisfy an fts5_api.xTokenize() request made by an auxiliary 10281 ** function. Or an fts5_api.xColumnSize() request made by the same 10282 ** on a columnsize=0 database. 10283 ** </ul> 10284 ** 10285 ** For each token in the input string, the supplied callback xToken() must 10286 ** be invoked. The first argument to it should be a copy of the pointer 10287 ** passed as the second argument to xTokenize(). The third and fourth 10288 ** arguments are a pointer to a buffer containing the token text, and the 10289 ** size of the token in bytes. The 4th and 5th arguments are the byte offsets 10290 ** of the first byte of and first byte immediately following the text from 10291 ** which the token is derived within the input. 10292 ** 10293 ** The second argument passed to the xToken() callback ("tflags") should 10294 ** normally be set to 0. The exception is if the tokenizer supports 10295 ** synonyms. In this case see the discussion below for details. 10296 ** 10297 ** FTS5 assumes the xToken() callback is invoked for each token in the 10298 ** order that they occur within the input text. 10299 ** 10300 ** If an xToken() callback returns any value other than SQLITE_OK, then 10301 ** the tokenization should be abandoned and the xTokenize() method should 10302 ** immediately return a copy of the xToken() return value. Or, if the 10303 ** input buffer is exhausted, xTokenize() should return SQLITE_OK. Finally, 10304 ** if an error occurs with the xTokenize() implementation itself, it 10305 ** may abandon the tokenization and return any error code other than 10306 ** SQLITE_OK or SQLITE_DONE. 10307 ** 10308 ** SYNONYM SUPPORT 10309 ** 10310 ** Custom tokenizers may also support synonyms. Consider a case in which a 10311 ** user wishes to query for a phrase such as "first place". Using the 10312 ** built-in tokenizers, the FTS5 query 'first + place' will match instances 10313 ** of "first place" within the document set, but not alternative forms 10314 ** such as "1st place". In some applications, it would be better to match 10315 ** all instances of "first place" or "1st place" regardless of which form 10316 ** the user specified in the MATCH query text. 10317 ** 10318 ** There are several ways to approach this in FTS5: 10319 ** 10320 ** <ol><li> By mapping all synonyms to a single token. In this case, the 10321 ** In the above example, this means that the tokenizer returns the 10322 ** same token for inputs "first" and "1st". Say that token is in 10323 ** fact "first", so that when the user inserts the document "I won 10324 ** 1st place" entries are added to the index for tokens "i", "won", 10325 ** "first" and "place". If the user then queries for '1st + place', 10326 ** the tokenizer substitutes "first" for "1st" and the query works 10327 ** as expected. 10328 ** 10329 ** <li> By adding multiple synonyms for a single term to the FTS index. 10330 ** In this case, when tokenizing query text, the tokenizer may 10331 ** provide multiple synonyms for a single term within the document. 10332 ** FTS5 then queries the index for each synonym individually. For 10333 ** example, faced with the query: 10334 ** 10335 ** <codeblock> 10336 ** ... MATCH 'first place'</codeblock> 10337 ** 10338 ** the tokenizer offers both "1st" and "first" as synonyms for the 10339 ** first token in the MATCH query and FTS5 effectively runs a query 10340 ** similar to: 10341 ** 10342 ** <codeblock> 10343 ** ... MATCH '(first OR 1st) place'</codeblock> 10344 ** 10345 ** except that, for the purposes of auxiliary functions, the query 10346 ** still appears to contain just two phrases - "(first OR 1st)" 10347 ** being treated as a single phrase. 10348 ** 10349 ** <li> By adding multiple synonyms for a single term to the FTS index. 10350 ** Using this method, when tokenizing document text, the tokenizer 10351 ** provides multiple synonyms for each token. So that when a 10352 ** document such as "I won first place" is tokenized, entries are 10353 ** added to the FTS index for "i", "won", "first", "1st" and 10354 ** "place". 10355 ** 10356 ** This way, even if the tokenizer does not provide synonyms 10357 ** when tokenizing query text (it should not - to do would be 10358 ** inefficient), it doesn't matter if the user queries for 10359 ** 'first + place' or '1st + place', as there are entires in the 10360 ** FTS index corresponding to both forms of the first token. 10361 ** </ol> 10362 ** 10363 ** Whether it is parsing document or query text, any call to xToken that 10364 ** specifies a <i>tflags</i> argument with the FTS5_TOKEN_COLOCATED bit 10365 ** is considered to supply a synonym for the previous token. For example, 10366 ** when parsing the document "I won first place", a tokenizer that supports 10367 ** synonyms would call xToken() 5 times, as follows: 10368 ** 10369 ** <codeblock> 10370 ** xToken(pCtx, 0, "i", 1, 0, 1); 10371 ** xToken(pCtx, 0, "won", 3, 2, 5); 10372 ** xToken(pCtx, 0, "first", 5, 6, 11); 10373 ** xToken(pCtx, FTS5_TOKEN_COLOCATED, "1st", 3, 6, 11); 10374 ** xToken(pCtx, 0, "place", 5, 12, 17); 10375 **</codeblock> 10376 ** 10377 ** It is an error to specify the FTS5_TOKEN_COLOCATED flag the first time 10378 ** xToken() is called. Multiple synonyms may be specified for a single token 10379 ** by making multiple calls to xToken(FTS5_TOKEN_COLOCATED) in sequence. 10380 ** There is no limit to the number of synonyms that may be provided for a 10381 ** single token. 10382 ** 10383 ** In many cases, method (1) above is the best approach. It does not add 10384 ** extra data to the FTS index or require FTS5 to query for multiple terms, 10385 ** so it is efficient in terms of disk space and query speed. However, it 10386 ** does not support prefix queries very well. If, as suggested above, the 10387 ** token "first" is subsituted for "1st" by the tokenizer, then the query: 10388 ** 10389 ** <codeblock> 10390 ** ... MATCH '1s*'</codeblock> 10391 ** 10392 ** will not match documents that contain the token "1st" (as the tokenizer 10393 ** will probably not map "1s" to any prefix of "first"). 10394 ** 10395 ** For full prefix support, method (3) may be preferred. In this case, 10396 ** because the index contains entries for both "first" and "1st", prefix 10397 ** queries such as 'fi*' or '1s*' will match correctly. However, because 10398 ** extra entries are added to the FTS index, this method uses more space 10399 ** within the database. 10400 ** 10401 ** Method (2) offers a midpoint between (1) and (3). Using this method, 10402 ** a query such as '1s*' will match documents that contain the literal 10403 ** token "1st", but not "first" (assuming the tokenizer is not able to 10404 ** provide synonyms for prefixes). However, a non-prefix query like '1st' 10405 ** will match against "1st" and "first". This method does not require 10406 ** extra disk space, as no extra entries are added to the FTS index. 10407 ** On the other hand, it may require more CPU cycles to run MATCH queries, 10408 ** as separate queries of the FTS index are required for each synonym. 10409 ** 10410 ** When using methods (2) or (3), it is important that the tokenizer only 10411 ** provide synonyms when tokenizing document text (method (2)) or query 10412 ** text (method (3)), not both. Doing so will not cause any errors, but is 10413 ** inefficient. 10414 */ 10415 typedef struct Fts5Tokenizer Fts5Tokenizer; 10416 typedef struct fts5_tokenizer fts5_tokenizer; 10417 struct fts5_tokenizer { 10418 int (*xCreate)(void*, const char **azArg, int nArg, Fts5Tokenizer **ppOut); 10419 void (*xDelete)(Fts5Tokenizer*); 10420 int (*xTokenize)(Fts5Tokenizer*, 10421 void *pCtx, 10422 int flags, /* Mask of FTS5_TOKENIZE_* flags */ 10423 const char *pText, int nText, 10424 int (*xToken)( 10425 void *pCtx, /* Copy of 2nd argument to xTokenize() */ 10426 int tflags, /* Mask of FTS5_TOKEN_* flags */ 10427 const char *pToken, /* Pointer to buffer containing token */ 10428 int nToken, /* Size of token in bytes */ 10429 int iStart, /* Byte offset of token within input text */ 10430 int iEnd /* Byte offset of end of token within input text */ 10431 ) 10432 ); 10433 }; 10434 10435 /* Flags that may be passed as the third argument to xTokenize() */ 10436 #define FTS5_TOKENIZE_QUERY 0x0001 10437 #define FTS5_TOKENIZE_PREFIX 0x0002 10438 #define FTS5_TOKENIZE_DOCUMENT 0x0004 10439 #define FTS5_TOKENIZE_AUX 0x0008 10440 10441 /* Flags that may be passed by the tokenizer implementation back to FTS5 10442 ** as the third argument to the supplied xToken callback. */ 10443 #define FTS5_TOKEN_COLOCATED 0x0001 /* Same position as prev. token */ 10444 10445 /* 10446 ** END OF CUSTOM TOKENIZERS 10447 *************************************************************************/ 10448 10449 /************************************************************************* 10450 ** FTS5 EXTENSION REGISTRATION API 10451 */ 10452 typedef struct fts5_api fts5_api; 10453 struct fts5_api { 10454 int iVersion; /* Currently always set to 2 */ 10455 10456 /* Create a new tokenizer */ 10457 int (*xCreateTokenizer)( 10458 fts5_api *pApi, 10459 const char *zName, 10460 void *pContext, 10461 fts5_tokenizer *pTokenizer, 10462 void (*xDestroy)(void*) 10463 ); 10464 10465 /* Find an existing tokenizer */ 10466 int (*xFindTokenizer)( 10467 fts5_api *pApi, 10468 const char *zName, 10469 void **ppContext, 10470 fts5_tokenizer *pTokenizer 10471 ); 10472 10473 /* Create a new auxiliary function */ 10474 int (*xCreateFunction)( 10475 fts5_api *pApi, 10476 const char *zName, 10477 void *pContext, 10478 fts5_extension_function xFunction, 10479 void (*xDestroy)(void*) 10480 ); 10481 }; 10482 10483 /* 10484 ** END OF REGISTRATION API 10485 *************************************************************************/ 10486 10487 #ifdef __cplusplus 10488 } /* end of the 'extern "C"' block */ 10489 #endif 10490 10491 #endif /* _FTS5_H */ 10492 10493 /******** End of fts5.h *********/ 10494