Coverage Report

Created: 2021-09-21 23:33

/home/liu/buildslave/linux-x64-runtests/build/lib/3rdparty/sqlite3/sqlite3.h
Line
Count
Source (jump to first uncovered line)
1
/*
2
** 2001-09-15
3
**
4
** The author disclaims copyright to this source code.  In place of
5
** a legal notice, here is a blessing:
6
**
7
**    May you do good and not evil.
8
**    May you find forgiveness for yourself and forgive others.
9
**    May you share freely, never taking more than you give.
10
**
11
*************************************************************************
12
** This header file defines the interface that the SQLite library
13
** presents to client programs.  If a C-function, structure, datatype,
14
** or constant definition does not appear in this file, then it is
15
** not a published API of SQLite, is subject to change without
16
** notice, and should not be referenced by programs that use SQLite.
17
**
18
** Some of the definitions that are in this file are marked as
19
** "experimental".  Experimental interfaces are normally new
20
** features recently added to SQLite.  We do not anticipate changes
21
** to experimental interfaces but reserve the right to make minor changes
22
** if experience from use "in the wild" suggest such changes are prudent.
23
**
24
** The official C-language API documentation for SQLite is derived
25
** from comments in this file.  This file is the authoritative source
26
** on how SQLite interfaces are supposed to operate.
27
**
28
** The name of this file under configuration management is "sqlite.h.in".
29
** The makefile makes some minor changes to this file (such as inserting
30
** the version number) and changes its name to "sqlite3.h" as
31
** part of the build process.
32
*/
33
#ifndef SQLITE3_H
34
#define SQLITE3_H
35
#include <stdarg.h>     /* Needed for the definition of va_list */
36
37
/*
38
** Make sure we can call this stuff from C++.
39
*/
40
#ifdef __cplusplus
41
extern "C" {
42
#endif
43
44
45
/*
46
** Provide the ability to override linkage features of the interface.
47
*/
48
#ifndef SQLITE_EXTERN
49
# define SQLITE_EXTERN extern
50
#endif
51
#ifndef SQLITE_API
52
# define SQLITE_API
53
#endif
54
#ifndef SQLITE_CDECL
55
# define SQLITE_CDECL
56
#endif
57
#ifndef SQLITE_APICALL
58
# define SQLITE_APICALL
59
#endif
60
#ifndef SQLITE_STDCALL
61
# define SQLITE_STDCALL SQLITE_APICALL
62
#endif
63
#ifndef SQLITE_CALLBACK
64
# define SQLITE_CALLBACK
65
#endif
66
#ifndef SQLITE_SYSAPI
67
# define SQLITE_SYSAPI
68
#endif
69
70
/*
71
** These no-op macros are used in front of interfaces to mark those
72
** interfaces as either deprecated or experimental.  New applications
73
** should not use deprecated interfaces - they are supported for backwards
74
** compatibility only.  Application writers should be aware that
75
** experimental interfaces are subject to change in point releases.
76
**
77
** These macros used to resolve to various kinds of compiler magic that
78
** would generate warning messages when they were used.  But that
79
** compiler magic ended up generating such a flurry of bug reports
80
** that we have taken it all out and gone back to using simple
81
** noop macros.
82
*/
83
#define SQLITE_DEPRECATED
84
#define SQLITE_EXPERIMENTAL
85
86
/*
87
** Ensure these symbols were not defined by some previous header file.
88
*/
89
#ifdef SQLITE_VERSION
90
# undef SQLITE_VERSION
91
#endif
92
#ifdef SQLITE_VERSION_NUMBER
93
# undef SQLITE_VERSION_NUMBER
94
#endif
95
96
/*
97
** CAPI3REF: Compile-Time Library Version Numbers
98
**
99
** ^(The [SQLITE_VERSION] C preprocessor macro in the sqlite3.h header
100
** evaluates to a string literal that is the SQLite version in the
101
** format "X.Y.Z" where X is the major version number (always 3 for
102
** SQLite3) and Y is the minor version number and Z is the release number.)^
103
** ^(The [SQLITE_VERSION_NUMBER] C preprocessor macro resolves to an integer
104
** with the value (X*1000000 + Y*1000 + Z) where X, Y, and Z are the same
105
** numbers used in [SQLITE_VERSION].)^
106
** The SQLITE_VERSION_NUMBER for any given release of SQLite will also
107
** be larger than the release from which it is derived.  Either Y will
108
** be held constant and Z will be incremented or else Y will be incremented
109
** and Z will be reset to zero.
110
**
111
** Since [version 3.6.18] ([dateof:3.6.18]),
112
** SQLite source code has been stored in the
113
** <a href="http://www.fossil-scm.org/">Fossil configuration management
114
** system</a>.  ^The SQLITE_SOURCE_ID macro evaluates to
115
** a string which identifies a particular check-in of SQLite
116
** within its configuration management system.  ^The SQLITE_SOURCE_ID
117
** string contains the date and time of the check-in (UTC) and a SHA1
118
** or SHA3-256 hash of the entire source tree.  If the source code has
119
** been edited in any way since it was last checked in, then the last
120
** four hexadecimal digits of the hash may be modified.
121
**
122
** See also: [sqlite3_libversion()],
123
** [sqlite3_libversion_number()], [sqlite3_sourceid()],
124
** [sqlite_version()] and [sqlite_source_id()].
125
*/
126
#define SQLITE_VERSION        "3.36.0"
127
#define SQLITE_VERSION_NUMBER 3036000
128
#define SQLITE_SOURCE_ID      "2021-06-18 18:36:39 5c9a6c06871cb9fe42814af9c039eb6da5427a6ec28f187af7ebfb62eafa66e5"
129
130
/*
131
** CAPI3REF: Run-Time Library Version Numbers
132
** KEYWORDS: sqlite3_version sqlite3_sourceid
133
**
134
** These interfaces provide the same information as the [SQLITE_VERSION],
135
** [SQLITE_VERSION_NUMBER], and [SQLITE_SOURCE_ID] C preprocessor macros
136
** but are associated with the library instead of the header file.  ^(Cautious
137
** programmers might include assert() statements in their application to
138
** verify that values returned by these interfaces match the macros in
139
** the header, and thus ensure that the application is
140
** compiled with matching library and header files.
141
**
142
** <blockquote><pre>
143
** assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER );
144
** assert( strncmp(sqlite3_sourceid(),SQLITE_SOURCE_ID,80)==0 );
145
** assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0 );
146
** </pre></blockquote>)^
147
**
148
** ^The sqlite3_version[] string constant contains the text of [SQLITE_VERSION]
149
** macro.  ^The sqlite3_libversion() function returns a pointer to the
150
** to the sqlite3_version[] string constant.  The sqlite3_libversion()
151
** function is provided for use in DLLs since DLL users usually do not have
152
** direct access to string constants within the DLL.  ^The
153
** sqlite3_libversion_number() function returns an integer equal to
154
** [SQLITE_VERSION_NUMBER].  ^(The sqlite3_sourceid() function returns
155
** a pointer to a string constant whose value is the same as the
156
** [SQLITE_SOURCE_ID] C preprocessor macro.  Except if SQLite is built
157
** using an edited copy of [the amalgamation], then the last four characters
158
** of the hash might be different from [SQLITE_SOURCE_ID].)^
159
**
160
** See also: [sqlite_version()] and [sqlite_source_id()].
161
*/
162
SQLITE_API SQLITE_EXTERN const char sqlite3_version[];
163
SQLITE_API const char *sqlite3_libversion(void);
164
SQLITE_API const char *sqlite3_sourceid(void);
165
SQLITE_API int sqlite3_libversion_number(void);
166
167
/*
168
** CAPI3REF: Run-Time Library Compilation Options Diagnostics
169
**
170
** ^The sqlite3_compileoption_used() function returns 0 or 1
171
** indicating whether the specified option was defined at
172
** compile time.  ^The SQLITE_ prefix may be omitted from the
173
** option name passed to sqlite3_compileoption_used().
174
**
175
** ^The sqlite3_compileoption_get() function allows iterating
176
** over the list of options that were defined at compile time by
177
** returning the N-th compile time option string.  ^If N is out of range,
178
** sqlite3_compileoption_get() returns a NULL pointer.  ^The SQLITE_
179
** prefix is omitted from any strings returned by
180
** sqlite3_compileoption_get().
181
**
182
** ^Support for the diagnostic functions sqlite3_compileoption_used()
183
** and sqlite3_compileoption_get() may be omitted by specifying the
184
** [SQLITE_OMIT_COMPILEOPTION_DIAGS] option at compile time.
185
**
186
** See also: SQL functions [sqlite_compileoption_used()] and
187
** [sqlite_compileoption_get()] and the [compile_options pragma].
188
*/
189
#ifndef SQLITE_OMIT_COMPILEOPTION_DIAGS
190
SQLITE_API int sqlite3_compileoption_used(const char *zOptName);
191
SQLITE_API const char *sqlite3_compileoption_get(int N);
192
#else
193
# define sqlite3_compileoption_used(X) 0
194
# define sqlite3_compileoption_get(X)  ((void*)0)
195
#endif
196
197
/*
198
** CAPI3REF: Test To See If The Library Is Threadsafe
199
**
200
** ^The sqlite3_threadsafe() function returns zero if and only if
201
** SQLite was compiled with mutexing code omitted due to the
202
** [SQLITE_THREADSAFE] compile-time option being set to 0.
203
**
204
** SQLite can be compiled with or without mutexes.  When
205
** the [SQLITE_THREADSAFE] C preprocessor macro is 1 or 2, mutexes
206
** are enabled and SQLite is threadsafe.  When the
207
** [SQLITE_THREADSAFE] macro is 0,
208
** the mutexes are omitted.  Without the mutexes, it is not safe
209
** to use SQLite concurrently from more than one thread.
210
**
211
** Enabling mutexes incurs a measurable performance penalty.
212
** So if speed is of utmost importance, it makes sense to disable
213
** the mutexes.  But for maximum safety, mutexes should be enabled.
214
** ^The default behavior is for mutexes to be enabled.
215
**
216
** This interface can be used by an application to make sure that the
217
** version of SQLite that it is linking against was compiled with
218
** the desired setting of the [SQLITE_THREADSAFE] macro.
219
**
220
** This interface only reports on the compile-time mutex setting
221
** of the [SQLITE_THREADSAFE] flag.  If SQLite is compiled with
222
** SQLITE_THREADSAFE=1 or =2 then mutexes are enabled by default but
223
** can be fully or partially disabled using a call to [sqlite3_config()]
224
** with the verbs [SQLITE_CONFIG_SINGLETHREAD], [SQLITE_CONFIG_MULTITHREAD],
225
** or [SQLITE_CONFIG_SERIALIZED].  ^(The return value of the
226
** sqlite3_threadsafe() function shows only the compile-time setting of
227
** thread safety, not any run-time changes to that setting made by
228
** sqlite3_config(). In other words, the return value from sqlite3_threadsafe()
229
** is unchanged by calls to sqlite3_config().)^
230
**
231
** See the [threading mode] documentation for additional information.
232
*/
233
SQLITE_API int sqlite3_threadsafe(void);
234
235
/*
236
** CAPI3REF: Database Connection Handle
237
** KEYWORDS: {database connection} {database connections}
238
**
239
** Each open SQLite database is represented by a pointer to an instance of
240
** the opaque structure named "sqlite3".  It is useful to think of an sqlite3
241
** pointer as an object.  The [sqlite3_open()], [sqlite3_open16()], and
242
** [sqlite3_open_v2()] interfaces are its constructors, and [sqlite3_close()]
243
** and [sqlite3_close_v2()] are its destructors.  There are many other
244
** interfaces (such as
245
** [sqlite3_prepare_v2()], [sqlite3_create_function()], and
246
** [sqlite3_busy_timeout()] to name but three) that are methods on an
247
** sqlite3 object.
248
*/
249
typedef struct sqlite3 sqlite3;
250
251
/*
252
** CAPI3REF: 64-Bit Integer Types
253
** KEYWORDS: sqlite_int64 sqlite_uint64
254
**
255
** Because there is no cross-platform way to specify 64-bit integer types
256
** SQLite includes typedefs for 64-bit signed and unsigned integers.
257
**
258
** The sqlite3_int64 and sqlite3_uint64 are the preferred type definitions.
259
** The sqlite_int64 and sqlite_uint64 types are supported for backwards
260
** compatibility only.
261
**
262
** ^The sqlite3_int64 and sqlite_int64 types can store integer values
263
** between -9223372036854775808 and +9223372036854775807 inclusive.  ^The
264
** sqlite3_uint64 and sqlite_uint64 types can store integer values
265
** between 0 and +18446744073709551615 inclusive.
266
*/
267
#ifdef SQLITE_INT64_TYPE
268
  typedef SQLITE_INT64_TYPE sqlite_int64;
269
# ifdef SQLITE_UINT64_TYPE
270
    typedef SQLITE_UINT64_TYPE sqlite_uint64;
271
# else
272
    typedef unsigned SQLITE_INT64_TYPE sqlite_uint64;
273
# endif
274
#elif defined(_MSC_VER) || defined(__BORLANDC__)
275
  typedef __int64 sqlite_int64;
276
  typedef unsigned __int64 sqlite_uint64;
277
#else
278
  typedef long long int sqlite_int64;
279
  typedef unsigned long long int sqlite_uint64;
280
#endif
281
typedef sqlite_int64 sqlite3_int64;
282
typedef sqlite_uint64 sqlite3_uint64;
283
284
/*
285
** If compiling for a processor that lacks floating point support,
286
** substitute integer for floating-point.
287
*/
288
#ifdef SQLITE_OMIT_FLOATING_POINT
289
# define double sqlite3_int64
290
#endif
291
292
/*
293
** CAPI3REF: Closing A Database Connection
294
** DESTRUCTOR: sqlite3
295
**
296
** ^The sqlite3_close() and sqlite3_close_v2() routines are destructors
297
** for the [sqlite3] object.
298
** ^Calls to sqlite3_close() and sqlite3_close_v2() return [SQLITE_OK] if
299
** the [sqlite3] object is successfully destroyed and all associated
300
** resources are deallocated.
301
**
302
** Ideally, applications should [sqlite3_finalize | finalize] all
303
** [prepared statements], [sqlite3_blob_close | close] all [BLOB handles], and
304
** [sqlite3_backup_finish | finish] all [sqlite3_backup] objects associated
305
** with the [sqlite3] object prior to attempting to close the object.
306
** ^If the database connection is associated with unfinalized prepared
307
** statements, BLOB handlers, and/or unfinished sqlite3_backup objects then
308
** sqlite3_close() will leave the database connection open and return
309
** [SQLITE_BUSY]. ^If sqlite3_close_v2() is called with unfinalized prepared
310
** statements, unclosed BLOB handlers, and/or unfinished sqlite3_backups,
311
** it returns [SQLITE_OK] regardless, but instead of deallocating the database
312
** connection immediately, it marks the database connection as an unusable
313
** "zombie" and makes arrangements to automatically deallocate the database
314
** connection after all prepared statements are finalized, all BLOB handles
315
** are closed, and all backups have finished. The sqlite3_close_v2() interface
316
** is intended for use with host languages that are garbage collected, and
317
** where the order in which destructors are called is arbitrary.
318
**
319
** ^If an [sqlite3] object is destroyed while a transaction is open,
320
** the transaction is automatically rolled back.
321
**
322
** The C parameter to [sqlite3_close(C)] and [sqlite3_close_v2(C)]
323
** must be either a NULL
324
** pointer or an [sqlite3] object pointer obtained
325
** from [sqlite3_open()], [sqlite3_open16()], or
326
** [sqlite3_open_v2()], and not previously closed.
327
** ^Calling sqlite3_close() or sqlite3_close_v2() with a NULL pointer
328
** argument is a harmless no-op.
329
*/
330
SQLITE_API int sqlite3_close(sqlite3*);
331
SQLITE_API int sqlite3_close_v2(sqlite3*);
332
333
/*
334
** The type for a callback function.
335
** This is legacy and deprecated.  It is included for historical
336
** compatibility and is not documented.
337
*/
338
typedef int (*sqlite3_callback)(void*,int,char**, char**);
339
340
/*
341
** CAPI3REF: One-Step Query Execution Interface
342
** METHOD: sqlite3
343
**
344
** The sqlite3_exec() interface is a convenience wrapper around
345
** [sqlite3_prepare_v2()], [sqlite3_step()], and [sqlite3_finalize()],
346
** that allows an application to run multiple statements of SQL
347
** without having to use a lot of C code.
348
**
349
** ^The sqlite3_exec() interface runs zero or more UTF-8 encoded,
350
** semicolon-separate SQL statements passed into its 2nd argument,
351
** in the context of the [database connection] passed in as its 1st
352
** argument.  ^If the callback function of the 3rd argument to
353
** sqlite3_exec() is not NULL, then it is invoked for each result row
354
** coming out of the evaluated SQL statements.  ^The 4th argument to
355
** sqlite3_exec() is relayed through to the 1st argument of each
356
** callback invocation.  ^If the callback pointer to sqlite3_exec()
357
** is NULL, then no callback is ever invoked and result rows are
358
** ignored.
359
**
360
** ^If an error occurs while evaluating the SQL statements passed into
361
** sqlite3_exec(), then execution of the current statement stops and
362
** subsequent statements are skipped.  ^If the 5th parameter to sqlite3_exec()
363
** is not NULL then any error message is written into memory obtained
364
** from [sqlite3_malloc()] and passed back through the 5th parameter.
365
** To avoid memory leaks, the application should invoke [sqlite3_free()]
366
** on error message strings returned through the 5th parameter of
367
** sqlite3_exec() after the error message string is no longer needed.
368
** ^If the 5th parameter to sqlite3_exec() is not NULL and no errors
369
** occur, then sqlite3_exec() sets the pointer in its 5th parameter to
370
** NULL before returning.
371
**
372
** ^If an sqlite3_exec() callback returns non-zero, the sqlite3_exec()
373
** routine returns SQLITE_ABORT without invoking the callback again and
374
** without running any subsequent SQL statements.
375
**
376
** ^The 2nd argument to the sqlite3_exec() callback function is the
377
** number of columns in the result.  ^The 3rd argument to the sqlite3_exec()
378
** callback is an array of pointers to strings obtained as if from
379
** [sqlite3_column_text()], one for each column.  ^If an element of a
380
** result row is NULL then the corresponding string pointer for the
381
** sqlite3_exec() callback is a NULL pointer.  ^The 4th argument to the
382
** sqlite3_exec() callback is an array of pointers to strings where each
383
** entry represents the name of corresponding result column as obtained
384
** from [sqlite3_column_name()].
385
**
386
** ^If the 2nd parameter to sqlite3_exec() is a NULL pointer, a pointer
387
** to an empty string, or a pointer that contains only whitespace and/or
388
** SQL comments, then no SQL statements are evaluated and the database
389
** is not changed.
390
**
391
** Restrictions:
392
**
393
** <ul>
394
** <li> The application must ensure that the 1st parameter to sqlite3_exec()
395
**      is a valid and open [database connection].
396
** <li> The application must not close the [database connection] specified by
397
**      the 1st parameter to sqlite3_exec() while sqlite3_exec() is running.
398
** <li> The application must not modify the SQL statement text passed into
399
**      the 2nd parameter of sqlite3_exec() while sqlite3_exec() is running.
400
** </ul>
401
*/
402
SQLITE_API int sqlite3_exec(
403
  sqlite3*,                                  /* An open database */
404
  const char *sql,                           /* SQL to be evaluated */
405
  int (*callback)(void*,int,char**,char**),  /* Callback function */
406
  void *,                                    /* 1st argument to callback */
407
  char **errmsg                              /* Error msg written here */
408
);
409
410
/*
411
** CAPI3REF: Result Codes
412
** KEYWORDS: {result code definitions}
413
**
414
** Many SQLite functions return an integer result code from the set shown
415
** here in order to indicate success or failure.
416
**
417
** New error codes may be added in future versions of SQLite.
418
**
419
** See also: [extended result code definitions]
420
*/
421
26
#define SQLITE_OK           0   /* Successful result */
422
/* beginning-of-error-codes */
423
#define SQLITE_ERROR        1   /* Generic error */
424
#define SQLITE_INTERNAL     2   /* Internal logic error in SQLite */
425
#define SQLITE_PERM         3   /* Access permission denied */
426
#define SQLITE_ABORT        4   /* Callback routine requested an abort */
427
#define SQLITE_BUSY         5   /* The database file is locked */
428
#define SQLITE_LOCKED       6   /* A table in the database is locked */
429
#define SQLITE_NOMEM        7   /* A malloc() failed */
430
#define SQLITE_READONLY     8   /* Attempt to write a readonly database */
431
#define SQLITE_INTERRUPT    9   /* Operation terminated by sqlite3_interrupt()*/
432
#define SQLITE_IOERR       10   /* Some kind of disk I/O error occurred */
433
#define SQLITE_CORRUPT     11   /* The database disk image is malformed */
434
#define SQLITE_NOTFOUND    12   /* Unknown opcode in sqlite3_file_control() */
435
#define SQLITE_FULL        13   /* Insertion failed because database is full */
436
#define SQLITE_CANTOPEN    14   /* Unable to open the database file */
437
#define SQLITE_PROTOCOL    15   /* Database lock protocol error */
438
#define SQLITE_EMPTY       16   /* Internal use only */
439
#define SQLITE_SCHEMA      17   /* The database schema changed */
440
#define SQLITE_TOOBIG      18   /* String or BLOB exceeds size limit */
441
#define SQLITE_CONSTRAINT  19   /* Abort due to constraint violation */
442
#define SQLITE_MISMATCH    20   /* Data type mismatch */
443
#define SQLITE_MISUSE      21   /* Library used incorrectly */
444
#define SQLITE_NOLFS       22   /* Uses OS features not supported on host */
445
#define SQLITE_AUTH        23   /* Authorization denied */
446
#define SQLITE_FORMAT      24   /* Not used */
447
#define SQLITE_RANGE       25   /* 2nd parameter to sqlite3_bind out of range */
448
#define SQLITE_NOTADB      26   /* File opened that is not a database file */
449
#define SQLITE_NOTICE      27   /* Notifications from sqlite3_log() */
450
#define SQLITE_WARNING     28   /* Warnings from sqlite3_log() */
451
110
#define SQLITE_ROW         100  /* sqlite3_step() has another row ready */
452
#define SQLITE_DONE        101  /* sqlite3_step() has finished executing */
453
/* end-of-error-codes */
454
455
/*
456
** CAPI3REF: Extended Result Codes
457
** KEYWORDS: {extended result code definitions}
458
**
459
** In its default configuration, SQLite API routines return one of 30 integer
460
** [result codes].  However, experience has shown that many of
461
** these result codes are too coarse-grained.  They do not provide as
462
** much information about problems as programmers might like.  In an effort to
463
** address this, newer versions of SQLite (version 3.3.8 [dateof:3.3.8]
464
** and later) include
465
** support for additional result codes that provide more detailed information
466
** about errors. These [extended result codes] are enabled or disabled
467
** on a per database connection basis using the
468
** [sqlite3_extended_result_codes()] API.  Or, the extended code for
469
** the most recent error can be obtained using
470
** [sqlite3_extended_errcode()].
471
*/
472
#define SQLITE_ERROR_MISSING_COLLSEQ   (SQLITE_ERROR | (1<<8))
473
#define SQLITE_ERROR_RETRY             (SQLITE_ERROR | (2<<8))
474
#define SQLITE_ERROR_SNAPSHOT          (SQLITE_ERROR | (3<<8))
475
#define SQLITE_IOERR_READ              (SQLITE_IOERR | (1<<8))
476
#define SQLITE_IOERR_SHORT_READ        (SQLITE_IOERR | (2<<8))
477
#define SQLITE_IOERR_WRITE             (SQLITE_IOERR | (3<<8))
478
#define SQLITE_IOERR_FSYNC             (SQLITE_IOERR | (4<<8))
479
#define SQLITE_IOERR_DIR_FSYNC         (SQLITE_IOERR | (5<<8))
480
#define SQLITE_IOERR_TRUNCATE          (SQLITE_IOERR | (6<<8))
481
#define SQLITE_IOERR_FSTAT             (SQLITE_IOERR | (7<<8))
482
#define SQLITE_IOERR_UNLOCK            (SQLITE_IOERR | (8<<8))
483
#define SQLITE_IOERR_RDLOCK            (SQLITE_IOERR | (9<<8))
484
#define SQLITE_IOERR_DELETE            (SQLITE_IOERR | (10<<8))
485
#define SQLITE_IOERR_BLOCKED           (SQLITE_IOERR | (11<<8))
486
#define SQLITE_IOERR_NOMEM             (SQLITE_IOERR | (12<<8))
487
#define SQLITE_IOERR_ACCESS            (SQLITE_IOERR | (13<<8))
488
#define SQLITE_IOERR_CHECKRESERVEDLOCK (SQLITE_IOERR | (14<<8))
489
#define SQLITE_IOERR_LOCK              (SQLITE_IOERR | (15<<8))
490
#define SQLITE_IOERR_CLOSE             (SQLITE_IOERR | (16<<8))
491
#define SQLITE_IOERR_DIR_CLOSE         (SQLITE_IOERR | (17<<8))
492
#define SQLITE_IOERR_SHMOPEN           (SQLITE_IOERR | (18<<8))
493
#define SQLITE_IOERR_SHMSIZE           (SQLITE_IOERR | (19<<8))
494
#define SQLITE_IOERR_SHMLOCK           (SQLITE_IOERR | (20<<8))
495
#define SQLITE_IOERR_SHMMAP            (SQLITE_IOERR | (21<<8))
496
#define SQLITE_IOERR_SEEK              (SQLITE_IOERR | (22<<8))
497
#define SQLITE_IOERR_DELETE_NOENT      (SQLITE_IOERR | (23<<8))
498
#define SQLITE_IOERR_MMAP              (SQLITE_IOERR | (24<<8))
499
#define SQLITE_IOERR_GETTEMPPATH       (SQLITE_IOERR | (25<<8))
500
#define SQLITE_IOERR_CONVPATH          (SQLITE_IOERR | (26<<8))
501
#define SQLITE_IOERR_VNODE             (SQLITE_IOERR | (27<<8))
502
#define SQLITE_IOERR_AUTH              (SQLITE_IOERR | (28<<8))
503
#define SQLITE_IOERR_BEGIN_ATOMIC      (SQLITE_IOERR | (29<<8))
504
#define SQLITE_IOERR_COMMIT_ATOMIC     (SQLITE_IOERR | (30<<8))
505
#define SQLITE_IOERR_ROLLBACK_ATOMIC   (SQLITE_IOERR | (31<<8))
506
#define SQLITE_IOERR_DATA              (SQLITE_IOERR | (32<<8))
507
#define SQLITE_IOERR_CORRUPTFS         (SQLITE_IOERR | (33<<8))
508
#define SQLITE_LOCKED_SHAREDCACHE      (SQLITE_LOCKED |  (1<<8))
509
#define SQLITE_LOCKED_VTAB             (SQLITE_LOCKED |  (2<<8))
510
#define SQLITE_BUSY_RECOVERY           (SQLITE_BUSY   |  (1<<8))
511
#define SQLITE_BUSY_SNAPSHOT           (SQLITE_BUSY   |  (2<<8))
512
#define SQLITE_BUSY_TIMEOUT            (SQLITE_BUSY   |  (3<<8))
513
#define SQLITE_CANTOPEN_NOTEMPDIR      (SQLITE_CANTOPEN | (1<<8))
514
#define SQLITE_CANTOPEN_ISDIR          (SQLITE_CANTOPEN | (2<<8))
515
#define SQLITE_CANTOPEN_FULLPATH       (SQLITE_CANTOPEN | (3<<8))
516
#define SQLITE_CANTOPEN_CONVPATH       (SQLITE_CANTOPEN | (4<<8))
517
#define SQLITE_CANTOPEN_DIRTYWAL       (SQLITE_CANTOPEN | (5<<8)) /* Not Used */
518
#define SQLITE_CANTOPEN_SYMLINK        (SQLITE_CANTOPEN | (6<<8))
519
#define SQLITE_CORRUPT_VTAB            (SQLITE_CORRUPT | (1<<8))
520
#define SQLITE_CORRUPT_SEQUENCE        (SQLITE_CORRUPT | (2<<8))
521
#define SQLITE_CORRUPT_INDEX           (SQLITE_CORRUPT | (3<<8))
522
#define SQLITE_READONLY_RECOVERY       (SQLITE_READONLY | (1<<8))
523
#define SQLITE_READONLY_CANTLOCK       (SQLITE_READONLY | (2<<8))
524
#define SQLITE_READONLY_ROLLBACK       (SQLITE_READONLY | (3<<8))
525
#define SQLITE_READONLY_DBMOVED        (SQLITE_READONLY | (4<<8))
526
#define SQLITE_READONLY_CANTINIT       (SQLITE_READONLY | (5<<8))
527
#define SQLITE_READONLY_DIRECTORY      (SQLITE_READONLY | (6<<8))
528
#define SQLITE_ABORT_ROLLBACK          (SQLITE_ABORT | (2<<8))
529
#define SQLITE_CONSTRAINT_CHECK        (SQLITE_CONSTRAINT | (1<<8))
530
#define SQLITE_CONSTRAINT_COMMITHOOK   (SQLITE_CONSTRAINT | (2<<8))
531
#define SQLITE_CONSTRAINT_FOREIGNKEY   (SQLITE_CONSTRAINT | (3<<8))
532
#define SQLITE_CONSTRAINT_FUNCTION     (SQLITE_CONSTRAINT | (4<<8))
533
#define SQLITE_CONSTRAINT_NOTNULL      (SQLITE_CONSTRAINT | (5<<8))
534
#define SQLITE_CONSTRAINT_PRIMARYKEY   (SQLITE_CONSTRAINT | (6<<8))
535
#define SQLITE_CONSTRAINT_TRIGGER      (SQLITE_CONSTRAINT | (7<<8))
536
#define SQLITE_CONSTRAINT_UNIQUE       (SQLITE_CONSTRAINT | (8<<8))
537
#define SQLITE_CONSTRAINT_VTAB         (SQLITE_CONSTRAINT | (9<<8))
538
#define SQLITE_CONSTRAINT_ROWID        (SQLITE_CONSTRAINT |(10<<8))
539
#define SQLITE_CONSTRAINT_PINNED       (SQLITE_CONSTRAINT |(11<<8))
540
#define SQLITE_NOTICE_RECOVER_WAL      (SQLITE_NOTICE | (1<<8))
541
#define SQLITE_NOTICE_RECOVER_ROLLBACK (SQLITE_NOTICE | (2<<8))
542
#define SQLITE_WARNING_AUTOINDEX       (SQLITE_WARNING | (1<<8))
543
#define SQLITE_AUTH_USER               (SQLITE_AUTH | (1<<8))
544
#define SQLITE_OK_LOAD_PERMANENTLY     (SQLITE_OK | (1<<8))
545
#define SQLITE_OK_SYMLINK              (SQLITE_OK | (2<<8))
546
547
/*
548
** CAPI3REF: Flags For File Open Operations
549
**
550
** These bit values are intended for use in the
551
** 3rd parameter to the [sqlite3_open_v2()] interface and
552
** in the 4th parameter to the [sqlite3_vfs.xOpen] method.
553
*/
554
#define SQLITE_OPEN_READONLY         0x00000001  /* Ok for sqlite3_open_v2() */
555
#define SQLITE_OPEN_READWRITE        0x00000002  /* Ok for sqlite3_open_v2() */
556
#define SQLITE_OPEN_CREATE           0x00000004  /* Ok for sqlite3_open_v2() */
557
#define SQLITE_OPEN_DELETEONCLOSE    0x00000008  /* VFS only */
558
#define SQLITE_OPEN_EXCLUSIVE        0x00000010  /* VFS only */
559
#define SQLITE_OPEN_AUTOPROXY        0x00000020  /* VFS only */
560
#define SQLITE_OPEN_URI              0x00000040  /* Ok for sqlite3_open_v2() */
561
#define SQLITE_OPEN_MEMORY           0x00000080  /* Ok for sqlite3_open_v2() */
562
#define SQLITE_OPEN_MAIN_DB          0x00000100  /* VFS only */
563
#define SQLITE_OPEN_TEMP_DB          0x00000200  /* VFS only */
564
#define SQLITE_OPEN_TRANSIENT_DB     0x00000400  /* VFS only */
565
#define SQLITE_OPEN_MAIN_JOURNAL     0x00000800  /* VFS only */
566
#define SQLITE_OPEN_TEMP_JOURNAL     0x00001000  /* VFS only */
567
#define SQLITE_OPEN_SUBJOURNAL       0x00002000  /* VFS only */
568
#define SQLITE_OPEN_SUPER_JOURNAL    0x00004000  /* VFS only */
569
#define SQLITE_OPEN_NOMUTEX          0x00008000  /* Ok for sqlite3_open_v2() */
570
#define SQLITE_OPEN_FULLMUTEX        0x00010000  /* Ok for sqlite3_open_v2() */
571
#define SQLITE_OPEN_SHAREDCACHE      0x00020000  /* Ok for sqlite3_open_v2() */
572
#define SQLITE_OPEN_PRIVATECACHE     0x00040000  /* Ok for sqlite3_open_v2() */
573
#define SQLITE_OPEN_WAL              0x00080000  /* VFS only */
574
#define SQLITE_OPEN_NOFOLLOW         0x01000000  /* Ok for sqlite3_open_v2() */
575
576
/* Reserved:                         0x00F00000 */
577
/* Legacy compatibility: */
578
#define SQLITE_OPEN_MASTER_JOURNAL   0x00004000  /* VFS only */
579
580
581
/*
582
** CAPI3REF: Device Characteristics
583
**
584
** The xDeviceCharacteristics method of the [sqlite3_io_methods]
585
** object returns an integer which is a vector of these
586
** bit values expressing I/O characteristics of the mass storage
587
** device that holds the file that the [sqlite3_io_methods]
588
** refers to.
589
**
590
** The SQLITE_IOCAP_ATOMIC property means that all writes of
591
** any size are atomic.  The SQLITE_IOCAP_ATOMICnnn values
592
** mean that writes of blocks that are nnn bytes in size and
593
** are aligned to an address which is an integer multiple of
594
** nnn are atomic.  The SQLITE_IOCAP_SAFE_APPEND value means
595
** that when data is appended to a file, the data is appended
596
** first then the size of the file is extended, never the other
597
** way around.  The SQLITE_IOCAP_SEQUENTIAL property means that
598
** information is written to disk in the same order as calls
599
** to xWrite().  The SQLITE_IOCAP_POWERSAFE_OVERWRITE property means that
600
** after reboot following a crash or power loss, the only bytes in a
601
** file that were written at the application level might have changed
602
** and that adjacent bytes, even bytes within the same sector are
603
** guaranteed to be unchanged.  The SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN
604
** flag indicates that a file cannot be deleted when open.  The
605
** SQLITE_IOCAP_IMMUTABLE flag indicates that the file is on
606
** read-only media and cannot be changed even by processes with
607
** elevated privileges.
608
**
609
** The SQLITE_IOCAP_BATCH_ATOMIC property means that the underlying
610
** filesystem supports doing multiple write operations atomically when those
611
** write operations are bracketed by [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] and
612
** [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE].
613
*/
614
#define SQLITE_IOCAP_ATOMIC                 0x00000001
615
#define SQLITE_IOCAP_ATOMIC512              0x00000002
616
#define SQLITE_IOCAP_ATOMIC1K               0x00000004
617
#define SQLITE_IOCAP_ATOMIC2K               0x00000008
618
#define SQLITE_IOCAP_ATOMIC4K               0x00000010
619
#define SQLITE_IOCAP_ATOMIC8K               0x00000020
620
#define SQLITE_IOCAP_ATOMIC16K              0x00000040
621
#define SQLITE_IOCAP_ATOMIC32K              0x00000080
622
#define SQLITE_IOCAP_ATOMIC64K              0x00000100
623
#define SQLITE_IOCAP_SAFE_APPEND            0x00000200
624
#define SQLITE_IOCAP_SEQUENTIAL             0x00000400
625
#define SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN  0x00000800
626
#define SQLITE_IOCAP_POWERSAFE_OVERWRITE    0x00001000
627
#define SQLITE_IOCAP_IMMUTABLE              0x00002000
628
#define SQLITE_IOCAP_BATCH_ATOMIC           0x00004000
629
630
/*
631
** CAPI3REF: File Locking Levels
632
**
633
** SQLite uses one of these integer values as the second
634
** argument to calls it makes to the xLock() and xUnlock() methods
635
** of an [sqlite3_io_methods] object.
636
*/
637
#define SQLITE_LOCK_NONE          0
638
#define SQLITE_LOCK_SHARED        1
639
#define SQLITE_LOCK_RESERVED      2
640
#define SQLITE_LOCK_PENDING       3
641
#define SQLITE_LOCK_EXCLUSIVE     4
642
643
/*
644
** CAPI3REF: Synchronization Type Flags
645
**
646
** When SQLite invokes the xSync() method of an
647
** [sqlite3_io_methods] object it uses a combination of
648
** these integer values as the second argument.
649
**
650
** When the SQLITE_SYNC_DATAONLY flag is used, it means that the
651
** sync operation only needs to flush data to mass storage.  Inode
652
** information need not be flushed. If the lower four bits of the flag
653
** equal SQLITE_SYNC_NORMAL, that means to use normal fsync() semantics.
654
** If the lower four bits equal SQLITE_SYNC_FULL, that means
655
** to use Mac OS X style fullsync instead of fsync().
656
**
657
** Do not confuse the SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags
658
** with the [PRAGMA synchronous]=NORMAL and [PRAGMA synchronous]=FULL
659
** settings.  The [synchronous pragma] determines when calls to the
660
** xSync VFS method occur and applies uniformly across all platforms.
661
** The SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags determine how
662
** energetic or rigorous or forceful the sync operations are and
663
** only make a difference on Mac OSX for the default SQLite code.
664
** (Third-party VFS implementations might also make the distinction
665
** between SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL, but among the
666
** operating systems natively supported by SQLite, only Mac OSX
667
** cares about the difference.)
668
*/
669
#define SQLITE_SYNC_NORMAL        0x00002
670
#define SQLITE_SYNC_FULL          0x00003
671
#define SQLITE_SYNC_DATAONLY      0x00010
672
673
/*
674
** CAPI3REF: OS Interface Open File Handle
675
**
676
** An [sqlite3_file] object represents an open file in the
677
** [sqlite3_vfs | OS interface layer].  Individual OS interface
678
** implementations will
679
** want to subclass this object by appending additional fields
680
** for their own use.  The pMethods entry is a pointer to an
681
** [sqlite3_io_methods] object that defines methods for performing
682
** I/O operations on the open file.
683
*/
684
typedef struct sqlite3_file sqlite3_file;
685
struct sqlite3_file {
686
  const struct sqlite3_io_methods *pMethods;  /* Methods for an open file */
687
};
688
689
/*
690
** CAPI3REF: OS Interface File Virtual Methods Object
691
**
692
** Every file opened by the [sqlite3_vfs.xOpen] method populates an
693
** [sqlite3_file] object (or, more commonly, a subclass of the
694
** [sqlite3_file] object) with a pointer to an instance of this object.
695
** This object defines the methods used to perform various operations
696
** against the open file represented by the [sqlite3_file] object.
697
**
698
** If the [sqlite3_vfs.xOpen] method sets the sqlite3_file.pMethods element
699
** to a non-NULL pointer, then the sqlite3_io_methods.xClose method
700
** may be invoked even if the [sqlite3_vfs.xOpen] reported that it failed.  The
701
** only way to prevent a call to xClose following a failed [sqlite3_vfs.xOpen]
702
** is for the [sqlite3_vfs.xOpen] to set the sqlite3_file.pMethods element
703
** to NULL.
704
**
705
** The flags argument to xSync may be one of [SQLITE_SYNC_NORMAL] or
706
** [SQLITE_SYNC_FULL].  The first choice is the normal fsync().
707
** The second choice is a Mac OS X style fullsync.  The [SQLITE_SYNC_DATAONLY]
708
** flag may be ORed in to indicate that only the data of the file
709
** and not its inode needs to be synced.
710
**
711
** The integer values to xLock() and xUnlock() are one of
712
** <ul>
713
** <li> [SQLITE_LOCK_NONE],
714
** <li> [SQLITE_LOCK_SHARED],
715
** <li> [SQLITE_LOCK_RESERVED],
716
** <li> [SQLITE_LOCK_PENDING], or
717
** <li> [SQLITE_LOCK_EXCLUSIVE].
718
** </ul>
719
** xLock() increases the lock. xUnlock() decreases the lock.
720
** The xCheckReservedLock() method checks whether any database connection,
721
** either in this process or in some other process, is holding a RESERVED,
722
** PENDING, or EXCLUSIVE lock on the file.  It returns true
723
** if such a lock exists and false otherwise.
724
**
725
** The xFileControl() method is a generic interface that allows custom
726
** VFS implementations to directly control an open file using the
727
** [sqlite3_file_control()] interface.  The second "op" argument is an
728
** integer opcode.  The third argument is a generic pointer intended to
729
** point to a structure that may contain arguments or space in which to
730
** write return values.  Potential uses for xFileControl() might be
731
** functions to enable blocking locks with timeouts, to change the
732
** locking strategy (for example to use dot-file locks), to inquire
733
** about the status of a lock, or to break stale locks.  The SQLite
734
** core reserves all opcodes less than 100 for its own use.
735
** A [file control opcodes | list of opcodes] less than 100 is available.
736
** Applications that define a custom xFileControl method should use opcodes
737
** greater than 100 to avoid conflicts.  VFS implementations should
738
** return [SQLITE_NOTFOUND] for file control opcodes that they do not
739
** recognize.
740
**
741
** The xSectorSize() method returns the sector size of the
742
** device that underlies the file.  The sector size is the
743
** minimum write that can be performed without disturbing
744
** other bytes in the file.  The xDeviceCharacteristics()
745
** method returns a bit vector describing behaviors of the
746
** underlying device:
747
**
748
** <ul>
749
** <li> [SQLITE_IOCAP_ATOMIC]
750
** <li> [SQLITE_IOCAP_ATOMIC512]
751
** <li> [SQLITE_IOCAP_ATOMIC1K]
752
** <li> [SQLITE_IOCAP_ATOMIC2K]
753
** <li> [SQLITE_IOCAP_ATOMIC4K]
754
** <li> [SQLITE_IOCAP_ATOMIC8K]
755
** <li> [SQLITE_IOCAP_ATOMIC16K]
756
** <li> [SQLITE_IOCAP_ATOMIC32K]
757
** <li> [SQLITE_IOCAP_ATOMIC64K]
758
** <li> [SQLITE_IOCAP_SAFE_APPEND]
759
** <li> [SQLITE_IOCAP_SEQUENTIAL]
760
** <li> [SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN]
761
** <li> [SQLITE_IOCAP_POWERSAFE_OVERWRITE]
762
** <li> [SQLITE_IOCAP_IMMUTABLE]
763
** <li> [SQLITE_IOCAP_BATCH_ATOMIC]
764
** </ul>
765
**
766
** The SQLITE_IOCAP_ATOMIC property means that all writes of
767
** any size are atomic.  The SQLITE_IOCAP_ATOMICnnn values
768
** mean that writes of blocks that are nnn bytes in size and
769
** are aligned to an address which is an integer multiple of
770
** nnn are atomic.  The SQLITE_IOCAP_SAFE_APPEND value means
771
** that when data is appended to a file, the data is appended
772
** first then the size of the file is extended, never the other
773
** way around.  The SQLITE_IOCAP_SEQUENTIAL property means that
774
** information is written to disk in the same order as calls
775
** to xWrite().
776
**
777
** If xRead() returns SQLITE_IOERR_SHORT_READ it must also fill
778
** in the unread portions of the buffer with zeros.  A VFS that
779
** fails to zero-fill short reads might seem to work.  However,
780
** failure to zero-fill short reads will eventually lead to
781
** database corruption.
782
*/
783
typedef struct sqlite3_io_methods sqlite3_io_methods;
784
struct sqlite3_io_methods {
785
  int iVersion;
786
  int (*xClose)(sqlite3_file*);
787
  int (*xRead)(sqlite3_file*, void*, int iAmt, sqlite3_int64 iOfst);
788
  int (*xWrite)(sqlite3_file*, const void*, int iAmt, sqlite3_int64 iOfst);
789
  int (*xTruncate)(sqlite3_file*, sqlite3_int64 size);
790
  int (*xSync)(sqlite3_file*, int flags);
791
  int (*xFileSize)(sqlite3_file*, sqlite3_int64 *pSize);
792
  int (*xLock)(sqlite3_file*, int);
793
  int (*xUnlock)(sqlite3_file*, int);
794
  int (*xCheckReservedLock)(sqlite3_file*, int *pResOut);
795
  int (*xFileControl)(sqlite3_file*, int op, void *pArg);
796
  int (*xSectorSize)(sqlite3_file*);
797
  int (*xDeviceCharacteristics)(sqlite3_file*);
798
  /* Methods above are valid for version 1 */
799
  int (*xShmMap)(sqlite3_file*, int iPg, int pgsz, int, void volatile**);
800
  int (*xShmLock)(sqlite3_file*, int offset, int n, int flags);
801
  void (*xShmBarrier)(sqlite3_file*);
802
  int (*xShmUnmap)(sqlite3_file*, int deleteFlag);
803
  /* Methods above are valid for version 2 */
804
  int (*xFetch)(sqlite3_file*, sqlite3_int64 iOfst, int iAmt, void **pp);
805
  int (*xUnfetch)(sqlite3_file*, sqlite3_int64 iOfst, void *p);
806
  /* Methods above are valid for version 3 */
807
  /* Additional methods may be added in future releases */
808
};
809
810
/*
811
** CAPI3REF: Standard File Control Opcodes
812
** KEYWORDS: {file control opcodes} {file control opcode}
813
**
814
** These integer constants are opcodes for the xFileControl method
815
** of the [sqlite3_io_methods] object and for the [sqlite3_file_control()]
816
** interface.
817
**
818
** <ul>
819
** <li>[[SQLITE_FCNTL_LOCKSTATE]]
820
** The [SQLITE_FCNTL_LOCKSTATE] opcode is used for debugging.  This
821
** opcode causes the xFileControl method to write the current state of
822
** the lock (one of [SQLITE_LOCK_NONE], [SQLITE_LOCK_SHARED],
823
** [SQLITE_LOCK_RESERVED], [SQLITE_LOCK_PENDING], or [SQLITE_LOCK_EXCLUSIVE])
824
** into an integer that the pArg argument points to. This capability
825
** is used during testing and is only available when the SQLITE_TEST
826
** compile-time option is used.
827
**
828
** <li>[[SQLITE_FCNTL_SIZE_HINT]]
829
** The [SQLITE_FCNTL_SIZE_HINT] opcode is used by SQLite to give the VFS
830
** layer a hint of how large the database file will grow to be during the
831
** current transaction.  This hint is not guaranteed to be accurate but it
832
** is often close.  The underlying VFS might choose to preallocate database
833
** file space based on this hint in order to help writes to the database
834
** file run faster.
835
**
836
** <li>[[SQLITE_FCNTL_SIZE_LIMIT]]
837
** The [SQLITE_FCNTL_SIZE_LIMIT] opcode is used by in-memory VFS that
838
** implements [sqlite3_deserialize()] to set an upper bound on the size
839
** of the in-memory database.  The argument is a pointer to a [sqlite3_int64].
840
** If the integer pointed to is negative, then it is filled in with the
841
** current limit.  Otherwise the limit is set to the larger of the value
842
** of the integer pointed to and the current database size.  The integer
843
** pointed to is set to the new limit.
844
**
845
** <li>[[SQLITE_FCNTL_CHUNK_SIZE]]
846
** The [SQLITE_FCNTL_CHUNK_SIZE] opcode is used to request that the VFS
847
** extends and truncates the database file in chunks of a size specified
848
** by the user. The fourth argument to [sqlite3_file_control()] should
849
** point to an integer (type int) containing the new chunk-size to use
850
** for the nominated database. Allocating database file space in large
851
** chunks (say 1MB at a time), may reduce file-system fragmentation and
852
** improve performance on some systems.
853
**
854
** <li>[[SQLITE_FCNTL_FILE_POINTER]]
855
** The [SQLITE_FCNTL_FILE_POINTER] opcode is used to obtain a pointer
856
** to the [sqlite3_file] object associated with a particular database
857
** connection.  See also [SQLITE_FCNTL_JOURNAL_POINTER].
858
**
859
** <li>[[SQLITE_FCNTL_JOURNAL_POINTER]]
860
** The [SQLITE_FCNTL_JOURNAL_POINTER] opcode is used to obtain a pointer
861
** to the [sqlite3_file] object associated with the journal file (either
862
** the [rollback journal] or the [write-ahead log]) for a particular database
863
** connection.  See also [SQLITE_FCNTL_FILE_POINTER].
864
**
865
** <li>[[SQLITE_FCNTL_SYNC_OMITTED]]
866
** No longer in use.
867
**
868
** <li>[[SQLITE_FCNTL_SYNC]]
869
** The [SQLITE_FCNTL_SYNC] opcode is generated internally by SQLite and
870
** sent to the VFS immediately before the xSync method is invoked on a
871
** database file descriptor. Or, if the xSync method is not invoked
872
** because the user has configured SQLite with
873
** [PRAGMA synchronous | PRAGMA synchronous=OFF] it is invoked in place
874
** of the xSync method. In most cases, the pointer argument passed with
875
** this file-control is NULL. However, if the database file is being synced
876
** as part of a multi-database commit, the argument points to a nul-terminated
877
** string containing the transactions super-journal file name. VFSes that
878
** do not need this signal should silently ignore this opcode. Applications
879
** should not call [sqlite3_file_control()] with this opcode as doing so may
880
** disrupt the operation of the specialized VFSes that do require it.
881
**
882
** <li>[[SQLITE_FCNTL_COMMIT_PHASETWO]]
883
** The [SQLITE_FCNTL_COMMIT_PHASETWO] opcode is generated internally by SQLite
884
** and sent to the VFS after a transaction has been committed immediately
885
** but before the database is unlocked. VFSes that do not need this signal
886
** should silently ignore this opcode. Applications should not call
887
** [sqlite3_file_control()] with this opcode as doing so may disrupt the
888
** operation of the specialized VFSes that do require it.
889
**
890
** <li>[[SQLITE_FCNTL_WIN32_AV_RETRY]]
891
** ^The [SQLITE_FCNTL_WIN32_AV_RETRY] opcode is used to configure automatic
892
** retry counts and intervals for certain disk I/O operations for the
893
** windows [VFS] in order to provide robustness in the presence of
894
** anti-virus programs.  By default, the windows VFS will retry file read,
895
** file write, and file delete operations up to 10 times, with a delay
896
** of 25 milliseconds before the first retry and with the delay increasing
897
** by an additional 25 milliseconds with each subsequent retry.  This
898
** opcode allows these two values (10 retries and 25 milliseconds of delay)
899
** to be adjusted.  The values are changed for all database connections
900
** within the same process.  The argument is a pointer to an array of two
901
** integers where the first integer is the new retry count and the second
902
** integer is the delay.  If either integer is negative, then the setting
903
** is not changed but instead the prior value of that setting is written
904
** into the array entry, allowing the current retry settings to be
905
** interrogated.  The zDbName parameter is ignored.
906
**
907
** <li>[[SQLITE_FCNTL_PERSIST_WAL]]
908
** ^The [SQLITE_FCNTL_PERSIST_WAL] opcode is used to set or query the
909
** persistent [WAL | Write Ahead Log] setting.  By default, the auxiliary
910
** write ahead log ([WAL file]) and shared memory
911
** files used for transaction control
912
** are automatically deleted when the latest connection to the database
913
** closes.  Setting persistent WAL mode causes those files to persist after
914
** close.  Persisting the files is useful when other processes that do not
915
** have write permission on the directory containing the database file want
916
** to read the database file, as the WAL and shared memory files must exist
917
** in order for the database to be readable.  The fourth parameter to
918
** [sqlite3_file_control()] for this opcode should be a pointer to an integer.
919
** That integer is 0 to disable persistent WAL mode or 1 to enable persistent
920
** WAL mode.  If the integer is -1, then it is overwritten with the current
921
** WAL persistence setting.
922
**
923
** <li>[[SQLITE_FCNTL_POWERSAFE_OVERWRITE]]
924
** ^The [SQLITE_FCNTL_POWERSAFE_OVERWRITE] opcode is used to set or query the
925
** persistent "powersafe-overwrite" or "PSOW" setting.  The PSOW setting
926
** determines the [SQLITE_IOCAP_POWERSAFE_OVERWRITE] bit of the
927
** xDeviceCharacteristics methods. The fourth parameter to
928
** [sqlite3_file_control()] for this opcode should be a pointer to an integer.
929
** That integer is 0 to disable zero-damage mode or 1 to enable zero-damage
930
** mode.  If the integer is -1, then it is overwritten with the current
931
** zero-damage mode setting.
932
**
933
** <li>[[SQLITE_FCNTL_OVERWRITE]]
934
** ^The [SQLITE_FCNTL_OVERWRITE] opcode is invoked by SQLite after opening
935
** a write transaction to indicate that, unless it is rolled back for some
936
** reason, the entire database file will be overwritten by the current
937
** transaction. This is used by VACUUM operations.
938
**
939
** <li>[[SQLITE_FCNTL_VFSNAME]]
940
** ^The [SQLITE_FCNTL_VFSNAME] opcode can be used to obtain the names of
941
** all [VFSes] in the VFS stack.  The names are of all VFS shims and the
942
** final bottom-level VFS are written into memory obtained from
943
** [sqlite3_malloc()] and the result is stored in the char* variable
944
** that the fourth parameter of [sqlite3_file_control()] points to.
945
** The caller is responsible for freeing the memory when done.  As with
946
** all file-control actions, there is no guarantee that this will actually
947
** do anything.  Callers should initialize the char* variable to a NULL
948
** pointer in case this file-control is not implemented.  This file-control
949
** is intended for diagnostic use only.
950
**
951
** <li>[[SQLITE_FCNTL_VFS_POINTER]]
952
** ^The [SQLITE_FCNTL_VFS_POINTER] opcode finds a pointer to the top-level
953
** [VFSes] currently in use.  ^(The argument X in
954
** sqlite3_file_control(db,SQLITE_FCNTL_VFS_POINTER,X) must be
955
** of type "[sqlite3_vfs] **".  This opcodes will set *X
956
** to a pointer to the top-level VFS.)^
957
** ^When there are multiple VFS shims in the stack, this opcode finds the
958
** upper-most shim only.
959
**
960
** <li>[[SQLITE_FCNTL_PRAGMA]]
961
** ^Whenever a [PRAGMA] statement is parsed, an [SQLITE_FCNTL_PRAGMA]
962
** file control is sent to the open [sqlite3_file] object corresponding
963
** to the database file to which the pragma statement refers. ^The argument
964
** to the [SQLITE_FCNTL_PRAGMA] file control is an array of
965
** pointers to strings (char**) in which the second element of the array
966
** is the name of the pragma and the third element is the argument to the
967
** pragma or NULL if the pragma has no argument.  ^The handler for an
968
** [SQLITE_FCNTL_PRAGMA] file control can optionally make the first element
969
** of the char** argument point to a string obtained from [sqlite3_mprintf()]
970
** or the equivalent and that string will become the result of the pragma or
971
** the error message if the pragma fails. ^If the
972
** [SQLITE_FCNTL_PRAGMA] file control returns [SQLITE_NOTFOUND], then normal
973
** [PRAGMA] processing continues.  ^If the [SQLITE_FCNTL_PRAGMA]
974
** file control returns [SQLITE_OK], then the parser assumes that the
975
** VFS has handled the PRAGMA itself and the parser generates a no-op
976
** prepared statement if result string is NULL, or that returns a copy
977
** of the result string if the string is non-NULL.
978
** ^If the [SQLITE_FCNTL_PRAGMA] file control returns
979
** any result code other than [SQLITE_OK] or [SQLITE_NOTFOUND], that means
980
** that the VFS encountered an error while handling the [PRAGMA] and the
981
** compilation of the PRAGMA fails with an error.  ^The [SQLITE_FCNTL_PRAGMA]
982
** file control occurs at the beginning of pragma statement analysis and so
983
** it is able to override built-in [PRAGMA] statements.
984
**
985
** <li>[[SQLITE_FCNTL_BUSYHANDLER]]
986
** ^The [SQLITE_FCNTL_BUSYHANDLER]
987
** file-control may be invoked by SQLite on the database file handle
988
** shortly after it is opened in order to provide a custom VFS with access
989
** to the connection's busy-handler callback. The argument is of type (void**)
990
** - an array of two (void *) values. The first (void *) actually points
991
** to a function of type (int (*)(void *)). In order to invoke the connection's
992
** busy-handler, this function should be invoked with the second (void *) in
993
** the array as the only argument. If it returns non-zero, then the operation
994
** should be retried. If it returns zero, the custom VFS should abandon the
995
** current operation.
996
**
997
** <li>[[SQLITE_FCNTL_TEMPFILENAME]]
998
** ^Applications can invoke the [SQLITE_FCNTL_TEMPFILENAME] file-control
999
** to have SQLite generate a
1000
** temporary filename using the same algorithm that is followed to generate
1001
** temporary filenames for TEMP tables and other internal uses.  The
1002
** argument should be a char** which will be filled with the filename
1003
** written into memory obtained from [sqlite3_malloc()].  The caller should
1004
** invoke [sqlite3_free()] on the result to avoid a memory leak.
1005
**
1006
** <li>[[SQLITE_FCNTL_MMAP_SIZE]]
1007
** The [SQLITE_FCNTL_MMAP_SIZE] file control is used to query or set the
1008
** maximum number of bytes that will be used for memory-mapped I/O.
1009
** The argument is a pointer to a value of type sqlite3_int64 that
1010
** is an advisory maximum number of bytes in the file to memory map.  The
1011
** pointer is overwritten with the old value.  The limit is not changed if
1012
** the value originally pointed to is negative, and so the current limit
1013
** can be queried by passing in a pointer to a negative number.  This
1014
** file-control is used internally to implement [PRAGMA mmap_size].
1015
**
1016
** <li>[[SQLITE_FCNTL_TRACE]]
1017
** The [SQLITE_FCNTL_TRACE] file control provides advisory information
1018
** to the VFS about what the higher layers of the SQLite stack are doing.
1019
** This file control is used by some VFS activity tracing [shims].
1020
** The argument is a zero-terminated string.  Higher layers in the
1021
** SQLite stack may generate instances of this file control if
1022
** the [SQLITE_USE_FCNTL_TRACE] compile-time option is enabled.
1023
**
1024
** <li>[[SQLITE_FCNTL_HAS_MOVED]]
1025
** The [SQLITE_FCNTL_HAS_MOVED] file control interprets its argument as a
1026
** pointer to an integer and it writes a boolean into that integer depending
1027
** on whether or not the file has been renamed, moved, or deleted since it
1028
** was first opened.
1029
**
1030
** <li>[[SQLITE_FCNTL_WIN32_GET_HANDLE]]
1031
** The [SQLITE_FCNTL_WIN32_GET_HANDLE] opcode can be used to obtain the
1032
** underlying native file handle associated with a file handle.  This file
1033
** control interprets its argument as a pointer to a native file handle and
1034
** writes the resulting value there.
1035
**
1036
** <li>[[SQLITE_FCNTL_WIN32_SET_HANDLE]]
1037
** The [SQLITE_FCNTL_WIN32_SET_HANDLE] opcode is used for debugging.  This
1038
** opcode causes the xFileControl method to swap the file handle with the one
1039
** pointed to by the pArg argument.  This capability is used during testing
1040
** and only needs to be supported when SQLITE_TEST is defined.
1041
**
1042
** <li>[[SQLITE_FCNTL_WAL_BLOCK]]
1043
** The [SQLITE_FCNTL_WAL_BLOCK] is a signal to the VFS layer that it might
1044
** be advantageous to block on the next WAL lock if the lock is not immediately
1045
** available.  The WAL subsystem issues this signal during rare
1046
** circumstances in order to fix a problem with priority inversion.
1047
** Applications should <em>not</em> use this file-control.
1048
**
1049
** <li>[[SQLITE_FCNTL_ZIPVFS]]
1050
** The [SQLITE_FCNTL_ZIPVFS] opcode is implemented by zipvfs only. All other
1051
** VFS should return SQLITE_NOTFOUND for this opcode.
1052
**
1053
** <li>[[SQLITE_FCNTL_RBU]]
1054
** The [SQLITE_FCNTL_RBU] opcode is implemented by the special VFS used by
1055
** the RBU extension only.  All other VFS should return SQLITE_NOTFOUND for
1056
** this opcode.
1057
**
1058
** <li>[[SQLITE_FCNTL_BEGIN_ATOMIC_WRITE]]
1059
** If the [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] opcode returns SQLITE_OK, then
1060
** the file descriptor is placed in "batch write mode", which
1061
** means all subsequent write operations will be deferred and done
1062
** atomically at the next [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE].  Systems
1063
** that do not support batch atomic writes will return SQLITE_NOTFOUND.
1064
** ^Following a successful SQLITE_FCNTL_BEGIN_ATOMIC_WRITE and prior to
1065
** the closing [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE] or
1066
** [SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE], SQLite will make
1067
** no VFS interface calls on the same [sqlite3_file] file descriptor
1068
** except for calls to the xWrite method and the xFileControl method
1069
** with [SQLITE_FCNTL_SIZE_HINT].
1070
**
1071
** <li>[[SQLITE_FCNTL_COMMIT_ATOMIC_WRITE]]
1072
** The [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE] opcode causes all write
1073
** operations since the previous successful call to
1074
** [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] to be performed atomically.
1075
** This file control returns [SQLITE_OK] if and only if the writes were
1076
** all performed successfully and have been committed to persistent storage.
1077
** ^Regardless of whether or not it is successful, this file control takes
1078
** the file descriptor out of batch write mode so that all subsequent
1079
** write operations are independent.
1080
** ^SQLite will never invoke SQLITE_FCNTL_COMMIT_ATOMIC_WRITE without
1081
** a prior successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE].
1082
**
1083
** <li>[[SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE]]
1084
** The [SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE] opcode causes all write
1085
** operations since the previous successful call to
1086
** [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] to be rolled back.
1087
** ^This file control takes the file descriptor out of batch write mode
1088
** so that all subsequent write operations are independent.
1089
** ^SQLite will never invoke SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE without
1090
** a prior successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE].
1091
**
1092
** <li>[[SQLITE_FCNTL_LOCK_TIMEOUT]]
1093
** The [SQLITE_FCNTL_LOCK_TIMEOUT] opcode is used to configure a VFS
1094
** to block for up to M milliseconds before failing when attempting to
1095
** obtain a file lock using the xLock or xShmLock methods of the VFS.
1096
** The parameter is a pointer to a 32-bit signed integer that contains
1097
** the value that M is to be set to. Before returning, the 32-bit signed
1098
** integer is overwritten with the previous value of M.
1099
**
1100
** <li>[[SQLITE_FCNTL_DATA_VERSION]]
1101
** The [SQLITE_FCNTL_DATA_VERSION] opcode is used to detect changes to
1102
** a database file.  The argument is a pointer to a 32-bit unsigned integer.
1103
** The "data version" for the pager is written into the pointer.  The
1104
** "data version" changes whenever any change occurs to the corresponding
1105
** database file, either through SQL statements on the same database
1106
** connection or through transactions committed by separate database
1107
** connections possibly in other processes. The [sqlite3_total_changes()]
1108
** interface can be used to find if any database on the connection has changed,
1109
** but that interface responds to changes on TEMP as well as MAIN and does
1110
** not provide a mechanism to detect changes to MAIN only.  Also, the
1111
** [sqlite3_total_changes()] interface responds to internal changes only and
1112
** omits changes made by other database connections.  The
1113
** [PRAGMA data_version] command provides a mechanism to detect changes to
1114
** a single attached database that occur due to other database connections,
1115
** but omits changes implemented by the database connection on which it is
1116
** called.  This file control is the only mechanism to detect changes that
1117
** happen either internally or externally and that are associated with
1118
** a particular attached database.
1119
**
1120
** <li>[[SQLITE_FCNTL_CKPT_START]]
1121
** The [SQLITE_FCNTL_CKPT_START] opcode is invoked from within a checkpoint
1122
** in wal mode before the client starts to copy pages from the wal
1123
** file to the database file.
1124
**
1125
** <li>[[SQLITE_FCNTL_CKPT_DONE]]
1126
** The [SQLITE_FCNTL_CKPT_DONE] opcode is invoked from within a checkpoint
1127
** in wal mode after the client has finished copying pages from the wal
1128
** file to the database file, but before the *-shm file is updated to
1129
** record the fact that the pages have been checkpointed.
1130
** </ul>
1131
**
1132
** <li>[[SQLITE_FCNTL_EXTERNAL_READER]]
1133
** The EXPERIMENTAL [SQLITE_FCNTL_EXTERNAL_READER] opcode is used to detect
1134
** whether or not there is a database client in another process with a wal-mode
1135
** transaction open on the database or not. It is only available on unix.The
1136
** (void*) argument passed with this file-control should be a pointer to a
1137
** value of type (int). The integer value is set to 1 if the database is a wal
1138
** mode database and there exists at least one client in another process that
1139
** currently has an SQL transaction open on the database. It is set to 0 if
1140
** the database is not a wal-mode db, or if there is no such connection in any
1141
** other process. This opcode cannot be used to detect transactions opened
1142
** by clients within the current process, only within other processes.
1143
** </ul>
1144
**
1145
** <li>[[SQLITE_FCNTL_CKSM_FILE]]
1146
** Used by the cksmvfs VFS module only.
1147
** </ul>
1148
*/
1149
#define SQLITE_FCNTL_LOCKSTATE               1
1150
#define SQLITE_FCNTL_GET_LOCKPROXYFILE       2
1151
#define SQLITE_FCNTL_SET_LOCKPROXYFILE       3
1152
#define SQLITE_FCNTL_LAST_ERRNO              4
1153
#define SQLITE_FCNTL_SIZE_HINT               5
1154
#define SQLITE_FCNTL_CHUNK_SIZE              6
1155
#define SQLITE_FCNTL_FILE_POINTER            7
1156
#define SQLITE_FCNTL_SYNC_OMITTED            8
1157
#define SQLITE_FCNTL_WIN32_AV_RETRY          9
1158
#define SQLITE_FCNTL_PERSIST_WAL            10
1159
#define SQLITE_FCNTL_OVERWRITE              11
1160
#define SQLITE_FCNTL_VFSNAME                12
1161
#define SQLITE_FCNTL_POWERSAFE_OVERWRITE    13
1162
#define SQLITE_FCNTL_PRAGMA                 14
1163
#define SQLITE_FCNTL_BUSYHANDLER            15
1164
#define SQLITE_FCNTL_TEMPFILENAME           16
1165
#define SQLITE_FCNTL_MMAP_SIZE              18
1166
#define SQLITE_FCNTL_TRACE                  19
1167
#define SQLITE_FCNTL_HAS_MOVED              20
1168
#define SQLITE_FCNTL_SYNC                   21
1169
#define SQLITE_FCNTL_COMMIT_PHASETWO        22
1170
#define SQLITE_FCNTL_WIN32_SET_HANDLE       23
1171
#define SQLITE_FCNTL_WAL_BLOCK              24
1172
#define SQLITE_FCNTL_ZIPVFS                 25
1173
#define SQLITE_FCNTL_RBU                    26
1174
#define SQLITE_FCNTL_VFS_POINTER            27
1175
#define SQLITE_FCNTL_JOURNAL_POINTER        28
1176
#define SQLITE_FCNTL_WIN32_GET_HANDLE       29
1177
#define SQLITE_FCNTL_PDB                    30
1178
#define SQLITE_FCNTL_BEGIN_ATOMIC_WRITE     31
1179
#define SQLITE_FCNTL_COMMIT_ATOMIC_WRITE    32
1180
#define SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE  33
1181
#define SQLITE_FCNTL_LOCK_TIMEOUT           34
1182
#define SQLITE_FCNTL_DATA_VERSION           35
1183
#define SQLITE_FCNTL_SIZE_LIMIT             36
1184
#define SQLITE_FCNTL_CKPT_DONE              37
1185
#define SQLITE_FCNTL_RESERVE_BYTES          38
1186
#define SQLITE_FCNTL_CKPT_START             39
1187
#define SQLITE_FCNTL_EXTERNAL_READER        40
1188
#define SQLITE_FCNTL_CKSM_FILE              41
1189
1190
/* deprecated names */
1191
#define SQLITE_GET_LOCKPROXYFILE      SQLITE_FCNTL_GET_LOCKPROXYFILE
1192
#define SQLITE_SET_LOCKPROXYFILE      SQLITE_FCNTL_SET_LOCKPROXYFILE
1193
#define SQLITE_LAST_ERRNO             SQLITE_FCNTL_LAST_ERRNO
1194
1195
1196
/*
1197
** CAPI3REF: Mutex Handle
1198
**
1199
** The mutex module within SQLite defines [sqlite3_mutex] to be an
1200
** abstract type for a mutex object.  The SQLite core never looks
1201
** at the internal representation of an [sqlite3_mutex].  It only
1202
** deals with pointers to the [sqlite3_mutex] object.
1203
**
1204
** Mutexes are created using [sqlite3_mutex_alloc()].
1205
*/
1206
typedef struct sqlite3_mutex sqlite3_mutex;
1207
1208
/*
1209
** CAPI3REF: Loadable Extension Thunk
1210
**
1211
** A pointer to the opaque sqlite3_api_routines structure is passed as
1212
** the third parameter to entry points of [loadable extensions].  This
1213
** structure must be typedefed in order to work around compiler warnings
1214
** on some platforms.
1215
*/
1216
typedef struct sqlite3_api_routines sqlite3_api_routines;
1217
1218
/*
1219
** CAPI3REF: OS Interface Object
1220
**
1221
** An instance of the sqlite3_vfs object defines the interface between
1222
** the SQLite core and the underlying operating system.  The "vfs"
1223
** in the name of the object stands for "virtual file system".  See
1224
** the [VFS | VFS documentation] for further information.
1225
**
1226
** The VFS interface is sometimes extended by adding new methods onto
1227
** the end.  Each time such an extension occurs, the iVersion field
1228
** is incremented.  The iVersion value started out as 1 in
1229
** SQLite [version 3.5.0] on [dateof:3.5.0], then increased to 2
1230
** with SQLite [version 3.7.0] on [dateof:3.7.0], and then increased
1231
** to 3 with SQLite [version 3.7.6] on [dateof:3.7.6].  Additional fields
1232
** may be appended to the sqlite3_vfs object and the iVersion value
1233
** may increase again in future versions of SQLite.
1234
** Note that due to an oversight, the structure
1235
** of the sqlite3_vfs object changed in the transition from
1236
** SQLite [version 3.5.9] to [version 3.6.0] on [dateof:3.6.0]
1237
** and yet the iVersion field was not increased.
1238
**
1239
** The szOsFile field is the size of the subclassed [sqlite3_file]
1240
** structure used by this VFS.  mxPathname is the maximum length of
1241
** a pathname in this VFS.
1242
**
1243
** Registered sqlite3_vfs objects are kept on a linked list formed by
1244
** the pNext pointer.  The [sqlite3_vfs_register()]
1245
** and [sqlite3_vfs_unregister()] interfaces manage this list
1246
** in a thread-safe way.  The [sqlite3_vfs_find()] interface
1247
** searches the list.  Neither the application code nor the VFS
1248
** implementation should use the pNext pointer.
1249
**
1250
** The pNext field is the only field in the sqlite3_vfs
1251
** structure that SQLite will ever modify.  SQLite will only access
1252
** or modify this field while holding a particular static mutex.
1253
** The application should never modify anything within the sqlite3_vfs
1254
** object once the object has been registered.
1255
**
1256
** The zName field holds the name of the VFS module.  The name must
1257
** be unique across all VFS modules.
1258
**
1259
** [[sqlite3_vfs.xOpen]]
1260
** ^SQLite guarantees that the zFilename parameter to xOpen
1261
** is either a NULL pointer or string obtained
1262
** from xFullPathname() with an optional suffix added.
1263
** ^If a suffix is added to the zFilename parameter, it will
1264
** consist of a single "-" character followed by no more than
1265
** 11 alphanumeric and/or "-" characters.
1266
** ^SQLite further guarantees that
1267
** the string will be valid and unchanged until xClose() is
1268
** called. Because of the previous sentence,
1269
** the [sqlite3_file] can safely store a pointer to the
1270
** filename if it needs to remember the filename for some reason.
1271
** If the zFilename parameter to xOpen is a NULL pointer then xOpen
1272
** must invent its own temporary name for the file.  ^Whenever the
1273
** xFilename parameter is NULL it will also be the case that the
1274
** flags parameter will include [SQLITE_OPEN_DELETEONCLOSE].
1275
**
1276
** The flags argument to xOpen() includes all bits set in
1277
** the flags argument to [sqlite3_open_v2()].  Or if [sqlite3_open()]
1278
** or [sqlite3_open16()] is used, then flags includes at least
1279
** [SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE].
1280
** If xOpen() opens a file read-only then it sets *pOutFlags to
1281
** include [SQLITE_OPEN_READONLY].  Other bits in *pOutFlags may be set.
1282
**
1283
** ^(SQLite will also add one of the following flags to the xOpen()
1284
** call, depending on the object being opened:
1285
**
1286
** <ul>
1287
** <li>  [SQLITE_OPEN_MAIN_DB]
1288
** <li>  [SQLITE_OPEN_MAIN_JOURNAL]
1289
** <li>  [SQLITE_OPEN_TEMP_DB]
1290
** <li>  [SQLITE_OPEN_TEMP_JOURNAL]
1291
** <li>  [SQLITE_OPEN_TRANSIENT_DB]
1292
** <li>  [SQLITE_OPEN_SUBJOURNAL]
1293
** <li>  [SQLITE_OPEN_SUPER_JOURNAL]
1294
** <li>  [SQLITE_OPEN_WAL]
1295
** </ul>)^
1296
**
1297
** The file I/O implementation can use the object type flags to
1298
** change the way it deals with files.  For example, an application
1299
** that does not care about crash recovery or rollback might make
1300
** the open of a journal file a no-op.  Writes to this journal would
1301
** also be no-ops, and any attempt to read the journal would return
1302
** SQLITE_IOERR.  Or the implementation might recognize that a database
1303
** file will be doing page-aligned sector reads and writes in a random
1304
** order and set up its I/O subsystem accordingly.
1305
**
1306
** SQLite might also add one of the following flags to the xOpen method:
1307
**
1308
** <ul>
1309
** <li> [SQLITE_OPEN_DELETEONCLOSE]
1310
** <li> [SQLITE_OPEN_EXCLUSIVE]
1311
** </ul>
1312
**
1313
** The [SQLITE_OPEN_DELETEONCLOSE] flag means the file should be
1314
** deleted when it is closed.  ^The [SQLITE_OPEN_DELETEONCLOSE]
1315
** will be set for TEMP databases and their journals, transient
1316
** databases, and subjournals.
1317
**
1318
** ^The [SQLITE_OPEN_EXCLUSIVE] flag is always used in conjunction
1319
** with the [SQLITE_OPEN_CREATE] flag, which are both directly
1320
** analogous to the O_EXCL and O_CREAT flags of the POSIX open()
1321
** API.  The SQLITE_OPEN_EXCLUSIVE flag, when paired with the
1322
** SQLITE_OPEN_CREATE, is used to indicate that file should always
1323
** be created, and that it is an error if it already exists.
1324
** It is <i>not</i> used to indicate the file should be opened
1325
** for exclusive access.
1326
**
1327
** ^At least szOsFile bytes of memory are allocated by SQLite
1328
** to hold the [sqlite3_file] structure passed as the third
1329
** argument to xOpen.  The xOpen method does not have to
1330
** allocate the structure; it should just fill it in.  Note that
1331
** the xOpen method must set the sqlite3_file.pMethods to either
1332
** a valid [sqlite3_io_methods] object or to NULL.  xOpen must do
1333
** this even if the open fails.  SQLite expects that the sqlite3_file.pMethods
1334
** element will be valid after xOpen returns regardless of the success
1335
** or failure of the xOpen call.
1336
**
1337
** [[sqlite3_vfs.xAccess]]
1338
** ^The flags argument to xAccess() may be [SQLITE_ACCESS_EXISTS]
1339
** to test for the existence of a file, or [SQLITE_ACCESS_READWRITE] to
1340
** test whether a file is readable and writable, or [SQLITE_ACCESS_READ]
1341
** to test whether a file is at least readable.  The SQLITE_ACCESS_READ
1342
** flag is never actually used and is not implemented in the built-in
1343
** VFSes of SQLite.  The file is named by the second argument and can be a
1344
** directory. The xAccess method returns [SQLITE_OK] on success or some
1345
** non-zero error code if there is an I/O error or if the name of
1346
** the file given in the second argument is illegal.  If SQLITE_OK
1347
** is returned, then non-zero or zero is written into *pResOut to indicate
1348
** whether or not the file is accessible.
1349
**
1350
** ^SQLite will always allocate at least mxPathname+1 bytes for the
1351
** output buffer xFullPathname.  The exact size of the output buffer
1352
** is also passed as a parameter to both  methods. If the output buffer
1353
** is not large enough, [SQLITE_CANTOPEN] should be returned. Since this is
1354
** handled as a fatal error by SQLite, vfs implementations should endeavor
1355
** to prevent this by setting mxPathname to a sufficiently large value.
1356
**
1357
** The xRandomness(), xSleep(), xCurrentTime(), and xCurrentTimeInt64()
1358
** interfaces are not strictly a part of the filesystem, but they are
1359
** included in the VFS structure for completeness.
1360
** The xRandomness() function attempts to return nBytes bytes
1361
** of good-quality randomness into zOut.  The return value is
1362
** the actual number of bytes of randomness obtained.
1363
** The xSleep() method causes the calling thread to sleep for at
1364
** least the number of microseconds given.  ^The xCurrentTime()
1365
** method returns a Julian Day Number for the current date and time as
1366
** a floating point value.
1367
** ^The xCurrentTimeInt64() method returns, as an integer, the Julian
1368
** Day Number multiplied by 86400000 (the number of milliseconds in
1369
** a 24-hour day).
1370
** ^SQLite will use the xCurrentTimeInt64() method to get the current
1371
** date and time if that method is available (if iVersion is 2 or
1372
** greater and the function pointer is not NULL) and will fall back
1373
** to xCurrentTime() if xCurrentTimeInt64() is unavailable.
1374
**
1375
** ^The xSetSystemCall(), xGetSystemCall(), and xNestSystemCall() interfaces
1376
** are not used by the SQLite core.  These optional interfaces are provided
1377
** by some VFSes to facilitate testing of the VFS code. By overriding
1378
** system calls with functions under its control, a test program can
1379
** simulate faults and error conditions that would otherwise be difficult
1380
** or impossible to induce.  The set of system calls that can be overridden
1381
** varies from one VFS to another, and from one version of the same VFS to the
1382
** next.  Applications that use these interfaces must be prepared for any
1383
** or all of these interfaces to be NULL or for their behavior to change
1384
** from one release to the next.  Applications must not attempt to access
1385
** any of these methods if the iVersion of the VFS is less than 3.
1386
*/
1387
typedef struct sqlite3_vfs sqlite3_vfs;
1388
typedef void (*sqlite3_syscall_ptr)(void);
1389
struct sqlite3_vfs {
1390
  int iVersion;            /* Structure version number (currently 3) */
1391
  int szOsFile;            /* Size of subclassed sqlite3_file */
1392
  int mxPathname;          /* Maximum file pathname length */
1393
  sqlite3_vfs *pNext;      /* Next registered VFS */
1394
  const char *zName;       /* Name of this virtual file system */
1395
  void *pAppData;          /* Pointer to application-specific data */
1396
  int (*xOpen)(sqlite3_vfs*, const char *zName, sqlite3_file*,
1397
               int flags, int *pOutFlags);
1398
  int (*xDelete)(sqlite3_vfs*, const char *zName, int syncDir);
1399
  int (*xAccess)(sqlite3_vfs*, const char *zName, int flags, int *pResOut);
1400
  int (*xFullPathname)(sqlite3_vfs*, const char *zName, int nOut, char *zOut);
1401
  void *(*xDlOpen)(sqlite3_vfs*, const char *zFilename);
1402
  void (*xDlError)(sqlite3_vfs*, int nByte, char *zErrMsg);
1403
  void (*(*xDlSym)(sqlite3_vfs*,void*, const char *zSymbol))(void);
1404
  void (*xDlClose)(sqlite3_vfs*, void*);
1405
  int (*xRandomness)(sqlite3_vfs*, int nByte, char *zOut);
1406
  int (*xSleep)(sqlite3_vfs*, int microseconds);
1407
  int (*xCurrentTime)(sqlite3_vfs*, double*);
1408
  int (*xGetLastError)(sqlite3_vfs*, int, char *);
1409
  /*
1410
  ** The methods above are in version 1 of the sqlite_vfs object
1411
  ** definition.  Those that follow are added in version 2 or later
1412
  */
1413
  int (*xCurrentTimeInt64)(sqlite3_vfs*, sqlite3_int64*);
1414
  /*
1415
  ** The methods above are in versions 1 and 2 of the sqlite_vfs object.
1416
  ** Those below are for version 3 and greater.
1417
  */
1418
  int (*xSetSystemCall)(sqlite3_vfs*, const char *zName, sqlite3_syscall_ptr);
1419
  sqlite3_syscall_ptr (*xGetSystemCall)(sqlite3_vfs*, const char *zName);
1420
  const char *(*xNextSystemCall)(sqlite3_vfs*, const char *zName);
1421
  /*
1422
  ** The methods above are in versions 1 through 3 of the sqlite_vfs object.
1423
  ** New fields may be appended in future versions.  The iVersion
1424
  ** value will increment whenever this happens.
1425
  */
1426
};
1427
1428
/*
1429
** CAPI3REF: Flags for the xAccess VFS method
1430
**
1431
** These integer constants can be used as the third parameter to
1432
** the xAccess method of an [sqlite3_vfs] object.  They determine
1433
** what kind of permissions the xAccess method is looking for.
1434
** With SQLITE_ACCESS_EXISTS, the xAccess method
1435
** simply checks whether the file exists.
1436
** With SQLITE_ACCESS_READWRITE, the xAccess method
1437
** checks whether the named directory is both readable and writable
1438
** (in other words, if files can be added, removed, and renamed within
1439
** the directory).
1440
** The SQLITE_ACCESS_READWRITE constant is currently used only by the
1441
** [temp_store_directory pragma], though this could change in a future
1442
** release of SQLite.
1443
** With SQLITE_ACCESS_READ, the xAccess method
1444
** checks whether the file is readable.  The SQLITE_ACCESS_READ constant is
1445
** currently unused, though it might be used in a future release of
1446
** SQLite.
1447
*/
1448
#define SQLITE_ACCESS_EXISTS    0
1449
#define SQLITE_ACCESS_READWRITE 1   /* Used by PRAGMA temp_store_directory */
1450
#define SQLITE_ACCESS_READ      2   /* Unused */
1451
1452
/*
1453
** CAPI3REF: Flags for the xShmLock VFS method
1454
**
1455
** These integer constants define the various locking operations
1456
** allowed by the xShmLock method of [sqlite3_io_methods].  The
1457
** following are the only legal combinations of flags to the
1458
** xShmLock method:
1459
**
1460
** <ul>
1461
** <li>  SQLITE_SHM_LOCK | SQLITE_SHM_SHARED
1462
** <li>  SQLITE_SHM_LOCK | SQLITE_SHM_EXCLUSIVE
1463
** <li>  SQLITE_SHM_UNLOCK | SQLITE_SHM_SHARED
1464
** <li>  SQLITE_SHM_UNLOCK | SQLITE_SHM_EXCLUSIVE
1465
** </ul>
1466
**
1467
** When unlocking, the same SHARED or EXCLUSIVE flag must be supplied as
1468
** was given on the corresponding lock.
1469
**
1470
** The xShmLock method can transition between unlocked and SHARED or
1471
** between unlocked and EXCLUSIVE.  It cannot transition between SHARED
1472
** and EXCLUSIVE.
1473
*/
1474
#define SQLITE_SHM_UNLOCK       1
1475
#define SQLITE_SHM_LOCK         2
1476
#define SQLITE_SHM_SHARED       4
1477
#define SQLITE_SHM_EXCLUSIVE    8
1478
1479
/*
1480
** CAPI3REF: Maximum xShmLock index
1481
**
1482
** The xShmLock method on [sqlite3_io_methods] may use values
1483
** between 0 and this upper bound as its "offset" argument.
1484
** The SQLite core will never attempt to acquire or release a
1485
** lock outside of this range
1486
*/
1487
#define SQLITE_SHM_NLOCK        8
1488
1489
1490
/*
1491
** CAPI3REF: Initialize The SQLite Library
1492
**
1493
** ^The sqlite3_initialize() routine initializes the
1494
** SQLite library.  ^The sqlite3_shutdown() routine
1495
** deallocates any resources that were allocated by sqlite3_initialize().
1496
** These routines are designed to aid in process initialization and
1497
** shutdown on embedded systems.  Workstation applications using
1498
** SQLite normally do not need to invoke either of these routines.
1499
**
1500
** A call to sqlite3_initialize() is an "effective" call if it is
1501
** the first time sqlite3_initialize() is invoked during the lifetime of
1502
** the process, or if it is the first time sqlite3_initialize() is invoked
1503
** following a call to sqlite3_shutdown().  ^(Only an effective call
1504
** of sqlite3_initialize() does any initialization.  All other calls
1505
** are harmless no-ops.)^
1506
**
1507
** A call to sqlite3_shutdown() is an "effective" call if it is the first
1508
** call to sqlite3_shutdown() since the last sqlite3_initialize().  ^(Only
1509
** an effective call to sqlite3_shutdown() does any deinitialization.
1510
** All other valid calls to sqlite3_shutdown() are harmless no-ops.)^
1511
**
1512
** The sqlite3_initialize() interface is threadsafe, but sqlite3_shutdown()
1513
** is not.  The sqlite3_shutdown() interface must only be called from a
1514
** single thread.  All open [database connections] must be closed and all
1515
** other SQLite resources must be deallocated prior to invoking
1516
** sqlite3_shutdown().
1517
**
1518
** Among other things, ^sqlite3_initialize() will invoke
1519
** sqlite3_os_init().  Similarly, ^sqlite3_shutdown()
1520
** will invoke sqlite3_os_end().
1521
**
1522
** ^The sqlite3_initialize() routine returns [SQLITE_OK] on success.
1523
** ^If for some reason, sqlite3_initialize() is unable to initialize
1524
** the library (perhaps it is unable to allocate a needed resource such
1525
** as a mutex) it returns an [error code] other than [SQLITE_OK].
1526
**
1527
** ^The sqlite3_initialize() routine is called internally by many other
1528
** SQLite interfaces so that an application usually does not need to
1529
** invoke sqlite3_initialize() directly.  For example, [sqlite3_open()]
1530
** calls sqlite3_initialize() so the SQLite library will be automatically
1531
** initialized when [sqlite3_open()] is called if it has not be initialized
1532
** already.  ^However, if SQLite is compiled with the [SQLITE_OMIT_AUTOINIT]
1533
** compile-time option, then the automatic calls to sqlite3_initialize()
1534
** are omitted and the application must call sqlite3_initialize() directly
1535
** prior to using any other SQLite interface.  For maximum portability,
1536
** it is recommended that applications always invoke sqlite3_initialize()
1537
** directly prior to using any other SQLite interface.  Future releases
1538
** of SQLite may require this.  In other words, the behavior exhibited
1539
** when SQLite is compiled with [SQLITE_OMIT_AUTOINIT] might become the
1540
** default behavior in some future release of SQLite.
1541
**
1542
** The sqlite3_os_init() routine does operating-system specific
1543
** initialization of the SQLite library.  The sqlite3_os_end()
1544
** routine undoes the effect of sqlite3_os_init().  Typical tasks
1545
** performed by these routines include allocation or deallocation
1546
** of static resources, initialization of global variables,
1547
** setting up a default [sqlite3_vfs] module, or setting up
1548
** a default configuration using [sqlite3_config()].
1549
**
1550
** The application should never invoke either sqlite3_os_init()
1551
** or sqlite3_os_end() directly.  The application should only invoke
1552
** sqlite3_initialize() and sqlite3_shutdown().  The sqlite3_os_init()
1553
** interface is called automatically by sqlite3_initialize() and
1554
** sqlite3_os_end() is called by sqlite3_shutdown().  Appropriate
1555
** implementations for sqlite3_os_init() and sqlite3_os_end()
1556
** are built into SQLite when it is compiled for Unix, Windows, or OS/2.
1557
** When [custom builds | built for other platforms]
1558
** (using the [SQLITE_OS_OTHER=1] compile-time
1559
** option) the application must supply a suitable implementation for
1560
** sqlite3_os_init() and sqlite3_os_end().  An application-supplied
1561
** implementation of sqlite3_os_init() or sqlite3_os_end()
1562
** must return [SQLITE_OK] on success and some other [error code] upon
1563
** failure.
1564
*/
1565
SQLITE_API int sqlite3_initialize(void);
1566
SQLITE_API int sqlite3_shutdown(void);
1567
SQLITE_API int sqlite3_os_init(void);
1568
SQLITE_API int sqlite3_os_end(void);
1569
1570
/*
1571
** CAPI3REF: Configuring The SQLite Library
1572
**
1573
** The sqlite3_config() interface is used to make global configuration
1574
** changes to SQLite in order to tune SQLite to the specific needs of
1575
** the application.  The default configuration is recommended for most
1576
** applications and so this routine is usually not necessary.  It is
1577
** provided to support rare applications with unusual needs.
1578
**
1579
** <b>The sqlite3_config() interface is not threadsafe. The application
1580
** must ensure that no other SQLite interfaces are invoked by other
1581
** threads while sqlite3_config() is running.</b>
1582
**
1583
** The sqlite3_config() interface
1584
** may only be invoked prior to library initialization using
1585
** [sqlite3_initialize()] or after shutdown by [sqlite3_shutdown()].
1586
** ^If sqlite3_config() is called after [sqlite3_initialize()] and before
1587
** [sqlite3_shutdown()] then it will return SQLITE_MISUSE.
1588
** Note, however, that ^sqlite3_config() can be called as part of the
1589
** implementation of an application-defined [sqlite3_os_init()].
1590
**
1591
** The first argument to sqlite3_config() is an integer
1592
** [configuration option] that determines
1593
** what property of SQLite is to be configured.  Subsequent arguments
1594
** vary depending on the [configuration option]
1595
** in the first argument.
1596
**
1597
** ^When a configuration option is set, sqlite3_config() returns [SQLITE_OK].
1598
** ^If the option is unknown or SQLite is unable to set the option
1599
** then this routine returns a non-zero [error code].
1600
*/
1601
SQLITE_API int sqlite3_config(int, ...);
1602
1603
/*
1604
** CAPI3REF: Configure database connections
1605
** METHOD: sqlite3
1606
**
1607
** The sqlite3_db_config() interface is used to make configuration
1608
** changes to a [database connection].  The interface is similar to
1609
** [sqlite3_config()] except that the changes apply to a single
1610
** [database connection] (specified in the first argument).
1611
**
1612
** The second argument to sqlite3_db_config(D,V,...)  is the
1613
** [SQLITE_DBCONFIG_LOOKASIDE | configuration verb] - an integer code
1614
** that indicates what aspect of the [database connection] is being configured.
1615
** Subsequent arguments vary depending on the configuration verb.
1616
**
1617
** ^Calls to sqlite3_db_config() return SQLITE_OK if and only if
1618
** the call is considered successful.
1619
*/
1620
SQLITE_API int sqlite3_db_config(sqlite3*, int op, ...);
1621
1622
/*
1623
** CAPI3REF: Memory Allocation Routines
1624
**
1625
** An instance of this object defines the interface between SQLite
1626
** and low-level memory allocation routines.
1627
**
1628
** This object is used in only one place in the SQLite interface.
1629
** A pointer to an instance of this object is the argument to
1630
** [sqlite3_config()] when the configuration option is
1631
** [SQLITE_CONFIG_MALLOC] or [SQLITE_CONFIG_GETMALLOC].
1632
** By creating an instance of this object
1633
** and passing it to [sqlite3_config]([SQLITE_CONFIG_MALLOC])
1634
** during configuration, an application can specify an alternative
1635
** memory allocation subsystem for SQLite to use for all of its
1636
** dynamic memory needs.
1637
**
1638
** Note that SQLite comes with several [built-in memory allocators]
1639
** that are perfectly adequate for the overwhelming majority of applications
1640
** and that this object is only useful to a tiny minority of applications
1641
** with specialized memory allocation requirements.  This object is
1642
** also used during testing of SQLite in order to specify an alternative
1643
** memory allocator that simulates memory out-of-memory conditions in
1644
** order to verify that SQLite recovers gracefully from such
1645
** conditions.
1646
**
1647
** The xMalloc, xRealloc, and xFree methods must work like the
1648
** malloc(), realloc() and free() functions from the standard C library.
1649
** ^SQLite guarantees that the second argument to
1650
** xRealloc is always a value returned by a prior call to xRoundup.
1651
**
1652
** xSize should return the allocated size of a memory allocation
1653
** previously obtained from xMalloc or xRealloc.  The allocated size
1654
** is always at least as big as the requested size but may be larger.
1655
**
1656
** The xRoundup method returns what would be the allocated size of
1657
** a memory allocation given a particular requested size.  Most memory
1658
** allocators round up memory allocations at least to the next multiple
1659
** of 8.  Some allocators round up to a larger multiple or to a power of 2.
1660
** Every memory allocation request coming in through [sqlite3_malloc()]
1661
** or [sqlite3_realloc()] first calls xRoundup.  If xRoundup returns 0,
1662
** that causes the corresponding memory allocation to fail.
1663
**
1664
** The xInit method initializes the memory allocator.  For example,
1665
** it might allocate any required mutexes or initialize internal data
1666
** structures.  The xShutdown method is invoked (indirectly) by
1667
** [sqlite3_shutdown()] and should deallocate any resources acquired
1668
** by xInit.  The pAppData pointer is used as the only parameter to
1669
** xInit and xShutdown.
1670
**
1671
** SQLite holds the [SQLITE_MUTEX_STATIC_MAIN] mutex when it invokes
1672
** the xInit method, so the xInit method need not be threadsafe.  The
1673
** xShutdown method is only called from [sqlite3_shutdown()] so it does
1674
** not need to be threadsafe either.  For all other methods, SQLite
1675
** holds the [SQLITE_MUTEX_STATIC_MEM] mutex as long as the
1676
** [SQLITE_CONFIG_MEMSTATUS] configuration option is turned on (which
1677
** it is by default) and so the methods are automatically serialized.
1678
** However, if [SQLITE_CONFIG_MEMSTATUS] is disabled, then the other
1679
** methods must be threadsafe or else make their own arrangements for
1680
** serialization.
1681
**
1682
** SQLite will never invoke xInit() more than once without an intervening
1683
** call to xShutdown().
1684
*/
1685
typedef struct sqlite3_mem_methods sqlite3_mem_methods;
1686
struct sqlite3_mem_methods {
1687
  void *(*xMalloc)(int);         /* Memory allocation function */
1688
  void (*xFree)(void*);          /* Free a prior allocation */
1689
  void *(*xRealloc)(void*,int);  /* Resize an allocation */
1690
  int (*xSize)(void*);           /* Return the size of an allocation */
1691
  int (*xRoundup)(int);          /* Round up request size to allocation size */
1692
  int (*xInit)(void*);           /* Initialize the memory allocator */
1693
  void (*xShutdown)(void*);      /* Deinitialize the memory allocator */
1694
  void *pAppData;                /* Argument to xInit() and xShutdown() */
1695
};
1696
1697
/*
1698
** CAPI3REF: Configuration Options
1699
** KEYWORDS: {configuration option}
1700
**
1701
** These constants are the available integer configuration options that
1702
** can be passed as the first argument to the [sqlite3_config()] interface.
1703
**
1704
** New configuration options may be added in future releases of SQLite.
1705
** Existing configuration options might be discontinued.  Applications
1706
** should check the return code from [sqlite3_config()] to make sure that
1707
** the call worked.  The [sqlite3_config()] interface will return a
1708
** non-zero [error code] if a discontinued or unsupported configuration option
1709
** is invoked.
1710
**
1711
** <dl>
1712
** [[SQLITE_CONFIG_SINGLETHREAD]] <dt>SQLITE_CONFIG_SINGLETHREAD</dt>
1713
** <dd>There are no arguments to this option.  ^This option sets the
1714
** [threading mode] to Single-thread.  In other words, it disables
1715
** all mutexing and puts SQLite into a mode where it can only be used
1716
** by a single thread.   ^If SQLite is compiled with
1717
** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1718
** it is not possible to change the [threading mode] from its default
1719
** value of Single-thread and so [sqlite3_config()] will return
1720
** [SQLITE_ERROR] if called with the SQLITE_CONFIG_SINGLETHREAD
1721
** configuration option.</dd>
1722
**
1723
** [[SQLITE_CONFIG_MULTITHREAD]] <dt>SQLITE_CONFIG_MULTITHREAD</dt>
1724
** <dd>There are no arguments to this option.  ^This option sets the
1725
** [threading mode] to Multi-thread.  In other words, it disables
1726
** mutexing on [database connection] and [prepared statement] objects.
1727
** The application is responsible for serializing access to
1728
** [database connections] and [prepared statements].  But other mutexes
1729
** are enabled so that SQLite will be safe to use in a multi-threaded
1730
** environment as long as no two threads attempt to use the same
1731
** [database connection] at the same time.  ^If SQLite is compiled with
1732
** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1733
** it is not possible to set the Multi-thread [threading mode] and
1734
** [sqlite3_config()] will return [SQLITE_ERROR] if called with the
1735
** SQLITE_CONFIG_MULTITHREAD configuration option.</dd>
1736
**
1737
** [[SQLITE_CONFIG_SERIALIZED]] <dt>SQLITE_CONFIG_SERIALIZED</dt>
1738
** <dd>There are no arguments to this option.  ^This option sets the
1739
** [threading mode] to Serialized. In other words, this option enables
1740
** all mutexes including the recursive
1741
** mutexes on [database connection] and [prepared statement] objects.
1742
** In this mode (which is the default when SQLite is compiled with
1743
** [SQLITE_THREADSAFE=1]) the SQLite library will itself serialize access
1744
** to [database connections] and [prepared statements] so that the
1745
** application is free to use the same [database connection] or the
1746
** same [prepared statement] in different threads at the same time.
1747
** ^If SQLite is compiled with
1748
** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1749
** it is not possible to set the Serialized [threading mode] and
1750
** [sqlite3_config()] will return [SQLITE_ERROR] if called with the
1751
** SQLITE_CONFIG_SERIALIZED configuration option.</dd>
1752
**
1753
** [[SQLITE_CONFIG_MALLOC]] <dt>SQLITE_CONFIG_MALLOC</dt>
1754
** <dd> ^(The SQLITE_CONFIG_MALLOC option takes a single argument which is
1755
** a pointer to an instance of the [sqlite3_mem_methods] structure.
1756
** The argument specifies
1757
** alternative low-level memory allocation routines to be used in place of
1758
** the memory allocation routines built into SQLite.)^ ^SQLite makes
1759
** its own private copy of the content of the [sqlite3_mem_methods] structure
1760
** before the [sqlite3_config()] call returns.</dd>
1761
**
1762
** [[SQLITE_CONFIG_GETMALLOC]] <dt>SQLITE_CONFIG_GETMALLOC</dt>
1763
** <dd> ^(The SQLITE_CONFIG_GETMALLOC option takes a single argument which
1764
** is a pointer to an instance of the [sqlite3_mem_methods] structure.
1765
** The [sqlite3_mem_methods]
1766
** structure is filled with the currently defined memory allocation routines.)^
1767
** This option can be used to overload the default memory allocation
1768
** routines with a wrapper that simulations memory allocation failure or
1769
** tracks memory usage, for example. </dd>
1770
**
1771
** [[SQLITE_CONFIG_SMALL_MALLOC]] <dt>SQLITE_CONFIG_SMALL_MALLOC</dt>
1772
** <dd> ^The SQLITE_CONFIG_SMALL_MALLOC option takes single argument of
1773
** type int, interpreted as a boolean, which if true provides a hint to
1774
** SQLite that it should avoid large memory allocations if possible.
1775
** SQLite will run faster if it is free to make large memory allocations,
1776
** but some application might prefer to run slower in exchange for
1777
** guarantees about memory fragmentation that are possible if large
1778
** allocations are avoided.  This hint is normally off.
1779
** </dd>
1780
**
1781
** [[SQLITE_CONFIG_MEMSTATUS]] <dt>SQLITE_CONFIG_MEMSTATUS</dt>
1782
** <dd> ^The SQLITE_CONFIG_MEMSTATUS option takes single argument of type int,
1783
** interpreted as a boolean, which enables or disables the collection of
1784
** memory allocation statistics. ^(When memory allocation statistics are
1785
** disabled, the following SQLite interfaces become non-operational:
1786
**   <ul>
1787
**   <li> [sqlite3_hard_heap_limit64()]
1788
**   <li> [sqlite3_memory_used()]
1789
**   <li> [sqlite3_memory_highwater()]
1790
**   <li> [sqlite3_soft_heap_limit64()]
1791
**   <li> [sqlite3_status64()]
1792
**   </ul>)^
1793
** ^Memory allocation statistics are enabled by default unless SQLite is
1794
** compiled with [SQLITE_DEFAULT_MEMSTATUS]=0 in which case memory
1795
** allocation statistics are disabled by default.
1796
** </dd>
1797
**
1798
** [[SQLITE_CONFIG_SCRATCH]] <dt>SQLITE_CONFIG_SCRATCH</dt>
1799
** <dd> The SQLITE_CONFIG_SCRATCH option is no longer used.
1800
** </dd>
1801
**
1802
** [[SQLITE_CONFIG_PAGECACHE]] <dt>SQLITE_CONFIG_PAGECACHE</dt>
1803
** <dd> ^The SQLITE_CONFIG_PAGECACHE option specifies a memory pool
1804
** that SQLite can use for the database page cache with the default page
1805
** cache implementation.
1806
** This configuration option is a no-op if an application-defined page
1807
** cache implementation is loaded using the [SQLITE_CONFIG_PCACHE2].
1808
** ^There are three arguments to SQLITE_CONFIG_PAGECACHE: A pointer to
1809
** 8-byte aligned memory (pMem), the size of each page cache line (sz),
1810
** and the number of cache lines (N).
1811
** The sz argument should be the size of the largest database page
1812
** (a power of two between 512 and 65536) plus some extra bytes for each
1813
** page header.  ^The number of extra bytes needed by the page header
1814
** can be determined using [SQLITE_CONFIG_PCACHE_HDRSZ].
1815
** ^It is harmless, apart from the wasted memory,
1816
** for the sz parameter to be larger than necessary.  The pMem
1817
** argument must be either a NULL pointer or a pointer to an 8-byte
1818
** aligned block of memory of at least sz*N bytes, otherwise
1819
** subsequent behavior is undefined.
1820
** ^When pMem is not NULL, SQLite will strive to use the memory provided
1821
** to satisfy page cache needs, falling back to [sqlite3_malloc()] if
1822
** a page cache line is larger than sz bytes or if all of the pMem buffer
1823
** is exhausted.
1824
** ^If pMem is NULL and N is non-zero, then each database connection
1825
** does an initial bulk allocation for page cache memory
1826
** from [sqlite3_malloc()] sufficient for N cache lines if N is positive or
1827
** of -1024*N bytes if N is negative, . ^If additional
1828
** page cache memory is needed beyond what is provided by the initial
1829
** allocation, then SQLite goes to [sqlite3_malloc()] separately for each
1830
** additional cache line. </dd>
1831
**
1832
** [[SQLITE_CONFIG_HEAP]] <dt>SQLITE_CONFIG_HEAP</dt>
1833
** <dd> ^The SQLITE_CONFIG_HEAP option specifies a static memory buffer
1834
** that SQLite will use for all of its dynamic memory allocation needs
1835
** beyond those provided for by [SQLITE_CONFIG_PAGECACHE].
1836
** ^The SQLITE_CONFIG_HEAP option is only available if SQLite is compiled
1837
** with either [SQLITE_ENABLE_MEMSYS3] or [SQLITE_ENABLE_MEMSYS5] and returns
1838
** [SQLITE_ERROR] if invoked otherwise.
1839
** ^There are three arguments to SQLITE_CONFIG_HEAP:
1840
** An 8-byte aligned pointer to the memory,
1841
** the number of bytes in the memory buffer, and the minimum allocation size.
1842
** ^If the first pointer (the memory pointer) is NULL, then SQLite reverts
1843
** to using its default memory allocator (the system malloc() implementation),
1844
** undoing any prior invocation of [SQLITE_CONFIG_MALLOC].  ^If the
1845
** memory pointer is not NULL then the alternative memory
1846
** allocator is engaged to handle all of SQLites memory allocation needs.
1847
** The first pointer (the memory pointer) must be aligned to an 8-byte
1848
** boundary or subsequent behavior of SQLite will be undefined.
1849
** The minimum allocation size is capped at 2**12. Reasonable values
1850
** for the minimum allocation size are 2**5 through 2**8.</dd>
1851
**
1852
** [[SQLITE_CONFIG_MUTEX]] <dt>SQLITE_CONFIG_MUTEX</dt>
1853
** <dd> ^(The SQLITE_CONFIG_MUTEX option takes a single argument which is a
1854
** pointer to an instance of the [sqlite3_mutex_methods] structure.
1855
** The argument specifies alternative low-level mutex routines to be used
1856
** in place the mutex routines built into SQLite.)^  ^SQLite makes a copy of
1857
** the content of the [sqlite3_mutex_methods] structure before the call to
1858
** [sqlite3_config()] returns. ^If SQLite is compiled with
1859
** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1860
** the entire mutexing subsystem is omitted from the build and hence calls to
1861
** [sqlite3_config()] with the SQLITE_CONFIG_MUTEX configuration option will
1862
** return [SQLITE_ERROR].</dd>
1863
**
1864
** [[SQLITE_CONFIG_GETMUTEX]] <dt>SQLITE_CONFIG_GETMUTEX</dt>
1865
** <dd> ^(The SQLITE_CONFIG_GETMUTEX option takes a single argument which
1866
** is a pointer to an instance of the [sqlite3_mutex_methods] structure.  The
1867
** [sqlite3_mutex_methods]
1868
** structure is filled with the currently defined mutex routines.)^
1869
** This option can be used to overload the default mutex allocation
1870
** routines with a wrapper used to track mutex usage for performance
1871
** profiling or testing, for example.   ^If SQLite is compiled with
1872
** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1873
** the entire mutexing subsystem is omitted from the build and hence calls to
1874
** [sqlite3_config()] with the SQLITE_CONFIG_GETMUTEX configuration option will
1875
** return [SQLITE_ERROR].</dd>
1876
**
1877
** [[SQLITE_CONFIG_LOOKASIDE]] <dt>SQLITE_CONFIG_LOOKASIDE</dt>
1878
** <dd> ^(The SQLITE_CONFIG_LOOKASIDE option takes two arguments that determine
1879
** the default size of lookaside memory on each [database connection].
1880
** The first argument is the
1881
** size of each lookaside buffer slot and the second is the number of
1882
** slots allocated to each database connection.)^  ^(SQLITE_CONFIG_LOOKASIDE
1883
** sets the <i>default</i> lookaside size. The [SQLITE_DBCONFIG_LOOKASIDE]
1884
** option to [sqlite3_db_config()] can be used to change the lookaside
1885
** configuration on individual connections.)^ </dd>
1886
**
1887
** [[SQLITE_CONFIG_PCACHE2]] <dt>SQLITE_CONFIG_PCACHE2</dt>
1888
** <dd> ^(The SQLITE_CONFIG_PCACHE2 option takes a single argument which is
1889
** a pointer to an [sqlite3_pcache_methods2] object.  This object specifies
1890
** the interface to a custom page cache implementation.)^
1891
** ^SQLite makes a copy of the [sqlite3_pcache_methods2] object.</dd>
1892
**
1893
** [[SQLITE_CONFIG_GETPCACHE2]] <dt>SQLITE_CONFIG_GETPCACHE2</dt>
1894
** <dd> ^(The SQLITE_CONFIG_GETPCACHE2 option takes a single argument which
1895
** is a pointer to an [sqlite3_pcache_methods2] object.  SQLite copies of
1896
** the current page cache implementation into that object.)^ </dd>
1897
**
1898
** [[SQLITE_CONFIG_LOG]] <dt>SQLITE_CONFIG_LOG</dt>
1899
** <dd> The SQLITE_CONFIG_LOG option is used to configure the SQLite
1900
** global [error log].
1901
** (^The SQLITE_CONFIG_LOG option takes two arguments: a pointer to a
1902
** function with a call signature of void(*)(void*,int,const char*),
1903
** and a pointer to void. ^If the function pointer is not NULL, it is
1904
** invoked by [sqlite3_log()] to process each logging event.  ^If the
1905
** function pointer is NULL, the [sqlite3_log()] interface becomes a no-op.
1906
** ^The void pointer that is the second argument to SQLITE_CONFIG_LOG is
1907
** passed through as the first parameter to the application-defined logger
1908
** function whenever that function is invoked.  ^The second parameter to
1909
** the logger function is a copy of the first parameter to the corresponding
1910
** [sqlite3_log()] call and is intended to be a [result code] or an
1911
** [extended result code].  ^The third parameter passed to the logger is
1912
** log message after formatting via [sqlite3_snprintf()].
1913
** The SQLite logging interface is not reentrant; the logger function
1914
** supplied by the application must not invoke any SQLite interface.
1915
** In a multi-threaded application, the application-defined logger
1916
** function must be threadsafe. </dd>
1917
**
1918
** [[SQLITE_CONFIG_URI]] <dt>SQLITE_CONFIG_URI
1919
** <dd>^(The SQLITE_CONFIG_URI option takes a single argument of type int.
1920
** If non-zero, then URI handling is globally enabled. If the parameter is zero,
1921
** then URI handling is globally disabled.)^ ^If URI handling is globally
1922
** enabled, all filenames passed to [sqlite3_open()], [sqlite3_open_v2()],
1923
** [sqlite3_open16()] or
1924
** specified as part of [ATTACH] commands are interpreted as URIs, regardless
1925
** of whether or not the [SQLITE_OPEN_URI] flag is set when the database
1926
** connection is opened. ^If it is globally disabled, filenames are
1927
** only interpreted as URIs if the SQLITE_OPEN_URI flag is set when the
1928
** database connection is opened. ^(By default, URI handling is globally
1929
** disabled. The default value may be changed by compiling with the
1930
** [SQLITE_USE_URI] symbol defined.)^
1931
**
1932
** [[SQLITE_CONFIG_COVERING_INDEX_SCAN]] <dt>SQLITE_CONFIG_COVERING_INDEX_SCAN
1933
** <dd>^The SQLITE_CONFIG_COVERING_INDEX_SCAN option takes a single integer
1934
** argument which is interpreted as a boolean in order to enable or disable
1935
** the use of covering indices for full table scans in the query optimizer.
1936
** ^The default setting is determined
1937
** by the [SQLITE_ALLOW_COVERING_INDEX_SCAN] compile-time option, or is "on"
1938
** if that compile-time option is omitted.
1939
** The ability to disable the use of covering indices for full table scans
1940
** is because some incorrectly coded legacy applications might malfunction
1941
** when the optimization is enabled.  Providing the ability to
1942
** disable the optimization allows the older, buggy application code to work
1943
** without change even with newer versions of SQLite.
1944
**
1945
** [[SQLITE_CONFIG_PCACHE]] [[SQLITE_CONFIG_GETPCACHE]]
1946
** <dt>SQLITE_CONFIG_PCACHE and SQLITE_CONFIG_GETPCACHE
1947
** <dd> These options are obsolete and should not be used by new code.
1948
** They are retained for backwards compatibility but are now no-ops.
1949
** </dd>
1950
**
1951
** [[SQLITE_CONFIG_SQLLOG]]
1952
** <dt>SQLITE_CONFIG_SQLLOG
1953
** <dd>This option is only available if sqlite is compiled with the
1954
** [SQLITE_ENABLE_SQLLOG] pre-processor macro defined. The first argument should
1955
** be a pointer to a function of type void(*)(void*,sqlite3*,const char*, int).
1956
** The second should be of type (void*). The callback is invoked by the library
1957
** in three separate circumstances, identified by the value passed as the
1958
** fourth parameter. If the fourth parameter is 0, then the database connection
1959
** passed as the second argument has just been opened. The third argument
1960
** points to a buffer containing the name of the main database file. If the
1961
** fourth parameter is 1, then the SQL statement that the third parameter
1962
** points to has just been executed. Or, if the fourth parameter is 2, then
1963
** the connection being passed as the second parameter is being closed. The
1964
** third parameter is passed NULL In this case.  An example of using this
1965
** configuration option can be seen in the "test_sqllog.c" source file in
1966
** the canonical SQLite source tree.</dd>
1967
**
1968
** [[SQLITE_CONFIG_MMAP_SIZE]]
1969
** <dt>SQLITE_CONFIG_MMAP_SIZE
1970
** <dd>^SQLITE_CONFIG_MMAP_SIZE takes two 64-bit integer (sqlite3_int64) values
1971
** that are the default mmap size limit (the default setting for
1972
** [PRAGMA mmap_size]) and the maximum allowed mmap size limit.
1973
** ^The default setting can be overridden by each database connection using
1974
** either the [PRAGMA mmap_size] command, or by using the
1975
** [SQLITE_FCNTL_MMAP_SIZE] file control.  ^(The maximum allowed mmap size
1976
** will be silently truncated if necessary so that it does not exceed the
1977
** compile-time maximum mmap size set by the
1978
** [SQLITE_MAX_MMAP_SIZE] compile-time option.)^
1979
** ^If either argument to this option is negative, then that argument is
1980
** changed to its compile-time default.
1981
**
1982
** [[SQLITE_CONFIG_WIN32_HEAPSIZE]]
1983
** <dt>SQLITE_CONFIG_WIN32_HEAPSIZE
1984
** <dd>^The SQLITE_CONFIG_WIN32_HEAPSIZE option is only available if SQLite is
1985
** compiled for Windows with the [SQLITE_WIN32_MALLOC] pre-processor macro
1986
** defined. ^SQLITE_CONFIG_WIN32_HEAPSIZE takes a 32-bit unsigned integer value
1987
** that specifies the maximum size of the created heap.
1988
**
1989
** [[SQLITE_CONFIG_PCACHE_HDRSZ]]
1990
** <dt>SQLITE_CONFIG_PCACHE_HDRSZ
1991
** <dd>^The SQLITE_CONFIG_PCACHE_HDRSZ option takes a single parameter which
1992
** is a pointer to an integer and writes into that integer the number of extra
1993
** bytes per page required for each page in [SQLITE_CONFIG_PAGECACHE].
1994
** The amount of extra space required can change depending on the compiler,
1995
** target platform, and SQLite version.
1996
**
1997
** [[SQLITE_CONFIG_PMASZ]]
1998
** <dt>SQLITE_CONFIG_PMASZ
1999
** <dd>^The SQLITE_CONFIG_PMASZ option takes a single parameter which
2000
** is an unsigned integer and sets the "Minimum PMA Size" for the multithreaded
2001
** sorter to that integer.  The default minimum PMA Size is set by the
2002
** [SQLITE_SORTER_PMASZ] compile-time option.  New threads are launched
2003
** to help with sort operations when multithreaded sorting
2004
** is enabled (using the [PRAGMA threads] command) and the amount of content
2005
** to be sorted exceeds the page size times the minimum of the
2006
** [PRAGMA cache_size] setting and this value.
2007
**
2008
** [[SQLITE_CONFIG_STMTJRNL_SPILL]]
2009
** <dt>SQLITE_CONFIG_STMTJRNL_SPILL
2010
** <dd>^The SQLITE_CONFIG_STMTJRNL_SPILL option takes a single parameter which
2011
** becomes the [statement journal] spill-to-disk threshold.
2012
** [Statement journals] are held in memory until their size (in bytes)
2013
** exceeds this threshold, at which point they are written to disk.
2014
** Or if the threshold is -1, statement journals are always held
2015
** exclusively in memory.
2016
** Since many statement journals never become large, setting the spill
2017
** threshold to a value such as 64KiB can greatly reduce the amount of
2018
** I/O required to support statement rollback.
2019
** The default value for this setting is controlled by the
2020
** [SQLITE_STMTJRNL_SPILL] compile-time option.
2021
**
2022
** [[SQLITE_CONFIG_SORTERREF_SIZE]]
2023
** <dt>SQLITE_CONFIG_SORTERREF_SIZE
2024
** <dd>The SQLITE_CONFIG_SORTERREF_SIZE option accepts a single parameter
2025
** of type (int) - the new value of the sorter-reference size threshold.
2026
** Usually, when SQLite uses an external sort to order records according
2027
** to an ORDER BY clause, all fields required by the caller are present in the
2028
** sorted records. However, if SQLite determines based on the declared type
2029
** of a table column that its values are likely to be very large - larger
2030
** than the configured sorter-reference size threshold - then a reference
2031
** is stored in each sorted record and the required column values loaded
2032
** from the database as records are returned in sorted order. The default
2033
** value for this option is to never use this optimization. Specifying a
2034
** negative value for this option restores the default behaviour.
2035
** This option is only available if SQLite is compiled with the
2036
** [SQLITE_ENABLE_SORTER_REFERENCES] compile-time option.
2037
**
2038
** [[SQLITE_CONFIG_MEMDB_MAXSIZE]]
2039
** <dt>SQLITE_CONFIG_MEMDB_MAXSIZE
2040
** <dd>The SQLITE_CONFIG_MEMDB_MAXSIZE option accepts a single parameter
2041
** [sqlite3_int64] parameter which is the default maximum size for an in-memory
2042
** database created using [sqlite3_deserialize()].  This default maximum
2043
** size can be adjusted up or down for individual databases using the
2044
** [SQLITE_FCNTL_SIZE_LIMIT] [sqlite3_file_control|file-control].  If this
2045
** configuration setting is never used, then the default maximum is determined
2046
** by the [SQLITE_MEMDB_DEFAULT_MAXSIZE] compile-time option.  If that
2047
** compile-time option is not set, then the default maximum is 1073741824.
2048
** </dl>
2049
*/
2050
#define SQLITE_CONFIG_SINGLETHREAD  1  /* nil */
2051
#define SQLITE_CONFIG_MULTITHREAD   2  /* nil */
2052
#define SQLITE_CONFIG_SERIALIZED    3  /* nil */
2053
#define SQLITE_CONFIG_MALLOC        4  /* sqlite3_mem_methods* */
2054
#define SQLITE_CONFIG_GETMALLOC     5  /* sqlite3_mem_methods* */
2055
#define SQLITE_CONFIG_SCRATCH       6  /* No longer used */
2056
#define SQLITE_CONFIG_PAGECACHE     7  /* void*, int sz, int N */
2057
#define SQLITE_CONFIG_HEAP          8  /* void*, int nByte, int min */
2058
#define SQLITE_CONFIG_MEMSTATUS     9  /* boolean */
2059
#define SQLITE_CONFIG_MUTEX        10  /* sqlite3_mutex_methods* */
2060
#define SQLITE_CONFIG_GETMUTEX     11  /* sqlite3_mutex_methods* */
2061
/* previously SQLITE_CONFIG_CHUNKALLOC 12 which is now unused. */
2062
#define SQLITE_CONFIG_LOOKASIDE    13  /* int int */
2063
#define SQLITE_CONFIG_PCACHE       14  /* no-op */
2064
#define SQLITE_CONFIG_GETPCACHE    15  /* no-op */
2065
#define SQLITE_CONFIG_LOG          16  /* xFunc, void* */
2066
#define SQLITE_CONFIG_URI          17  /* int */
2067
#define SQLITE_CONFIG_PCACHE2      18  /* sqlite3_pcache_methods2* */
2068
#define SQLITE_CONFIG_GETPCACHE2   19  /* sqlite3_pcache_methods2* */
2069
#define SQLITE_CONFIG_COVERING_INDEX_SCAN 20  /* int */
2070
#define SQLITE_CONFIG_SQLLOG       21  /* xSqllog, void* */
2071
#define SQLITE_CONFIG_MMAP_SIZE    22  /* sqlite3_int64, sqlite3_int64 */
2072
#define SQLITE_CONFIG_WIN32_HEAPSIZE      23  /* int nByte */
2073
#define SQLITE_CONFIG_PCACHE_HDRSZ        24  /* int *psz */
2074
#define SQLITE_CONFIG_PMASZ               25  /* unsigned int szPma */
2075
#define SQLITE_CONFIG_STMTJRNL_SPILL      26  /* int nByte */
2076
#define SQLITE_CONFIG_SMALL_MALLOC        27  /* boolean */
2077
#define SQLITE_CONFIG_SORTERREF_SIZE      28  /* int nByte */
2078
#define SQLITE_CONFIG_MEMDB_MAXSIZE       29  /* sqlite3_int64 */
2079
2080
/*
2081
** CAPI3REF: Database Connection Configuration Options
2082
**
2083
** These constants are the available integer configuration options that
2084
** can be passed as the second argument to the [sqlite3_db_config()] interface.
2085
**
2086
** New configuration options may be added in future releases of SQLite.
2087
** Existing configuration options might be discontinued.  Applications
2088
** should check the return code from [sqlite3_db_config()] to make sure that
2089
** the call worked.  ^The [sqlite3_db_config()] interface will return a
2090
** non-zero [error code] if a discontinued or unsupported configuration option
2091
** is invoked.
2092
**
2093
** <dl>
2094
** [[SQLITE_DBCONFIG_LOOKASIDE]]
2095
** <dt>SQLITE_DBCONFIG_LOOKASIDE</dt>
2096
** <dd> ^This option takes three additional arguments that determine the
2097
** [lookaside memory allocator] configuration for the [database connection].
2098
** ^The first argument (the third parameter to [sqlite3_db_config()] is a
2099
** pointer to a memory buffer to use for lookaside memory.
2100
** ^The first argument after the SQLITE_DBCONFIG_LOOKASIDE verb
2101
** may be NULL in which case SQLite will allocate the
2102
** lookaside buffer itself using [sqlite3_malloc()]. ^The second argument is the
2103
** size of each lookaside buffer slot.  ^The third argument is the number of
2104
** slots.  The size of the buffer in the first argument must be greater than
2105
** or equal to the product of the second and third arguments.  The buffer
2106
** must be aligned to an 8-byte boundary.  ^If the second argument to
2107
** SQLITE_DBCONFIG_LOOKASIDE is not a multiple of 8, it is internally
2108
** rounded down to the next smaller multiple of 8.  ^(The lookaside memory
2109
** configuration for a database connection can only be changed when that
2110
** connection is not currently using lookaside memory, or in other words
2111
** when the "current value" returned by
2112
** [sqlite3_db_status](D,[SQLITE_CONFIG_LOOKASIDE],...) is zero.
2113
** Any attempt to change the lookaside memory configuration when lookaside
2114
** memory is in use leaves the configuration unchanged and returns
2115
** [SQLITE_BUSY].)^</dd>
2116
**
2117
** [[SQLITE_DBCONFIG_ENABLE_FKEY]]
2118
** <dt>SQLITE_DBCONFIG_ENABLE_FKEY</dt>
2119
** <dd> ^This option is used to enable or disable the enforcement of
2120
** [foreign key constraints].  There should be two additional arguments.
2121
** The first argument is an integer which is 0 to disable FK enforcement,
2122
** positive to enable FK enforcement or negative to leave FK enforcement
2123
** unchanged.  The second parameter is a pointer to an integer into which
2124
** is written 0 or 1 to indicate whether FK enforcement is off or on
2125
** following this call.  The second parameter may be a NULL pointer, in
2126
** which case the FK enforcement setting is not reported back. </dd>
2127
**
2128
** [[SQLITE_DBCONFIG_ENABLE_TRIGGER]]
2129
** <dt>SQLITE_DBCONFIG_ENABLE_TRIGGER</dt>
2130
** <dd> ^This option is used to enable or disable [CREATE TRIGGER | triggers].
2131
** There should be two additional arguments.
2132
** The first argument is an integer which is 0 to disable triggers,
2133
** positive to enable triggers or negative to leave the setting unchanged.
2134
** The second parameter is a pointer to an integer into which
2135
** is written 0 or 1 to indicate whether triggers are disabled or enabled
2136
** following this call.  The second parameter may be a NULL pointer, in
2137
** which case the trigger setting is not reported back.
2138
**
2139
** <p>Originally this option disabled all triggers.  ^(However, since
2140
** SQLite version 3.35.0, TEMP triggers are still allowed even if
2141
** this option is off.  So, in other words, this option now only disables
2142
** triggers in the main database schema or in the schemas of ATTACH-ed
2143
** databases.)^ </dd>
2144
**
2145
** [[SQLITE_DBCONFIG_ENABLE_VIEW]]
2146
** <dt>SQLITE_DBCONFIG_ENABLE_VIEW</dt>
2147
** <dd> ^This option is used to enable or disable [CREATE VIEW | views].
2148
** There should be two additional arguments.
2149
** The first argument is an integer which is 0 to disable views,
2150
** positive to enable views or negative to leave the setting unchanged.
2151
** The second parameter is a pointer to an integer into which
2152
** is written 0 or 1 to indicate whether views are disabled or enabled
2153
** following this call.  The second parameter may be a NULL pointer, in
2154
** which case the view setting is not reported back.
2155
**
2156
** <p>Originally this option disabled all views.  ^(However, since
2157
** SQLite version 3.35.0, TEMP views are still allowed even if
2158
** this option is off.  So, in other words, this option now only disables
2159
** views in the main database schema or in the schemas of ATTACH-ed
2160
** databases.)^ </dd>
2161
**
2162
** [[SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER]]
2163
** <dt>SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER</dt>
2164
** <dd> ^This option is used to enable or disable the
2165
** [fts3_tokenizer()] function which is part of the
2166
** [FTS3] full-text search engine extension.
2167
** There should be two additional arguments.
2168
** The first argument is an integer which is 0 to disable fts3_tokenizer() or
2169
** positive to enable fts3_tokenizer() or negative to leave the setting
2170
** unchanged.
2171
** The second parameter is a pointer to an integer into which
2172
** is written 0 or 1 to indicate whether fts3_tokenizer is disabled or enabled
2173
** following this call.  The second parameter may be a NULL pointer, in
2174
** which case the new setting is not reported back. </dd>
2175
**
2176
** [[SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION]]
2177
** <dt>SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION</dt>
2178
** <dd> ^This option is used to enable or disable the [sqlite3_load_extension()]
2179
** interface independently of the [load_extension()] SQL function.
2180
** The [sqlite3_enable_load_extension()] API enables or disables both the
2181
** C-API [sqlite3_load_extension()] and the SQL function [load_extension()].
2182
** There should be two additional arguments.
2183
** When the first argument to this interface is 1, then only the C-API is
2184
** enabled and the SQL function remains disabled.  If the first argument to
2185
** this interface is 0, then both the C-API and the SQL function are disabled.
2186
** If the first argument is -1, then no changes are made to state of either the
2187
** C-API or the SQL function.
2188
** The second parameter is a pointer to an integer into which
2189
** is written 0 or 1 to indicate whether [sqlite3_load_extension()] interface
2190
** is disabled or enabled following this call.  The second parameter may
2191
** be a NULL pointer, in which case the new setting is not reported back.
2192
** </dd>
2193
**
2194
** [[SQLITE_DBCONFIG_MAINDBNAME]] <dt>SQLITE_DBCONFIG_MAINDBNAME</dt>
2195
** <dd> ^This option is used to change the name of the "main" database
2196
** schema.  ^The sole argument is a pointer to a constant UTF8 string
2197
** which will become the new schema name in place of "main".  ^SQLite
2198
** does not make a copy of the new main schema name string, so the application
2199
** must ensure that the argument passed into this DBCONFIG option is unchanged
2200
** until after the database connection closes.
2201
** </dd>
2202
**
2203
** [[SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE]]
2204
** <dt>SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE</dt>
2205
** <dd> Usually, when a database in wal mode is closed or detached from a
2206
** database handle, SQLite checks if this will mean that there are now no
2207
** connections at all to the database. If so, it performs a checkpoint
2208
** operation before closing the connection. This option may be used to
2209
** override this behaviour. The first parameter passed to this operation
2210
** is an integer - positive to disable checkpoints-on-close, or zero (the
2211
** default) to enable them, and negative to leave the setting unchanged.
2212
** The second parameter is a pointer to an integer
2213
** into which is written 0 or 1 to indicate whether checkpoints-on-close
2214
** have been disabled - 0 if they are not disabled, 1 if they are.
2215
** </dd>
2216
**
2217
** [[SQLITE_DBCONFIG_ENABLE_QPSG]] <dt>SQLITE_DBCONFIG_ENABLE_QPSG</dt>
2218
** <dd>^(The SQLITE_DBCONFIG_ENABLE_QPSG option activates or deactivates
2219
** the [query planner stability guarantee] (QPSG).  When the QPSG is active,
2220
** a single SQL query statement will always use the same algorithm regardless
2221
** of values of [bound parameters].)^ The QPSG disables some query optimizations
2222
** that look at the values of bound parameters, which can make some queries
2223
** slower.  But the QPSG has the advantage of more predictable behavior.  With
2224
** the QPSG active, SQLite will always use the same query plan in the field as
2225
** was used during testing in the lab.
2226
** The first argument to this setting is an integer which is 0 to disable
2227
** the QPSG, positive to enable QPSG, or negative to leave the setting
2228
** unchanged. The second parameter is a pointer to an integer into which
2229
** is written 0 or 1 to indicate whether the QPSG is disabled or enabled
2230
** following this call.
2231
** </dd>
2232
**
2233
** [[SQLITE_DBCONFIG_TRIGGER_EQP]] <dt>SQLITE_DBCONFIG_TRIGGER_EQP</dt>
2234
** <dd> By default, the output of EXPLAIN QUERY PLAN commands does not
2235
** include output for any operations performed by trigger programs. This
2236
** option is used to set or clear (the default) a flag that governs this
2237
** behavior. The first parameter passed to this operation is an integer -
2238
** positive to enable output for trigger programs, or zero to disable it,
2239
** or negative to leave the setting unchanged.
2240
** The second parameter is a pointer to an integer into which is written
2241
** 0 or 1 to indicate whether output-for-triggers has been disabled - 0 if
2242
** it is not disabled, 1 if it is.
2243
** </dd>
2244
**
2245
** [[SQLITE_DBCONFIG_RESET_DATABASE]] <dt>SQLITE_DBCONFIG_RESET_DATABASE</dt>
2246
** <dd> Set the SQLITE_DBCONFIG_RESET_DATABASE flag and then run
2247
** [VACUUM] in order to reset a database back to an empty database
2248
** with no schema and no content. The following process works even for
2249
** a badly corrupted database file:
2250
** <ol>
2251
** <li> If the database connection is newly opened, make sure it has read the
2252
**      database schema by preparing then discarding some query against the
2253
**      database, or calling sqlite3_table_column_metadata(), ignoring any
2254
**      errors.  This step is only necessary if the application desires to keep
2255
**      the database in WAL mode after the reset if it was in WAL mode before
2256
**      the reset.
2257
** <li> sqlite3_db_config(db, SQLITE_DBCONFIG_RESET_DATABASE, 1, 0);
2258
** <li> [sqlite3_exec](db, "[VACUUM]", 0, 0, 0);
2259
** <li> sqlite3_db_config(db, SQLITE_DBCONFIG_RESET_DATABASE, 0, 0);
2260
** </ol>
2261
** Because resetting a database is destructive and irreversible, the
2262
** process requires the use of this obscure API and multiple steps to help
2263
** ensure that it does not happen by accident.
2264
**
2265
** [[SQLITE_DBCONFIG_DEFENSIVE]] <dt>SQLITE_DBCONFIG_DEFENSIVE</dt>
2266
** <dd>The SQLITE_DBCONFIG_DEFENSIVE option activates or deactivates the
2267
** "defensive" flag for a database connection.  When the defensive
2268
** flag is enabled, language features that allow ordinary SQL to
2269
** deliberately corrupt the database file are disabled.  The disabled
2270
** features include but are not limited to the following:
2271
** <ul>
2272
** <li> The [PRAGMA writable_schema=ON] statement.
2273
** <li> The [PRAGMA journal_mode=OFF] statement.
2274
** <li> Writes to the [sqlite_dbpage] virtual table.
2275
** <li> Direct writes to [shadow tables].
2276
** </ul>
2277
** </dd>
2278
**
2279
** [[SQLITE_DBCONFIG_WRITABLE_SCHEMA]] <dt>SQLITE_DBCONFIG_WRITABLE_SCHEMA</dt>
2280
** <dd>The SQLITE_DBCONFIG_WRITABLE_SCHEMA option activates or deactivates the
2281
** "writable_schema" flag. This has the same effect and is logically equivalent
2282
** to setting [PRAGMA writable_schema=ON] or [PRAGMA writable_schema=OFF].
2283
** The first argument to this setting is an integer which is 0 to disable
2284
** the writable_schema, positive to enable writable_schema, or negative to
2285
** leave the setting unchanged. The second parameter is a pointer to an
2286
** integer into which is written 0 or 1 to indicate whether the writable_schema
2287
** is enabled or disabled following this call.
2288
** </dd>
2289
**
2290
** [[SQLITE_DBCONFIG_LEGACY_ALTER_TABLE]]
2291
** <dt>SQLITE_DBCONFIG_LEGACY_ALTER_TABLE</dt>
2292
** <dd>The SQLITE_DBCONFIG_LEGACY_ALTER_TABLE option activates or deactivates
2293
** the legacy behavior of the [ALTER TABLE RENAME] command such it
2294
** behaves as it did prior to [version 3.24.0] (2018-06-04).  See the
2295
** "Compatibility Notice" on the [ALTER TABLE RENAME documentation] for
2296
** additional information. This feature can also be turned on and off
2297
** using the [PRAGMA legacy_alter_table] statement.
2298
** </dd>
2299
**
2300
** [[SQLITE_DBCONFIG_DQS_DML]]
2301
** <dt>SQLITE_DBCONFIG_DQS_DML</td>
2302
** <dd>The SQLITE_DBCONFIG_DQS_DML option activates or deactivates
2303
** the legacy [double-quoted string literal] misfeature for DML statements
2304
** only, that is DELETE, INSERT, SELECT, and UPDATE statements. The
2305
** default value of this setting is determined by the [-DSQLITE_DQS]
2306
** compile-time option.
2307
** </dd>
2308
**
2309
** [[SQLITE_DBCONFIG_DQS_DDL]]
2310
** <dt>SQLITE_DBCONFIG_DQS_DDL</td>
2311
** <dd>The SQLITE_DBCONFIG_DQS option activates or deactivates
2312
** the legacy [double-quoted string literal] misfeature for DDL statements,
2313
** such as CREATE TABLE and CREATE INDEX. The
2314
** default value of this setting is determined by the [-DSQLITE_DQS]
2315
** compile-time option.
2316
** </dd>
2317
**
2318
** [[SQLITE_DBCONFIG_TRUSTED_SCHEMA]]
2319
** <dt>SQLITE_DBCONFIG_TRUSTED_SCHEMA</td>
2320
** <dd>The SQLITE_DBCONFIG_TRUSTED_SCHEMA option tells SQLite to
2321
** assume that database schemas are untainted by malicious content.
2322
** When the SQLITE_DBCONFIG_TRUSTED_SCHEMA option is disabled, SQLite
2323
** takes additional defensive steps to protect the application from harm
2324
** including:
2325
** <ul>
2326
** <li> Prohibit the use of SQL functions inside triggers, views,
2327
** CHECK constraints, DEFAULT clauses, expression indexes,
2328
** partial indexes, or generated columns
2329
** unless those functions are tagged with [SQLITE_INNOCUOUS].
2330
** <li> Prohibit the use of virtual tables inside of triggers or views
2331
** unless those virtual tables are tagged with [SQLITE_VTAB_INNOCUOUS].
2332
** </ul>
2333
** This setting defaults to "on" for legacy compatibility, however
2334
** all applications are advised to turn it off if possible. This setting
2335
** can also be controlled using the [PRAGMA trusted_schema] statement.
2336
** </dd>
2337
**
2338
** [[SQLITE_DBCONFIG_LEGACY_FILE_FORMAT]]
2339
** <dt>SQLITE_DBCONFIG_LEGACY_FILE_FORMAT</td>
2340
** <dd>The SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option activates or deactivates
2341
** the legacy file format flag.  When activated, this flag causes all newly
2342
** created database file to have a schema format version number (the 4-byte
2343
** integer found at offset 44 into the database header) of 1.  This in turn
2344
** means that the resulting database file will be readable and writable by
2345
** any SQLite version back to 3.0.0 ([dateof:3.0.0]).  Without this setting,
2346
** newly created databases are generally not understandable by SQLite versions
2347
** prior to 3.3.0 ([dateof:3.3.0]).  As these words are written, there
2348
** is now scarcely any need to generated database files that are compatible
2349
** all the way back to version 3.0.0, and so this setting is of little
2350
** practical use, but is provided so that SQLite can continue to claim the
2351
** ability to generate new database files that are compatible with  version
2352
** 3.0.0.
2353
** <p>Note that when the SQLITE_DBCONFIG_LEGACY_FILE_FORMAT setting is on,
2354
** the [VACUUM] command will fail with an obscure error when attempting to
2355
** process a table with generated columns and a descending index.  This is
2356
** not considered a bug since SQLite versions 3.3.0 and earlier do not support
2357
** either generated columns or decending indexes.
2358
** </dd>
2359
** </dl>
2360
*/
2361
#define SQLITE_DBCONFIG_MAINDBNAME            1000 /* const char* */
2362
#define SQLITE_DBCONFIG_LOOKASIDE             1001 /* void* int int */
2363
#define SQLITE_DBCONFIG_ENABLE_FKEY           1002 /* int int* */
2364
#define SQLITE_DBCONFIG_ENABLE_TRIGGER        1003 /* int int* */
2365
#define SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER 1004 /* int int* */
2366
#define SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION 1005 /* int int* */
2367
#define SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE      1006 /* int int* */
2368
#define SQLITE_DBCONFIG_ENABLE_QPSG           1007 /* int int* */
2369
#define SQLITE_DBCONFIG_TRIGGER_EQP           1008 /* int int* */
2370
#define SQLITE_DBCONFIG_RESET_DATABASE        1009 /* int int* */
2371
#define SQLITE_DBCONFIG_DEFENSIVE             1010 /* int int* */
2372
#define SQLITE_DBCONFIG_WRITABLE_SCHEMA       1011 /* int int* */
2373
#define SQLITE_DBCONFIG_LEGACY_ALTER_TABLE    1012 /* int int* */
2374
#define SQLITE_DBCONFIG_DQS_DML               1013 /* int int* */
2375
#define SQLITE_DBCONFIG_DQS_DDL               1014 /* int int* */
2376
#define SQLITE_DBCONFIG_ENABLE_VIEW           1015 /* int int* */
2377
#define SQLITE_DBCONFIG_LEGACY_FILE_FORMAT    1016 /* int int* */
2378
#define SQLITE_DBCONFIG_TRUSTED_SCHEMA        1017 /* int int* */
2379
#define SQLITE_DBCONFIG_MAX                   1017 /* Largest DBCONFIG */
2380
2381
/*
2382
** CAPI3REF: Enable Or Disable Extended Result Codes
2383
** METHOD: sqlite3
2384
**
2385
** ^The sqlite3_extended_result_codes() routine enables or disables the
2386
** [extended result codes] feature of SQLite. ^The extended result
2387
** codes are disabled by default for historical compatibility.
2388
*/
2389
SQLITE_API int sqlite3_extended_result_codes(sqlite3*, int onoff);
2390
2391
/*
2392
** CAPI3REF: Last Insert Rowid
2393
** METHOD: sqlite3
2394
**
2395
** ^Each entry in most SQLite tables (except for [WITHOUT ROWID] tables)
2396
** has a unique 64-bit signed
2397
** integer key called the [ROWID | "rowid"]. ^The rowid is always available
2398
** as an undeclared column named ROWID, OID, or _ROWID_ as long as those
2399
** names are not also used by explicitly declared columns. ^If
2400
** the table has a column of type [INTEGER PRIMARY KEY] then that column
2401
** is another alias for the rowid.
2402
**
2403
** ^The sqlite3_last_insert_rowid(D) interface usually returns the [rowid] of
2404
** the most recent successful [INSERT] into a rowid table or [virtual table]
2405
** on database connection D. ^Inserts into [WITHOUT ROWID] tables are not
2406
** recorded. ^If no successful [INSERT]s into rowid tables have ever occurred
2407
** on the database connection D, then sqlite3_last_insert_rowid(D) returns
2408
** zero.
2409
**
2410
** As well as being set automatically as rows are inserted into database
2411
** tables, the value returned by this function may be set explicitly by
2412
** [sqlite3_set_last_insert_rowid()]
2413
**
2414
** Some virtual table implementations may INSERT rows into rowid tables as
2415
** part of committing a transaction (e.g. to flush data accumulated in memory
2416
** to disk). In this case subsequent calls to this function return the rowid
2417
** associated with these internal INSERT operations, which leads to
2418
** unintuitive results. Virtual table implementations that do write to rowid
2419
** tables in this way can avoid this problem by restoring the original
2420
** rowid value using [sqlite3_set_last_insert_rowid()] before returning
2421
** control to the user.
2422
**
2423
** ^(If an [INSERT] occurs within a trigger then this routine will
2424
** return the [rowid] of the inserted row as long as the trigger is
2425
** running. Once the trigger program ends, the value returned
2426
** by this routine reverts to what it was before the trigger was fired.)^
2427
**
2428
** ^An [INSERT] that fails due to a constraint violation is not a
2429
** successful [INSERT] and does not change the value returned by this
2430
** routine.  ^Thus INSERT OR FAIL, INSERT OR IGNORE, INSERT OR ROLLBACK,
2431
** and INSERT OR ABORT make no changes to the return value of this
2432
** routine when their insertion fails.  ^(When INSERT OR REPLACE
2433
** encounters a constraint violation, it does not fail.  The
2434
** INSERT continues to completion after deleting rows that caused
2435
** the constraint problem so INSERT OR REPLACE will always change
2436
** the return value of this interface.)^
2437
**
2438
** ^For the purposes of this routine, an [INSERT] is considered to
2439
** be successful even if it is subsequently rolled back.
2440
**
2441
** This function is accessible to SQL statements via the
2442
** [last_insert_rowid() SQL function].
2443
**
2444
** If a separate thread performs a new [INSERT] on the same
2445
** database connection while the [sqlite3_last_insert_rowid()]
2446
** function is running and thus changes the last insert [rowid],
2447
** then the value returned by [sqlite3_last_insert_rowid()] is
2448
** unpredictable and might not equal either the old or the new
2449
** last insert [rowid].
2450
*/
2451
SQLITE_API sqlite3_int64 sqlite3_last_insert_rowid(sqlite3*);
2452
2453
/*
2454
** CAPI3REF: Set the Last Insert Rowid value.
2455
** METHOD: sqlite3
2456
**
2457
** The sqlite3_set_last_insert_rowid(D, R) method allows the application to
2458
** set the value returned by calling sqlite3_last_insert_rowid(D) to R
2459
** without inserting a row into the database.
2460
*/
2461
SQLITE_API void sqlite3_set_last_insert_rowid(sqlite3*,sqlite3_int64);
2462
2463
/*
2464
** CAPI3REF: Count The Number Of Rows Modified
2465
** METHOD: sqlite3
2466
**
2467
** ^This function returns the number of rows modified, inserted or
2468
** deleted by the most recently completed INSERT, UPDATE or DELETE
2469
** statement on the database connection specified by the only parameter.
2470
** ^Executing any other type of SQL statement does not modify the value
2471
** returned by this function.
2472
**
2473
** ^Only changes made directly by the INSERT, UPDATE or DELETE statement are
2474
** considered - auxiliary changes caused by [CREATE TRIGGER | triggers],
2475
** [foreign key actions] or [REPLACE] constraint resolution are not counted.
2476
**
2477
** Changes to a view that are intercepted by
2478
** [INSTEAD OF trigger | INSTEAD OF triggers] are not counted. ^The value
2479
** returned by sqlite3_changes() immediately after an INSERT, UPDATE or
2480
** DELETE statement run on a view is always zero. Only changes made to real
2481
** tables are counted.
2482
**
2483
** Things are more complicated if the sqlite3_changes() function is
2484
** executed while a trigger program is running. This may happen if the
2485
** program uses the [changes() SQL function], or if some other callback
2486
** function invokes sqlite3_changes() directly. Essentially:
2487
**
2488
** <ul>
2489
**   <li> ^(Before entering a trigger program the value returned by
2490
**        sqlite3_changes() function is saved. After the trigger program
2491
**        has finished, the original value is restored.)^
2492
**
2493
**   <li> ^(Within a trigger program each INSERT, UPDATE and DELETE
2494
**        statement sets the value returned by sqlite3_changes()
2495
**        upon completion as normal. Of course, this value will not include
2496
**        any changes performed by sub-triggers, as the sqlite3_changes()
2497
**        value will be saved and restored after each sub-trigger has run.)^
2498
** </ul>
2499
**
2500
** ^This means that if the changes() SQL function (or similar) is used
2501
** by the first INSERT, UPDATE or DELETE statement within a trigger, it
2502
** returns the value as set when the calling statement began executing.
2503
** ^If it is used by the second or subsequent such statement within a trigger
2504
** program, the value returned reflects the number of rows modified by the
2505
** previous INSERT, UPDATE or DELETE statement within the same trigger.
2506
**
2507
** If a separate thread makes changes on the same database connection
2508
** while [sqlite3_changes()] is running then the value returned
2509
** is unpredictable and not meaningful.
2510
**
2511
** See also:
2512
** <ul>
2513
** <li> the [sqlite3_total_changes()] interface
2514
** <li> the [count_changes pragma]
2515
** <li> the [changes() SQL function]
2516
** <li> the [data_version pragma]
2517
** </ul>
2518
*/
2519
SQLITE_API int sqlite3_changes(sqlite3*);
2520
2521
/*
2522
** CAPI3REF: Total Number Of Rows Modified
2523
** METHOD: sqlite3
2524
**
2525
** ^This function returns the total number of rows inserted, modified or
2526
** deleted by all [INSERT], [UPDATE] or [DELETE] statements completed
2527
** since the database connection was opened, including those executed as
2528
** part of trigger programs. ^Executing any other type of SQL statement
2529
** does not affect the value returned by sqlite3_total_changes().
2530
**
2531
** ^Changes made as part of [foreign key actions] are included in the
2532
** count, but those made as part of REPLACE constraint resolution are
2533
** not. ^Changes to a view that are intercepted by INSTEAD OF triggers
2534
** are not counted.
2535
**
2536
** The [sqlite3_total_changes(D)] interface only reports the number
2537
** of rows that changed due to SQL statement run against database
2538
** connection D.  Any changes by other database connections are ignored.
2539
** To detect changes against a database file from other database
2540
** connections use the [PRAGMA data_version] command or the
2541
** [SQLITE_FCNTL_DATA_VERSION] [file control].
2542
**
2543
** If a separate thread makes changes on the same database connection
2544
** while [sqlite3_total_changes()] is running then the value
2545
** returned is unpredictable and not meaningful.
2546
**
2547
** See also:
2548
** <ul>
2549
** <li> the [sqlite3_changes()] interface
2550
** <li> the [count_changes pragma]
2551
** <li> the [changes() SQL function]
2552
** <li> the [data_version pragma]
2553
** <li> the [SQLITE_FCNTL_DATA_VERSION] [file control]
2554
** </ul>
2555
*/
2556
SQLITE_API int sqlite3_total_changes(sqlite3*);
2557
2558
/*
2559
** CAPI3REF: Interrupt A Long-Running Query
2560
** METHOD: sqlite3
2561
**
2562
** ^This function causes any pending database operation to abort and
2563
** return at its earliest opportunity. This routine is typically
2564
** called in response to a user action such as pressing "Cancel"
2565
** or Ctrl-C where the user wants a long query operation to halt
2566
** immediately.
2567
**
2568
** ^It is safe to call this routine from a thread different from the
2569
** thread that is currently running the database operation.  But it
2570
** is not safe to call this routine with a [database connection] that
2571
** is closed or might close before sqlite3_interrupt() returns.
2572
**
2573
** ^If an SQL operation is very nearly finished at the time when
2574
** sqlite3_interrupt() is called, then it might not have an opportunity
2575
** to be interrupted and might continue to completion.
2576
**
2577
** ^An SQL operation that is interrupted will return [SQLITE_INTERRUPT].
2578
** ^If the interrupted SQL operation is an INSERT, UPDATE, or DELETE
2579
** that is inside an explicit transaction, then the entire transaction
2580
** will be rolled back automatically.
2581
**
2582
** ^The sqlite3_interrupt(D) call is in effect until all currently running
2583
** SQL statements on [database connection] D complete.  ^Any new SQL statements
2584
** that are started after the sqlite3_interrupt() call and before the
2585
** running statement count reaches zero are interrupted as if they had been
2586
** running prior to the sqlite3_interrupt() call.  ^New SQL statements
2587
** that are started after the running statement count reaches zero are
2588
** not effected by the sqlite3_interrupt().
2589
** ^A call to sqlite3_interrupt(D) that occurs when there are no running
2590
** SQL statements is a no-op and has no effect on SQL statements
2591
** that are started after the sqlite3_interrupt() call returns.
2592
*/
2593
SQLITE_API void sqlite3_interrupt(sqlite3*);
2594
2595
/*
2596
** CAPI3REF: Determine If An SQL Statement Is Complete
2597
**
2598
** These routines are useful during command-line input to determine if the
2599
** currently entered text seems to form a complete SQL statement or
2600
** if additional input is needed before sending the text into
2601
** SQLite for parsing.  ^These routines return 1 if the input string
2602
** appears to be a complete SQL statement.  ^A statement is judged to be
2603
** complete if it ends with a semicolon token and is not a prefix of a
2604
** well-formed CREATE TRIGGER statement.  ^Semicolons that are embedded within
2605
** string literals or quoted identifier names or comments are not
2606
** independent tokens (they are part of the token in which they are
2607
** embedded) and thus do not count as a statement terminator.  ^Whitespace
2608
** and comments that follow the final semicolon are ignored.
2609
**
2610
** ^These routines return 0 if the statement is incomplete.  ^If a
2611
** memory allocation fails, then SQLITE_NOMEM is returned.
2612
**
2613
** ^These routines do not parse the SQL statements thus
2614
** will not detect syntactically incorrect SQL.
2615
**
2616
** ^(If SQLite has not been initialized using [sqlite3_initialize()] prior
2617
** to invoking sqlite3_complete16() then sqlite3_initialize() is invoked
2618
** automatically by sqlite3_complete16().  If that initialization fails,
2619
** then the return value from sqlite3_complete16() will be non-zero
2620
** regardless of whether or not the input SQL is complete.)^
2621
**
2622
** The input to [sqlite3_complete()] must be a zero-terminated
2623
** UTF-8 string.
2624
**
2625
** The input to [sqlite3_complete16()] must be a zero-terminated
2626
** UTF-16 string in native byte order.
2627
*/
2628
SQLITE_API int sqlite3_complete(const char *sql);
2629
SQLITE_API int sqlite3_complete16(const void *sql);
2630
2631
/*
2632
** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2633
** KEYWORDS: {busy-handler callback} {busy handler}
2634
** METHOD: sqlite3
2635
**
2636
** ^The sqlite3_busy_handler(D,X,P) routine sets a callback function X
2637
** that might be invoked with argument P whenever
2638
** an attempt is made to access a database table associated with
2639
** [database connection] D when another thread
2640
** or process has the table locked.
2641
** The sqlite3_busy_handler() interface is used to implement
2642
** [sqlite3_busy_timeout()] and [PRAGMA busy_timeout].
2643
**
2644
** ^If the busy callback is NULL, then [SQLITE_BUSY]
2645
** is returned immediately upon encountering the lock.  ^If the busy callback
2646
** is not NULL, then the callback might be invoked with two arguments.
2647
**
2648
** ^The first argument to the busy handler is a copy of the void* pointer which
2649
** is the third argument to sqlite3_busy_handler().  ^The second argument to
2650
** the busy handler callback is the number of times that the busy handler has
2651
** been invoked previously for the same locking event.  ^If the
2652
** busy callback returns 0, then no additional attempts are made to
2653
** access the database and [SQLITE_BUSY] is returned
2654
** to the application.
2655
** ^If the callback returns non-zero, then another attempt
2656
** is made to access the database and the cycle repeats.
2657
**
2658
** The presence of a busy handler does not guarantee that it will be invoked
2659
** when there is lock contention. ^If SQLite determines that invoking the busy
2660
** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2661
** to the application instead of invoking the
2662
** busy handler.
2663
** Consider a scenario where one process is holding a read lock that
2664
** it is trying to promote to a reserved lock and
2665
** a second process is holding a reserved lock that it is trying
2666
** to promote to an exclusive lock.  The first process cannot proceed
2667
** because it is blocked by the second and the second process cannot
2668
** proceed because it is blocked by the first.  If both processes
2669
** invoke the busy handlers, neither will make any progress.  Therefore,
2670
** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2671
** will induce the first process to release its read lock and allow
2672
** the second process to proceed.
2673
**
2674
** ^The default busy callback is NULL.
2675
**
2676
** ^(There can only be a single busy handler defined for each
2677
** [database connection].  Setting a new busy handler clears any
2678
** previously set handler.)^  ^Note that calling [sqlite3_busy_timeout()]
2679
** or evaluating [PRAGMA busy_timeout=N] will change the
2680
** busy handler and thus clear any previously set busy handler.
2681
**
2682
** The busy callback should not take any actions which modify the
2683
** database connection that invoked the busy handler.  In other words,
2684
** the busy handler is not reentrant.  Any such actions
2685
** result in undefined behavior.
2686
**
2687
** A busy handler must not close the database connection
2688
** or [prepared statement] that invoked the busy handler.
2689
*/
2690
SQLITE_API int sqlite3_busy_handler(sqlite3*,int(*)(void*,int),void*);
2691
2692
/*
2693
** CAPI3REF: Set A Busy Timeout
2694
** METHOD: sqlite3
2695
**
2696
** ^This routine sets a [sqlite3_busy_handler | busy handler] that sleeps
2697
** for a specified amount of time when a table is locked.  ^The handler
2698
** will sleep multiple times until at least "ms" milliseconds of sleeping
2699
** have accumulated.  ^After at least "ms" milliseconds of sleeping,
2700
** the handler returns 0 which causes [sqlite3_step()] to return
2701
** [SQLITE_BUSY].
2702
**
2703
** ^Calling this routine with an argument less than or equal to zero
2704
** turns off all busy handlers.
2705
**
2706
** ^(There can only be a single busy handler for a particular
2707
** [database connection] at any given moment.  If another busy handler
2708
** was defined  (using [sqlite3_busy_handler()]) prior to calling
2709
** this routine, that other busy handler is cleared.)^
2710
**
2711
** See also:  [PRAGMA busy_timeout]
2712
*/
2713
SQLITE_API int sqlite3_busy_timeout(sqlite3*, int ms);
2714
2715
/*
2716
** CAPI3REF: Convenience Routines For Running Queries
2717
** METHOD: sqlite3
2718
**
2719
** This is a legacy interface that is preserved for backwards compatibility.
2720
** Use of this interface is not recommended.
2721
**
2722
** Definition: A <b>result table</b> is memory data structure created by the
2723
** [sqlite3_get_table()] interface.  A result table records the
2724
** complete query results from one or more queries.
2725
**
2726
** The table conceptually has a number of rows and columns.  But
2727
** these numbers are not part of the result table itself.  These
2728
** numbers are obtained separately.  Let N be the number of rows
2729
** and M be the number of columns.
2730
**
2731
** A result table is an array of pointers to zero-terminated UTF-8 strings.
2732
** There are (N+1)*M elements in the array.  The first M pointers point
2733
** to zero-terminated strings that  contain the names of the columns.
2734
** The remaining entries all point to query results.  NULL values result
2735
** in NULL pointers.  All other values are in their UTF-8 zero-terminated
2736
** string representation as returned by [sqlite3_column_text()].
2737
**
2738
** A result table might consist of one or more memory allocations.
2739
** It is not safe to pass a result table directly to [sqlite3_free()].
2740
** A result table should be deallocated using [sqlite3_free_table()].
2741
**
2742
** ^(As an example of the result table format, suppose a query result
2743
** is as follows:
2744
**
2745
** <blockquote><pre>
2746
**        Name        | Age
2747
**        -----------------------
2748
**        Alice       | 43
2749
**        Bob         | 28
2750
**        Cindy       | 21
2751
** </pre></blockquote>
2752
**
2753
** There are two columns (M==2) and three rows (N==3).  Thus the
2754
** result table has 8 entries.  Suppose the result table is stored
2755
** in an array named azResult.  Then azResult holds this content:
2756
**
2757
** <blockquote><pre>
2758
**        azResult&#91;0] = "Name";
2759
**        azResult&#91;1] = "Age";
2760
**        azResult&#91;2] = "Alice";
2761
**        azResult&#91;3] = "43";
2762
**        azResult&#91;4] = "Bob";
2763
**        azResult&#91;5] = "28";
2764
**        azResult&#91;6] = "Cindy";
2765
**        azResult&#91;7] = "21";
2766
** </pre></blockquote>)^
2767
**
2768
** ^The sqlite3_get_table() function evaluates one or more
2769
** semicolon-separated SQL statements in the zero-terminated UTF-8
2770
** string of its 2nd parameter and returns a result table to the
2771
** pointer given in its 3rd parameter.
2772
**
2773
** After the application has finished with the result from sqlite3_get_table(),
2774
** it must pass the result table pointer to sqlite3_free_table() in order to
2775
** release the memory that was malloced.  Because of the way the
2776
** [sqlite3_malloc()] happens within sqlite3_get_table(), the calling
2777
** function must not try to call [sqlite3_free()] directly.  Only
2778
** [sqlite3_free_table()] is able to release the memory properly and safely.
2779
**
2780
** The sqlite3_get_table() interface is implemented as a wrapper around
2781
** [sqlite3_exec()].  The sqlite3_get_table() routine does not have access
2782
** to any internal data structures of SQLite.  It uses only the public
2783
** interface defined here.  As a consequence, errors that occur in the
2784
** wrapper layer outside of the internal [sqlite3_exec()] call are not
2785
** reflected in subsequent calls to [sqlite3_errcode()] or
2786
** [sqlite3_errmsg()].
2787
*/
2788
SQLITE_API int sqlite3_get_table(
2789
  sqlite3 *db,          /* An open database */
2790
  const char *zSql,     /* SQL to be evaluated */
2791
  char ***pazResult,    /* Results of the query */
2792
  int *pnRow,           /* Number of result rows written here */
2793
  int *pnColumn,        /* Number of result columns written here */
2794
  char **pzErrmsg       /* Error msg written here */
2795
);
2796
SQLITE_API void sqlite3_free_table(char **result);
2797
2798
/*
2799
** CAPI3REF: Formatted String Printing Functions
2800
**
2801
** These routines are work-alikes of the "printf()" family of functions
2802
** from the standard C library.
2803
** These routines understand most of the common formatting options from
2804
** the standard library printf()
2805
** plus some additional non-standard formats ([%q], [%Q], [%w], and [%z]).
2806
** See the [built-in printf()] documentation for details.
2807
**
2808
** ^The sqlite3_mprintf() and sqlite3_vmprintf() routines write their
2809
** results into memory obtained from [sqlite3_malloc64()].
2810
** The strings returned by these two routines should be
2811
** released by [sqlite3_free()].  ^Both routines return a
2812
** NULL pointer if [sqlite3_malloc64()] is unable to allocate enough
2813
** memory to hold the resulting string.
2814
**
2815
** ^(The sqlite3_snprintf() routine is similar to "snprintf()" from
2816
** the standard C library.  The result is written into the
2817
** buffer supplied as the second parameter whose size is given by
2818
** the first parameter. Note that the order of the
2819
** first two parameters is reversed from snprintf().)^  This is an
2820
** historical accident that cannot be fixed without breaking
2821
** backwards compatibility.  ^(Note also that sqlite3_snprintf()
2822
** returns a pointer to its buffer instead of the number of
2823
** characters actually written into the buffer.)^  We admit that
2824
** the number of characters written would be a more useful return
2825
** value but we cannot change the implementation of sqlite3_snprintf()
2826
** now without breaking compatibility.
2827
**
2828
** ^As long as the buffer size is greater than zero, sqlite3_snprintf()
2829
** guarantees that the buffer is always zero-terminated.  ^The first
2830
** parameter "n" is the total size of the buffer, including space for
2831
** the zero terminator.  So the longest string that can be completely
2832
** written will be n-1 characters.
2833
**
2834
** ^The sqlite3_vsnprintf() routine is a varargs version of sqlite3_snprintf().
2835
**
2836
** See also:  [built-in printf()], [printf() SQL function]
2837
*/
2838
SQLITE_API char *sqlite3_mprintf(const char*,...);
2839
SQLITE_API char *sqlite3_vmprintf(const char*, va_list);
2840
SQLITE_API char *sqlite3_snprintf(int,char*,const char*, ...);
2841
SQLITE_API char *sqlite3_vsnprintf(int,char*,const char*, va_list);
2842
2843
/*
2844
** CAPI3REF: Memory Allocation Subsystem
2845
**
2846
** The SQLite core uses these three routines for all of its own
2847
** internal memory allocation needs. "Core" in the previous sentence
2848
** does not include operating-system specific [VFS] implementation.  The
2849
** Windows VFS uses native malloc() and free() for some operations.
2850
**
2851
** ^The sqlite3_malloc() routine returns a pointer to a block
2852
** of memory at least N bytes in length, where N is the parameter.
2853
** ^If sqlite3_malloc() is unable to obtain sufficient free
2854
** memory, it returns a NULL pointer.  ^If the parameter N to
2855
** sqlite3_malloc() is zero or negative then sqlite3_malloc() returns
2856
** a NULL pointer.
2857
**
2858
** ^The sqlite3_malloc64(N) routine works just like
2859
** sqlite3_malloc(N) except that N is an unsigned 64-bit integer instead
2860
** of a signed 32-bit integer.
2861
**
2862
** ^Calling sqlite3_free() with a pointer previously returned
2863
** by sqlite3_malloc() or sqlite3_realloc() releases that memory so
2864
** that it might be reused.  ^The sqlite3_free() routine is
2865
** a no-op if is called with a NULL pointer.  Passing a NULL pointer
2866
** to sqlite3_free() is harmless.  After being freed, memory
2867
** should neither be read nor written.  Even reading previously freed
2868
** memory might result in a segmentation fault or other severe error.
2869
** Memory corruption, a segmentation fault, or other severe error
2870
** might result if sqlite3_free() is called with a non-NULL pointer that
2871
** was not obtained from sqlite3_malloc() or sqlite3_realloc().
2872
**
2873
** ^The sqlite3_realloc(X,N) interface attempts to resize a
2874
** prior memory allocation X to be at least N bytes.
2875
** ^If the X parameter to sqlite3_realloc(X,N)
2876
** is a NULL pointer then its behavior is identical to calling
2877
** sqlite3_malloc(N).
2878
** ^If the N parameter to sqlite3_realloc(X,N) is zero or
2879
** negative then the behavior is exactly the same as calling
2880
** sqlite3_free(X).
2881
** ^sqlite3_realloc(X,N) returns a pointer to a memory allocation
2882
** of at least N bytes in size or NULL if insufficient memory is available.
2883
** ^If M is the size of the prior allocation, then min(N,M) bytes
2884
** of the prior allocation are copied into the beginning of buffer returned
2885
** by sqlite3_realloc(X,N) and the prior allocation is freed.
2886
** ^If sqlite3_realloc(X,N) returns NULL and N is positive, then the
2887
** prior allocation is not freed.
2888
**
2889
** ^The sqlite3_realloc64(X,N) interfaces works the same as
2890
** sqlite3_realloc(X,N) except that N is a 64-bit unsigned integer instead
2891
** of a 32-bit signed integer.
2892
**
2893
** ^If X is a memory allocation previously obtained from sqlite3_malloc(),
2894
** sqlite3_malloc64(), sqlite3_realloc(), or sqlite3_realloc64(), then
2895
** sqlite3_msize(X) returns the size of that memory allocation in bytes.
2896
** ^The value returned by sqlite3_msize(X) might be larger than the number
2897
** of bytes requested when X was allocated.  ^If X is a NULL pointer then
2898
** sqlite3_msize(X) returns zero.  If X points to something that is not
2899
** the beginning of memory allocation, or if it points to a formerly
2900
** valid memory allocation that has now been freed, then the behavior
2901
** of sqlite3_msize(X) is undefined and possibly harmful.
2902
**
2903
** ^The memory returned by sqlite3_malloc(), sqlite3_realloc(),
2904
** sqlite3_malloc64(), and sqlite3_realloc64()
2905
** is always aligned to at least an 8 byte boundary, or to a
2906
** 4 byte boundary if the [SQLITE_4_BYTE_ALIGNED_MALLOC] compile-time
2907
** option is used.
2908
**
2909
** The pointer arguments to [sqlite3_free()] and [sqlite3_realloc()]
2910
** must be either NULL or else pointers obtained from a prior
2911
** invocation of [sqlite3_malloc()] or [sqlite3_realloc()] that have
2912
** not yet been released.
2913
**
2914
** The application must not read or write any part of
2915
** a block of memory after it has been released using
2916
** [sqlite3_free()] or [sqlite3_realloc()].
2917
*/
2918
SQLITE_API void *sqlite3_malloc(int);
2919
SQLITE_API void *sqlite3_malloc64(sqlite3_uint64);
2920
SQLITE_API void *sqlite3_realloc(void*, int);
2921
SQLITE_API void *sqlite3_realloc64(void*, sqlite3_uint64);
2922
SQLITE_API void sqlite3_free(void*);
2923
SQLITE_API sqlite3_uint64 sqlite3_msize(void*);
2924
2925
/*
2926
** CAPI3REF: Memory Allocator Statistics
2927
**
2928
** SQLite provides these two interfaces for reporting on the status
2929
** of the [sqlite3_malloc()], [sqlite3_free()], and [sqlite3_realloc()]
2930
** routines, which form the built-in memory allocation subsystem.
2931
**
2932
** ^The [sqlite3_memory_used()] routine returns the number of bytes
2933
** of memory currently outstanding (malloced but not freed).
2934
** ^The [sqlite3_memory_highwater()] routine returns the maximum
2935
** value of [sqlite3_memory_used()] since the high-water mark
2936
** was last reset.  ^The values returned by [sqlite3_memory_used()] and
2937
** [sqlite3_memory_highwater()] include any overhead
2938
** added by SQLite in its implementation of [sqlite3_malloc()],
2939
** but not overhead added by the any underlying system library
2940
** routines that [sqlite3_malloc()] may call.
2941
**
2942
** ^The memory high-water mark is reset to the current value of
2943
** [sqlite3_memory_used()] if and only if the parameter to
2944
** [sqlite3_memory_highwater()] is true.  ^The value returned
2945
** by [sqlite3_memory_highwater(1)] is the high-water mark
2946
** prior to the reset.
2947
*/
2948
SQLITE_API sqlite3_int64 sqlite3_memory_used(void);
2949
SQLITE_API sqlite3_int64 sqlite3_memory_highwater(int resetFlag);
2950
2951
/*
2952
** CAPI3REF: Pseudo-Random Number Generator
2953
**
2954
** SQLite contains a high-quality pseudo-random number generator (PRNG) used to
2955
** select random [ROWID | ROWIDs] when inserting new records into a table that
2956
** already uses the largest possible [ROWID].  The PRNG is also used for
2957
** the built-in random() and randomblob() SQL functions.  This interface allows
2958
** applications to access the same PRNG for other purposes.
2959
**
2960
** ^A call to this routine stores N bytes of randomness into buffer P.
2961
** ^The P parameter can be a NULL pointer.
2962
**
2963
** ^If this routine has not been previously called or if the previous
2964
** call had N less than one or a NULL pointer for P, then the PRNG is
2965
** seeded using randomness obtained from the xRandomness method of
2966
** the default [sqlite3_vfs] object.
2967
** ^If the previous call to this routine had an N of 1 or more and a
2968
** non-NULL P then the pseudo-randomness is generated
2969
** internally and without recourse to the [sqlite3_vfs] xRandomness
2970
** method.
2971
*/
2972
SQLITE_API void sqlite3_randomness(int N, void *P);
2973
2974
/*
2975
** CAPI3REF: Compile-Time Authorization Callbacks
2976
** METHOD: sqlite3
2977
** KEYWORDS: {authorizer callback}
2978
**
2979
** ^This routine registers an authorizer callback with a particular
2980
** [database connection], supplied in the first argument.
2981
** ^The authorizer callback is invoked as SQL statements are being compiled
2982
** by [sqlite3_prepare()] or its variants [sqlite3_prepare_v2()],
2983
** [sqlite3_prepare_v3()], [sqlite3_prepare16()], [sqlite3_prepare16_v2()],
2984
** and [sqlite3_prepare16_v3()].  ^At various
2985
** points during the compilation process, as logic is being created
2986
** to perform various actions, the authorizer callback is invoked to
2987
** see if those actions are allowed.  ^The authorizer callback should
2988
** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the
2989
** specific action but allow the SQL statement to continue to be
2990
** compiled, or [SQLITE_DENY] to cause the entire SQL statement to be
2991
** rejected with an error.  ^If the authorizer callback returns
2992
** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY]
2993
** then the [sqlite3_prepare_v2()] or equivalent call that triggered
2994
** the authorizer will fail with an error message.
2995
**
2996
** When the callback returns [SQLITE_OK], that means the operation
2997
** requested is ok.  ^When the callback returns [SQLITE_DENY], the
2998
** [sqlite3_prepare_v2()] or equivalent call that triggered the
2999
** authorizer will fail with an error message explaining that
3000
** access is denied.
3001
**
3002
** ^The first parameter to the authorizer callback is a copy of the third
3003
** parameter to the sqlite3_set_authorizer() interface. ^The second parameter
3004
** to the callback is an integer [SQLITE_COPY | action code] that specifies
3005
** the particular action to be authorized. ^The third through sixth parameters
3006
** to the callback are either NULL pointers or zero-terminated strings
3007
** that contain additional details about the action to be authorized.
3008
** Applications must always be prepared to encounter a NULL pointer in any
3009
** of the third through the sixth parameters of the authorization callback.
3010
**
3011
** ^If the action code is [SQLITE_READ]
3012
** and the callback returns [SQLITE_IGNORE] then the
3013
** [prepared statement] statement is constructed to substitute
3014
** a NULL value in place of the table column that would have
3015
** been read if [SQLITE_OK] had been returned.  The [SQLITE_IGNORE]
3016
** return can be used to deny an untrusted user access to individual
3017
** columns of a table.
3018
** ^When a table is referenced by a [SELECT] but no column values are
3019
** extracted from that table (for example in a query like
3020
** "SELECT count(*) FROM tab") then the [SQLITE_READ] authorizer callback
3021
** is invoked once for that table with a column name that is an empty string.
3022
** ^If the action code is [SQLITE_DELETE] and the callback returns
3023
** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the
3024
** [truncate optimization] is disabled and all rows are deleted individually.
3025
**
3026
** An authorizer is used when [sqlite3_prepare | preparing]
3027
** SQL statements from an untrusted source, to ensure that the SQL statements
3028
** do not try to access data they are not allowed to see, or that they do not
3029
** try to execute malicious statements that damage the database.  For
3030
** example, an application may allow a user to enter arbitrary
3031
** SQL queries for evaluation by a database.  But the application does
3032
** not want the user to be able to make arbitrary changes to the
3033
** database.  An authorizer could then be put in place while the
3034
** user-entered SQL is being [sqlite3_prepare | prepared] that
3035
** disallows everything except [SELECT] statements.
3036
**
3037
** Applications that need to process SQL from untrusted sources
3038
** might also consider lowering resource limits using [sqlite3_limit()]
3039
** and limiting database size using the [max_page_count] [PRAGMA]
3040
** in addition to using an authorizer.
3041
**
3042
** ^(Only a single authorizer can be in place on a database connection
3043
** at a time.  Each call to sqlite3_set_authorizer overrides the
3044
** previous call.)^  ^Disable the authorizer by installing a NULL callback.
3045
** The authorizer is disabled by default.
3046
**
3047
** The authorizer callback must not do anything that will modify
3048
** the database connection that invoked the authorizer callback.
3049
** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
3050
** database connections for the meaning of "modify" in this paragraph.
3051
**
3052
** ^When [sqlite3_prepare_v2()] is used to prepare a statement, the
3053
** statement might be re-prepared during [sqlite3_step()] due to a
3054
** schema change.  Hence, the application should ensure that the
3055
** correct authorizer callback remains in place during the [sqlite3_step()].
3056
**
3057
** ^Note that the authorizer callback is invoked only during
3058
** [sqlite3_prepare()] or its variants.  Authorization is not
3059
** performed during statement evaluation in [sqlite3_step()], unless
3060
** as stated in the previous paragraph, sqlite3_step() invokes
3061
** sqlite3_prepare_v2() to reprepare a statement after a schema change.
3062
*/
3063
SQLITE_API int sqlite3_set_authorizer(
3064
  sqlite3*,
3065
  int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
3066
  void *pUserData
3067
);
3068
3069
/*
3070
** CAPI3REF: Authorizer Return Codes
3071
**
3072
** The [sqlite3_set_authorizer | authorizer callback function] must
3073
** return either [SQLITE_OK] or one of these two constants in order
3074
** to signal SQLite whether or not the action is permitted.  See the
3075
** [sqlite3_set_authorizer | authorizer documentation] for additional
3076
** information.
3077
**
3078
** Note that SQLITE_IGNORE is also used as a [conflict resolution mode]
3079
** returned from the [sqlite3_vtab_on_conflict()] interface.
3080
*/
3081
#define SQLITE_DENY   1   /* Abort the SQL statement with an error */
3082
#define SQLITE_IGNORE 2   /* Don't allow access, but don't generate an error */
3083
3084
/*
3085
** CAPI3REF: Authorizer Action Codes
3086
**
3087
** The [sqlite3_set_authorizer()] interface registers a callback function
3088
** that is invoked to authorize certain SQL statement actions.  The
3089
** second parameter to the callback is an integer code that specifies
3090
** what action is being authorized.  These are the integer action codes that
3091
** the authorizer callback may be passed.
3092
**
3093
** These action code values signify what kind of operation is to be
3094
** authorized.  The 3rd and 4th parameters to the authorization
3095
** callback function will be parameters or NULL depending on which of these
3096
** codes is used as the second parameter.  ^(The 5th parameter to the
3097
** authorizer callback is the name of the database ("main", "temp",
3098
** etc.) if applicable.)^  ^The 6th parameter to the authorizer callback
3099
** is the name of the inner-most trigger or view that is responsible for
3100
** the access attempt or NULL if this access attempt is directly from
3101
** top-level SQL code.
3102
*/
3103
/******************************************* 3rd ************ 4th ***********/
3104
#define SQLITE_CREATE_INDEX          1   /* Index Name      Table Name      */
3105
#define SQLITE_CREATE_TABLE          2   /* Table Name      NULL            */
3106
#define SQLITE_CREATE_TEMP_INDEX     3   /* Index Name      Table Name      */
3107
#define SQLITE_CREATE_TEMP_TABLE     4   /* Table Name      NULL            */
3108
#define SQLITE_CREATE_TEMP_TRIGGER   5   /* Trigger Name    Table Name      */
3109
#define SQLITE_CREATE_TEMP_VIEW      6   /* View Name       NULL            */
3110
#define SQLITE_CREATE_TRIGGER        7   /* Trigger Name    Table Name      */
3111
#define SQLITE_CREATE_VIEW           8   /* View Name       NULL            */
3112
#define SQLITE_DELETE                9   /* Table Name      NULL            */
3113
#define SQLITE_DROP_INDEX           10   /* Index Name      Table Name      */
3114
#define SQLITE_DROP_TABLE           11   /* Table Name      NULL            */
3115
#define SQLITE_DROP_TEMP_INDEX      12   /* Index Name      Table Name      */
3116
#define SQLITE_DROP_TEMP_TABLE      13   /* Table Name      NULL            */
3117
#define SQLITE_DROP_TEMP_TRIGGER    14   /* Trigger Name    Table Name      */
3118
#define SQLITE_DROP_TEMP_VIEW       15   /* View Name       NULL            */
3119
#define SQLITE_DROP_TRIGGER         16   /* Trigger Name    Table Name      */
3120
#define SQLITE_DROP_VIEW            17   /* View Name       NULL            */
3121
#define SQLITE_INSERT               18   /* Table Name      NULL            */
3122
#define SQLITE_PRAGMA               19   /* Pragma Name     1st arg or NULL */
3123
#define SQLITE_READ                 20   /* Table Name      Column Name     */
3124
#define SQLITE_SELECT               21   /* NULL            NULL            */
3125
#define SQLITE_TRANSACTION          22   /* Operation       NULL            */
3126
#define SQLITE_UPDATE               23   /* Table Name      Column Name     */
3127
#define SQLITE_ATTACH               24   /* Filename        NULL            */
3128
#define SQLITE_DETACH               25   /* Database Name   NULL            */
3129
#define SQLITE_ALTER_TABLE          26   /* Database Name   Table Name      */
3130
#define SQLITE_REINDEX              27   /* Index Name      NULL            */
3131
#define SQLITE_ANALYZE              28   /* Table Name      NULL            */
3132
#define SQLITE_CREATE_VTABLE        29   /* Table Name      Module Name     */
3133
#define SQLITE_DROP_VTABLE          30   /* Table Name      Module Name     */
3134
#define SQLITE_FUNCTION             31   /* NULL            Function Name   */
3135
#define SQLITE_SAVEPOINT            32   /* Operation       Savepoint Name  */
3136
#define SQLITE_COPY                  0   /* No longer used */
3137
#define SQLITE_RECURSIVE            33   /* NULL            NULL            */
3138
3139
/*
3140
** CAPI3REF: Tracing And Profiling Functions
3141
** METHOD: sqlite3
3142
**
3143
** These routines are deprecated. Use the [sqlite3_trace_v2()] interface
3144
** instead of the routines described here.
3145
**
3146
** These routines register callback functions that can be used for
3147
** tracing and profiling the execution of SQL statements.
3148
**
3149
** ^The callback function registered by sqlite3_trace() is invoked at
3150
** various times when an SQL statement is being run by [sqlite3_step()].
3151
** ^The sqlite3_trace() callback is invoked with a UTF-8 rendering of the
3152
** SQL statement text as the statement first begins executing.
3153
** ^(Additional sqlite3_trace() callbacks might occur
3154
** as each triggered subprogram is entered.  The callbacks for triggers
3155
** contain a UTF-8 SQL comment that identifies the trigger.)^
3156
**
3157
** The [SQLITE_TRACE_SIZE_LIMIT] compile-time option can be used to limit
3158
** the length of [bound parameter] expansion in the output of sqlite3_trace().
3159
**
3160
** ^The callback function registered by sqlite3_profile() is invoked
3161
** as each SQL statement finishes.  ^The profile callback contains
3162
** the original statement text and an estimate of wall-clock time
3163
** of how long that statement took to run.  ^The profile callback
3164
** time is in units of nanoseconds, however the current implementation
3165
** is only capable of millisecond resolution so the six least significant
3166
** digits in the time are meaningless.  Future versions of SQLite
3167
** might provide greater resolution on the profiler callback.  Invoking
3168
** either [sqlite3_trace()] or [sqlite3_trace_v2()] will cancel the
3169
** profile callback.
3170
*/
3171
SQLITE_API SQLITE_DEPRECATED void *sqlite3_trace(sqlite3*,
3172
   void(*xTrace)(void*,const char*), void*);
3173
SQLITE_API SQLITE_DEPRECATED void *sqlite3_profile(sqlite3*,
3174
   void(*xProfile)(void*,const char*,sqlite3_uint64), void*);
3175
3176
/*
3177
** CAPI3REF: SQL Trace Event Codes
3178
** KEYWORDS: SQLITE_TRACE
3179
**
3180
** These constants identify classes of events that can be monitored
3181
** using the [sqlite3_trace_v2()] tracing logic.  The M argument
3182
** to [sqlite3_trace_v2(D,M,X,P)] is an OR-ed combination of one or more of
3183
** the following constants.  ^The first argument to the trace callback
3184
** is one of the following constants.
3185
**
3186
** New tracing constants may be added in future releases.
3187
**
3188
** ^A trace callback has four arguments: xCallback(T,C,P,X).
3189
** ^The T argument is one of the integer type codes above.
3190
** ^The C argument is a copy of the context pointer passed in as the
3191
** fourth argument to [sqlite3_trace_v2()].
3192
** The P and X arguments are pointers whose meanings depend on T.
3193
**
3194
** <dl>
3195
** [[SQLITE_TRACE_STMT]] <dt>SQLITE_TRACE_STMT</dt>
3196
** <dd>^An SQLITE_TRACE_STMT callback is invoked when a prepared statement
3197
** first begins running and possibly at other times during the
3198
** execution of the prepared statement, such as at the start of each
3199
** trigger subprogram. ^The P argument is a pointer to the
3200
** [prepared statement]. ^The X argument is a pointer to a string which
3201
** is the unexpanded SQL text of the prepared statement or an SQL comment
3202
** that indicates the invocation of a trigger.  ^The callback can compute
3203
** the same text that would have been returned by the legacy [sqlite3_trace()]
3204
** interface by using the X argument when X begins with "--" and invoking
3205
** [sqlite3_expanded_sql(P)] otherwise.
3206
**
3207
** [[SQLITE_TRACE_PROFILE]] <dt>SQLITE_TRACE_PROFILE</dt>
3208
** <dd>^An SQLITE_TRACE_PROFILE callback provides approximately the same
3209
** information as is provided by the [sqlite3_profile()] callback.
3210
** ^The P argument is a pointer to the [prepared statement] and the
3211
** X argument points to a 64-bit integer which is the estimated of
3212
** the number of nanosecond that the prepared statement took to run.
3213
** ^The SQLITE_TRACE_PROFILE callback is invoked when the statement finishes.
3214
**
3215
** [[SQLITE_TRACE_ROW]] <dt>SQLITE_TRACE_ROW</dt>
3216
** <dd>^An SQLITE_TRACE_ROW callback is invoked whenever a prepared
3217
** statement generates a single row of result.
3218
** ^The P argument is a pointer to the [prepared statement] and the
3219
** X argument is unused.
3220
**
3221
** [[SQLITE_TRACE_CLOSE]] <dt>SQLITE_TRACE_CLOSE</dt>
3222
** <dd>^An SQLITE_TRACE_CLOSE callback is invoked when a database
3223
** connection closes.
3224
** ^The P argument is a pointer to the [database connection] object
3225
** and the X argument is unused.
3226
** </dl>
3227
*/
3228
#define SQLITE_TRACE_STMT       0x01
3229
#define SQLITE_TRACE_PROFILE    0x02
3230
#define SQLITE_TRACE_ROW        0x04
3231
#define SQLITE_TRACE_CLOSE      0x08
3232
3233
/*
3234
** CAPI3REF: SQL Trace Hook
3235
** METHOD: sqlite3
3236
**
3237
** ^The sqlite3_trace_v2(D,M,X,P) interface registers a trace callback
3238
** function X against [database connection] D, using property mask M
3239
** and context pointer P.  ^If the X callback is
3240
** NULL or if the M mask is zero, then tracing is disabled.  The
3241
** M argument should be the bitwise OR-ed combination of
3242
** zero or more [SQLITE_TRACE] constants.
3243
**
3244
** ^Each call to either sqlite3_trace() or sqlite3_trace_v2() overrides
3245
** (cancels) any prior calls to sqlite3_trace() or sqlite3_trace_v2().
3246
**
3247
** ^The X callback is invoked whenever any of the events identified by
3248
** mask M occur.  ^The integer return value from the callback is currently
3249
** ignored, though this may change in future releases.  Callback
3250
** implementations should return zero to ensure future compatibility.
3251
**
3252
** ^A trace callback is invoked with four arguments: callback(T,C,P,X).
3253
** ^The T argument is one of the [SQLITE_TRACE]
3254
** constants to indicate why the callback was invoked.
3255
** ^The C argument is a copy of the context pointer.
3256
** The P and X arguments are pointers whose meanings depend on T.
3257
**
3258
** The sqlite3_trace_v2() interface is intended to replace the legacy
3259
** interfaces [sqlite3_trace()] and [sqlite3_profile()], both of which
3260
** are deprecated.
3261
*/
3262
SQLITE_API int sqlite3_trace_v2(
3263
  sqlite3*,
3264
  unsigned uMask,
3265
  int(*xCallback)(unsigned,void*,void*,void*),
3266
  void *pCtx
3267
);
3268
3269
/*
3270
** CAPI3REF: Query Progress Callbacks
3271
** METHOD: sqlite3
3272
**
3273
** ^The sqlite3_progress_handler(D,N,X,P) interface causes the callback
3274
** function X to be invoked periodically during long running calls to
3275
** [sqlite3_exec()], [sqlite3_step()] and [sqlite3_get_table()] for
3276
** database connection D.  An example use for this
3277
** interface is to keep a GUI updated during a large query.
3278
**
3279
** ^The parameter P is passed through as the only parameter to the
3280
** callback function X.  ^The parameter N is the approximate number of
3281
** [virtual machine instructions] that are evaluated between successive
3282
** invocations of the callback X.  ^If N is less than one then the progress
3283
** handler is disabled.
3284
**
3285
** ^Only a single progress handler may be defined at one time per
3286
** [database connection]; setting a new progress handler cancels the
3287
** old one.  ^Setting parameter X to NULL disables the progress handler.
3288
** ^The progress handler is also disabled by setting N to a value less
3289
** than 1.
3290
**
3291
** ^If the progress callback returns non-zero, the operation is
3292
** interrupted.  This feature can be used to implement a
3293
** "Cancel" button on a GUI progress dialog box.
3294
**
3295
** The progress handler callback must not do anything that will modify
3296
** the database connection that invoked the progress handler.
3297
** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
3298
** database connections for the meaning of "modify" in this paragraph.
3299
**
3300
*/
3301
SQLITE_API void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
3302
3303
/*
3304
** CAPI3REF: Opening A New Database Connection
3305
** CONSTRUCTOR: sqlite3
3306
**
3307
** ^These routines open an SQLite database file as specified by the
3308
** filename argument. ^The filename argument is interpreted as UTF-8 for
3309
** sqlite3_open() and sqlite3_open_v2() and as UTF-16 in the native byte
3310
** order for sqlite3_open16(). ^(A [database connection] handle is usually
3311
** returned in *ppDb, even if an error occurs.  The only exception is that
3312
** if SQLite is unable to allocate memory to hold the [sqlite3] object,
3313
** a NULL will be written into *ppDb instead of a pointer to the [sqlite3]
3314
** object.)^ ^(If the database is opened (and/or created) successfully, then
3315
** [SQLITE_OK] is returned.  Otherwise an [error code] is returned.)^ ^The
3316
** [sqlite3_errmsg()] or [sqlite3_errmsg16()] routines can be used to obtain
3317
** an English language description of the error following a failure of any
3318
** of the sqlite3_open() routines.
3319
**
3320
** ^The default encoding will be UTF-8 for databases created using
3321
** sqlite3_open() or sqlite3_open_v2().  ^The default encoding for databases
3322
** created using sqlite3_open16() will be UTF-16 in the native byte order.
3323
**
3324
** Whether or not an error occurs when it is opened, resources
3325
** associated with the [database connection] handle should be released by
3326
** passing it to [sqlite3_close()] when it is no longer required.
3327
**
3328
** The sqlite3_open_v2() interface works like sqlite3_open()
3329
** except that it accepts two additional parameters for additional control
3330
** over the new database connection.  ^(The flags parameter to
3331
** sqlite3_open_v2() must include, at a minimum, one of the following
3332
** three flag combinations:)^
3333
**
3334
** <dl>
3335
** ^(<dt>[SQLITE_OPEN_READONLY]</dt>
3336
** <dd>The database is opened in read-only mode.  If the database does not
3337
** already exist, an error is returned.</dd>)^
3338
**
3339
** ^(<dt>[SQLITE_OPEN_READWRITE]</dt>
3340
** <dd>The database is opened for reading and writing if possible, or reading
3341
** only if the file is write protected by the operating system.  In either
3342
** case the database must already exist, otherwise an error is returned.</dd>)^
3343
**
3344
** ^(<dt>[SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE]</dt>
3345
** <dd>The database is opened for reading and writing, and is created if
3346
** it does not already exist. This is the behavior that is always used for
3347
** sqlite3_open() and sqlite3_open16().</dd>)^
3348
** </dl>
3349
**
3350
** In addition to the required flags, the following optional flags are
3351
** also supported:
3352
**
3353
** <dl>
3354
** ^(<dt>[SQLITE_OPEN_URI]</dt>
3355
** <dd>The filename can be interpreted as a URI if this flag is set.</dd>)^
3356
**
3357
** ^(<dt>[SQLITE_OPEN_MEMORY]</dt>
3358
** <dd>The database will be opened as an in-memory database.  The database
3359
** is named by the "filename" argument for the purposes of cache-sharing,
3360
** if shared cache mode is enabled, but the "filename" is otherwise ignored.
3361
** </dd>)^
3362
**
3363
** ^(<dt>[SQLITE_OPEN_NOMUTEX]</dt>
3364
** <dd>The new database connection will use the "multi-thread"
3365
** [threading mode].)^  This means that separate threads are allowed
3366
** to use SQLite at the same time, as long as each thread is using
3367
** a different [database connection].
3368
**
3369
** ^(<dt>[SQLITE_OPEN_FULLMUTEX]</dt>
3370
** <dd>The new database connection will use the "serialized"
3371
** [threading mode].)^  This means the multiple threads can safely
3372
** attempt to use the same database connection at the same time.
3373
** (Mutexes will block any actual concurrency, but in this mode
3374
** there is no harm in trying.)
3375
**
3376
** ^(<dt>[SQLITE_OPEN_SHAREDCACHE]</dt>
3377
** <dd>The database is opened [shared cache] enabled, overriding
3378
** the default shared cache setting provided by
3379
** [sqlite3_enable_shared_cache()].)^
3380
**
3381
** ^(<dt>[SQLITE_OPEN_PRIVATECACHE]</dt>
3382
** <dd>The database is opened [shared cache] disabled, overriding
3383
** the default shared cache setting provided by
3384
** [sqlite3_enable_shared_cache()].)^
3385
**
3386
** [[OPEN_NOFOLLOW]] ^(<dt>[SQLITE_OPEN_NOFOLLOW]</dt>
3387
** <dd>The database filename is not allowed to be a symbolic link</dd>
3388
** </dl>)^
3389
**
3390
** If the 3rd parameter to sqlite3_open_v2() is not one of the
3391
** required combinations shown above optionally combined with other
3392
** [SQLITE_OPEN_READONLY | SQLITE_OPEN_* bits]
3393
** then the behavior is undefined.
3394
**
3395
** ^The fourth parameter to sqlite3_open_v2() is the name of the
3396
** [sqlite3_vfs] object that defines the operating system interface that
3397
** the new database connection should use.  ^If the fourth parameter is
3398
** a NULL pointer then the default [sqlite3_vfs] object is used.
3399
**
3400
** ^If the filename is ":memory:", then a private, temporary in-memory database
3401
** is created for the connection.  ^This in-memory database will vanish when
3402
** the database connection is closed.  Future versions of SQLite might
3403
** make use of additional special filenames that begin with the ":" character.
3404
** It is recommended that when a database filename actually does begin with
3405
** a ":" character you should prefix the filename with a pathname such as
3406
** "./" to avoid ambiguity.
3407
**
3408
** ^If the filename is an empty string, then a private, temporary
3409
** on-disk database will be created.  ^This private database will be
3410
** automatically deleted as soon as the database connection is closed.
3411
**
3412
** [[URI filenames in sqlite3_open()]] <h3>URI Filenames</h3>
3413
**
3414
** ^If [URI filename] interpretation is enabled, and the filename argument
3415
** begins with "file:", then the filename is interpreted as a URI. ^URI
3416
** filename interpretation is enabled if the [SQLITE_OPEN_URI] flag is
3417
** set in the third argument to sqlite3_open_v2(), or if it has
3418
** been enabled globally using the [SQLITE_CONFIG_URI] option with the
3419
** [sqlite3_config()] method or by the [SQLITE_USE_URI] compile-time option.
3420
** URI filename interpretation is turned off
3421
** by default, but future releases of SQLite might enable URI filename
3422
** interpretation by default.  See "[URI filenames]" for additional
3423
** information.
3424
**
3425
** URI filenames are parsed according to RFC 3986. ^If the URI contains an
3426
** authority, then it must be either an empty string or the string
3427
** "localhost". ^If the authority is not an empty string or "localhost", an
3428
** error is returned to the caller. ^The fragment component of a URI, if
3429
** present, is ignored.
3430
**
3431
** ^SQLite uses the path component of the URI as the name of the disk file
3432
** which contains the database. ^If the path begins with a '/' character,
3433
** then it is interpreted as an absolute path. ^If the path does not begin
3434
** with a '/' (meaning that the authority section is omitted from the URI)
3435
** then the path is interpreted as a relative path.
3436
** ^(On windows, the first component of an absolute path
3437
** is a drive specification (e.g. "C:").)^
3438
**
3439
** [[core URI query parameters]]
3440
** The query component of a URI may contain parameters that are interpreted
3441
** either by SQLite itself, or by a [VFS | custom VFS implementation].
3442
** SQLite and its built-in [VFSes] interpret the
3443
** following query parameters:
3444
**
3445
** <ul>
3446
**   <li> <b>vfs</b>: ^The "vfs" parameter may be used to specify the name of
3447
**     a VFS object that provides the operating system interface that should
3448
**     be used to access the database file on disk. ^If this option is set to
3449
**     an empty string the default VFS object is used. ^Specifying an unknown
3450
**     VFS is an error. ^If sqlite3_open_v2() is used and the vfs option is
3451
**     present, then the VFS specified by the option takes precedence over
3452
**     the value passed as the fourth parameter to sqlite3_open_v2().
3453
**
3454
**   <li> <b>mode</b>: ^(The mode parameter may be set to either "ro", "rw",
3455
**     "rwc", or "memory". Attempting to set it to any other value is
3456
**     an error)^.
3457
**     ^If "ro" is specified, then the database is opened for read-only
3458
**     access, just as if the [SQLITE_OPEN_READONLY] flag had been set in the
3459
**     third argument to sqlite3_open_v2(). ^If the mode option is set to
3460
**     "rw", then the database is opened for read-write (but not create)
3461
**     access, as if SQLITE_OPEN_READWRITE (but not SQLITE_OPEN_CREATE) had
3462
**     been set. ^Value "rwc" is equivalent to setting both
3463
**     SQLITE_OPEN_READWRITE and SQLITE_OPEN_CREATE.  ^If the mode option is
3464
**     set to "memory" then a pure [in-memory database] that never reads
3465
**     or writes from disk is used. ^It is an error to specify a value for
3466
**     the mode parameter that is less restrictive than that specified by
3467
**     the flags passed in the third parameter to sqlite3_open_v2().
3468
**
3469
**   <li> <b>cache</b>: ^The cache parameter may be set to either "shared" or
3470
**     "private". ^Setting it to "shared" is equivalent to setting the
3471
**     SQLITE_OPEN_SHAREDCACHE bit in the flags argument passed to
3472
**     sqlite3_open_v2(). ^Setting the cache parameter to "private" is
3473
**     equivalent to setting the SQLITE_OPEN_PRIVATECACHE bit.
3474
**     ^If sqlite3_open_v2() is used and the "cache" parameter is present in
3475
**     a URI filename, its value overrides any behavior requested by setting
3476
**     SQLITE_OPEN_PRIVATECACHE or SQLITE_OPEN_SHAREDCACHE flag.
3477
**
3478
**  <li> <b>psow</b>: ^The psow parameter indicates whether or not the
3479
**     [powersafe overwrite] property does or does not apply to the
3480
**     storage media on which the database file resides.
3481
**
3482
**  <li> <b>nolock</b>: ^The nolock parameter is a boolean query parameter
3483
**     which if set disables file locking in rollback journal modes.  This
3484
**     is useful for accessing a database on a filesystem that does not
3485
**     support locking.  Caution:  Database corruption might result if two
3486
**     or more processes write to the same database and any one of those
3487
**     processes uses nolock=1.
3488
**
3489
**  <li> <b>immutable</b>: ^The immutable parameter is a boolean query
3490
**     parameter that indicates that the database file is stored on
3491
**     read-only media.  ^When immutable is set, SQLite assumes that the
3492
**     database file cannot be changed, even by a process with higher
3493
**     privilege, and so the database is opened read-only and all locking
3494
**     and change detection is disabled.  Caution: Setting the immutable
3495
**     property on a database file that does in fact change can result
3496
**     in incorrect query results and/or [SQLITE_CORRUPT] errors.
3497
**     See also: [SQLITE_IOCAP_IMMUTABLE].
3498
**
3499
** </ul>
3500
**
3501
** ^Specifying an unknown parameter in the query component of a URI is not an
3502
** error.  Future versions of SQLite might understand additional query
3503
** parameters.  See "[query parameters with special meaning to SQLite]" for
3504
** additional information.
3505
**
3506
** [[URI filename examples]] <h3>URI filename examples</h3>
3507
**
3508
** <table border="1" align=center cellpadding=5>
3509
** <tr><th> URI filenames <th> Results
3510
** <tr><td> file:data.db <td>
3511
**          Open the file "data.db" in the current directory.
3512
** <tr><td> file:/home/fred/data.db<br>
3513
**          file:///home/fred/data.db <br>
3514
**          file://localhost/home/fred/data.db <br> <td>
3515
**          Open the database file "/home/fred/data.db".
3516
** <tr><td> file://darkstar/home/fred/data.db <td>
3517
**          An error. "darkstar" is not a recognized authority.
3518
** <tr><td style="white-space:nowrap">
3519
**          file:///C:/Documents%20and%20Settings/fred/Desktop/data.db
3520
**     <td> Windows only: Open the file "data.db" on fred's desktop on drive
3521
**          C:. Note that the %20 escaping in this example is not strictly
3522
**          necessary - space characters can be used literally
3523
**          in URI filenames.
3524
** <tr><td> file:data.db?mode=ro&cache=private <td>
3525
**          Open file "data.db" in the current directory for read-only access.
3526
**          Regardless of whether or not shared-cache mode is enabled by
3527
**          default, use a private cache.
3528
** <tr><td> file:/home/fred/data.db?vfs=unix-dotfile <td>
3529
**          Open file "/home/fred/data.db". Use the special VFS "unix-dotfile"
3530
**          that uses dot-files in place of posix advisory locking.
3531
** <tr><td> file:data.db?mode=readonly <td>
3532
**          An error. "readonly" is not a valid option for the "mode" parameter.
3533
**          Use "ro" instead:  "file:data.db?mode=ro".
3534
** </table>
3535
**
3536
** ^URI hexadecimal escape sequences (%HH) are supported within the path and
3537
** query components of a URI. A hexadecimal escape sequence consists of a
3538
** percent sign - "%" - followed by exactly two hexadecimal digits
3539
** specifying an octet value. ^Before the path or query components of a
3540
** URI filename are interpreted, they are encoded using UTF-8 and all
3541
** hexadecimal escape sequences replaced by a single byte containing the
3542
** corresponding octet. If this process generates an invalid UTF-8 encoding,
3543
** the results are undefined.
3544
**
3545
** <b>Note to Windows users:</b>  The encoding used for the filename argument
3546
** of sqlite3_open() and sqlite3_open_v2() must be UTF-8, not whatever
3547
** codepage is currently defined.  Filenames containing international
3548
** characters must be converted to UTF-8 prior to passing them into
3549
** sqlite3_open() or sqlite3_open_v2().
3550
**
3551
** <b>Note to Windows Runtime users:</b>  The temporary directory must be set
3552
** prior to calling sqlite3_open() or sqlite3_open_v2().  Otherwise, various
3553
** features that require the use of temporary files may fail.
3554
**
3555
** See also: [sqlite3_temp_directory]
3556
*/
3557
SQLITE_API int sqlite3_open(
3558
  const char *filename,   /* Database filename (UTF-8) */
3559
  sqlite3 **ppDb          /* OUT: SQLite db handle */
3560
);
3561
SQLITE_API int sqlite3_open16(
3562
  const void *filename,   /* Database filename (UTF-16) */
3563
  sqlite3 **ppDb          /* OUT: SQLite db handle */
3564
);
3565
SQLITE_API int sqlite3_open_v2(
3566
  const char *filename,   /* Database filename (UTF-8) */
3567
  sqlite3 **ppDb,         /* OUT: SQLite db handle */
3568
  int flags,              /* Flags */
3569
  const char *zVfs        /* Name of VFS module to use */
3570
);
3571
3572
/*
3573
** CAPI3REF: Obtain Values For URI Parameters
3574
**
3575
** These are utility routines, useful to [VFS|custom VFS implementations],
3576
** that check if a database file was a URI that contained a specific query
3577
** parameter, and if so obtains the value of that query parameter.
3578
**
3579
** The first parameter to these interfaces (hereafter referred to
3580
** as F) must be one of:
3581
** <ul>
3582
** <li> A database filename pointer created by the SQLite core and
3583
** passed into the xOpen() method of a VFS implemention, or
3584
** <li> A filename obtained from [sqlite3_db_filename()], or
3585
** <li> A new filename constructed using [sqlite3_create_filename()].
3586
** </ul>
3587
** If the F parameter is not one of the above, then the behavior is
3588
** undefined and probably undesirable.  Older versions of SQLite were
3589
** more tolerant of invalid F parameters than newer versions.
3590
**
3591
** If F is a suitable filename (as described in the previous paragraph)
3592
** and if P is the name of the query parameter, then
3593
** sqlite3_uri_parameter(F,P) returns the value of the P
3594
** parameter if it exists or a NULL pointer if P does not appear as a
3595
** query parameter on F.  If P is a query parameter of F and it
3596
** has no explicit value, then sqlite3_uri_parameter(F,P) returns
3597
** a pointer to an empty string.
3598
**
3599
** The sqlite3_uri_boolean(F,P,B) routine assumes that P is a boolean
3600
** parameter and returns true (1) or false (0) according to the value
3601
** of P.  The sqlite3_uri_boolean(F,P,B) routine returns true (1) if the
3602
** value of query parameter P is one of "yes", "true", or "on" in any
3603
** case or if the value begins with a non-zero number.  The
3604
** sqlite3_uri_boolean(F,P,B) routines returns false (0) if the value of
3605
** query parameter P is one of "no", "false", or "off" in any case or
3606
** if the value begins with a numeric zero.  If P is not a query
3607
** parameter on F or if the value of P does not match any of the
3608
** above, then sqlite3_uri_boolean(F,P,B) returns (B!=0).
3609
**
3610
** The sqlite3_uri_int64(F,P,D) routine converts the value of P into a
3611
** 64-bit signed integer and returns that integer, or D if P does not
3612
** exist.  If the value of P is something other than an integer, then
3613
** zero is returned.
3614
**
3615
** The sqlite3_uri_key(F,N) returns a pointer to the name (not
3616
** the value) of the N-th query parameter for filename F, or a NULL
3617
** pointer if N is less than zero or greater than the number of query
3618
** parameters minus 1.  The N value is zero-based so N should be 0 to obtain
3619
** the name of the first query parameter, 1 for the second parameter, and
3620
** so forth.
3621
**
3622
** If F is a NULL pointer, then sqlite3_uri_parameter(F,P) returns NULL and
3623
** sqlite3_uri_boolean(F,P,B) returns B.  If F is not a NULL pointer and
3624
** is not a database file pathname pointer that the SQLite core passed
3625
** into the xOpen VFS method, then the behavior of this routine is undefined
3626
** and probably undesirable.
3627
**
3628
** Beginning with SQLite [version 3.31.0] ([dateof:3.31.0]) the input F
3629
** parameter can also be the name of a rollback journal file or WAL file
3630
** in addition to the main database file.  Prior to version 3.31.0, these
3631
** routines would only work if F was the name of the main database file.
3632
** When the F parameter is the name of the rollback journal or WAL file,
3633
** it has access to all the same query parameters as were found on the
3634
** main database file.
3635
**
3636
** See the [URI filename] documentation for additional information.
3637
*/
3638
SQLITE_API const char *sqlite3_uri_parameter(const char *zFilename, const char *zParam);
3639
SQLITE_API int sqlite3_uri_boolean(const char *zFile, const char *zParam, int bDefault);
3640
SQLITE_API sqlite3_int64 sqlite3_uri_int64(const char*, const char*, sqlite3_int64);
3641
SQLITE_API const char *sqlite3_uri_key(const char *zFilename, int N);
3642
3643
/*
3644
** CAPI3REF:  Translate filenames
3645
**
3646
** These routines are available to [VFS|custom VFS implementations] for
3647
** translating filenames between the main database file, the journal file,
3648
** and the WAL file.
3649
**
3650
** If F is the name of an sqlite database file, journal file, or WAL file
3651
** passed by the SQLite core into the VFS, then sqlite3_filename_database(F)
3652
** returns the name of the corresponding database file.
3653
**
3654
** If F is the name of an sqlite database file, journal file, or WAL file
3655
** passed by the SQLite core into the VFS, or if F is a database filename
3656
** obtained from [sqlite3_db_filename()], then sqlite3_filename_journal(F)
3657
** returns the name of the corresponding rollback journal file.
3658
**
3659
** If F is the name of an sqlite database file, journal file, or WAL file
3660
** that was passed by the SQLite core into the VFS, or if F is a database
3661
** filename obtained from [sqlite3_db_filename()], then
3662
** sqlite3_filename_wal(F) returns the name of the corresponding
3663
** WAL file.
3664
**
3665
** In all of the above, if F is not the name of a database, journal or WAL
3666
** filename passed into the VFS from the SQLite core and F is not the
3667
** return value from [sqlite3_db_filename()], then the result is
3668
** undefined and is likely a memory access violation.
3669
*/
3670
SQLITE_API const char *sqlite3_filename_database(const char*);
3671
SQLITE_API const char *sqlite3_filename_journal(const char*);
3672
SQLITE_API const char *sqlite3_filename_wal(const char*);
3673
3674
/*
3675
** CAPI3REF:  Database File Corresponding To A Journal
3676
**
3677
** ^If X is the name of a rollback or WAL-mode journal file that is
3678
** passed into the xOpen method of [sqlite3_vfs], then
3679
** sqlite3_database_file_object(X) returns a pointer to the [sqlite3_file]
3680
** object that represents the main database file.
3681
**
3682
** This routine is intended for use in custom [VFS] implementations
3683
** only.  It is not a general-purpose interface.
3684
** The argument sqlite3_file_object(X) must be a filename pointer that
3685
** has been passed into [sqlite3_vfs].xOpen method where the
3686
** flags parameter to xOpen contains one of the bits
3687
** [SQLITE_OPEN_MAIN_JOURNAL] or [SQLITE_OPEN_WAL].  Any other use
3688
** of this routine results in undefined and probably undesirable
3689
** behavior.
3690
*/
3691
SQLITE_API sqlite3_file *sqlite3_database_file_object(const char*);
3692
3693
/*
3694
** CAPI3REF: Create and Destroy VFS Filenames
3695
**
3696
** These interfces are provided for use by [VFS shim] implementations and
3697
** are not useful outside of that context.
3698
**
3699
** The sqlite3_create_filename(D,J,W,N,P) allocates memory to hold a version of
3700
** database filename D with corresponding journal file J and WAL file W and
3701
** with N URI parameters key/values pairs in the array P.  The result from
3702
** sqlite3_create_filename(D,J,W,N,P) is a pointer to a database filename that
3703
** is safe to pass to routines like:
3704
** <ul>
3705
** <li> [sqlite3_uri_parameter()],
3706
** <li> [sqlite3_uri_boolean()],
3707
** <li> [sqlite3_uri_int64()],
3708
** <li> [sqlite3_uri_key()],
3709
** <li> [sqlite3_filename_database()],
3710
** <li> [sqlite3_filename_journal()], or
3711
** <li> [sqlite3_filename_wal()].
3712
** </ul>
3713
** If a memory allocation error occurs, sqlite3_create_filename() might
3714
** return a NULL pointer.  The memory obtained from sqlite3_create_filename(X)
3715
** must be released by a corresponding call to sqlite3_free_filename(Y).
3716
**
3717
** The P parameter in sqlite3_create_filename(D,J,W,N,P) should be an array
3718
** of 2*N pointers to strings.  Each pair of pointers in this array corresponds
3719
** to a key and value for a query parameter.  The P parameter may be a NULL
3720
** pointer if N is zero.  None of the 2*N pointers in the P array may be
3721
** NULL pointers and key pointers should not be empty strings.
3722
** None of the D, J, or W parameters to sqlite3_create_filename(D,J,W,N,P) may
3723
** be NULL pointers, though they can be empty strings.
3724
**
3725
** The sqlite3_free_filename(Y) routine releases a memory allocation
3726
** previously obtained from sqlite3_create_filename().  Invoking
3727
** sqlite3_free_filename(Y) where Y is a NULL pointer is a harmless no-op.
3728
**
3729
** If the Y parameter to sqlite3_free_filename(Y) is anything other
3730
** than a NULL pointer or a pointer previously acquired from
3731
** sqlite3_create_filename(), then bad things such as heap
3732
** corruption or segfaults may occur. The value Y should not be
3733
** used again after sqlite3_free_filename(Y) has been called.  This means
3734
** that if the [sqlite3_vfs.xOpen()] method of a VFS has been called using Y,
3735
** then the corresponding [sqlite3_module.xClose() method should also be
3736
** invoked prior to calling sqlite3_free_filename(Y).
3737
*/
3738
SQLITE_API char *sqlite3_create_filename(
3739
  const char *zDatabase,
3740
  const char *zJournal,
3741
  const char *zWal,
3742
  int nParam,
3743
  const char **azParam
3744
);
3745
SQLITE_API void sqlite3_free_filename(char*);
3746
3747
/*
3748
** CAPI3REF: Error Codes And Messages
3749
** METHOD: sqlite3
3750
**
3751
** ^If the most recent sqlite3_* API call associated with
3752
** [database connection] D failed, then the sqlite3_errcode(D) interface
3753
** returns the numeric [result code] or [extended result code] for that
3754
** API call.
3755
** ^The sqlite3_extended_errcode()
3756
** interface is the same except that it always returns the
3757
** [extended result code] even when extended result codes are
3758
** disabled.
3759
**
3760
** The values returned by sqlite3_errcode() and/or
3761
** sqlite3_extended_errcode() might change with each API call.
3762
** Except, there are some interfaces that are guaranteed to never
3763
** change the value of the error code.  The error-code preserving
3764
** interfaces are:
3765
**
3766
** <ul>
3767
** <li> sqlite3_errcode()
3768
** <li> sqlite3_extended_errcode()
3769
** <li> sqlite3_errmsg()
3770
** <li> sqlite3_errmsg16()
3771
** </ul>
3772
**
3773
** ^The sqlite3_errmsg() and sqlite3_errmsg16() return English-language
3774
** text that describes the error, as either UTF-8 or UTF-16 respectively.
3775
** ^(Memory to hold the error message string is managed internally.
3776
** The application does not need to worry about freeing the result.
3777
** However, the error string might be overwritten or deallocated by
3778
** subsequent calls to other SQLite interface functions.)^
3779
**
3780
** ^The sqlite3_errstr() interface returns the English-language text
3781
** that describes the [result code], as UTF-8.
3782
** ^(Memory to hold the error message string is managed internally
3783
** and must not be freed by the application)^.
3784
**
3785
** When the serialized [threading mode] is in use, it might be the
3786
** case that a second error occurs on a separate thread in between
3787
** the time of the first error and the call to these interfaces.
3788
** When that happens, the second error will be reported since these
3789
** interfaces always report the most recent result.  To avoid
3790
** this, each thread can obtain exclusive use of the [database connection] D
3791
** by invoking [sqlite3_mutex_enter]([sqlite3_db_mutex](D)) before beginning
3792
** to use D and invoking [sqlite3_mutex_leave]([sqlite3_db_mutex](D)) after
3793
** all calls to the interfaces listed here are completed.
3794
**
3795
** If an interface fails with SQLITE_MISUSE, that means the interface
3796
** was invoked incorrectly by the application.  In that case, the
3797
** error code and message may or may not be set.
3798
*/
3799
SQLITE_API int sqlite3_errcode(sqlite3 *db);
3800
SQLITE_API int sqlite3_extended_errcode(sqlite3 *db);
3801
SQLITE_API const char *sqlite3_errmsg(sqlite3*);
3802
SQLITE_API const void *sqlite3_errmsg16(sqlite3*);
3803
SQLITE_API const char *sqlite3_errstr(int);
3804
3805
/*
3806
** CAPI3REF: Prepared Statement Object
3807
** KEYWORDS: {prepared statement} {prepared statements}
3808
**
3809
** An instance of this object represents a single SQL statement that
3810
** has been compiled into binary form and is ready to be evaluated.
3811
**
3812
** Think of each SQL statement as a separate computer program.  The
3813
** original SQL text is source code.  A prepared statement object
3814
** is the compiled object code.  All SQL must be converted into a
3815
** prepared statement before it can be run.
3816
**
3817
** The life-cycle of a prepared statement object usually goes like this:
3818
**
3819
** <ol>
3820
** <li> Create the prepared statement object using [sqlite3_prepare_v2()].
3821
** <li> Bind values to [parameters] using the sqlite3_bind_*()
3822
**      interfaces.
3823
** <li> Run the SQL by calling [sqlite3_step()] one or more times.
3824
** <li> Reset the prepared statement using [sqlite3_reset()] then go back
3825
**      to step 2.  Do this zero or more times.
3826
** <li> Destroy the object using [sqlite3_finalize()].
3827
** </ol>
3828
*/
3829
typedef struct sqlite3_stmt sqlite3_stmt;
3830
3831
/*
3832
** CAPI3REF: Run-time Limits
3833
** METHOD: sqlite3
3834
**
3835
** ^(This interface allows the size of various constructs to be limited
3836
** on a connection by connection basis.  The first parameter is the
3837
** [database connection] whose limit is to be set or queried.  The
3838
** second parameter is one of the [limit categories] that define a
3839
** class of constructs to be size limited.  The third parameter is the
3840
** new limit for that construct.)^
3841
**
3842
** ^If the new limit is a negative number, the limit is unchanged.
3843
** ^(For each limit category SQLITE_LIMIT_<i>NAME</i> there is a
3844
** [limits | hard upper bound]
3845
** set at compile-time by a C preprocessor macro called
3846
** [limits | SQLITE_MAX_<i>NAME</i>].
3847
** (The "_LIMIT_" in the name is changed to "_MAX_".))^
3848
** ^Attempts to increase a limit above its hard upper bound are
3849
** silently truncated to the hard upper bound.
3850
**
3851
** ^Regardless of whether or not the limit was changed, the
3852
** [sqlite3_limit()] interface returns the prior value of the limit.
3853
** ^Hence, to find the current value of a limit without changing it,
3854
** simply invoke this interface with the third parameter set to -1.
3855
**
3856
** Run-time limits are intended for use in applications that manage
3857
** both their own internal database and also databases that are controlled
3858
** by untrusted external sources.  An example application might be a
3859
** web browser that has its own databases for storing history and
3860
** separate databases controlled by JavaScript applications downloaded
3861
** off the Internet.  The internal databases can be given the
3862
** large, default limits.  Databases managed by external sources can
3863
** be given much smaller limits designed to prevent a denial of service
3864
** attack.  Developers might also want to use the [sqlite3_set_authorizer()]
3865
** interface to further control untrusted SQL.  The size of the database
3866
** created by an untrusted script can be contained using the
3867
** [max_page_count] [PRAGMA].
3868
**
3869
** New run-time limit categories may be added in future releases.
3870
*/
3871
SQLITE_API int sqlite3_limit(sqlite3*, int id, int newVal);
3872
3873
/*
3874
** CAPI3REF: Run-Time Limit Categories
3875
** KEYWORDS: {limit category} {*limit categories}
3876
**
3877
** These constants define various performance limits
3878
** that can be lowered at run-time using [sqlite3_limit()].
3879
** The synopsis of the meanings of the various limits is shown below.
3880
** Additional information is available at [limits | Limits in SQLite].
3881
**
3882
** <dl>
3883
** [[SQLITE_LIMIT_LENGTH]] ^(<dt>SQLITE_LIMIT_LENGTH</dt>
3884
** <dd>The maximum size of any string or BLOB or table row, in bytes.<dd>)^
3885
**
3886
** [[SQLITE_LIMIT_SQL_LENGTH]] ^(<dt>SQLITE_LIMIT_SQL_LENGTH</dt>
3887
** <dd>The maximum length of an SQL statement, in bytes.</dd>)^
3888
**
3889
** [[SQLITE_LIMIT_COLUMN]] ^(<dt>SQLITE_LIMIT_COLUMN</dt>
3890
** <dd>The maximum number of columns in a table definition or in the
3891
** result set of a [SELECT] or the maximum number of columns in an index
3892
** or in an ORDER BY or GROUP BY clause.</dd>)^
3893
**
3894
** [[SQLITE_LIMIT_EXPR_DEPTH]] ^(<dt>SQLITE_LIMIT_EXPR_DEPTH</dt>
3895
** <dd>The maximum depth of the parse tree on any expression.</dd>)^
3896
**
3897
** [[SQLITE_LIMIT_COMPOUND_SELECT]] ^(<dt>SQLITE_LIMIT_COMPOUND_SELECT</dt>
3898
** <dd>The maximum number of terms in a compound SELECT statement.</dd>)^
3899
**
3900
** [[SQLITE_LIMIT_VDBE_OP]] ^(<dt>SQLITE_LIMIT_VDBE_OP</dt>
3901
** <dd>The maximum number of instructions in a virtual machine program
3902
** used to implement an SQL statement.  If [sqlite3_prepare_v2()] or
3903
** the equivalent tries to allocate space for more than this many opcodes
3904
** in a single prepared statement, an SQLITE_NOMEM error is returned.</dd>)^
3905
**
3906
** [[SQLITE_LIMIT_FUNCTION_ARG]] ^(<dt>SQLITE_LIMIT_FUNCTION_ARG</dt>
3907
** <dd>The maximum number of arguments on a function.</dd>)^
3908
**
3909
** [[SQLITE_LIMIT_ATTACHED]] ^(<dt>SQLITE_LIMIT_ATTACHED</dt>
3910
** <dd>The maximum number of [ATTACH | attached databases].)^</dd>
3911
**
3912
** [[SQLITE_LIMIT_LIKE_PATTERN_LENGTH]]
3913
** ^(<dt>SQLITE_LIMIT_LIKE_PATTERN_LENGTH</dt>
3914
** <dd>The maximum length of the pattern argument to the [LIKE] or
3915
** [GLOB] operators.</dd>)^
3916
**
3917
** [[SQLITE_LIMIT_VARIABLE_NUMBER]]
3918
** ^(<dt>SQLITE_LIMIT_VARIABLE_NUMBER</dt>
3919
** <dd>The maximum index number of any [parameter] in an SQL statement.)^
3920
**
3921
** [[SQLITE_LIMIT_TRIGGER_DEPTH]] ^(<dt>SQLITE_LIMIT_TRIGGER_DEPTH</dt>
3922
** <dd>The maximum depth of recursion for triggers.</dd>)^
3923
**
3924
** [[SQLITE_LIMIT_WORKER_THREADS]] ^(<dt>SQLITE_LIMIT_WORKER_THREADS</dt>
3925
** <dd>The maximum number of auxiliary worker threads that a single
3926
** [prepared statement] may start.</dd>)^
3927
** </dl>
3928
*/
3929
#define SQLITE_LIMIT_LENGTH                    0
3930
#define SQLITE_LIMIT_SQL_LENGTH                1
3931
#define SQLITE_LIMIT_COLUMN                    2
3932
#define SQLITE_LIMIT_EXPR_DEPTH                3
3933
#define SQLITE_LIMIT_COMPOUND_SELECT           4
3934
#define SQLITE_LIMIT_VDBE_OP                   5
3935
#define SQLITE_LIMIT_FUNCTION_ARG              6
3936
#define SQLITE_LIMIT_ATTACHED                  7
3937
#define SQLITE_LIMIT_LIKE_PATTERN_LENGTH       8
3938
#define SQLITE_LIMIT_VARIABLE_NUMBER           9
3939
#define SQLITE_LIMIT_TRIGGER_DEPTH            10
3940
#define SQLITE_LIMIT_WORKER_THREADS           11
3941
3942
/*
3943
** CAPI3REF: Prepare Flags
3944
**
3945
** These constants define various flags that can be passed into
3946
** "prepFlags" parameter of the [sqlite3_prepare_v3()] and
3947
** [sqlite3_prepare16_v3()] interfaces.
3948
**
3949
** New flags may be added in future releases of SQLite.
3950
**
3951
** <dl>
3952
** [[SQLITE_PREPARE_PERSISTENT]] ^(<dt>SQLITE_PREPARE_PERSISTENT</dt>
3953
** <dd>The SQLITE_PREPARE_PERSISTENT flag is a hint to the query planner
3954
** that the prepared statement will be retained for a long time and
3955
** probably reused many times.)^ ^Without this flag, [sqlite3_prepare_v3()]
3956
** and [sqlite3_prepare16_v3()] assume that the prepared statement will
3957
** be used just once or at most a few times and then destroyed using
3958
** [sqlite3_finalize()] relatively soon. The current implementation acts
3959
** on this hint by avoiding the use of [lookaside memory] so as not to
3960
** deplete the limited store of lookaside memory. Future versions of
3961
** SQLite may act on this hint differently.
3962
**
3963
** [[SQLITE_PREPARE_NORMALIZE]] <dt>SQLITE_PREPARE_NORMALIZE</dt>
3964
** <dd>The SQLITE_PREPARE_NORMALIZE flag is a no-op. This flag used
3965
** to be required for any prepared statement that wanted to use the
3966
** [sqlite3_normalized_sql()] interface.  However, the
3967
** [sqlite3_normalized_sql()] interface is now available to all
3968
** prepared statements, regardless of whether or not they use this
3969
** flag.
3970
**
3971
** [[SQLITE_PREPARE_NO_VTAB]] <dt>SQLITE_PREPARE_NO_VTAB</dt>
3972
** <dd>The SQLITE_PREPARE_NO_VTAB flag causes the SQL compiler
3973
** to return an error (error code SQLITE_ERROR) if the statement uses
3974
** any virtual tables.
3975
** </dl>
3976
*/
3977
#define SQLITE_PREPARE_PERSISTENT              0x01
3978
#define SQLITE_PREPARE_NORMALIZE               0x02
3979
#define SQLITE_PREPARE_NO_VTAB                 0x04
3980
3981
/*
3982
** CAPI3REF: Compiling An SQL Statement
3983
** KEYWORDS: {SQL statement compiler}
3984
** METHOD: sqlite3
3985
** CONSTRUCTOR: sqlite3_stmt
3986
**
3987
** To execute an SQL statement, it must first be compiled into a byte-code
3988
** program using one of these routines.  Or, in other words, these routines
3989
** are constructors for the [prepared statement] object.
3990
**
3991
** The preferred routine to use is [sqlite3_prepare_v2()].  The
3992
** [sqlite3_prepare()] interface is legacy and should be avoided.
3993
** [sqlite3_prepare_v3()] has an extra "prepFlags" option that is used
3994
** for special purposes.
3995
**
3996
** The use of the UTF-8 interfaces is preferred, as SQLite currently
3997
** does all parsing using UTF-8.  The UTF-16 interfaces are provided
3998
** as a convenience.  The UTF-16 interfaces work by converting the
3999
** input text into UTF-8, then invoking the corresponding UTF-8 interface.
4000
**
4001
** The first argument, "db", is a [database connection] obtained from a
4002
** prior successful call to [sqlite3_open()], [sqlite3_open_v2()] or
4003
** [sqlite3_open16()].  The database connection must not have been closed.
4004
**
4005
** The second argument, "zSql", is the statement to be compiled, encoded
4006
** as either UTF-8 or UTF-16.  The sqlite3_prepare(), sqlite3_prepare_v2(),
4007
** and sqlite3_prepare_v3()
4008
** interfaces use UTF-8, and sqlite3_prepare16(), sqlite3_prepare16_v2(),
4009
** and sqlite3_prepare16_v3() use UTF-16.
4010
**
4011
** ^If the nByte argument is negative, then zSql is read up to the
4012
** first zero terminator. ^If nByte is positive, then it is the
4013
** number of bytes read from zSql.  ^If nByte is zero, then no prepared
4014
** statement is generated.
4015
** If the caller knows that the supplied string is nul-terminated, then
4016
** there is a small performance advantage to passing an nByte parameter that
4017
** is the number of bytes in the input string <i>including</i>
4018
** the nul-terminator.
4019
**
4020
** ^If pzTail is not NULL then *pzTail is made to point to the first byte
4021
** past the end of the first SQL statement in zSql.  These routines only
4022
** compile the first statement in zSql, so *pzTail is left pointing to
4023
** what remains uncompiled.
4024
**
4025
** ^*ppStmt is left pointing to a compiled [prepared statement] that can be
4026
** executed using [sqlite3_step()].  ^If there is an error, *ppStmt is set
4027
** to NULL.  ^If the input text contains no SQL (if the input is an empty
4028
** string or a comment) then *ppStmt is set to NULL.
4029
** The calling procedure is responsible for deleting the compiled
4030
** SQL statement using [sqlite3_finalize()] after it has finished with it.
4031
** ppStmt may not be NULL.
4032
**
4033
** ^On success, the sqlite3_prepare() family of routines return [SQLITE_OK];
4034
** otherwise an [error code] is returned.
4035
**
4036
** The sqlite3_prepare_v2(), sqlite3_prepare_v3(), sqlite3_prepare16_v2(),
4037
** and sqlite3_prepare16_v3() interfaces are recommended for all new programs.
4038
** The older interfaces (sqlite3_prepare() and sqlite3_prepare16())
4039
** are retained for backwards compatibility, but their use is discouraged.
4040
** ^In the "vX" interfaces, the prepared statement
4041
** that is returned (the [sqlite3_stmt] object) contains a copy of the
4042
** original SQL text. This causes the [sqlite3_step()] interface to
4043
** behave differently in three ways:
4044
**
4045
** <ol>
4046
** <li>
4047
** ^If the database schema changes, instead of returning [SQLITE_SCHEMA] as it
4048
** always used to do, [sqlite3_step()] will automatically recompile the SQL
4049
** statement and try to run it again. As many as [SQLITE_MAX_SCHEMA_RETRY]
4050
** retries will occur before sqlite3_step() gives up and returns an error.
4051
** </li>
4052
**
4053
** <li>
4054
** ^When an error occurs, [sqlite3_step()] will return one of the detailed
4055
** [error codes] or [extended error codes].  ^The legacy behavior was that
4056
** [sqlite3_step()] would only return a generic [SQLITE_ERROR] result code
4057
** and the application would have to make a second call to [sqlite3_reset()]
4058
** in order to find the underlying cause of the problem. With the "v2" prepare
4059
** interfaces, the underlying reason for the error is returned immediately.
4060
** </li>
4061
**
4062
** <li>
4063
** ^If the specific value bound to a [parameter | host parameter] in the
4064
** WHERE clause might influence the choice of query plan for a statement,
4065
** then the statement will be automatically recompiled, as if there had been
4066
** a schema change, on the first [sqlite3_step()] call following any change
4067
** to the [sqlite3_bind_text | bindings] of that [parameter].
4068
** ^The specific value of a WHERE-clause [parameter] might influence the
4069
** choice of query plan if the parameter is the left-hand side of a [LIKE]
4070
** or [GLOB] operator or if the parameter is compared to an indexed column
4071
** and the [SQLITE_ENABLE_STAT4] compile-time option is enabled.
4072
** </li>
4073
** </ol>
4074
**
4075
** <p>^sqlite3_prepare_v3() differs from sqlite3_prepare_v2() only in having
4076
** the extra prepFlags parameter, which is a bit array consisting of zero or
4077
** more of the [SQLITE_PREPARE_PERSISTENT|SQLITE_PREPARE_*] flags.  ^The
4078
** sqlite3_prepare_v2() interface works exactly the same as
4079
** sqlite3_prepare_v3() with a zero prepFlags parameter.
4080
*/
4081
SQLITE_API int sqlite3_prepare(
4082
  sqlite3 *db,            /* Database handle */
4083
  const char *zSql,       /* SQL statement, UTF-8 encoded */
4084
  int nByte,              /* Maximum length of zSql in bytes. */
4085
  sqlite3_stmt **ppStmt,  /* OUT: Statement handle */
4086
  const char **pzTail     /* OUT: Pointer to unused portion of zSql */
4087
);
4088
SQLITE_API int sqlite3_prepare_v2(
4089
  sqlite3 *db,            /* Database handle */
4090
  const char *zSql,       /* SQL statement, UTF-8 encoded */
4091
  int nByte,              /* Maximum length of zSql in bytes. */
4092
  sqlite3_stmt **ppStmt,  /* OUT: Statement handle */
4093
  const char **pzTail     /* OUT: Pointer to unused portion of zSql */
4094
);
4095
SQLITE_API int sqlite3_prepare_v3(
4096
  sqlite3 *db,            /* Database handle */
4097
  const char *zSql,       /* SQL statement, UTF-8 encoded */
4098
  int nByte,              /* Maximum length of zSql in bytes. */
4099
  unsigned int prepFlags, /* Zero or more SQLITE_PREPARE_ flags */
4100
  sqlite3_stmt **ppStmt,  /* OUT: Statement handle */
4101
  const char **pzTail     /* OUT: Pointer to unused portion of zSql */
4102
);
4103
SQLITE_API int sqlite3_prepare16(
4104
  sqlite3 *db,            /* Database handle */
4105
  const void *zSql,       /* SQL statement, UTF-16 encoded */
4106
  int nByte,              /* Maximum length of zSql in bytes. */
4107
  sqlite3_stmt **ppStmt,  /* OUT: Statement handle */
4108
  const void **pzTail     /* OUT: Pointer to unused portion of zSql */
4109
);
4110
SQLITE_API int sqlite3_prepare16_v2(
4111
  sqlite3 *db,            /* Database handle */
4112
  const void *zSql,       /* SQL statement, UTF-16 encoded */
4113
  int nByte,              /* Maximum length of zSql in bytes. */
4114
  sqlite3_stmt **ppStmt,  /* OUT: Statement handle */
4115
  const void **pzTail     /* OUT: Pointer to unused portion of zSql */
4116
);
4117
SQLITE_API int sqlite3_prepare16_v3(
4118
  sqlite3 *db,            /* Database handle */
4119
  const void *zSql,       /* SQL statement, UTF-16 encoded */
4120
  int nByte,              /* Maximum length of zSql in bytes. */
4121
  unsigned int prepFlags, /* Zero or more SQLITE_PREPARE_ flags */
4122
  sqlite3_stmt **ppStmt,  /* OUT: Statement handle */
4123
  const void **pzTail     /* OUT: Pointer to unused portion of zSql */
4124
);
4125
4126
/*
4127
** CAPI3REF: Retrieving Statement SQL
4128
** METHOD: sqlite3_stmt
4129
**
4130
** ^The sqlite3_sql(P) interface returns a pointer to a copy of the UTF-8
4131
** SQL text used to create [prepared statement] P if P was
4132
** created by [sqlite3_prepare_v2()], [sqlite3_prepare_v3()],
4133
** [sqlite3_prepare16_v2()], or [sqlite3_prepare16_v3()].
4134
** ^The sqlite3_expanded_sql(P) interface returns a pointer to a UTF-8
4135
** string containing the SQL text of prepared statement P with
4136
** [bound parameters] expanded.
4137
** ^The sqlite3_normalized_sql(P) interface returns a pointer to a UTF-8
4138
** string containing the normalized SQL text of prepared statement P.  The
4139
** semantics used to normalize a SQL statement are unspecified and subject
4140
** to change.  At a minimum, literal values will be replaced with suitable
4141
** placeholders.
4142
**
4143
** ^(For example, if a prepared statement is created using the SQL
4144
** text "SELECT $abc,:xyz" and if parameter $abc is bound to integer 2345
4145
** and parameter :xyz is unbound, then sqlite3_sql() will return
4146
** the original string, "SELECT $abc,:xyz" but sqlite3_expanded_sql()
4147
** will return "SELECT 2345,NULL".)^
4148
**
4149
** ^The sqlite3_expanded_sql() interface returns NULL if insufficient memory
4150
** is available to hold the result, or if the result would exceed the
4151
** the maximum string length determined by the [SQLITE_LIMIT_LENGTH].
4152
**
4153
** ^The [SQLITE_TRACE_SIZE_LIMIT] compile-time option limits the size of
4154
** bound parameter expansions.  ^The [SQLITE_OMIT_TRACE] compile-time
4155
** option causes sqlite3_expanded_sql() to always return NULL.
4156
**
4157
** ^The strings returned by sqlite3_sql(P) and sqlite3_normalized_sql(P)
4158
** are managed by SQLite and are automatically freed when the prepared
4159
** statement is finalized.
4160
** ^The string returned by sqlite3_expanded_sql(P), on the other hand,
4161
** is obtained from [sqlite3_malloc()] and must be free by the application
4162
** by passing it to [sqlite3_free()].
4163
*/
4164
SQLITE_API const char *sqlite3_sql(sqlite3_stmt *pStmt);
4165
SQLITE_API char *sqlite3_expanded_sql(sqlite3_stmt *pStmt);
4166
SQLITE_API const char *sqlite3_normalized_sql(sqlite3_stmt *pStmt);
4167
4168
/*
4169
** CAPI3REF: Determine If An SQL Statement Writes The Database
4170
** METHOD: sqlite3_stmt
4171
**
4172
** ^The sqlite3_stmt_readonly(X) interface returns true (non-zero) if
4173
** and only if the [prepared statement] X makes no direct changes to
4174
** the content of the database file.
4175
**
4176
** Note that [application-defined SQL functions] or
4177
** [virtual tables] might change the database indirectly as a side effect.
4178
** ^(For example, if an application defines a function "eval()" that
4179
** calls [sqlite3_exec()], then the following SQL statement would
4180
** change the database file through side-effects:
4181
**
4182
** <blockquote><pre>
4183
**    SELECT eval('DELETE FROM t1') FROM t2;
4184
** </pre></blockquote>
4185
**
4186
** But because the [SELECT] statement does not change the database file
4187
** directly, sqlite3_stmt_readonly() would still return true.)^
4188
**
4189
** ^Transaction control statements such as [BEGIN], [COMMIT], [ROLLBACK],
4190
** [SAVEPOINT], and [RELEASE] cause sqlite3_stmt_readonly() to return true,
4191
** since the statements themselves do not actually modify the database but
4192
** rather they control the timing of when other statements modify the
4193
** database.  ^The [ATTACH] and [DETACH] statements also cause
4194
** sqlite3_stmt_readonly() to return true since, while those statements
4195
** change the configuration of a database connection, they do not make
4196
** changes to the content of the database files on disk.
4197
** ^The sqlite3_stmt_readonly() interface returns true for [BEGIN] since
4198
** [BEGIN] merely sets internal flags, but the [BEGIN|BEGIN IMMEDIATE] and
4199
** [BEGIN|BEGIN EXCLUSIVE] commands do touch the database and so
4200
** sqlite3_stmt_readonly() returns false for those commands.
4201
**
4202
** ^This routine returns false if there is any possibility that the
4203
** statement might change the database file.  ^A false return does
4204
** not guarantee that the statement will change the database file.
4205
** ^For example, an UPDATE statement might have a WHERE clause that
4206
** makes it a no-op, but the sqlite3_stmt_readonly() result would still
4207
** be false.  ^Similarly, a CREATE TABLE IF NOT EXISTS statement is a
4208
** read-only no-op if the table already exists, but
4209
** sqlite3_stmt_readonly() still returns false for such a statement.
4210
*/
4211
SQLITE_API int sqlite3_stmt_readonly(sqlite3_stmt *pStmt);
4212
4213
/*
4214
** CAPI3REF: Query The EXPLAIN Setting For A Prepared Statement
4215
** METHOD: sqlite3_stmt
4216
**
4217
** ^The sqlite3_stmt_isexplain(S) interface returns 1 if the
4218
** prepared statement S is an EXPLAIN statement, or 2 if the
4219
** statement S is an EXPLAIN QUERY PLAN.
4220
** ^The sqlite3_stmt_isexplain(S) interface returns 0 if S is
4221
** an ordinary statement or a NULL pointer.
4222
*/
4223
SQLITE_API int sqlite3_stmt_isexplain(sqlite3_stmt *pStmt);
4224
4225
/*
4226
** CAPI3REF: Determine If A Prepared Statement Has Been Reset
4227
** METHOD: sqlite3_stmt
4228
**
4229
** ^The sqlite3_stmt_busy(S) interface returns true (non-zero) if the
4230
** [prepared statement] S has been stepped at least once using
4231
** [sqlite3_step(S)] but has neither run to completion (returned
4232
** [SQLITE_DONE] from [sqlite3_step(S)]) nor
4233
** been reset using [sqlite3_reset(S)].  ^The sqlite3_stmt_busy(S)
4234
** interface returns false if S is a NULL pointer.  If S is not a
4235
** NULL pointer and is not a pointer to a valid [prepared statement]
4236
** object, then the behavior is undefined and probably undesirable.
4237
**
4238
** This interface can be used in combination [sqlite3_next_stmt()]
4239
** to locate all prepared statements associated with a database
4240
** connection that are in need of being reset.  This can be used,
4241
** for example, in diagnostic routines to search for prepared
4242
** statements that are holding a transaction open.
4243
*/
4244
SQLITE_API int sqlite3_stmt_busy(sqlite3_stmt*);
4245
4246
/*
4247
** CAPI3REF: Dynamically Typed Value Object
4248
** KEYWORDS: {protected sqlite3_value} {unprotected sqlite3_value}
4249
**
4250
** SQLite uses the sqlite3_value object to represent all values
4251
** that can be stored in a database table. SQLite uses dynamic typing
4252
** for the values it stores.  ^Values stored in sqlite3_value objects
4253
** can be integers, floating point values, strings, BLOBs, or NULL.
4254
**
4255
** An sqlite3_value object may be either "protected" or "unprotected".
4256
** Some interfaces require a protected sqlite3_value.  Other interfaces
4257
** will accept either a protected or an unprotected sqlite3_value.
4258
** Every interface that accepts sqlite3_value arguments specifies
4259
** whether or not it requires a protected sqlite3_value.  The
4260
** [sqlite3_value_dup()] interface can be used to construct a new
4261
** protected sqlite3_value from an unprotected sqlite3_value.
4262
**
4263
** The terms "protected" and "unprotected" refer to whether or not
4264
** a mutex is held.  An internal mutex is held for a protected
4265
** sqlite3_value object but no mutex is held for an unprotected
4266
** sqlite3_value object.  If SQLite is compiled to be single-threaded
4267
** (with [SQLITE_THREADSAFE=0] and with [sqlite3_threadsafe()] returning 0)
4268
** or if SQLite is run in one of reduced mutex modes
4269
** [SQLITE_CONFIG_SINGLETHREAD] or [SQLITE_CONFIG_MULTITHREAD]
4270
** then there is no distinction between protected and unprotected
4271
** sqlite3_value objects and they can be used interchangeably.  However,
4272
** for maximum code portability it is recommended that applications
4273
** still make the distinction between protected and unprotected
4274
** sqlite3_value objects even when not strictly required.
4275
**
4276
** ^The sqlite3_value objects that are passed as parameters into the
4277
** implementation of [application-defined SQL functions] are protected.
4278
** ^The sqlite3_value object returned by
4279
** [sqlite3_column_value()] is unprotected.
4280
** Unprotected sqlite3_value objects may only be used as arguments
4281
** to [sqlite3_result_value()], [sqlite3_bind_value()], and
4282
** [sqlite3_value_dup()].
4283
** The [sqlite3_value_blob | sqlite3_value_type()] family of
4284
** interfaces require protected sqlite3_value objects.
4285
*/
4286
typedef struct sqlite3_value sqlite3_value;
4287
4288
/*
4289
** CAPI3REF: SQL Function Context Object
4290
**
4291
** The context in which an SQL function executes is stored in an
4292
** sqlite3_context object.  ^A pointer to an sqlite3_context object
4293
** is always first parameter to [application-defined SQL functions].
4294
** The application-defined SQL function implementation will pass this
4295
** pointer through into calls to [sqlite3_result_int | sqlite3_result()],
4296
** [sqlite3_aggregate_context()], [sqlite3_user_data()],
4297
** [sqlite3_context_db_handle()], [sqlite3_get_auxdata()],
4298
** and/or [sqlite3_set_auxdata()].
4299
*/
4300
typedef struct sqlite3_context sqlite3_context;
4301
4302
/*
4303
** CAPI3REF: Binding Values To Prepared Statements
4304
** KEYWORDS: {host parameter} {host parameters} {host parameter name}
4305
** KEYWORDS: {SQL parameter} {SQL parameters} {parameter binding}
4306
** METHOD: sqlite3_stmt
4307
**
4308
** ^(In the SQL statement text input to [sqlite3_prepare_v2()] and its variants,
4309
** literals may be replaced by a [parameter] that matches one of following
4310
** templates:
4311
**
4312
** <ul>
4313
** <li>  ?
4314
** <li>  ?NNN
4315
** <li>  :VVV
4316
** <li>  @VVV
4317
** <li>  $VVV
4318
** </ul>
4319
**
4320
** In the templates above, NNN represents an integer literal,
4321
** and VVV represents an alphanumeric identifier.)^  ^The values of these
4322
** parameters (also called "host parameter names" or "SQL parameters")
4323
** can be set using the sqlite3_bind_*() routines defined here.
4324
**
4325
** ^The first argument to the sqlite3_bind_*() routines is always
4326
** a pointer to the [sqlite3_stmt] object returned from
4327
** [sqlite3_prepare_v2()] or its variants.
4328
**
4329
** ^The second argument is the index of the SQL parameter to be set.
4330
** ^The leftmost SQL parameter has an index of 1.  ^When the same named
4331
** SQL parameter is used more than once, second and subsequent
4332
** occurrences have the same index as the first occurrence.
4333
** ^The index for named parameters can be looked up using the
4334
** [sqlite3_bind_parameter_index()] API if desired.  ^The index
4335
** for "?NNN" parameters is the value of NNN.
4336
** ^The NNN value must be between 1 and the [sqlite3_limit()]
4337
** parameter [SQLITE_LIMIT_VARIABLE_NUMBER] (default value: 32766).
4338
**
4339
** ^The third argument is the value to bind to the parameter.
4340
** ^If the third parameter to sqlite3_bind_text() or sqlite3_bind_text16()
4341
** or sqlite3_bind_blob() is a NULL pointer then the fourth parameter
4342
** is ignored and the end result is the same as sqlite3_bind_null().
4343
** ^If the third parameter to sqlite3_bind_text() is not NULL, then
4344
** it should be a pointer to well-formed UTF8 text.
4345
** ^If the third parameter to sqlite3_bind_text16() is not NULL, then
4346
** it should be a pointer to well-formed UTF16 text.
4347
** ^If the third parameter to sqlite3_bind_text64() is not NULL, then
4348
** it should be a pointer to a well-formed unicode string that is
4349
** either UTF8 if the sixth parameter is SQLITE_UTF8, or UTF16
4350
** otherwise.
4351
**
4352
** [[byte-order determination rules]] ^The byte-order of
4353
** UTF16 input text is determined by the byte-order mark (BOM, U+FEFF)
4354
** found in first character, which is removed, or in the absence of a BOM
4355
** the byte order is the native byte order of the host
4356
** machine for sqlite3_bind_text16() or the byte order specified in
4357
** the 6th parameter for sqlite3_bind_text64().)^
4358
** ^If UTF16 input text contains invalid unicode
4359
** characters, then SQLite might change those invalid characters
4360
** into the unicode replacement character: U+FFFD.
4361
**
4362
** ^(In those routines that have a fourth argument, its value is the
4363
** number of bytes in the parameter.  To be clear: the value is the
4364
** number of <u>bytes</u> in the value, not the number of characters.)^
4365
** ^If the fourth parameter to sqlite3_bind_text() or sqlite3_bind_text16()
4366
** is negative, then the length of the string is
4367
** the number of bytes up to the first zero terminator.
4368
** If the fourth parameter to sqlite3_bind_blob() is negative, then
4369
** the behavior is undefined.
4370
** If a non-negative fourth parameter is provided to sqlite3_bind_text()
4371
** or sqlite3_bind_text16() or sqlite3_bind_text64() then
4372
** that parameter must be the byte offset
4373
** where the NUL terminator would occur assuming the string were NUL
4374
** terminated.  If any NUL characters occurs at byte offsets less than
4375
** the value of the fourth parameter then the resulting string value will
4376
** contain embedded NULs.  The result of expressions involving strings
4377
** with embedded NULs is undefined.
4378
**
4379
** ^The fifth argument to the BLOB and string binding interfaces controls
4380
** or indicates the lifetime of the object referenced by the third parameter.
4381
** These three options exist:
4382
** ^ (1) A destructor to dispose of the BLOB or string after SQLite has finished
4383
** with it may be passed. ^It is called to dispose of the BLOB or string even
4384
** if the call to the bind API fails, except the destructor is not called if
4385
** the third parameter is a NULL pointer or the fourth parameter is negative.
4386
** ^ (2) The special constant, [SQLITE_STATIC], may be passsed to indicate that
4387
** the application remains responsible for disposing of the object. ^In this
4388
** case, the object and the provided pointer to it must remain valid until
4389
** either the prepared statement is finalized or the same SQL parameter is
4390
** bound to something else, whichever occurs sooner.
4391
** ^ (3) The constant, [SQLITE_TRANSIENT], may be passed to indicate that the
4392
** object is to be copied prior to the return from sqlite3_bind_*(). ^The
4393
** object and pointer to it must remain valid until then. ^SQLite will then
4394
** manage the lifetime of its private copy.
4395
**
4396
** ^The sixth argument to sqlite3_bind_text64() must be one of
4397
** [SQLITE_UTF8], [SQLITE_UTF16], [SQLITE_UTF16BE], or [SQLITE_UTF16LE]
4398
** to specify the encoding of the text in the third parameter.  If
4399
** the sixth argument to sqlite3_bind_text64() is not one of the
4400
** allowed values shown above, or if the text encoding is different
4401
** from the encoding specified by the sixth parameter, then the behavior
4402
** is undefined.
4403
**
4404
** ^The sqlite3_bind_zeroblob() routine binds a BLOB of length N that
4405
** is filled with zeroes.  ^A zeroblob uses a fixed amount of memory
4406
** (just an integer to hold its size) while it is being processed.
4407
** Zeroblobs are intended to serve as placeholders for BLOBs whose
4408
** content is later written using
4409
** [sqlite3_blob_open | incremental BLOB I/O] routines.
4410
** ^A negative value for the zeroblob results in a zero-length BLOB.
4411
**
4412
** ^The sqlite3_bind_pointer(S,I,P,T,D) routine causes the I-th parameter in
4413
** [prepared statement] S to have an SQL value of NULL, but to also be
4414
** associated with the pointer P of type T.  ^D is either a NULL pointer or
4415
** a pointer to a destructor function for P. ^SQLite will invoke the
4416
** destructor D with a single argument of P when it is finished using
4417
** P.  The T parameter should be a static string, preferably a string
4418
** literal. The sqlite3_bind_pointer() routine is part of the
4419
** [pointer passing interface] added for SQLite 3.20.0.
4420
**
4421
** ^If any of the sqlite3_bind_*() routines are called with a NULL pointer
4422
** for the [prepared statement] or with a prepared statement for which
4423
** [sqlite3_step()] has been called more recently than [sqlite3_reset()],
4424
** then the call will return [SQLITE_MISUSE].  If any sqlite3_bind_()
4425
** routine is passed a [prepared statement] that has been finalized, the
4426
** result is undefined and probably harmful.
4427
**
4428
** ^Bindings are not cleared by the [sqlite3_reset()] routine.
4429
** ^Unbound parameters are interpreted as NULL.
4430
**
4431
** ^The sqlite3_bind_* routines return [SQLITE_OK] on success or an
4432
** [error code] if anything goes wrong.
4433
** ^[SQLITE_TOOBIG] might be returned if the size of a string or BLOB
4434
** exceeds limits imposed by [sqlite3_limit]([SQLITE_LIMIT_LENGTH]) or
4435
** [SQLITE_MAX_LENGTH].
4436
** ^[SQLITE_RANGE] is returned if the parameter
4437
** index is out of range.  ^[SQLITE_NOMEM] is returned if malloc() fails.
4438
**
4439
** See also: [sqlite3_bind_parameter_count()],
4440
** [sqlite3_bind_parameter_name()], and [sqlite3_bind_parameter_index()].
4441
*/
4442
SQLITE_API int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
4443
SQLITE_API int sqlite3_bind_blob64(sqlite3_stmt*, int, const void*, sqlite3_uint64,
4444
                        void(*)(void*));
4445
SQLITE_API int sqlite3_bind_double(sqlite3_stmt*, int, double);
4446
SQLITE_API int sqlite3_bind_int(sqlite3_stmt*, int, int);
4447
SQLITE_API int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite3_int64);
4448
SQLITE_API int sqlite3_bind_null(sqlite3_stmt*, int);
4449
SQLITE_API int sqlite3_bind_text(sqlite3_stmt*,int,const char*,int,void(*)(void*));
4450
SQLITE_API int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
4451
SQLITE_API int sqlite3_bind_text64(sqlite3_stmt*, int, const char*, sqlite3_uint64,
4452
                         void(*)(void*), unsigned char encoding);
