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 41extern "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_STDCALL 58# define SQLITE_STDCALL 59#endif 60 61/* 62** These no-op macros are used in front of interfaces to mark those 63** interfaces as either deprecated or experimental. New applications 64** should not use deprecated interfaces - they are supported for backwards 65** compatibility only. Application writers should be aware that 66** experimental interfaces are subject to change in point releases. 67** 68** These macros used to resolve to various kinds of compiler magic that 69** would generate warning messages when they were used. But that 70** compiler magic ended up generating such a flurry of bug reports 71** that we have taken it all out and gone back to using simple 72** noop macros. 73*/ 74#define SQLITE_DEPRECATED 75#define SQLITE_EXPERIMENTAL 76 77/* 78** Ensure these symbols were not defined by some previous header file. 79*/ 80#ifdef SQLITE_VERSION 81# undef SQLITE_VERSION 82#endif 83#ifdef SQLITE_VERSION_NUMBER 84# undef SQLITE_VERSION_NUMBER 85#endif 86 87/* 88** CAPI3REF: Compile-Time Library Version Numbers 89** 90** ^(The [SQLITE_VERSION] C preprocessor macro in the sqlite3.h header 91** evaluates to a string literal that is the SQLite version in the 92** format "X.Y.Z" where X is the major version number (always 3 for 93** SQLite3) and Y is the minor version number and Z is the release number.)^ 94** ^(The [SQLITE_VERSION_NUMBER] C preprocessor macro resolves to an integer 95** with the value (X*1000000 + Y*1000 + Z) where X, Y, and Z are the same 96** numbers used in [SQLITE_VERSION].)^ 97** The SQLITE_VERSION_NUMBER for any given release of SQLite will also 98** be larger than the release from which it is derived. Either Y will 99** be held constant and Z will be incremented or else Y will be incremented 100** and Z will be reset to zero. 101** 102** Since version 3.6.18, SQLite source code has been stored in the 103** <a href="http://www.fossil-scm.org/">Fossil configuration management 104** system</a>. ^The SQLITE_SOURCE_ID macro evaluates to 105** a string which identifies a particular check-in of SQLite 106** within its configuration management system. ^The SQLITE_SOURCE_ID 107** string contains the date and time of the check-in (UTC) and an SHA1 108** hash of the entire source tree. 109** 110** See also: [sqlite3_libversion()], 111** [sqlite3_libversion_number()], [sqlite3_sourceid()], 112** [sqlite_version()] and [sqlite_source_id()]. 113*/ 114#define SQLITE_VERSION "--VERS--" 115#define SQLITE_VERSION_NUMBER --VERSION-NUMBER-- 116#define SQLITE_SOURCE_ID "--SOURCE-ID--" 117 118/* 119** CAPI3REF: Run-Time Library Version Numbers 120** KEYWORDS: sqlite3_version, sqlite3_sourceid 121** 122** These interfaces provide the same information as the [SQLITE_VERSION], 123** [SQLITE_VERSION_NUMBER], and [SQLITE_SOURCE_ID] C preprocessor macros 124** but are associated with the library instead of the header file. ^(Cautious 125** programmers might include assert() statements in their application to 126** verify that values returned by these interfaces match the macros in 127** the header, and thus insure that the application is 128** compiled with matching library and header files. 129** 130** <blockquote><pre> 131** assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER ); 132** assert( strcmp(sqlite3_sourceid(),SQLITE_SOURCE_ID)==0 ); 133** assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0 ); 134** </pre></blockquote>)^ 135** 136** ^The sqlite3_version[] string constant contains the text of [SQLITE_VERSION] 137** macro. ^The sqlite3_libversion() function returns a pointer to the 138** to the sqlite3_version[] string constant. The sqlite3_libversion() 139** function is provided for use in DLLs since DLL users usually do not have 140** direct access to string constants within the DLL. ^The 141** sqlite3_libversion_number() function returns an integer equal to 142** [SQLITE_VERSION_NUMBER]. ^The sqlite3_sourceid() function returns 143** a pointer to a string constant whose value is the same as the 144** [SQLITE_SOURCE_ID] C preprocessor macro. 145** 146** See also: [sqlite_version()] and [sqlite_source_id()]. 147*/ 148SQLITE_EXTERN const char sqlite3_version[]; 149const char *sqlite3_libversion(void); 150const char *sqlite3_sourceid(void); 151int sqlite3_libversion_number(void); 152 153/* 154** CAPI3REF: Run-Time Library Compilation Options Diagnostics 155** 156** ^The sqlite3_compileoption_used() function returns 0 or 1 157** indicating whether the specified option was defined at 158** compile time. ^The SQLITE_ prefix may be omitted from the 159** option name passed to sqlite3_compileoption_used(). 160** 161** ^The sqlite3_compileoption_get() function allows iterating 162** over the list of options that were defined at compile time by 163** returning the N-th compile time option string. ^If N is out of range, 164** sqlite3_compileoption_get() returns a NULL pointer. ^The SQLITE_ 165** prefix is omitted from any strings returned by 166** sqlite3_compileoption_get(). 167** 168** ^Support for the diagnostic functions sqlite3_compileoption_used() 169** and sqlite3_compileoption_get() may be omitted by specifying the 170** [SQLITE_OMIT_COMPILEOPTION_DIAGS] option at compile time. 171** 172** See also: SQL functions [sqlite_compileoption_used()] and 173** [sqlite_compileoption_get()] and the [compile_options pragma]. 174*/ 175#ifndef SQLITE_OMIT_COMPILEOPTION_DIAGS 176int sqlite3_compileoption_used(const char *zOptName); 177const char *sqlite3_compileoption_get(int N); 178#endif 179 180/* 181** CAPI3REF: Test To See If The Library Is Threadsafe 182** 183** ^The sqlite3_threadsafe() function returns zero if and only if 184** SQLite was compiled with mutexing code omitted due to the 185** [SQLITE_THREADSAFE] compile-time option being set to 0. 186** 187** SQLite can be compiled with or without mutexes. When 188** the [SQLITE_THREADSAFE] C preprocessor macro is 1 or 2, mutexes 189** are enabled and SQLite is threadsafe. When the 190** [SQLITE_THREADSAFE] macro is 0, 191** the mutexes are omitted. Without the mutexes, it is not safe 192** to use SQLite concurrently from more than one thread. 193** 194** Enabling mutexes incurs a measurable performance penalty. 195** So if speed is of utmost importance, it makes sense to disable 196** the mutexes. But for maximum safety, mutexes should be enabled. 197** ^The default behavior is for mutexes to be enabled. 198** 199** This interface can be used by an application to make sure that the 200** version of SQLite that it is linking against was compiled with 201** the desired setting of the [SQLITE_THREADSAFE] macro. 202** 203** This interface only reports on the compile-time mutex setting 204** of the [SQLITE_THREADSAFE] flag. If SQLite is compiled with 205** SQLITE_THREADSAFE=1 or =2 then mutexes are enabled by default but 206** can be fully or partially disabled using a call to [sqlite3_config()] 207** with the verbs [SQLITE_CONFIG_SINGLETHREAD], [SQLITE_CONFIG_MULTITHREAD], 208** or [SQLITE_CONFIG_SERIALIZED]. ^(The return value of the 209** sqlite3_threadsafe() function shows only the compile-time setting of 210** thread safety, not any run-time changes to that setting made by 211** sqlite3_config(). In other words, the return value from sqlite3_threadsafe() 212** is unchanged by calls to sqlite3_config().)^ 213** 214** See the [threading mode] documentation for additional information. 215*/ 216int sqlite3_threadsafe(void); 217 218/* 219** CAPI3REF: Database Connection Handle 220** KEYWORDS: {database connection} {database connections} 221** 222** Each open SQLite database is represented by a pointer to an instance of 223** the opaque structure named "sqlite3". It is useful to think of an sqlite3 224** pointer as an object. The [sqlite3_open()], [sqlite3_open16()], and 225** [sqlite3_open_v2()] interfaces are its constructors, and [sqlite3_close()] 226** and [sqlite3_close_v2()] are its destructors. There are many other 227** interfaces (such as 228** [sqlite3_prepare_v2()], [sqlite3_create_function()], and 229** [sqlite3_busy_timeout()] to name but three) that are methods on an 230** sqlite3 object. 231*/ 232typedef struct sqlite3 sqlite3; 233 234/* 235** CAPI3REF: 64-Bit Integer Types 236** KEYWORDS: sqlite_int64 sqlite_uint64 237** 238** Because there is no cross-platform way to specify 64-bit integer types 239** SQLite includes typedefs for 64-bit signed and unsigned integers. 240** 241** The sqlite3_int64 and sqlite3_uint64 are the preferred type definitions. 242** The sqlite_int64 and sqlite_uint64 types are supported for backwards 243** compatibility only. 244** 245** ^The sqlite3_int64 and sqlite_int64 types can store integer values 246** between -9223372036854775808 and +9223372036854775807 inclusive. ^The 247** sqlite3_uint64 and sqlite_uint64 types can store integer values 248** between 0 and +18446744073709551615 inclusive. 249*/ 250#ifdef SQLITE_INT64_TYPE 251 typedef SQLITE_INT64_TYPE sqlite_int64; 252 typedef unsigned SQLITE_INT64_TYPE sqlite_uint64; 253#elif defined(_MSC_VER) || defined(__BORLANDC__) 254 typedef __int64 sqlite_int64; 255 typedef unsigned __int64 sqlite_uint64; 256#else 257 typedef long long int sqlite_int64; 258 typedef unsigned long long int sqlite_uint64; 259#endif 260typedef sqlite_int64 sqlite3_int64; 261typedef sqlite_uint64 sqlite3_uint64; 262 263/* 264** If compiling for a processor that lacks floating point support, 265** substitute integer for floating-point. 266*/ 267#ifdef SQLITE_OMIT_FLOATING_POINT 268# define double sqlite3_int64 269#endif 270 271/* 272** CAPI3REF: Closing A Database Connection 273** DESTRUCTOR: sqlite3 274** 275** ^The sqlite3_close() and sqlite3_close_v2() routines are destructors 276** for the [sqlite3] object. 277** ^Calls to sqlite3_close() and sqlite3_close_v2() return [SQLITE_OK] if 278** the [sqlite3] object is successfully destroyed and all associated 279** resources are deallocated. 280** 281** ^If the database connection is associated with unfinalized prepared 282** statements or unfinished sqlite3_backup objects then sqlite3_close() 283** will leave the database connection open and return [SQLITE_BUSY]. 284** ^If sqlite3_close_v2() is called with unfinalized prepared statements 285** and/or unfinished sqlite3_backups, then the database connection becomes 286** an unusable "zombie" which will automatically be deallocated when the 287** last prepared statement is finalized or the last sqlite3_backup is 288** finished. The sqlite3_close_v2() interface is intended for use with 289** host languages that are garbage collected, and where the order in which 290** destructors are called is arbitrary. 291** 292** Applications should [sqlite3_finalize | finalize] all [prepared statements], 293** [sqlite3_blob_close | close] all [BLOB handles], and 294** [sqlite3_backup_finish | finish] all [sqlite3_backup] objects associated 295** with the [sqlite3] object prior to attempting to close the object. ^If 296** sqlite3_close_v2() is called on a [database connection] that still has 297** outstanding [prepared statements], [BLOB handles], and/or 298** [sqlite3_backup] objects then it returns [SQLITE_OK] and the deallocation 299** of resources is deferred until all [prepared statements], [BLOB handles], 300** and [sqlite3_backup] objects are also destroyed. 301** 302** ^If an [sqlite3] object is destroyed while a transaction is open, 303** the transaction is automatically rolled back. 304** 305** The C parameter to [sqlite3_close(C)] and [sqlite3_close_v2(C)] 306** must be either a NULL 307** pointer or an [sqlite3] object pointer obtained 308** from [sqlite3_open()], [sqlite3_open16()], or 309** [sqlite3_open_v2()], and not previously closed. 310** ^Calling sqlite3_close() or sqlite3_close_v2() with a NULL pointer 311** argument is a harmless no-op. 312*/ 313int sqlite3_close(sqlite3*); 314int sqlite3_close_v2(sqlite3*); 315 316/* 317** The type for a callback function. 318** This is legacy and deprecated. It is included for historical 319** compatibility and is not documented. 320*/ 321typedef int (*sqlite3_callback)(void*,int,char**, char**); 322 323/* 324** CAPI3REF: One-Step Query Execution Interface 325** METHOD: sqlite3 326** 327** The sqlite3_exec() interface is a convenience wrapper around 328** [sqlite3_prepare_v2()], [sqlite3_step()], and [sqlite3_finalize()], 329** that allows an application to run multiple statements of SQL 330** without having to use a lot of C code. 331** 332** ^The sqlite3_exec() interface runs zero or more UTF-8 encoded, 333** semicolon-separate SQL statements passed into its 2nd argument, 334** in the context of the [database connection] passed in as its 1st 335** argument. ^If the callback function of the 3rd argument to 336** sqlite3_exec() is not NULL, then it is invoked for each result row 337** coming out of the evaluated SQL statements. ^The 4th argument to 338** sqlite3_exec() is relayed through to the 1st argument of each 339** callback invocation. ^If the callback pointer to sqlite3_exec() 340** is NULL, then no callback is ever invoked and result rows are 341** ignored. 342** 343** ^If an error occurs while evaluating the SQL statements passed into 344** sqlite3_exec(), then execution of the current statement stops and 345** subsequent statements are skipped. ^If the 5th parameter to sqlite3_exec() 346** is not NULL then any error message is written into memory obtained 347** from [sqlite3_malloc()] and passed back through the 5th parameter. 348** To avoid memory leaks, the application should invoke [sqlite3_free()] 349** on error message strings returned through the 5th parameter of 350** of sqlite3_exec() after the error message string is no longer needed. 351** ^If the 5th parameter to sqlite3_exec() is not NULL and no errors 352** occur, then sqlite3_exec() sets the pointer in its 5th parameter to 353** NULL before returning. 354** 355** ^If an sqlite3_exec() callback returns non-zero, the sqlite3_exec() 356** routine returns SQLITE_ABORT without invoking the callback again and 357** without running any subsequent SQL statements. 358** 359** ^The 2nd argument to the sqlite3_exec() callback function is the 360** number of columns in the result. ^The 3rd argument to the sqlite3_exec() 361** callback is an array of pointers to strings obtained as if from 362** [sqlite3_column_text()], one for each column. ^If an element of a 363** result row is NULL then the corresponding string pointer for the 364** sqlite3_exec() callback is a NULL pointer. ^The 4th argument to the 365** sqlite3_exec() callback is an array of pointers to strings where each 366** entry represents the name of corresponding result column as obtained 367** from [sqlite3_column_name()]. 368** 369** ^If the 2nd parameter to sqlite3_exec() is a NULL pointer, a pointer 370** to an empty string, or a pointer that contains only whitespace and/or 371** SQL comments, then no SQL statements are evaluated and the database 372** is not changed. 373** 374** Restrictions: 375** 376** <ul> 377** <li> The application must insure that the 1st parameter to sqlite3_exec() 378** is a valid and open [database connection]. 379** <li> The application must not close the [database connection] specified by 380** the 1st parameter to sqlite3_exec() while sqlite3_exec() is running. 381** <li> The application must not modify the SQL statement text passed into 382** the 2nd parameter of sqlite3_exec() while sqlite3_exec() is running. 383** </ul> 384*/ 385int sqlite3_exec( 386 sqlite3*, /* An open database */ 387 const char *sql, /* SQL to be evaluated */ 388 int (*callback)(void*,int,char**,char**), /* Callback function */ 389 void *, /* 1st argument to callback */ 390 char **errmsg /* Error msg written here */ 391); 392 393/* 394** CAPI3REF: Result Codes 395** KEYWORDS: {result code definitions} 396** 397** Many SQLite functions return an integer result code from the set shown 398** here in order to indicate success or failure. 399** 400** New error codes may be added in future versions of SQLite. 401** 402** See also: [extended result code definitions] 403*/ 404#define SQLITE_OK 0 /* Successful result */ 405/* beginning-of-error-codes */ 406#define SQLITE_ERROR 1 /* SQL error or missing database */ 407#define SQLITE_INTERNAL 2 /* Internal logic error in SQLite */ 408#define SQLITE_PERM 3 /* Access permission denied */ 409#define SQLITE_ABORT 4 /* Callback routine requested an abort */ 410#define SQLITE_BUSY 5 /* The database file is locked */ 411#define SQLITE_LOCKED 6 /* A table in the database is locked */ 412#define SQLITE_NOMEM 7 /* A malloc() failed */ 413#define SQLITE_READONLY 8 /* Attempt to write a readonly database */ 414#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/ 415#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */ 416#define SQLITE_CORRUPT 11 /* The database disk image is malformed */ 417#define SQLITE_NOTFOUND 12 /* Unknown opcode in sqlite3_file_control() */ 418#define SQLITE_FULL 13 /* Insertion failed because database is full */ 419#define SQLITE_CANTOPEN 14 /* Unable to open the database file */ 420#define SQLITE_PROTOCOL 15 /* Database lock protocol error */ 421#define SQLITE_EMPTY 16 /* Database is empty */ 422#define SQLITE_SCHEMA 17 /* The database schema changed */ 423#define SQLITE_TOOBIG 18 /* String or BLOB exceeds size limit */ 424#define SQLITE_CONSTRAINT 19 /* Abort due to constraint violation */ 425#define SQLITE_MISMATCH 20 /* Data type mismatch */ 426#define SQLITE_MISUSE 21 /* Library used incorrectly */ 427#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */ 428#define SQLITE_AUTH 23 /* Authorization denied */ 429#define SQLITE_FORMAT 24 /* Auxiliary database format error */ 430#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */ 431#define SQLITE_NOTADB 26 /* File opened that is not a database file */ 432#define SQLITE_NOTICE 27 /* Notifications from sqlite3_log() */ 433#define SQLITE_WARNING 28 /* Warnings from sqlite3_log() */ 434#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */ 435#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */ 436/* end-of-error-codes */ 437 438/* 439** CAPI3REF: Extended Result Codes 440** KEYWORDS: {extended result code definitions} 441** 442** In its default configuration, SQLite API routines return one of 30 integer 443** [result codes]. However, experience has shown that many of 444** these result codes are too coarse-grained. They do not provide as 445** much information about problems as programmers might like. In an effort to 446** address this, newer versions of SQLite (version 3.3.8 and later) include 447** support for additional result codes that provide more detailed information 448** about errors. These [extended result codes] are enabled or disabled 449** on a per database connection basis using the 450** [sqlite3_extended_result_codes()] API. Or, the extended code for 451** the most recent error can be obtained using 452** [sqlite3_extended_errcode()]. 453*/ 454#define SQLITE_IOERR_READ (SQLITE_IOERR | (1<<8)) 455#define SQLITE_IOERR_SHORT_READ (SQLITE_IOERR | (2<<8)) 456#define SQLITE_IOERR_WRITE (SQLITE_IOERR | (3<<8)) 457#define SQLITE_IOERR_FSYNC (SQLITE_IOERR | (4<<8)) 458#define SQLITE_IOERR_DIR_FSYNC (SQLITE_IOERR | (5<<8)) 459#define SQLITE_IOERR_TRUNCATE (SQLITE_IOERR | (6<<8)) 460#define SQLITE_IOERR_FSTAT (SQLITE_IOERR | (7<<8)) 461#define SQLITE_IOERR_UNLOCK (SQLITE_IOERR | (8<<8)) 462#define SQLITE_IOERR_RDLOCK (SQLITE_IOERR | (9<<8)) 463#define SQLITE_IOERR_DELETE (SQLITE_IOERR | (10<<8)) 464#define SQLITE_IOERR_BLOCKED (SQLITE_IOERR | (11<<8)) 465#define SQLITE_IOERR_NOMEM (SQLITE_IOERR | (12<<8)) 466#define SQLITE_IOERR_ACCESS (SQLITE_IOERR | (13<<8)) 467#define SQLITE_IOERR_CHECKRESERVEDLOCK (SQLITE_IOERR | (14<<8)) 468#define SQLITE_IOERR_LOCK (SQLITE_IOERR | (15<<8)) 469#define SQLITE_IOERR_CLOSE (SQLITE_IOERR | (16<<8)) 470#define SQLITE_IOERR_DIR_CLOSE (SQLITE_IOERR | (17<<8)) 471#define SQLITE_IOERR_SHMOPEN (SQLITE_IOERR | (18<<8)) 472#define SQLITE_IOERR_SHMSIZE (SQLITE_IOERR | (19<<8)) 473#define SQLITE_IOERR_SHMLOCK (SQLITE_IOERR | (20<<8)) 474#define SQLITE_IOERR_SHMMAP (SQLITE_IOERR | (21<<8)) 475#define SQLITE_IOERR_SEEK (SQLITE_IOERR | (22<<8)) 476#define SQLITE_IOERR_DELETE_NOENT (SQLITE_IOERR | (23<<8)) 477#define SQLITE_IOERR_MMAP (SQLITE_IOERR | (24<<8)) 478#define SQLITE_IOERR_GETTEMPPATH (SQLITE_IOERR | (25<<8)) 479#define SQLITE_IOERR_CONVPATH (SQLITE_IOERR | (26<<8)) 480#define SQLITE_LOCKED_SHAREDCACHE (SQLITE_LOCKED | (1<<8)) 481#define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8)) 482#define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY | (2<<8)) 483#define SQLITE_CANTOPEN_NOTEMPDIR (SQLITE_CANTOPEN | (1<<8)) 484#define SQLITE_CANTOPEN_ISDIR (SQLITE_CANTOPEN | (2<<8)) 485#define SQLITE_CANTOPEN_FULLPATH (SQLITE_CANTOPEN | (3<<8)) 486#define SQLITE_CANTOPEN_CONVPATH (SQLITE_CANTOPEN | (4<<8)) 487#define SQLITE_CORRUPT_VTAB (SQLITE_CORRUPT | (1<<8)) 488#define SQLITE_READONLY_RECOVERY (SQLITE_READONLY | (1<<8)) 489#define SQLITE_READONLY_CANTLOCK (SQLITE_READONLY | (2<<8)) 490#define SQLITE_READONLY_ROLLBACK (SQLITE_READONLY | (3<<8)) 491#define SQLITE_READONLY_DBMOVED (SQLITE_READONLY | (4<<8)) 492#define SQLITE_ABORT_ROLLBACK (SQLITE_ABORT | (2<<8)) 493#define SQLITE_CONSTRAINT_CHECK (SQLITE_CONSTRAINT | (1<<8)) 494#define SQLITE_CONSTRAINT_COMMITHOOK (SQLITE_CONSTRAINT | (2<<8)) 495#define SQLITE_CONSTRAINT_FOREIGNKEY (SQLITE_CONSTRAINT | (3<<8)) 496#define SQLITE_CONSTRAINT_FUNCTION (SQLITE_CONSTRAINT | (4<<8)) 497#define SQLITE_CONSTRAINT_NOTNULL (SQLITE_CONSTRAINT | (5<<8)) 498#define SQLITE_CONSTRAINT_PRIMARYKEY (SQLITE_CONSTRAINT | (6<<8)) 499#define SQLITE_CONSTRAINT_TRIGGER (SQLITE_CONSTRAINT | (7<<8)) 500#define SQLITE_CONSTRAINT_UNIQUE (SQLITE_CONSTRAINT | (8<<8)) 501#define SQLITE_CONSTRAINT_VTAB (SQLITE_CONSTRAINT | (9<<8)) 502#define SQLITE_CONSTRAINT_ROWID (SQLITE_CONSTRAINT |(10<<8)) 503#define SQLITE_NOTICE_RECOVER_WAL (SQLITE_NOTICE | (1<<8)) 504#define SQLITE_NOTICE_RECOVER_ROLLBACK (SQLITE_NOTICE | (2<<8)) 505#define SQLITE_WARNING_AUTOINDEX (SQLITE_WARNING | (1<<8)) 506#define SQLITE_AUTH_USER (SQLITE_AUTH | (1<<8)) 507 508/* 509** CAPI3REF: Flags For File Open Operations 510** 511** These bit values are intended for use in the 512** 3rd parameter to the [sqlite3_open_v2()] interface and 513** in the 4th parameter to the [sqlite3_vfs.xOpen] method. 514*/ 515#define SQLITE_OPEN_READONLY 0x00000001 /* Ok for sqlite3_open_v2() */ 516#define SQLITE_OPEN_READWRITE 0x00000002 /* Ok for sqlite3_open_v2() */ 517#define SQLITE_OPEN_CREATE 0x00000004 /* Ok for sqlite3_open_v2() */ 518#define SQLITE_OPEN_DELETEONCLOSE 0x00000008 /* VFS only */ 519#define SQLITE_OPEN_EXCLUSIVE 0x00000010 /* VFS only */ 520#define SQLITE_OPEN_AUTOPROXY 0x00000020 /* VFS only */ 521#define SQLITE_OPEN_URI 0x00000040 /* Ok for sqlite3_open_v2() */ 522#define SQLITE_OPEN_MEMORY 0x00000080 /* Ok for sqlite3_open_v2() */ 523#define SQLITE_OPEN_MAIN_DB 0x00000100 /* VFS only */ 524#define SQLITE_OPEN_TEMP_DB 0x00000200 /* VFS only */ 525#define SQLITE_OPEN_TRANSIENT_DB 0x00000400 /* VFS only */ 526#define SQLITE_OPEN_MAIN_JOURNAL 0x00000800 /* VFS only */ 527#define SQLITE_OPEN_TEMP_JOURNAL 0x00001000 /* VFS only */ 528#define SQLITE_OPEN_SUBJOURNAL 0x00002000 /* VFS only */ 529#define SQLITE_OPEN_MASTER_JOURNAL 0x00004000 /* VFS only */ 530#define SQLITE_OPEN_NOMUTEX 0x00008000 /* Ok for sqlite3_open_v2() */ 531#define SQLITE_OPEN_FULLMUTEX 0x00010000 /* Ok for sqlite3_open_v2() */ 532#define SQLITE_OPEN_SHAREDCACHE 0x00020000 /* Ok for sqlite3_open_v2() */ 533#define SQLITE_OPEN_PRIVATECACHE 0x00040000 /* Ok for sqlite3_open_v2() */ 534#define SQLITE_OPEN_WAL 0x00080000 /* VFS only */ 535 536/* Reserved: 0x00F00000 */ 537 538/* 539** CAPI3REF: Device Characteristics 540** 541** The xDeviceCharacteristics method of the [sqlite3_io_methods] 542** object returns an integer which is a vector of these 543** bit values expressing I/O characteristics of the mass storage 544** device that holds the file that the [sqlite3_io_methods] 545** refers to. 546** 547** The SQLITE_IOCAP_ATOMIC property means that all writes of 548** any size are atomic. The SQLITE_IOCAP_ATOMICnnn values 549** mean that writes of blocks that are nnn bytes in size and 550** are aligned to an address which is an integer multiple of 551** nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means 552** that when data is appended to a file, the data is appended 553** first then the size of the file is extended, never the other 554** way around. The SQLITE_IOCAP_SEQUENTIAL property means that 555** information is written to disk in the same order as calls 556** to xWrite(). The SQLITE_IOCAP_POWERSAFE_OVERWRITE property means that 557** after reboot following a crash or power loss, the only bytes in a 558** file that were written at the application level might have changed 559** and that adjacent bytes, even bytes within the same sector are 560** guaranteed to be unchanged. The SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN 561** flag indicate that a file cannot be deleted when open. The 562** SQLITE_IOCAP_IMMUTABLE flag indicates that the file is on 563** read-only media and cannot be changed even by processes with 564** elevated privileges. 565*/ 566#define SQLITE_IOCAP_ATOMIC 0x00000001 567#define SQLITE_IOCAP_ATOMIC512 0x00000002 568#define SQLITE_IOCAP_ATOMIC1K 0x00000004 569#define SQLITE_IOCAP_ATOMIC2K 0x00000008 570#define SQLITE_IOCAP_ATOMIC4K 0x00000010 571#define SQLITE_IOCAP_ATOMIC8K 0x00000020 572#define SQLITE_IOCAP_ATOMIC16K 0x00000040 573#define SQLITE_IOCAP_ATOMIC32K 0x00000080 574#define SQLITE_IOCAP_ATOMIC64K 0x00000100 575#define SQLITE_IOCAP_SAFE_APPEND 0x00000200 576#define SQLITE_IOCAP_SEQUENTIAL 0x00000400 577#define SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN 0x00000800 578#define SQLITE_IOCAP_POWERSAFE_OVERWRITE 0x00001000 579#define SQLITE_IOCAP_IMMUTABLE 0x00002000 580 581/* 582** CAPI3REF: File Locking Levels 583** 584** SQLite uses one of these integer values as the second 585** argument to calls it makes to the xLock() and xUnlock() methods 586** of an [sqlite3_io_methods] object. 587*/ 588#define SQLITE_LOCK_NONE 0 589#define SQLITE_LOCK_SHARED 1 590#define SQLITE_LOCK_RESERVED 2 591#define SQLITE_LOCK_PENDING 3 592#define SQLITE_LOCK_EXCLUSIVE 4 593 594/* 595** CAPI3REF: Synchronization Type Flags 596** 597** When SQLite invokes the xSync() method of an 598** [sqlite3_io_methods] object it uses a combination of 599** these integer values as the second argument. 600** 601** When the SQLITE_SYNC_DATAONLY flag is used, it means that the 602** sync operation only needs to flush data to mass storage. Inode 603** information need not be flushed. If the lower four bits of the flag 604** equal SQLITE_SYNC_NORMAL, that means to use normal fsync() semantics. 605** If the lower four bits equal SQLITE_SYNC_FULL, that means 606** to use Mac OS X style fullsync instead of fsync(). 607** 608** Do not confuse the SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags 609** with the [PRAGMA synchronous]=NORMAL and [PRAGMA synchronous]=FULL 610** settings. The [synchronous pragma] determines when calls to the 611** xSync VFS method occur and applies uniformly across all platforms. 612** The SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags determine how 613** energetic or rigorous or forceful the sync operations are and 614** only make a difference on Mac OSX for the default SQLite code. 615** (Third-party VFS implementations might also make the distinction 616** between SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL, but among the 617** operating systems natively supported by SQLite, only Mac OSX 618** cares about the difference.) 619*/ 620#define SQLITE_SYNC_NORMAL 0x00002 621#define SQLITE_SYNC_FULL 0x00003 622#define SQLITE_SYNC_DATAONLY 0x00010 623 624/* 625** CAPI3REF: OS Interface Open File Handle 626** 627** An [sqlite3_file] object represents an open file in the 628** [sqlite3_vfs | OS interface layer]. Individual OS interface 629** implementations will 630** want to subclass this object by appending additional fields 631** for their own use. The pMethods entry is a pointer to an 632** [sqlite3_io_methods] object that defines methods for performing 633** I/O operations on the open file. 634*/ 635typedef struct sqlite3_file sqlite3_file; 636struct sqlite3_file { 637 const struct sqlite3_io_methods *pMethods; /* Methods for an open file */ 638}; 639 640/* 641** CAPI3REF: OS Interface File Virtual Methods Object 642** 643** Every file opened by the [sqlite3_vfs.xOpen] method populates an 644** [sqlite3_file] object (or, more commonly, a subclass of the 645** [sqlite3_file] object) with a pointer to an instance of this object. 646** This object defines the methods used to perform various operations 647** against the open file represented by the [sqlite3_file] object. 648** 649** If the [sqlite3_vfs.xOpen] method sets the sqlite3_file.pMethods element 650** to a non-NULL pointer, then the sqlite3_io_methods.xClose method 651** may be invoked even if the [sqlite3_vfs.xOpen] reported that it failed. The 652** only way to prevent a call to xClose following a failed [sqlite3_vfs.xOpen] 653** is for the [sqlite3_vfs.xOpen] to set the sqlite3_file.pMethods element 654** to NULL. 655** 656** The flags argument to xSync may be one of [SQLITE_SYNC_NORMAL] or 657** [SQLITE_SYNC_FULL]. The first choice is the normal fsync(). 658** The second choice is a Mac OS X style fullsync. The [SQLITE_SYNC_DATAONLY] 659** flag may be ORed in to indicate that only the data of the file 660** and not its inode needs to be synced. 661** 662** The integer values to xLock() and xUnlock() are one of 663** <ul> 664** <li> [SQLITE_LOCK_NONE], 665** <li> [SQLITE_LOCK_SHARED], 666** <li> [SQLITE_LOCK_RESERVED], 667** <li> [SQLITE_LOCK_PENDING], or 668** <li> [SQLITE_LOCK_EXCLUSIVE]. 669** </ul> 670** xLock() increases the lock. xUnlock() decreases the lock. 671** The xCheckReservedLock() method checks whether any database connection, 672** either in this process or in some other process, is holding a RESERVED, 673** PENDING, or EXCLUSIVE lock on the file. It returns true 674** if such a lock exists and false otherwise. 675** 676** The xFileControl() method is a generic interface that allows custom 677** VFS implementations to directly control an open file using the 678** [sqlite3_file_control()] interface. The second "op" argument is an 679** integer opcode. The third argument is a generic pointer intended to 680** point to a structure that may contain arguments or space in which to 681** write return values. Potential uses for xFileControl() might be 682** functions to enable blocking locks with timeouts, to change the 683** locking strategy (for example to use dot-file locks), to inquire 684** about the status of a lock, or to break stale locks. The SQLite 685** core reserves all opcodes less than 100 for its own use. 686** A [file control opcodes | list of opcodes] less than 100 is available. 687** Applications that define a custom xFileControl method should use opcodes 688** greater than 100 to avoid conflicts. VFS implementations should 689** return [SQLITE_NOTFOUND] for file control opcodes that they do not 690** recognize. 691** 692** The xSectorSize() method returns the sector size of the 693** device that underlies the file. The sector size is the 694** minimum write that can be performed without disturbing 695** other bytes in the file. The xDeviceCharacteristics() 696** method returns a bit vector describing behaviors of the 697** underlying device: 698** 699** <ul> 700** <li> [SQLITE_IOCAP_ATOMIC] 701** <li> [SQLITE_IOCAP_ATOMIC512] 702** <li> [SQLITE_IOCAP_ATOMIC1K] 703** <li> [SQLITE_IOCAP_ATOMIC2K] 704** <li> [SQLITE_IOCAP_ATOMIC4K] 705** <li> [SQLITE_IOCAP_ATOMIC8K] 706** <li> [SQLITE_IOCAP_ATOMIC16K] 707** <li> [SQLITE_IOCAP_ATOMIC32K] 708** <li> [SQLITE_IOCAP_ATOMIC64K] 709** <li> [SQLITE_IOCAP_SAFE_APPEND] 710** <li> [SQLITE_IOCAP_SEQUENTIAL] 711** </ul> 712** 713** The SQLITE_IOCAP_ATOMIC property means that all writes of 714** any size are atomic. The SQLITE_IOCAP_ATOMICnnn values 715** mean that writes of blocks that are nnn bytes in size and 716** are aligned to an address which is an integer multiple of 717** nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means 718** that when data is appended to a file, the data is appended 719** first then the size of the file is extended, never the other 720** way around. The SQLITE_IOCAP_SEQUENTIAL property means that 721** information is written to disk in the same order as calls 722** to xWrite(). 723** 724** If xRead() returns SQLITE_IOERR_SHORT_READ it must also fill 725** in the unread portions of the buffer with zeros. A VFS that 726** fails to zero-fill short reads might seem to work. However, 727** failure to zero-fill short reads will eventually lead to 728** database corruption. 729*/ 730typedef struct sqlite3_io_methods sqlite3_io_methods; 731struct sqlite3_io_methods { 732 int iVersion; 733 int (*xClose)(sqlite3_file*); 734 int (*xRead)(sqlite3_file*, void*, int iAmt, sqlite3_int64 iOfst); 735 int (*xWrite)(sqlite3_file*, const void*, int iAmt, sqlite3_int64 iOfst); 736 int (*xTruncate)(sqlite3_file*, sqlite3_int64 size); 737 int (*xSync)(sqlite3_file*, int flags); 738 int (*xFileSize)(sqlite3_file*, sqlite3_int64 *pSize); 739 int (*xLock)(sqlite3_file*, int); 740 int (*xUnlock)(sqlite3_file*, int); 741 int (*xCheckReservedLock)(sqlite3_file*, int *pResOut); 742 int (*xFileControl)(sqlite3_file*, int op, void *pArg); 743 int (*xSectorSize)(sqlite3_file*); 744 int (*xDeviceCharacteristics)(sqlite3_file*); 745 /* Methods above are valid for version 1 */ 746 int (*xShmMap)(sqlite3_file*, int iPg, int pgsz, int, void volatile**); 747 int (*xShmLock)(sqlite3_file*, int offset, int n, int flags); 748 void (*xShmBarrier)(sqlite3_file*); 749 int (*xShmUnmap)(sqlite3_file*, int deleteFlag); 750 /* Methods above are valid for version 2 */ 751 int (*xFetch)(sqlite3_file*, sqlite3_int64 iOfst, int iAmt, void **pp); 752 int (*xUnfetch)(sqlite3_file*, sqlite3_int64 iOfst, void *p); 753 /* Methods above are valid for version 3 */ 754 /* Additional methods may be added in future releases */ 755}; 756 757/* 758** CAPI3REF: Standard File Control Opcodes 759** KEYWORDS: {file control opcodes} {file control opcode} 760** 761** These integer constants are opcodes for the xFileControl method 762** of the [sqlite3_io_methods] object and for the [sqlite3_file_control()] 763** interface. 764** 765** <ul> 766** <li>[[SQLITE_FCNTL_LOCKSTATE]] 767** The [SQLITE_FCNTL_LOCKSTATE] opcode is used for debugging. This 768** opcode causes the xFileControl method to write the current state of 769** the lock (one of [SQLITE_LOCK_NONE], [SQLITE_LOCK_SHARED], 770** [SQLITE_LOCK_RESERVED], [SQLITE_LOCK_PENDING], or [SQLITE_LOCK_EXCLUSIVE]) 771** into an integer that the pArg argument points to. This capability 772** is used during testing and is only available when the SQLITE_TEST 773** compile-time option is used. 774** 775** <li>[[SQLITE_FCNTL_SIZE_HINT]] 776** The [SQLITE_FCNTL_SIZE_HINT] opcode is used by SQLite to give the VFS 777** layer a hint of how large the database file will grow to be during the 778** current transaction. This hint is not guaranteed to be accurate but it 779** is often close. The underlying VFS might choose to preallocate database 780** file space based on this hint in order to help writes to the database 781** file run faster. 782** 783** <li>[[SQLITE_FCNTL_CHUNK_SIZE]] 784** The [SQLITE_FCNTL_CHUNK_SIZE] opcode is used to request that the VFS 785** extends and truncates the database file in chunks of a size specified 786** by the user. The fourth argument to [sqlite3_file_control()] should 787** point to an integer (type int) containing the new chunk-size to use 788** for the nominated database. Allocating database file space in large 789** chunks (say 1MB at a time), may reduce file-system fragmentation and 790** improve performance on some systems. 791** 792** <li>[[SQLITE_FCNTL_FILE_POINTER]] 793** The [SQLITE_FCNTL_FILE_POINTER] opcode is used to obtain a pointer 794** to the [sqlite3_file] object associated with a particular database 795** connection. See the [sqlite3_file_control()] documentation for 796** additional information. 797** 798** <li>[[SQLITE_FCNTL_SYNC_OMITTED]] 799** No longer in use. 800** 801** <li>[[SQLITE_FCNTL_SYNC]] 802** The [SQLITE_FCNTL_SYNC] opcode is generated internally by SQLite and 803** sent to the VFS immediately before the xSync method is invoked on a 804** database file descriptor. Or, if the xSync method is not invoked 805** because the user has configured SQLite with 806** [PRAGMA synchronous | PRAGMA synchronous=OFF] it is invoked in place 807** of the xSync method. In most cases, the pointer argument passed with 808** this file-control is NULL. However, if the database file is being synced 809** as part of a multi-database commit, the argument points to a nul-terminated 810** string containing the transactions master-journal file name. VFSes that 811** do not need this signal should silently ignore this opcode. Applications 812** should not call [sqlite3_file_control()] with this opcode as doing so may 813** disrupt the operation of the specialized VFSes that do require it. 814** 815** <li>[[SQLITE_FCNTL_COMMIT_PHASETWO]] 816** The [SQLITE_FCNTL_COMMIT_PHASETWO] opcode is generated internally by SQLite 817** and sent to the VFS after a transaction has been committed immediately 818** but before the database is unlocked. VFSes that do not need this signal 819** should silently ignore this opcode. Applications should not call 820** [sqlite3_file_control()] with this opcode as doing so may disrupt the 821** operation of the specialized VFSes that do require it. 822** 823** <li>[[SQLITE_FCNTL_WIN32_AV_RETRY]] 824** ^The [SQLITE_FCNTL_WIN32_AV_RETRY] opcode is used to configure automatic 825** retry counts and intervals for certain disk I/O operations for the 826** windows [VFS] in order to provide robustness in the presence of 827** anti-virus programs. By default, the windows VFS will retry file read, 828** file write, and file delete operations up to 10 times, with a delay 829** of 25 milliseconds before the first retry and with the delay increasing 830** by an additional 25 milliseconds with each subsequent retry. This 831** opcode allows these two values (10 retries and 25 milliseconds of delay) 832** to be adjusted. The values are changed for all database connections 833** within the same process. The argument is a pointer to an array of two 834** integers where the first integer i the new retry count and the second 835** integer is the delay. If either integer is negative, then the setting 836** is not changed but instead the prior value of that setting is written 837** into the array entry, allowing the current retry settings to be 838** interrogated. The zDbName parameter is ignored. 839** 840** <li>[[SQLITE_FCNTL_PERSIST_WAL]] 841** ^The [SQLITE_FCNTL_PERSIST_WAL] opcode is used to set or query the 842** persistent [WAL | Write Ahead Log] setting. By default, the auxiliary 843** write ahead log and shared memory files used for transaction control 844** are automatically deleted when the latest connection to the database 845** closes. Setting persistent WAL mode causes those files to persist after 846** close. Persisting the files is useful when other processes that do not 847** have write permission on the directory containing the database file want 848** to read the database file, as the WAL and shared memory files must exist 849** in order for the database to be readable. The fourth parameter to 850** [sqlite3_file_control()] for this opcode should be a pointer to an integer. 851** That integer is 0 to disable persistent WAL mode or 1 to enable persistent 852** WAL mode. If the integer is -1, then it is overwritten with the current 853** WAL persistence setting. 854** 855** <li>[[SQLITE_FCNTL_POWERSAFE_OVERWRITE]] 856** ^The [SQLITE_FCNTL_POWERSAFE_OVERWRITE] opcode is used to set or query the 857** persistent "powersafe-overwrite" or "PSOW" setting. The PSOW setting 858** determines the [SQLITE_IOCAP_POWERSAFE_OVERWRITE] bit of the 859** xDeviceCharacteristics methods. The fourth parameter to 860** [sqlite3_file_control()] for this opcode should be a pointer to an integer. 861** That integer is 0 to disable zero-damage mode or 1 to enable zero-damage 862** mode. If the integer is -1, then it is overwritten with the current 863** zero-damage mode setting. 864** 865** <li>[[SQLITE_FCNTL_OVERWRITE]] 866** ^The [SQLITE_FCNTL_OVERWRITE] opcode is invoked by SQLite after opening 867** a write transaction to indicate that, unless it is rolled back for some 868** reason, the entire database file will be overwritten by the current 869** transaction. This is used by VACUUM operations. 870** 871** <li>[[SQLITE_FCNTL_VFSNAME]] 872** ^The [SQLITE_FCNTL_VFSNAME] opcode can be used to obtain the names of 873** all [VFSes] in the VFS stack. The names are of all VFS shims and the 874** final bottom-level VFS are written into memory obtained from 875** [sqlite3_malloc()] and the result is stored in the char* variable 876** that the fourth parameter of [sqlite3_file_control()] points to. 877** The caller is responsible for freeing the memory when done. As with 878** all file-control actions, there is no guarantee that this will actually 879** do anything. Callers should initialize the char* variable to a NULL 880** pointer in case this file-control is not implemented. This file-control 881** is intended for diagnostic use only. 882** 883** <li>[[SQLITE_FCNTL_PRAGMA]] 884** ^Whenever a [PRAGMA] statement is parsed, an [SQLITE_FCNTL_PRAGMA] 885** file control is sent to the open [sqlite3_file] object corresponding 886** to the database file to which the pragma statement refers. ^The argument 887** to the [SQLITE_FCNTL_PRAGMA] file control is an array of 888** pointers to strings (char**) in which the second element of the array 889** is the name of the pragma and the third element is the argument to the 890** pragma or NULL if the pragma has no argument. ^The handler for an 891** [SQLITE_FCNTL_PRAGMA] file control can optionally make the first element 892** of the char** argument point to a string obtained from [sqlite3_mprintf()] 893** or the equivalent and that string will become the result of the pragma or 894** the error message if the pragma fails. ^If the 895** [SQLITE_FCNTL_PRAGMA] file control returns [SQLITE_NOTFOUND], then normal 896** [PRAGMA] processing continues. ^If the [SQLITE_FCNTL_PRAGMA] 897** file control returns [SQLITE_OK], then the parser assumes that the 898** VFS has handled the PRAGMA itself and the parser generates a no-op 899** prepared statement if result string is NULL, or that returns a copy 900** of the result string if the string is non-NULL. 901** ^If the [SQLITE_FCNTL_PRAGMA] file control returns 902** any result code other than [SQLITE_OK] or [SQLITE_NOTFOUND], that means 903** that the VFS encountered an error while handling the [PRAGMA] and the 904** compilation of the PRAGMA fails with an error. ^The [SQLITE_FCNTL_PRAGMA] 905** file control occurs at the beginning of pragma statement analysis and so 906** it is able to override built-in [PRAGMA] statements. 907** 908** <li>[[SQLITE_FCNTL_BUSYHANDLER]] 909** ^The [SQLITE_FCNTL_BUSYHANDLER] 910** file-control may be invoked by SQLite on the database file handle 911** shortly after it is opened in order to provide a custom VFS with access 912** to the connections busy-handler callback. The argument is of type (void **) 913** - an array of two (void *) values. The first (void *) actually points 914** to a function of type (int (*)(void *)). In order to invoke the connections 915** busy-handler, this function should be invoked with the second (void *) in 916** the array as the only argument. If it returns non-zero, then the operation 917** should be retried. If it returns zero, the custom VFS should abandon the 918** current operation. 919** 920** <li>[[SQLITE_FCNTL_TEMPFILENAME]] 921** ^Application can invoke the [SQLITE_FCNTL_TEMPFILENAME] file-control 922** to have SQLite generate a 923** temporary filename using the same algorithm that is followed to generate 924** temporary filenames for TEMP tables and other internal uses. The 925** argument should be a char** which will be filled with the filename 926** written into memory obtained from [sqlite3_malloc()]. The caller should 927** invoke [sqlite3_free()] on the result to avoid a memory leak. 928** 929** <li>[[SQLITE_FCNTL_MMAP_SIZE]] 930** The [SQLITE_FCNTL_MMAP_SIZE] file control is used to query or set the 931** maximum number of bytes that will be used for memory-mapped I/O. 932** The argument is a pointer to a value of type sqlite3_int64 that 933** is an advisory maximum number of bytes in the file to memory map. The 934** pointer is overwritten with the old value. The limit is not changed if 935** the value originally pointed to is negative, and so the current limit 936** can be queried by passing in a pointer to a negative number. This 937** file-control is used internally to implement [PRAGMA mmap_size]. 938** 939** <li>[[SQLITE_FCNTL_TRACE]] 940** The [SQLITE_FCNTL_TRACE] file control provides advisory information 941** to the VFS about what the higher layers of the SQLite stack are doing. 942** This file control is used by some VFS activity tracing [shims]. 943** The argument is a zero-terminated string. Higher layers in the 944** SQLite stack may generate instances of this file control if 945** the [SQLITE_USE_FCNTL_TRACE] compile-time option is enabled. 946** 947** <li>[[SQLITE_FCNTL_HAS_MOVED]] 948** The [SQLITE_FCNTL_HAS_MOVED] file control interprets its argument as a 949** pointer to an integer and it writes a boolean into that integer depending 950** on whether or not the file has been renamed, moved, or deleted since it 951** was first opened. 952** 953** <li>[[SQLITE_FCNTL_WIN32_SET_HANDLE]] 954** The [SQLITE_FCNTL_WIN32_SET_HANDLE] opcode is used for debugging. This 955** opcode causes the xFileControl method to swap the file handle with the one 956** pointed to by the pArg argument. This capability is used during testing 957** and only needs to be supported when SQLITE_TEST is defined. 958** 959** <li>[[SQLITE_FCNTL_WAL_BLOCK]] 960** The [SQLITE_FCNTL_WAL_BLOCK] is a signal to the VFS layer that it might 961** be advantageous to block on the next WAL lock if the lock is not immediately 962** available. The WAL subsystem issues this signal during rare 963** circumstances in order to fix a problem with priority inversion. 964** Applications should <em>not</em> use this file-control. 965** 966** <li>[[SQLITE_FCNTL_ZIPVFS]] 967** The [SQLITE_FCNTL_ZIPVFS] opcode is implemented by zipvfs only. All other 968** VFS should return SQLITE_NOTFOUND for this opcode. 969** 970** <li>[[SQLITE_FCNTL_OTA]] 971** The [SQLITE_FCNTL_OTA] opcode is implemented by the special VFS used by 972** the OTA extension only. All other VFS should return SQLITE_NOTFOUND for 973** this opcode. 974** </ul> 975*/ 976#define SQLITE_FCNTL_LOCKSTATE 1 977#define SQLITE_FCNTL_GET_LOCKPROXYFILE 2 978#define SQLITE_FCNTL_SET_LOCKPROXYFILE 3 979#define SQLITE_FCNTL_LAST_ERRNO 4 980#define SQLITE_FCNTL_SIZE_HINT 5 981#define SQLITE_FCNTL_CHUNK_SIZE 6 982#define SQLITE_FCNTL_FILE_POINTER 7 983#define SQLITE_FCNTL_SYNC_OMITTED 8 984#define SQLITE_FCNTL_WIN32_AV_RETRY 9 985#define SQLITE_FCNTL_PERSIST_WAL 10 986#define SQLITE_FCNTL_OVERWRITE 11 987#define SQLITE_FCNTL_VFSNAME 12 988#define SQLITE_FCNTL_POWERSAFE_OVERWRITE 13 989#define SQLITE_FCNTL_PRAGMA 14 990#define SQLITE_FCNTL_BUSYHANDLER 15 991#define SQLITE_FCNTL_TEMPFILENAME 16 992#define SQLITE_FCNTL_MMAP_SIZE 18 993#define SQLITE_FCNTL_TRACE 19 994#define SQLITE_FCNTL_HAS_MOVED 20 995#define SQLITE_FCNTL_SYNC 21 996#define SQLITE_FCNTL_COMMIT_PHASETWO 22 997#define SQLITE_FCNTL_WIN32_SET_HANDLE 23 998#define SQLITE_FCNTL_WAL_BLOCK 24 999#define SQLITE_FCNTL_ZIPVFS 25 1000#define SQLITE_FCNTL_OTA 26 1001 1002/* deprecated names */ 1003#define SQLITE_GET_LOCKPROXYFILE SQLITE_FCNTL_GET_LOCKPROXYFILE 1004#define SQLITE_SET_LOCKPROXYFILE SQLITE_FCNTL_SET_LOCKPROXYFILE 1005#define SQLITE_LAST_ERRNO SQLITE_FCNTL_LAST_ERRNO 1006 1007 1008/* 1009** CAPI3REF: Mutex Handle 1010** 1011** The mutex module within SQLite defines [sqlite3_mutex] to be an 1012** abstract type for a mutex object. The SQLite core never looks 1013** at the internal representation of an [sqlite3_mutex]. It only 1014** deals with pointers to the [sqlite3_mutex] object. 1015** 1016** Mutexes are created using [sqlite3_mutex_alloc()]. 1017*/ 1018typedef struct sqlite3_mutex sqlite3_mutex; 1019 1020/* 1021** CAPI3REF: OS Interface Object 1022** 1023** An instance of the sqlite3_vfs object defines the interface between 1024** the SQLite core and the underlying operating system. The "vfs" 1025** in the name of the object stands for "virtual file system". See 1026** the [VFS | VFS documentation] for further information. 1027** 1028** The value of the iVersion field is initially 1 but may be larger in 1029** future versions of SQLite. Additional fields may be appended to this 1030** object when the iVersion value is increased. Note that the structure 1031** of the sqlite3_vfs object changes in the transaction between 1032** SQLite version 3.5.9 and 3.6.0 and yet the iVersion field was not 1033** modified. 1034** 1035** The szOsFile field is the size of the subclassed [sqlite3_file] 1036** structure used by this VFS. mxPathname is the maximum length of 1037** a pathname in this VFS. 1038** 1039** Registered sqlite3_vfs objects are kept on a linked list formed by 1040** the pNext pointer. The [sqlite3_vfs_register()] 1041** and [sqlite3_vfs_unregister()] interfaces manage this list 1042** in a thread-safe way. The [sqlite3_vfs_find()] interface 1043** searches the list. Neither the application code nor the VFS 1044** implementation should use the pNext pointer. 1045** 1046** The pNext field is the only field in the sqlite3_vfs 1047** structure that SQLite will ever modify. SQLite will only access 1048** or modify this field while holding a particular static mutex. 1049** The application should never modify anything within the sqlite3_vfs 1050** object once the object has been registered. 1051** 1052** The zName field holds the name of the VFS module. The name must 1053** be unique across all VFS modules. 1054** 1055** [[sqlite3_vfs.xOpen]] 1056** ^SQLite guarantees that the zFilename parameter to xOpen 1057** is either a NULL pointer or string obtained 1058** from xFullPathname() with an optional suffix added. 1059** ^If a suffix is added to the zFilename parameter, it will 1060** consist of a single "-" character followed by no more than 1061** 11 alphanumeric and/or "-" characters. 1062** ^SQLite further guarantees that 1063** the string will be valid and unchanged until xClose() is 1064** called. Because of the previous sentence, 1065** the [sqlite3_file] can safely store a pointer to the 1066** filename if it needs to remember the filename for some reason. 1067** If the zFilename parameter to xOpen is a NULL pointer then xOpen 1068** must invent its own temporary name for the file. ^Whenever the 1069** xFilename parameter is NULL it will also be the case that the 1070** flags parameter will include [SQLITE_OPEN_DELETEONCLOSE]. 1071** 1072** The flags argument to xOpen() includes all bits set in 1073** the flags argument to [sqlite3_open_v2()]. Or if [sqlite3_open()] 1074** or [sqlite3_open16()] is used, then flags includes at least 1075** [SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE]. 1076** If xOpen() opens a file read-only then it sets *pOutFlags to 1077** include [SQLITE_OPEN_READONLY]. Other bits in *pOutFlags may be set. 1078** 1079** ^(SQLite will also add one of the following flags to the xOpen() 1080** call, depending on the object being opened: 1081** 1082** <ul> 1083** <li> [SQLITE_OPEN_MAIN_DB] 1084** <li> [SQLITE_OPEN_MAIN_JOURNAL] 1085** <li> [SQLITE_OPEN_TEMP_DB] 1086** <li> [SQLITE_OPEN_TEMP_JOURNAL] 1087** <li> [SQLITE_OPEN_TRANSIENT_DB] 1088** <li> [SQLITE_OPEN_SUBJOURNAL] 1089** <li> [SQLITE_OPEN_MASTER_JOURNAL] 1090** <li> [SQLITE_OPEN_WAL] 1091** </ul>)^ 1092** 1093** The file I/O implementation can use the object type flags to 1094** change the way it deals with files. For example, an application 1095** that does not care about crash recovery or rollback might make 1096** the open of a journal file a no-op. Writes to this journal would 1097** also be no-ops, and any attempt to read the journal would return 1098** SQLITE_IOERR. Or the implementation might recognize that a database 1099** file will be doing page-aligned sector reads and writes in a random 1100** order and set up its I/O subsystem accordingly. 1101** 1102** SQLite might also add one of the following flags to the xOpen method: 1103** 1104** <ul> 1105** <li> [SQLITE_OPEN_DELETEONCLOSE] 1106** <li> [SQLITE_OPEN_EXCLUSIVE] 1107** </ul> 1108** 1109** The [SQLITE_OPEN_DELETEONCLOSE] flag means the file should be 1110** deleted when it is closed. ^The [SQLITE_OPEN_DELETEONCLOSE] 1111** will be set for TEMP databases and their journals, transient 1112** databases, and subjournals. 1113** 1114** ^The [SQLITE_OPEN_EXCLUSIVE] flag is always used in conjunction 1115** with the [SQLITE_OPEN_CREATE] flag, which are both directly 1116** analogous to the O_EXCL and O_CREAT flags of the POSIX open() 1117** API. The SQLITE_OPEN_EXCLUSIVE flag, when paired with the 1118** SQLITE_OPEN_CREATE, is used to indicate that file should always 1119** be created, and that it is an error if it already exists. 1120** It is <i>not</i> used to indicate the file should be opened 1121** for exclusive access. 1122** 1123** ^At least szOsFile bytes of memory are allocated by SQLite 1124** to hold the [sqlite3_file] structure passed as the third 1125** argument to xOpen. The xOpen method does not have to 1126** allocate the structure; it should just fill it in. Note that 1127** the xOpen method must set the sqlite3_file.pMethods to either 1128** a valid [sqlite3_io_methods] object or to NULL. xOpen must do 1129** this even if the open fails. SQLite expects that the sqlite3_file.pMethods 1130** element will be valid after xOpen returns regardless of the success 1131** or failure of the xOpen call. 1132** 1133** [[sqlite3_vfs.xAccess]] 1134** ^The flags argument to xAccess() may be [SQLITE_ACCESS_EXISTS] 1135** to test for the existence of a file, or [SQLITE_ACCESS_READWRITE] to 1136** test whether a file is readable and writable, or [SQLITE_ACCESS_READ] 1137** to test whether a file is at least readable. The file can be a 1138** directory. 1139** 1140** ^SQLite will always allocate at least mxPathname+1 bytes for the 1141** output buffer xFullPathname. The exact size of the output buffer 1142** is also passed as a parameter to both methods. If the output buffer 1143** is not large enough, [SQLITE_CANTOPEN] should be returned. Since this is 1144** handled as a fatal error by SQLite, vfs implementations should endeavor 1145** to prevent this by setting mxPathname to a sufficiently large value. 1146** 1147** The xRandomness(), xSleep(), xCurrentTime(), and xCurrentTimeInt64() 1148** interfaces are not strictly a part of the filesystem, but they are 1149** included in the VFS structure for completeness. 1150** The xRandomness() function attempts to return nBytes bytes 1151** of good-quality randomness into zOut. The return value is 1152** the actual number of bytes of randomness obtained. 1153** The xSleep() method causes the calling thread to sleep for at 1154** least the number of microseconds given. ^The xCurrentTime() 1155** method returns a Julian Day Number for the current date and time as 1156** a floating point value. 1157** ^The xCurrentTimeInt64() method returns, as an integer, the Julian 1158** Day Number multiplied by 86400000 (the number of milliseconds in 1159** a 24-hour day). 1160** ^SQLite will use the xCurrentTimeInt64() method to get the current 1161** date and time if that method is available (if iVersion is 2 or 1162** greater and the function pointer is not NULL) and will fall back 1163** to xCurrentTime() if xCurrentTimeInt64() is unavailable. 1164** 1165** ^The xSetSystemCall(), xGetSystemCall(), and xNestSystemCall() interfaces 1166** are not used by the SQLite core. These optional interfaces are provided 1167** by some VFSes to facilitate testing of the VFS code. By overriding 1168** system calls with functions under its control, a test program can 1169** simulate faults and error conditions that would otherwise be difficult 1170** or impossible to induce. The set of system calls that can be overridden 1171** varies from one VFS to another, and from one version of the same VFS to the 1172** next. Applications that use these interfaces must be prepared for any 1173** or all of these interfaces to be NULL or for their behavior to change 1174** from one release to the next. Applications must not attempt to access 1175** any of these methods if the iVersion of the VFS is less than 3. 1176*/ 1177typedef struct sqlite3_vfs sqlite3_vfs; 1178typedef void (*sqlite3_syscall_ptr)(void); 1179struct sqlite3_vfs { 1180 int iVersion; /* Structure version number (currently 3) */ 1181 int szOsFile; /* Size of subclassed sqlite3_file */ 1182 int mxPathname; /* Maximum file pathname length */ 1183 sqlite3_vfs *pNext; /* Next registered VFS */ 1184 const char *zName; /* Name of this virtual file system */ 1185 void *pAppData; /* Pointer to application-specific data */ 1186 int (*xOpen)(sqlite3_vfs*, const char *zName, sqlite3_file*, 1187 int flags, int *pOutFlags); 1188 int (*xDelete)(sqlite3_vfs*, const char *zName, int syncDir); 1189 int (*xAccess)(sqlite3_vfs*, const char *zName, int flags, int *pResOut); 1190 int (*xFullPathname)(sqlite3_vfs*, const char *zName, int nOut, char *zOut); 1191 void *(*xDlOpen)(sqlite3_vfs*, const char *zFilename); 1192 void (*xDlError)(sqlite3_vfs*, int nByte, char *zErrMsg); 1193 void (*(*xDlSym)(sqlite3_vfs*,void*, const char *zSymbol))(void); 1194 void (*xDlClose)(sqlite3_vfs*, void*); 1195 int (*xRandomness)(sqlite3_vfs*, int nByte, char *zOut); 1196 int (*xSleep)(sqlite3_vfs*, int microseconds); 1197 int (*xCurrentTime)(sqlite3_vfs*, double*); 1198 int (*xGetLastError)(sqlite3_vfs*, int, char *); 1199 /* 1200 ** The methods above are in version 1 of the sqlite_vfs object 1201 ** definition. Those that follow are added in version 2 or later 1202 */ 1203 int (*xCurrentTimeInt64)(sqlite3_vfs*, sqlite3_int64*); 1204 /* 1205 ** The methods above are in versions 1 and 2 of the sqlite_vfs object. 1206 ** Those below are for version 3 and greater. 1207 */ 1208 int (*xSetSystemCall)(sqlite3_vfs*, const char *zName, sqlite3_syscall_ptr); 1209 sqlite3_syscall_ptr (*xGetSystemCall)(sqlite3_vfs*, const char *zName); 1210 const char *(*xNextSystemCall)(sqlite3_vfs*, const char *zName); 1211 /* 1212 ** The methods above are in versions 1 through 3 of the sqlite_vfs object. 1213 ** New fields may be appended in figure versions. The iVersion 1214 ** value will increment whenever this happens. 1215 */ 1216}; 1217 1218/* 1219** CAPI3REF: Flags for the xAccess VFS method 1220** 1221** These integer constants can be used as the third parameter to 1222** the xAccess method of an [sqlite3_vfs] object. They determine 1223** what kind of permissions the xAccess method is looking for. 1224** With SQLITE_ACCESS_EXISTS, the xAccess method 1225** simply checks whether the file exists. 1226** With SQLITE_ACCESS_READWRITE, the xAccess method 1227** checks whether the named directory is both readable and writable 1228** (in other words, if files can be added, removed, and renamed within 1229** the directory). 1230** The SQLITE_ACCESS_READWRITE constant is currently used only by the 1231** [temp_store_directory pragma], though this could change in a future 1232** release of SQLite. 1233** With SQLITE_ACCESS_READ, the xAccess method 1234** checks whether the file is readable. The SQLITE_ACCESS_READ constant is 1235** currently unused, though it might be used in a future release of 1236** SQLite. 1237*/ 1238#define SQLITE_ACCESS_EXISTS 0 1239#define SQLITE_ACCESS_READWRITE 1 /* Used by PRAGMA temp_store_directory */ 1240#define SQLITE_ACCESS_READ 2 /* Unused */ 1241 1242/* 1243** CAPI3REF: Flags for the xShmLock VFS method 1244** 1245** These integer constants define the various locking operations 1246** allowed by the xShmLock method of [sqlite3_io_methods]. The 1247** following are the only legal combinations of flags to the 1248** xShmLock method: 1249** 1250** <ul> 1251** <li> SQLITE_SHM_LOCK | SQLITE_SHM_SHARED 1252** <li> SQLITE_SHM_LOCK | SQLITE_SHM_EXCLUSIVE 1253** <li> SQLITE_SHM_UNLOCK | SQLITE_SHM_SHARED 1254** <li> SQLITE_SHM_UNLOCK | SQLITE_SHM_EXCLUSIVE 1255** </ul> 1256** 1257** When unlocking, the same SHARED or EXCLUSIVE flag must be supplied as 1258** was given on the corresponding lock. 1259** 1260** The xShmLock method can transition between unlocked and SHARED or 1261** between unlocked and EXCLUSIVE. It cannot transition between SHARED 1262** and EXCLUSIVE. 1263*/ 1264#define SQLITE_SHM_UNLOCK 1 1265#define SQLITE_SHM_LOCK 2 1266#define SQLITE_SHM_SHARED 4 1267#define SQLITE_SHM_EXCLUSIVE 8 1268 1269/* 1270** CAPI3REF: Maximum xShmLock index 1271** 1272** The xShmLock method on [sqlite3_io_methods] may use values 1273** between 0 and this upper bound as its "offset" argument. 1274** The SQLite core will never attempt to acquire or release a 1275** lock outside of this range 1276*/ 1277#define SQLITE_SHM_NLOCK 8 1278 1279 1280/* 1281** CAPI3REF: Initialize The SQLite Library 1282** 1283** ^The sqlite3_initialize() routine initializes the 1284** SQLite library. ^The sqlite3_shutdown() routine 1285** deallocates any resources that were allocated by sqlite3_initialize(). 1286** These routines are designed to aid in process initialization and 1287** shutdown on embedded systems. Workstation applications using 1288** SQLite normally do not need to invoke either of these routines. 1289** 1290** A call to sqlite3_initialize() is an "effective" call if it is 1291** the first time sqlite3_initialize() is invoked during the lifetime of 1292** the process, or if it is the first time sqlite3_initialize() is invoked 1293** following a call to sqlite3_shutdown(). ^(Only an effective call 1294** of sqlite3_initialize() does any initialization. All other calls 1295** are harmless no-ops.)^ 1296** 1297** A call to sqlite3_shutdown() is an "effective" call if it is the first 1298** call to sqlite3_shutdown() since the last sqlite3_initialize(). ^(Only 1299** an effective call to sqlite3_shutdown() does any deinitialization. 1300** All other valid calls to sqlite3_shutdown() are harmless no-ops.)^ 1301** 1302** The sqlite3_initialize() interface is threadsafe, but sqlite3_shutdown() 1303** is not. The sqlite3_shutdown() interface must only be called from a 1304** single thread. All open [database connections] must be closed and all 1305** other SQLite resources must be deallocated prior to invoking 1306** sqlite3_shutdown(). 1307** 1308** Among other things, ^sqlite3_initialize() will invoke 1309** sqlite3_os_init(). Similarly, ^sqlite3_shutdown() 1310** will invoke sqlite3_os_end(). 1311** 1312** ^The sqlite3_initialize() routine returns [SQLITE_OK] on success. 1313** ^If for some reason, sqlite3_initialize() is unable to initialize 1314** the library (perhaps it is unable to allocate a needed resource such 1315** as a mutex) it returns an [error code] other than [SQLITE_OK]. 1316** 1317** ^The sqlite3_initialize() routine is called internally by many other 1318** SQLite interfaces so that an application usually does not need to 1319** invoke sqlite3_initialize() directly. For example, [sqlite3_open()] 1320** calls sqlite3_initialize() so the SQLite library will be automatically 1321** initialized when [sqlite3_open()] is called if it has not be initialized 1322** already. ^However, if SQLite is compiled with the [SQLITE_OMIT_AUTOINIT] 1323** compile-time option, then the automatic calls to sqlite3_initialize() 1324** are omitted and the application must call sqlite3_initialize() directly 1325** prior to using any other SQLite interface. For maximum portability, 1326** it is recommended that applications always invoke sqlite3_initialize() 1327** directly prior to using any other SQLite interface. Future releases 1328** of SQLite may require this. In other words, the behavior exhibited 1329** when SQLite is compiled with [SQLITE_OMIT_AUTOINIT] might become the 1330** default behavior in some future release of SQLite. 1331** 1332** The sqlite3_os_init() routine does operating-system specific 1333** initialization of the SQLite library. The sqlite3_os_end() 1334** routine undoes the effect of sqlite3_os_init(). Typical tasks 1335** performed by these routines include allocation or deallocation 1336** of static resources, initialization of global variables, 1337** setting up a default [sqlite3_vfs] module, or setting up 1338** a default configuration using [sqlite3_config()]. 1339** 1340** The application should never invoke either sqlite3_os_init() 1341** or sqlite3_os_end() directly. The application should only invoke 1342** sqlite3_initialize() and sqlite3_shutdown(). The sqlite3_os_init() 1343** interface is called automatically by sqlite3_initialize() and 1344** sqlite3_os_end() is called by sqlite3_shutdown(). Appropriate 1345** implementations for sqlite3_os_init() and sqlite3_os_end() 1346** are built into SQLite when it is compiled for Unix, Windows, or OS/2. 1347** When [custom builds | built for other platforms] 1348** (using the [SQLITE_OS_OTHER=1] compile-time 1349** option) the application must supply a suitable implementation for 1350** sqlite3_os_init() and sqlite3_os_end(). An application-supplied 1351** implementation of sqlite3_os_init() or sqlite3_os_end() 1352** must return [SQLITE_OK] on success and some other [error code] upon 1353** failure. 1354*/ 1355int sqlite3_initialize(void); 1356int sqlite3_shutdown(void); 1357int sqlite3_os_init(void); 1358int sqlite3_os_end(void); 1359 1360/* 1361** CAPI3REF: Configuring The SQLite Library 1362** 1363** The sqlite3_config() interface is used to make global configuration 1364** changes to SQLite in order to tune SQLite to the specific needs of 1365** the application. The default configuration is recommended for most 1366** applications and so this routine is usually not necessary. It is 1367** provided to support rare applications with unusual needs. 1368** 1369** The sqlite3_config() interface is not threadsafe. The application 1370** must insure that no other SQLite interfaces are invoked by other 1371** threads while sqlite3_config() is running. Furthermore, sqlite3_config() 1372** may only be invoked prior to library initialization using 1373** [sqlite3_initialize()] or after shutdown by [sqlite3_shutdown()]. 1374** ^If sqlite3_config() is called after [sqlite3_initialize()] and before 1375** [sqlite3_shutdown()] then it will return SQLITE_MISUSE. 1376** Note, however, that ^sqlite3_config() can be called as part of the 1377** implementation of an application-defined [sqlite3_os_init()]. 1378** 1379** The first argument to sqlite3_config() is an integer 1380** [configuration option] that determines 1381** what property of SQLite is to be configured. Subsequent arguments 1382** vary depending on the [configuration option] 1383** in the first argument. 1384** 1385** ^When a configuration option is set, sqlite3_config() returns [SQLITE_OK]. 1386** ^If the option is unknown or SQLite is unable to set the option 1387** then this routine returns a non-zero [error code]. 1388*/ 1389int sqlite3_config(int, ...); 1390 1391/* 1392** CAPI3REF: Configure database connections 1393** METHOD: sqlite3 1394** 1395** The sqlite3_db_config() interface is used to make configuration 1396** changes to a [database connection]. The interface is similar to 1397** [sqlite3_config()] except that the changes apply to a single 1398** [database connection] (specified in the first argument). 1399** 1400** The second argument to sqlite3_db_config(D,V,...) is the 1401** [SQLITE_DBCONFIG_LOOKASIDE | configuration verb] - an integer code 1402** that indicates what aspect of the [database connection] is being configured. 1403** Subsequent arguments vary depending on the configuration verb. 1404** 1405** ^Calls to sqlite3_db_config() return SQLITE_OK if and only if 1406** the call is considered successful. 1407*/ 1408int sqlite3_db_config(sqlite3*, int op, ...); 1409 1410/* 1411** CAPI3REF: Memory Allocation Routines 1412** 1413** An instance of this object defines the interface between SQLite 1414** and low-level memory allocation routines. 1415** 1416** This object is used in only one place in the SQLite interface. 1417** A pointer to an instance of this object is the argument to 1418** [sqlite3_config()] when the configuration option is 1419** [SQLITE_CONFIG_MALLOC] or [SQLITE_CONFIG_GETMALLOC]. 1420** By creating an instance of this object 1421** and passing it to [sqlite3_config]([SQLITE_CONFIG_MALLOC]) 1422** during configuration, an application can specify an alternative 1423** memory allocation subsystem for SQLite to use for all of its 1424** dynamic memory needs. 1425** 1426** Note that SQLite comes with several [built-in memory allocators] 1427** that are perfectly adequate for the overwhelming majority of applications 1428** and that this object is only useful to a tiny minority of applications 1429** with specialized memory allocation requirements. This object is 1430** also used during testing of SQLite in order to specify an alternative 1431** memory allocator that simulates memory out-of-memory conditions in 1432** order to verify that SQLite recovers gracefully from such 1433** conditions. 1434** 1435** The xMalloc, xRealloc, and xFree methods must work like the 1436** malloc(), realloc() and free() functions from the standard C library. 1437** ^SQLite guarantees that the second argument to 1438** xRealloc is always a value returned by a prior call to xRoundup. 1439** 1440** xSize should return the allocated size of a memory allocation 1441** previously obtained from xMalloc or xRealloc. The allocated size 1442** is always at least as big as the requested size but may be larger. 1443** 1444** The xRoundup method returns what would be the allocated size of 1445** a memory allocation given a particular requested size. Most memory 1446** allocators round up memory allocations at least to the next multiple 1447** of 8. Some allocators round up to a larger multiple or to a power of 2. 1448** Every memory allocation request coming in through [sqlite3_malloc()] 1449** or [sqlite3_realloc()] first calls xRoundup. If xRoundup returns 0, 1450** that causes the corresponding memory allocation to fail. 1451** 1452** The xInit method initializes the memory allocator. For example, 1453** it might allocate any require mutexes or initialize internal data 1454** structures. The xShutdown method is invoked (indirectly) by 1455** [sqlite3_shutdown()] and should deallocate any resources acquired 1456** by xInit. The pAppData pointer is used as the only parameter to 1457** xInit and xShutdown. 1458** 1459** SQLite holds the [SQLITE_MUTEX_STATIC_MASTER] mutex when it invokes 1460** the xInit method, so the xInit method need not be threadsafe. The 1461** xShutdown method is only called from [sqlite3_shutdown()] so it does 1462** not need to be threadsafe either. For all other methods, SQLite 1463** holds the [SQLITE_MUTEX_STATIC_MEM] mutex as long as the 1464** [SQLITE_CONFIG_MEMSTATUS] configuration option is turned on (which 1465** it is by default) and so the methods are automatically serialized. 1466** However, if [SQLITE_CONFIG_MEMSTATUS] is disabled, then the other 1467** methods must be threadsafe or else make their own arrangements for 1468** serialization. 1469** 1470** SQLite will never invoke xInit() more than once without an intervening 1471** call to xShutdown(). 1472*/ 1473typedef struct sqlite3_mem_methods sqlite3_mem_methods; 1474struct sqlite3_mem_methods { 1475 void *(*xMalloc)(int); /* Memory allocation function */ 1476 void (*xFree)(void*); /* Free a prior allocation */ 1477 void *(*xRealloc)(void*,int); /* Resize an allocation */ 1478 int (*xSize)(void*); /* Return the size of an allocation */ 1479 int (*xRoundup)(int); /* Round up request size to allocation size */ 1480 int (*xInit)(void*); /* Initialize the memory allocator */ 1481 void (*xShutdown)(void*); /* Deinitialize the memory allocator */ 1482 void *pAppData; /* Argument to xInit() and xShutdown() */ 1483}; 1484 1485/* 1486** CAPI3REF: Configuration Options 1487** KEYWORDS: {configuration option} 1488** 1489** These constants are the available integer configuration options that 1490** can be passed as the first argument to the [sqlite3_config()] interface. 1491** 1492** New configuration options may be added in future releases of SQLite. 1493** Existing configuration options might be discontinued. Applications 1494** should check the return code from [sqlite3_config()] to make sure that 1495** the call worked. The [sqlite3_config()] interface will return a 1496** non-zero [error code] if a discontinued or unsupported configuration option 1497** is invoked. 1498** 1499** <dl> 1500** [[SQLITE_CONFIG_SINGLETHREAD]] <dt>SQLITE_CONFIG_SINGLETHREAD</dt> 1501** <dd>There are no arguments to this option. ^This option sets the 1502** [threading mode] to Single-thread. In other words, it disables 1503** all mutexing and puts SQLite into a mode where it can only be used 1504** by a single thread. ^If SQLite is compiled with 1505** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1506** it is not possible to change the [threading mode] from its default 1507** value of Single-thread and so [sqlite3_config()] will return 1508** [SQLITE_ERROR] if called with the SQLITE_CONFIG_SINGLETHREAD 1509** configuration option.</dd> 1510** 1511** [[SQLITE_CONFIG_MULTITHREAD]] <dt>SQLITE_CONFIG_MULTITHREAD</dt> 1512** <dd>There are no arguments to this option. ^This option sets the 1513** [threading mode] to Multi-thread. In other words, it disables 1514** mutexing on [database connection] and [prepared statement] objects. 1515** The application is responsible for serializing access to 1516** [database connections] and [prepared statements]. But other mutexes 1517** are enabled so that SQLite will be safe to use in a multi-threaded 1518** environment as long as no two threads attempt to use the same 1519** [database connection] at the same time. ^If SQLite is compiled with 1520** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1521** it is not possible to set the Multi-thread [threading mode] and 1522** [sqlite3_config()] will return [SQLITE_ERROR] if called with the 1523** SQLITE_CONFIG_MULTITHREAD configuration option.</dd> 1524** 1525** [[SQLITE_CONFIG_SERIALIZED]] <dt>SQLITE_CONFIG_SERIALIZED</dt> 1526** <dd>There are no arguments to this option. ^This option sets the 1527** [threading mode] to Serialized. In other words, this option enables 1528** all mutexes including the recursive 1529** mutexes on [database connection] and [prepared statement] objects. 1530** In this mode (which is the default when SQLite is compiled with 1531** [SQLITE_THREADSAFE=1]) the SQLite library will itself serialize access 1532** to [database connections] and [prepared statements] so that the 1533** application is free to use the same [database connection] or the 1534** same [prepared statement] in different threads at the same time. 1535** ^If SQLite is compiled with 1536** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1537** it is not possible to set the Serialized [threading mode] and 1538** [sqlite3_config()] will return [SQLITE_ERROR] if called with the 1539** SQLITE_CONFIG_SERIALIZED configuration option.</dd> 1540** 1541** [[SQLITE_CONFIG_MALLOC]] <dt>SQLITE_CONFIG_MALLOC</dt> 1542** <dd> ^(The SQLITE_CONFIG_MALLOC option takes a single argument which is 1543** a pointer to an instance of the [sqlite3_mem_methods] structure. 1544** The argument specifies 1545** alternative low-level memory allocation routines to be used in place of 1546** the memory allocation routines built into SQLite.)^ ^SQLite makes 1547** its own private copy of the content of the [sqlite3_mem_methods] structure 1548** before the [sqlite3_config()] call returns.</dd> 1549** 1550** [[SQLITE_CONFIG_GETMALLOC]] <dt>SQLITE_CONFIG_GETMALLOC</dt> 1551** <dd> ^(The SQLITE_CONFIG_GETMALLOC option takes a single argument which 1552** is a pointer to an instance of the [sqlite3_mem_methods] structure. 1553** The [sqlite3_mem_methods] 1554** structure is filled with the currently defined memory allocation routines.)^ 1555** This option can be used to overload the default memory allocation 1556** routines with a wrapper that simulations memory allocation failure or 1557** tracks memory usage, for example. </dd> 1558** 1559** [[SQLITE_CONFIG_MEMSTATUS]] <dt>SQLITE_CONFIG_MEMSTATUS</dt> 1560** <dd> ^The SQLITE_CONFIG_MEMSTATUS option takes single argument of type int, 1561** interpreted as a boolean, which enables or disables the collection of 1562** memory allocation statistics. ^(When memory allocation statistics are 1563** disabled, the following SQLite interfaces become non-operational: 1564** <ul> 1565** <li> [sqlite3_memory_used()] 1566** <li> [sqlite3_memory_highwater()] 1567** <li> [sqlite3_soft_heap_limit64()] 1568** <li> [sqlite3_status64()] 1569** </ul>)^ 1570** ^Memory allocation statistics are enabled by default unless SQLite is 1571** compiled with [SQLITE_DEFAULT_MEMSTATUS]=0 in which case memory 1572** allocation statistics are disabled by default. 1573** </dd> 1574** 1575** [[SQLITE_CONFIG_SCRATCH]] <dt>SQLITE_CONFIG_SCRATCH</dt> 1576** <dd> ^The SQLITE_CONFIG_SCRATCH option specifies a static memory buffer 1577** that SQLite can use for scratch memory. ^(There are three arguments 1578** to SQLITE_CONFIG_SCRATCH: A pointer an 8-byte 1579** aligned memory buffer from which the scratch allocations will be 1580** drawn, the size of each scratch allocation (sz), 1581** and the maximum number of scratch allocations (N).)^ 1582** The first argument must be a pointer to an 8-byte aligned buffer 1583** of at least sz*N bytes of memory. 1584** ^SQLite will not use more than one scratch buffers per thread. 1585** ^SQLite will never request a scratch buffer that is more than 6 1586** times the database page size. 1587** ^If SQLite needs needs additional 1588** scratch memory beyond what is provided by this configuration option, then 1589** [sqlite3_malloc()] will be used to obtain the memory needed.<p> 1590** ^When the application provides any amount of scratch memory using 1591** SQLITE_CONFIG_SCRATCH, SQLite avoids unnecessary large 1592** [sqlite3_malloc|heap allocations]. 1593** This can help [Robson proof|prevent memory allocation failures] due to heap 1594** fragmentation in low-memory embedded systems. 1595** </dd> 1596** 1597** [[SQLITE_CONFIG_PAGECACHE]] <dt>SQLITE_CONFIG_PAGECACHE</dt> 1598** <dd> ^The SQLITE_CONFIG_PAGECACHE option specifies a static memory buffer 1599** that SQLite can use for the database page cache with the default page 1600** cache implementation. 1601** This configuration should not be used if an application-define page 1602** cache implementation is loaded using the [SQLITE_CONFIG_PCACHE2] 1603** configuration option. 1604** ^There are three arguments to SQLITE_CONFIG_PAGECACHE: A pointer to 1605** 8-byte aligned 1606** memory, the size of each page buffer (sz), and the number of pages (N). 1607** The sz argument should be the size of the largest database page 1608** (a power of two between 512 and 65536) plus some extra bytes for each 1609** page header. ^The number of extra bytes needed by the page header 1610** can be determined using the [SQLITE_CONFIG_PCACHE_HDRSZ] option 1611** to [sqlite3_config()]. 1612** ^It is harmless, apart from the wasted memory, 1613** for the sz parameter to be larger than necessary. The first 1614** argument should pointer to an 8-byte aligned block of memory that 1615** is at least sz*N bytes of memory, otherwise subsequent behavior is 1616** undefined. 1617** ^SQLite will use the memory provided by the first argument to satisfy its 1618** memory needs for the first N pages that it adds to cache. ^If additional 1619** page cache memory is needed beyond what is provided by this option, then 1620** SQLite goes to [sqlite3_malloc()] for the additional storage space.</dd> 1621** 1622** [[SQLITE_CONFIG_HEAP]] <dt>SQLITE_CONFIG_HEAP</dt> 1623** <dd> ^The SQLITE_CONFIG_HEAP option specifies a static memory buffer 1624** that SQLite will use for all of its dynamic memory allocation needs 1625** beyond those provided for by [SQLITE_CONFIG_SCRATCH] and 1626** [SQLITE_CONFIG_PAGECACHE]. 1627** ^The SQLITE_CONFIG_HEAP option is only available if SQLite is compiled 1628** with either [SQLITE_ENABLE_MEMSYS3] or [SQLITE_ENABLE_MEMSYS5] and returns 1629** [SQLITE_ERROR] if invoked otherwise. 1630** ^There are three arguments to SQLITE_CONFIG_HEAP: 1631** An 8-byte aligned pointer to the memory, 1632** the number of bytes in the memory buffer, and the minimum allocation size. 1633** ^If the first pointer (the memory pointer) is NULL, then SQLite reverts 1634** to using its default memory allocator (the system malloc() implementation), 1635** undoing any prior invocation of [SQLITE_CONFIG_MALLOC]. ^If the 1636** memory pointer is not NULL then the alternative memory 1637** allocator is engaged to handle all of SQLites memory allocation needs. 1638** The first pointer (the memory pointer) must be aligned to an 8-byte 1639** boundary or subsequent behavior of SQLite will be undefined. 1640** The minimum allocation size is capped at 2**12. Reasonable values 1641** for the minimum allocation size are 2**5 through 2**8.</dd> 1642** 1643** [[SQLITE_CONFIG_MUTEX]] <dt>SQLITE_CONFIG_MUTEX</dt> 1644** <dd> ^(The SQLITE_CONFIG_MUTEX option takes a single argument which is a 1645** pointer to an instance of the [sqlite3_mutex_methods] structure. 1646** The argument specifies alternative low-level mutex routines to be used 1647** in place the mutex routines built into SQLite.)^ ^SQLite makes a copy of 1648** the content of the [sqlite3_mutex_methods] structure before the call to 1649** [sqlite3_config()] returns. ^If SQLite is compiled with 1650** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1651** the entire mutexing subsystem is omitted from the build and hence calls to 1652** [sqlite3_config()] with the SQLITE_CONFIG_MUTEX configuration option will 1653** return [SQLITE_ERROR].</dd> 1654** 1655** [[SQLITE_CONFIG_GETMUTEX]] <dt>SQLITE_CONFIG_GETMUTEX</dt> 1656** <dd> ^(The SQLITE_CONFIG_GETMUTEX option takes a single argument which 1657** is a pointer to an instance of the [sqlite3_mutex_methods] structure. The 1658** [sqlite3_mutex_methods] 1659** structure is filled with the currently defined mutex routines.)^ 1660** This option can be used to overload the default mutex allocation 1661** routines with a wrapper used to track mutex usage for performance 1662** profiling or testing, for example. ^If SQLite is compiled with 1663** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then 1664** the entire mutexing subsystem is omitted from the build and hence calls to 1665** [sqlite3_config()] with the SQLITE_CONFIG_GETMUTEX configuration option will 1666** return [SQLITE_ERROR].</dd> 1667** 1668** [[SQLITE_CONFIG_LOOKASIDE]] <dt>SQLITE_CONFIG_LOOKASIDE</dt> 1669** <dd> ^(The SQLITE_CONFIG_LOOKASIDE option takes two arguments that determine 1670** the default size of lookaside memory on each [database connection]. 1671** The first argument is the 1672** size of each lookaside buffer slot and the second is the number of 1673** slots allocated to each database connection.)^ ^(SQLITE_CONFIG_LOOKASIDE 1674** sets the <i>default</i> lookaside size. The [SQLITE_DBCONFIG_LOOKASIDE] 1675** option to [sqlite3_db_config()] can be used to change the lookaside 1676** configuration on individual connections.)^ </dd> 1677** 1678** [[SQLITE_CONFIG_PCACHE2]] <dt>SQLITE_CONFIG_PCACHE2</dt> 1679** <dd> ^(The SQLITE_CONFIG_PCACHE2 option takes a single argument which is 1680** a pointer to an [sqlite3_pcache_methods2] object. This object specifies 1681** the interface to a custom page cache implementation.)^ 1682** ^SQLite makes a copy of the [sqlite3_pcache_methods2] object.</dd> 1683** 1684** [[SQLITE_CONFIG_GETPCACHE2]] <dt>SQLITE_CONFIG_GETPCACHE2</dt> 1685** <dd> ^(The SQLITE_CONFIG_GETPCACHE2 option takes a single argument which 1686** is a pointer to an [sqlite3_pcache_methods2] object. SQLite copies of 1687** the current page cache implementation into that object.)^ </dd> 1688** 1689** [[SQLITE_CONFIG_LOG]] <dt>SQLITE_CONFIG_LOG</dt> 1690** <dd> The SQLITE_CONFIG_LOG option is used to configure the SQLite 1691** global [error log]. 1692** (^The SQLITE_CONFIG_LOG option takes two arguments: a pointer to a 1693** function with a call signature of void(*)(void*,int,const char*), 1694** and a pointer to void. ^If the function pointer is not NULL, it is 1695** invoked by [sqlite3_log()] to process each logging event. ^If the 1696** function pointer is NULL, the [sqlite3_log()] interface becomes a no-op. 1697** ^The void pointer that is the second argument to SQLITE_CONFIG_LOG is 1698** passed through as the first parameter to the application-defined logger 1699** function whenever that function is invoked. ^The second parameter to 1700** the logger function is a copy of the first parameter to the corresponding 1701** [sqlite3_log()] call and is intended to be a [result code] or an 1702** [extended result code]. ^The third parameter passed to the logger is 1703** log message after formatting via [sqlite3_snprintf()]. 1704** The SQLite logging interface is not reentrant; the logger function 1705** supplied by the application must not invoke any SQLite interface. 1706** In a multi-threaded application, the application-defined logger 1707** function must be threadsafe. </dd> 1708** 1709** [[SQLITE_CONFIG_URI]] <dt>SQLITE_CONFIG_URI 1710** <dd>^(The SQLITE_CONFIG_URI option takes a single argument of type int. 1711** If non-zero, then URI handling is globally enabled. If the parameter is zero, 1712** then URI handling is globally disabled.)^ ^If URI handling is globally 1713** enabled, all filenames passed to [sqlite3_open()], [sqlite3_open_v2()], 1714** [sqlite3_open16()] or 1715** specified as part of [ATTACH] commands are interpreted as URIs, regardless 1716** of whether or not the [SQLITE_OPEN_URI] flag is set when the database 1717** connection is opened. ^If it is globally disabled, filenames are 1718** only interpreted as URIs if the SQLITE_OPEN_URI flag is set when the 1719** database connection is opened. ^(By default, URI handling is globally 1720** disabled. The default value may be changed by compiling with the 1721** [SQLITE_USE_URI] symbol defined.)^ 1722** 1723** [[SQLITE_CONFIG_COVERING_INDEX_SCAN]] <dt>SQLITE_CONFIG_COVERING_INDEX_SCAN 1724** <dd>^The SQLITE_CONFIG_COVERING_INDEX_SCAN option takes a single integer 1725** argument which is interpreted as a boolean in order to enable or disable 1726** the use of covering indices for full table scans in the query optimizer. 1727** ^The default setting is determined 1728** by the [SQLITE_ALLOW_COVERING_INDEX_SCAN] compile-time option, or is "on" 1729** if that compile-time option is omitted. 1730** The ability to disable the use of covering indices for full table scans 1731** is because some incorrectly coded legacy applications might malfunction 1732** when the optimization is enabled. Providing the ability to 1733** disable the optimization allows the older, buggy application code to work 1734** without change even with newer versions of SQLite. 1735** 1736** [[SQLITE_CONFIG_PCACHE]] [[SQLITE_CONFIG_GETPCACHE]] 1737** <dt>SQLITE_CONFIG_PCACHE and SQLITE_CONFIG_GETPCACHE 1738** <dd> These options are obsolete and should not be used by new code. 1739** They are retained for backwards compatibility but are now no-ops. 1740** </dd> 1741** 1742** [[SQLITE_CONFIG_SQLLOG]] 1743** <dt>SQLITE_CONFIG_SQLLOG 1744** <dd>This option is only available if sqlite is compiled with the 1745** [SQLITE_ENABLE_SQLLOG] pre-processor macro defined. The first argument should 1746** be a pointer to a function of type void(*)(void*,sqlite3*,const char*, int). 1747** The second should be of type (void*). The callback is invoked by the library 1748** in three separate circumstances, identified by the value passed as the 1749** fourth parameter. If the fourth parameter is 0, then the database connection 1750** passed as the second argument has just been opened. The third argument 1751** points to a buffer containing the name of the main database file. If the 1752** fourth parameter is 1, then the SQL statement that the third parameter 1753** points to has just been executed. Or, if the fourth parameter is 2, then 1754** the connection being passed as the second parameter is being closed. The 1755** third parameter is passed NULL In this case. An example of using this 1756** configuration option can be seen in the "test_sqllog.c" source file in 1757** the canonical SQLite source tree.</dd> 1758** 1759** [[SQLITE_CONFIG_MMAP_SIZE]] 1760** <dt>SQLITE_CONFIG_MMAP_SIZE 1761** <dd>^SQLITE_CONFIG_MMAP_SIZE takes two 64-bit integer (sqlite3_int64) values 1762** that are the default mmap size limit (the default setting for 1763** [PRAGMA mmap_size]) and the maximum allowed mmap size limit. 1764** ^The default setting can be overridden by each database connection using 1765** either the [PRAGMA mmap_size] command, or by using the 1766** [SQLITE_FCNTL_MMAP_SIZE] file control. ^(The maximum allowed mmap size 1767** will be silently truncated if necessary so that it does not exceed the 1768** compile-time maximum mmap size set by the 1769** [SQLITE_MAX_MMAP_SIZE] compile-time option.)^ 1770** ^If either argument to this option is negative, then that argument is 1771** changed to its compile-time default. 1772** 1773** [[SQLITE_CONFIG_WIN32_HEAPSIZE]] 1774** <dt>SQLITE_CONFIG_WIN32_HEAPSIZE 1775** <dd>^The SQLITE_CONFIG_WIN32_HEAPSIZE option is only available if SQLite is 1776** compiled for Windows with the [SQLITE_WIN32_MALLOC] pre-processor macro 1777** defined. ^SQLITE_CONFIG_WIN32_HEAPSIZE takes a 32-bit unsigned integer value 1778** that specifies the maximum size of the created heap. 1779** 1780** [[SQLITE_CONFIG_PCACHE_HDRSZ]] 1781** <dt>SQLITE_CONFIG_PCACHE_HDRSZ 1782** <dd>^The SQLITE_CONFIG_PCACHE_HDRSZ option takes a single parameter which 1783** is a pointer to an integer and writes into that integer the number of extra 1784** bytes per page required for each page in [SQLITE_CONFIG_PAGECACHE]. 1785** The amount of extra space required can change depending on the compiler, 1786** target platform, and SQLite version. 1787** 1788** [[SQLITE_CONFIG_PMASZ]] 1789** <dt>SQLITE_CONFIG_PMASZ 1790** <dd>^The SQLITE_CONFIG_PMASZ option takes a single parameter which 1791** is an unsigned integer and sets the "Minimum PMA Size" for the multithreaded 1792** sorter to that integer. The default minimum PMA Size is set by the 1793** [SQLITE_SORTER_PMASZ] compile-time option. New threads are launched 1794** to help with sort operations when multithreaded sorting 1795** is enabled (using the [PRAGMA threads] command) and the amount of content 1796** to be sorted exceeds the page size times the minimum of the 1797** [PRAGMA cache_size] setting and this value. 1798** </dl> 1799*/ 1800#define SQLITE_CONFIG_SINGLETHREAD 1 /* nil */ 1801#define SQLITE_CONFIG_MULTITHREAD 2 /* nil */ 1802#define SQLITE_CONFIG_SERIALIZED 3 /* nil */ 1803#define SQLITE_CONFIG_MALLOC 4 /* sqlite3_mem_methods* */ 1804#define SQLITE_CONFIG_GETMALLOC 5 /* sqlite3_mem_methods* */ 1805#define SQLITE_CONFIG_SCRATCH 6 /* void*, int sz, int N */ 1806#define SQLITE_CONFIG_PAGECACHE 7 /* void*, int sz, int N */ 1807#define SQLITE_CONFIG_HEAP 8 /* void*, int nByte, int min */ 1808#define SQLITE_CONFIG_MEMSTATUS 9 /* boolean */ 1809#define SQLITE_CONFIG_MUTEX 10 /* sqlite3_mutex_methods* */ 1810#define SQLITE_CONFIG_GETMUTEX 11 /* sqlite3_mutex_methods* */ 1811/* previously SQLITE_CONFIG_CHUNKALLOC 12 which is now unused. */ 1812#define SQLITE_CONFIG_LOOKASIDE 13 /* int int */ 1813#define SQLITE_CONFIG_PCACHE 14 /* no-op */ 1814#define SQLITE_CONFIG_GETPCACHE 15 /* no-op */ 1815#define SQLITE_CONFIG_LOG 16 /* xFunc, void* */ 1816#define SQLITE_CONFIG_URI 17 /* int */ 1817#define SQLITE_CONFIG_PCACHE2 18 /* sqlite3_pcache_methods2* */ 1818#define SQLITE_CONFIG_GETPCACHE2 19 /* sqlite3_pcache_methods2* */ 1819#define SQLITE_CONFIG_COVERING_INDEX_SCAN 20 /* int */ 1820#define SQLITE_CONFIG_SQLLOG 21 /* xSqllog, void* */ 1821#define SQLITE_CONFIG_MMAP_SIZE 22 /* sqlite3_int64, sqlite3_int64 */ 1822#define SQLITE_CONFIG_WIN32_HEAPSIZE 23 /* int nByte */ 1823#define SQLITE_CONFIG_PCACHE_HDRSZ 24 /* int *psz */ 1824#define SQLITE_CONFIG_PMASZ 25 /* unsigned int szPma */ 1825 1826/* 1827** CAPI3REF: Database Connection Configuration Options 1828** 1829** These constants are the available integer configuration options that 1830** can be passed as the second argument to the [sqlite3_db_config()] interface. 1831** 1832** New configuration options may be added in future releases of SQLite. 1833** Existing configuration options might be discontinued. Applications 1834** should check the return code from [sqlite3_db_config()] to make sure that 1835** the call worked. ^The [sqlite3_db_config()] interface will return a 1836** non-zero [error code] if a discontinued or unsupported configuration option 1837** is invoked. 1838** 1839** <dl> 1840** <dt>SQLITE_DBCONFIG_LOOKASIDE</dt> 1841** <dd> ^This option takes three additional arguments that determine the 1842** [lookaside memory allocator] configuration for the [database connection]. 1843** ^The first argument (the third parameter to [sqlite3_db_config()] is a 1844** pointer to a memory buffer to use for lookaside memory. 1845** ^The first argument after the SQLITE_DBCONFIG_LOOKASIDE verb 1846** may be NULL in which case SQLite will allocate the 1847** lookaside buffer itself using [sqlite3_malloc()]. ^The second argument is the 1848** size of each lookaside buffer slot. ^The third argument is the number of 1849** slots. The size of the buffer in the first argument must be greater than 1850** or equal to the product of the second and third arguments. The buffer 1851** must be aligned to an 8-byte boundary. ^If the second argument to 1852** SQLITE_DBCONFIG_LOOKASIDE is not a multiple of 8, it is internally 1853** rounded down to the next smaller multiple of 8. ^(The lookaside memory 1854** configuration for a database connection can only be changed when that 1855** connection is not currently using lookaside memory, or in other words 1856** when the "current value" returned by 1857** [sqlite3_db_status](D,[SQLITE_CONFIG_LOOKASIDE],...) is zero. 1858** Any attempt to change the lookaside memory configuration when lookaside 1859** memory is in use leaves the configuration unchanged and returns 1860** [SQLITE_BUSY].)^</dd> 1861** 1862** <dt>SQLITE_DBCONFIG_ENABLE_FKEY</dt> 1863** <dd> ^This option is used to enable or disable the enforcement of 1864** [foreign key constraints]. There should be two additional arguments. 1865** The first argument is an integer which is 0 to disable FK enforcement, 1866** positive to enable FK enforcement or negative to leave FK enforcement 1867** unchanged. The second parameter is a pointer to an integer into which 1868** is written 0 or 1 to indicate whether FK enforcement is off or on 1869** following this call. The second parameter may be a NULL pointer, in 1870** which case the FK enforcement setting is not reported back. </dd> 1871** 1872** <dt>SQLITE_DBCONFIG_ENABLE_TRIGGER</dt> 1873** <dd> ^This option is used to enable or disable [CREATE TRIGGER | triggers]. 1874** There should be two additional arguments. 1875** The first argument is an integer which is 0 to disable triggers, 1876** positive to enable triggers or negative to leave the setting unchanged. 1877** The second parameter is a pointer to an integer into which 1878** is written 0 or 1 to indicate whether triggers are disabled or enabled 1879** following this call. The second parameter may be a NULL pointer, in 1880** which case the trigger setting is not reported back. </dd> 1881** 1882** </dl> 1883*/ 1884#define SQLITE_DBCONFIG_LOOKASIDE 1001 /* void* int int */ 1885#define SQLITE_DBCONFIG_ENABLE_FKEY 1002 /* int int* */ 1886#define SQLITE_DBCONFIG_ENABLE_TRIGGER 1003 /* int int* */ 1887 1888 1889/* 1890** CAPI3REF: Enable Or Disable Extended Result Codes 1891** METHOD: sqlite3 1892** 1893** ^The sqlite3_extended_result_codes() routine enables or disables the 1894** [extended result codes] feature of SQLite. ^The extended result 1895** codes are disabled by default for historical compatibility. 1896*/ 1897int sqlite3_extended_result_codes(sqlite3*, int onoff); 1898 1899/* 1900** CAPI3REF: Last Insert Rowid 1901** METHOD: sqlite3 1902** 1903** ^Each entry in most SQLite tables (except for [WITHOUT ROWID] tables) 1904** has a unique 64-bit signed 1905** integer key called the [ROWID | "rowid"]. ^The rowid is always available 1906** as an undeclared column named ROWID, OID, or _ROWID_ as long as those 1907** names are not also used by explicitly declared columns. ^If 1908** the table has a column of type [INTEGER PRIMARY KEY] then that column 1909** is another alias for the rowid. 1910** 1911** ^The sqlite3_last_insert_rowid(D) interface returns the [rowid] of the 1912** most recent successful [INSERT] into a rowid table or [virtual table] 1913** on database connection D. 1914** ^Inserts into [WITHOUT ROWID] tables are not recorded. 1915** ^If no successful [INSERT]s into rowid tables 1916** have ever occurred on the database connection D, 1917** then sqlite3_last_insert_rowid(D) returns zero. 1918** 1919** ^(If an [INSERT] occurs within a trigger or within a [virtual table] 1920** method, then this routine will return the [rowid] of the inserted 1921** row as long as the trigger or virtual table method is running. 1922** But once the trigger or virtual table method ends, the value returned 1923** by this routine reverts to what it was before the trigger or virtual 1924** table method began.)^ 1925** 1926** ^An [INSERT] that fails due to a constraint violation is not a 1927** successful [INSERT] and does not change the value returned by this 1928** routine. ^Thus INSERT OR FAIL, INSERT OR IGNORE, INSERT OR ROLLBACK, 1929** and INSERT OR ABORT make no changes to the return value of this 1930** routine when their insertion fails. ^(When INSERT OR REPLACE 1931** encounters a constraint violation, it does not fail. The 1932** INSERT continues to completion after deleting rows that caused 1933** the constraint problem so INSERT OR REPLACE will always change 1934** the return value of this interface.)^ 1935** 1936** ^For the purposes of this routine, an [INSERT] is considered to 1937** be successful even if it is subsequently rolled back. 1938** 1939** This function is accessible to SQL statements via the 1940** [last_insert_rowid() SQL function]. 1941** 1942** If a separate thread performs a new [INSERT] on the same 1943** database connection while the [sqlite3_last_insert_rowid()] 1944** function is running and thus changes the last insert [rowid], 1945** then the value returned by [sqlite3_last_insert_rowid()] is 1946** unpredictable and might not equal either the old or the new 1947** last insert [rowid]. 1948*/ 1949sqlite3_int64 sqlite3_last_insert_rowid(sqlite3*); 1950 1951/* 1952** CAPI3REF: Count The Number Of Rows Modified 1953** METHOD: sqlite3 1954** 1955** ^This function returns the number of rows modified, inserted or 1956** deleted by the most recently completed INSERT, UPDATE or DELETE 1957** statement on the database connection specified by the only parameter. 1958** ^Executing any other type of SQL statement does not modify the value 1959** returned by this function. 1960** 1961** ^Only changes made directly by the INSERT, UPDATE or DELETE statement are 1962** considered - auxiliary changes caused by [CREATE TRIGGER | triggers], 1963** [foreign key actions] or [REPLACE] constraint resolution are not counted. 1964** 1965** Changes to a view that are intercepted by 1966** [INSTEAD OF trigger | INSTEAD OF triggers] are not counted. ^The value 1967** returned by sqlite3_changes() immediately after an INSERT, UPDATE or 1968** DELETE statement run on a view is always zero. Only changes made to real 1969** tables are counted. 1970** 1971** Things are more complicated if the sqlite3_changes() function is 1972** executed while a trigger program is running. This may happen if the 1973** program uses the [changes() SQL function], or if some other callback 1974** function invokes sqlite3_changes() directly. Essentially: 1975** 1976** <ul> 1977** <li> ^(Before entering a trigger program the value returned by 1978** sqlite3_changes() function is saved. After the trigger program 1979** has finished, the original value is restored.)^ 1980** 1981** <li> ^(Within a trigger program each INSERT, UPDATE and DELETE 1982** statement sets the value returned by sqlite3_changes() 1983** upon completion as normal. Of course, this value will not include 1984** any changes performed by sub-triggers, as the sqlite3_changes() 1985** value will be saved and restored after each sub-trigger has run.)^ 1986** </ul> 1987** 1988** ^This means that if the changes() SQL function (or similar) is used 1989** by the first INSERT, UPDATE or DELETE statement within a trigger, it 1990** returns the value as set when the calling statement began executing. 1991** ^If it is used by the second or subsequent such statement within a trigger 1992** program, the value returned reflects the number of rows modified by the 1993** previous INSERT, UPDATE or DELETE statement within the same trigger. 1994** 1995** See also the [sqlite3_total_changes()] interface, the 1996** [count_changes pragma], and the [changes() SQL function]. 1997** 1998** If a separate thread makes changes on the same database connection 1999** while [sqlite3_changes()] is running then the value returned 2000** is unpredictable and not meaningful. 2001*/ 2002int sqlite3_changes(sqlite3*); 2003 2004/* 2005** CAPI3REF: Total Number Of Rows Modified 2006** METHOD: sqlite3 2007** 2008** ^This function returns the total number of rows inserted, modified or 2009** deleted by all [INSERT], [UPDATE] or [DELETE] statements completed 2010** since the database connection was opened, including those executed as 2011** part of trigger programs. ^Executing any other type of SQL statement 2012** does not affect the value returned by sqlite3_total_changes(). 2013** 2014** ^Changes made as part of [foreign key actions] are included in the 2015** count, but those made as part of REPLACE constraint resolution are 2016** not. ^Changes to a view that are intercepted by INSTEAD OF triggers 2017** are not counted. 2018** 2019** See also the [sqlite3_changes()] interface, the 2020** [count_changes pragma], and the [total_changes() SQL function]. 2021** 2022** If a separate thread makes changes on the same database connection 2023** while [sqlite3_total_changes()] is running then the value 2024** returned is unpredictable and not meaningful. 2025*/ 2026int sqlite3_total_changes(sqlite3*); 2027 2028/* 2029** CAPI3REF: Interrupt A Long-Running Query 2030** METHOD: sqlite3 2031** 2032** ^This function causes any pending database operation to abort and 2033** return at its earliest opportunity. This routine is typically 2034** called in response to a user action such as pressing "Cancel" 2035** or Ctrl-C where the user wants a long query operation to halt 2036** immediately. 2037** 2038** ^It is safe to call this routine from a thread different from the 2039** thread that is currently running the database operation. But it 2040** is not safe to call this routine with a [database connection] that 2041** is closed or might close before sqlite3_interrupt() returns. 2042** 2043** ^If an SQL operation is very nearly finished at the time when 2044** sqlite3_interrupt() is called, then it might not have an opportunity 2045** to be interrupted and might continue to completion. 2046** 2047** ^An SQL operation that is interrupted will return [SQLITE_INTERRUPT]. 2048** ^If the interrupted SQL operation is an INSERT, UPDATE, or DELETE 2049** that is inside an explicit transaction, then the entire transaction 2050** will be rolled back automatically. 2051** 2052** ^The sqlite3_interrupt(D) call is in effect until all currently running 2053** SQL statements on [database connection] D complete. ^Any new SQL statements 2054** that are started after the sqlite3_interrupt() call and before the 2055** running statements reaches zero are interrupted as if they had been 2056** running prior to the sqlite3_interrupt() call. ^New SQL statements 2057** that are started after the running statement count reaches zero are 2058** not effected by the sqlite3_interrupt(). 2059** ^A call to sqlite3_interrupt(D) that occurs when there are no running 2060** SQL statements is a no-op and has no effect on SQL statements 2061** that are started after the sqlite3_interrupt() call returns. 2062** 2063** If the database connection closes while [sqlite3_interrupt()] 2064** is running then bad things will likely happen. 2065*/ 2066void sqlite3_interrupt(sqlite3*); 2067 2068/* 2069** CAPI3REF: Determine If An SQL Statement Is Complete 2070** 2071** These routines are useful during command-line input to determine if the 2072** currently entered text seems to form a complete SQL statement or 2073** if additional input is needed before sending the text into 2074** SQLite for parsing. ^These routines return 1 if the input string 2075** appears to be a complete SQL statement. ^A statement is judged to be 2076** complete if it ends with a semicolon token and is not a prefix of a 2077** well-formed CREATE TRIGGER statement. ^Semicolons that are embedded within 2078** string literals or quoted identifier names or comments are not 2079** independent tokens (they are part of the token in which they are 2080** embedded) and thus do not count as a statement terminator. ^Whitespace 2081** and comments that follow the final semicolon are ignored. 2082** 2083** ^These routines return 0 if the statement is incomplete. ^If a 2084** memory allocation fails, then SQLITE_NOMEM is returned. 2085** 2086** ^These routines do not parse the SQL statements thus 2087** will not detect syntactically incorrect SQL. 2088** 2089** ^(If SQLite has not been initialized using [sqlite3_initialize()] prior 2090** to invoking sqlite3_complete16() then sqlite3_initialize() is invoked 2091** automatically by sqlite3_complete16(). If that initialization fails, 2092** then the return value from sqlite3_complete16() will be non-zero 2093** regardless of whether or not the input SQL is complete.)^ 2094** 2095** The input to [sqlite3_complete()] must be a zero-terminated 2096** UTF-8 string. 2097** 2098** The input to [sqlite3_complete16()] must be a zero-terminated 2099** UTF-16 string in native byte order. 2100*/ 2101int sqlite3_complete(const char *sql); 2102int sqlite3_complete16(const void *sql); 2103 2104/* 2105** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors 2106** KEYWORDS: {busy-handler callback} {busy handler} 2107** METHOD: sqlite3 2108** 2109** ^The sqlite3_busy_handler(D,X,P) routine sets a callback function X 2110** that might be invoked with argument P whenever 2111** an attempt is made to access a database table associated with 2112** [database connection] D when another thread 2113** or process has the table locked. 2114** The sqlite3_busy_handler() interface is used to implement 2115** [sqlite3_busy_timeout()] and [PRAGMA busy_timeout]. 2116** 2117** ^If the busy callback is NULL, then [SQLITE_BUSY] 2118** is returned immediately upon encountering the lock. ^If the busy callback 2119** is not NULL, then the callback might be invoked with two arguments. 2120** 2121** ^The first argument to the busy handler is a copy of the void* pointer which 2122** is the third argument to sqlite3_busy_handler(). ^The second argument to 2123** the busy handler callback is the number of times that the busy handler has 2124** been invoked previously for the same locking event. ^If the 2125** busy callback returns 0, then no additional attempts are made to 2126** access the database and [SQLITE_BUSY] is returned 2127** to the application. 2128** ^If the callback returns non-zero, then another attempt 2129** is made to access the database and the cycle repeats. 2130** 2131** The presence of a busy handler does not guarantee that it will be invoked 2132** when there is lock contention. ^If SQLite determines that invoking the busy 2133** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY] 2134** to the application instead of invoking the 2135** busy handler. 2136** Consider a scenario where one process is holding a read lock that 2137** it is trying to promote to a reserved lock and 2138** a second process is holding a reserved lock that it is trying 2139** to promote to an exclusive lock. The first process cannot proceed 2140** because it is blocked by the second and the second process cannot 2141** proceed because it is blocked by the first. If both processes 2142** invoke the busy handlers, neither will make any progress. Therefore, 2143** SQLite returns [SQLITE_BUSY] for the first process, hoping that this 2144** will induce the first process to release its read lock and allow 2145** the second process to proceed. 2146** 2147** ^The default busy callback is NULL. 2148** 2149** ^(There can only be a single busy handler defined for each 2150** [database connection]. Setting a new busy handler clears any 2151** previously set handler.)^ ^Note that calling [sqlite3_busy_timeout()] 2152** or evaluating [PRAGMA busy_timeout=N] will change the 2153** busy handler and thus clear any previously set busy handler. 2154** 2155** The busy callback should not take any actions which modify the 2156** database connection that invoked the busy handler. In other words, 2157** the busy handler is not reentrant. Any such actions 2158** result in undefined behavior. 2159** 2160** A busy handler must not close the database connection 2161** or [prepared statement] that invoked the busy handler. 2162*/ 2163int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*); 2164 2165/* 2166** CAPI3REF: Set A Busy Timeout 2167** METHOD: sqlite3 2168** 2169** ^This routine sets a [sqlite3_busy_handler | busy handler] that sleeps 2170** for a specified amount of time when a table is locked. ^The handler 2171** will sleep multiple times until at least "ms" milliseconds of sleeping 2172** have accumulated. ^After at least "ms" milliseconds of sleeping, 2173** the handler returns 0 which causes [sqlite3_step()] to return 2174** [SQLITE_BUSY]. 2175** 2176** ^Calling this routine with an argument less than or equal to zero 2177** turns off all busy handlers. 2178** 2179** ^(There can only be a single busy handler for a particular 2180** [database connection] at any given moment. If another busy handler 2181** was defined (using [sqlite3_busy_handler()]) prior to calling 2182** this routine, that other busy handler is cleared.)^ 2183** 2184** See also: [PRAGMA busy_timeout] 2185*/ 2186int sqlite3_busy_timeout(sqlite3*, int ms); 2187 2188/* 2189** CAPI3REF: Convenience Routines For Running Queries 2190** METHOD: sqlite3 2191** 2192** This is a legacy interface that is preserved for backwards compatibility. 2193** Use of this interface is not recommended. 2194** 2195** Definition: A <b>result table</b> is memory data structure created by the 2196** [sqlite3_get_table()] interface. A result table records the 2197** complete query results from one or more queries. 2198** 2199** The table conceptually has a number of rows and columns. But 2200** these numbers are not part of the result table itself. These 2201** numbers are obtained separately. Let N be the number of rows 2202** and M be the number of columns. 2203** 2204** A result table is an array of pointers to zero-terminated UTF-8 strings. 2205** There are (N+1)*M elements in the array. The first M pointers point 2206** to zero-terminated strings that contain the names of the columns. 2207** The remaining entries all point to query results. NULL values result 2208** in NULL pointers. All other values are in their UTF-8 zero-terminated 2209** string representation as returned by [sqlite3_column_text()]. 2210** 2211** A result table might consist of one or more memory allocations. 2212** It is not safe to pass a result table directly to [sqlite3_free()]. 2213** A result table should be deallocated using [sqlite3_free_table()]. 2214** 2215** ^(As an example of the result table format, suppose a query result 2216** is as follows: 2217** 2218** <blockquote><pre> 2219** Name | Age 2220** ----------------------- 2221** Alice | 43 2222** Bob | 28 2223** Cindy | 21 2224** </pre></blockquote> 2225** 2226** There are two column (M==2) and three rows (N==3). Thus the 2227** result table has 8 entries. Suppose the result table is stored 2228** in an array names azResult. Then azResult holds this content: 2229** 2230** <blockquote><pre> 2231** azResult[0] = "Name"; 2232** azResult[1] = "Age"; 2233** azResult[2] = "Alice"; 2234** azResult[3] = "43"; 2235** azResult[4] = "Bob"; 2236** azResult[5] = "28"; 2237** azResult[6] = "Cindy"; 2238** azResult[7] = "21"; 2239** </pre></blockquote>)^ 2240** 2241** ^The sqlite3_get_table() function evaluates one or more 2242** semicolon-separated SQL statements in the zero-terminated UTF-8 2243** string of its 2nd parameter and returns a result table to the 2244** pointer given in its 3rd parameter. 2245** 2246** After the application has finished with the result from sqlite3_get_table(), 2247** it must pass the result table pointer to sqlite3_free_table() in order to 2248** release the memory that was malloced. Because of the way the 2249** [sqlite3_malloc()] happens within sqlite3_get_table(), the calling 2250** function must not try to call [sqlite3_free()] directly. Only 2251** [sqlite3_free_table()] is able to release the memory properly and safely. 2252** 2253** The sqlite3_get_table() interface is implemented as a wrapper around 2254** [sqlite3_exec()]. The sqlite3_get_table() routine does not have access 2255** to any internal data structures of SQLite. It uses only the public 2256** interface defined here. As a consequence, errors that occur in the 2257** wrapper layer outside of the internal [sqlite3_exec()] call are not 2258** reflected in subsequent calls to [sqlite3_errcode()] or 2259** [sqlite3_errmsg()]. 2260*/ 2261int sqlite3_get_table( 2262 sqlite3 *db, /* An open database */ 2263 const char *zSql, /* SQL to be evaluated */ 2264 char ***pazResult, /* Results of the query */ 2265 int *pnRow, /* Number of result rows written here */ 2266 int *pnColumn, /* Number of result columns written here */ 2267 char **pzErrmsg /* Error msg written here */ 2268); 2269void sqlite3_free_table(char **result); 2270 2271/* 2272** CAPI3REF: Formatted String Printing Functions 2273** 2274** These routines are work-alikes of the "printf()" family of functions 2275** from the standard C library. 2276** These routines understand most of the common K&R formatting options, 2277** plus some additional non-standard formats, detailed below. 2278** Note that some of the more obscure formatting options from recent 2279** C-library standards are omitted from this implementation. 2280** 2281** ^The sqlite3_mprintf() and sqlite3_vmprintf() routines write their 2282** results into memory obtained from [sqlite3_malloc()]. 2283** The strings returned by these two routines should be 2284** released by [sqlite3_free()]. ^Both routines return a 2285** NULL pointer if [sqlite3_malloc()] is unable to allocate enough 2286** memory to hold the resulting string. 2287** 2288** ^(The sqlite3_snprintf() routine is similar to "snprintf()" from 2289** the standard C library. The result is written into the 2290** buffer supplied as the second parameter whose size is given by 2291** the first parameter. Note that the order of the 2292** first two parameters is reversed from snprintf().)^ This is an 2293** historical accident that cannot be fixed without breaking 2294** backwards compatibility. ^(Note also that sqlite3_snprintf() 2295** returns a pointer to its buffer instead of the number of 2296** characters actually written into the buffer.)^ We admit that 2297** the number of characters written would be a more useful return 2298** value but we cannot change the implementation of sqlite3_snprintf() 2299** now without breaking compatibility. 2300** 2301** ^As long as the buffer size is greater than zero, sqlite3_snprintf() 2302** guarantees that the buffer is always zero-terminated. ^The first 2303** parameter "n" is the total size of the buffer, including space for 2304** the zero terminator. So the longest string that can be completely 2305** written will be n-1 characters. 2306** 2307** ^The sqlite3_vsnprintf() routine is a varargs version of sqlite3_snprintf(). 2308** 2309** These routines all implement some additional formatting 2310** options that are useful for constructing SQL statements. 2311** All of the usual printf() formatting options apply. In addition, there 2312** is are "%q", "%Q", "%w" and "%z" options. 2313** 2314** ^(The %q option works like %s in that it substitutes a nul-terminated 2315** string from the argument list. But %q also doubles every '\'' character. 2316** %q is designed for use inside a string literal.)^ By doubling each '\'' 2317** character it escapes that character and allows it to be inserted into 2318** the string. 2319** 2320** For example, assume the string variable zText contains text as follows: 2321** 2322** <blockquote><pre> 2323** char *zText = "It's a happy day!"; 2324** </pre></blockquote> 2325** 2326** One can use this text in an SQL statement as follows: 2327** 2328** <blockquote><pre> 2329** char *zSQL = sqlite3_mprintf("INSERT INTO table VALUES('%q')", zText); 2330** sqlite3_exec(db, zSQL, 0, 0, 0); 2331** sqlite3_free(zSQL); 2332** </pre></blockquote> 2333** 2334** Because the %q format string is used, the '\'' character in zText 2335** is escaped and the SQL generated is as follows: 2336** 2337** <blockquote><pre> 2338** INSERT INTO table1 VALUES('It''s a happy day!') 2339** </pre></blockquote> 2340** 2341** This is correct. Had we used %s instead of %q, the generated SQL 2342** would have looked like this: 2343** 2344** <blockquote><pre> 2345** INSERT INTO table1 VALUES('It's a happy day!'); 2346** </pre></blockquote> 2347** 2348** This second example is an SQL syntax error. As a general rule you should 2349** always use %q instead of %s when inserting text into a string literal. 2350** 2351** ^(The %Q option works like %q except it also adds single quotes around 2352** the outside of the total string. Additionally, if the parameter in the 2353** argument list is a NULL pointer, %Q substitutes the text "NULL" (without 2354** single quotes).)^ So, for example, one could say: 2355** 2356** <blockquote><pre> 2357** char *zSQL = sqlite3_mprintf("INSERT INTO table VALUES(%Q)", zText); 2358** sqlite3_exec(db, zSQL, 0, 0, 0); 2359** sqlite3_free(zSQL); 2360** </pre></blockquote> 2361** 2362** The code above will render a correct SQL statement in the zSQL 2363** variable even if the zText variable is a NULL pointer. 2364** 2365** ^(The "%w" formatting option is like "%q" except that it expects to 2366** be contained within double-quotes instead of single quotes, and it 2367** escapes the double-quote character instead of the single-quote 2368** character.)^ The "%w" formatting option is intended for safely inserting 2369** table and column names into a constructed SQL statement. 2370** 2371** ^(The "%z" formatting option works like "%s" but with the 2372** addition that after the string has been read and copied into 2373** the result, [sqlite3_free()] is called on the input string.)^ 2374*/ 2375char *sqlite3_mprintf(const char*,...); 2376char *sqlite3_vmprintf(const char*, va_list); 2377char *sqlite3_snprintf(int,char*,const char*, ...); 2378char *sqlite3_vsnprintf(int,char*,const char*, va_list); 2379 2380/* 2381** CAPI3REF: Memory Allocation Subsystem 2382** 2383** The SQLite core uses these three routines for all of its own 2384** internal memory allocation needs. "Core" in the previous sentence 2385** does not include operating-system specific VFS implementation. The 2386** Windows VFS uses native malloc() and free() for some operations. 2387** 2388** ^The sqlite3_malloc() routine returns a pointer to a block 2389** of memory at least N bytes in length, where N is the parameter. 2390** ^If sqlite3_malloc() is unable to obtain sufficient free 2391** memory, it returns a NULL pointer. ^If the parameter N to 2392** sqlite3_malloc() is zero or negative then sqlite3_malloc() returns 2393** a NULL pointer. 2394** 2395** ^The sqlite3_malloc64(N) routine works just like 2396** sqlite3_malloc(N) except that N is an unsigned 64-bit integer instead 2397** of a signed 32-bit integer. 2398** 2399** ^Calling sqlite3_free() with a pointer previously returned 2400** by sqlite3_malloc() or sqlite3_realloc() releases that memory so 2401** that it might be reused. ^The sqlite3_free() routine is 2402** a no-op if is called with a NULL pointer. Passing a NULL pointer 2403** to sqlite3_free() is harmless. After being freed, memory 2404** should neither be read nor written. Even reading previously freed 2405** memory might result in a segmentation fault or other severe error. 2406** Memory corruption, a segmentation fault, or other severe error 2407** might result if sqlite3_free() is called with a non-NULL pointer that 2408** was not obtained from sqlite3_malloc() or sqlite3_realloc(). 2409** 2410** ^The sqlite3_realloc(X,N) interface attempts to resize a 2411** prior memory allocation X to be at least N bytes. 2412** ^If the X parameter to sqlite3_realloc(X,N) 2413** is a NULL pointer then its behavior is identical to calling 2414** sqlite3_malloc(N). 2415** ^If the N parameter to sqlite3_realloc(X,N) is zero or 2416** negative then the behavior is exactly the same as calling 2417** sqlite3_free(X). 2418** ^sqlite3_realloc(X,N) returns a pointer to a memory allocation 2419** of at least N bytes in size or NULL if insufficient memory is available. 2420** ^If M is the size of the prior allocation, then min(N,M) bytes 2421** of the prior allocation are copied into the beginning of buffer returned 2422** by sqlite3_realloc(X,N) and the prior allocation is freed. 2423** ^If sqlite3_realloc(X,N) returns NULL and N is positive, then the 2424** prior allocation is not freed. 2425** 2426** ^The sqlite3_realloc64(X,N) interfaces works the same as 2427** sqlite3_realloc(X,N) except that N is a 64-bit unsigned integer instead 2428** of a 32-bit signed integer. 2429** 2430** ^If X is a memory allocation previously obtained from sqlite3_malloc(), 2431** sqlite3_malloc64(), sqlite3_realloc(), or sqlite3_realloc64(), then 2432** sqlite3_msize(X) returns the size of that memory allocation in bytes. 2433** ^The value returned by sqlite3_msize(X) might be larger than the number 2434** of bytes requested when X was allocated. ^If X is a NULL pointer then 2435** sqlite3_msize(X) returns zero. If X points to something that is not 2436** the beginning of memory allocation, or if it points to a formerly 2437** valid memory allocation that has now been freed, then the behavior 2438** of sqlite3_msize(X) is undefined and possibly harmful. 2439** 2440** ^The memory returned by sqlite3_malloc(), sqlite3_realloc(), 2441** sqlite3_malloc64(), and sqlite3_realloc64() 2442** is always aligned to at least an 8 byte boundary, or to a 2443** 4 byte boundary if the [SQLITE_4_BYTE_ALIGNED_MALLOC] compile-time 2444** option is used. 2445** 2446** In SQLite version 3.5.0 and 3.5.1, it was possible to define 2447** the SQLITE_OMIT_MEMORY_ALLOCATION which would cause the built-in 2448** implementation of these routines to be omitted. That capability 2449** is no longer provided. Only built-in memory allocators can be used. 2450** 2451** Prior to SQLite version 3.7.10, the Windows OS interface layer called 2452** the system malloc() and free() directly when converting 2453** filenames between the UTF-8 encoding used by SQLite 2454** and whatever filename encoding is used by the particular Windows 2455** installation. Memory allocation errors were detected, but 2456** they were reported back as [SQLITE_CANTOPEN] or 2457** [SQLITE_IOERR] rather than [SQLITE_NOMEM]. 2458** 2459** The pointer arguments to [sqlite3_free()] and [sqlite3_realloc()] 2460** must be either NULL or else pointers obtained from a prior 2461** invocation of [sqlite3_malloc()] or [sqlite3_realloc()] that have 2462** not yet been released. 2463** 2464** The application must not read or write any part of 2465** a block of memory after it has been released using 2466** [sqlite3_free()] or [sqlite3_realloc()]. 2467*/ 2468void *sqlite3_malloc(int); 2469void *sqlite3_malloc64(sqlite3_uint64); 2470void *sqlite3_realloc(void*, int); 2471void *sqlite3_realloc64(void*, sqlite3_uint64); 2472void sqlite3_free(void*); 2473sqlite3_uint64 sqlite3_msize(void*); 2474 2475/* 2476** CAPI3REF: Memory Allocator Statistics 2477** 2478** SQLite provides these two interfaces for reporting on the status 2479** of the [sqlite3_malloc()], [sqlite3_free()], and [sqlite3_realloc()] 2480** routines, which form the built-in memory allocation subsystem. 2481** 2482** ^The [sqlite3_memory_used()] routine returns the number of bytes 2483** of memory currently outstanding (malloced but not freed). 2484** ^The [sqlite3_memory_highwater()] routine returns the maximum 2485** value of [sqlite3_memory_used()] since the high-water mark 2486** was last reset. ^The values returned by [sqlite3_memory_used()] and 2487** [sqlite3_memory_highwater()] include any overhead 2488** added by SQLite in its implementation of [sqlite3_malloc()], 2489** but not overhead added by the any underlying system library 2490** routines that [sqlite3_malloc()] may call. 2491** 2492** ^The memory high-water mark is reset to the current value of 2493** [sqlite3_memory_used()] if and only if the parameter to 2494** [sqlite3_memory_highwater()] is true. ^The value returned 2495** by [sqlite3_memory_highwater(1)] is the high-water mark 2496** prior to the reset. 2497*/ 2498sqlite3_int64 sqlite3_memory_used(void); 2499sqlite3_int64 sqlite3_memory_highwater(int resetFlag); 2500 2501/* 2502** CAPI3REF: Pseudo-Random Number Generator 2503** 2504** SQLite contains a high-quality pseudo-random number generator (PRNG) used to 2505** select random [ROWID | ROWIDs] when inserting new records into a table that 2506** already uses the largest possible [ROWID]. The PRNG is also used for 2507** the build-in random() and randomblob() SQL functions. This interface allows 2508** applications to access the same PRNG for other purposes. 2509** 2510** ^A call to this routine stores N bytes of randomness into buffer P. 2511** ^The P parameter can be a NULL pointer. 2512** 2513** ^If this routine has not been previously called or if the previous 2514** call had N less than one or a NULL pointer for P, then the PRNG is 2515** seeded using randomness obtained from the xRandomness method of 2516** the default [sqlite3_vfs] object. 2517** ^If the previous call to this routine had an N of 1 or more and a 2518** non-NULL P then the pseudo-randomness is generated 2519** internally and without recourse to the [sqlite3_vfs] xRandomness 2520** method. 2521*/ 2522void sqlite3_randomness(int N, void *P); 2523 2524/* 2525** CAPI3REF: Compile-Time Authorization Callbacks 2526** METHOD: sqlite3 2527** 2528** ^This routine registers an authorizer callback with a particular 2529** [database connection], supplied in the first argument. 2530** ^The authorizer callback is invoked as SQL statements are being compiled 2531** by [sqlite3_prepare()] or its variants [sqlite3_prepare_v2()], 2532** [sqlite3_prepare16()] and [sqlite3_prepare16_v2()]. ^At various 2533** points during the compilation process, as logic is being created 2534** to perform various actions, the authorizer callback is invoked to 2535** see if those actions are allowed. ^The authorizer callback should 2536** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the 2537** specific action but allow the SQL statement to continue to be 2538** compiled, or [SQLITE_DENY] to cause the entire SQL statement to be 2539** rejected with an error. ^If the authorizer callback returns 2540** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY] 2541** then the [sqlite3_prepare_v2()] or equivalent call that triggered 2542** the authorizer will fail with an error message. 2543** 2544** When the callback returns [SQLITE_OK], that means the operation 2545** requested is ok. ^When the callback returns [SQLITE_DENY], the 2546** [sqlite3_prepare_v2()] or equivalent call that triggered the 2547** authorizer will fail with an error message explaining that 2548** access is denied. 2549** 2550** ^The first parameter to the authorizer callback is a copy of the third 2551** parameter to the sqlite3_set_authorizer() interface. ^The second parameter 2552** to the callback is an integer [SQLITE_COPY | action code] that specifies 2553** the particular action to be authorized. ^The third through sixth parameters 2554** to the callback are zero-terminated strings that contain additional 2555** details about the action to be authorized. 2556** 2557** ^If the action code is [SQLITE_READ] 2558** and the callback returns [SQLITE_IGNORE] then the 2559** [prepared statement] statement is constructed to substitute 2560** a NULL value in place of the table column that would have 2561** been read if [SQLITE_OK] had been returned. The [SQLITE_IGNORE] 2562** return can be used to deny an untrusted user access to individual 2563** columns of a table. 2564** ^If the action code is [SQLITE_DELETE] and the callback returns 2565** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the 2566** [truncate optimization] is disabled and all rows are deleted individually. 2567** 2568** An authorizer is used when [sqlite3_prepare | preparing] 2569** SQL statements from an untrusted source, to ensure that the SQL statements 2570** do not try to access data they are not allowed to see, or that they do not 2571** try to execute malicious statements that damage the database. For 2572** example, an application may allow a user to enter arbitrary 2573** SQL queries for evaluation by a database. But the application does 2574** not want the user to be able to make arbitrary changes to the 2575** database. An authorizer could then be put in place while the 2576** user-entered SQL is being [sqlite3_prepare | prepared] that 2577** disallows everything except [SELECT] statements. 2578** 2579** Applications that need to process SQL from untrusted sources 2580** might also consider lowering resource limits using [sqlite3_limit()] 2581** and limiting database size using the [max_page_count] [PRAGMA] 2582** in addition to using an authorizer. 2583** 2584** ^(Only a single authorizer can be in place on a database connection 2585** at a time. Each call to sqlite3_set_authorizer overrides the 2586** previous call.)^ ^Disable the authorizer by installing a NULL callback. 2587** The authorizer is disabled by default. 2588** 2589** The authorizer callback must not do anything that will modify 2590** the database connection that invoked the authorizer callback. 2591** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their 2592** database connections for the meaning of "modify" in this paragraph. 2593** 2594** ^When [sqlite3_prepare_v2()] is used to prepare a statement, the 2595** statement might be re-prepared during [sqlite3_step()] due to a 2596** schema change. Hence, the application should ensure that the 2597** correct authorizer callback remains in place during the [sqlite3_step()]. 2598** 2599** ^Note that the authorizer callback is invoked only during 2600** [sqlite3_prepare()] or its variants. Authorization is not 2601** performed during statement evaluation in [sqlite3_step()], unless 2602** as stated in the previous paragraph, sqlite3_step() invokes 2603** sqlite3_prepare_v2() to reprepare a statement after a schema change. 2604*/ 2605int sqlite3_set_authorizer( 2606 sqlite3*, 2607 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*), 2608 void *pUserData 2609); 2610 2611/* 2612** CAPI3REF: Authorizer Return Codes 2613** 2614** The [sqlite3_set_authorizer | authorizer callback function] must 2615** return either [SQLITE_OK] or one of these two constants in order 2616** to signal SQLite whether or not the action is permitted. See the 2617** [sqlite3_set_authorizer | authorizer documentation] for additional 2618** information. 2619** 2620** Note that SQLITE_IGNORE is also used as a [conflict resolution mode] 2621** returned from the [sqlite3_vtab_on_conflict()] interface. 2622*/ 2623#define SQLITE_DENY 1 /* Abort the SQL statement with an error */ 2624#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */ 2625 2626/* 2627** CAPI3REF: Authorizer Action Codes 2628** 2629** The [sqlite3_set_authorizer()] interface registers a callback function 2630** that is invoked to authorize certain SQL statement actions. The 2631** second parameter to the callback is an integer code that specifies 2632** what action is being authorized. These are the integer action codes that 2633** the authorizer callback may be passed. 2634** 2635** These action code values signify what kind of operation is to be 2636** authorized. The 3rd and 4th parameters to the authorization 2637** callback function will be parameters or NULL depending on which of these 2638** codes is used as the second parameter. ^(The 5th parameter to the 2639** authorizer callback is the name of the database ("main", "temp", 2640** etc.) if applicable.)^ ^The 6th parameter to the authorizer callback 2641** is the name of the inner-most trigger or view that is responsible for 2642** the access attempt or NULL if this access attempt is directly from 2643** top-level SQL code. 2644*/ 2645/******************************************* 3rd ************ 4th ***********/ 2646#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */ 2647#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */ 2648#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */ 2649#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */ 2650#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */ 2651#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */ 2652#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */ 2653#define SQLITE_CREATE_VIEW 8 /* View Name NULL */ 2654#define SQLITE_DELETE 9 /* Table Name NULL */ 2655#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */ 2656#define SQLITE_DROP_TABLE 11 /* Table Name NULL */ 2657#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */ 2658#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */ 2659#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */ 2660#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */ 2661#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */ 2662#define SQLITE_DROP_VIEW 17 /* View Name NULL */ 2663#define SQLITE_INSERT 18 /* Table Name NULL */ 2664#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */ 2665#define SQLITE_READ 20 /* Table Name Column Name */ 2666#define SQLITE_SELECT 21 /* NULL NULL */ 2667#define SQLITE_TRANSACTION 22 /* Operation NULL */ 2668#define SQLITE_UPDATE 23 /* Table Name Column Name */ 2669#define SQLITE_ATTACH 24 /* Filename NULL */ 2670#define SQLITE_DETACH 25 /* Database Name NULL */ 2671#define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */ 2672#define SQLITE_REINDEX 27 /* Index Name NULL */ 2673#define SQLITE_ANALYZE 28 /* Table Name NULL */ 2674#define SQLITE_CREATE_VTABLE 29 /* Table Name Module Name */ 2675#define SQLITE_DROP_VTABLE 30 /* Table Name Module Name */ 2676#define SQLITE_FUNCTION 31 /* NULL Function Name */ 2677#define SQLITE_SAVEPOINT 32 /* Operation Savepoint Name */ 2678#define SQLITE_COPY 0 /* No longer used */ 2679#define SQLITE_RECURSIVE 33 /* NULL NULL */ 2680 2681/* 2682** CAPI3REF: Tracing And Profiling Functions 2683** METHOD: sqlite3 2684** 2685** These routines register callback functions that can be used for 2686** tracing and profiling the execution of SQL statements. 2687** 2688** ^The callback function registered by sqlite3_trace() is invoked at 2689** various times when an SQL statement is being run by [sqlite3_step()]. 2690** ^The sqlite3_trace() callback is invoked with a UTF-8 rendering of the 2691** SQL statement text as the statement first begins executing. 2692** ^(Additional sqlite3_trace() callbacks might occur 2693** as each triggered subprogram is entered. The callbacks for triggers 2694** contain a UTF-8 SQL comment that identifies the trigger.)^ 2695** 2696** The [SQLITE_TRACE_SIZE_LIMIT] compile-time option can be used to limit 2697** the length of [bound parameter] expansion in the output of sqlite3_trace(). 2698** 2699** ^The callback function registered by sqlite3_profile() is invoked 2700** as each SQL statement finishes. ^The profile callback contains 2701** the original statement text and an estimate of wall-clock time 2702** of how long that statement took to run. ^The profile callback 2703** time is in units of nanoseconds, however the current implementation 2704** is only capable of millisecond resolution so the six least significant 2705** digits in the time are meaningless. Future versions of SQLite 2706** might provide greater resolution on the profiler callback. The 2707** sqlite3_profile() function is considered experimental and is 2708** subject to change in future versions of SQLite. 2709*/ 2710void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*); 2711SQLITE_EXPERIMENTAL void *sqlite3_profile(sqlite3*, 2712 void(*xProfile)(void*,const char*,sqlite3_uint64), void*); 2713 2714/* 2715** CAPI3REF: Query Progress Callbacks 2716** METHOD: sqlite3 2717** 2718** ^The sqlite3_progress_handler(D,N,X,P) interface causes the callback 2719** function X to be invoked periodically during long running calls to 2720** [sqlite3_exec()], [sqlite3_step()] and [sqlite3_get_table()] for 2721** database connection D. An example use for this 2722** interface is to keep a GUI updated during a large query. 2723** 2724** ^The parameter P is passed through as the only parameter to the 2725** callback function X. ^The parameter N is the approximate number of 2726** [virtual machine instructions] that are evaluated between successive 2727** invocations of the callback X. ^If N is less than one then the progress 2728** handler is disabled. 2729** 2730** ^Only a single progress handler may be defined at one time per 2731** [database connection]; setting a new progress handler cancels the 2732** old one. ^Setting parameter X to NULL disables the progress handler. 2733** ^The progress handler is also disabled by setting N to a value less 2734** than 1. 2735** 2736** ^If the progress callback returns non-zero, the operation is 2737** interrupted. This feature can be used to implement a 2738** "Cancel" button on a GUI progress dialog box. 2739** 2740** The progress handler callback must not do anything that will modify 2741** the database connection that invoked the progress handler. 2742** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their 2743** database connections for the meaning of "modify" in this paragraph. 2744** 2745*/ 2746void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*); 2747 2748/* 2749** CAPI3REF: Opening A New Database Connection 2750** CONSTRUCTOR: sqlite3 2751** 2752** ^These routines open an SQLite database file as specified by the 2753** filename argument. ^The filename argument is interpreted as UTF-8 for 2754** sqlite3_open() and sqlite3_open_v2() and as UTF-16 in the native byte 2755** order for sqlite3_open16(). ^(A [database connection] handle is usually 2756** returned in *ppDb, even if an error occurs. The only exception is that 2757** if SQLite is unable to allocate memory to hold the [sqlite3] object, 2758** a NULL will be written into *ppDb instead of a pointer to the [sqlite3] 2759** object.)^ ^(If the database is opened (and/or created) successfully, then 2760** [SQLITE_OK] is returned. Otherwise an [error code] is returned.)^ ^The 2761** [sqlite3_errmsg()] or [sqlite3_errmsg16()] routines can be used to obtain 2762** an English language description of the error following a failure of any 2763** of the sqlite3_open() routines. 2764** 2765** ^The default encoding will be UTF-8 for databases created using 2766** sqlite3_open() or sqlite3_open_v2(). ^The default encoding for databases 2767** created using sqlite3_open16() will be UTF-16 in the native byte order. 2768** 2769** Whether or not an error occurs when it is opened, resources 2770** associated with the [database connection] handle should be released by 2771** passing it to [sqlite3_close()] when it is no longer required. 2772** 2773** The sqlite3_open_v2() interface works like sqlite3_open() 2774** except that it accepts two additional parameters for additional control 2775** over the new database connection. ^(The flags parameter to 2776** sqlite3_open_v2() can take one of 2777** the following three values, optionally combined with the 2778** [SQLITE_OPEN_NOMUTEX], [SQLITE_OPEN_FULLMUTEX], [SQLITE_OPEN_SHAREDCACHE], 2779** [SQLITE_OPEN_PRIVATECACHE], and/or [SQLITE_OPEN_URI] flags:)^ 2780** 2781** <dl> 2782** ^(<dt>[SQLITE_OPEN_READONLY]</dt> 2783** <dd>The database is opened in read-only mode. If the database does not 2784** already exist, an error is returned.</dd>)^ 2785** 2786** ^(<dt>[SQLITE_OPEN_READWRITE]</dt> 2787** <dd>The database is opened for reading and writing if possible, or reading 2788** only if the file is write protected by the operating system. In either 2789** case the database must already exist, otherwise an error is returned.</dd>)^ 2790** 2791** ^(<dt>[SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE]</dt> 2792** <dd>The database is opened for reading and writing, and is created if 2793** it does not already exist. This is the behavior that is always used for 2794** sqlite3_open() and sqlite3_open16().</dd>)^ 2795** </dl> 2796** 2797** If the 3rd parameter to sqlite3_open_v2() is not one of the 2798** combinations shown above optionally combined with other 2799** [SQLITE_OPEN_READONLY | SQLITE_OPEN_* bits] 2800** then the behavior is undefined. 2801** 2802** ^If the [SQLITE_OPEN_NOMUTEX] flag is set, then the database connection 2803** opens in the multi-thread [threading mode] as long as the single-thread 2804** mode has not been set at compile-time or start-time. ^If the 2805** [SQLITE_OPEN_FULLMUTEX] flag is set then the database connection opens 2806** in the serialized [threading mode] unless single-thread was 2807** previously selected at compile-time or start-time. 2808** ^The [SQLITE_OPEN_SHAREDCACHE] flag causes the database connection to be 2809** eligible to use [shared cache mode], regardless of whether or not shared 2810** cache is enabled using [sqlite3_enable_shared_cache()]. ^The 2811** [SQLITE_OPEN_PRIVATECACHE] flag causes the database connection to not 2812** participate in [shared cache mode] even if it is enabled. 2813** 2814** ^The fourth parameter to sqlite3_open_v2() is the name of the 2815** [sqlite3_vfs] object that defines the operating system interface that 2816** the new database connection should use. ^If the fourth parameter is 2817** a NULL pointer then the default [sqlite3_vfs] object is used. 2818** 2819** ^If the filename is ":memory:", then a private, temporary in-memory database 2820** is created for the connection. ^This in-memory database will vanish when 2821** the database connection is closed. Future versions of SQLite might 2822** make use of additional special filenames that begin with the ":" character. 2823** It is recommended that when a database filename actually does begin with 2824** a ":" character you should prefix the filename with a pathname such as 2825** "./" to avoid ambiguity. 2826** 2827** ^If the filename is an empty string, then a private, temporary 2828** on-disk database will be created. ^This private database will be 2829** automatically deleted as soon as the database connection is closed. 2830** 2831** [[URI filenames in sqlite3_open()]] <h3>URI Filenames</h3> 2832** 2833** ^If [URI filename] interpretation is enabled, and the filename argument 2834** begins with "file:", then the filename is interpreted as a URI. ^URI 2835** filename interpretation is enabled if the [SQLITE_OPEN_URI] flag is 2836** set in the fourth argument to sqlite3_open_v2(), or if it has 2837** been enabled globally using the [SQLITE_CONFIG_URI] option with the 2838** [sqlite3_config()] method or by the [SQLITE_USE_URI] compile-time option. 2839** As of SQLite version 3.7.7, URI filename interpretation is turned off 2840** by default, but future releases of SQLite might enable URI filename 2841** interpretation by default. See "[URI filenames]" for additional 2842** information. 2843** 2844** URI filenames are parsed according to RFC 3986. ^If the URI contains an 2845** authority, then it must be either an empty string or the string 2846** "localhost". ^If the authority is not an empty string or "localhost", an 2847** error is returned to the caller. ^The fragment component of a URI, if 2848** present, is ignored. 2849** 2850** ^SQLite uses the path component of the URI as the name of the disk file 2851** which contains the database. ^If the path begins with a '/' character, 2852** then it is interpreted as an absolute path. ^If the path does not begin 2853** with a '/' (meaning that the authority section is omitted from the URI) 2854** then the path is interpreted as a relative path. 2855** ^(On windows, the first component of an absolute path 2856** is a drive specification (e.g. "C:").)^ 2857** 2858** [[core URI query parameters]] 2859** The query component of a URI may contain parameters that are interpreted 2860** either by SQLite itself, or by a [VFS | custom VFS implementation]. 2861** SQLite and its built-in [VFSes] interpret the 2862** following query parameters: 2863** 2864** <ul> 2865** <li> <b>vfs</b>: ^The "vfs" parameter may be used to specify the name of 2866** a VFS object that provides the operating system interface that should 2867** be used to access the database file on disk. ^If this option is set to 2868** an empty string the default VFS object is used. ^Specifying an unknown 2869** VFS is an error. ^If sqlite3_open_v2() is used and the vfs option is 2870** present, then the VFS specified by the option takes precedence over 2871** the value passed as the fourth parameter to sqlite3_open_v2(). 2872** 2873** <li> <b>mode</b>: ^(The mode parameter may be set to either "ro", "rw", 2874** "rwc", or "memory". Attempting to set it to any other value is 2875** an error)^. 2876** ^If "ro" is specified, then the database is opened for read-only 2877** access, just as if the [SQLITE_OPEN_READONLY] flag had been set in the 2878** third argument to sqlite3_open_v2(). ^If the mode option is set to 2879** "rw", then the database is opened for read-write (but not create) 2880** access, as if SQLITE_OPEN_READWRITE (but not SQLITE_OPEN_CREATE) had 2881** been set. ^Value "rwc" is equivalent to setting both 2882** SQLITE_OPEN_READWRITE and SQLITE_OPEN_CREATE. ^If the mode option is 2883** set to "memory" then a pure [in-memory database] that never reads 2884** or writes from disk is used. ^It is an error to specify a value for 2885** the mode parameter that is less restrictive than that specified by 2886** the flags passed in the third parameter to sqlite3_open_v2(). 2887** 2888** <li> <b>cache</b>: ^The cache parameter may be set to either "shared" or 2889** "private". ^Setting it to "shared" is equivalent to setting the 2890** SQLITE_OPEN_SHAREDCACHE bit in the flags argument passed to 2891** sqlite3_open_v2(). ^Setting the cache parameter to "private" is 2892** equivalent to setting the SQLITE_OPEN_PRIVATECACHE bit. 2893** ^If sqlite3_open_v2() is used and the "cache" parameter is present in 2894** a URI filename, its value overrides any behavior requested by setting 2895** SQLITE_OPEN_PRIVATECACHE or SQLITE_OPEN_SHAREDCACHE flag. 2896** 2897** <li> <b>psow</b>: ^The psow parameter indicates whether or not the 2898** [powersafe overwrite] property does or does not apply to the 2899** storage media on which the database file resides. 2900** 2901** <li> <b>nolock</b>: ^The nolock parameter is a boolean query parameter 2902** which if set disables file locking in rollback journal modes. This 2903** is useful for accessing a database on a filesystem that does not 2904** support locking. Caution: Database corruption might result if two 2905** or more processes write to the same database and any one of those 2906** processes uses nolock=1. 2907** 2908** <li> <b>immutable</b>: ^The immutable parameter is a boolean query 2909** parameter that indicates that the database file is stored on 2910** read-only media. ^When immutable is set, SQLite assumes that the 2911** database file cannot be changed, even by a process with higher 2912** privilege, and so the database is opened read-only and all locking 2913** and change detection is disabled. Caution: Setting the immutable 2914** property on a database file that does in fact change can result 2915** in incorrect query results and/or [SQLITE_CORRUPT] errors. 2916** See also: [SQLITE_IOCAP_IMMUTABLE]. 2917** 2918** </ul> 2919** 2920** ^Specifying an unknown parameter in the query component of a URI is not an 2921** error. Future versions of SQLite might understand additional query 2922** parameters. See "[query parameters with special meaning to SQLite]" for 2923** additional information. 2924** 2925** [[URI filename examples]] <h3>URI filename examples</h3> 2926** 2927** <table border="1" align=center cellpadding=5> 2928** <tr><th> URI filenames <th> Results 2929** <tr><td> file:data.db <td> 2930** Open the file "data.db" in the current directory. 2931** <tr><td> file:/home/fred/data.db<br> 2932** file:///home/fred/data.db <br> 2933** file://localhost/home/fred/data.db <br> <td> 2934** Open the database file "/home/fred/data.db". 2935** <tr><td> file://darkstar/home/fred/data.db <td> 2936** An error. "darkstar" is not a recognized authority. 2937** <tr><td style="white-space:nowrap"> 2938** file:///C:/Documents%20and%20Settings/fred/Desktop/data.db 2939** <td> Windows only: Open the file "data.db" on fred's desktop on drive 2940** C:. Note that the %20 escaping in this example is not strictly 2941** necessary - space characters can be used literally 2942** in URI filenames. 2943** <tr><td> file:data.db?mode=ro&cache=private <td> 2944** Open file "data.db" in the current directory for read-only access. 2945** Regardless of whether or not shared-cache mode is enabled by 2946** default, use a private cache. 2947** <tr><td> file:/home/fred/data.db?vfs=unix-dotfile <td> 2948** Open file "/home/fred/data.db". Use the special VFS "unix-dotfile" 2949** that uses dot-files in place of posix advisory locking. 2950** <tr><td> file:data.db?mode=readonly <td> 2951** An error. "readonly" is not a valid option for the "mode" parameter. 2952** </table> 2953** 2954** ^URI hexadecimal escape sequences (%HH) are supported within the path and 2955** query components of a URI. A hexadecimal escape sequence consists of a 2956** percent sign - "%" - followed by exactly two hexadecimal digits 2957** specifying an octet value. ^Before the path or query components of a 2958** URI filename are interpreted, they are encoded using UTF-8 and all 2959** hexadecimal escape sequences replaced by a single byte containing the 2960** corresponding octet. If this process generates an invalid UTF-8 encoding, 2961** the results are undefined. 2962** 2963** <b>Note to Windows users:</b> The encoding used for the filename argument 2964** of sqlite3_open() and sqlite3_open_v2() must be UTF-8, not whatever 2965** codepage is currently defined. Filenames containing international 2966** characters must be converted to UTF-8 prior to passing them into 2967** sqlite3_open() or sqlite3_open_v2(). 2968** 2969** <b>Note to Windows Runtime users:</b> The temporary directory must be set 2970** prior to calling sqlite3_open() or sqlite3_open_v2(). Otherwise, various 2971** features that require the use of temporary files may fail. 2972** 2973** See also: [sqlite3_temp_directory] 2974*/ 2975int sqlite3_open( 2976 const char *filename, /* Database filename (UTF-8) */ 2977 sqlite3 **ppDb /* OUT: SQLite db handle */ 2978); 2979int sqlite3_open16( 2980 const void *filename, /* Database filename (UTF-16) */ 2981 sqlite3 **ppDb /* OUT: SQLite db handle */ 2982); 2983int sqlite3_open_v2( 2984 const char *filename, /* Database filename (UTF-8) */ 2985 sqlite3 **ppDb, /* OUT: SQLite db handle */ 2986 int flags, /* Flags */ 2987 const char *zVfs /* Name of VFS module to use */ 2988); 2989 2990/* 2991** CAPI3REF: Obtain Values For URI Parameters 2992** 2993** These are utility routines, useful to VFS implementations, that check 2994** to see if a database file was a URI that contained a specific query 2995** parameter, and if so obtains the value of that query parameter. 2996** 2997** If F is the database filename pointer passed into the xOpen() method of 2998** a VFS implementation when the flags parameter to xOpen() has one or 2999** more of the [SQLITE_OPEN_URI] or [SQLITE_OPEN_MAIN_DB] bits set and 3000** P is the name of the query parameter, then 3001** sqlite3_uri_parameter(F,P) returns the value of the P 3002** parameter if it exists or a NULL pointer if P does not appear as a 3003** query parameter on F. If P is a query parameter of F 3004** has no explicit value, then sqlite3_uri_parameter(F,P) returns 3005** a pointer to an empty string. 3006** 3007** The sqlite3_uri_boolean(F,P,B) routine assumes that P is a boolean 3008** parameter and returns true (1) or false (0) according to the value 3009** of P. The sqlite3_uri_boolean(F,P,B) routine returns true (1) if the 3010** value of query parameter P is one of "yes", "true", or "on" in any 3011** case or if the value begins with a non-zero number. The 3012** sqlite3_uri_boolean(F,P,B) routines returns false (0) if the value of 3013** query parameter P is one of "no", "false", or "off" in any case or 3014** if the value begins with a numeric zero. If P is not a query 3015** parameter on F or if the value of P is does not match any of the 3016** above, then sqlite3_uri_boolean(F,P,B) returns (B!=0). 3017** 3018** The sqlite3_uri_int64(F,P,D) routine converts the value of P into a 3019** 64-bit signed integer and returns that integer, or D if P does not 3020** exist. If the value of P is something other than an integer, then 3021** zero is returned. 3022** 3023** If F is a NULL pointer, then sqlite3_uri_parameter(F,P) returns NULL and 3024** sqlite3_uri_boolean(F,P,B) returns B. If F is not a NULL pointer and 3025** is not a database file pathname pointer that SQLite passed into the xOpen 3026** VFS method, then the behavior of this routine is undefined and probably 3027** undesirable. 3028*/ 3029const char *sqlite3_uri_parameter(const char *zFilename, const char *zParam); 3030int sqlite3_uri_boolean(const char *zFile, const char *zParam, int bDefault); 3031sqlite3_int64 sqlite3_uri_int64(const char*, const char*, sqlite3_int64); 3032 3033 3034/* 3035** CAPI3REF: Error Codes And Messages 3036** METHOD: sqlite3 3037** 3038** ^If the most recent sqlite3_* API call associated with 3039** [database connection] D failed, then the sqlite3_errcode(D) interface 3040** returns the numeric [result code] or [extended result code] for that 3041** API call. 3042** If the most recent API call was successful, 3043** then the return value from sqlite3_errcode() is undefined. 3044** ^The sqlite3_extended_errcode() 3045** interface is the same except that it always returns the 3046** [extended result code] even when extended result codes are 3047** disabled. 3048** 3049** ^The sqlite3_errmsg() and sqlite3_errmsg16() return English-language 3050** text that describes the error, as either UTF-8 or UTF-16 respectively. 3051** ^(Memory to hold the error message string is managed internally. 3052** The application does not need to worry about freeing the result. 3053** However, the error string might be overwritten or deallocated by 3054** subsequent calls to other SQLite interface functions.)^ 3055** 3056** ^The sqlite3_errstr() interface returns the English-language text 3057** that describes the [result code], as UTF-8. 3058** ^(Memory to hold the error message string is managed internally 3059** and must not be freed by the application)^. 3060** 3061** When the serialized [threading mode] is in use, it might be the 3062** case that a second error occurs on a separate thread in between 3063** the time of the first error and the call to these interfaces. 3064** When that happens, the second error will be reported since these 3065** interfaces always report the most recent result. To avoid 3066** this, each thread can obtain exclusive use of the [database connection] D 3067** by invoking [sqlite3_mutex_enter]([sqlite3_db_mutex](D)) before beginning 3068** to use D and invoking [sqlite3_mutex_leave]([sqlite3_db_mutex](D)) after 3069** all calls to the interfaces listed here are completed. 3070** 3071** If an interface fails with SQLITE_MISUSE, that means the interface 3072** was invoked incorrectly by the application. In that case, the 3073** error code and message may or may not be set. 3074*/ 3075int sqlite3_errcode(sqlite3 *db); 3076int sqlite3_extended_errcode(sqlite3 *db); 3077const char *sqlite3_errmsg(sqlite3*); 3078const void *sqlite3_errmsg16(sqlite3*); 3079const char *sqlite3_errstr(int); 3080 3081/* 3082** CAPI3REF: Prepared Statement Object 3083** KEYWORDS: {prepared statement} {prepared statements} 3084** 3085** An instance of this object represents a single SQL statement that 3086** has been compiled into binary form and is ready to be evaluated. 3087** 3088** Think of each SQL statement as a separate computer program. The 3089** original SQL text is source code. A prepared statement object 3090** is the compiled object code. All SQL must be converted into a 3091** prepared statement before it can be run. 3092** 3093** The life-cycle of a prepared statement object usually goes like this: 3094** 3095** <ol> 3096** <li> Create the prepared statement object using [sqlite3_prepare_v2()]. 3097** <li> Bind values to [parameters] using the sqlite3_bind_*() 3098** interfaces. 3099** <li> Run the SQL by calling [sqlite3_step()] one or more times. 3100** <li> Reset the prepared statement using [sqlite3_reset()] then go back 3101** to step 2. Do this zero or more times. 3102** <li> Destroy the object using [sqlite3_finalize()]. 3103** </ol> 3104*/ 3105typedef struct sqlite3_stmt sqlite3_stmt; 3106 3107/* 3108** CAPI3REF: Run-time Limits 3109** METHOD: sqlite3 3110** 3111** ^(This interface allows the size of various constructs to be limited 3112** on a connection by connection basis. The first parameter is the 3113** [database connection] whose limit is to be set or queried. The 3114** second parameter is one of the [limit categories] that define a 3115** class of constructs to be size limited. The third parameter is the 3116** new limit for that construct.)^ 3117** 3118** ^If the new limit is a negative number, the limit is unchanged. 3119** ^(For each limit category SQLITE_LIMIT_<i>NAME</i> there is a 3120** [limits | hard upper bound] 3121** set at compile-time by a C preprocessor macro called 3122** [limits | SQLITE_MAX_<i>NAME</i>]. 3123** (The "_LIMIT_" in the name is changed to "_MAX_".))^ 3124** ^Attempts to increase a limit above its hard upper bound are 3125** silently truncated to the hard upper bound. 3126** 3127** ^Regardless of whether or not the limit was changed, the 3128** [sqlite3_limit()] interface returns the prior value of the limit. 3129** ^Hence, to find the current value of a limit without changing it, 3130** simply invoke this interface with the third parameter set to -1. 3131** 3132** Run-time limits are intended for use in applications that manage 3133** both their own internal database and also databases that are controlled 3134** by untrusted external sources. An example application might be a 3135** web browser that has its own databases for storing history and 3136** separate databases controlled by JavaScript applications downloaded 3137** off the Internet. The internal databases can be given the 3138** large, default limits. Databases managed by external sources can 3139** be given much smaller limits designed to prevent a denial of service 3140** attack. Developers might also want to use the [sqlite3_set_authorizer()] 3141** interface to further control untrusted SQL. The size of the database 3142** created by an untrusted script can be contained using the 3143** [max_page_count] [PRAGMA]. 3144** 3145** New run-time limit categories may be added in future releases. 3146*/ 3147int sqlite3_limit(sqlite3*, int id, int newVal); 3148 3149/* 3150** CAPI3REF: Run-Time Limit Categories 3151** KEYWORDS: {limit category} {*limit categories} 3152** 3153** These constants define various performance limits 3154** that can be lowered at run-time using [sqlite3_limit()]. 3155** The synopsis of the meanings of the various limits is shown below. 3156** Additional information is available at [limits | Limits in SQLite]. 3157** 3158** <dl> 3159** [[SQLITE_LIMIT_LENGTH]] ^(<dt>SQLITE_LIMIT_LENGTH</dt> 3160** <dd>The maximum size of any string or BLOB or table row, in bytes.<dd>)^ 3161** 3162** [[SQLITE_LIMIT_SQL_LENGTH]] ^(<dt>SQLITE_LIMIT_SQL_LENGTH</dt> 3163** <dd>The maximum length of an SQL statement, in bytes.</dd>)^ 3164** 3165** [[SQLITE_LIMIT_COLUMN]] ^(<dt>SQLITE_LIMIT_COLUMN</dt> 3166** <dd>The maximum number of columns in a table definition or in the 3167** result set of a [SELECT] or the maximum number of columns in an index 3168** or in an ORDER BY or GROUP BY clause.</dd>)^ 3169** 3170** [[SQLITE_LIMIT_EXPR_DEPTH]] ^(<dt>SQLITE_LIMIT_EXPR_DEPTH</dt> 3171** <dd>The maximum depth of the parse tree on any expression.</dd>)^ 3172** 3173** [[SQLITE_LIMIT_COMPOUND_SELECT]] ^(<dt>SQLITE_LIMIT_COMPOUND_SELECT</dt> 3174** <dd>The maximum number of terms in a compound SELECT statement.</dd>)^ 3175** 3176** [[SQLITE_LIMIT_VDBE_OP]] ^(<dt>SQLITE_LIMIT_VDBE_OP</dt> 3177** <dd>The maximum number of instructions in a virtual machine program 3178** used to implement an SQL statement. This limit is not currently 3179** enforced, though that might be added in some future release of 3180** SQLite.</dd>)^ 3181** 3182** [[SQLITE_LIMIT_FUNCTION_ARG]] ^(<dt>SQLITE_LIMIT_FUNCTION_ARG</dt> 3183** <dd>The maximum number of arguments on a function.</dd>)^ 3184** 3185** [[SQLITE_LIMIT_ATTACHED]] ^(<dt>SQLITE_LIMIT_ATTACHED</dt> 3186** <dd>The maximum number of [ATTACH | attached databases].)^</dd> 3187** 3188** [[SQLITE_LIMIT_LIKE_PATTERN_LENGTH]] 3189** ^(<dt>SQLITE_LIMIT_LIKE_PATTERN_LENGTH</dt> 3190** <dd>The maximum length of the pattern argument to the [LIKE] or 3191** [GLOB] operators.</dd>)^ 3192** 3193** [[SQLITE_LIMIT_VARIABLE_NUMBER]] 3194** ^(<dt>SQLITE_LIMIT_VARIABLE_NUMBER</dt> 3195** <dd>The maximum index number of any [parameter] in an SQL statement.)^ 3196** 3197** [[SQLITE_LIMIT_TRIGGER_DEPTH]] ^(<dt>SQLITE_LIMIT_TRIGGER_DEPTH</dt> 3198** <dd>The maximum depth of recursion for triggers.</dd>)^ 3199** 3200** [[SQLITE_LIMIT_WORKER_THREADS]] ^(<dt>SQLITE_LIMIT_WORKER_THREADS</dt> 3201** <dd>The maximum number of auxiliary worker threads that a single 3202** [prepared statement] may start.</dd>)^ 3203** </dl> 3204*/ 3205#define SQLITE_LIMIT_LENGTH 0 3206#define SQLITE_LIMIT_SQL_LENGTH 1 3207#define SQLITE_LIMIT_COLUMN 2 3208#define SQLITE_LIMIT_EXPR_DEPTH 3 3209#define SQLITE_LIMIT_COMPOUND_SELECT 4 3210#define SQLITE_LIMIT_VDBE_OP 5 3211#define SQLITE_LIMIT_FUNCTION_ARG 6 3212#define SQLITE_LIMIT_ATTACHED 7 3213#define SQLITE_LIMIT_LIKE_PATTERN_LENGTH 8 3214#define SQLITE_LIMIT_VARIABLE_NUMBER 9 3215#define SQLITE_LIMIT_TRIGGER_DEPTH 10 3216#define SQLITE_LIMIT_WORKER_THREADS 11 3217 3218/* 3219** CAPI3REF: Compiling An SQL Statement 3220** KEYWORDS: {SQL statement compiler} 3221** METHOD: sqlite3 3222** CONSTRUCTOR: sqlite3_stmt 3223** 3224** To execute an SQL query, it must first be compiled into a byte-code 3225** program using one of these routines. 3226** 3227** The first argument, "db", is a [database connection] obtained from a 3228** prior successful call to [sqlite3_open()], [sqlite3_open_v2()] or 3229** [sqlite3_open16()]. The database connection must not have been closed. 3230** 3231** The second argument, "zSql", is the statement to be compiled, encoded 3232** as either UTF-8 or UTF-16. The sqlite3_prepare() and sqlite3_prepare_v2() 3233** interfaces use UTF-8, and sqlite3_prepare16() and sqlite3_prepare16_v2() 3234** use UTF-16. 3235** 3236** ^If the nByte argument is negative, then zSql is read up to the 3237** first zero terminator. ^If nByte is positive, then it is the 3238** number of bytes read from zSql. ^If nByte is zero, then no prepared 3239** statement is generated. 3240** If the caller knows that the supplied string is nul-terminated, then 3241** there is a small performance advantage to passing an nByte parameter that 3242** is the number of bytes in the input string <i>including</i> 3243** the nul-terminator. 3244** 3245** ^If pzTail is not NULL then *pzTail is made to point to the first byte 3246** past the end of the first SQL statement in zSql. These routines only 3247** compile the first statement in zSql, so *pzTail is left pointing to 3248** what remains uncompiled. 3249** 3250** ^*ppStmt is left pointing to a compiled [prepared statement] that can be 3251** executed using [sqlite3_step()]. ^If there is an error, *ppStmt is set 3252** to NULL. ^If the input text contains no SQL (if the input is an empty 3253** string or a comment) then *ppStmt is set to NULL. 3254** The calling procedure is responsible for deleting the compiled 3255** SQL statement using [sqlite3_finalize()] after it has finished with it. 3256** ppStmt may not be NULL. 3257** 3258** ^On success, the sqlite3_prepare() family of routines return [SQLITE_OK]; 3259** otherwise an [error code] is returned. 3260** 3261** The sqlite3_prepare_v2() and sqlite3_prepare16_v2() interfaces are 3262** recommended for all new programs. The two older interfaces are retained 3263** for backwards compatibility, but their use is discouraged. 3264** ^In the "v2" interfaces, the prepared statement 3265** that is returned (the [sqlite3_stmt] object) contains a copy of the 3266** original SQL text. This causes the [sqlite3_step()] interface to 3267** behave differently in three ways: 3268** 3269** <ol> 3270** <li> 3271** ^If the database schema changes, instead of returning [SQLITE_SCHEMA] as it 3272** always used to do, [sqlite3_step()] will automatically recompile the SQL 3273** statement and try to run it again. As many as [SQLITE_MAX_SCHEMA_RETRY] 3274** retries will occur before sqlite3_step() gives up and returns an error. 3275** </li> 3276** 3277** <li> 3278** ^When an error occurs, [sqlite3_step()] will return one of the detailed 3279** [error codes] or [extended error codes]. ^The legacy behavior was that 3280** [sqlite3_step()] would only return a generic [SQLITE_ERROR] result code 3281** and the application would have to make a second call to [sqlite3_reset()] 3282** in order to find the underlying cause of the problem. With the "v2" prepare 3283** interfaces, the underlying reason for the error is returned immediately. 3284** </li> 3285** 3286** <li> 3287** ^If the specific value bound to [parameter | host parameter] in the 3288** WHERE clause might influence the choice of query plan for a statement, 3289** then the statement will be automatically recompiled, as if there had been 3290** a schema change, on the first [sqlite3_step()] call following any change 3291** to the [sqlite3_bind_text | bindings] of that [parameter]. 3292** ^The specific value of WHERE-clause [parameter] might influence the 3293** choice of query plan if the parameter is the left-hand side of a [LIKE] 3294** or [GLOB] operator or if the parameter is compared to an indexed column 3295** and the [SQLITE_ENABLE_STAT3] compile-time option is enabled. 3296** </li> 3297** </ol> 3298*/ 3299int sqlite3_prepare( 3300 sqlite3 *db, /* Database handle */ 3301 const char *zSql, /* SQL statement, UTF-8 encoded */ 3302 int nByte, /* Maximum length of zSql in bytes. */ 3303 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 3304 const char **pzTail /* OUT: Pointer to unused portion of zSql */ 3305); 3306int sqlite3_prepare_v2( 3307 sqlite3 *db, /* Database handle */ 3308 const char *zSql, /* SQL statement, UTF-8 encoded */ 3309 int nByte, /* Maximum length of zSql in bytes. */ 3310 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 3311 const char **pzTail /* OUT: Pointer to unused portion of zSql */ 3312); 3313int sqlite3_prepare16( 3314 sqlite3 *db, /* Database handle */ 3315 const void *zSql, /* SQL statement, UTF-16 encoded */ 3316 int nByte, /* Maximum length of zSql in bytes. */ 3317 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 3318 const void **pzTail /* OUT: Pointer to unused portion of zSql */ 3319); 3320int sqlite3_prepare16_v2( 3321 sqlite3 *db, /* Database handle */ 3322 const void *zSql, /* SQL statement, UTF-16 encoded */ 3323 int nByte, /* Maximum length of zSql in bytes. */ 3324 sqlite3_stmt **ppStmt, /* OUT: Statement handle */ 3325 const void **pzTail /* OUT: Pointer to unused portion of zSql */ 3326); 3327 3328/* 3329** CAPI3REF: Retrieving Statement SQL 3330** METHOD: sqlite3_stmt 3331** 3332** ^This interface can be used to retrieve a saved copy of the original 3333** SQL text used to create a [prepared statement] if that statement was 3334** compiled using either [sqlite3_prepare_v2()] or [sqlite3_prepare16_v2()]. 3335*/ 3336const char *sqlite3_sql(sqlite3_stmt *pStmt); 3337 3338/* 3339** CAPI3REF: Determine If An SQL Statement Writes The Database 3340** METHOD: sqlite3_stmt 3341** 3342** ^The sqlite3_stmt_readonly(X) interface returns true (non-zero) if 3343** and only if the [prepared statement] X makes no direct changes to 3344** the content of the database file. 3345** 3346** Note that [application-defined SQL functions] or 3347** [virtual tables] might change the database indirectly as a side effect. 3348** ^(For example, if an application defines a function "eval()" that 3349** calls [sqlite3_exec()], then the following SQL statement would 3350** change the database file through side-effects: 3351** 3352** <blockquote><pre> 3353** SELECT eval('DELETE FROM t1') FROM t2; 3354** </pre></blockquote> 3355** 3356** But because the [SELECT] statement does not change the database file 3357** directly, sqlite3_stmt_readonly() would still return true.)^ 3358** 3359** ^Transaction control statements such as [BEGIN], [COMMIT], [ROLLBACK], 3360** [SAVEPOINT], and [RELEASE] cause sqlite3_stmt_readonly() to return true, 3361** since the statements themselves do not actually modify the database but 3362** rather they control the timing of when other statements modify the 3363** database. ^The [ATTACH] and [DETACH] statements also cause 3364** sqlite3_stmt_readonly() to return true since, while those statements 3365** change the configuration of a database connection, they do not make 3366** changes to the content of the database files on disk. 3367*/ 3368int sqlite3_stmt_readonly(sqlite3_stmt *pStmt); 3369 3370/* 3371** CAPI3REF: Determine If A Prepared Statement Has Been Reset 3372** METHOD: sqlite3_stmt 3373** 3374** ^The sqlite3_stmt_busy(S) interface returns true (non-zero) if the 3375** [prepared statement] S has been stepped at least once using 3376** [sqlite3_step(S)] but has not run to completion and/or has not 3377** been reset using [sqlite3_reset(S)]. ^The sqlite3_stmt_busy(S) 3378** interface returns false if S is a NULL pointer. If S is not a 3379** NULL pointer and is not a pointer to a valid [prepared statement] 3380** object, then the behavior is undefined and probably undesirable. 3381** 3382** This interface can be used in combination [sqlite3_next_stmt()] 3383** to locate all prepared statements associated with a database 3384** connection that are in need of being reset. This can be used, 3385** for example, in diagnostic routines to search for prepared 3386** statements that are holding a transaction open. 3387*/ 3388int sqlite3_stmt_busy(sqlite3_stmt*); 3389 3390/* 3391** CAPI3REF: Dynamically Typed Value Object 3392** KEYWORDS: {protected sqlite3_value} {unprotected sqlite3_value} 3393** 3394** SQLite uses the sqlite3_value object to represent all values 3395** that can be stored in a database table. SQLite uses dynamic typing 3396** for the values it stores. ^Values stored in sqlite3_value objects 3397** can be integers, floating point values, strings, BLOBs, or NULL. 3398** 3399** An sqlite3_value object may be either "protected" or "unprotected". 3400** Some interfaces require a protected sqlite3_value. Other interfaces 3401** will accept either a protected or an unprotected sqlite3_value. 3402** Every interface that accepts sqlite3_value arguments specifies 3403** whether or not it requires a protected sqlite3_value. The 3404** [sqlite3_value_dup()] interface can be used to construct a new 3405** protected sqlite3_value from an unprotected sqlite3_value. 3406** 3407** The terms "protected" and "unprotected" refer to whether or not 3408** a mutex is held. An internal mutex is held for a protected 3409** sqlite3_value object but no mutex is held for an unprotected 3410** sqlite3_value object. If SQLite is compiled to be single-threaded 3411** (with [SQLITE_THREADSAFE=0] and with [sqlite3_threadsafe()] returning 0) 3412** or if SQLite is run in one of reduced mutex modes 3413** [SQLITE_CONFIG_SINGLETHREAD] or [SQLITE_CONFIG_MULTITHREAD] 3414** then there is no distinction between protected and unprotected 3415** sqlite3_value objects and they can be used interchangeably. However, 3416** for maximum code portability it is recommended that applications 3417** still make the distinction between protected and unprotected 3418** sqlite3_value objects even when not strictly required. 3419** 3420** ^The sqlite3_value objects that are passed as parameters into the 3421** implementation of [application-defined SQL functions] are protected. 3422** ^The sqlite3_value object returned by 3423** [sqlite3_column_value()] is unprotected. 3424** Unprotected sqlite3_value objects may only be used with 3425** [sqlite3_result_value()] and [sqlite3_bind_value()]. 3426** The [sqlite3_value_blob | sqlite3_value_type()] family of 3427** interfaces require protected sqlite3_value objects. 3428*/ 3429typedef struct Mem sqlite3_value; 3430 3431/* 3432** CAPI3REF: SQL Function Context Object 3433** 3434** The context in which an SQL function executes is stored in an 3435** sqlite3_context object. ^A pointer to an sqlite3_context object 3436** is always first parameter to [application-defined SQL functions]. 3437** The application-defined SQL function implementation will pass this 3438** pointer through into calls to [sqlite3_result_int | sqlite3_result()], 3439** [sqlite3_aggregate_context()], [sqlite3_user_data()], 3440** [sqlite3_context_db_handle()], [sqlite3_get_auxdata()], 3441** and/or [sqlite3_set_auxdata()]. 3442*/ 3443typedef struct sqlite3_context sqlite3_context; 3444 3445/* 3446** CAPI3REF: Binding Values To Prepared Statements 3447** KEYWORDS: {host parameter} {host parameters} {host parameter name} 3448** KEYWORDS: {SQL parameter} {SQL parameters} {parameter binding} 3449** METHOD: sqlite3_stmt 3450** 3451** ^(In the SQL statement text input to [sqlite3_prepare_v2()] and its variants, 3452** literals may be replaced by a [parameter] that matches one of following 3453** templates: 3454** 3455** <ul> 3456** <li> ? 3457** <li> ?NNN 3458** <li> :VVV 3459** <li> @VVV 3460** <li> $VVV 3461** </ul> 3462** 3463** In the templates above, NNN represents an integer literal, 3464** and VVV represents an alphanumeric identifier.)^ ^The values of these 3465** parameters (also called "host parameter names" or "SQL parameters") 3466** can be set using the sqlite3_bind_*() routines defined here. 3467** 3468** ^The first argument to the sqlite3_bind_*() routines is always 3469** a pointer to the [sqlite3_stmt] object returned from 3470** [sqlite3_prepare_v2()] or its variants. 3471** 3472** ^The second argument is the index of the SQL parameter to be set. 3473** ^The leftmost SQL parameter has an index of 1. ^When the same named 3474** SQL parameter is used more than once, second and subsequent 3475** occurrences have the same index as the first occurrence. 3476** ^The index for named parameters can be looked up using the 3477** [sqlite3_bind_parameter_index()] API if desired. ^The index 3478** for "?NNN" parameters is the value of NNN. 3479** ^The NNN value must be between 1 and the [sqlite3_limit()] 3480** parameter [SQLITE_LIMIT_VARIABLE_NUMBER] (default value: 999). 3481** 3482** ^The third argument is the value to bind to the parameter. 3483** ^If the third parameter to sqlite3_bind_text() or sqlite3_bind_text16() 3484** or sqlite3_bind_blob() is a NULL pointer then the fourth parameter 3485** is ignored and the end result is the same as sqlite3_bind_null(). 3486** 3487** ^(In those routines that have a fourth argument, its value is the 3488** number of bytes in the parameter. To be clear: the value is the 3489** number of <u>bytes</u> in the value, not the number of characters.)^ 3490** ^If the fourth parameter to sqlite3_bind_text() or sqlite3_bind_text16() 3491** is negative, then the length of the string is 3492** the number of bytes up to the first zero terminator. 3493** If the fourth parameter to sqlite3_bind_blob() is negative, then 3494** the behavior is undefined. 3495** If a non-negative fourth parameter is provided to sqlite3_bind_text() 3496** or sqlite3_bind_text16() or sqlite3_bind_text64() then 3497** that parameter must be the byte offset 3498** where the NUL terminator would occur assuming the string were NUL 3499** terminated. If any NUL characters occur at byte offsets less than 3500** the value of the fourth parameter then the resulting string value will 3501** contain embedded NULs. The result of expressions involving strings 3502** with embedded NULs is undefined. 3503** 3504** ^The fifth argument to the BLOB and string binding interfaces 3505** is a destructor used to dispose of the BLOB or 3506** string after SQLite has finished with it. ^The destructor is called 3507** to dispose of the BLOB or string even if the call to bind API fails. 3508** ^If the fifth argument is 3509** the special value [SQLITE_STATIC], then SQLite assumes that the 3510** information is in static, unmanaged space and does not need to be freed. 3511** ^If the fifth argument has the value [SQLITE_TRANSIENT], then 3512** SQLite makes its own private copy of the data immediately, before 3513** the sqlite3_bind_*() routine returns. 3514** 3515** ^The sixth argument to sqlite3_bind_text64() must be one of 3516** [SQLITE_UTF8], [SQLITE_UTF16], [SQLITE_UTF16BE], or [SQLITE_UTF16LE] 3517** to specify the encoding of the text in the third parameter. If 3518** the sixth argument to sqlite3_bind_text64() is not one of the 3519** allowed values shown above, or if the text encoding is different 3520** from the encoding specified by the sixth parameter, then the behavior 3521** is undefined. 3522** 3523** ^The sqlite3_bind_zeroblob() routine binds a BLOB of length N that 3524** is filled with zeroes. ^A zeroblob uses a fixed amount of memory 3525** (just an integer to hold its size) while it is being processed. 3526** Zeroblobs are intended to serve as placeholders for BLOBs whose 3527** content is later written using 3528** [sqlite3_blob_open | incremental BLOB I/O] routines. 3529** ^A negative value for the zeroblob results in a zero-length BLOB. 3530** 3531** ^If any of the sqlite3_bind_*() routines are called with a NULL pointer 3532** for the [prepared statement] or with a prepared statement for which 3533** [sqlite3_step()] has been called more recently than [sqlite3_reset()], 3534** then the call will return [SQLITE_MISUSE]. If any sqlite3_bind_() 3535** routine is passed a [prepared statement] that has been finalized, the 3536** result is undefined and probably harmful. 3537** 3538** ^Bindings are not cleared by the [sqlite3_reset()] routine. 3539** ^Unbound parameters are interpreted as NULL. 3540** 3541** ^The sqlite3_bind_* routines return [SQLITE_OK] on success or an 3542** [error code] if anything goes wrong. 3543** ^[SQLITE_TOOBIG] might be returned if the size of a string or BLOB 3544** exceeds limits imposed by [sqlite3_limit]([SQLITE_LIMIT_LENGTH]) or 3545** [SQLITE_MAX_LENGTH]. 3546** ^[SQLITE_RANGE] is returned if the parameter 3547** index is out of range. ^[SQLITE_NOMEM] is returned if malloc() fails. 3548** 3549** See also: [sqlite3_bind_parameter_count()], 3550** [sqlite3_bind_parameter_name()], and [sqlite3_bind_parameter_index()]. 3551*/ 3552int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*)); 3553int sqlite3_bind_blob64(sqlite3_stmt*, int, const void*, sqlite3_uint64, 3554 void(*)(void*)); 3555int sqlite3_bind_double(sqlite3_stmt*, int, double); 3556int sqlite3_bind_int(sqlite3_stmt*, int, int); 3557int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite3_int64); 3558int sqlite3_bind_null(sqlite3_stmt*, int); 3559int sqlite3_bind_text(sqlite3_stmt*,int,const char*,int,void(*)(void*)); 3560int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*)); 3561int sqlite3_bind_text64(sqlite3_stmt*, int, const char*, sqlite3_uint64, 3562 void(*)(void*), unsigned char encoding); 3563int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*); 3564int sqlite3_bind_zeroblob(sqlite3_stmt*, int, int n); 3565 3566/* 3567** CAPI3REF: Number Of SQL Parameters 3568** METHOD: sqlite3_stmt 3569** 3570** ^This routine can be used to find the number of [SQL parameters] 3571** in a [prepared statement]. SQL parameters are tokens of the 3572** form "?", "?NNN", ":AAA", "$AAA", or "@AAA" that serve as 3573** placeholders for values that are [sqlite3_bind_blob | bound] 3574** to the parameters at a later time. 3575** 3576** ^(This routine actually returns the index of the largest (rightmost) 3577** parameter. For all forms except ?NNN, this will correspond to the 3578** number of unique parameters. If parameters of the ?NNN form are used, 3579** there may be gaps in the list.)^ 3580** 3581** See also: [sqlite3_bind_blob|sqlite3_bind()], 3582** [sqlite3_bind_parameter_name()], and 3583** [sqlite3_bind_parameter_index()]. 3584*/ 3585int sqlite3_bind_parameter_count(sqlite3_stmt*); 3586 3587/* 3588** CAPI3REF: Name Of A Host Parameter 3589** METHOD: sqlite3_stmt 3590** 3591** ^The sqlite3_bind_parameter_name(P,N) interface returns 3592** the name of the N-th [SQL parameter] in the [prepared statement] P. 3593** ^(SQL parameters of the form "?NNN" or ":AAA" or "@AAA" or "$AAA" 3594** have a name which is the string "?NNN" or ":AAA" or "@AAA" or "$AAA" 3595** respectively. 3596** In other words, the initial ":" or "$" or "@" or "?" 3597** is included as part of the name.)^ 3598** ^Parameters of the form "?" without a following integer have no name 3599** and are referred to as "nameless" or "anonymous parameters". 3600** 3601** ^The first host parameter has an index of 1, not 0. 3602** 3603** ^If the value N is out of range or if the N-th parameter is 3604** nameless, then NULL is returned. ^The returned string is 3605** always in UTF-8 encoding even if the named parameter was 3606** originally specified as UTF-16 in [sqlite3_prepare16()] or 3607** [sqlite3_prepare16_v2()]. 3608** 3609** See also: [sqlite3_bind_blob|sqlite3_bind()], 3610** [sqlite3_bind_parameter_count()], and 3611** [sqlite3_bind_parameter_index()]. 3612*/ 3613const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int); 3614 3615/* 3616** CAPI3REF: Index Of A Parameter With A Given Name 3617** METHOD: sqlite3_stmt 3618** 3619** ^Return the index of an SQL parameter given its name. ^The 3620** index value returned is suitable for use as the second 3621** parameter to [sqlite3_bind_blob|sqlite3_bind()]. ^A zero 3622** is returned if no matching parameter is found. ^The parameter 3623** name must be given in UTF-8 even if the original statement 3624** was prepared from UTF-16 text using [sqlite3_prepare16_v2()]. 3625** 3626** See also: [sqlite3_bind_blob|sqlite3_bind()], 3627** [sqlite3_bind_parameter_count()], and 3628** [sqlite3_bind_parameter_index()]. 3629*/ 3630int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName); 3631 3632/* 3633** CAPI3REF: Reset All Bindings On A Prepared Statement 3634** METHOD: sqlite3_stmt 3635** 3636** ^Contrary to the intuition of many, [sqlite3_reset()] does not reset 3637** the [sqlite3_bind_blob | bindings] on a [prepared statement]. 3638** ^Use this routine to reset all host parameters to NULL. 3639*/ 3640int sqlite3_clear_bindings(sqlite3_stmt*); 3641 3642/* 3643** CAPI3REF: Number Of Columns In A Result Set 3644** METHOD: sqlite3_stmt 3645** 3646** ^Return the number of columns in the result set returned by the 3647** [prepared statement]. ^This routine returns 0 if pStmt is an SQL 3648** statement that does not return data (for example an [UPDATE]). 3649** 3650** See also: [sqlite3_data_count()] 3651*/ 3652int sqlite3_column_count(sqlite3_stmt *pStmt); 3653 3654/* 3655** CAPI3REF: Column Names In A Result Set 3656** METHOD: sqlite3_stmt 3657** 3658** ^These routines return the name assigned to a particular column 3659** in the result set of a [SELECT] statement. ^The sqlite3_column_name() 3660** interface returns a pointer to a zero-terminated UTF-8 string 3661** and sqlite3_column_name16() returns a pointer to a zero-terminated 3662** UTF-16 string. ^The first parameter is the [prepared statement] 3663** that implements the [SELECT] statement. ^The second parameter is the 3664** column number. ^The leftmost column is number 0. 3665** 3666** ^The returned string pointer is valid until either the [prepared statement] 3667** is destroyed by [sqlite3_finalize()] or until the statement is automatically 3668** reprepared by the first call to [sqlite3_step()] for a particular run 3669** or until the next call to 3670** sqlite3_column_name() or sqlite3_column_name16() on the same column. 3671** 3672** ^If sqlite3_malloc() fails during the processing of either routine 3673** (for example during a conversion from UTF-8 to UTF-16) then a 3674** NULL pointer is returned. 3675** 3676** ^The name of a result column is the value of the "AS" clause for 3677** that column, if there is an AS clause. If there is no AS clause 3678** then the name of the column is unspecified and may change from 3679** one release of SQLite to the next. 3680*/ 3681const char *sqlite3_column_name(sqlite3_stmt*, int N); 3682const void *sqlite3_column_name16(sqlite3_stmt*, int N); 3683 3684/* 3685** CAPI3REF: Source Of Data In A Query Result 3686** METHOD: sqlite3_stmt 3687** 3688** ^These routines provide a means to determine the database, table, and 3689** table column that is the origin of a particular result column in 3690** [SELECT] statement. 3691** ^The name of the database or table or column can be returned as 3692** either a UTF-8 or UTF-16 string. ^The _database_ routines return 3693** the database name, the _table_ routines return the table name, and 3694** the origin_ routines return the column name. 3695** ^The returned string is valid until the [prepared statement] is destroyed 3696** using [sqlite3_finalize()] or until the statement is automatically 3697** reprepared by the first call to [sqlite3_step()] for a particular run 3698** or until the same information is requested 3699** again in a different encoding. 3700** 3701** ^The names returned are the original un-aliased names of the 3702** database, table, and column. 3703** 3704** ^The first argument to these interfaces is a [prepared statement]. 3705** ^These functions return information about the Nth result column returned by 3706** the statement, where N is the second function argument. 3707** ^The left-most column is column 0 for these routines. 3708** 3709** ^If the Nth column returned by the statement is an expression or 3710** subquery and is not a column value, then all of these functions return 3711** NULL. ^These routine might also return NULL if a memory allocation error 3712** occurs. ^Otherwise, they return the name of the attached database, table, 3713** or column that query result column was extracted from. 3714** 3715** ^As with all other SQLite APIs, those whose names end with "16" return 3716** UTF-16 encoded strings and the other functions return UTF-8. 3717** 3718** ^These APIs are only available if the library was compiled with the 3719** [SQLITE_ENABLE_COLUMN_METADATA] C-preprocessor symbol. 3720** 3721** If two or more threads call one or more of these routines against the same 3722** prepared statement and column at the same time then the results are 3723** undefined. 3724** 3725** If two or more threads call one or more 3726** [sqlite3_column_database_name | column metadata interfaces] 3727** for the same [prepared statement] and result column 3728** at the same time then the results are undefined. 3729*/ 3730const char *sqlite3_column_database_name(sqlite3_stmt*,int); 3731const void *sqlite3_column_database_name16(sqlite3_stmt*,int); 3732const char *sqlite3_column_table_name(sqlite3_stmt*,int); 3733const void *sqlite3_column_table_name16(sqlite3_stmt*,int); 3734const char *sqlite3_column_origin_name(sqlite3_stmt*,int); 3735const void *sqlite3_column_origin_name16(sqlite3_stmt*,int); 3736 3737/* 3738** CAPI3REF: Declared Datatype Of A Query Result 3739** METHOD: sqlite3_stmt 3740** 3741** ^(The first parameter is a [prepared statement]. 3742** If this statement is a [SELECT] statement and the Nth column of the 3743** returned result set of that [SELECT] is a table column (not an 3744** expression or subquery) then the declared type of the table 3745** column is returned.)^ ^If the Nth column of the result set is an 3746** expression or subquery, then a NULL pointer is returned. 3747** ^The returned string is always UTF-8 encoded. 3748** 3749** ^(For example, given the database schema: 3750** 3751** CREATE TABLE t1(c1 VARIANT); 3752** 3753** and the following statement to be compiled: 3754** 3755** SELECT c1 + 1, c1 FROM t1; 3756** 3757** this routine would return the string "VARIANT" for the second result 3758** column (i==1), and a NULL pointer for the first result column (i==0).)^ 3759** 3760** ^SQLite uses dynamic run-time typing. ^So just because a column 3761** is declared to contain a particular type does not mean that the 3762** data stored in that column is of the declared type. SQLite is 3763** strongly typed, but the typing is dynamic not static. ^Type 3764** is associated with individual values, not with the containers 3765** used to hold those values. 3766*/ 3767const char *sqlite3_column_decltype(sqlite3_stmt*,int); 3768const void *sqlite3_column_decltype16(sqlite3_stmt*,int); 3769 3770/* 3771** CAPI3REF: Evaluate An SQL Statement 3772** METHOD: sqlite3_stmt 3773** 3774** After a [prepared statement] has been prepared using either 3775** [sqlite3_prepare_v2()] or [sqlite3_prepare16_v2()] or one of the legacy 3776** interfaces [sqlite3_prepare()] or [sqlite3_prepare16()], this function 3777** must be called one or more times to evaluate the statement. 3778** 3779** The details of the behavior of the sqlite3_step() interface depend 3780** on whether the statement was prepared using the newer "v2" interface 3781** [sqlite3_prepare_v2()] and [sqlite3_prepare16_v2()] or the older legacy 3782** interface [sqlite3_prepare()] and [sqlite3_prepare16()]. The use of the 3783** new "v2" interface is recommended for new applications but the legacy 3784** interface will continue to be supported. 3785** 3786** ^In the legacy interface, the return value will be either [SQLITE_BUSY], 3787** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE]. 3788** ^With the "v2" interface, any of the other [result codes] or 3789** [extended result codes] might be returned as well. 3790** 3791** ^[SQLITE_BUSY] means that the database engine was unable to acquire the 3792** database locks it needs to do its job. ^If the statement is a [COMMIT] 3793** or occurs outside of an explicit transaction, then you can retry the 3794** statement. If the statement is not a [COMMIT] and occurs within an 3795** explicit transaction then you should rollback the transaction before 3796** continuing. 3797** 3798** ^[SQLITE_DONE] means that the statement has finished executing 3799** successfully. sqlite3_step() should not be called again on this virtual 3800** machine without first calling [sqlite3_reset()] to reset the virtual 3801** machine back to its initial state. 3802** 3803** ^If the SQL statement being executed returns any data, then [SQLITE_ROW] 3804** is returned each time a new row of data is ready for processing by the 3805** caller. The values may be accessed using the [column access functions]. 3806** sqlite3_step() is called again to retrieve the next row of data. 3807** 3808** ^[SQLITE_ERROR] means that a run-time error (such as a constraint 3809** violation) has occurred. sqlite3_step() should not be called again on 3810** the VM. More information may be found by calling [sqlite3_errmsg()]. 3811** ^With the legacy interface, a more specific error code (for example, 3812** [SQLITE_INTERRUPT], [SQLITE_SCHEMA], [SQLITE_CORRUPT], and so forth) 3813** can be obtained by calling [sqlite3_reset()] on the 3814** [prepared statement]. ^In the "v2" interface, 3815** the more specific error code is returned directly by sqlite3_step(). 3816** 3817** [SQLITE_MISUSE] means that the this routine was called inappropriately. 3818** Perhaps it was called on a [prepared statement] that has 3819** already been [sqlite3_finalize | finalized] or on one that had 3820** previously returned [SQLITE_ERROR] or [SQLITE_DONE]. Or it could 3821** be the case that the same database connection is being used by two or 3822** more threads at the same moment in time. 3823** 3824** For all versions of SQLite up to and including 3.6.23.1, a call to 3825** [sqlite3_reset()] was required after sqlite3_step() returned anything 3826** other than [SQLITE_ROW] before any subsequent invocation of 3827** sqlite3_step(). Failure to reset the prepared statement using 3828** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from 3829** sqlite3_step(). But after version 3.6.23.1, sqlite3_step() began 3830** calling [sqlite3_reset()] automatically in this circumstance rather 3831** than returning [SQLITE_MISUSE]. This is not considered a compatibility 3832** break because any application that ever receives an SQLITE_MISUSE error 3833** is broken by definition. The [SQLITE_OMIT_AUTORESET] compile-time option 3834** can be used to restore the legacy behavior. 3835** 3836** <b>Goofy Interface Alert:</b> In the legacy interface, the sqlite3_step() 3837** API always returns a generic error code, [SQLITE_ERROR], following any 3838** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call 3839** [sqlite3_reset()] or [sqlite3_finalize()] in order to find one of the 3840** specific [error codes] that better describes the error. 3841** We admit that this is a goofy design. The problem has been fixed 3842** with the "v2" interface. If you prepare all of your SQL statements 3843** using either [sqlite3_prepare_v2()] or [sqlite3_prepare16_v2()] instead 3844** of the legacy [sqlite3_prepare()] and [sqlite3_prepare16()] interfaces, 3845** then the more specific [error codes] are returned directly 3846** by sqlite3_step(). The use of the "v2" interface is recommended. 3847*/ 3848int sqlite3_step(sqlite3_stmt*); 3849 3850/* 3851** CAPI3REF: Number of columns in a result set 3852** METHOD: sqlite3_stmt 3853** 3854** ^The sqlite3_data_count(P) interface returns the number of columns in the 3855** current row of the result set of [prepared statement] P. 3856** ^If prepared statement P does not have results ready to return 3857** (via calls to the [sqlite3_column_int | sqlite3_column_*()] of 3858** interfaces) then sqlite3_data_count(P) returns 0. 3859** ^The sqlite3_data_count(P) routine also returns 0 if P is a NULL pointer. 3860** ^The sqlite3_data_count(P) routine returns 0 if the previous call to 3861** [sqlite3_step](P) returned [SQLITE_DONE]. ^The sqlite3_data_count(P) 3862** will return non-zero if previous call to [sqlite3_step](P) returned 3863** [SQLITE_ROW], except in the case of the [PRAGMA incremental_vacuum] 3864** where it always returns zero since each step of that multi-step 3865** pragma returns 0 columns of data. 3866** 3867** See also: [sqlite3_column_count()] 3868*/ 3869int sqlite3_data_count(sqlite3_stmt *pStmt); 3870 3871/* 3872** CAPI3REF: Fundamental Datatypes 3873** KEYWORDS: SQLITE_TEXT 3874** 3875** ^(Every value in SQLite has one of five fundamental datatypes: 3876** 3877** <ul> 3878** <li> 64-bit signed integer 3879** <li> 64-bit IEEE floating point number 3880** <li> string 3881** <li> BLOB 3882** <li> NULL 3883** </ul>)^ 3884** 3885** These constants are codes for each of those types. 3886** 3887** Note that the SQLITE_TEXT constant was also used in SQLite version 2 3888** for a completely different meaning. Software that links against both 3889** SQLite version 2 and SQLite version 3 should use SQLITE3_TEXT, not 3890** SQLITE_TEXT. 3891*/ 3892#define SQLITE_INTEGER 1 3893#define SQLITE_FLOAT 2 3894#define SQLITE_BLOB 4 3895#define SQLITE_NULL 5 3896#ifdef SQLITE_TEXT 3897# undef SQLITE_TEXT 3898#else 3899# define SQLITE_TEXT 3 3900#endif 3901#define SQLITE3_TEXT 3 3902 3903/* 3904** CAPI3REF: Result Values From A Query 3905** KEYWORDS: {column access functions} 3906** METHOD: sqlite3_stmt 3907** 3908** ^These routines return information about a single column of the current 3909** result row of a query. ^In every case the first argument is a pointer 3910** to the [prepared statement] that is being evaluated (the [sqlite3_stmt*] 3911** that was returned from [sqlite3_prepare_v2()] or one of its variants) 3912** and the second argument is the index of the column for which information 3913** should be returned. ^The leftmost column of the result set has the index 0. 3914** ^The number of columns in the result can be determined using 3915** [sqlite3_column_count()]. 3916** 3917** If the SQL statement does not currently point to a valid row, or if the 3918** column index is out of range, the result is undefined. 3919** These routines may only be called when the most recent call to 3920** [sqlite3_step()] has returned [SQLITE_ROW] and neither 3921** [sqlite3_reset()] nor [sqlite3_finalize()] have been called subsequently. 3922** If any of these routines are called after [sqlite3_reset()] or 3923** [sqlite3_finalize()] or after [sqlite3_step()] has returned 3924** something other than [SQLITE_ROW], the results are undefined. 3925** If [sqlite3_step()] or [sqlite3_reset()] or [sqlite3_finalize()] 3926** are called from a different thread while any of these routines 3927** are pending, then the results are undefined. 3928** 3929** ^The sqlite3_column_type() routine returns the 3930** [SQLITE_INTEGER | datatype code] for the initial data type 3931** of the result column. ^The returned value is one of [SQLITE_INTEGER], 3932** [SQLITE_FLOAT], [SQLITE_TEXT], [SQLITE_BLOB], or [SQLITE_NULL]. The value 3933** returned by sqlite3_column_type() is only meaningful if no type 3934** conversions have occurred as described below. After a type conversion, 3935** the value returned by sqlite3_column_type() is undefined. Future 3936** versions of SQLite may change the behavior of sqlite3_column_type() 3937** following a type conversion. 3938** 3939** ^If the result is a BLOB or UTF-8 string then the sqlite3_column_bytes() 3940** routine returns the number of bytes in that BLOB or string. 3941** ^If the result is a UTF-16 string, then sqlite3_column_bytes() converts 3942** the string to UTF-8 and then returns the number of bytes. 3943** ^If the result is a numeric value then sqlite3_column_bytes() uses 3944** [sqlite3_snprintf()] to convert that value to a UTF-8 string and returns 3945** the number of bytes in that string. 3946** ^If the result is NULL, then sqlite3_column_bytes() returns zero. 3947** 3948** ^If the result is a BLOB or UTF-16 string then the sqlite3_column_bytes16() 3949** routine returns the number of bytes in that BLOB or string. 3950** ^If the result is a UTF-8 string, then sqlite3_column_bytes16() converts 3951** the string to UTF-16 and then returns the number of bytes. 3952** ^If the result is a numeric value then sqlite3_column_bytes16() uses 3953** [sqlite3_snprintf()] to convert that value to a UTF-16 string and returns 3954** the number of bytes in that string. 3955** ^If the result is NULL, then sqlite3_column_bytes16() returns zero. 3956** 3957** ^The values returned by [sqlite3_column_bytes()] and 3958** [sqlite3_column_bytes16()] do not include the zero terminators at the end 3959** of the string. ^For clarity: the values returned by 3960** [sqlite3_column_bytes()] and [sqlite3_column_bytes16()] are the number of 3961** bytes in the string, not the number of characters. 3962** 3963** ^Strings returned by sqlite3_column_text() and sqlite3_column_text16(), 3964** even empty strings, are always zero-terminated. ^The return 3965** value from sqlite3_column_blob() for a zero-length BLOB is a NULL pointer. 3966** 3967** <b>Warning:</b> ^The object returned by [sqlite3_column_value()] is an 3968** [unprotected sqlite3_value] object. In a multithreaded environment, 3969** an unprotected sqlite3_value object may only be used safely with 3970** [sqlite3_bind_value()] and [sqlite3_result_value()]. 3971** If the [unprotected sqlite3_value] object returned by 3972** [sqlite3_column_value()] is used in any other way, including calls 3973** to routines like [sqlite3_value_int()], [sqlite3_value_text()], 3974** or [sqlite3_value_bytes()], the behavior is not threadsafe. 3975** 3976** These routines attempt to convert the value where appropriate. ^For 3977** example, if the internal representation is FLOAT and a text result 3978** is requested, [sqlite3_snprintf()] is used internally to perform the 3979** conversion automatically. ^(The following table details the conversions 3980** that are applied: 3981** 3982** <blockquote> 3983** <table border="1"> 3984** <tr><th> Internal<br>Type <th> Requested<br>Type <th> Conversion 3985** 3986** <tr><td> NULL <td> INTEGER <td> Result is 0 3987** <tr><td> NULL <td> FLOAT <td> Result is 0.0 3988** <tr><td> NULL <td> TEXT <td> Result is a NULL pointer 3989** <tr><td> NULL <td> BLOB <td> Result is a NULL pointer 3990** <tr><td> INTEGER <td> FLOAT <td> Convert from integer to float 3991** <tr><td> INTEGER <td> TEXT <td> ASCII rendering of the integer 3992** <tr><td> INTEGER <td> BLOB <td> Same as INTEGER->TEXT 3993** <tr><td> FLOAT <td> INTEGER <td> [CAST] to INTEGER 3994** <tr><td> FLOAT <td> TEXT <td> ASCII rendering of the float 3995** <tr><td> FLOAT <td> BLOB <td> [CAST] to BLOB 3996** <tr><td> TEXT <td> INTEGER <td> [CAST] to INTEGER 3997** <tr><td> TEXT <td> FLOAT <td> [CAST] to REAL 3998** <tr><td> TEXT <td> BLOB <td> No change 3999** <tr><td> BLOB <td> INTEGER <td> [CAST] to INTEGER 4000** <tr><td> BLOB <td> FLOAT <td> [CAST] to REAL 4001** <tr><td> BLOB <td> TEXT <td> Add a zero terminator if needed 4002** </table> 4003** </blockquote>)^ 4004** 4005** Note that when type conversions occur, pointers returned by prior 4006** calls to sqlite3_column_blob(), sqlite3_column_text(), and/or 4007** sqlite3_column_text16() may be invalidated. 4008** Type conversions and pointer invalidations might occur 4009** in the following cases: 4010** 4011** <ul> 4012** <li> The initial content is a BLOB and sqlite3_column_text() or 4013** sqlite3_column_text16() is called. A zero-terminator might 4014** need to be added to the string.</li> 4015** <li> The initial content is UTF-8 text and sqlite3_column_bytes16() or 4016** sqlite3_column_text16() is called. The content must be converted 4017** to UTF-16.</li> 4018** <li> The initial content is UTF-16 text and sqlite3_column_bytes() or 4019** sqlite3_column_text() is called. The content must be converted 4020** to UTF-8.</li> 4021** </ul> 4022** 4023** ^Conversions between UTF-16be and UTF-16le are always done in place and do 4024** not invalidate a prior pointer, though of course the content of the buffer 4025** that the prior pointer references will have been modified. Other kinds 4026** of conversion are done in place when it is possible, but sometimes they 4027** are not possible and in those cases prior pointers are invalidated. 4028** 4029** The safest policy is to invoke these routines 4030** in one of the following ways: 4031** 4032** <ul> 4033** <li>sqlite3_column_text() followed by sqlite3_column_bytes()</li> 4034** <li>sqlite3_column_blob() followed by sqlite3_column_bytes()</li> 4035** <li>sqlite3_column_text16() followed by sqlite3_column_bytes16()</li> 4036** </ul> 4037** 4038** In other words, you should call sqlite3_column_text(), 4039** sqlite3_column_blob(), or sqlite3_column_text16() first to force the result 4040** into the desired format, then invoke sqlite3_column_bytes() or 4041** sqlite3_column_bytes16() to find the size of the result. Do not mix calls 4042** to sqlite3_column_text() or sqlite3_column_blob() with calls to 4043** sqlite3_column_bytes16(), and do not mix calls to sqlite3_column_text16() 4044** with calls to sqlite3_column_bytes(). 4045** 4046** ^The pointers returned are valid until a type conversion occurs as 4047** described above, or until [sqlite3_step()] or [sqlite3_reset()] or 4048** [sqlite3_finalize()] is called. ^The memory space used to hold strings 4049** and BLOBs is freed automatically. Do <em>not</em> pass the pointers returned 4050** from [sqlite3_column_blob()], [sqlite3_column_text()], etc. into 4051** [sqlite3_free()]. 4052** 4053** ^(If a memory allocation error occurs during the evaluation of any 4054** of these routines, a default value is returned. The default value 4055** is either the integer 0, the floating point number 0.0, or a NULL 4056** pointer. Subsequent calls to [sqlite3_errcode()] will return 4057** [SQLITE_NOMEM].)^ 4058*/ 4059const void *sqlite3_column_blob(sqlite3_stmt*, int iCol); 4060int sqlite3_column_bytes(sqlite3_stmt*, int iCol); 4061int sqlite3_column_bytes16(sqlite3_stmt*, int iCol); 4062double sqlite3_column_double(sqlite3_stmt*, int iCol); 4063int sqlite3_column_int(sqlite3_stmt*, int iCol); 4064sqlite3_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol); 4065const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol); 4066const void *sqlite3_column_text16(sqlite3_stmt*, int iCol); 4067int sqlite3_column_type(sqlite3_stmt*, int iCol); 4068sqlite3_value *sqlite3_column_value(sqlite3_stmt*, int iCol); 4069 4070/* 4071** CAPI3REF: Destroy A Prepared Statement Object 4072** DESTRUCTOR: sqlite3_stmt 4073** 4074** ^The sqlite3_finalize() function is called to delete a [prepared statement]. 4075** ^If the most recent evaluation of the statement encountered no errors 4076** or if the statement is never been evaluated, then sqlite3_finalize() returns 4077** SQLITE_OK. ^If the most recent evaluation of statement S failed, then 4078** sqlite3_finalize(S) returns the appropriate [error code] or 4079** [extended error code]. 4080** 4081** ^The sqlite3_finalize(S) routine can be called at any point during 4082** the life cycle of [prepared statement] S: 4083** before statement S is ever evaluated, after 4084** one or more calls to [sqlite3_reset()], or after any call 4085** to [sqlite3_step()] regardless of whether or not the statement has 4086** completed execution. 4087** 4088** ^Invoking sqlite3_finalize() on a NULL pointer is a harmless no-op. 4089** 4090** The application must finalize every [prepared statement] in order to avoid 4091** resource leaks. It is a grievous error for the application to try to use 4092** a prepared statement after it has been finalized. Any use of a prepared 4093** statement after it has been finalized can result in undefined and 4094** undesirable behavior such as segfaults and heap corruption. 4095*/ 4096int sqlite3_finalize(sqlite3_stmt *pStmt); 4097 4098/* 4099** CAPI3REF: Reset A Prepared Statement Object 4100** METHOD: sqlite3_stmt 4101** 4102** The sqlite3_reset() function is called to reset a [prepared statement] 4103** object back to its initial state, ready to be re-executed. 4104** ^Any SQL statement variables that had values bound to them using 4105** the [sqlite3_bind_blob | sqlite3_bind_*() API] retain their values. 4106** Use [sqlite3_clear_bindings()] to reset the bindings. 4107** 4108** ^The [sqlite3_reset(S)] interface resets the [prepared statement] S 4109** back to the beginning of its program. 4110** 4111** ^If the most recent call to [sqlite3_step(S)] for the 4112** [prepared statement] S returned [SQLITE_ROW] or [SQLITE_DONE], 4113** or if [sqlite3_step(S)] has never before been called on S, 4114** then [sqlite3_reset(S)] returns [SQLITE_OK]. 4115** 4116** ^If the most recent call to [sqlite3_step(S)] for the 4117** [prepared statement] S indicated an error, then 4118** [sqlite3_reset(S)] returns an appropriate [error code]. 4119** 4120** ^The [sqlite3_reset(S)] interface does not change the values 4121** of any [sqlite3_bind_blob|bindings] on the [prepared statement] S. 4122*/ 4123int sqlite3_reset(sqlite3_stmt *pStmt); 4124 4125/* 4126** CAPI3REF: Create Or Redefine SQL Functions 4127** KEYWORDS: {function creation routines} 4128** KEYWORDS: {application-defined SQL function} 4129** KEYWORDS: {application-defined SQL functions} 4130** METHOD: sqlite3 4131** 4132** ^These functions (collectively known as "function creation routines") 4133** are used to add SQL functions or aggregates or to redefine the behavior 4134** of existing SQL functions or aggregates. The only differences between 4135** these routines are the text encoding expected for 4136** the second parameter (the name of the function being created) 4137** and the presence or absence of a destructor callback for 4138** the application data pointer. 4139** 4140** ^The first parameter is the [database connection] to which the SQL 4141** function is to be added. ^If an application uses more than one database 4142** connection then application-defined SQL functions must be added 4143** to each database connection separately. 4144** 4145** ^The second parameter is the name of the SQL function to be created or 4146** redefined. ^The length of the name is limited to 255 bytes in a UTF-8 4147** representation, exclusive of the zero-terminator. ^Note that the name 4148** length limit is in UTF-8 bytes, not characters nor UTF-16 bytes. 4149** ^Any attempt to create a function with a longer name 4150** will result in [SQLITE_MISUSE] being returned. 4151** 4152** ^The third parameter (nArg) 4153** is the number of arguments that the SQL function or 4154** aggregate takes. ^If this parameter is -1, then the SQL function or 4155** aggregate may take any number of arguments between 0 and the limit 4156** set by [sqlite3_limit]([SQLITE_LIMIT_FUNCTION_ARG]). If the third 4157** parameter is less than -1 or greater than 127 then the behavior is 4158** undefined. 4159** 4160** ^The fourth parameter, eTextRep, specifies what 4161** [SQLITE_UTF8 | text encoding] this SQL function prefers for 4162** its parameters. The application should set this parameter to 4163** [SQLITE_UTF16LE] if the function implementation invokes 4164** [sqlite3_value_text16le()] on an input, or [SQLITE_UTF16BE] if the 4165** implementation invokes [sqlite3_value_text16be()] on an input, or 4166** [SQLITE_UTF16] if [sqlite3_value_text16()] is used, or [SQLITE_UTF8] 4167** otherwise. ^The same SQL function may be registered multiple times using 4168** different preferred text encodings, with different implementations for 4169** each encoding. 4170** ^When multiple implementations of the same function are available, SQLite 4171** will pick the one that involves the least amount of data conversion. 4172** 4173** ^The fourth parameter may optionally be ORed with [SQLITE_DETERMINISTIC] 4174** to signal that the function will always return the same result given 4175** the same inputs within a single SQL statement. Most SQL functions are 4176** deterministic. The built-in [random()] SQL function is an example of a 4177** function that is not deterministic. The SQLite query planner is able to 4178** perform additional optimizations on deterministic functions, so use 4179** of the [SQLITE_DETERMINISTIC] flag is recommended where possible. 4180** 4181** ^(The fifth parameter is an arbitrary pointer. The implementation of the 4182** function can gain access to this pointer using [sqlite3_user_data()].)^ 4183** 4184** ^The sixth, seventh and eighth parameters, xFunc, xStep and xFinal, are 4185** pointers to C-language functions that implement the SQL function or 4186** aggregate. ^A scalar SQL function requires an implementation of the xFunc 4187** callback only; NULL pointers must be passed as the xStep and xFinal 4188** parameters. ^An aggregate SQL function requires an implementation of xStep 4189** and xFinal and NULL pointer must be passed for xFunc. ^To delete an existing 4190** SQL function or aggregate, pass NULL pointers for all three function 4191** callbacks. 4192** 4193** ^(If the ninth parameter to sqlite3_create_function_v2() is not NULL, 4194** then it is destructor for the application data pointer. 4195** The destructor is invoked when the function is deleted, either by being 4196** overloaded or when the database connection closes.)^ 4197** ^The destructor is also invoked if the call to 4198** sqlite3_create_function_v2() fails. 4199** ^When the destructor callback of the tenth parameter is invoked, it 4200** is passed a single argument which is a copy of the application data 4201** pointer which was the fifth parameter to sqlite3_create_function_v2(). 4202** 4203** ^It is permitted to register multiple implementations of the same 4204** functions with the same name but with either differing numbers of 4205** arguments or differing preferred text encodings. ^SQLite will use 4206** the implementation that most closely matches the way in which the 4207** SQL function is used. ^A function implementation with a non-negative 4208** nArg parameter is a better match than a function implementation with 4209** a negative nArg. ^A function where the preferred text encoding 4210** matches the database encoding is a better 4211** match than a function where the encoding is different. 4212** ^A function where the encoding difference is between UTF16le and UTF16be 4213** is a closer match than a function where the encoding difference is 4214** between UTF8 and UTF16. 4215** 4216** ^Built-in functions may be overloaded by new application-defined functions. 4217** 4218** ^An application-defined function is permitted to call other 4219** SQLite interfaces. However, such calls must not 4220** close the database connection nor finalize or reset the prepared 4221** statement in which the function is running. 4222*/ 4223int sqlite3_create_function( 4224 sqlite3 *db, 4225 const char *zFunctionName, 4226 int nArg, 4227 int eTextRep, 4228 void *pApp, 4229 void (*xFunc)(sqlite3_context*,int,sqlite3_value**), 4230 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 4231 void (*xFinal)(sqlite3_context*) 4232); 4233int sqlite3_create_function16( 4234 sqlite3 *db, 4235 const void *zFunctionName, 4236 int nArg, 4237 int eTextRep, 4238 void *pApp, 4239 void (*xFunc)(sqlite3_context*,int,sqlite3_value**), 4240 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 4241 void (*xFinal)(sqlite3_context*) 4242); 4243int sqlite3_create_function_v2( 4244 sqlite3 *db, 4245 const char *zFunctionName, 4246 int nArg, 4247 int eTextRep, 4248 void *pApp, 4249 void (*xFunc)(sqlite3_context*,int,sqlite3_value**), 4250 void (*xStep)(sqlite3_context*,int,sqlite3_value**), 4251 void (*xFinal)(sqlite3_context*), 4252 void(*xDestroy)(void*) 4253); 4254 4255/* 4256** CAPI3REF: Text Encodings 4257** 4258** These constant define integer codes that represent the various 4259** text encodings supported by SQLite. 4260*/ 4261#define SQLITE_UTF8 1 /* IMP: R-37514-35566 */ 4262#define SQLITE_UTF16LE 2 /* IMP: R-03371-37637 */ 4263#define SQLITE_UTF16BE 3 /* IMP: R-51971-34154 */ 4264#define SQLITE_UTF16 4 /* Use native byte order */ 4265#define SQLITE_ANY 5 /* Deprecated */ 4266#define SQLITE_UTF16_ALIGNED 8 /* sqlite3_create_collation only */ 4267 4268/* 4269** CAPI3REF: Function Flags 4270** 4271** These constants may be ORed together with the 4272** [SQLITE_UTF8 | preferred text encoding] as the fourth argument 4273** to [sqlite3_create_function()], [sqlite3_create_function16()], or 4274** [sqlite3_create_function_v2()]. 4275*/ 4276#define SQLITE_DETERMINISTIC 0x800 4277 4278/* 4279** CAPI3REF: Deprecated Functions 4280** DEPRECATED 4281** 4282** These functions are [deprecated]. In order to maintain 4283** backwards compatibility with older code, these functions continue 4284** to be supported. However, new applications should avoid 4285** the use of these functions. To encourage programmers to avoid 4286** these functions, we will not explain what they do. 4287*/ 4288#ifndef SQLITE_OMIT_DEPRECATED 4289SQLITE_DEPRECATED int sqlite3_aggregate_count(sqlite3_context*); 4290SQLITE_DEPRECATED int sqlite3_expired(sqlite3_stmt*); 4291SQLITE_DEPRECATED int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*); 4292SQLITE_DEPRECATED int sqlite3_global_recover(void); 4293SQLITE_DEPRECATED void sqlite3_thread_cleanup(void); 4294SQLITE_DEPRECATED int sqlite3_memory_alarm(void(*)(void*,sqlite3_int64,int), 4295 void*,sqlite3_int64); 4296#endif 4297 4298/* 4299** CAPI3REF: Obtaining SQL Values 4300** METHOD: sqlite3_value 4301** 4302** The C-language implementation of SQL functions and aggregates uses 4303** this set of interface routines to access the parameter values on 4304** the function or aggregate. 4305** 4306** The xFunc (for scalar functions) or xStep (for aggregates) parameters 4307** to [sqlite3_create_function()] and [sqlite3_create_function16()] 4308** define callbacks that implement the SQL functions and aggregates. 4309** The 3rd parameter to these callbacks is an array of pointers to 4310** [protected sqlite3_value] objects. There is one [sqlite3_value] object for 4311** each parameter to the SQL function. These routines are used to 4312** extract values from the [sqlite3_value] objects. 4313** 4314** These routines work only with [protected sqlite3_value] objects. 4315** Any attempt to use these routines on an [unprotected sqlite3_value] 4316** object results in undefined behavior. 4317** 4318** ^These routines work just like the corresponding [column access functions] 4319** except that these routines take a single [protected sqlite3_value] object 4320** pointer instead of a [sqlite3_stmt*] pointer and an integer column number. 4321** 4322** ^The sqlite3_value_text16() interface extracts a UTF-16 string 4323** in the native byte-order of the host machine. ^The 4324** sqlite3_value_text16be() and sqlite3_value_text16le() interfaces 4325** extract UTF-16 strings as big-endian and little-endian respectively. 4326** 4327** ^(The sqlite3_value_numeric_type() interface attempts to apply 4328** numeric affinity to the value. This means that an attempt is 4329** made to convert the value to an integer or floating point. If 4330** such a conversion is possible without loss of information (in other 4331** words, if the value is a string that looks like a number) 4332** then the conversion is performed. Otherwise no conversion occurs. 4333** The [SQLITE_INTEGER | datatype] after conversion is returned.)^ 4334** 4335** Please pay particular attention to the fact that the pointer returned 4336** from [sqlite3_value_blob()], [sqlite3_value_text()], or 4337** [sqlite3_value_text16()] can be invalidated by a subsequent call to 4338** [sqlite3_value_bytes()], [sqlite3_value_bytes16()], [sqlite3_value_text()], 4339** or [sqlite3_value_text16()]. 4340** 4341** These routines must be called from the same thread as 4342** the SQL function that supplied the [sqlite3_value*] parameters. 4343*/ 4344const void *sqlite3_value_blob(sqlite3_value*); 4345int sqlite3_value_bytes(sqlite3_value*); 4346int sqlite3_value_bytes16(sqlite3_value*); 4347double sqlite3_value_double(sqlite3_value*); 4348int sqlite3_value_int(sqlite3_value*); 4349sqlite3_int64 sqlite3_value_int64(sqlite3_value*); 4350const unsigned char *sqlite3_value_text(sqlite3_value*); 4351const void *sqlite3_value_text16(sqlite3_value*); 4352const void *sqlite3_value_text16le(sqlite3_value*); 4353const void *sqlite3_value_text16be(sqlite3_value*); 4354int sqlite3_value_type(sqlite3_value*); 4355int sqlite3_value_numeric_type(sqlite3_value*); 4356 4357/* 4358** CAPI3REF: Copy And Free SQL Values 4359** METHOD: sqlite3_value 4360** 4361** ^The sqlite3_value_dup(V) interface makes a copy of the [sqlite3_value] 4362** object D and returns a pointer to that copy. ^The [sqlite3_value] returned 4363** is a [protected sqlite3_value] object even if the input is not. 4364** ^The sqlite3_value_dup(V) interface returns NULL if V is NULL or if a 4365** memory allocation fails. 4366** 4367** ^The sqlite3_value_free(V) interface frees an [sqlite3_value] object 4368** previously obtained from [sqlite3_value_dup()]. ^If V is a NULL pointer 4369** then sqlite3_value_free(V) is a harmless no-op. 4370*/ 4371SQLITE_EXPERIMENTAL sqlite3_value *sqlite3_value_dup(const sqlite3_value*); 4372SQLITE_EXPERIMENTAL void sqlite3_value_free(sqlite3_value*); 4373 4374/* 4375** CAPI3REF: Obtain Aggregate Function Context 4376** METHOD: sqlite3_context 4377** 4378** Implementations of aggregate SQL functions use this 4379** routine to allocate memory for storing their state. 4380** 4381** ^The first time the sqlite3_aggregate_context(C,N) routine is called 4382** for a particular aggregate function, SQLite 4383** allocates N of memory, zeroes out that memory, and returns a pointer 4384** to the new memory. ^On second and subsequent calls to 4385** sqlite3_aggregate_context() for the same aggregate function instance, 4386** the same buffer is returned. Sqlite3_aggregate_context() is normally 4387** called once for each invocation of the xStep callback and then one 4388** last time when the xFinal callback is invoked. ^(When no rows match 4389** an aggregate query, the xStep() callback of the aggregate function 4390** implementation is never called and xFinal() is called exactly once. 4391** In those cases, sqlite3_aggregate_context() might be called for the 4392** first time from within xFinal().)^ 4393** 4394** ^The sqlite3_aggregate_context(C,N) routine returns a NULL pointer 4395** when first called if N is less than or equal to zero or if a memory 4396** allocate error occurs. 4397** 4398** ^(The amount of space allocated by sqlite3_aggregate_context(C,N) is 4399** determined by the N parameter on first successful call. Changing the 4400** value of N in subsequent call to sqlite3_aggregate_context() within 4401** the same aggregate function instance will not resize the memory 4402** allocation.)^ Within the xFinal callback, it is customary to set 4403** N=0 in calls to sqlite3_aggregate_context(C,N) so that no 4404** pointless memory allocations occur. 4405** 4406** ^SQLite automatically frees the memory allocated by 4407** sqlite3_aggregate_context() when the aggregate query concludes. 4408** 4409** The first parameter must be a copy of the 4410** [sqlite3_context | SQL function context] that is the first parameter 4411** to the xStep or xFinal callback routine that implements the aggregate 4412** function. 4413** 4414** This routine must be called from the same thread in which 4415** the aggregate SQL function is running. 4416*/ 4417void *sqlite3_aggregate_context(sqlite3_context*, int nBytes); 4418 4419/* 4420** CAPI3REF: User Data For Functions 4421** METHOD: sqlite3_context 4422** 4423** ^The sqlite3_user_data() interface returns a copy of 4424** the pointer that was the pUserData parameter (the 5th parameter) 4425** of the [sqlite3_create_function()] 4426** and [sqlite3_create_function16()] routines that originally 4427** registered the application defined function. 4428** 4429** This routine must be called from the same thread in which 4430** the application-defined function is running. 4431*/ 4432void *sqlite3_user_data(sqlite3_context*); 4433 4434/* 4435** CAPI3REF: Database Connection For Functions 4436** METHOD: sqlite3_context 4437** 4438** ^The sqlite3_context_db_handle() interface returns a copy of 4439** the pointer to the [database connection] (the 1st parameter) 4440** of the [sqlite3_create_function()] 4441** and [sqlite3_create_function16()] routines that originally 4442** registered the application defined function. 4443*/ 4444sqlite3 *sqlite3_context_db_handle(sqlite3_context*); 4445 4446/* 4447** CAPI3REF: Function Auxiliary Data 4448** METHOD: sqlite3_context 4449** 4450** These functions may be used by (non-aggregate) SQL functions to 4451** associate metadata with argument values. If the same value is passed to 4452** multiple invocations of the same SQL function during query execution, under 4453** some circumstances the associated metadata may be preserved. An example 4454** of where this might be useful is in a regular-expression matching 4455** function. The compiled version of the regular expression can be stored as 4456** metadata associated with the pattern string. 4457** Then as long as the pattern string remains the same, 4458** the compiled regular expression can be reused on multiple 4459** invocations of the same function. 4460** 4461** ^The sqlite3_get_auxdata() interface returns a pointer to the metadata 4462** associated by the sqlite3_set_auxdata() function with the Nth argument 4463** value to the application-defined function. ^If there is no metadata 4464** associated with the function argument, this sqlite3_get_auxdata() interface 4465** returns a NULL pointer. 4466** 4467** ^The sqlite3_set_auxdata(C,N,P,X) interface saves P as metadata for the N-th 4468** argument of the application-defined function. ^Subsequent 4469** calls to sqlite3_get_auxdata(C,N) return P from the most recent 4470** sqlite3_set_auxdata(C,N,P,X) call if the metadata is still valid or 4471** NULL if the metadata has been discarded. 4472** ^After each call to sqlite3_set_auxdata(C,N,P,X) where X is not NULL, 4473** SQLite will invoke the destructor function X with parameter P exactly 4474** once, when the metadata is discarded. 4475** SQLite is free to discard the metadata at any time, including: <ul> 4476** <li> when the corresponding function parameter changes, or 4477** <li> when [sqlite3_reset()] or [sqlite3_finalize()] is called for the 4478** SQL statement, or 4479** <li> when sqlite3_set_auxdata() is invoked again on the same parameter, or 4480** <li> during the original sqlite3_set_auxdata() call when a memory 4481** allocation error occurs. </ul>)^ 4482** 4483** Note the last bullet in particular. The destructor X in 4484** sqlite3_set_auxdata(C,N,P,X) might be called immediately, before the 4485** sqlite3_set_auxdata() interface even returns. Hence sqlite3_set_auxdata() 4486** should be called near the end of the function implementation and the 4487** function implementation should not make any use of P after 4488** sqlite3_set_auxdata() has been called. 4489** 4490** ^(In practice, metadata is preserved between function calls for 4491** function parameters that are compile-time constants, including literal 4492** values and [parameters] and expressions composed from the same.)^ 4493** 4494** These routines must be called from the same thread in which 4495** the SQL function is running. 4496*/ 4497void *sqlite3_get_auxdata(sqlite3_context*, int N); 4498void sqlite3_set_auxdata(sqlite3_context*, int N, void*, void (*)(void*)); 4499 4500 4501/* 4502** CAPI3REF: Constants Defining Special Destructor Behavior 4503** 4504** These are special values for the destructor that is passed in as the 4505** final argument to routines like [sqlite3_result_blob()]. ^If the destructor 4506** argument is SQLITE_STATIC, it means that the content pointer is constant 4507** and will never change. It does not need to be destroyed. ^The 4508** SQLITE_TRANSIENT value means that the content will likely change in 4509** the near future and that SQLite should make its own private copy of 4510** the content before returning. 4511** 4512** The typedef is necessary to work around problems in certain 4513** C++ compilers. 4514*/ 4515typedef void (*sqlite3_destructor_type)(void*); 4516#define SQLITE_STATIC ((sqlite3_destructor_type)0) 4517#define SQLITE_TRANSIENT ((sqlite3_destructor_type)-1) 4518 4519/* 4520** CAPI3REF: Setting The Result Of An SQL Function 4521** METHOD: sqlite3_context 4522** 4523** These routines are used by the xFunc or xFinal callbacks that 4524** implement SQL functions and aggregates. See 4525** [sqlite3_create_function()] and [sqlite3_create_function16()] 4526** for additional information. 4527** 4528** These functions work very much like the [parameter binding] family of 4529** functions used to bind values to host parameters in prepared statements. 4530** Refer to the [SQL parameter] documentation for additional information. 4531** 4532** ^The sqlite3_result_blob() interface sets the result from 4533** an application-defined function to be the BLOB whose content is pointed 4534** to by the second parameter and which is N bytes long where N is the 4535** third parameter. 4536** 4537** ^The sqlite3_result_zeroblob() interfaces set the result of 4538** the application-defined function to be a BLOB containing all zero 4539** bytes and N bytes in size, where N is the value of the 2nd parameter. 4540** 4541** ^The sqlite3_result_double() interface sets the result from 4542** an application-defined function to be a floating point value specified 4543** by its 2nd argument. 4544** 4545** ^The sqlite3_result_error() and sqlite3_result_error16() functions 4546** cause the implemented SQL function to throw an exception. 4547** ^SQLite uses the string pointed to by the 4548** 2nd parameter of sqlite3_result_error() or sqlite3_result_error16() 4549** as the text of an error message. ^SQLite interprets the error 4550** message string from sqlite3_result_error() as UTF-8. ^SQLite 4551** interprets the string from sqlite3_result_error16() as UTF-16 in native 4552** byte order. ^If the third parameter to sqlite3_result_error() 4553** or sqlite3_result_error16() is negative then SQLite takes as the error 4554** message all text up through the first zero character. 4555** ^If the third parameter to sqlite3_result_error() or 4556** sqlite3_result_error16() is non-negative then SQLite takes that many 4557** bytes (not characters) from the 2nd parameter as the error message. 4558** ^The sqlite3_result_error() and sqlite3_result_error16() 4559** routines make a private copy of the error message text before 4560** they return. Hence, the calling function can deallocate or 4561** modify the text after they return without harm. 4562** ^The sqlite3_result_error_code() function changes the error code 4563** returned by SQLite as a result of an error in a function. ^By default, 4564** the error code is SQLITE_ERROR. ^A subsequent call to sqlite3_result_error() 4565** or sqlite3_result_error16() resets the error code to SQLITE_ERROR. 4566** 4567** ^The sqlite3_result_error_toobig() interface causes SQLite to throw an 4568** error indicating that a string or BLOB is too long to represent. 4569** 4570** ^The sqlite3_result_error_nomem() interface causes SQLite to throw an 4571** error indicating that a memory allocation failed. 4572** 4573** ^The sqlite3_result_int() interface sets the return value 4574** of the application-defined function to be the 32-bit signed integer 4575** value given in the 2nd argument. 4576** ^The sqlite3_result_int64() interface sets the return value 4577** of the application-defined function to be the 64-bit signed integer 4578** value given in the 2nd argument. 4579** 4580** ^The sqlite3_result_null() interface sets the return value 4581** of the application-defined function to be NULL. 4582** 4583** ^The sqlite3_result_text(), sqlite3_result_text16(), 4584** sqlite3_result_text16le(), and sqlite3_result_text16be() interfaces 4585** set the return value of the application-defined function to be 4586** a text string which is represented as UTF-8, UTF-16 native byte order, 4587** UTF-16 little endian, or UTF-16 big endian, respectively. 4588** ^The sqlite3_result_text64() interface sets the return value of an 4589** application-defined function to be a text string in an encoding 4590** specified by the fifth (and last) parameter, which must be one 4591** of [SQLITE_UTF8], [SQLITE_UTF16], [SQLITE_UTF16BE], or [SQLITE_UTF16LE]. 4592** ^SQLite takes the text result from the application from 4593** the 2nd parameter of the sqlite3_result_text* interfaces. 4594** ^If the 3rd parameter to the sqlite3_result_text* interfaces 4595** is negative, then SQLite takes result text from the 2nd parameter 4596** through the first zero character. 4597** ^If the 3rd parameter to the sqlite3_result_text* interfaces 4598** is non-negative, then as many bytes (not characters) of the text 4599** pointed to by the 2nd parameter are taken as the application-defined 4600** function result. If the 3rd parameter is non-negative, then it 4601** must be the byte offset into the string where the NUL terminator would 4602** appear if the string where NUL terminated. If any NUL characters occur 4603** in the string at a byte offset that is less than the value of the 3rd 4604** parameter, then the resulting string will contain embedded NULs and the 4605** result of expressions operating on strings with embedded NULs is undefined. 4606** ^If the 4th parameter to the sqlite3_result_text* interfaces 4607** or sqlite3_result_blob is a non-NULL pointer, then SQLite calls that 4608** function as the destructor on the text or BLOB result when it has 4609** finished using that result. 4610** ^If the 4th parameter to the sqlite3_result_text* interfaces or to 4611** sqlite3_result_blob is the special constant SQLITE_STATIC, then SQLite 4612** assumes that the text or BLOB result is in constant space and does not 4613** copy the content of the parameter nor call a destructor on the content 4614** when it has finished using that result. 4615** ^If the 4th parameter to the sqlite3_result_text* interfaces 4616** or sqlite3_result_blob is the special constant SQLITE_TRANSIENT 4617** then SQLite makes a copy of the result into space obtained from 4618** from [sqlite3_malloc()] before it returns. 4619** 4620** ^The sqlite3_result_value() interface sets the result of 4621** the application-defined function to be a copy of the 4622** [unprotected sqlite3_value] object specified by the 2nd parameter. ^The 4623** sqlite3_result_value() interface makes a copy of the [sqlite3_value] 4624** so that the [sqlite3_value] specified in the parameter may change or 4625** be deallocated after sqlite3_result_value() returns without harm. 4626** ^A [protected sqlite3_value] object may always be used where an 4627** [unprotected sqlite3_value] object is required, so either 4628** kind of [sqlite3_value] object can be used with this interface. 4629** 4630** If these routines are called from within the different thread 4631** than the one containing the application-defined function that received 4632** the [sqlite3_context] pointer, the results are undefined. 4633*/ 4634void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*)); 4635void sqlite3_result_blob64(sqlite3_context*,const void*, 4636 sqlite3_uint64,void(*)(void*)); 4637void sqlite3_result_double(sqlite3_context*, double); 4638void sqlite3_result_error(sqlite3_context*, const char*, int); 4639void sqlite3_result_error16(sqlite3_context*, const void*, int); 4640void sqlite3_result_error_toobig(sqlite3_context*); 4641void sqlite3_result_error_nomem(sqlite3_context*); 4642void sqlite3_result_error_code(sqlite3_context*, int); 4643void sqlite3_result_int(sqlite3_context*, int); 4644void sqlite3_result_int64(sqlite3_context*, sqlite3_int64); 4645void sqlite3_result_null(sqlite3_context*); 4646void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*)); 4647void sqlite3_result_text64(sqlite3_context*, const char*,sqlite3_uint64, 4648 void(*)(void*), unsigned char encoding); 4649void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*)); 4650void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*)); 4651void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*)); 4652void sqlite3_result_value(sqlite3_context*, sqlite3_value*); 4653void sqlite3_result_zeroblob(sqlite3_context*, int n); 4654 4655/* 4656** CAPI3REF: Define New Collating Sequences 4657** METHOD: sqlite3 4658** 4659** ^These functions add, remove, or modify a [collation] associated 4660** with the [database connection] specified as the first argument. 4661** 4662** ^The name of the collation is a UTF-8 string 4663** for sqlite3_create_collation() and sqlite3_create_collation_v2() 4664** and a UTF-16 string in native byte order for sqlite3_create_collation16(). 4665** ^Collation names that compare equal according to [sqlite3_strnicmp()] are 4666** considered to be the same name. 4667** 4668** ^(The third argument (eTextRep) must be one of the constants: 4669** <ul> 4670** <li> [SQLITE_UTF8], 4671** <li> [SQLITE_UTF16LE], 4672** <li> [SQLITE_UTF16BE], 4673** <li> [SQLITE_UTF16], or 4674** <li> [SQLITE_UTF16_ALIGNED]. 4675** </ul>)^ 4676** ^The eTextRep argument determines the encoding of strings passed 4677** to the collating function callback, xCallback. 4678** ^The [SQLITE_UTF16] and [SQLITE_UTF16_ALIGNED] values for eTextRep 4679** force strings to be UTF16 with native byte order. 4680** ^The [SQLITE_UTF16_ALIGNED] value for eTextRep forces strings to begin 4681** on an even byte address. 4682** 4683** ^The fourth argument, pArg, is an application data pointer that is passed 4684** through as the first argument to the collating function callback. 4685** 4686** ^The fifth argument, xCallback, is a pointer to the collating function. 4687** ^Multiple collating functions can be registered using the same name but 4688** with different eTextRep parameters and SQLite will use whichever 4689** function requires the least amount of data transformation. 4690** ^If the xCallback argument is NULL then the collating function is 4691** deleted. ^When all collating functions having the same name are deleted, 4692** that collation is no longer usable. 4693** 4694** ^The collating function callback is invoked with a copy of the pArg 4695** application data pointer and with two strings in the encoding specified 4696** by the eTextRep argument. The collating function must return an 4697** integer that is negative, zero, or positive 4698** if the first string is less than, equal to, or greater than the second, 4699** respectively. A collating function must always return the same answer 4700** given the same inputs. If two or more collating functions are registered 4701** to the same collation name (using different eTextRep values) then all 4702** must give an equivalent answer when invoked with equivalent strings. 4703** The collating function must obey the following properties for all 4704** strings A, B, and C: 4705** 4706** <ol> 4707** <li> If A==B then B==A. 4708** <li> If A==B and B==C then A==C. 4709** <li> If A<B THEN B>A. 4710** <li> If A<B and B<C then A<C. 4711** </ol> 4712** 4713** If a collating function fails any of the above constraints and that 4714** collating function is registered and used, then the behavior of SQLite 4715** is undefined. 4716** 4717** ^The sqlite3_create_collation_v2() works like sqlite3_create_collation() 4718** with the addition that the xDestroy callback is invoked on pArg when 4719** the collating function is deleted. 4720** ^Collating functions are deleted when they are overridden by later 4721** calls to the collation creation functions or when the 4722** [database connection] is closed using [sqlite3_close()]. 4723** 4724** ^The xDestroy callback is <u>not</u> called if the 4725** sqlite3_create_collation_v2() function fails. Applications that invoke 4726** sqlite3_create_collation_v2() with a non-NULL xDestroy argument should 4727** check the return code and dispose of the application data pointer 4728** themselves rather than expecting SQLite to deal with it for them. 4729** This is different from every other SQLite interface. The inconsistency 4730** is unfortunate but cannot be changed without breaking backwards 4731** compatibility. 4732** 4733** See also: [sqlite3_collation_needed()] and [sqlite3_collation_needed16()]. 4734*/ 4735int sqlite3_create_collation( 4736 sqlite3*, 4737 const char *zName, 4738 int eTextRep, 4739 void *pArg, 4740 int(*xCompare)(void*,int,const void*,int,const void*) 4741); 4742int sqlite3_create_collation_v2( 4743 sqlite3*, 4744 const char *zName, 4745 int eTextRep, 4746 void *pArg, 4747 int(*xCompare)(void*,int,const void*,int,const void*), 4748 void(*xDestroy)(void*) 4749); 4750int sqlite3_create_collation16( 4751 sqlite3*, 4752 const void *zName, 4753 int eTextRep, 4754 void *pArg, 4755 int(*xCompare)(void*,int,const void*,int,const void*) 4756); 4757 4758/* 4759** CAPI3REF: Collation Needed Callbacks 4760** METHOD: sqlite3 4761** 4762** ^To avoid having to register all collation sequences before a database 4763** can be used, a single callback function may be registered with the 4764** [database connection] to be invoked whenever an undefined collation 4765** sequence is required. 4766** 4767** ^If the function is registered using the sqlite3_collation_needed() API, 4768** then it is passed the names of undefined collation sequences as strings 4769** encoded in UTF-8. ^If sqlite3_collation_needed16() is used, 4770** the names are passed as UTF-16 in machine native byte order. 4771** ^A call to either function replaces the existing collation-needed callback. 4772** 4773** ^(When the callback is invoked, the first argument passed is a copy 4774** of the second argument to sqlite3_collation_needed() or 4775** sqlite3_collation_needed16(). The second argument is the database 4776** connection. The third argument is one of [SQLITE_UTF8], [SQLITE_UTF16BE], 4777** or [SQLITE_UTF16LE], indicating the most desirable form of the collation 4778** sequence function required. The fourth parameter is the name of the 4779** required collation sequence.)^ 4780** 4781** The callback function should register the desired collation using 4782** [sqlite3_create_collation()], [sqlite3_create_collation16()], or 4783** [sqlite3_create_collation_v2()]. 4784*/ 4785int sqlite3_collation_needed( 4786 sqlite3*, 4787 void*, 4788 void(*)(void*,sqlite3*,int eTextRep,const char*) 4789); 4790int sqlite3_collation_needed16( 4791 sqlite3*, 4792 void*, 4793 void(*)(void*,sqlite3*,int eTextRep,const void*) 4794); 4795 4796#ifdef SQLITE_HAS_CODEC 4797/* 4798** Specify the key for an encrypted database. This routine should be 4799** called right after sqlite3_open(). 4800** 4801** The code to implement this API is not available in the public release 4802** of SQLite. 4803*/ 4804int sqlite3_key( 4805 sqlite3 *db, /* Database to be rekeyed */ 4806 const void *pKey, int nKey /* The key */ 4807); 4808int sqlite3_key_v2( 4809 sqlite3 *db, /* Database to be rekeyed */ 4810 const char *zDbName, /* Name of the database */ 4811 const void *pKey, int nKey /* The key */ 4812); 4813 4814/* 4815** Change the key on an open database. If the current database is not 4816** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the 4817** database is decrypted. 4818** 4819** The code to implement this API is not available in the public release 4820** of SQLite. 4821*/ 4822int sqlite3_rekey( 4823 sqlite3 *db, /* Database to be rekeyed */ 4824 const void *pKey, int nKey /* The new key */ 4825); 4826int sqlite3_rekey_v2( 4827 sqlite3 *db, /* Database to be rekeyed */ 4828 const char *zDbName, /* Name of the database */ 4829 const void *pKey, int nKey /* The new key */ 4830); 4831 4832/* 4833** Specify the activation key for a SEE database. Unless 4834** activated, none of the SEE routines will work. 4835*/ 4836void sqlite3_activate_see( 4837 const char *zPassPhrase /* Activation phrase */ 4838); 4839#endif 4840 4841#ifdef SQLITE_ENABLE_CEROD 4842/* 4843** Specify the activation key for a CEROD database. Unless 4844** activated, none of the CEROD routines will work. 4845*/ 4846void sqlite3_activate_cerod( 4847 const char *zPassPhrase /* Activation phrase */ 4848); 4849#endif 4850 4851/* 4852** CAPI3REF: Suspend Execution For A Short Time 4853** 4854** The sqlite3_sleep() function causes the current thread to suspend execution 4855** for at least a number of milliseconds specified in its parameter. 4856** 4857** If the operating system does not support sleep requests with 4858** millisecond time resolution, then the time will be rounded up to 4859** the nearest second. The number of milliseconds of sleep actually 4860** requested from the operating system is returned. 4861** 4862** ^SQLite implements this interface by calling the xSleep() 4863** method of the default [sqlite3_vfs] object. If the xSleep() method 4864** of the default VFS is not implemented correctly, or not implemented at 4865** all, then the behavior of sqlite3_sleep() may deviate from the description 4866** in the previous paragraphs. 4867*/ 4868int sqlite3_sleep(int); 4869 4870/* 4871** CAPI3REF: Name Of The Folder Holding Temporary Files 4872** 4873** ^(If this global variable is made to point to a string which is 4874** the name of a folder (a.k.a. directory), then all temporary files 4875** created by SQLite when using a built-in [sqlite3_vfs | VFS] 4876** will be placed in that directory.)^ ^If this variable 4877** is a NULL pointer, then SQLite performs a search for an appropriate 4878** temporary file directory. 4879** 4880** Applications are strongly discouraged from using this global variable. 4881** It is required to set a temporary folder on Windows Runtime (WinRT). 4882** But for all other platforms, it is highly recommended that applications 4883** neither read nor write this variable. This global variable is a relic 4884** that exists for backwards compatibility of legacy applications and should 4885** be avoided in new projects. 4886** 4887** It is not safe to read or modify this variable in more than one 4888** thread at a time. It is not safe to read or modify this variable 4889** if a [database connection] is being used at the same time in a separate 4890** thread. 4891** It is intended that this variable be set once 4892** as part of process initialization and before any SQLite interface 4893** routines have been called and that this variable remain unchanged 4894** thereafter. 4895** 4896** ^The [temp_store_directory pragma] may modify this variable and cause 4897** it to point to memory obtained from [sqlite3_malloc]. ^Furthermore, 4898** the [temp_store_directory pragma] always assumes that any string 4899** that this variable points to is held in memory obtained from 4900** [sqlite3_malloc] and the pragma may attempt to free that memory 4901** using [sqlite3_free]. 4902** Hence, if this variable is modified directly, either it should be 4903** made NULL or made to point to memory obtained from [sqlite3_malloc] 4904** or else the use of the [temp_store_directory pragma] should be avoided. 4905** Except when requested by the [temp_store_directory pragma], SQLite 4906** does not free the memory that sqlite3_temp_directory points to. If 4907** the application wants that memory to be freed, it must do 4908** so itself, taking care to only do so after all [database connection] 4909** objects have been destroyed. 4910** 4911** <b>Note to Windows Runtime users:</b> The temporary directory must be set 4912** prior to calling [sqlite3_open] or [sqlite3_open_v2]. Otherwise, various 4913** features that require the use of temporary files may fail. Here is an 4914** example of how to do this using C++ with the Windows Runtime: 4915** 4916** <blockquote><pre> 4917** LPCWSTR zPath = Windows::Storage::ApplicationData::Current-> 4918** TemporaryFolder->Path->Data(); 4919** char zPathBuf[MAX_PATH + 1]; 4920** memset(zPathBuf, 0, sizeof(zPathBuf)); 4921** WideCharToMultiByte(CP_UTF8, 0, zPath, -1, zPathBuf, sizeof(zPathBuf), 4922** NULL, NULL); 4923** sqlite3_temp_directory = sqlite3_mprintf("%s", zPathBuf); 4924** </pre></blockquote> 4925*/ 4926SQLITE_EXTERN char *sqlite3_temp_directory; 4927 4928/* 4929** CAPI3REF: Name Of The Folder Holding Database Files 4930** 4931** ^(If this global variable is made to point to a string which is 4932** the name of a folder (a.k.a. directory), then all database files 4933** specified with a relative pathname and created or accessed by 4934** SQLite when using a built-in windows [sqlite3_vfs | VFS] will be assumed 4935** to be relative to that directory.)^ ^If this variable is a NULL 4936** pointer, then SQLite assumes that all database files specified 4937** with a relative pathname are relative to the current directory 4938** for the process. Only the windows VFS makes use of this global 4939** variable; it is ignored by the unix VFS. 4940** 4941** Changing the value of this variable while a database connection is 4942** open can result in a corrupt database. 4943** 4944** It is not safe to read or modify this variable in more than one 4945** thread at a time. It is not safe to read or modify this variable 4946** if a [database connection] is being used at the same time in a separate 4947** thread. 4948** It is intended that this variable be set once 4949** as part of process initialization and before any SQLite interface 4950** routines have been called and that this variable remain unchanged 4951** thereafter. 4952** 4953** ^The [data_store_directory pragma] may modify this variable and cause 4954** it to point to memory obtained from [sqlite3_malloc]. ^Furthermore, 4955** the [data_store_directory pragma] always assumes that any string 4956** that this variable points to is held in memory obtained from 4957** [sqlite3_malloc] and the pragma may attempt to free that memory 4958** using [sqlite3_free]. 4959** Hence, if this variable is modified directly, either it should be 4960** made NULL or made to point to memory obtained from [sqlite3_malloc] 4961** or else the use of the [data_store_directory pragma] should be avoided. 4962*/ 4963SQLITE_EXTERN char *sqlite3_data_directory; 4964 4965/* 4966** CAPI3REF: Test For Auto-Commit Mode 4967** KEYWORDS: {autocommit mode} 4968** METHOD: sqlite3 4969** 4970** ^The sqlite3_get_autocommit() interface returns non-zero or 4971** zero if the given database connection is or is not in autocommit mode, 4972** respectively. ^Autocommit mode is on by default. 4973** ^Autocommit mode is disabled by a [BEGIN] statement. 4974** ^Autocommit mode is re-enabled by a [COMMIT] or [ROLLBACK]. 4975** 4976** If certain kinds of errors occur on a statement within a multi-statement 4977** transaction (errors including [SQLITE_FULL], [SQLITE_IOERR], 4978** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the 4979** transaction might be rolled back automatically. The only way to 4980** find out whether SQLite automatically rolled back the transaction after 4981** an error is to use this function. 4982** 4983** If another thread changes the autocommit status of the database 4984** connection while this routine is running, then the return value 4985** is undefined. 4986*/ 4987int sqlite3_get_autocommit(sqlite3*); 4988 4989/* 4990** CAPI3REF: Find The Database Handle Of A Prepared Statement 4991** METHOD: sqlite3_stmt 4992** 4993** ^The sqlite3_db_handle interface returns the [database connection] handle 4994** to which a [prepared statement] belongs. ^The [database connection] 4995** returned by sqlite3_db_handle is the same [database connection] 4996** that was the first argument 4997** to the [sqlite3_prepare_v2()] call (or its variants) that was used to 4998** create the statement in the first place. 4999*/ 5000sqlite3 *sqlite3_db_handle(sqlite3_stmt*); 5001 5002/* 5003** CAPI3REF: Return The Filename For A Database Connection 5004** METHOD: sqlite3 5005** 5006** ^The sqlite3_db_filename(D,N) interface returns a pointer to a filename 5007** associated with database N of connection D. ^The main database file 5008** has the name "main". If there is no attached database N on the database 5009** connection D, or if database N is a temporary or in-memory database, then 5010** a NULL pointer is returned. 5011** 5012** ^The filename returned by this function is the output of the 5013** xFullPathname method of the [VFS]. ^In other words, the filename 5014** will be an absolute pathname, even if the filename used 5015** to open the database originally was a URI or relative pathname. 5016*/ 5017const char *sqlite3_db_filename(sqlite3 *db, const char *zDbName); 5018 5019/* 5020** CAPI3REF: Determine if a database is read-only 5021** METHOD: sqlite3 5022** 5023** ^The sqlite3_db_readonly(D,N) interface returns 1 if the database N 5024** of connection D is read-only, 0 if it is read/write, or -1 if N is not 5025** the name of a database on connection D. 5026*/ 5027int sqlite3_db_readonly(sqlite3 *db, const char *zDbName); 5028 5029/* 5030** CAPI3REF: Find the next prepared statement 5031** METHOD: sqlite3 5032** 5033** ^This interface returns a pointer to the next [prepared statement] after 5034** pStmt associated with the [database connection] pDb. ^If pStmt is NULL 5035** then this interface returns a pointer to the first prepared statement 5036** associated with the database connection pDb. ^If no prepared statement 5037** satisfies the conditions of this routine, it returns NULL. 5038** 5039** The [database connection] pointer D in a call to 5040** [sqlite3_next_stmt(D,S)] must refer to an open database 5041** connection and in particular must not be a NULL pointer. 5042*/ 5043sqlite3_stmt *sqlite3_next_stmt(sqlite3 *pDb, sqlite3_stmt *pStmt); 5044 5045/* 5046** CAPI3REF: Commit And Rollback Notification Callbacks 5047** METHOD: sqlite3 5048** 5049** ^The sqlite3_commit_hook() interface registers a callback 5050** function to be invoked whenever a transaction is [COMMIT | committed]. 5051** ^Any callback set by a previous call to sqlite3_commit_hook() 5052** for the same database connection is overridden. 5053** ^The sqlite3_rollback_hook() interface registers a callback 5054** function to be invoked whenever a transaction is [ROLLBACK | rolled back]. 5055** ^Any callback set by a previous call to sqlite3_rollback_hook() 5056** for the same database connection is overridden. 5057** ^The pArg argument is passed through to the callback. 5058** ^If the callback on a commit hook function returns non-zero, 5059** then the commit is converted into a rollback. 5060** 5061** ^The sqlite3_commit_hook(D,C,P) and sqlite3_rollback_hook(D,C,P) functions 5062** return the P argument from the previous call of the same function 5063** on the same [database connection] D, or NULL for 5064** the first call for each function on D. 5065** 5066** The commit and rollback hook callbacks are not reentrant. 5067** The callback implementation must not do anything that will modify 5068** the database connection that invoked the callback. Any actions 5069** to modify the database connection must be deferred until after the 5070** completion of the [sqlite3_step()] call that triggered the commit 5071** or rollback hook in the first place. 5072** Note that running any other SQL statements, including SELECT statements, 5073** or merely calling [sqlite3_prepare_v2()] and [sqlite3_step()] will modify 5074** the database connections for the meaning of "modify" in this paragraph. 5075** 5076** ^Registering a NULL function disables the callback. 5077** 5078** ^When the commit hook callback routine returns zero, the [COMMIT] 5079** operation is allowed to continue normally. ^If the commit hook 5080** returns non-zero, then the [COMMIT] is converted into a [ROLLBACK]. 5081** ^The rollback hook is invoked on a rollback that results from a commit 5082** hook returning non-zero, just as it would be with any other rollback. 5083** 5084** ^For the purposes of this API, a transaction is said to have been 5085** rolled back if an explicit "ROLLBACK" statement is executed, or 5086** an error or constraint causes an implicit rollback to occur. 5087** ^The rollback callback is not invoked if a transaction is 5088** automatically rolled back because the database connection is closed. 5089** 5090** See also the [sqlite3_update_hook()] interface. 5091*/ 5092void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*); 5093void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*); 5094 5095/* 5096** CAPI3REF: Data Change Notification Callbacks 5097** METHOD: sqlite3 5098** 5099** ^The sqlite3_update_hook() interface registers a callback function 5100** with the [database connection] identified by the first argument 5101** to be invoked whenever a row is updated, inserted or deleted in 5102** a rowid table. 5103** ^Any callback set by a previous call to this function 5104** for the same database connection is overridden. 5105** 5106** ^The second argument is a pointer to the function to invoke when a 5107** row is updated, inserted or deleted in a rowid table. 5108** ^The first argument to the callback is a copy of the third argument 5109** to sqlite3_update_hook(). 5110** ^The second callback argument is one of [SQLITE_INSERT], [SQLITE_DELETE], 5111** or [SQLITE_UPDATE], depending on the operation that caused the callback 5112** to be invoked. 5113** ^The third and fourth arguments to the callback contain pointers to the 5114** database and table name containing the affected row. 5115** ^The final callback parameter is the [rowid] of the row. 5116** ^In the case of an update, this is the [rowid] after the update takes place. 5117** 5118** ^(The update hook is not invoked when internal system tables are 5119** modified (i.e. sqlite_master and sqlite_sequence).)^ 5120** ^The update hook is not invoked when [WITHOUT ROWID] tables are modified. 5121** 5122** ^In the current implementation, the update hook 5123** is not invoked when duplication rows are deleted because of an 5124** [ON CONFLICT | ON CONFLICT REPLACE] clause. ^Nor is the update hook 5125** invoked when rows are deleted using the [truncate optimization]. 5126** The exceptions defined in this paragraph might change in a future 5127** release of SQLite. 5128** 5129** The update hook implementation must not do anything that will modify 5130** the database connection that invoked the update hook. Any actions 5131** to modify the database connection must be deferred until after the 5132** completion of the [sqlite3_step()] call that triggered the update hook. 5133** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their 5134** database connections for the meaning of "modify" in this paragraph. 5135** 5136** ^The sqlite3_update_hook(D,C,P) function 5137** returns the P argument from the previous call 5138** on the same [database connection] D, or NULL for 5139** the first call on D. 5140** 5141** See also the [sqlite3_commit_hook()] and [sqlite3_rollback_hook()] 5142** interfaces. 5143*/ 5144void *sqlite3_update_hook( 5145 sqlite3*, 5146 void(*)(void *,int ,char const *,char const *,sqlite3_int64), 5147 void* 5148); 5149 5150/* 5151** CAPI3REF: Enable Or Disable Shared Pager Cache 5152** 5153** ^(This routine enables or disables the sharing of the database cache 5154** and schema data structures between [database connection | connections] 5155** to the same database. Sharing is enabled if the argument is true 5156** and disabled if the argument is false.)^ 5157** 5158** ^Cache sharing is enabled and disabled for an entire process. 5159** This is a change as of SQLite version 3.5.0. In prior versions of SQLite, 5160** sharing was enabled or disabled for each thread separately. 5161** 5162** ^(The cache sharing mode set by this interface effects all subsequent 5163** calls to [sqlite3_open()], [sqlite3_open_v2()], and [sqlite3_open16()]. 5164** Existing database connections continue use the sharing mode 5165** that was in effect at the time they were opened.)^ 5166** 5167** ^(This routine returns [SQLITE_OK] if shared cache was enabled or disabled 5168** successfully. An [error code] is returned otherwise.)^ 5169** 5170** ^Shared cache is disabled by default. But this might change in 5171** future releases of SQLite. Applications that care about shared 5172** cache setting should set it explicitly. 5173** 5174** Note: This method is disabled on MacOS X 10.7 and iOS version 5.0 5175** and will always return SQLITE_MISUSE. On those systems, 5176** shared cache mode should be enabled per-database connection via 5177** [sqlite3_open_v2()] with [SQLITE_OPEN_SHAREDCACHE]. 5178** 5179** This interface is threadsafe on processors where writing a 5180** 32-bit integer is atomic. 5181** 5182** See Also: [SQLite Shared-Cache Mode] 5183*/ 5184int sqlite3_enable_shared_cache(int); 5185 5186/* 5187** CAPI3REF: Attempt To Free Heap Memory 5188** 5189** ^The sqlite3_release_memory() interface attempts to free N bytes 5190** of heap memory by deallocating non-essential memory allocations 5191** held by the database library. Memory used to cache database 5192** pages to improve performance is an example of non-essential memory. 5193** ^sqlite3_release_memory() returns the number of bytes actually freed, 5194** which might be more or less than the amount requested. 5195** ^The sqlite3_release_memory() routine is a no-op returning zero 5196** if SQLite is not compiled with [SQLITE_ENABLE_MEMORY_MANAGEMENT]. 5197** 5198** See also: [sqlite3_db_release_memory()] 5199*/ 5200int sqlite3_release_memory(int); 5201 5202/* 5203** CAPI3REF: Free Memory Used By A Database Connection 5204** METHOD: sqlite3 5205** 5206** ^The sqlite3_db_release_memory(D) interface attempts to free as much heap 5207** memory as possible from database connection D. Unlike the 5208** [sqlite3_release_memory()] interface, this interface is in effect even 5209** when the [SQLITE_ENABLE_MEMORY_MANAGEMENT] compile-time option is 5210** omitted. 5211** 5212** See also: [sqlite3_release_memory()] 5213*/ 5214int sqlite3_db_release_memory(sqlite3*); 5215 5216/* 5217** CAPI3REF: Impose A Limit On Heap Size 5218** 5219** ^The sqlite3_soft_heap_limit64() interface sets and/or queries the 5220** soft limit on the amount of heap memory that may be allocated by SQLite. 5221** ^SQLite strives to keep heap memory utilization below the soft heap 5222** limit by reducing the number of pages held in the page cache 5223** as heap memory usages approaches the limit. 5224** ^The soft heap limit is "soft" because even though SQLite strives to stay 5225** below the limit, it will exceed the limit rather than generate 5226** an [SQLITE_NOMEM] error. In other words, the soft heap limit 5227** is advisory only. 5228** 5229** ^The return value from sqlite3_soft_heap_limit64() is the size of 5230** the soft heap limit prior to the call, or negative in the case of an 5231** error. ^If the argument N is negative 5232** then no change is made to the soft heap limit. Hence, the current 5233** size of the soft heap limit can be determined by invoking 5234** sqlite3_soft_heap_limit64() with a negative argument. 5235** 5236** ^If the argument N is zero then the soft heap limit is disabled. 5237** 5238** ^(The soft heap limit is not enforced in the current implementation 5239** if one or more of following conditions are true: 5240** 5241** <ul> 5242** <li> The soft heap limit is set to zero. 5243** <li> Memory accounting is disabled using a combination of the 5244** [sqlite3_config]([SQLITE_CONFIG_MEMSTATUS],...) start-time option and 5245** the [SQLITE_DEFAULT_MEMSTATUS] compile-time option. 5246** <li> An alternative page cache implementation is specified using 5247** [sqlite3_config]([SQLITE_CONFIG_PCACHE2],...). 5248** <li> The page cache allocates from its own memory pool supplied 5249** by [sqlite3_config]([SQLITE_CONFIG_PAGECACHE],...) rather than 5250** from the heap. 5251** </ul>)^ 5252** 5253** Beginning with SQLite version 3.7.3, the soft heap limit is enforced 5254** regardless of whether or not the [SQLITE_ENABLE_MEMORY_MANAGEMENT] 5255** compile-time option is invoked. With [SQLITE_ENABLE_MEMORY_MANAGEMENT], 5256** the soft heap limit is enforced on every memory allocation. Without 5257** [SQLITE_ENABLE_MEMORY_MANAGEMENT], the soft heap limit is only enforced 5258** when memory is allocated by the page cache. Testing suggests that because 5259** the page cache is the predominate memory user in SQLite, most 5260** applications will achieve adequate soft heap limit enforcement without 5261** the use of [SQLITE_ENABLE_MEMORY_MANAGEMENT]. 5262** 5263** The circumstances under which SQLite will enforce the soft heap limit may 5264** changes in future releases of SQLite. 5265*/ 5266sqlite3_int64 sqlite3_soft_heap_limit64(sqlite3_int64 N); 5267 5268/* 5269** CAPI3REF: Deprecated Soft Heap Limit Interface 5270** DEPRECATED 5271** 5272** This is a deprecated version of the [sqlite3_soft_heap_limit64()] 5273** interface. This routine is provided for historical compatibility 5274** only. All new applications should use the 5275** [sqlite3_soft_heap_limit64()] interface rather than this one. 5276*/ 5277SQLITE_DEPRECATED void sqlite3_soft_heap_limit(int N); 5278 5279 5280/* 5281** CAPI3REF: Extract Metadata About A Column Of A Table 5282** METHOD: sqlite3 5283** 5284** ^(The sqlite3_table_column_metadata(X,D,T,C,....) routine returns 5285** information about column C of table T in database D 5286** on [database connection] X.)^ ^The sqlite3_table_column_metadata() 5287** interface returns SQLITE_OK and fills in the non-NULL pointers in 5288** the final five arguments with appropriate values if the specified 5289** column exists. ^The sqlite3_table_column_metadata() interface returns 5290** SQLITE_ERROR and if the specified column does not exist. 5291** ^If the column-name parameter to sqlite3_table_column_metadata() is a 5292** NULL pointer, then this routine simply checks for the existance of the 5293** table and returns SQLITE_OK if the table exists and SQLITE_ERROR if it 5294** does not. 5295** 5296** ^The column is identified by the second, third and fourth parameters to 5297** this function. ^(The second parameter is either the name of the database 5298** (i.e. "main", "temp", or an attached database) containing the specified 5299** table or NULL.)^ ^If it is NULL, then all attached databases are searched 5300** for the table using the same algorithm used by the database engine to 5301** resolve unqualified table references. 5302** 5303** ^The third and fourth parameters to this function are the table and column 5304** name of the desired column, respectively. 5305** 5306** ^Metadata is returned by writing to the memory locations passed as the 5th 5307** and subsequent parameters to this function. ^Any of these arguments may be 5308** NULL, in which case the corresponding element of metadata is omitted. 5309** 5310** ^(<blockquote> 5311** <table border="1"> 5312** <tr><th> Parameter <th> Output<br>Type <th> Description 5313** 5314** <tr><td> 5th <td> const char* <td> Data type 5315** <tr><td> 6th <td> const char* <td> Name of default collation sequence 5316** <tr><td> 7th <td> int <td> True if column has a NOT NULL constraint 5317** <tr><td> 8th <td> int <td> True if column is part of the PRIMARY KEY 5318** <tr><td> 9th <td> int <td> True if column is [AUTOINCREMENT] 5319** </table> 5320** </blockquote>)^ 5321** 5322** ^The memory pointed to by the character pointers returned for the 5323** declaration type and collation sequence is valid until the next 5324** call to any SQLite API function. 5325** 5326** ^If the specified table is actually a view, an [error code] is returned. 5327** 5328** ^If the specified column is "rowid", "oid" or "_rowid_" and the table 5329** is not a [WITHOUT ROWID] table and an 5330** [INTEGER PRIMARY KEY] column has been explicitly declared, then the output 5331** parameters are set for the explicitly declared column. ^(If there is no 5332** [INTEGER PRIMARY KEY] column, then the outputs 5333** for the [rowid] are set as follows: 5334** 5335** <pre> 5336** data type: "INTEGER" 5337** collation sequence: "BINARY" 5338** not null: 0 5339** primary key: 1 5340** auto increment: 0 5341** </pre>)^ 5342** 5343** ^This function causes all database schemas to be read from disk and 5344** parsed, if that has not already been done, and returns an error if 5345** any errors are encountered while loading the schema. 5346*/ 5347int sqlite3_table_column_metadata( 5348 sqlite3 *db, /* Connection handle */ 5349 const char *zDbName, /* Database name or NULL */ 5350 const char *zTableName, /* Table name */ 5351 const char *zColumnName, /* Column name */ 5352 char const **pzDataType, /* OUTPUT: Declared data type */ 5353 char const **pzCollSeq, /* OUTPUT: Collation sequence name */ 5354 int *pNotNull, /* OUTPUT: True if NOT NULL constraint exists */ 5355 int *pPrimaryKey, /* OUTPUT: True if column part of PK */ 5356 int *pAutoinc /* OUTPUT: True if column is auto-increment */ 5357); 5358 5359/* 5360** CAPI3REF: Load An Extension 5361** METHOD: sqlite3 5362** 5363** ^This interface loads an SQLite extension library from the named file. 5364** 5365** ^The sqlite3_load_extension() interface attempts to load an 5366** [SQLite extension] library contained in the file zFile. If 5367** the file cannot be loaded directly, attempts are made to load 5368** with various operating-system specific extensions added. 5369** So for example, if "samplelib" cannot be loaded, then names like 5370** "samplelib.so" or "samplelib.dylib" or "samplelib.dll" might 5371** be tried also. 5372** 5373** ^The entry point is zProc. 5374** ^(zProc may be 0, in which case SQLite will try to come up with an 5375** entry point name on its own. It first tries "sqlite3_extension_init". 5376** If that does not work, it constructs a name "sqlite3_X_init" where the 5377** X is consists of the lower-case equivalent of all ASCII alphabetic 5378** characters in the filename from the last "/" to the first following 5379** "." and omitting any initial "lib".)^ 5380** ^The sqlite3_load_extension() interface returns 5381** [SQLITE_OK] on success and [SQLITE_ERROR] if something goes wrong. 5382** ^If an error occurs and pzErrMsg is not 0, then the 5383** [sqlite3_load_extension()] interface shall attempt to 5384** fill *pzErrMsg with error message text stored in memory 5385** obtained from [sqlite3_malloc()]. The calling function 5386** should free this memory by calling [sqlite3_free()]. 5387** 5388** ^Extension loading must be enabled using 5389** [sqlite3_enable_load_extension()] prior to calling this API, 5390** otherwise an error will be returned. 5391** 5392** See also the [load_extension() SQL function]. 5393*/ 5394int sqlite3_load_extension( 5395 sqlite3 *db, /* Load the extension into this database connection */ 5396 const char *zFile, /* Name of the shared library containing extension */ 5397 const char *zProc, /* Entry point. Derived from zFile if 0 */ 5398 char **pzErrMsg /* Put error message here if not 0 */ 5399); 5400 5401/* 5402** CAPI3REF: Enable Or Disable Extension Loading 5403** METHOD: sqlite3 5404** 5405** ^So as not to open security holes in older applications that are 5406** unprepared to deal with [extension loading], and as a means of disabling 5407** [extension loading] while evaluating user-entered SQL, the following API 5408** is provided to turn the [sqlite3_load_extension()] mechanism on and off. 5409** 5410** ^Extension loading is off by default. 5411** ^Call the sqlite3_enable_load_extension() routine with onoff==1 5412** to turn extension loading on and call it with onoff==0 to turn 5413** it back off again. 5414*/ 5415int sqlite3_enable_load_extension(sqlite3 *db, int onoff); 5416 5417/* 5418** CAPI3REF: Automatically Load Statically Linked Extensions 5419** 5420** ^This interface causes the xEntryPoint() function to be invoked for 5421** each new [database connection] that is created. The idea here is that 5422** xEntryPoint() is the entry point for a statically linked [SQLite extension] 5423** that is to be automatically loaded into all new database connections. 5424** 5425** ^(Even though the function prototype shows that xEntryPoint() takes 5426** no arguments and returns void, SQLite invokes xEntryPoint() with three 5427** arguments and expects and integer result as if the signature of the 5428** entry point where as follows: 5429** 5430** <blockquote><pre> 5431** int xEntryPoint( 5432** sqlite3 *db, 5433** const char **pzErrMsg, 5434** const struct sqlite3_api_routines *pThunk 5435** ); 5436** </pre></blockquote>)^ 5437** 5438** If the xEntryPoint routine encounters an error, it should make *pzErrMsg 5439** point to an appropriate error message (obtained from [sqlite3_mprintf()]) 5440** and return an appropriate [error code]. ^SQLite ensures that *pzErrMsg 5441** is NULL before calling the xEntryPoint(). ^SQLite will invoke 5442** [sqlite3_free()] on *pzErrMsg after xEntryPoint() returns. ^If any 5443** xEntryPoint() returns an error, the [sqlite3_open()], [sqlite3_open16()], 5444** or [sqlite3_open_v2()] call that provoked the xEntryPoint() will fail. 5445** 5446** ^Calling sqlite3_auto_extension(X) with an entry point X that is already 5447** on the list of automatic extensions is a harmless no-op. ^No entry point 5448** will be called more than once for each database connection that is opened. 5449** 5450** See also: [sqlite3_reset_auto_extension()] 5451** and [sqlite3_cancel_auto_extension()] 5452*/ 5453int sqlite3_auto_extension(void (*xEntryPoint)(void)); 5454 5455/* 5456** CAPI3REF: Cancel Automatic Extension Loading 5457** 5458** ^The [sqlite3_cancel_auto_extension(X)] interface unregisters the 5459** initialization routine X that was registered using a prior call to 5460** [sqlite3_auto_extension(X)]. ^The [sqlite3_cancel_auto_extension(X)] 5461** routine returns 1 if initialization routine X was successfully 5462** unregistered and it returns 0 if X was not on the list of initialization 5463** routines. 5464*/ 5465int sqlite3_cancel_auto_extension(void (*xEntryPoint)(void)); 5466 5467/* 5468** CAPI3REF: Reset Automatic Extension Loading 5469** 5470** ^This interface disables all automatic extensions previously 5471** registered using [sqlite3_auto_extension()]. 5472*/ 5473void sqlite3_reset_auto_extension(void); 5474 5475/* 5476** The interface to the virtual-table mechanism is currently considered 5477** to be experimental. The interface might change in incompatible ways. 5478** If this is a problem for you, do not use the interface at this time. 5479** 5480** When the virtual-table mechanism stabilizes, we will declare the 5481** interface fixed, support it indefinitely, and remove this comment. 5482*/ 5483 5484/* 5485** Structures used by the virtual table interface 5486*/ 5487typedef struct sqlite3_vtab sqlite3_vtab; 5488typedef struct sqlite3_index_info sqlite3_index_info; 5489typedef struct sqlite3_vtab_cursor sqlite3_vtab_cursor; 5490typedef struct sqlite3_module sqlite3_module; 5491 5492/* 5493** CAPI3REF: Virtual Table Object 5494** KEYWORDS: sqlite3_module {virtual table module} 5495** 5496** This structure, sometimes called a "virtual table module", 5497** defines the implementation of a [virtual tables]. 5498** This structure consists mostly of methods for the module. 5499** 5500** ^A virtual table module is created by filling in a persistent 5501** instance of this structure and passing a pointer to that instance 5502** to [sqlite3_create_module()] or [sqlite3_create_module_v2()]. 5503** ^The registration remains valid until it is replaced by a different 5504** module or until the [database connection] closes. The content 5505** of this structure must not change while it is registered with 5506** any database connection. 5507*/ 5508struct sqlite3_module { 5509 int iVersion; 5510 int (*xCreate)(sqlite3*, void *pAux, 5511 int argc, const char *const*argv, 5512 sqlite3_vtab **ppVTab, char**); 5513 int (*xConnect)(sqlite3*, void *pAux, 5514 int argc, const char *const*argv, 5515 sqlite3_vtab **ppVTab, char**); 5516 int (*xBestIndex)(sqlite3_vtab *pVTab, sqlite3_index_info*); 5517 int (*xDisconnect)(sqlite3_vtab *pVTab); 5518 int (*xDestroy)(sqlite3_vtab *pVTab); 5519 int (*xOpen)(sqlite3_vtab *pVTab, sqlite3_vtab_cursor **ppCursor); 5520 int (*xClose)(sqlite3_vtab_cursor*); 5521 int (*xFilter)(sqlite3_vtab_cursor*, int idxNum, const char *idxStr, 5522 int argc, sqlite3_value **argv); 5523 int (*xNext)(sqlite3_vtab_cursor*); 5524 int (*xEof)(sqlite3_vtab_cursor*); 5525 int (*xColumn)(sqlite3_vtab_cursor*, sqlite3_context*, int); 5526 int (*xRowid)(sqlite3_vtab_cursor*, sqlite3_int64 *pRowid); 5527 int (*xUpdate)(sqlite3_vtab *, int, sqlite3_value **, sqlite3_int64 *); 5528 int (*xBegin)(sqlite3_vtab *pVTab); 5529 int (*xSync)(sqlite3_vtab *pVTab); 5530 int (*xCommit)(sqlite3_vtab *pVTab); 5531 int (*xRollback)(sqlite3_vtab *pVTab); 5532 int (*xFindFunction)(sqlite3_vtab *pVtab, int nArg, const char *zName, 5533 void (**pxFunc)(sqlite3_context*,int,sqlite3_value**), 5534 void **ppArg); 5535 int (*xRename)(sqlite3_vtab *pVtab, const char *zNew); 5536 /* The methods above are in version 1 of the sqlite_module object. Those 5537 ** below are for version 2 and greater. */ 5538 int (*xSavepoint)(sqlite3_vtab *pVTab, int); 5539 int (*xRelease)(sqlite3_vtab *pVTab, int); 5540 int (*xRollbackTo)(sqlite3_vtab *pVTab, int); 5541}; 5542 5543/* 5544** CAPI3REF: Virtual Table Indexing Information 5545** KEYWORDS: sqlite3_index_info 5546** 5547** The sqlite3_index_info structure and its substructures is used as part 5548** of the [virtual table] interface to 5549** pass information into and receive the reply from the [xBestIndex] 5550** method of a [virtual table module]. The fields under **Inputs** are the 5551** inputs to xBestIndex and are read-only. xBestIndex inserts its 5552** results into the **Outputs** fields. 5553** 5554** ^(The aConstraint[] array records WHERE clause constraints of the form: 5555** 5556** <blockquote>column OP expr</blockquote> 5557** 5558** where OP is =, <, <=, >, or >=.)^ ^(The particular operator is 5559** stored in aConstraint[].op using one of the 5560** [SQLITE_INDEX_CONSTRAINT_EQ | SQLITE_INDEX_CONSTRAINT_ values].)^ 5561** ^(The index of the column is stored in 5562** aConstraint[].iColumn.)^ ^(aConstraint[].usable is TRUE if the 5563** expr on the right-hand side can be evaluated (and thus the constraint 5564** is usable) and false if it cannot.)^ 5565** 5566** ^The optimizer automatically inverts terms of the form "expr OP column" 5567** and makes other simplifications to the WHERE clause in an attempt to 5568** get as many WHERE clause terms into the form shown above as possible. 5569** ^The aConstraint[] array only reports WHERE clause terms that are 5570** relevant to the particular virtual table being queried. 5571** 5572** ^Information about the ORDER BY clause is stored in aOrderBy[]. 5573** ^Each term of aOrderBy records a column of the ORDER BY clause. 5574** 5575** The [xBestIndex] method must fill aConstraintUsage[] with information 5576** about what parameters to pass to xFilter. ^If argvIndex>0 then 5577** the right-hand side of the corresponding aConstraint[] is evaluated 5578** and becomes the argvIndex-th entry in argv. ^(If aConstraintUsage[].omit 5579** is true, then the constraint is assumed to be fully handled by the 5580** virtual table and is not checked again by SQLite.)^ 5581** 5582** ^The idxNum and idxPtr values are recorded and passed into the 5583** [xFilter] method. 5584** ^[sqlite3_free()] is used to free idxPtr if and only if 5585** needToFreeIdxPtr is true. 5586** 5587** ^The orderByConsumed means that output from [xFilter]/[xNext] will occur in 5588** the correct order to satisfy the ORDER BY clause so that no separate 5589** sorting step is required. 5590** 5591** ^The estimatedCost value is an estimate of the cost of a particular 5592** strategy. A cost of N indicates that the cost of the strategy is similar 5593** to a linear scan of an SQLite table with N rows. A cost of log(N) 5594** indicates that the expense of the operation is similar to that of a 5595** binary search on a unique indexed field of an SQLite table with N rows. 5596** 5597** ^The estimatedRows value is an estimate of the number of rows that 5598** will be returned by the strategy. 5599** 5600** IMPORTANT: The estimatedRows field was added to the sqlite3_index_info 5601** structure for SQLite version 3.8.2. If a virtual table extension is 5602** used with an SQLite version earlier than 3.8.2, the results of attempting 5603** to read or write the estimatedRows field are undefined (but are likely 5604** to included crashing the application). The estimatedRows field should 5605** therefore only be used if [sqlite3_libversion_number()] returns a 5606** value greater than or equal to 3008002. 5607*/ 5608struct sqlite3_index_info { 5609 /* Inputs */ 5610 int nConstraint; /* Number of entries in aConstraint */ 5611 struct sqlite3_index_constraint { 5612 int iColumn; /* Column on left-hand side of constraint */ 5613 unsigned char op; /* Constraint operator */ 5614 unsigned char usable; /* True if this constraint is usable */ 5615 int iTermOffset; /* Used internally - xBestIndex should ignore */ 5616 } *aConstraint; /* Table of WHERE clause constraints */ 5617 int nOrderBy; /* Number of terms in the ORDER BY clause */ 5618 struct sqlite3_index_orderby { 5619 int iColumn; /* Column number */ 5620 unsigned char desc; /* True for DESC. False for ASC. */ 5621 } *aOrderBy; /* The ORDER BY clause */ 5622 /* Outputs */ 5623 struct sqlite3_index_constraint_usage { 5624 int argvIndex; /* if >0, constraint is part of argv to xFilter */ 5625 unsigned char omit; /* Do not code a test for this constraint */ 5626 } *aConstraintUsage; 5627 int idxNum; /* Number used to identify the index */ 5628 char *idxStr; /* String, possibly obtained from sqlite3_malloc */ 5629 int needToFreeIdxStr; /* Free idxStr using sqlite3_free() if true */ 5630 int orderByConsumed; /* True if output is already ordered */ 5631 double estimatedCost; /* Estimated cost of using this index */ 5632 /* Fields below are only available in SQLite 3.8.2 and later */ 5633 sqlite3_int64 estimatedRows; /* Estimated number of rows returned */ 5634}; 5635 5636/* 5637** CAPI3REF: Virtual Table Constraint Operator Codes 5638** 5639** These macros defined the allowed values for the 5640** [sqlite3_index_info].aConstraint[].op field. Each value represents 5641** an operator that is part of a constraint term in the wHERE clause of 5642** a query that uses a [virtual table]. 5643*/ 5644#define SQLITE_INDEX_CONSTRAINT_EQ 2 5645#define SQLITE_INDEX_CONSTRAINT_GT 4 5646#define SQLITE_INDEX_CONSTRAINT_LE 8 5647#define SQLITE_INDEX_CONSTRAINT_LT 16 5648#define SQLITE_INDEX_CONSTRAINT_GE 32 5649#define SQLITE_INDEX_CONSTRAINT_MATCH 64 5650 5651/* 5652** CAPI3REF: Register A Virtual Table Implementation 5653** METHOD: sqlite3 5654** 5655** ^These routines are used to register a new [virtual table module] name. 5656** ^Module names must be registered before 5657** creating a new [virtual table] using the module and before using a 5658** preexisting [virtual table] for the module. 5659** 5660** ^The module name is registered on the [database connection] specified 5661** by the first parameter. ^The name of the module is given by the 5662** second parameter. ^The third parameter is a pointer to 5663** the implementation of the [virtual table module]. ^The fourth 5664** parameter is an arbitrary client data pointer that is passed through 5665** into the [xCreate] and [xConnect] methods of the virtual table module 5666** when a new virtual table is be being created or reinitialized. 5667** 5668** ^The sqlite3_create_module_v2() interface has a fifth parameter which 5669** is a pointer to a destructor for the pClientData. ^SQLite will 5670** invoke the destructor function (if it is not NULL) when SQLite 5671** no longer needs the pClientData pointer. ^The destructor will also 5672** be invoked if the call to sqlite3_create_module_v2() fails. 5673** ^The sqlite3_create_module() 5674** interface is equivalent to sqlite3_create_module_v2() with a NULL 5675** destructor. 5676*/ 5677int sqlite3_create_module( 5678 sqlite3 *db, /* SQLite connection to register module with */ 5679 const char *zName, /* Name of the module */ 5680 const sqlite3_module *p, /* Methods for the module */ 5681 void *pClientData /* Client data for xCreate/xConnect */ 5682); 5683int sqlite3_create_module_v2( 5684 sqlite3 *db, /* SQLite connection to register module with */ 5685 const char *zName, /* Name of the module */ 5686 const sqlite3_module *p, /* Methods for the module */ 5687 void *pClientData, /* Client data for xCreate/xConnect */ 5688 void(*xDestroy)(void*) /* Module destructor function */ 5689); 5690 5691/* 5692** CAPI3REF: Virtual Table Instance Object 5693** KEYWORDS: sqlite3_vtab 5694** 5695** Every [virtual table module] implementation uses a subclass 5696** of this object to describe a particular instance 5697** of the [virtual table]. Each subclass will 5698** be tailored to the specific needs of the module implementation. 5699** The purpose of this superclass is to define certain fields that are 5700** common to all module implementations. 5701** 5702** ^Virtual tables methods can set an error message by assigning a 5703** string obtained from [sqlite3_mprintf()] to zErrMsg. The method should 5704** take care that any prior string is freed by a call to [sqlite3_free()] 5705** prior to assigning a new string to zErrMsg. ^After the error message 5706** is delivered up to the client application, the string will be automatically 5707** freed by sqlite3_free() and the zErrMsg field will be zeroed. 5708*/ 5709struct sqlite3_vtab { 5710 const sqlite3_module *pModule; /* The module for this virtual table */ 5711 int nRef; /* Number of open cursors */ 5712 char *zErrMsg; /* Error message from sqlite3_mprintf() */ 5713 /* Virtual table implementations will typically add additional fields */ 5714}; 5715 5716/* 5717** CAPI3REF: Virtual Table Cursor Object 5718** KEYWORDS: sqlite3_vtab_cursor {virtual table cursor} 5719** 5720** Every [virtual table module] implementation uses a subclass of the 5721** following structure to describe cursors that point into the 5722** [virtual table] and are used 5723** to loop through the virtual table. Cursors are created using the 5724** [sqlite3_module.xOpen | xOpen] method of the module and are destroyed 5725** by the [sqlite3_module.xClose | xClose] method. Cursors are used 5726** by the [xFilter], [xNext], [xEof], [xColumn], and [xRowid] methods 5727** of the module. Each module implementation will define 5728** the content of a cursor structure to suit its own needs. 5729** 5730** This superclass exists in order to define fields of the cursor that 5731** are common to all implementations. 5732*/ 5733struct sqlite3_vtab_cursor { 5734 sqlite3_vtab *pVtab; /* Virtual table of this cursor */ 5735 /* Virtual table implementations will typically add additional fields */ 5736}; 5737 5738/* 5739** CAPI3REF: Declare The Schema Of A Virtual Table 5740** 5741** ^The [xCreate] and [xConnect] methods of a 5742** [virtual table module] call this interface 5743** to declare the format (the names and datatypes of the columns) of 5744** the virtual tables they implement. 5745*/ 5746int sqlite3_declare_vtab(sqlite3*, const char *zSQL); 5747 5748/* 5749** CAPI3REF: Overload A Function For A Virtual Table 5750** METHOD: sqlite3 5751** 5752** ^(Virtual tables can provide alternative implementations of functions 5753** using the [xFindFunction] method of the [virtual table module]. 5754** But global versions of those functions 5755** must exist in order to be overloaded.)^ 5756** 5757** ^(This API makes sure a global version of a function with a particular 5758** name and number of parameters exists. If no such function exists 5759** before this API is called, a new function is created.)^ ^The implementation 5760** of the new function always causes an exception to be thrown. So 5761** the new function is not good for anything by itself. Its only 5762** purpose is to be a placeholder function that can be overloaded 5763** by a [virtual table]. 5764*/ 5765int sqlite3_overload_function(sqlite3*, const char *zFuncName, int nArg); 5766 5767/* 5768** The interface to the virtual-table mechanism defined above (back up 5769** to a comment remarkably similar to this one) is currently considered 5770** to be experimental. The interface might change in incompatible ways. 5771** If this is a problem for you, do not use the interface at this time. 5772** 5773** When the virtual-table mechanism stabilizes, we will declare the 5774** interface fixed, support it indefinitely, and remove this comment. 5775*/ 5776 5777/* 5778** CAPI3REF: A Handle To An Open BLOB 5779** KEYWORDS: {BLOB handle} {BLOB handles} 5780** 5781** An instance of this object represents an open BLOB on which 5782** [sqlite3_blob_open | incremental BLOB I/O] can be performed. 5783** ^Objects of this type are created by [sqlite3_blob_open()] 5784** and destroyed by [sqlite3_blob_close()]. 5785** ^The [sqlite3_blob_read()] and [sqlite3_blob_write()] interfaces 5786** can be used to read or write small subsections of the BLOB. 5787** ^The [sqlite3_blob_bytes()] interface returns the size of the BLOB in bytes. 5788*/ 5789typedef struct sqlite3_blob sqlite3_blob; 5790 5791/* 5792** CAPI3REF: Open A BLOB For Incremental I/O 5793** METHOD: sqlite3 5794** CONSTRUCTOR: sqlite3_blob 5795** 5796** ^(This interfaces opens a [BLOB handle | handle] to the BLOB located 5797** in row iRow, column zColumn, table zTable in database zDb; 5798** in other words, the same BLOB that would be selected by: 5799** 5800** <pre> 5801** SELECT zColumn FROM zDb.zTable WHERE [rowid] = iRow; 5802** </pre>)^ 5803** 5804** ^(Parameter zDb is not the filename that contains the database, but 5805** rather the symbolic name of the database. For attached databases, this is 5806** the name that appears after the AS keyword in the [ATTACH] statement. 5807** For the main database file, the database name is "main". For TEMP 5808** tables, the database name is "temp".)^ 5809** 5810** ^If the flags parameter is non-zero, then the BLOB is opened for read 5811** and write access. ^If the flags parameter is zero, the BLOB is opened for 5812** read-only access. 5813** 5814** ^(On success, [SQLITE_OK] is returned and the new [BLOB handle] is stored 5815** in *ppBlob. Otherwise an [error code] is returned and, unless the error 5816** code is SQLITE_MISUSE, *ppBlob is set to NULL.)^ ^This means that, provided 5817** the API is not misused, it is always safe to call [sqlite3_blob_close()] 5818** on *ppBlob after this function it returns. 5819** 5820** This function fails with SQLITE_ERROR if any of the following are true: 5821** <ul> 5822** <li> ^(Database zDb does not exist)^, 5823** <li> ^(Table zTable does not exist within database zDb)^, 5824** <li> ^(Table zTable is a WITHOUT ROWID table)^, 5825** <li> ^(Column zColumn does not exist)^, 5826** <li> ^(Row iRow is not present in the table)^, 5827** <li> ^(The specified column of row iRow contains a value that is not 5828** a TEXT or BLOB value)^, 5829** <li> ^(Column zColumn is part of an index, PRIMARY KEY or UNIQUE 5830** constraint and the blob is being opened for read/write access)^, 5831** <li> ^([foreign key constraints | Foreign key constraints] are enabled, 5832** column zColumn is part of a [child key] definition and the blob is 5833** being opened for read/write access)^. 5834** </ul> 5835** 5836** ^Unless it returns SQLITE_MISUSE, this function sets the 5837** [database connection] error code and message accessible via 5838** [sqlite3_errcode()] and [sqlite3_errmsg()] and related functions. 5839** 5840** 5841** ^(If the row that a BLOB handle points to is modified by an 5842** [UPDATE], [DELETE], or by [ON CONFLICT] side-effects 5843** then the BLOB handle is marked as "expired". 5844** This is true if any column of the row is changed, even a column 5845** other than the one the BLOB handle is open on.)^ 5846** ^Calls to [sqlite3_blob_read()] and [sqlite3_blob_write()] for 5847** an expired BLOB handle fail with a return code of [SQLITE_ABORT]. 5848** ^(Changes written into a BLOB prior to the BLOB expiring are not 5849** rolled back by the expiration of the BLOB. Such changes will eventually 5850** commit if the transaction continues to completion.)^ 5851** 5852** ^Use the [sqlite3_blob_bytes()] interface to determine the size of 5853** the opened blob. ^The size of a blob may not be changed by this 5854** interface. Use the [UPDATE] SQL command to change the size of a 5855** blob. 5856** 5857** ^The [sqlite3_bind_zeroblob()] and [sqlite3_result_zeroblob()] interfaces 5858** and the built-in [zeroblob] SQL function may be used to create a 5859** zero-filled blob to read or write using the incremental-blob interface. 5860** 5861** To avoid a resource leak, every open [BLOB handle] should eventually 5862** be released by a call to [sqlite3_blob_close()]. 5863*/ 5864int sqlite3_blob_open( 5865 sqlite3*, 5866 const char *zDb, 5867 const char *zTable, 5868 const char *zColumn, 5869 sqlite3_int64 iRow, 5870 int flags, 5871 sqlite3_blob **ppBlob 5872); 5873 5874/* 5875** CAPI3REF: Move a BLOB Handle to a New Row 5876** METHOD: sqlite3_blob 5877** 5878** ^This function is used to move an existing blob handle so that it points 5879** to a different row of the same database table. ^The new row is identified 5880** by the rowid value passed as the second argument. Only the row can be 5881** changed. ^The database, table and column on which the blob handle is open 5882** remain the same. Moving an existing blob handle to a new row can be 5883** faster than closing the existing handle and opening a new one. 5884** 5885** ^(The new row must meet the same criteria as for [sqlite3_blob_open()] - 5886** it must exist and there must be either a blob or text value stored in 5887** the nominated column.)^ ^If the new row is not present in the table, or if 5888** it does not contain a blob or text value, or if another error occurs, an 5889** SQLite error code is returned and the blob handle is considered aborted. 5890** ^All subsequent calls to [sqlite3_blob_read()], [sqlite3_blob_write()] or 5891** [sqlite3_blob_reopen()] on an aborted blob handle immediately return 5892** SQLITE_ABORT. ^Calling [sqlite3_blob_bytes()] on an aborted blob handle 5893** always returns zero. 5894** 5895** ^This function sets the database handle error code and message. 5896*/ 5897int sqlite3_blob_reopen(sqlite3_blob *, sqlite3_int64); 5898 5899/* 5900** CAPI3REF: Close A BLOB Handle 5901** DESTRUCTOR: sqlite3_blob 5902** 5903** ^This function closes an open [BLOB handle]. ^(The BLOB handle is closed 5904** unconditionally. Even if this routine returns an error code, the 5905** handle is still closed.)^ 5906** 5907** ^If the blob handle being closed was opened for read-write access, and if 5908** the database is in auto-commit mode and there are no other open read-write 5909** blob handles or active write statements, the current transaction is 5910** committed. ^If an error occurs while committing the transaction, an error 5911** code is returned and the transaction rolled back. 5912** 5913** Calling this function with an argument that is not a NULL pointer or an 5914** open blob handle results in undefined behaviour. ^Calling this routine 5915** with a null pointer (such as would be returned by a failed call to 5916** [sqlite3_blob_open()]) is a harmless no-op. ^Otherwise, if this function 5917** is passed a valid open blob handle, the values returned by the 5918** sqlite3_errcode() and sqlite3_errmsg() functions are set before returning. 5919*/ 5920int sqlite3_blob_close(sqlite3_blob *); 5921 5922/* 5923** CAPI3REF: Return The Size Of An Open BLOB 5924** METHOD: sqlite3_blob 5925** 5926** ^Returns the size in bytes of the BLOB accessible via the 5927** successfully opened [BLOB handle] in its only argument. ^The 5928** incremental blob I/O routines can only read or overwriting existing 5929** blob content; they cannot change the size of a blob. 5930** 5931** This routine only works on a [BLOB handle] which has been created 5932** by a prior successful call to [sqlite3_blob_open()] and which has not 5933** been closed by [sqlite3_blob_close()]. Passing any other pointer in 5934** to this routine results in undefined and probably undesirable behavior. 5935*/ 5936int sqlite3_blob_bytes(sqlite3_blob *); 5937 5938/* 5939** CAPI3REF: Read Data From A BLOB Incrementally 5940** METHOD: sqlite3_blob 5941** 5942** ^(This function is used to read data from an open [BLOB handle] into a 5943** caller-supplied buffer. N bytes of data are copied into buffer Z 5944** from the open BLOB, starting at offset iOffset.)^ 5945** 5946** ^If offset iOffset is less than N bytes from the end of the BLOB, 5947** [SQLITE_ERROR] is returned and no data is read. ^If N or iOffset is 5948** less than zero, [SQLITE_ERROR] is returned and no data is read. 5949** ^The size of the blob (and hence the maximum value of N+iOffset) 5950** can be determined using the [sqlite3_blob_bytes()] interface. 5951** 5952** ^An attempt to read from an expired [BLOB handle] fails with an 5953** error code of [SQLITE_ABORT]. 5954** 5955** ^(On success, sqlite3_blob_read() returns SQLITE_OK. 5956** Otherwise, an [error code] or an [extended error code] is returned.)^ 5957** 5958** This routine only works on a [BLOB handle] which has been created 5959** by a prior successful call to [sqlite3_blob_open()] and which has not 5960** been closed by [sqlite3_blob_close()]. Passing any other pointer in 5961** to this routine results in undefined and probably undesirable behavior. 5962** 5963** See also: [sqlite3_blob_write()]. 5964*/ 5965int sqlite3_blob_read(sqlite3_blob *, void *Z, int N, int iOffset); 5966 5967/* 5968** CAPI3REF: Write Data Into A BLOB Incrementally 5969** METHOD: sqlite3_blob 5970** 5971** ^(This function is used to write data into an open [BLOB handle] from a 5972** caller-supplied buffer. N bytes of data are copied from the buffer Z 5973** into the open BLOB, starting at offset iOffset.)^ 5974** 5975** ^(On success, sqlite3_blob_write() returns SQLITE_OK. 5976** Otherwise, an [error code] or an [extended error code] is returned.)^ 5977** ^Unless SQLITE_MISUSE is returned, this function sets the 5978** [database connection] error code and message accessible via 5979** [sqlite3_errcode()] and [sqlite3_errmsg()] and related functions. 5980** 5981** ^If the [BLOB handle] passed as the first argument was not opened for 5982** writing (the flags parameter to [sqlite3_blob_open()] was zero), 5983** this function returns [SQLITE_READONLY]. 5984** 5985** This function may only modify the contents of the BLOB; it is 5986** not possible to increase the size of a BLOB using this API. 5987** ^If offset iOffset is less than N bytes from the end of the BLOB, 5988** [SQLITE_ERROR] is returned and no data is written. The size of the 5989** BLOB (and hence the maximum value of N+iOffset) can be determined 5990** using the [sqlite3_blob_bytes()] interface. ^If N or iOffset are less 5991** than zero [SQLITE_ERROR] is returned and no data is written. 5992** 5993** ^An attempt to write to an expired [BLOB handle] fails with an 5994** error code of [SQLITE_ABORT]. ^Writes to the BLOB that occurred 5995** before the [BLOB handle] expired are not rolled back by the 5996** expiration of the handle, though of course those changes might 5997** have been overwritten by the statement that expired the BLOB handle 5998** or by other independent statements. 5999** 6000** This routine only works on a [BLOB handle] which has been created 6001** by a prior successful call to [sqlite3_blob_open()] and which has not 6002** been closed by [sqlite3_blob_close()]. Passing any other pointer in 6003** to this routine results in undefined and probably undesirable behavior. 6004** 6005** See also: [sqlite3_blob_read()]. 6006*/ 6007int sqlite3_blob_write(sqlite3_blob *, const void *z, int n, int iOffset); 6008 6009/* 6010** CAPI3REF: Virtual File System Objects 6011** 6012** A virtual filesystem (VFS) is an [sqlite3_vfs] object 6013** that SQLite uses to interact 6014** with the underlying operating system. Most SQLite builds come with a 6015** single default VFS that is appropriate for the host computer. 6016** New VFSes can be registered and existing VFSes can be unregistered. 6017** The following interfaces are provided. 6018** 6019** ^The sqlite3_vfs_find() interface returns a pointer to a VFS given its name. 6020** ^Names are case sensitive. 6021** ^Names are zero-terminated UTF-8 strings. 6022** ^If there is no match, a NULL pointer is returned. 6023** ^If zVfsName is NULL then the default VFS is returned. 6024** 6025** ^New VFSes are registered with sqlite3_vfs_register(). 6026** ^Each new VFS becomes the default VFS if the makeDflt flag is set. 6027** ^The same VFS can be registered multiple times without injury. 6028** ^To make an existing VFS into the default VFS, register it again 6029** with the makeDflt flag set. If two different VFSes with the 6030** same name are registered, the behavior is undefined. If a 6031** VFS is registered with a name that is NULL or an empty string, 6032** then the behavior is undefined. 6033** 6034** ^Unregister a VFS with the sqlite3_vfs_unregister() interface. 6035** ^(If the default VFS is unregistered, another VFS is chosen as 6036** the default. The choice for the new VFS is arbitrary.)^ 6037*/ 6038sqlite3_vfs *sqlite3_vfs_find(const char *zVfsName); 6039int sqlite3_vfs_register(sqlite3_vfs*, int makeDflt); 6040int sqlite3_vfs_unregister(sqlite3_vfs*); 6041 6042/* 6043** CAPI3REF: Mutexes 6044** 6045** The SQLite core uses these routines for thread 6046** synchronization. Though they are intended for internal 6047** use by SQLite, code that links against SQLite is 6048** permitted to use any of these routines. 6049** 6050** The SQLite source code contains multiple implementations 6051** of these mutex routines. An appropriate implementation 6052** is selected automatically at compile-time. The following 6053** implementations are available in the SQLite core: 6054** 6055** <ul> 6056** <li> SQLITE_MUTEX_PTHREADS 6057** <li> SQLITE_MUTEX_W32 6058** <li> SQLITE_MUTEX_NOOP 6059** </ul> 6060** 6061** The SQLITE_MUTEX_NOOP implementation is a set of routines 6062** that does no real locking and is appropriate for use in 6063** a single-threaded application. The SQLITE_MUTEX_PTHREADS and 6064** SQLITE_MUTEX_W32 implementations are appropriate for use on Unix 6065** and Windows. 6066** 6067** If SQLite is compiled with the SQLITE_MUTEX_APPDEF preprocessor 6068** macro defined (with "-DSQLITE_MUTEX_APPDEF=1"), then no mutex 6069** implementation is included with the library. In this case the 6070** application must supply a custom mutex implementation using the 6071** [SQLITE_CONFIG_MUTEX] option of the sqlite3_config() function 6072** before calling sqlite3_initialize() or any other public sqlite3_ 6073** function that calls sqlite3_initialize(). 6074** 6075** ^The sqlite3_mutex_alloc() routine allocates a new 6076** mutex and returns a pointer to it. ^The sqlite3_mutex_alloc() 6077** routine returns NULL if it is unable to allocate the requested 6078** mutex. The argument to sqlite3_mutex_alloc() must one of these 6079** integer constants: 6080** 6081** <ul> 6082** <li> SQLITE_MUTEX_FAST 6083** <li> SQLITE_MUTEX_RECURSIVE 6084** <li> SQLITE_MUTEX_STATIC_MASTER 6085** <li> SQLITE_MUTEX_STATIC_MEM 6086** <li> SQLITE_MUTEX_STATIC_OPEN 6087** <li> SQLITE_MUTEX_STATIC_PRNG 6088** <li> SQLITE_MUTEX_STATIC_LRU 6089** <li> SQLITE_MUTEX_STATIC_PMEM 6090** <li> SQLITE_MUTEX_STATIC_APP1 6091** <li> SQLITE_MUTEX_STATIC_APP2 6092** <li> SQLITE_MUTEX_STATIC_APP3 6093** </ul> 6094** 6095** ^The first two constants (SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE) 6096** cause sqlite3_mutex_alloc() to create 6097** a new mutex. ^The new mutex is recursive when SQLITE_MUTEX_RECURSIVE 6098** is used but not necessarily so when SQLITE_MUTEX_FAST is used. 6099** The mutex implementation does not need to make a distinction 6100** between SQLITE_MUTEX_RECURSIVE and SQLITE_MUTEX_FAST if it does 6101** not want to. SQLite will only request a recursive mutex in 6102** cases where it really needs one. If a faster non-recursive mutex 6103** implementation is available on the host platform, the mutex subsystem 6104** might return such a mutex in response to SQLITE_MUTEX_FAST. 6105** 6106** ^The other allowed parameters to sqlite3_mutex_alloc() (anything other 6107** than SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE) each return 6108** a pointer to a static preexisting mutex. ^Nine static mutexes are 6109** used by the current version of SQLite. Future versions of SQLite 6110** may add additional static mutexes. Static mutexes are for internal 6111** use by SQLite only. Applications that use SQLite mutexes should 6112** use only the dynamic mutexes returned by SQLITE_MUTEX_FAST or 6113** SQLITE_MUTEX_RECURSIVE. 6114** 6115** ^Note that if one of the dynamic mutex parameters (SQLITE_MUTEX_FAST 6116** or SQLITE_MUTEX_RECURSIVE) is used then sqlite3_mutex_alloc() 6117** returns a different mutex on every call. ^For the static 6118** mutex types, the same mutex is returned on every call that has 6119** the same type number. 6120** 6121** ^The sqlite3_mutex_free() routine deallocates a previously 6122** allocated dynamic mutex. Attempting to deallocate a static 6123** mutex results in undefined behavior. 6124** 6125** ^The sqlite3_mutex_enter() and sqlite3_mutex_try() routines attempt 6126** to enter a mutex. ^If another thread is already within the mutex, 6127** sqlite3_mutex_enter() will block and sqlite3_mutex_try() will return 6128** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK] 6129** upon successful entry. ^(Mutexes created using 6130** SQLITE_MUTEX_RECURSIVE can be entered multiple times by the same thread. 6131** In such cases, the 6132** mutex must be exited an equal number of times before another thread 6133** can enter.)^ If the same thread tries to enter any mutex other 6134** than an SQLITE_MUTEX_RECURSIVE more than once, the behavior is undefined. 6135** 6136** ^(Some systems (for example, Windows 95) do not support the operation 6137** implemented by sqlite3_mutex_try(). On those systems, sqlite3_mutex_try() 6138** will always return SQLITE_BUSY. The SQLite core only ever uses 6139** sqlite3_mutex_try() as an optimization so this is acceptable 6140** behavior.)^ 6141** 6142** ^The sqlite3_mutex_leave() routine exits a mutex that was 6143** previously entered by the same thread. The behavior 6144** is undefined if the mutex is not currently entered by the 6145** calling thread or is not currently allocated. 6146** 6147** ^If the argument to sqlite3_mutex_enter(), sqlite3_mutex_try(), or 6148** sqlite3_mutex_leave() is a NULL pointer, then all three routines 6149** behave as no-ops. 6150** 6151** See also: [sqlite3_mutex_held()] and [sqlite3_mutex_notheld()]. 6152*/ 6153sqlite3_mutex *sqlite3_mutex_alloc(int); 6154void sqlite3_mutex_free(sqlite3_mutex*); 6155void sqlite3_mutex_enter(sqlite3_mutex*); 6156int sqlite3_mutex_try(sqlite3_mutex*); 6157void sqlite3_mutex_leave(sqlite3_mutex*); 6158 6159/* 6160** CAPI3REF: Mutex Methods Object 6161** 6162** An instance of this structure defines the low-level routines 6163** used to allocate and use mutexes. 6164** 6165** Usually, the default mutex implementations provided by SQLite are 6166** sufficient, however the application has the option of substituting a custom 6167** implementation for specialized deployments or systems for which SQLite 6168** does not provide a suitable implementation. In this case, the application 6169** creates and populates an instance of this structure to pass 6170** to sqlite3_config() along with the [SQLITE_CONFIG_MUTEX] option. 6171** Additionally, an instance of this structure can be used as an 6172** output variable when querying the system for the current mutex 6173** implementation, using the [SQLITE_CONFIG_GETMUTEX] option. 6174** 6175** ^The xMutexInit method defined by this structure is invoked as 6176** part of system initialization by the sqlite3_initialize() function. 6177** ^The xMutexInit routine is called by SQLite exactly once for each 6178** effective call to [sqlite3_initialize()]. 6179** 6180** ^The xMutexEnd method defined by this structure is invoked as 6181** part of system shutdown by the sqlite3_shutdown() function. The 6182** implementation of this method is expected to release all outstanding 6183** resources obtained by the mutex methods implementation, especially 6184** those obtained by the xMutexInit method. ^The xMutexEnd() 6185** interface is invoked exactly once for each call to [sqlite3_shutdown()]. 6186** 6187** ^(The remaining seven methods defined by this structure (xMutexAlloc, 6188** xMutexFree, xMutexEnter, xMutexTry, xMutexLeave, xMutexHeld and 6189** xMutexNotheld) implement the following interfaces (respectively): 6190** 6191** <ul> 6192** <li> [sqlite3_mutex_alloc()] </li> 6193** <li> [sqlite3_mutex_free()] </li> 6194** <li> [sqlite3_mutex_enter()] </li> 6195** <li> [sqlite3_mutex_try()] </li> 6196** <li> [sqlite3_mutex_leave()] </li> 6197** <li> [sqlite3_mutex_held()] </li> 6198** <li> [sqlite3_mutex_notheld()] </li> 6199** </ul>)^ 6200** 6201** The only difference is that the public sqlite3_XXX functions enumerated 6202** above silently ignore any invocations that pass a NULL pointer instead 6203** of a valid mutex handle. The implementations of the methods defined 6204** by this structure are not required to handle this case, the results 6205** of passing a NULL pointer instead of a valid mutex handle are undefined 6206** (i.e. it is acceptable to provide an implementation that segfaults if 6207** it is passed a NULL pointer). 6208** 6209** The xMutexInit() method must be threadsafe. It must be harmless to 6210** invoke xMutexInit() multiple times within the same process and without 6211** intervening calls to xMutexEnd(). Second and subsequent calls to 6212** xMutexInit() must be no-ops. 6213** 6214** xMutexInit() must not use SQLite memory allocation ([sqlite3_malloc()] 6215** and its associates). Similarly, xMutexAlloc() must not use SQLite memory 6216** allocation for a static mutex. ^However xMutexAlloc() may use SQLite 6217** memory allocation for a fast or recursive mutex. 6218** 6219** ^SQLite will invoke the xMutexEnd() method when [sqlite3_shutdown()] is 6220** called, but only if the prior call to xMutexInit returned SQLITE_OK. 6221** If xMutexInit fails in any way, it is expected to clean up after itself 6222** prior to returning. 6223*/ 6224typedef struct sqlite3_mutex_methods sqlite3_mutex_methods; 6225struct sqlite3_mutex_methods { 6226 int (*xMutexInit)(void); 6227 int (*xMutexEnd)(void); 6228 sqlite3_mutex *(*xMutexAlloc)(int); 6229 void (*xMutexFree)(sqlite3_mutex *); 6230 void (*xMutexEnter)(sqlite3_mutex *); 6231 int (*xMutexTry)(sqlite3_mutex *); 6232 void (*xMutexLeave)(sqlite3_mutex *); 6233 int (*xMutexHeld)(sqlite3_mutex *); 6234 int (*xMutexNotheld)(sqlite3_mutex *); 6235}; 6236 6237/* 6238** CAPI3REF: Mutex Verification Routines 6239** 6240** The sqlite3_mutex_held() and sqlite3_mutex_notheld() routines 6241** are intended for use inside assert() statements. The SQLite core 6242** never uses these routines except inside an assert() and applications 6243** are advised to follow the lead of the core. The SQLite core only 6244** provides implementations for these routines when it is compiled 6245** with the SQLITE_DEBUG flag. External mutex implementations 6246** are only required to provide these routines if SQLITE_DEBUG is 6247** defined and if NDEBUG is not defined. 6248** 6249** These routines should return true if the mutex in their argument 6250** is held or not held, respectively, by the calling thread. 6251** 6252** The implementation is not required to provide versions of these 6253** routines that actually work. If the implementation does not provide working 6254** versions of these routines, it should at least provide stubs that always 6255** return true so that one does not get spurious assertion failures. 6256** 6257** If the argument to sqlite3_mutex_held() is a NULL pointer then 6258** the routine should return 1. This seems counter-intuitive since 6259** clearly the mutex cannot be held if it does not exist. But 6260** the reason the mutex does not exist is because the build is not 6261** using mutexes. And we do not want the assert() containing the 6262** call to sqlite3_mutex_held() to fail, so a non-zero return is 6263** the appropriate thing to do. The sqlite3_mutex_notheld() 6264** interface should also return 1 when given a NULL pointer. 6265*/ 6266#ifndef NDEBUG 6267int sqlite3_mutex_held(sqlite3_mutex*); 6268int sqlite3_mutex_notheld(sqlite3_mutex*); 6269#endif 6270 6271/* 6272** CAPI3REF: Mutex Types 6273** 6274** The [sqlite3_mutex_alloc()] interface takes a single argument 6275** which is one of these integer constants. 6276** 6277** The set of static mutexes may change from one SQLite release to the 6278** next. Applications that override the built-in mutex logic must be 6279** prepared to accommodate additional static mutexes. 6280*/ 6281#define SQLITE_MUTEX_FAST 0 6282#define SQLITE_MUTEX_RECURSIVE 1 6283#define SQLITE_MUTEX_STATIC_MASTER 2 6284#define SQLITE_MUTEX_STATIC_MEM 3 /* sqlite3_malloc() */ 6285#define SQLITE_MUTEX_STATIC_MEM2 4 /* NOT USED */ 6286#define SQLITE_MUTEX_STATIC_OPEN 4 /* sqlite3BtreeOpen() */ 6287#define SQLITE_MUTEX_STATIC_PRNG 5 /* sqlite3_random() */ 6288#define SQLITE_MUTEX_STATIC_LRU 6 /* lru page list */ 6289#define SQLITE_MUTEX_STATIC_LRU2 7 /* NOT USED */ 6290#define SQLITE_MUTEX_STATIC_PMEM 7 /* sqlite3PageMalloc() */ 6291#define SQLITE_MUTEX_STATIC_APP1 8 /* For use by application */ 6292#define SQLITE_MUTEX_STATIC_APP2 9 /* For use by application */ 6293#define SQLITE_MUTEX_STATIC_APP3 10 /* For use by application */ 6294#define SQLITE_MUTEX_STATIC_VFS1 11 /* For use by built-in VFS */ 6295#define SQLITE_MUTEX_STATIC_VFS2 12 /* For use by extension VFS */ 6296#define SQLITE_MUTEX_STATIC_VFS3 13 /* For use by application VFS */ 6297 6298/* 6299** CAPI3REF: Retrieve the mutex for a database connection 6300** METHOD: sqlite3 6301** 6302** ^This interface returns a pointer the [sqlite3_mutex] object that 6303** serializes access to the [database connection] given in the argument 6304** when the [threading mode] is Serialized. 6305** ^If the [threading mode] is Single-thread or Multi-thread then this 6306** routine returns a NULL pointer. 6307*/ 6308sqlite3_mutex *sqlite3_db_mutex(sqlite3*); 6309 6310/* 6311** CAPI3REF: Low-Level Control Of Database Files 6312** METHOD: sqlite3 6313** 6314** ^The [sqlite3_file_control()] interface makes a direct call to the 6315** xFileControl method for the [sqlite3_io_methods] object associated 6316** with a particular database identified by the second argument. ^The 6317** name of the database is "main" for the main database or "temp" for the 6318** TEMP database, or the name that appears after the AS keyword for 6319** databases that are added using the [ATTACH] SQL command. 6320** ^A NULL pointer can be used in place of "main" to refer to the 6321** main database file. 6322** ^The third and fourth parameters to this routine 6323** are passed directly through to the second and third parameters of 6324** the xFileControl method. ^The return value of the xFileControl 6325** method becomes the return value of this routine. 6326** 6327** ^The SQLITE_FCNTL_FILE_POINTER value for the op parameter causes 6328** a pointer to the underlying [sqlite3_file] object to be written into 6329** the space pointed to by the 4th parameter. ^The SQLITE_FCNTL_FILE_POINTER 6330** case is a short-circuit path which does not actually invoke the 6331** underlying sqlite3_io_methods.xFileControl method. 6332** 6333** ^If the second parameter (zDbName) does not match the name of any 6334** open database file, then SQLITE_ERROR is returned. ^This error 6335** code is not remembered and will not be recalled by [sqlite3_errcode()] 6336** or [sqlite3_errmsg()]. The underlying xFileControl method might 6337** also return SQLITE_ERROR. There is no way to distinguish between 6338** an incorrect zDbName and an SQLITE_ERROR return from the underlying 6339** xFileControl method. 6340** 6341** See also: [SQLITE_FCNTL_LOCKSTATE] 6342*/ 6343int sqlite3_file_control(sqlite3*, const char *zDbName, int op, void*); 6344 6345/* 6346** CAPI3REF: Testing Interface 6347** 6348** ^The sqlite3_test_control() interface is used to read out internal 6349** state of SQLite and to inject faults into SQLite for testing 6350** purposes. ^The first parameter is an operation code that determines 6351** the number, meaning, and operation of all subsequent parameters. 6352** 6353** This interface is not for use by applications. It exists solely 6354** for verifying the correct operation of the SQLite library. Depending 6355** on how the SQLite library is compiled, this interface might not exist. 6356** 6357** The details of the operation codes, their meanings, the parameters 6358** they take, and what they do are all subject to change without notice. 6359** Unlike most of the SQLite API, this function is not guaranteed to 6360** operate consistently from one release to the next. 6361*/ 6362int sqlite3_test_control(int op, ...); 6363 6364/* 6365** CAPI3REF: Testing Interface Operation Codes 6366** 6367** These constants are the valid operation code parameters used 6368** as the first argument to [sqlite3_test_control()]. 6369** 6370** These parameters and their meanings are subject to change 6371** without notice. These values are for testing purposes only. 6372** Applications should not use any of these parameters or the 6373** [sqlite3_test_control()] interface. 6374*/ 6375#define SQLITE_TESTCTRL_FIRST 5 6376#define SQLITE_TESTCTRL_PRNG_SAVE 5 6377#define SQLITE_TESTCTRL_PRNG_RESTORE 6 6378#define SQLITE_TESTCTRL_PRNG_RESET 7 6379#define SQLITE_TESTCTRL_BITVEC_TEST 8 6380#define SQLITE_TESTCTRL_FAULT_INSTALL 9 6381#define SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS 10 6382#define SQLITE_TESTCTRL_PENDING_BYTE 11 6383#define SQLITE_TESTCTRL_ASSERT 12 6384#define SQLITE_TESTCTRL_ALWAYS 13 6385#define SQLITE_TESTCTRL_RESERVE 14 6386#define SQLITE_TESTCTRL_OPTIMIZATIONS 15 6387#define SQLITE_TESTCTRL_ISKEYWORD 16 6388#define SQLITE_TESTCTRL_SCRATCHMALLOC 17 6389#define SQLITE_TESTCTRL_LOCALTIME_FAULT 18 6390#define SQLITE_TESTCTRL_EXPLAIN_STMT 19 /* NOT USED */ 6391#define SQLITE_TESTCTRL_NEVER_CORRUPT 20 6392#define SQLITE_TESTCTRL_VDBE_COVERAGE 21 6393#define SQLITE_TESTCTRL_BYTEORDER 22 6394#define SQLITE_TESTCTRL_ISINIT 23 6395#define SQLITE_TESTCTRL_SORTER_MMAP 24 6396#define SQLITE_TESTCTRL_IMPOSTER 25 6397#define SQLITE_TESTCTRL_LAST 25 6398 6399/* 6400** CAPI3REF: SQLite Runtime Status 6401** 6402** ^These interfaces are used to retrieve runtime status information 6403** about the performance of SQLite, and optionally to reset various 6404** highwater marks. ^The first argument is an integer code for 6405** the specific parameter to measure. ^(Recognized integer codes 6406** are of the form [status parameters | SQLITE_STATUS_...].)^ 6407** ^The current value of the parameter is returned into *pCurrent. 6408** ^The highest recorded value is returned in *pHighwater. ^If the 6409** resetFlag is true, then the highest record value is reset after 6410** *pHighwater is written. ^(Some parameters do not record the highest 6411** value. For those parameters 6412** nothing is written into *pHighwater and the resetFlag is ignored.)^ 6413** ^(Other parameters record only the highwater mark and not the current 6414** value. For these latter parameters nothing is written into *pCurrent.)^ 6415** 6416** ^The sqlite3_status() and sqlite3_status64() routines return 6417** SQLITE_OK on success and a non-zero [error code] on failure. 6418** 6419** If either the current value or the highwater mark is too large to 6420** be represented by a 32-bit integer, then the values returned by 6421** sqlite3_status() are undefined. 6422** 6423** See also: [sqlite3_db_status()] 6424*/ 6425int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetFlag); 6426int sqlite3_status64( 6427 int op, 6428 sqlite3_int64 *pCurrent, 6429 sqlite3_int64 *pHighwater, 6430 int resetFlag 6431); 6432 6433 6434/* 6435** CAPI3REF: Status Parameters 6436** KEYWORDS: {status parameters} 6437** 6438** These integer constants designate various run-time status parameters 6439** that can be returned by [sqlite3_status()]. 6440** 6441** <dl> 6442** [[SQLITE_STATUS_MEMORY_USED]] ^(<dt>SQLITE_STATUS_MEMORY_USED</dt> 6443** <dd>This parameter is the current amount of memory checked out 6444** using [sqlite3_malloc()], either directly or indirectly. The 6445** figure includes calls made to [sqlite3_malloc()] by the application 6446** and internal memory usage by the SQLite library. Scratch memory 6447** controlled by [SQLITE_CONFIG_SCRATCH] and auxiliary page-cache 6448** memory controlled by [SQLITE_CONFIG_PAGECACHE] is not included in 6449** this parameter. The amount returned is the sum of the allocation 6450** sizes as reported by the xSize method in [sqlite3_mem_methods].</dd>)^ 6451** 6452** [[SQLITE_STATUS_MALLOC_SIZE]] ^(<dt>SQLITE_STATUS_MALLOC_SIZE</dt> 6453** <dd>This parameter records the largest memory allocation request 6454** handed to [sqlite3_malloc()] or [sqlite3_realloc()] (or their 6455** internal equivalents). Only the value returned in the 6456** *pHighwater parameter to [sqlite3_status()] is of interest. 6457** The value written into the *pCurrent parameter is undefined.</dd>)^ 6458** 6459** [[SQLITE_STATUS_MALLOC_COUNT]] ^(<dt>SQLITE_STATUS_MALLOC_COUNT</dt> 6460** <dd>This parameter records the number of separate memory allocations 6461** currently checked out.</dd>)^ 6462** 6463** [[SQLITE_STATUS_PAGECACHE_USED]] ^(<dt>SQLITE_STATUS_PAGECACHE_USED</dt> 6464** <dd>This parameter returns the number of pages used out of the 6465** [pagecache memory allocator] that was configured using 6466** [SQLITE_CONFIG_PAGECACHE]. The 6467** value returned is in pages, not in bytes.</dd>)^ 6468** 6469** [[SQLITE_STATUS_PAGECACHE_OVERFLOW]] 6470** ^(<dt>SQLITE_STATUS_PAGECACHE_OVERFLOW</dt> 6471** <dd>This parameter returns the number of bytes of page cache 6472** allocation which could not be satisfied by the [SQLITE_CONFIG_PAGECACHE] 6473** buffer and where forced to overflow to [sqlite3_malloc()]. The 6474** returned value includes allocations that overflowed because they 6475** where too large (they were larger than the "sz" parameter to 6476** [SQLITE_CONFIG_PAGECACHE]) and allocations that overflowed because 6477** no space was left in the page cache.</dd>)^ 6478** 6479** [[SQLITE_STATUS_PAGECACHE_SIZE]] ^(<dt>SQLITE_STATUS_PAGECACHE_SIZE</dt> 6480** <dd>This parameter records the largest memory allocation request 6481** handed to [pagecache memory allocator]. Only the value returned in the 6482** *pHighwater parameter to [sqlite3_status()] is of interest. 6483** The value written into the *pCurrent parameter is undefined.</dd>)^ 6484** 6485** [[SQLITE_STATUS_SCRATCH_USED]] ^(<dt>SQLITE_STATUS_SCRATCH_USED</dt> 6486** <dd>This parameter returns the number of allocations used out of the 6487** [scratch memory allocator] configured using 6488** [SQLITE_CONFIG_SCRATCH]. The value returned is in allocations, not 6489** in bytes. Since a single thread may only have one scratch allocation 6490** outstanding at time, this parameter also reports the number of threads 6491** using scratch memory at the same time.</dd>)^ 6492** 6493** [[SQLITE_STATUS_SCRATCH_OVERFLOW]] ^(<dt>SQLITE_STATUS_SCRATCH_OVERFLOW</dt> 6494** <dd>This parameter returns the number of bytes of scratch memory 6495** allocation which could not be satisfied by the [SQLITE_CONFIG_SCRATCH] 6496** buffer and where forced to overflow to [sqlite3_malloc()]. The values 6497** returned include overflows because the requested allocation was too 6498** larger (that is, because the requested allocation was larger than the 6499** "sz" parameter to [SQLITE_CONFIG_SCRATCH]) and because no scratch buffer 6500** slots were available. 6501** </dd>)^ 6502** 6503** [[SQLITE_STATUS_SCRATCH_SIZE]] ^(<dt>SQLITE_STATUS_SCRATCH_SIZE</dt> 6504** <dd>This parameter records the largest memory allocation request 6505** handed to [scratch memory allocator]. Only the value returned in the 6506** *pHighwater parameter to [sqlite3_status()] is of interest. 6507** The value written into the *pCurrent parameter is undefined.</dd>)^ 6508** 6509** [[SQLITE_STATUS_PARSER_STACK]] ^(<dt>SQLITE_STATUS_PARSER_STACK</dt> 6510** <dd>This parameter records the deepest parser stack. It is only 6511** meaningful if SQLite is compiled with [YYTRACKMAXSTACKDEPTH].</dd>)^ 6512** </dl> 6513** 6514** New status parameters may be added from time to time. 6515*/ 6516#define SQLITE_STATUS_MEMORY_USED 0 6517#define SQLITE_STATUS_PAGECACHE_USED 1 6518#define SQLITE_STATUS_PAGECACHE_OVERFLOW 2 6519#define SQLITE_STATUS_SCRATCH_USED 3 6520#define SQLITE_STATUS_SCRATCH_OVERFLOW 4 6521#define SQLITE_STATUS_MALLOC_SIZE 5 6522#define SQLITE_STATUS_PARSER_STACK 6 6523#define SQLITE_STATUS_PAGECACHE_SIZE 7 6524#define SQLITE_STATUS_SCRATCH_SIZE 8 6525#define SQLITE_STATUS_MALLOC_COUNT 9 6526 6527/* 6528** CAPI3REF: Database Connection Status 6529** METHOD: sqlite3 6530** 6531** ^This interface is used to retrieve runtime status information 6532** about a single [database connection]. ^The first argument is the 6533** database connection object to be interrogated. ^The second argument 6534** is an integer constant, taken from the set of 6535** [SQLITE_DBSTATUS options], that 6536** determines the parameter to interrogate. The set of 6537** [SQLITE_DBSTATUS options] is likely 6538** to grow in future releases of SQLite. 6539** 6540** ^The current value of the requested parameter is written into *pCur 6541** and the highest instantaneous value is written into *pHiwtr. ^If 6542** the resetFlg is true, then the highest instantaneous value is 6543** reset back down to the current value. 6544** 6545** ^The sqlite3_db_status() routine returns SQLITE_OK on success and a 6546** non-zero [error code] on failure. 6547** 6548** See also: [sqlite3_status()] and [sqlite3_stmt_status()]. 6549*/ 6550int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int resetFlg); 6551 6552/* 6553** CAPI3REF: Status Parameters for database connections 6554** KEYWORDS: {SQLITE_DBSTATUS options} 6555** 6556** These constants are the available integer "verbs" that can be passed as 6557** the second argument to the [sqlite3_db_status()] interface. 6558** 6559** New verbs may be added in future releases of SQLite. Existing verbs 6560** might be discontinued. Applications should check the return code from 6561** [sqlite3_db_status()] to make sure that the call worked. 6562** The [sqlite3_db_status()] interface will return a non-zero error code 6563** if a discontinued or unsupported verb is invoked. 6564** 6565** <dl> 6566** [[SQLITE_DBSTATUS_LOOKASIDE_USED]] ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_USED</dt> 6567** <dd>This parameter returns the number of lookaside memory slots currently 6568** checked out.</dd>)^ 6569** 6570** [[SQLITE_DBSTATUS_LOOKASIDE_HIT]] ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_HIT</dt> 6571** <dd>This parameter returns the number malloc attempts that were 6572** satisfied using lookaside memory. Only the high-water value is meaningful; 6573** the current value is always zero.)^ 6574** 6575** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE]] 6576** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE</dt> 6577** <dd>This parameter returns the number malloc attempts that might have 6578** been satisfied using lookaside memory but failed due to the amount of 6579** memory requested being larger than the lookaside slot size. 6580** Only the high-water value is meaningful; 6581** the current value is always zero.)^ 6582** 6583** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL]] 6584** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL</dt> 6585** <dd>This parameter returns the number malloc attempts that might have 6586** been satisfied using lookaside memory but failed due to all lookaside 6587** memory already being in use. 6588** Only the high-water value is meaningful; 6589** the current value is always zero.)^ 6590** 6591** [[SQLITE_DBSTATUS_CACHE_USED]] ^(<dt>SQLITE_DBSTATUS_CACHE_USED</dt> 6592** <dd>This parameter returns the approximate number of bytes of heap 6593** memory used by all pager caches associated with the database connection.)^ 6594** ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_USED is always 0. 6595** 6596** [[SQLITE_DBSTATUS_SCHEMA_USED]] ^(<dt>SQLITE_DBSTATUS_SCHEMA_USED</dt> 6597** <dd>This parameter returns the approximate number of bytes of heap 6598** memory used to store the schema for all databases associated 6599** with the connection - main, temp, and any [ATTACH]-ed databases.)^ 6600** ^The full amount of memory used by the schemas is reported, even if the 6601** schema memory is shared with other database connections due to 6602** [shared cache mode] being enabled. 6603** ^The highwater mark associated with SQLITE_DBSTATUS_SCHEMA_USED is always 0. 6604** 6605** [[SQLITE_DBSTATUS_STMT_USED]] ^(<dt>SQLITE_DBSTATUS_STMT_USED</dt> 6606** <dd>This parameter returns the approximate number of bytes of heap 6607** and lookaside memory used by all prepared statements associated with 6608** the database connection.)^ 6609** ^The highwater mark associated with SQLITE_DBSTATUS_STMT_USED is always 0. 6610** </dd> 6611** 6612** [[SQLITE_DBSTATUS_CACHE_HIT]] ^(<dt>SQLITE_DBSTATUS_CACHE_HIT</dt> 6613** <dd>This parameter returns the number of pager cache hits that have 6614** occurred.)^ ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_HIT 6615** is always 0. 6616** </dd> 6617** 6618** [[SQLITE_DBSTATUS_CACHE_MISS]] ^(<dt>SQLITE_DBSTATUS_CACHE_MISS</dt> 6619** <dd>This parameter returns the number of pager cache misses that have 6620** occurred.)^ ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_MISS 6621** is always 0. 6622** </dd> 6623** 6624** [[SQLITE_DBSTATUS_CACHE_WRITE]] ^(<dt>SQLITE_DBSTATUS_CACHE_WRITE</dt> 6625** <dd>This parameter returns the number of dirty cache entries that have 6626** been written to disk. Specifically, the number of pages written to the 6627** wal file in wal mode databases, or the number of pages written to the 6628** database file in rollback mode databases. Any pages written as part of 6629** transaction rollback or database recovery operations are not included. 6630** If an IO or other error occurs while writing a page to disk, the effect 6631** on subsequent SQLITE_DBSTATUS_CACHE_WRITE requests is undefined.)^ ^The 6632** highwater mark associated with SQLITE_DBSTATUS_CACHE_WRITE is always 0. 6633** </dd> 6634** 6635** [[SQLITE_DBSTATUS_DEFERRED_FKS]] ^(<dt>SQLITE_DBSTATUS_DEFERRED_FKS</dt> 6636** <dd>This parameter returns zero for the current value if and only if 6637** all foreign key constraints (deferred or immediate) have been 6638** resolved.)^ ^The highwater mark is always 0. 6639** </dd> 6640** </dl> 6641*/ 6642#define SQLITE_DBSTATUS_LOOKASIDE_USED 0 6643#define SQLITE_DBSTATUS_CACHE_USED 1 6644#define SQLITE_DBSTATUS_SCHEMA_USED 2 6645#define SQLITE_DBSTATUS_STMT_USED 3 6646#define SQLITE_DBSTATUS_LOOKASIDE_HIT 4 6647#define SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE 5 6648#define SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL 6 6649#define SQLITE_DBSTATUS_CACHE_HIT 7 6650#define SQLITE_DBSTATUS_CACHE_MISS 8 6651#define SQLITE_DBSTATUS_CACHE_WRITE 9 6652#define SQLITE_DBSTATUS_DEFERRED_FKS 10 6653#define SQLITE_DBSTATUS_MAX 10 /* Largest defined DBSTATUS */ 6654 6655 6656/* 6657** CAPI3REF: Prepared Statement Status 6658** METHOD: sqlite3_stmt 6659** 6660** ^(Each prepared statement maintains various 6661** [SQLITE_STMTSTATUS counters] that measure the number 6662** of times it has performed specific operations.)^ These counters can 6663** be used to monitor the performance characteristics of the prepared 6664** statements. For example, if the number of table steps greatly exceeds 6665** the number of table searches or result rows, that would tend to indicate 6666** that the prepared statement is using a full table scan rather than 6667** an index. 6668** 6669** ^(This interface is used to retrieve and reset counter values from 6670** a [prepared statement]. The first argument is the prepared statement 6671** object to be interrogated. The second argument 6672** is an integer code for a specific [SQLITE_STMTSTATUS counter] 6673** to be interrogated.)^ 6674** ^The current value of the requested counter is returned. 6675** ^If the resetFlg is true, then the counter is reset to zero after this 6676** interface call returns. 6677** 6678** See also: [sqlite3_status()] and [sqlite3_db_status()]. 6679*/ 6680int sqlite3_stmt_status(sqlite3_stmt*, int op,int resetFlg); 6681 6682/* 6683** CAPI3REF: Status Parameters for prepared statements 6684** KEYWORDS: {SQLITE_STMTSTATUS counter} {SQLITE_STMTSTATUS counters} 6685** 6686** These preprocessor macros define integer codes that name counter 6687** values associated with the [sqlite3_stmt_status()] interface. 6688** The meanings of the various counters are as follows: 6689** 6690** <dl> 6691** [[SQLITE_STMTSTATUS_FULLSCAN_STEP]] <dt>SQLITE_STMTSTATUS_FULLSCAN_STEP</dt> 6692** <dd>^This is the number of times that SQLite has stepped forward in 6693** a table as part of a full table scan. Large numbers for this counter 6694** may indicate opportunities for performance improvement through 6695** careful use of indices.</dd> 6696** 6697** [[SQLITE_STMTSTATUS_SORT]] <dt>SQLITE_STMTSTATUS_SORT</dt> 6698** <dd>^This is the number of sort operations that have occurred. 6699** A non-zero value in this counter may indicate an opportunity to 6700** improvement performance through careful use of indices.</dd> 6701** 6702** [[SQLITE_STMTSTATUS_AUTOINDEX]] <dt>SQLITE_STMTSTATUS_AUTOINDEX</dt> 6703** <dd>^This is the number of rows inserted into transient indices that 6704** were created automatically in order to help joins run faster. 6705** A non-zero value in this counter may indicate an opportunity to 6706** improvement performance by adding permanent indices that do not 6707** need to be reinitialized each time the statement is run.</dd> 6708** 6709** [[SQLITE_STMTSTATUS_VM_STEP]] <dt>SQLITE_STMTSTATUS_VM_STEP</dt> 6710** <dd>^This is the number of virtual machine operations executed 6711** by the prepared statement if that number is less than or equal 6712** to 2147483647. The number of virtual machine operations can be 6713** used as a proxy for the total work done by the prepared statement. 6714** If the number of virtual machine operations exceeds 2147483647 6715** then the value returned by this statement status code is undefined. 6716** </dd> 6717** </dl> 6718*/ 6719#define SQLITE_STMTSTATUS_FULLSCAN_STEP 1 6720#define SQLITE_STMTSTATUS_SORT 2 6721#define SQLITE_STMTSTATUS_AUTOINDEX 3 6722#define SQLITE_STMTSTATUS_VM_STEP 4 6723 6724/* 6725** CAPI3REF: Custom Page Cache Object 6726** 6727** The sqlite3_pcache type is opaque. It is implemented by 6728** the pluggable module. The SQLite core has no knowledge of 6729** its size or internal structure and never deals with the 6730** sqlite3_pcache object except by holding and passing pointers 6731** to the object. 6732** 6733** See [sqlite3_pcache_methods2] for additional information. 6734*/ 6735typedef struct sqlite3_pcache sqlite3_pcache; 6736 6737/* 6738** CAPI3REF: Custom Page Cache Object 6739** 6740** The sqlite3_pcache_page object represents a single page in the 6741** page cache. The page cache will allocate instances of this 6742** object. Various methods of the page cache use pointers to instances 6743** of this object as parameters or as their return value. 6744** 6745** See [sqlite3_pcache_methods2] for additional information. 6746*/ 6747typedef struct sqlite3_pcache_page sqlite3_pcache_page; 6748struct sqlite3_pcache_page { 6749 void *pBuf; /* The content of the page */ 6750 void *pExtra; /* Extra information associated with the page */ 6751}; 6752 6753/* 6754** CAPI3REF: Application Defined Page Cache. 6755** KEYWORDS: {page cache} 6756** 6757** ^(The [sqlite3_config]([SQLITE_CONFIG_PCACHE2], ...) interface can 6758** register an alternative page cache implementation by passing in an 6759** instance of the sqlite3_pcache_methods2 structure.)^ 6760** In many applications, most of the heap memory allocated by 6761** SQLite is used for the page cache. 6762** By implementing a 6763** custom page cache using this API, an application can better control 6764** the amount of memory consumed by SQLite, the way in which 6765** that memory is allocated and released, and the policies used to 6766** determine exactly which parts of a database file are cached and for 6767** how long. 6768** 6769** The alternative page cache mechanism is an 6770** extreme measure that is only needed by the most demanding applications. 6771** The built-in page cache is recommended for most uses. 6772** 6773** ^(The contents of the sqlite3_pcache_methods2 structure are copied to an 6774** internal buffer by SQLite within the call to [sqlite3_config]. Hence 6775** the application may discard the parameter after the call to 6776** [sqlite3_config()] returns.)^ 6777** 6778** [[the xInit() page cache method]] 6779** ^(The xInit() method is called once for each effective 6780** call to [sqlite3_initialize()])^ 6781** (usually only once during the lifetime of the process). ^(The xInit() 6782** method is passed a copy of the sqlite3_pcache_methods2.pArg value.)^ 6783** The intent of the xInit() method is to set up global data structures 6784** required by the custom page cache implementation. 6785** ^(If the xInit() method is NULL, then the 6786** built-in default page cache is used instead of the application defined 6787** page cache.)^ 6788** 6789** [[the xShutdown() page cache method]] 6790** ^The xShutdown() method is called by [sqlite3_shutdown()]. 6791** It can be used to clean up 6792** any outstanding resources before process shutdown, if required. 6793** ^The xShutdown() method may be NULL. 6794** 6795** ^SQLite automatically serializes calls to the xInit method, 6796** so the xInit method need not be threadsafe. ^The 6797** xShutdown method is only called from [sqlite3_shutdown()] so it does 6798** not need to be threadsafe either. All other methods must be threadsafe 6799** in multithreaded applications. 6800** 6801** ^SQLite will never invoke xInit() more than once without an intervening 6802** call to xShutdown(). 6803** 6804** [[the xCreate() page cache methods]] 6805** ^SQLite invokes the xCreate() method to construct a new cache instance. 6806** SQLite will typically create one cache instance for each open database file, 6807** though this is not guaranteed. ^The 6808** first parameter, szPage, is the size in bytes of the pages that must 6809** be allocated by the cache. ^szPage will always a power of two. ^The 6810** second parameter szExtra is a number of bytes of extra storage 6811** associated with each page cache entry. ^The szExtra parameter will 6812** a number less than 250. SQLite will use the 6813** extra szExtra bytes on each page to store metadata about the underlying 6814** database page on disk. The value passed into szExtra depends 6815** on the SQLite version, the target platform, and how SQLite was compiled. 6816** ^The third argument to xCreate(), bPurgeable, is true if the cache being 6817** created will be used to cache database pages of a file stored on disk, or 6818** false if it is used for an in-memory database. The cache implementation 6819** does not have to do anything special based with the value of bPurgeable; 6820** it is purely advisory. ^On a cache where bPurgeable is false, SQLite will 6821** never invoke xUnpin() except to deliberately delete a page. 6822** ^In other words, calls to xUnpin() on a cache with bPurgeable set to 6823** false will always have the "discard" flag set to true. 6824** ^Hence, a cache created with bPurgeable false will 6825** never contain any unpinned pages. 6826** 6827** [[the xCachesize() page cache method]] 6828** ^(The xCachesize() method may be called at any time by SQLite to set the 6829** suggested maximum cache-size (number of pages stored by) the cache 6830** instance passed as the first argument. This is the value configured using 6831** the SQLite "[PRAGMA cache_size]" command.)^ As with the bPurgeable 6832** parameter, the implementation is not required to do anything with this 6833** value; it is advisory only. 6834** 6835** [[the xPagecount() page cache methods]] 6836** The xPagecount() method must return the number of pages currently 6837** stored in the cache, both pinned and unpinned. 6838** 6839** [[the xFetch() page cache methods]] 6840** The xFetch() method locates a page in the cache and returns a pointer to 6841** an sqlite3_pcache_page object associated with that page, or a NULL pointer. 6842** The pBuf element of the returned sqlite3_pcache_page object will be a 6843** pointer to a buffer of szPage bytes used to store the content of a 6844** single database page. The pExtra element of sqlite3_pcache_page will be 6845** a pointer to the szExtra bytes of extra storage that SQLite has requested 6846** for each entry in the page cache. 6847** 6848** The page to be fetched is determined by the key. ^The minimum key value 6849** is 1. After it has been retrieved using xFetch, the page is considered 6850** to be "pinned". 6851** 6852** If the requested page is already in the page cache, then the page cache 6853** implementation must return a pointer to the page buffer with its content 6854** intact. If the requested page is not already in the cache, then the 6855** cache implementation should use the value of the createFlag 6856** parameter to help it determined what action to take: 6857** 6858** <table border=1 width=85% align=center> 6859** <tr><th> createFlag <th> Behavior when page is not already in cache 6860** <tr><td> 0 <td> Do not allocate a new page. Return NULL. 6861** <tr><td> 1 <td> Allocate a new page if it easy and convenient to do so. 6862** Otherwise return NULL. 6863** <tr><td> 2 <td> Make every effort to allocate a new page. Only return 6864** NULL if allocating a new page is effectively impossible. 6865** </table> 6866** 6867** ^(SQLite will normally invoke xFetch() with a createFlag of 0 or 1. SQLite 6868** will only use a createFlag of 2 after a prior call with a createFlag of 1 6869** failed.)^ In between the to xFetch() calls, SQLite may 6870** attempt to unpin one or more cache pages by spilling the content of 6871** pinned pages to disk and synching the operating system disk cache. 6872** 6873** [[the xUnpin() page cache method]] 6874** ^xUnpin() is called by SQLite with a pointer to a currently pinned page 6875** as its second argument. If the third parameter, discard, is non-zero, 6876** then the page must be evicted from the cache. 6877** ^If the discard parameter is 6878** zero, then the page may be discarded or retained at the discretion of 6879** page cache implementation. ^The page cache implementation 6880** may choose to evict unpinned pages at any time. 6881** 6882** The cache must not perform any reference counting. A single 6883** call to xUnpin() unpins the page regardless of the number of prior calls 6884** to xFetch(). 6885** 6886** [[the xRekey() page cache methods]] 6887** The xRekey() method is used to change the key value associated with the 6888** page passed as the second argument. If the cache 6889** previously contains an entry associated with newKey, it must be 6890** discarded. ^Any prior cache entry associated with newKey is guaranteed not 6891** to be pinned. 6892** 6893** When SQLite calls the xTruncate() method, the cache must discard all 6894** existing cache entries with page numbers (keys) greater than or equal 6895** to the value of the iLimit parameter passed to xTruncate(). If any 6896** of these pages are pinned, they are implicitly unpinned, meaning that 6897** they can be safely discarded. 6898** 6899** [[the xDestroy() page cache method]] 6900** ^The xDestroy() method is used to delete a cache allocated by xCreate(). 6901** All resources associated with the specified cache should be freed. ^After 6902** calling the xDestroy() method, SQLite considers the [sqlite3_pcache*] 6903** handle invalid, and will not use it with any other sqlite3_pcache_methods2 6904** functions. 6905** 6906** [[the xShrink() page cache method]] 6907** ^SQLite invokes the xShrink() method when it wants the page cache to 6908** free up as much of heap memory as possible. The page cache implementation 6909** is not obligated to free any memory, but well-behaved implementations should 6910** do their best. 6911*/ 6912typedef struct sqlite3_pcache_methods2 sqlite3_pcache_methods2; 6913struct sqlite3_pcache_methods2 { 6914 int iVersion; 6915 void *pArg; 6916 int (*xInit)(void*); 6917 void (*xShutdown)(void*); 6918 sqlite3_pcache *(*xCreate)(int szPage, int szExtra, int bPurgeable); 6919 void (*xCachesize)(sqlite3_pcache*, int nCachesize); 6920 int (*xPagecount)(sqlite3_pcache*); 6921 sqlite3_pcache_page *(*xFetch)(sqlite3_pcache*, unsigned key, int createFlag); 6922 void (*xUnpin)(sqlite3_pcache*, sqlite3_pcache_page*, int discard); 6923 void (*xRekey)(sqlite3_pcache*, sqlite3_pcache_page*, 6924 unsigned oldKey, unsigned newKey); 6925 void (*xTruncate)(sqlite3_pcache*, unsigned iLimit); 6926 void (*xDestroy)(sqlite3_pcache*); 6927 void (*xShrink)(sqlite3_pcache*); 6928}; 6929 6930/* 6931** This is the obsolete pcache_methods object that has now been replaced 6932** by sqlite3_pcache_methods2. This object is not used by SQLite. It is 6933** retained in the header file for backwards compatibility only. 6934*/ 6935typedef struct sqlite3_pcache_methods sqlite3_pcache_methods; 6936struct sqlite3_pcache_methods { 6937 void *pArg; 6938 int (*xInit)(void*); 6939 void (*xShutdown)(void*); 6940 sqlite3_pcache *(*xCreate)(int szPage, int bPurgeable); 6941 void (*xCachesize)(sqlite3_pcache*, int nCachesize); 6942 int (*xPagecount)(sqlite3_pcache*); 6943 void *(*xFetch)(sqlite3_pcache*, unsigned key, int createFlag); 6944 void (*xUnpin)(sqlite3_pcache*, void*, int discard); 6945 void (*xRekey)(sqlite3_pcache*, void*, unsigned oldKey, unsigned newKey); 6946 void (*xTruncate)(sqlite3_pcache*, unsigned iLimit); 6947 void (*xDestroy)(sqlite3_pcache*); 6948}; 6949 6950 6951/* 6952** CAPI3REF: Online Backup Object 6953** 6954** The sqlite3_backup object records state information about an ongoing 6955** online backup operation. ^The sqlite3_backup object is created by 6956** a call to [sqlite3_backup_init()] and is destroyed by a call to 6957** [sqlite3_backup_finish()]. 6958** 6959** See Also: [Using the SQLite Online Backup API] 6960*/ 6961typedef struct sqlite3_backup sqlite3_backup; 6962 6963/* 6964** CAPI3REF: Online Backup API. 6965** 6966** The backup API copies the content of one database into another. 6967** It is useful either for creating backups of databases or 6968** for copying in-memory databases to or from persistent files. 6969** 6970** See Also: [Using the SQLite Online Backup API] 6971** 6972** ^SQLite holds a write transaction open on the destination database file 6973** for the duration of the backup operation. 6974** ^The source database is read-locked only while it is being read; 6975** it is not locked continuously for the entire backup operation. 6976** ^Thus, the backup may be performed on a live source database without 6977** preventing other database connections from 6978** reading or writing to the source database while the backup is underway. 6979** 6980** ^(To perform a backup operation: 6981** <ol> 6982** <li><b>sqlite3_backup_init()</b> is called once to initialize the 6983** backup, 6984** <li><b>sqlite3_backup_step()</b> is called one or more times to transfer 6985** the data between the two databases, and finally 6986** <li><b>sqlite3_backup_finish()</b> is called to release all resources 6987** associated with the backup operation. 6988** </ol>)^ 6989** There should be exactly one call to sqlite3_backup_finish() for each 6990** successful call to sqlite3_backup_init(). 6991** 6992** [[sqlite3_backup_init()]] <b>sqlite3_backup_init()</b> 6993** 6994** ^The D and N arguments to sqlite3_backup_init(D,N,S,M) are the 6995** [database connection] associated with the destination database 6996** and the database name, respectively. 6997** ^The database name is "main" for the main database, "temp" for the 6998** temporary database, or the name specified after the AS keyword in 6999** an [ATTACH] statement for an attached database. 7000** ^The S and M arguments passed to 7001** sqlite3_backup_init(D,N,S,M) identify the [database connection] 7002** and database name of the source database, respectively. 7003** ^The source and destination [database connections] (parameters S and D) 7004** must be different or else sqlite3_backup_init(D,N,S,M) will fail with 7005** an error. 7006** 7007** ^A call to sqlite3_backup_init() will fail, returning SQLITE_ERROR, if 7008** there is already a read or read-write transaction open on the 7009** destination database. 7010** 7011** ^If an error occurs within sqlite3_backup_init(D,N,S,M), then NULL is 7012** returned and an error code and error message are stored in the 7013** destination [database connection] D. 7014** ^The error code and message for the failed call to sqlite3_backup_init() 7015** can be retrieved using the [sqlite3_errcode()], [sqlite3_errmsg()], and/or 7016** [sqlite3_errmsg16()] functions. 7017** ^A successful call to sqlite3_backup_init() returns a pointer to an 7018** [sqlite3_backup] object. 7019** ^The [sqlite3_backup] object may be used with the sqlite3_backup_step() and 7020** sqlite3_backup_finish() functions to perform the specified backup 7021** operation. 7022** 7023** [[sqlite3_backup_step()]] <b>sqlite3_backup_step()</b> 7024** 7025** ^Function sqlite3_backup_step(B,N) will copy up to N pages between 7026** the source and destination databases specified by [sqlite3_backup] object B. 7027** ^If N is negative, all remaining source pages are copied. 7028** ^If sqlite3_backup_step(B,N) successfully copies N pages and there 7029** are still more pages to be copied, then the function returns [SQLITE_OK]. 7030** ^If sqlite3_backup_step(B,N) successfully finishes copying all pages 7031** from source to destination, then it returns [SQLITE_DONE]. 7032** ^If an error occurs while running sqlite3_backup_step(B,N), 7033** then an [error code] is returned. ^As well as [SQLITE_OK] and 7034** [SQLITE_DONE], a call to sqlite3_backup_step() may return [SQLITE_READONLY], 7035** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an 7036** [SQLITE_IOERR_ACCESS | SQLITE_IOERR_XXX] extended error code. 7037** 7038** ^(The sqlite3_backup_step() might return [SQLITE_READONLY] if 7039** <ol> 7040** <li> the destination database was opened read-only, or 7041** <li> the destination database is using write-ahead-log journaling 7042** and the destination and source page sizes differ, or 7043** <li> the destination database is an in-memory database and the 7044** destination and source page sizes differ. 7045** </ol>)^ 7046** 7047** ^If sqlite3_backup_step() cannot obtain a required file-system lock, then 7048** the [sqlite3_busy_handler | busy-handler function] 7049** is invoked (if one is specified). ^If the 7050** busy-handler returns non-zero before the lock is available, then 7051** [SQLITE_BUSY] is returned to the caller. ^In this case the call to 7052** sqlite3_backup_step() can be retried later. ^If the source 7053** [database connection] 7054** is being used to write to the source database when sqlite3_backup_step() 7055** is called, then [SQLITE_LOCKED] is returned immediately. ^Again, in this 7056** case the call to sqlite3_backup_step() can be retried later on. ^(If 7057** [SQLITE_IOERR_ACCESS | SQLITE_IOERR_XXX], [SQLITE_NOMEM], or 7058** [SQLITE_READONLY] is returned, then 7059** there is no point in retrying the call to sqlite3_backup_step(). These 7060** errors are considered fatal.)^ The application must accept 7061** that the backup operation has failed and pass the backup operation handle 7062** to the sqlite3_backup_finish() to release associated resources. 7063** 7064** ^The first call to sqlite3_backup_step() obtains an exclusive lock 7065** on the destination file. ^The exclusive lock is not released until either 7066** sqlite3_backup_finish() is called or the backup operation is complete 7067** and sqlite3_backup_step() returns [SQLITE_DONE]. ^Every call to 7068** sqlite3_backup_step() obtains a [shared lock] on the source database that 7069** lasts for the duration of the sqlite3_backup_step() call. 7070** ^Because the source database is not locked between calls to 7071** sqlite3_backup_step(), the source database may be modified mid-way 7072** through the backup process. ^If the source database is modified by an 7073** external process or via a database connection other than the one being 7074** used by the backup operation, then the backup will be automatically 7075** restarted by the next call to sqlite3_backup_step(). ^If the source 7076** database is modified by the using the same database connection as is used 7077** by the backup operation, then the backup database is automatically 7078** updated at the same time. 7079** 7080** [[sqlite3_backup_finish()]] <b>sqlite3_backup_finish()</b> 7081** 7082** When sqlite3_backup_step() has returned [SQLITE_DONE], or when the 7083** application wishes to abandon the backup operation, the application 7084** should destroy the [sqlite3_backup] by passing it to sqlite3_backup_finish(). 7085** ^The sqlite3_backup_finish() interfaces releases all 7086** resources associated with the [sqlite3_backup] object. 7087** ^If sqlite3_backup_step() has not yet returned [SQLITE_DONE], then any 7088** active write-transaction on the destination database is rolled back. 7089** The [sqlite3_backup] object is invalid 7090** and may not be used following a call to sqlite3_backup_finish(). 7091** 7092** ^The value returned by sqlite3_backup_finish is [SQLITE_OK] if no 7093** sqlite3_backup_step() errors occurred, regardless or whether or not 7094** sqlite3_backup_step() completed. 7095** ^If an out-of-memory condition or IO error occurred during any prior 7096** sqlite3_backup_step() call on the same [sqlite3_backup] object, then 7097** sqlite3_backup_finish() returns the corresponding [error code]. 7098** 7099** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step() 7100** is not a permanent error and does not affect the return value of 7101** sqlite3_backup_finish(). 7102** 7103** [[sqlite3_backup_remaining()]] [[sqlite3_backup_pagecount()]] 7104** <b>sqlite3_backup_remaining() and sqlite3_backup_pagecount()</b> 7105** 7106** ^The sqlite3_backup_remaining() routine returns the number of pages still 7107** to be backed up at the conclusion of the most recent sqlite3_backup_step(). 7108** ^The sqlite3_backup_pagecount() routine returns the total number of pages 7109** in the source database at the conclusion of the most recent 7110** sqlite3_backup_step(). 7111** ^(The values returned by these functions are only updated by 7112** sqlite3_backup_step(). If the source database is modified in a way that 7113** changes the size of the source database or the number of pages remaining, 7114** those changes are not reflected in the output of sqlite3_backup_pagecount() 7115** and sqlite3_backup_remaining() until after the next 7116** sqlite3_backup_step().)^ 7117** 7118** <b>Concurrent Usage of Database Handles</b> 7119** 7120** ^The source [database connection] may be used by the application for other 7121** purposes while a backup operation is underway or being initialized. 7122** ^If SQLite is compiled and configured to support threadsafe database 7123** connections, then the source database connection may be used concurrently 7124** from within other threads. 7125** 7126** However, the application must guarantee that the destination 7127** [database connection] is not passed to any other API (by any thread) after 7128** sqlite3_backup_init() is called and before the corresponding call to 7129** sqlite3_backup_finish(). SQLite does not currently check to see 7130** if the application incorrectly accesses the destination [database connection] 7131** and so no error code is reported, but the operations may malfunction 7132** nevertheless. Use of the destination database connection while a 7133** backup is in progress might also also cause a mutex deadlock. 7134** 7135** If running in [shared cache mode], the application must 7136** guarantee that the shared cache used by the destination database 7137** is not accessed while the backup is running. In practice this means 7138** that the application must guarantee that the disk file being 7139** backed up to is not accessed by any connection within the process, 7140** not just the specific connection that was passed to sqlite3_backup_init(). 7141** 7142** The [sqlite3_backup] object itself is partially threadsafe. Multiple 7143** threads may safely make multiple concurrent calls to sqlite3_backup_step(). 7144** However, the sqlite3_backup_remaining() and sqlite3_backup_pagecount() 7145** APIs are not strictly speaking threadsafe. If they are invoked at the 7146** same time as another thread is invoking sqlite3_backup_step() it is 7147** possible that they return invalid values. 7148*/ 7149sqlite3_backup *sqlite3_backup_init( 7150 sqlite3 *pDest, /* Destination database handle */ 7151 const char *zDestName, /* Destination database name */ 7152 sqlite3 *pSource, /* Source database handle */ 7153 const char *zSourceName /* Source database name */ 7154); 7155int sqlite3_backup_step(sqlite3_backup *p, int nPage); 7156int sqlite3_backup_finish(sqlite3_backup *p); 7157int sqlite3_backup_remaining(sqlite3_backup *p); 7158int sqlite3_backup_pagecount(sqlite3_backup *p); 7159 7160/* 7161** CAPI3REF: Unlock Notification 7162** METHOD: sqlite3 7163** 7164** ^When running in shared-cache mode, a database operation may fail with 7165** an [SQLITE_LOCKED] error if the required locks on the shared-cache or 7166** individual tables within the shared-cache cannot be obtained. See 7167** [SQLite Shared-Cache Mode] for a description of shared-cache locking. 7168** ^This API may be used to register a callback that SQLite will invoke 7169** when the connection currently holding the required lock relinquishes it. 7170** ^This API is only available if the library was compiled with the 7171** [SQLITE_ENABLE_UNLOCK_NOTIFY] C-preprocessor symbol defined. 7172** 7173** See Also: [Using the SQLite Unlock Notification Feature]. 7174** 7175** ^Shared-cache locks are released when a database connection concludes 7176** its current transaction, either by committing it or rolling it back. 7177** 7178** ^When a connection (known as the blocked connection) fails to obtain a 7179** shared-cache lock and SQLITE_LOCKED is returned to the caller, the 7180** identity of the database connection (the blocking connection) that 7181** has locked the required resource is stored internally. ^After an 7182** application receives an SQLITE_LOCKED error, it may call the 7183** sqlite3_unlock_notify() method with the blocked connection handle as 7184** the first argument to register for a callback that will be invoked 7185** when the blocking connections current transaction is concluded. ^The 7186** callback is invoked from within the [sqlite3_step] or [sqlite3_close] 7187** call that concludes the blocking connections transaction. 7188** 7189** ^(If sqlite3_unlock_notify() is called in a multi-threaded application, 7190** there is a chance that the blocking connection will have already 7191** concluded its transaction by the time sqlite3_unlock_notify() is invoked. 7192** If this happens, then the specified callback is invoked immediately, 7193** from within the call to sqlite3_unlock_notify().)^ 7194** 7195** ^If the blocked connection is attempting to obtain a write-lock on a 7196** shared-cache table, and more than one other connection currently holds 7197** a read-lock on the same table, then SQLite arbitrarily selects one of 7198** the other connections to use as the blocking connection. 7199** 7200** ^(There may be at most one unlock-notify callback registered by a 7201** blocked connection. If sqlite3_unlock_notify() is called when the 7202** blocked connection already has a registered unlock-notify callback, 7203** then the new callback replaces the old.)^ ^If sqlite3_unlock_notify() is 7204** called with a NULL pointer as its second argument, then any existing 7205** unlock-notify callback is canceled. ^The blocked connections 7206** unlock-notify callback may also be canceled by closing the blocked 7207** connection using [sqlite3_close()]. 7208** 7209** The unlock-notify callback is not reentrant. If an application invokes 7210** any sqlite3_xxx API functions from within an unlock-notify callback, a 7211** crash or deadlock may be the result. 7212** 7213** ^Unless deadlock is detected (see below), sqlite3_unlock_notify() always 7214** returns SQLITE_OK. 7215** 7216** <b>Callback Invocation Details</b> 7217** 7218** When an unlock-notify callback is registered, the application provides a 7219** single void* pointer that is passed to the callback when it is invoked. 7220** However, the signature of the callback function allows SQLite to pass 7221** it an array of void* context pointers. The first argument passed to 7222** an unlock-notify callback is a pointer to an array of void* pointers, 7223** and the second is the number of entries in the array. 7224** 7225** When a blocking connections transaction is concluded, there may be 7226** more than one blocked connection that has registered for an unlock-notify 7227** callback. ^If two or more such blocked connections have specified the 7228** same callback function, then instead of invoking the callback function 7229** multiple times, it is invoked once with the set of void* context pointers 7230** specified by the blocked connections bundled together into an array. 7231** This gives the application an opportunity to prioritize any actions 7232** related to the set of unblocked database connections. 7233** 7234** <b>Deadlock Detection</b> 7235** 7236** Assuming that after registering for an unlock-notify callback a 7237** database waits for the callback to be issued before taking any further 7238** action (a reasonable assumption), then using this API may cause the 7239** application to deadlock. For example, if connection X is waiting for 7240** connection Y's transaction to be concluded, and similarly connection 7241** Y is waiting on connection X's transaction, then neither connection 7242** will proceed and the system may remain deadlocked indefinitely. 7243** 7244** To avoid this scenario, the sqlite3_unlock_notify() performs deadlock 7245** detection. ^If a given call to sqlite3_unlock_notify() would put the 7246** system in a deadlocked state, then SQLITE_LOCKED is returned and no 7247** unlock-notify callback is registered. The system is said to be in 7248** a deadlocked state if connection A has registered for an unlock-notify 7249** callback on the conclusion of connection B's transaction, and connection 7250** B has itself registered for an unlock-notify callback when connection 7251** A's transaction is concluded. ^Indirect deadlock is also detected, so 7252** the system is also considered to be deadlocked if connection B has 7253** registered for an unlock-notify callback on the conclusion of connection 7254** C's transaction, where connection C is waiting on connection A. ^Any 7255** number of levels of indirection are allowed. 7256** 7257** <b>The "DROP TABLE" Exception</b> 7258** 7259** When a call to [sqlite3_step()] returns SQLITE_LOCKED, it is almost 7260** always appropriate to call sqlite3_unlock_notify(). There is however, 7261** one exception. When executing a "DROP TABLE" or "DROP INDEX" statement, 7262** SQLite checks if there are any currently executing SELECT statements 7263** that belong to the same connection. If there are, SQLITE_LOCKED is 7264** returned. In this case there is no "blocking connection", so invoking 7265** sqlite3_unlock_notify() results in the unlock-notify callback being 7266** invoked immediately. If the application then re-attempts the "DROP TABLE" 7267** or "DROP INDEX" query, an infinite loop might be the result. 7268** 7269** One way around this problem is to check the extended error code returned 7270** by an sqlite3_step() call. ^(If there is a blocking connection, then the 7271** extended error code is set to SQLITE_LOCKED_SHAREDCACHE. Otherwise, in 7272** the special "DROP TABLE/INDEX" case, the extended error code is just 7273** SQLITE_LOCKED.)^ 7274*/ 7275int sqlite3_unlock_notify( 7276 sqlite3 *pBlocked, /* Waiting connection */ 7277 void (*xNotify)(void **apArg, int nArg), /* Callback function to invoke */ 7278 void *pNotifyArg /* Argument to pass to xNotify */ 7279); 7280 7281 7282/* 7283** CAPI3REF: String Comparison 7284** 7285** ^The [sqlite3_stricmp()] and [sqlite3_strnicmp()] APIs allow applications 7286** and extensions to compare the contents of two buffers containing UTF-8 7287** strings in a case-independent fashion, using the same definition of "case 7288** independence" that SQLite uses internally when comparing identifiers. 7289*/ 7290int sqlite3_stricmp(const char *, const char *); 7291int sqlite3_strnicmp(const char *, const char *, int); 7292 7293/* 7294** CAPI3REF: String Globbing 7295* 7296** ^The [sqlite3_strglob(P,X)] interface returns zero if string X matches 7297** the glob pattern P, and it returns non-zero if string X does not match 7298** the glob pattern P. ^The definition of glob pattern matching used in 7299** [sqlite3_strglob(P,X)] is the same as for the "X GLOB P" operator in the 7300** SQL dialect used by SQLite. ^The sqlite3_strglob(P,X) function is case 7301** sensitive. 7302** 7303** Note that this routine returns zero on a match and non-zero if the strings 7304** do not match, the same as [sqlite3_stricmp()] and [sqlite3_strnicmp()]. 7305*/ 7306int sqlite3_strglob(const char *zGlob, const char *zStr); 7307 7308/* 7309** CAPI3REF: Error Logging Interface 7310** 7311** ^The [sqlite3_log()] interface writes a message into the [error log] 7312** established by the [SQLITE_CONFIG_LOG] option to [sqlite3_config()]. 7313** ^If logging is enabled, the zFormat string and subsequent arguments are 7314** used with [sqlite3_snprintf()] to generate the final output string. 7315** 7316** The sqlite3_log() interface is intended for use by extensions such as 7317** virtual tables, collating functions, and SQL functions. While there is 7318** nothing to prevent an application from calling sqlite3_log(), doing so 7319** is considered bad form. 7320** 7321** The zFormat string must not be NULL. 7322** 7323** To avoid deadlocks and other threading problems, the sqlite3_log() routine 7324** will not use dynamically allocated memory. The log message is stored in 7325** a fixed-length buffer on the stack. If the log message is longer than 7326** a few hundred characters, it will be truncated to the length of the 7327** buffer. 7328*/ 7329void sqlite3_log(int iErrCode, const char *zFormat, ...); 7330 7331/* 7332** CAPI3REF: Write-Ahead Log Commit Hook 7333** METHOD: sqlite3 7334** 7335** ^The [sqlite3_wal_hook()] function is used to register a callback that 7336** is invoked each time data is committed to a database in wal mode. 7337** 7338** ^(The callback is invoked by SQLite after the commit has taken place and 7339** the associated write-lock on the database released)^, so the implementation 7340** may read, write or [checkpoint] the database as required. 7341** 7342** ^The first parameter passed to the callback function when it is invoked 7343** is a copy of the third parameter passed to sqlite3_wal_hook() when 7344** registering the callback. ^The second is a copy of the database handle. 7345** ^The third parameter is the name of the database that was written to - 7346** either "main" or the name of an [ATTACH]-ed database. ^The fourth parameter 7347** is the number of pages currently in the write-ahead log file, 7348** including those that were just committed. 7349** 7350** The callback function should normally return [SQLITE_OK]. ^If an error 7351** code is returned, that error will propagate back up through the 7352** SQLite code base to cause the statement that provoked the callback 7353** to report an error, though the commit will have still occurred. If the 7354** callback returns [SQLITE_ROW] or [SQLITE_DONE], or if it returns a value 7355** that does not correspond to any valid SQLite error code, the results 7356** are undefined. 7357** 7358** A single database handle may have at most a single write-ahead log callback 7359** registered at one time. ^Calling [sqlite3_wal_hook()] replaces any 7360** previously registered write-ahead log callback. ^Note that the 7361** [sqlite3_wal_autocheckpoint()] interface and the 7362** [wal_autocheckpoint pragma] both invoke [sqlite3_wal_hook()] and will 7363** those overwrite any prior [sqlite3_wal_hook()] settings. 7364*/ 7365void *sqlite3_wal_hook( 7366 sqlite3*, 7367 int(*)(void *,sqlite3*,const char*,int), 7368 void* 7369); 7370 7371/* 7372** CAPI3REF: Configure an auto-checkpoint 7373** METHOD: sqlite3 7374** 7375** ^The [sqlite3_wal_autocheckpoint(D,N)] is a wrapper around 7376** [sqlite3_wal_hook()] that causes any database on [database connection] D 7377** to automatically [checkpoint] 7378** after committing a transaction if there are N or 7379** more frames in the [write-ahead log] file. ^Passing zero or 7380** a negative value as the nFrame parameter disables automatic 7381** checkpoints entirely. 7382** 7383** ^The callback registered by this function replaces any existing callback 7384** registered using [sqlite3_wal_hook()]. ^Likewise, registering a callback 7385** using [sqlite3_wal_hook()] disables the automatic checkpoint mechanism 7386** configured by this function. 7387** 7388** ^The [wal_autocheckpoint pragma] can be used to invoke this interface 7389** from SQL. 7390** 7391** ^Checkpoints initiated by this mechanism are 7392** [sqlite3_wal_checkpoint_v2|PASSIVE]. 7393** 7394** ^Every new [database connection] defaults to having the auto-checkpoint 7395** enabled with a threshold of 1000 or [SQLITE_DEFAULT_WAL_AUTOCHECKPOINT] 7396** pages. The use of this interface 7397** is only necessary if the default setting is found to be suboptimal 7398** for a particular application. 7399*/ 7400int sqlite3_wal_autocheckpoint(sqlite3 *db, int N); 7401 7402/* 7403** CAPI3REF: Checkpoint a database 7404** METHOD: sqlite3 7405** 7406** ^(The sqlite3_wal_checkpoint(D,X) is equivalent to 7407** [sqlite3_wal_checkpoint_v2](D,X,[SQLITE_CHECKPOINT_PASSIVE],0,0).)^ 7408** 7409** In brief, sqlite3_wal_checkpoint(D,X) causes the content in the 7410** [write-ahead log] for database X on [database connection] D to be 7411** transferred into the database file and for the write-ahead log to 7412** be reset. See the [checkpointing] documentation for addition 7413** information. 7414** 7415** This interface used to be the only way to cause a checkpoint to 7416** occur. But then the newer and more powerful [sqlite3_wal_checkpoint_v2()] 7417** interface was added. This interface is retained for backwards 7418** compatibility and as a convenience for applications that need to manually 7419** start a callback but which do not need the full power (and corresponding 7420** complication) of [sqlite3_wal_checkpoint_v2()]. 7421*/ 7422int sqlite3_wal_checkpoint(sqlite3 *db, const char *zDb); 7423 7424/* 7425** CAPI3REF: Checkpoint a database 7426** METHOD: sqlite3 7427** 7428** ^(The sqlite3_wal_checkpoint_v2(D,X,M,L,C) interface runs a checkpoint 7429** operation on database X of [database connection] D in mode M. Status 7430** information is written back into integers pointed to by L and C.)^ 7431** ^(The M parameter must be a valid [checkpoint mode]:)^ 7432** 7433** <dl> 7434** <dt>SQLITE_CHECKPOINT_PASSIVE<dd> 7435** ^Checkpoint as many frames as possible without waiting for any database 7436** readers or writers to finish, then sync the database file if all frames 7437** in the log were checkpointed. ^The [busy-handler callback] 7438** is never invoked in the SQLITE_CHECKPOINT_PASSIVE mode. 7439** ^On the other hand, passive mode might leave the checkpoint unfinished 7440** if there are concurrent readers or writers. 7441** 7442** <dt>SQLITE_CHECKPOINT_FULL<dd> 7443** ^This mode blocks (it invokes the 7444** [sqlite3_busy_handler|busy-handler callback]) until there is no 7445** database writer and all readers are reading from the most recent database 7446** snapshot. ^It then checkpoints all frames in the log file and syncs the 7447** database file. ^This mode blocks new database writers while it is pending, 7448** but new database readers are allowed to continue unimpeded. 7449** 7450** <dt>SQLITE_CHECKPOINT_RESTART<dd> 7451** ^This mode works the same way as SQLITE_CHECKPOINT_FULL with the addition 7452** that after checkpointing the log file it blocks (calls the 7453** [busy-handler callback]) 7454** until all readers are reading from the database file only. ^This ensures 7455** that the next writer will restart the log file from the beginning. 7456** ^Like SQLITE_CHECKPOINT_FULL, this mode blocks new 7457** database writer attempts while it is pending, but does not impede readers. 7458** 7459** <dt>SQLITE_CHECKPOINT_TRUNCATE<dd> 7460** ^This mode works the same way as SQLITE_CHECKPOINT_RESTART with the 7461** addition that it also truncates the log file to zero bytes just prior 7462** to a successful return. 7463** </dl> 7464** 7465** ^If pnLog is not NULL, then *pnLog is set to the total number of frames in 7466** the log file or to -1 if the checkpoint could not run because 7467** of an error or because the database is not in [WAL mode]. ^If pnCkpt is not 7468** NULL,then *pnCkpt is set to the total number of checkpointed frames in the 7469** log file (including any that were already checkpointed before the function 7470** was called) or to -1 if the checkpoint could not run due to an error or 7471** because the database is not in WAL mode. ^Note that upon successful 7472** completion of an SQLITE_CHECKPOINT_TRUNCATE, the log file will have been 7473** truncated to zero bytes and so both *pnLog and *pnCkpt will be set to zero. 7474** 7475** ^All calls obtain an exclusive "checkpoint" lock on the database file. ^If 7476** any other process is running a checkpoint operation at the same time, the 7477** lock cannot be obtained and SQLITE_BUSY is returned. ^Even if there is a 7478** busy-handler configured, it will not be invoked in this case. 7479** 7480** ^The SQLITE_CHECKPOINT_FULL, RESTART and TRUNCATE modes also obtain the 7481** exclusive "writer" lock on the database file. ^If the writer lock cannot be 7482** obtained immediately, and a busy-handler is configured, it is invoked and 7483** the writer lock retried until either the busy-handler returns 0 or the lock 7484** is successfully obtained. ^The busy-handler is also invoked while waiting for 7485** database readers as described above. ^If the busy-handler returns 0 before 7486** the writer lock is obtained or while waiting for database readers, the 7487** checkpoint operation proceeds from that point in the same way as 7488** SQLITE_CHECKPOINT_PASSIVE - checkpointing as many frames as possible 7489** without blocking any further. ^SQLITE_BUSY is returned in this case. 7490** 7491** ^If parameter zDb is NULL or points to a zero length string, then the 7492** specified operation is attempted on all WAL databases [attached] to 7493** [database connection] db. In this case the 7494** values written to output parameters *pnLog and *pnCkpt are undefined. ^If 7495** an SQLITE_BUSY error is encountered when processing one or more of the 7496** attached WAL databases, the operation is still attempted on any remaining 7497** attached databases and SQLITE_BUSY is returned at the end. ^If any other 7498** error occurs while processing an attached database, processing is abandoned 7499** and the error code is returned to the caller immediately. ^If no error 7500** (SQLITE_BUSY or otherwise) is encountered while processing the attached 7501** databases, SQLITE_OK is returned. 7502** 7503** ^If database zDb is the name of an attached database that is not in WAL 7504** mode, SQLITE_OK is returned and both *pnLog and *pnCkpt set to -1. ^If 7505** zDb is not NULL (or a zero length string) and is not the name of any 7506** attached database, SQLITE_ERROR is returned to the caller. 7507** 7508** ^Unless it returns SQLITE_MISUSE, 7509** the sqlite3_wal_checkpoint_v2() interface 7510** sets the error information that is queried by 7511** [sqlite3_errcode()] and [sqlite3_errmsg()]. 7512** 7513** ^The [PRAGMA wal_checkpoint] command can be used to invoke this interface 7514** from SQL. 7515*/ 7516int sqlite3_wal_checkpoint_v2( 7517 sqlite3 *db, /* Database handle */ 7518 const char *zDb, /* Name of attached database (or NULL) */ 7519 int eMode, /* SQLITE_CHECKPOINT_* value */ 7520 int *pnLog, /* OUT: Size of WAL log in frames */ 7521 int *pnCkpt /* OUT: Total number of frames checkpointed */ 7522); 7523 7524/* 7525** CAPI3REF: Checkpoint Mode Values 7526** KEYWORDS: {checkpoint mode} 7527** 7528** These constants define all valid values for the "checkpoint mode" passed 7529** as the third parameter to the [sqlite3_wal_checkpoint_v2()] interface. 7530** See the [sqlite3_wal_checkpoint_v2()] documentation for details on the 7531** meaning of each of these checkpoint modes. 7532*/ 7533#define SQLITE_CHECKPOINT_PASSIVE 0 /* Do as much as possible w/o blocking */ 7534#define SQLITE_CHECKPOINT_FULL 1 /* Wait for writers, then checkpoint */ 7535#define SQLITE_CHECKPOINT_RESTART 2 /* Like FULL but wait for for readers */ 7536#define SQLITE_CHECKPOINT_TRUNCATE 3 /* Like RESTART but also truncate WAL */ 7537 7538/* 7539** CAPI3REF: Virtual Table Interface Configuration 7540** 7541** This function may be called by either the [xConnect] or [xCreate] method 7542** of a [virtual table] implementation to configure 7543** various facets of the virtual table interface. 7544** 7545** If this interface is invoked outside the context of an xConnect or 7546** xCreate virtual table method then the behavior is undefined. 7547** 7548** At present, there is only one option that may be configured using 7549** this function. (See [SQLITE_VTAB_CONSTRAINT_SUPPORT].) Further options 7550** may be added in the future. 7551*/ 7552int sqlite3_vtab_config(sqlite3*, int op, ...); 7553 7554/* 7555** CAPI3REF: Virtual Table Configuration Options 7556** 7557** These macros define the various options to the 7558** [sqlite3_vtab_config()] interface that [virtual table] implementations 7559** can use to customize and optimize their behavior. 7560** 7561** <dl> 7562** <dt>SQLITE_VTAB_CONSTRAINT_SUPPORT 7563** <dd>Calls of the form 7564** [sqlite3_vtab_config](db,SQLITE_VTAB_CONSTRAINT_SUPPORT,X) are supported, 7565** where X is an integer. If X is zero, then the [virtual table] whose 7566** [xCreate] or [xConnect] method invoked [sqlite3_vtab_config()] does not 7567** support constraints. In this configuration (which is the default) if 7568** a call to the [xUpdate] method returns [SQLITE_CONSTRAINT], then the entire 7569** statement is rolled back as if [ON CONFLICT | OR ABORT] had been 7570** specified as part of the users SQL statement, regardless of the actual 7571** ON CONFLICT mode specified. 7572** 7573** If X is non-zero, then the virtual table implementation guarantees 7574** that if [xUpdate] returns [SQLITE_CONSTRAINT], it will do so before 7575** any modifications to internal or persistent data structures have been made. 7576** If the [ON CONFLICT] mode is ABORT, FAIL, IGNORE or ROLLBACK, SQLite 7577** is able to roll back a statement or database transaction, and abandon 7578** or continue processing the current SQL statement as appropriate. 7579** If the ON CONFLICT mode is REPLACE and the [xUpdate] method returns 7580** [SQLITE_CONSTRAINT], SQLite handles this as if the ON CONFLICT mode 7581** had been ABORT. 7582** 7583** Virtual table implementations that are required to handle OR REPLACE 7584** must do so within the [xUpdate] method. If a call to the 7585** [sqlite3_vtab_on_conflict()] function indicates that the current ON 7586** CONFLICT policy is REPLACE, the virtual table implementation should 7587** silently replace the appropriate rows within the xUpdate callback and 7588** return SQLITE_OK. Or, if this is not possible, it may return 7589** SQLITE_CONSTRAINT, in which case SQLite falls back to OR ABORT 7590** constraint handling. 7591** </dl> 7592*/ 7593#define SQLITE_VTAB_CONSTRAINT_SUPPORT 1 7594 7595/* 7596** CAPI3REF: Determine The Virtual Table Conflict Policy 7597** 7598** This function may only be called from within a call to the [xUpdate] method 7599** of a [virtual table] implementation for an INSERT or UPDATE operation. ^The 7600** value returned is one of [SQLITE_ROLLBACK], [SQLITE_IGNORE], [SQLITE_FAIL], 7601** [SQLITE_ABORT], or [SQLITE_REPLACE], according to the [ON CONFLICT] mode 7602** of the SQL statement that triggered the call to the [xUpdate] method of the 7603** [virtual table]. 7604*/ 7605int sqlite3_vtab_on_conflict(sqlite3 *); 7606 7607/* 7608** CAPI3REF: Conflict resolution modes 7609** KEYWORDS: {conflict resolution mode} 7610** 7611** These constants are returned by [sqlite3_vtab_on_conflict()] to 7612** inform a [virtual table] implementation what the [ON CONFLICT] mode 7613** is for the SQL statement being evaluated. 7614** 7615** Note that the [SQLITE_IGNORE] constant is also used as a potential 7616** return value from the [sqlite3_set_authorizer()] callback and that 7617** [SQLITE_ABORT] is also a [result code]. 7618*/ 7619#define SQLITE_ROLLBACK 1 7620/* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback */ 7621#define SQLITE_FAIL 3 7622/* #define SQLITE_ABORT 4 // Also an error code */ 7623#define SQLITE_REPLACE 5 7624 7625/* 7626** CAPI3REF: Prepared Statement Scan Status Opcodes 7627** KEYWORDS: {scanstatus options} 7628** 7629** The following constants can be used for the T parameter to the 7630** [sqlite3_stmt_scanstatus(S,X,T,V)] interface. Each constant designates a 7631** different metric for sqlite3_stmt_scanstatus() to return. 7632** 7633** When the value returned to V is a string, space to hold that string is 7634** managed by the prepared statement S and will be automatically freed when 7635** S is finalized. 7636** 7637** <dl> 7638** [[SQLITE_SCANSTAT_NLOOP]] <dt>SQLITE_SCANSTAT_NLOOP</dt> 7639** <dd>^The [sqlite3_int64] variable pointed to by the T parameter will be 7640** set to the total number of times that the X-th loop has run.</dd> 7641** 7642** [[SQLITE_SCANSTAT_NVISIT]] <dt>SQLITE_SCANSTAT_NVISIT</dt> 7643** <dd>^The [sqlite3_int64] variable pointed to by the T parameter will be set 7644** to the total number of rows examined by all iterations of the X-th loop.</dd> 7645** 7646** [[SQLITE_SCANSTAT_EST]] <dt>SQLITE_SCANSTAT_EST</dt> 7647** <dd>^The "double" variable pointed to by the T parameter will be set to the 7648** query planner's estimate for the average number of rows output from each 7649** iteration of the X-th loop. If the query planner's estimates was accurate, 7650** then this value will approximate the quotient NVISIT/NLOOP and the 7651** product of this value for all prior loops with the same SELECTID will 7652** be the NLOOP value for the current loop. 7653** 7654** [[SQLITE_SCANSTAT_NAME]] <dt>SQLITE_SCANSTAT_NAME</dt> 7655** <dd>^The "const char *" variable pointed to by the T parameter will be set 7656** to a zero-terminated UTF-8 string containing the name of the index or table 7657** used for the X-th loop. 7658** 7659** [[SQLITE_SCANSTAT_EXPLAIN]] <dt>SQLITE_SCANSTAT_EXPLAIN</dt> 7660** <dd>^The "const char *" variable pointed to by the T parameter will be set 7661** to a zero-terminated UTF-8 string containing the [EXPLAIN QUERY PLAN] 7662** description for the X-th loop. 7663** 7664** [[SQLITE_SCANSTAT_SELECTID]] <dt>SQLITE_SCANSTAT_SELECT</dt> 7665** <dd>^The "int" variable pointed to by the T parameter will be set to the 7666** "select-id" for the X-th loop. The select-id identifies which query or 7667** subquery the loop is part of. The main query has a select-id of zero. 7668** The select-id is the same value as is output in the first column 7669** of an [EXPLAIN QUERY PLAN] query. 7670** </dl> 7671*/ 7672#define SQLITE_SCANSTAT_NLOOP 0 7673#define SQLITE_SCANSTAT_NVISIT 1 7674#define SQLITE_SCANSTAT_EST 2 7675#define SQLITE_SCANSTAT_NAME 3 7676#define SQLITE_SCANSTAT_EXPLAIN 4 7677#define SQLITE_SCANSTAT_SELECTID 5 7678 7679/* 7680** CAPI3REF: Prepared Statement Scan Status 7681** METHOD: sqlite3_stmt 7682** 7683** This interface returns information about the predicted and measured 7684** performance for pStmt. Advanced applications can use this 7685** interface to compare the predicted and the measured performance and 7686** issue warnings and/or rerun [ANALYZE] if discrepancies are found. 7687** 7688** Since this interface is expected to be rarely used, it is only 7689** available if SQLite is compiled using the [SQLITE_ENABLE_STMT_SCANSTATUS] 7690** compile-time option. 7691** 7692** The "iScanStatusOp" parameter determines which status information to return. 7693** The "iScanStatusOp" must be one of the [scanstatus options] or the behavior 7694** of this interface is undefined. 7695** ^The requested measurement is written into a variable pointed to by 7696** the "pOut" parameter. 7697** Parameter "idx" identifies the specific loop to retrieve statistics for. 7698** Loops are numbered starting from zero. ^If idx is out of range - less than 7699** zero or greater than or equal to the total number of loops used to implement 7700** the statement - a non-zero value is returned and the variable that pOut 7701** points to is unchanged. 7702** 7703** ^Statistics might not be available for all loops in all statements. ^In cases 7704** where there exist loops with no available statistics, this function behaves 7705** as if the loop did not exist - it returns non-zero and leave the variable 7706** that pOut points to unchanged. 7707** 7708** See also: [sqlite3_stmt_scanstatus_reset()] 7709*/ 7710int sqlite3_stmt_scanstatus( 7711 sqlite3_stmt *pStmt, /* Prepared statement for which info desired */ 7712 int idx, /* Index of loop to report on */ 7713 int iScanStatusOp, /* Information desired. SQLITE_SCANSTAT_* */ 7714 void *pOut /* Result written here */ 7715); 7716 7717/* 7718** CAPI3REF: Zero Scan-Status Counters 7719** METHOD: sqlite3_stmt 7720** 7721** ^Zero all [sqlite3_stmt_scanstatus()] related event counters. 7722** 7723** This API is only available if the library is built with pre-processor 7724** symbol [SQLITE_ENABLE_STMT_SCANSTATUS] defined. 7725*/ 7726void sqlite3_stmt_scanstatus_reset(sqlite3_stmt*); 7727 7728 7729/* 7730** Undo the hack that converts floating point types to integer for 7731** builds on processors without floating point support. 7732*/ 7733#ifdef SQLITE_OMIT_FLOATING_POINT 7734# undef double 7735#endif 7736 7737#ifdef __cplusplus 7738} /* End of the 'extern "C"' block */ 7739#endif 7740#endif /* _SQLITE3_H_ */ 7741