4453
SQLITE_API int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
4454
SQLITE_API int sqlite3_bind_pointer(sqlite3_stmt*, int, void*, const char*,void(*)(void*));
4455
SQLITE_API int sqlite3_bind_zeroblob(sqlite3_stmt*, int, int n);
4456
SQLITE_API int sqlite3_bind_zeroblob64(sqlite3_stmt*, int, sqlite3_uint64);
4457
4458
/*
4459
** CAPI3REF: Number Of SQL Parameters
4460
** METHOD: sqlite3_stmt
4461
**
4462
** ^This routine can be used to find the number of [SQL parameters]
4463
** in a [prepared statement].  SQL parameters are tokens of the
4464
** form "?", "?NNN", ":AAA", "$AAA", or "@AAA" that serve as
4465
** placeholders for values that are [sqlite3_bind_blob | bound]
4466
** to the parameters at a later time.
4467
**
4468
** ^(This routine actually returns the index of the largest (rightmost)
4469
** parameter. For all forms except ?NNN, this will correspond to the
4470
** number of unique parameters.  If parameters of the ?NNN form are used,
4471
** there may be gaps in the list.)^
4472
**
4473
** See also: [sqlite3_bind_blob|sqlite3_bind()],
4474
** [sqlite3_bind_parameter_name()], and
4475
** [sqlite3_bind_parameter_index()].
4476
*/
4477
SQLITE_API int sqlite3_bind_parameter_count(sqlite3_stmt*);
4478
4479
/*
4480
** CAPI3REF: Name Of A Host Parameter
4481
** METHOD: sqlite3_stmt
4482
**
4483
** ^The sqlite3_bind_parameter_name(P,N) interface returns
4484
** the name of the N-th [SQL parameter] in the [prepared statement] P.
4485
** ^(SQL parameters of the form "?NNN" or ":AAA" or "@AAA" or "$AAA"
4486
** have a name which is the string "?NNN" or ":AAA" or "@AAA" or "$AAA"
4487
** respectively.
4488
** In other words, the initial ":" or "$" or "@" or "?"
4489
** is included as part of the name.)^
4490
** ^Parameters of the form "?" without a following integer have no name
4491
** and are referred to as "nameless" or "anonymous parameters".
4492
**
4493
** ^The first host parameter has an index of 1, not 0.
4494
**
4495
** ^If the value N is out of range or if the N-th parameter is
4496
** nameless, then NULL is returned.  ^The returned string is
4497
** always in UTF-8 encoding even if the named parameter was
4498
** originally specified as UTF-16 in [sqlite3_prepare16()],
4499
** [sqlite3_prepare16_v2()], or [sqlite3_prepare16_v3()].
4500
**
4501
** See also: [sqlite3_bind_blob|sqlite3_bind()],
4502
** [sqlite3_bind_parameter_count()], and
4503
** [sqlite3_bind_parameter_index()].
4504
*/
4505
SQLITE_API const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
4506
4507
/*
4508
** CAPI3REF: Index Of A Parameter With A Given Name
4509
** METHOD: sqlite3_stmt
4510
**
4511
** ^Return the index of an SQL parameter given its name.  ^The
4512
** index value returned is suitable for use as the second
4513
** parameter to [sqlite3_bind_blob|sqlite3_bind()].  ^A zero
4514
** is returned if no matching parameter is found.  ^The parameter
4515
** name must be given in UTF-8 even if the original statement
4516
** was prepared from UTF-16 text using [sqlite3_prepare16_v2()] or
4517
** [sqlite3_prepare16_v3()].
4518
**
4519
** See also: [sqlite3_bind_blob|sqlite3_bind()],
4520
** [sqlite3_bind_parameter_count()], and
4521
** [sqlite3_bind_parameter_name()].
4522
*/
4523
SQLITE_API int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
4524
4525
/*
4526
** CAPI3REF: Reset All Bindings On A Prepared Statement
4527
** METHOD: sqlite3_stmt
4528
**
4529
** ^Contrary to the intuition of many, [sqlite3_reset()] does not reset
4530
** the [sqlite3_bind_blob | bindings] on a [prepared statement].
4531
** ^Use this routine to reset all host parameters to NULL.
4532
*/
4533
SQLITE_API int sqlite3_clear_bindings(sqlite3_stmt*);
4534
4535
/*
4536
** CAPI3REF: Number Of Columns In A Result Set
4537
** METHOD: sqlite3_stmt
4538
**
4539
** ^Return the number of columns in the result set returned by the
4540
** [prepared statement]. ^If this routine returns 0, that means the
4541
** [prepared statement] returns no data (for example an [UPDATE]).
4542
** ^However, just because this routine returns a positive number does not
4543
** mean that one or more rows of data will be returned.  ^A SELECT statement
4544
** will always have a positive sqlite3_column_count() but depending on the
4545
** WHERE clause constraints and the table content, it might return no rows.
4546
**
4547
** See also: [sqlite3_data_count()]
4548
*/
4549
SQLITE_API int sqlite3_column_count(sqlite3_stmt *pStmt);
4550
4551
/*
4552
** CAPI3REF: Column Names In A Result Set
4553
** METHOD: sqlite3_stmt
4554
**
4555
** ^These routines return the name assigned to a particular column
4556
** in the result set of a [SELECT] statement.  ^The sqlite3_column_name()
4557
** interface returns a pointer to a zero-terminated UTF-8 string
4558
** and sqlite3_column_name16() returns a pointer to a zero-terminated
4559
** UTF-16 string.  ^The first parameter is the [prepared statement]
4560
** that implements the [SELECT] statement. ^The second parameter is the
4561
** column number.  ^The leftmost column is number 0.
4562
**
4563
** ^The returned string pointer is valid until either the [prepared statement]
4564
** is destroyed by [sqlite3_finalize()] or until the statement is automatically
4565
** reprepared by the first call to [sqlite3_step()] for a particular run
4566
** or until the next call to
4567
** sqlite3_column_name() or sqlite3_column_name16() on the same column.
4568
**
4569
** ^If sqlite3_malloc() fails during the processing of either routine
4570
** (for example during a conversion from UTF-8 to UTF-16) then a
4571
** NULL pointer is returned.
4572
**
4573
** ^The name of a result column is the value of the "AS" clause for
4574
** that column, if there is an AS clause.  If there is no AS clause
4575
** then the name of the column is unspecified and may change from
4576
** one release of SQLite to the next.
4577
*/
4578
SQLITE_API const char *sqlite3_column_name(sqlite3_stmt*, int N);
4579
SQLITE_API const void *sqlite3_column_name16(sqlite3_stmt*, int N);
4580
4581
/*
4582
** CAPI3REF: Source Of Data In A Query Result
4583
** METHOD: sqlite3_stmt
4584
**
4585
** ^These routines provide a means to determine the database, table, and
4586
** table column that is the origin of a particular result column in
4587
** [SELECT] statement.
4588
** ^The name of the database or table or column can be returned as
4589
** either a UTF-8 or UTF-16 string.  ^The _database_ routines return
4590
** the database name, the _table_ routines return the table name, and
4591
** the origin_ routines return the column name.
4592
** ^The returned string is valid until the [prepared statement] is destroyed
4593
** using [sqlite3_finalize()] or until the statement is automatically
4594
** reprepared by the first call to [sqlite3_step()] for a particular run
4595
** or until the same information is requested
4596
** again in a different encoding.
4597
**
4598
** ^The names returned are the original un-aliased names of the
4599
** database, table, and column.
4600
**
4601
** ^The first argument to these interfaces is a [prepared statement].
4602
** ^These functions return information about the Nth result column returned by
4603
** the statement, where N is the second function argument.
4604
** ^The left-most column is column 0 for these routines.
4605
**
4606
** ^If the Nth column returned by the statement is an expression or
4607
** subquery and is not a column value, then all of these functions return
4608
** NULL.  ^These routines might also return NULL if a memory allocation error
4609
** occurs.  ^Otherwise, they return the name of the attached database, table,
4610
** or column that query result column was extracted from.
4611
**
4612
** ^As with all other SQLite APIs, those whose names end with "16" return
4613
** UTF-16 encoded strings and the other functions return UTF-8.
4614
**
4615
** ^These APIs are only available if the library was compiled with the
4616
** [SQLITE_ENABLE_COLUMN_METADATA] C-preprocessor symbol.
4617
**
4618
** If two or more threads call one or more
4619
** [sqlite3_column_database_name | column metadata interfaces]
4620
** for the same [prepared statement] and result column
4621
** at the same time then the results are undefined.
4622
*/
4623
SQLITE_API const char *sqlite3_column_database_name(sqlite3_stmt*,int);
4624
SQLITE_API const void *sqlite3_column_database_name16(sqlite3_stmt*,int);
4625
SQLITE_API const char *sqlite3_column_table_name(sqlite3_stmt*,int);
4626
SQLITE_API const void *sqlite3_column_table_name16(sqlite3_stmt*,int);
4627
SQLITE_API const char *sqlite3_column_origin_name(sqlite3_stmt*,int);
4628
SQLITE_API const void *sqlite3_column_origin_name16(sqlite3_stmt*,int);
4629
4630
/*
4631
** CAPI3REF: Declared Datatype Of A Query Result
4632
** METHOD: sqlite3_stmt
4633
**
4634
** ^(The first parameter is a [prepared statement].
4635
** If this statement is a [SELECT] statement and the Nth column of the
4636
** returned result set of that [SELECT] is a table column (not an
4637
** expression or subquery) then the declared type of the table
4638
** column is returned.)^  ^If the Nth column of the result set is an
4639
** expression or subquery, then a NULL pointer is returned.
4640
** ^The returned string is always UTF-8 encoded.
4641
**
4642
** ^(For example, given the database schema:
4643
**
4644
** CREATE TABLE t1(c1 VARIANT);
4645
**
4646
** and the following statement to be compiled:
4647
**
4648
** SELECT c1 + 1, c1 FROM t1;
4649
**
4650
** this routine would return the string "VARIANT" for the second result
4651
** column (i==1), and a NULL pointer for the first result column (i==0).)^
4652
**
4653
** ^SQLite uses dynamic run-time typing.  ^So just because a column
4654
** is declared to contain a particular type does not mean that the
4655
** data stored in that column is of the declared type.  SQLite is
4656
** strongly typed, but the typing is dynamic not static.  ^Type
4657
** is associated with individual values, not with the containers
4658
** used to hold those values.
4659
*/
4660
SQLITE_API const char *sqlite3_column_decltype(sqlite3_stmt*,int);
4661
SQLITE_API const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
4662
4663
/*
4664
** CAPI3REF: Evaluate An SQL Statement
4665
** METHOD: sqlite3_stmt
4666
**
4667
** After a [prepared statement] has been prepared using any of
4668
** [sqlite3_prepare_v2()], [sqlite3_prepare_v3()], [sqlite3_prepare16_v2()],
4669
** or [sqlite3_prepare16_v3()] or one of the legacy
4670
** interfaces [sqlite3_prepare()] or [sqlite3_prepare16()], this function
4671
** must be called one or more times to evaluate the statement.
4672
**
4673
** The details of the behavior of the sqlite3_step() interface depend
4674
** on whether the statement was prepared using the newer "vX" interfaces
4675
** [sqlite3_prepare_v3()], [sqlite3_prepare_v2()], [sqlite3_prepare16_v3()],
4676
** [sqlite3_prepare16_v2()] or the older legacy
4677
** interfaces [sqlite3_prepare()] and [sqlite3_prepare16()].  The use of the
4678
** new "vX" interface is recommended for new applications but the legacy
4679
** interface will continue to be supported.
4680
**
4681
** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
4682
** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE].
4683
** ^With the "v2" interface, any of the other [result codes] or
4684
** [extended result codes] might be returned as well.
4685
**
4686
** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
4687
** database locks it needs to do its job.  ^If the statement is a [COMMIT]
4688
** or occurs outside of an explicit transaction, then you can retry the
4689
** statement.  If the statement is not a [COMMIT] and occurs within an
4690
** explicit transaction then you should rollback the transaction before
4691
** continuing.
4692
**
4693
** ^[SQLITE_DONE] means that the statement has finished executing
4694
** successfully.  sqlite3_step() should not be called again on this virtual
4695
** machine without first calling [sqlite3_reset()] to reset the virtual
4696
** machine back to its initial state.
4697
**
4698
** ^If the SQL statement being executed returns any data, then [SQLITE_ROW]
4699
** is returned each time a new row of data is ready for processing by the
4700
** caller. The values may be accessed using the [column access functions].
4701
** sqlite3_step() is called again to retrieve the next row of data.
4702
**
4703
** ^[SQLITE_ERROR] means that a run-time error (such as a constraint
4704
** violation) has occurred.  sqlite3_step() should not be called again on
4705
** the VM. More information may be found by calling [sqlite3_errmsg()].
4706
** ^With the legacy interface, a more specific error code (for example,
4707
** [SQLITE_INTERRUPT], [SQLITE_SCHEMA], [SQLITE_CORRUPT], and so forth)
4708
** can be obtained by calling [sqlite3_reset()] on the
4709
** [prepared statement].  ^In the "v2" interface,
4710
** the more specific error code is returned directly by sqlite3_step().
4711
**
4712
** [SQLITE_MISUSE] means that the this routine was called inappropriately.
4713
** Perhaps it was called on a [prepared statement] that has
4714
** already been [sqlite3_finalize | finalized] or on one that had
4715
** previously returned [SQLITE_ERROR] or [SQLITE_DONE].  Or it could
4716
** be the case that the same database connection is being used by two or
4717
** more threads at the same moment in time.
4718
**
4719
** For all versions of SQLite up to and including 3.6.23.1, a call to
4720
** [sqlite3_reset()] was required after sqlite3_step() returned anything
4721
** other than [SQLITE_ROW] before any subsequent invocation of
4722
** sqlite3_step().  Failure to reset the prepared statement using
4723
** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from
4724
** sqlite3_step().  But after [version 3.6.23.1] ([dateof:3.6.23.1],
4725
** sqlite3_step() began
4726
** calling [sqlite3_reset()] automatically in this circumstance rather
4727
** than returning [SQLITE_MISUSE].  This is not considered a compatibility
4728
** break because any application that ever receives an SQLITE_MISUSE error
4729
** is broken by definition.  The [SQLITE_OMIT_AUTORESET] compile-time option
4730
** can be used to restore the legacy behavior.
4731
**
4732
** <b>Goofy Interface Alert:</b> In the legacy interface, the sqlite3_step()
4733
** API always returns a generic error code, [SQLITE_ERROR], following any
4734
** error other than [SQLITE_BUSY] and [SQLITE_MISUSE].  You must call
4735
** [sqlite3_reset()] or [sqlite3_finalize()] in order to find one of the
4736
** specific [error codes] that better describes the error.
4737
** We admit that this is a goofy design.  The problem has been fixed
4738
** with the "v2" interface.  If you prepare all of your SQL statements
4739
** using [sqlite3_prepare_v3()] or [sqlite3_prepare_v2()]
4740
** or [sqlite3_prepare16_v2()] or [sqlite3_prepare16_v3()] instead
4741
** of the legacy [sqlite3_prepare()] and [sqlite3_prepare16()] interfaces,
4742
** then the more specific [error codes] are returned directly
4743
** by sqlite3_step().  The use of the "vX" interfaces is recommended.
4744
*/
4745
SQLITE_API int sqlite3_step(sqlite3_stmt*);
4746
4747
/*
4748
** CAPI3REF: Number of columns in a result set
4749
** METHOD: sqlite3_stmt
4750
**
4751
** ^The sqlite3_data_count(P) interface returns the number of columns in the
4752
** current row of the result set of [prepared statement] P.
4753
** ^If prepared statement P does not have results ready to return
4754
** (via calls to the [sqlite3_column_int | sqlite3_column()] family of
4755
** interfaces) then sqlite3_data_count(P) returns 0.
4756
** ^The sqlite3_data_count(P) routine also returns 0 if P is a NULL pointer.
4757
** ^The sqlite3_data_count(P) routine returns 0 if the previous call to
4758
** [sqlite3_step](P) returned [SQLITE_DONE].  ^The sqlite3_data_count(P)
4759
** will return non-zero if previous call to [sqlite3_step](P) returned
4760
** [SQLITE_ROW], except in the case of the [PRAGMA incremental_vacuum]
4761
** where it always returns zero since each step of that multi-step
4762
** pragma returns 0 columns of data.
4763
**
4764
** See also: [sqlite3_column_count()]
4765
*/
4766
SQLITE_API int sqlite3_data_count(sqlite3_stmt *pStmt);
4767
4768
/*
4769
** CAPI3REF: Fundamental Datatypes
4770
** KEYWORDS: SQLITE_TEXT
4771
**
4772
** ^(Every value in SQLite has one of five fundamental datatypes:
4773
**
4774
** <ul>
4775
** <li> 64-bit signed integer
4776
** <li> 64-bit IEEE floating point number
4777
** <li> string
4778
** <li> BLOB
4779
** <li> NULL
4780
** </ul>)^
4781
**
4782
** These constants are codes for each of those types.
4783
**
4784
** Note that the SQLITE_TEXT constant was also used in SQLite version 2
4785
** for a completely different meaning.  Software that links against both
4786
** SQLite version 2 and SQLite version 3 should use SQLITE3_TEXT, not
4787
** SQLITE_TEXT.
4788
*/
4789
#define SQLITE_INTEGER  1
4790
#define SQLITE_FLOAT    2
4791
#define SQLITE_BLOB     4
4792
#define SQLITE_NULL     5
4793
#ifdef SQLITE_TEXT
4794
# undef SQLITE_TEXT
4795
#else
4796
# define SQLITE_TEXT     3
4797
#endif
4798
#define SQLITE3_TEXT     3
4799
4800
/*
4801
** CAPI3REF: Result Values From A Query
4802
** KEYWORDS: {column access functions}
4803
** METHOD: sqlite3_stmt
4804
**
4805
** <b>Summary:</b>
4806
** <blockquote><table border=0 cellpadding=0 cellspacing=0>
4807
** <tr><td><b>sqlite3_column_blob</b><td>&rarr;<td>BLOB result
4808
** <tr><td><b>sqlite3_column_double</b><td>&rarr;<td>REAL result
4809
** <tr><td><b>sqlite3_column_int</b><td>&rarr;<td>32-bit INTEGER result
4810
** <tr><td><b>sqlite3_column_int64</b><td>&rarr;<td>64-bit INTEGER result
4811
** <tr><td><b>sqlite3_column_text</b><td>&rarr;<td>UTF-8 TEXT result
4812
** <tr><td><b>sqlite3_column_text16</b><td>&rarr;<td>UTF-16 TEXT result
4813
** <tr><td><b>sqlite3_column_value</b><td>&rarr;<td>The result as an
4814
** [sqlite3_value|unprotected sqlite3_value] object.
4815
** <tr><td>&nbsp;<td>&nbsp;<td>&nbsp;
4816
** <tr><td><b>sqlite3_column_bytes</b><td>&rarr;<td>Size of a BLOB
4817
** or a UTF-8 TEXT result in bytes
4818
** <tr><td><b>sqlite3_column_bytes16&nbsp;&nbsp;</b>
4819
** <td>&rarr;&nbsp;&nbsp;<td>Size of UTF-16
4820
** TEXT in bytes
4821
** <tr><td><b>sqlite3_column_type</b><td>&rarr;<td>Default
4822
** datatype of the result
4823
** </table></blockquote>
4824
**
4825
** <b>Details:</b>
4826
**
4827
** ^These routines return information about a single column of the current
4828
** result row of a query.  ^In every case the first argument is a pointer
4829
** to the [prepared statement] that is being evaluated (the [sqlite3_stmt*]
4830
** that was returned from [sqlite3_prepare_v2()] or one of its variants)
4831
** and the second argument is the index of the column for which information
4832
** should be returned. ^The leftmost column of the result set has the index 0.
4833
** ^The number of columns in the result can be determined using
4834
** [sqlite3_column_count()].
4835
**
4836
** If the SQL statement does not currently point to a valid row, or if the
4837
** column index is out of range, the result is undefined.
4838
** These routines may only be called when the most recent call to
4839
** [sqlite3_step()] has returned [SQLITE_ROW] and neither
4840
** [sqlite3_reset()] nor [sqlite3_finalize()] have been called subsequently.
4841
** If any of these routines are called after [sqlite3_reset()] or
4842
** [sqlite3_finalize()] or after [sqlite3_step()] has returned
4843
** something other than [SQLITE_ROW], the results are undefined.
4844
** If [sqlite3_step()] or [sqlite3_reset()] or [sqlite3_finalize()]
4845
** are called from a different thread while any of these routines
4846
** are pending, then the results are undefined.
4847
**
4848
** The first six interfaces (_blob, _double, _int, _int64, _text, and _text16)
4849
** each return the value of a result column in a specific data format.  If
4850
** the result column is not initially in the requested format (for example,
4851
** if the query returns an integer but the sqlite3_column_text() interface
4852
** is used to extract the value) then an automatic type conversion is performed.
4853
**
4854
** ^The sqlite3_column_type() routine returns the
4855
** [SQLITE_INTEGER | datatype code] for the initial data type
4856
** of the result column.  ^The returned value is one of [SQLITE_INTEGER],
4857
** [SQLITE_FLOAT], [SQLITE_TEXT], [SQLITE_BLOB], or [SQLITE_NULL].
4858
** The return value of sqlite3_column_type() can be used to decide which
4859
** of the first six interface should be used to extract the column value.
4860
** The value returned by sqlite3_column_type() is only meaningful if no
4861
** automatic type conversions have occurred for the value in question.
4862
** After a type conversion, the result of calling sqlite3_column_type()
4863
** is undefined, though harmless.  Future
4864
** versions of SQLite may change the behavior of sqlite3_column_type()
4865
** following a type conversion.
4866
**
4867
** If the result is a BLOB or a TEXT string, then the sqlite3_column_bytes()
4868
** or sqlite3_column_bytes16() interfaces can be used to determine the size
4869
** of that BLOB or string.
4870
**
4871
** ^If the result is a BLOB or UTF-8 string then the sqlite3_column_bytes()
4872
** routine returns the number of bytes in that BLOB or string.
4873
** ^If the result is a UTF-16 string, then sqlite3_column_bytes() converts
4874
** the string to UTF-8 and then returns the number of bytes.
4875
** ^If the result is a numeric value then sqlite3_column_bytes() uses
4876
** [sqlite3_snprintf()] to convert that value to a UTF-8 string and returns
4877
** the number of bytes in that string.
4878
** ^If the result is NULL, then sqlite3_column_bytes() returns zero.
4879
**
4880
** ^If the result is a BLOB or UTF-16 string then the sqlite3_column_bytes16()
4881
** routine returns the number of bytes in that BLOB or string.
4882
** ^If the result is a UTF-8 string, then sqlite3_column_bytes16() converts
4883
** the string to UTF-16 and then returns the number of bytes.
4884
** ^If the result is a numeric value then sqlite3_column_bytes16() uses
4885
** [sqlite3_snprintf()] to convert that value to a UTF-16 string and returns
4886
** the number of bytes in that string.
4887
** ^If the result is NULL, then sqlite3_column_bytes16() returns zero.
4888
**
4889
** ^The values returned by [sqlite3_column_bytes()] and
4890
** [sqlite3_column_bytes16()] do not include the zero terminators at the end
4891
** of the string.  ^For clarity: the values returned by
4892
** [sqlite3_column_bytes()] and [sqlite3_column_bytes16()] are the number of
4893
** bytes in the string, not the number of characters.
4894
**
4895
** ^Strings returned by sqlite3_column_text() and sqlite3_column_text16(),
4896
** even empty strings, are always zero-terminated.  ^The return
4897
** value from sqlite3_column_blob() for a zero-length BLOB is a NULL pointer.
4898
**
4899
** <b>Warning:</b> ^The object returned by [sqlite3_column_value()] is an
4900
** [unprotected sqlite3_value] object.  In a multithreaded environment,
4901
** an unprotected sqlite3_value object may only be used safely with
4902
** [sqlite3_bind_value()] and [sqlite3_result_value()].
4903
** If the [unprotected sqlite3_value] object returned by
4904
** [sqlite3_column_value()] is used in any other way, including calls
4905
** to routines like [sqlite3_value_int()], [sqlite3_value_text()],
4906
** or [sqlite3_value_bytes()], the behavior is not threadsafe.
4907
** Hence, the sqlite3_column_value() interface
4908
** is normally only useful within the implementation of
4909
** [application-defined SQL functions] or [virtual tables], not within
4910
** top-level application code.
4911
**
4912
** The these routines may attempt to convert the datatype of the result.
4913
** ^For example, if the internal representation is FLOAT and a text result
4914
** is requested, [sqlite3_snprintf()] is used internally to perform the
4915
** conversion automatically.  ^(The following table details the conversions
4916
** that are applied:
4917
**
4918
** <blockquote>
4919
** <table border="1">
4920
** <tr><th> Internal<br>Type <th> Requested<br>Type <th>  Conversion
4921
**
4922
** <tr><td>  NULL    <td> INTEGER   <td> Result is 0
4923
** <tr><td>  NULL    <td>  FLOAT    <td> Result is 0.0
4924
** <tr><td>  NULL    <td>   TEXT    <td> Result is a NULL pointer
4925
** <tr><td>  NULL    <td>   BLOB    <td> Result is a NULL pointer
4926
** <tr><td> INTEGER  <td>  FLOAT    <td> Convert from integer to float
4927
** <tr><td> INTEGER  <td>   TEXT    <td> ASCII rendering of the integer
4928
** <tr><td> INTEGER  <td>   BLOB    <td> Same as INTEGER->TEXT
4929
** <tr><td>  FLOAT   <td> INTEGER   <td> [CAST] to INTEGER
4930
** <tr><td>  FLOAT   <td>   TEXT    <td> ASCII rendering of the float
4931
** <tr><td>  FLOAT   <td>   BLOB    <td> [CAST] to BLOB
4932
** <tr><td>  TEXT    <td> INTEGER   <td> [CAST] to INTEGER
4933
** <tr><td>  TEXT    <td>  FLOAT    <td> [CAST] to REAL
4934
** <tr><td>  TEXT    <td>   BLOB    <td> No change
4935
** <tr><td>  BLOB    <td> INTEGER   <td> [CAST] to INTEGER
4936
** <tr><td>  BLOB    <td>  FLOAT    <td> [CAST] to REAL
4937
** <tr><td>  BLOB    <td>   TEXT    <td> Add a zero terminator if needed
4938
** </table>
4939
** </blockquote>)^
4940
**
4941
** Note that when type conversions occur, pointers returned by prior
4942
** calls to sqlite3_column_blob(), sqlite3_column_text(), and/or
4943
** sqlite3_column_text16() may be invalidated.
4944
** Type conversions and pointer invalidations might occur
4945
** in the following cases:
4946
**
4947
** <ul>
4948
** <li> The initial content is a BLOB and sqlite3_column_text() or
4949
**      sqlite3_column_text16() is called.  A zero-terminator might
4950
**      need to be added to the string.</li>
4951
** <li> The initial content is UTF-8 text and sqlite3_column_bytes16() or
4952
**      sqlite3_column_text16() is called.  The content must be converted
4953
**      to UTF-16.</li>
4954
** <li> The initial content is UTF-16 text and sqlite3_column_bytes() or
4955
**      sqlite3_column_text() is called.  The content must be converted
4956
**      to UTF-8.</li>
4957
** </ul>
4958
**
4959
** ^Conversions between UTF-16be and UTF-16le are always done in place and do
4960
** not invalidate a prior pointer, though of course the content of the buffer
4961
** that the prior pointer references will have been modified.  Other kinds
4962
** of conversion are done in place when it is possible, but sometimes they
4963
** are not possible and in those cases prior pointers are invalidated.
4964
**
4965
** The safest policy is to invoke these routines
4966
** in one of the following ways:
4967
**
4968
** <ul>
4969
**  <li>sqlite3_column_text() followed by sqlite3_column_bytes()</li>
4970
**  <li>sqlite3_column_blob() followed by sqlite3_column_bytes()</li>
4971
**  <li>sqlite3_column_text16() followed by sqlite3_column_bytes16()</li>
4972
** </ul>
4973
**
4974
** In other words, you should call sqlite3_column_text(),
4975
** sqlite3_column_blob(), or sqlite3_column_text16() first to force the result
4976
** into the desired format, then invoke sqlite3_column_bytes() or
4977
** sqlite3_column_bytes16() to find the size of the result.  Do not mix calls
4978
** to sqlite3_column_text() or sqlite3_column_blob() with calls to
4979
** sqlite3_column_bytes16(), and do not mix calls to sqlite3_column_text16()
4980
** with calls to sqlite3_column_bytes().
4981
**
4982
** ^The pointers returned are valid until a type conversion occurs as
4983
** described above, or until [sqlite3_step()] or [sqlite3_reset()] or
4984
** [sqlite3_finalize()] is called.  ^The memory space used to hold strings
4985
** and BLOBs is freed automatically.  Do not pass the pointers returned
4986
** from [sqlite3_column_blob()], [sqlite3_column_text()], etc. into
4987
** [sqlite3_free()].
4988
**
4989
** As long as the input parameters are correct, these routines will only
4990
** fail if an out-of-memory error occurs during a format conversion.
4991
** Only the following subset of interfaces are subject to out-of-memory
4992
** errors:
4993
**
4994
** <ul>
4995
** <li> sqlite3_column_blob()
4996
** <li> sqlite3_column_text()
4997
** <li> sqlite3_column_text16()
4998
** <li> sqlite3_column_bytes()
4999
** <li> sqlite3_column_bytes16()
5000
** </ul>
5001
**
5002
** If an out-of-memory error occurs, then the return value from these
5003
** routines is the same as if the column had contained an SQL NULL value.
5004
** Valid SQL NULL returns can be distinguished from out-of-memory errors
5005
** by invoking the [sqlite3_errcode()] immediately after the suspect
5006
** return value is obtained and before any
5007
** other SQLite interface is called on the same [database connection].
5008
*/
5009
SQLITE_API const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
5010
SQLITE_API double sqlite3_column_double(sqlite3_stmt*, int iCol);
5011
SQLITE_API int sqlite3_column_int(sqlite3_stmt*, int iCol);
5012
SQLITE_API sqlite3_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
5013
SQLITE_API const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
5014
SQLITE_API const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
5015
SQLITE_API sqlite3_value *sqlite3_column_value(sqlite3_stmt*, int iCol);
5016
SQLITE_API int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
5017
SQLITE_API int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
5018
SQLITE_API int sqlite3_column_type(sqlite3_stmt*, int iCol);
5019
5020
/*
5021
** CAPI3REF: Destroy A Prepared Statement Object
5022
** DESTRUCTOR: sqlite3_stmt
5023
**
5024
** ^The sqlite3_finalize() function is called to delete a [prepared statement].
5025
** ^If the most recent evaluation of the statement encountered no errors
5026
** or if the statement is never been evaluated, then sqlite3_finalize() returns
5027
** SQLITE_OK.  ^If the most recent evaluation of statement S failed, then
5028
** sqlite3_finalize(S) returns the appropriate [error code] or
5029
** [extended error code].
5030
**
5031
** ^The sqlite3_finalize(S) routine can be called at any point during
5032
** the life cycle of [prepared statement] S:
5033
** before statement S is ever evaluated, after
5034
** one or more calls to [sqlite3_reset()], or after any call
5035
** to [sqlite3_step()] regardless of whether or not the statement has
5036
** completed execution.
5037
**
5038
** ^Invoking sqlite3_finalize() on a NULL pointer is a harmless no-op.
5039
**
5040
** The application must finalize every [prepared statement] in order to avoid
5041
** resource leaks.  It is a grievous error for the application to try to use
5042
** a prepared statement after it has been finalized.  Any use of a prepared
5043
** statement after it has been finalized can result in undefined and
5044
** undesirable behavior such as segfaults and heap corruption.
5045
*/
5046
SQLITE_API int sqlite3_finalize(sqlite3_stmt *pStmt);
5047
5048
/*
5049
** CAPI3REF: Reset A Prepared Statement Object
5050
** METHOD: sqlite3_stmt
5051
**
5052
** The sqlite3_reset() function is called to reset a [prepared statement]
5053
** object back to its initial state, ready to be re-executed.
5054
** ^Any SQL statement variables that had values bound to them using
5055
** the [sqlite3_bind_blob | sqlite3_bind_*() API] retain their values.
5056
** Use [sqlite3_clear_bindings()] to reset the bindings.
5057
**
5058
** ^The [sqlite3_reset(S)] interface resets the [prepared statement] S
5059
** back to the beginning of its program.
5060
**
5061
** ^If the most recent call to [sqlite3_step(S)] for the
5062
** [prepared statement] S returned [SQLITE_ROW] or [SQLITE_DONE],
5063
** or if [sqlite3_step(S)] has never before been called on S,
5064
** then [sqlite3_reset(S)] returns [SQLITE_OK].
5065
**
5066
** ^If the most recent call to [sqlite3_step(S)] for the
5067
** [prepared statement] S indicated an error, then
5068
** [sqlite3_reset(S)] returns an appropriate [error code].
5069
**
5070
** ^The [sqlite3_reset(S)] interface does not change the values
5071
** of any [sqlite3_bind_blob|bindings] on the [prepared statement] S.
5072
*/
5073
SQLITE_API int sqlite3_reset(sqlite3_stmt *pStmt);
5074
5075
/*
5076
** CAPI3REF: Create Or Redefine SQL Functions
5077
** KEYWORDS: {function creation routines}
5078
** METHOD: sqlite3
5079
**
5080
** ^These functions (collectively known as "function creation routines")
5081
** are used to add SQL functions or aggregates or to redefine the behavior
5082
** of existing SQL functions or aggregates. The only differences between
5083
** the three "sqlite3_create_function*" routines are the text encoding
5084
** expected for the second parameter (the name of the function being
5085
** created) and the presence or absence of a destructor callback for
5086
** the application data pointer. Function sqlite3_create_window_function()
5087
** is similar, but allows the user to supply the extra callback functions
5088
** needed by [aggregate window functions].
5089
**
5090
** ^The first parameter is the [database connection] to which the SQL
5091
** function is to be added.  ^If an application uses more than one database
5092
** connection then application-defined SQL functions must be added
5093
** to each database connection separately.
5094
**
5095
** ^The second parameter is the name of the SQL function to be created or
5096
** redefined.  ^The length of the name is limited to 255 bytes in a UTF-8
5097
** representation, exclusive of the zero-terminator.  ^Note that the name
5098
** length limit is in UTF-8 bytes, not characters nor UTF-16 bytes.
5099
** ^Any attempt to create a function with a longer name
5100
** will result in [SQLITE_MISUSE] being returned.
5101
**
5102
** ^The third parameter (nArg)
5103
** is the number of arguments that the SQL function or
5104
** aggregate takes. ^If this parameter is -1, then the SQL function or
5105
** aggregate may take any number of arguments between 0 and the limit
5106
** set by [sqlite3_limit]([SQLITE_LIMIT_FUNCTION_ARG]).  If the third
5107
** parameter is less than -1 or greater than 127 then the behavior is
5108
** undefined.
5109
**
5110
** ^The fourth parameter, eTextRep, specifies what
5111
** [SQLITE_UTF8 | text encoding] this SQL function prefers for
5112
** its parameters.  The application should set this parameter to
5113
** [SQLITE_UTF16LE] if the function implementation invokes
5114
** [sqlite3_value_text16le()] on an input, or [SQLITE_UTF16BE] if the
5115
** implementation invokes [sqlite3_value_text16be()] on an input, or
5116
** [SQLITE_UTF16] if [sqlite3_value_text16()] is used, or [SQLITE_UTF8]
5117
** otherwise.  ^The same SQL function may be registered multiple times using
5118
** different preferred text encodings, with different implementations for
5119
** each encoding.
5120
** ^When multiple implementations of the same function are available, SQLite
5121
** will pick the one that involves the least amount of data conversion.
5122
**
5123
** ^The fourth parameter may optionally be ORed with [SQLITE_DETERMINISTIC]
5124
** to signal that the function will always return the same result given
5125
** the same inputs within a single SQL statement.  Most SQL functions are
5126
** deterministic.  The built-in [random()] SQL function is an example of a
5127
** function that is not deterministic.  The SQLite query planner is able to
5128
** perform additional optimizations on deterministic functions, so use
5129
** of the [SQLITE_DETERMINISTIC] flag is recommended where possible.
5130
**
5131
** ^The fourth parameter may also optionally include the [SQLITE_DIRECTONLY]
5132
** flag, which if present prevents the function from being invoked from
5133
** within VIEWs, TRIGGERs, CHECK constraints, generated column expressions,
5134
** index expressions, or the WHERE clause of partial indexes.
5135
**
5136
** For best security, the [SQLITE_DIRECTONLY] flag is recommended for
5137
** all application-defined SQL functions that do not need to be
5138
** used inside of triggers, view, CHECK constraints, or other elements of
5139
** the database schema.  This flags is especially recommended for SQL
5140
** functions that have side effects or reveal internal application state.
5141
** Without this flag, an attacker might be able to modify the schema of
5142
** a database file to include invocations of the function with parameters
5143
** chosen by the attacker, which the application will then execute when
5144
** the database file is opened and read.
5145
**
5146
** ^(The fifth parameter is an arbitrary pointer.  The implementation of the
5147
** function can gain access to this pointer using [sqlite3_user_data()].)^
5148
**
5149
** ^The sixth, seventh and eighth parameters passed to the three
5150
** "sqlite3_create_function*" functions, xFunc, xStep and xFinal, are
5151
** pointers to C-language functions that implement the SQL function or
5152
** aggregate. ^A scalar SQL function requires an implementation of the xFunc
5153
** callback only; NULL pointers must be passed as the xStep and xFinal
5154
** parameters. ^An aggregate SQL function requires an implementation of xStep
5155
** and xFinal and NULL pointer must be passed for xFunc. ^To delete an existing
5156
** SQL function or aggregate, pass NULL pointers for all three function
5157
** callbacks.
5158
**
5159
** ^The sixth, seventh, eighth and ninth parameters (xStep, xFinal, xValue
5160
** and xInverse) passed to sqlite3_create_window_function are pointers to
5161
** C-language callbacks that implement the new function. xStep and xFinal
5162
** must both be non-NULL. xValue and xInverse may either both be NULL, in
5163
** which case a regular aggregate function is created, or must both be
5164
** non-NULL, in which case the new function may be used as either an aggregate
5165
** or aggregate window function. More details regarding the implementation
5166
** of aggregate window functions are
5167
** [user-defined window functions|available here].
5168
**
5169
** ^(If the final parameter to sqlite3_create_function_v2() or
5170
** sqlite3_create_window_function() is not NULL, then it is destructor for
5171
** the application data pointer. The destructor is invoked when the function
5172
** is deleted, either by being overloaded or when the database connection
5173
** closes.)^ ^The destructor is also invoked if the call to
5174
** sqlite3_create_function_v2() fails.  ^When the destructor callback is
5175
** invoked, it is passed a single argument which is a copy of the application
5176
** data pointer which was the fifth parameter to sqlite3_create_function_v2().
5177
**
5178
** ^It is permitted to register multiple implementations of the same
5179
** functions with the same name but with either differing numbers of
5180
** arguments or differing preferred text encodings.  ^SQLite will use
5181
** the implementation that most closely matches the way in which the
5182
** SQL function is used.  ^A function implementation with a non-negative
5183
** nArg parameter is a better match than a function implementation with
5184
** a negative nArg.  ^A function where the preferred text encoding
5185
** matches the database encoding is a better
5186
** match than a function where the encoding is different.
5187
** ^A function where the encoding difference is between UTF16le and UTF16be
5188
** is a closer match than a function where the encoding difference is
5189
** between UTF8 and UTF16.
5190
**
5191
** ^Built-in functions may be overloaded by new application-defined functions.
5192
**
5193
** ^An application-defined function is permitted to call other
5194
** SQLite interfaces.  However, such calls must not
5195
** close the database connection nor finalize or reset the prepared
5196
** statement in which the function is running.
5197
*/
5198
SQLITE_API int sqlite3_create_function(
5199
  sqlite3 *db,
5200
  const char *zFunctionName,
5201
  int nArg,
5202
  int eTextRep,
5203
  void *pApp,