blob: d2ea460f60701e93fd3023a5336b0732940bc4e1 [file] [log] [blame]
drh75897232000-05-29 14:26:00 +00001/*
drhb19a2bc2001-09-16 00:13:26 +00002** 2001 September 15
drh75897232000-05-29 14:26:00 +00003**
drhb19a2bc2001-09-16 00:13:26 +00004** The author disclaims copyright to this source code. In place of
5** a legal notice, here is a blessing:
drh75897232000-05-29 14:26:00 +00006**
drhb19a2bc2001-09-16 00:13:26 +00007** 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.
drh75897232000-05-29 14:26:00 +000010**
11*************************************************************************
drhb19a2bc2001-09-16 00:13:26 +000012** This header file defines the interface that the SQLite library
drh6ed48bf2007-06-14 20:57:18 +000013** 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.
drh75897232000-05-29 14:26:00 +000017**
drh6ed48bf2007-06-14 20:57:18 +000018** Some of the definitions that are in this file are marked as
19** "experimental". Experimental interfaces are normally new
mihailima3f64902008-06-21 13:35:56 +000020** features recently added to SQLite. We do not anticipate changes
shane7c7c3112009-08-17 15:31:23 +000021** to experimental interfaces but reserve the right to make minor changes
22** if experience from use "in the wild" suggest such changes are prudent.
drh6ed48bf2007-06-14 20:57:18 +000023**
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 suppose 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.
drh75897232000-05-29 14:26:00 +000032*/
drh12057d52004-09-06 17:34:12 +000033#ifndef _SQLITE3_H_
34#define _SQLITE3_H_
drha18c5682000-10-08 22:20:57 +000035#include <stdarg.h> /* Needed for the definition of va_list */
drh75897232000-05-29 14:26:00 +000036
37/*
drh382c0242001-10-06 16:33:02 +000038** Make sure we can call this stuff from C++.
39*/
40#ifdef __cplusplus
41extern "C" {
42#endif
43
drh6d2069d2007-08-14 01:58:53 +000044
drh382c0242001-10-06 16:33:02 +000045/*
drh73be5012007-08-08 12:11:21 +000046** Add the ability to override 'extern'
47*/
48#ifndef SQLITE_EXTERN
49# define SQLITE_EXTERN extern
50#endif
51
52/*
drh4d6618f2008-09-22 17:54:46 +000053** These no-op macros are used in front of interfaces to mark those
54** interfaces as either deprecated or experimental. New applications
shane7c7c3112009-08-17 15:31:23 +000055** should not use deprecated interfaces - they are support for backwards
drh4d6618f2008-09-22 17:54:46 +000056** compatibility only. Application writers should be aware that
57** experimental interfaces are subject to change in point releases.
58**
59** These macros used to resolve to various kinds of compiler magic that
60** would generate warning messages when they were used. But that
61** compiler magic ended up generating such a flurry of bug reports
62** that we have taken it all out and gone back to using simple
63** noop macros.
shanea79c3cc2008-08-11 17:27:01 +000064*/
drh4d6618f2008-09-22 17:54:46 +000065#define SQLITE_DEPRECATED
66#define SQLITE_EXPERIMENTAL
shanea79c3cc2008-08-11 17:27:01 +000067
68/*
mihailim362cc832008-06-21 06:16:42 +000069** Ensure these symbols were not defined by some previous header file.
drhb86ccfb2003-01-28 23:13:10 +000070*/
drh1e284f42004-10-06 15:52:01 +000071#ifdef SQLITE_VERSION
72# undef SQLITE_VERSION
drh1e284f42004-10-06 15:52:01 +000073#endif
drh6ed48bf2007-06-14 20:57:18 +000074#ifdef SQLITE_VERSION_NUMBER
75# undef SQLITE_VERSION_NUMBER
76#endif
danielk197799ba19e2005-02-05 07:33:34 +000077
78/*
drh1e15c032009-12-08 15:16:54 +000079** CAPI3REF: Compile-Time Library Version Numbers
drh6ed48bf2007-06-14 20:57:18 +000080**
drh1e15c032009-12-08 15:16:54 +000081** ^(The [SQLITE_VERSION] C preprocessor macro in the sqlite3.h header
82** evaluates to a string literal that is the SQLite version in the
83** format "X.Y.Z" where X is the major version number (always 3 for
84** SQLite3) and Y is the minor version number and Z is the release number.)^
85** ^(The [SQLITE_VERSION_NUMBER] C preprocessor macro resolves to an integer
86** with the value (X*1000000 + Y*1000 + Z) where X, Y, and Z are the same
87** numbers used in [SQLITE_VERSION].)^
88** The SQLITE_VERSION_NUMBER for any given release of SQLite will also
89** be larger than the release from which it is derived. Either Y will
90** be held constant and Z will be incremented or else Y will be incremented
91** and Z will be reset to zero.
drh6aa5f152009-08-19 15:57:07 +000092**
drh47baebc2009-08-14 16:01:24 +000093** Since version 3.6.18, SQLite source code has been stored in the
drh1e15c032009-12-08 15:16:54 +000094** <a href="http://www.fossil-scm.org/">Fossil configuration management
drh9b8d0272010-08-09 15:44:21 +000095** system</a>. ^The SQLITE_SOURCE_ID macro evaluates to
drh1e15c032009-12-08 15:16:54 +000096** a string which identifies a particular check-in of SQLite
97** within its configuration management system. ^The SQLITE_SOURCE_ID
98** string contains the date and time of the check-in (UTC) and an SHA1
99** hash of the entire source tree.
drh47baebc2009-08-14 16:01:24 +0000100**
drh6aa5f152009-08-19 15:57:07 +0000101** See also: [sqlite3_libversion()],
drh4e0b31c2009-09-02 19:04:24 +0000102** [sqlite3_libversion_number()], [sqlite3_sourceid()],
103** [sqlite_version()] and [sqlite_source_id()].
danielk197799ba19e2005-02-05 07:33:34 +0000104*/
drh47baebc2009-08-14 16:01:24 +0000105#define SQLITE_VERSION "--VERS--"
106#define SQLITE_VERSION_NUMBER --VERSION-NUMBER--
107#define SQLITE_SOURCE_ID "--SOURCE-ID--"
drhb86ccfb2003-01-28 23:13:10 +0000108
109/*
drh1e15c032009-12-08 15:16:54 +0000110** CAPI3REF: Run-Time Library Version Numbers
shanehdc97a8c2010-02-23 20:08:35 +0000111** KEYWORDS: sqlite3_version, sqlite3_sourceid
drh6ed48bf2007-06-14 20:57:18 +0000112**
drh47baebc2009-08-14 16:01:24 +0000113** These interfaces provide the same information as the [SQLITE_VERSION],
drh1e15c032009-12-08 15:16:54 +0000114** [SQLITE_VERSION_NUMBER], and [SQLITE_SOURCE_ID] C preprocessor macros
drhd68eee02009-12-11 03:44:18 +0000115** but are associated with the library instead of the header file. ^(Cautious
drh4e0b31c2009-09-02 19:04:24 +0000116** programmers might include assert() statements in their application to
117** verify that values returned by these interfaces match the macros in
118** the header, and thus insure that the application is
drh6aa5f152009-08-19 15:57:07 +0000119** compiled with matching library and header files.
120**
121** <blockquote><pre>
122** assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER );
drh4e0b31c2009-09-02 19:04:24 +0000123** assert( strcmp(sqlite3_sourceid(),SQLITE_SOURCE_ID)==0 );
drh1e15c032009-12-08 15:16:54 +0000124** assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0 );
drhd68eee02009-12-11 03:44:18 +0000125** </pre></blockquote>)^
drh6ed48bf2007-06-14 20:57:18 +0000126**
drh1e15c032009-12-08 15:16:54 +0000127** ^The sqlite3_version[] string constant contains the text of [SQLITE_VERSION]
128** macro. ^The sqlite3_libversion() function returns a pointer to the
129** to the sqlite3_version[] string constant. The sqlite3_libversion()
130** function is provided for use in DLLs since DLL users usually do not have
131** direct access to string constants within the DLL. ^The
132** sqlite3_libversion_number() function returns an integer equal to
shanehbdea6d12010-02-23 04:19:54 +0000133** [SQLITE_VERSION_NUMBER]. ^The sqlite3_sourceid() function returns
134** a pointer to a string constant whose value is the same as the
shanehdc97a8c2010-02-23 20:08:35 +0000135** [SQLITE_SOURCE_ID] C preprocessor macro.
drh33c1be32008-01-30 16:16:14 +0000136**
drh4e0b31c2009-09-02 19:04:24 +0000137** See also: [sqlite_version()] and [sqlite_source_id()].
drhb217a572000-08-22 13:40:18 +0000138*/
drh73be5012007-08-08 12:11:21 +0000139SQLITE_EXTERN const char sqlite3_version[];
drha3f70cb2004-09-30 14:24:50 +0000140const char *sqlite3_libversion(void);
drh47baebc2009-08-14 16:01:24 +0000141const char *sqlite3_sourceid(void);
danielk197799ba19e2005-02-05 07:33:34 +0000142int sqlite3_libversion_number(void);
143
144/*
shanehdc97a8c2010-02-23 20:08:35 +0000145** CAPI3REF: Run-Time Library Compilation Options Diagnostics
shanehdc97a8c2010-02-23 20:08:35 +0000146**
147** ^The sqlite3_compileoption_used() function returns 0 or 1
148** indicating whether the specified option was defined at
149** compile time. ^The SQLITE_ prefix may be omitted from the
150** option name passed to sqlite3_compileoption_used().
151**
drh9b8d0272010-08-09 15:44:21 +0000152** ^The sqlite3_compileoption_get() function allows iterating
shanehdc97a8c2010-02-23 20:08:35 +0000153** over the list of options that were defined at compile time by
154** returning the N-th compile time option string. ^If N is out of range,
155** sqlite3_compileoption_get() returns a NULL pointer. ^The SQLITE_
156** prefix is omitted from any strings returned by
157** sqlite3_compileoption_get().
158**
159** ^Support for the diagnostic functions sqlite3_compileoption_used()
drh9b8d0272010-08-09 15:44:21 +0000160** and sqlite3_compileoption_get() may be omitted by specifying the
drh71caabf2010-02-26 15:39:24 +0000161** [SQLITE_OMIT_COMPILEOPTION_DIAGS] option at compile time.
shanehdc97a8c2010-02-23 20:08:35 +0000162**
drh71caabf2010-02-26 15:39:24 +0000163** See also: SQL functions [sqlite_compileoption_used()] and
164** [sqlite_compileoption_get()] and the [compile_options pragma].
shanehdc97a8c2010-02-23 20:08:35 +0000165*/
dan98f0c362010-03-22 04:32:13 +0000166#ifndef SQLITE_OMIT_COMPILEOPTION_DIAGS
shanehdc97a8c2010-02-23 20:08:35 +0000167int sqlite3_compileoption_used(const char *zOptName);
drh380083c2010-02-23 20:32:15 +0000168const char *sqlite3_compileoption_get(int N);
dan98f0c362010-03-22 04:32:13 +0000169#endif
drhefad9992004-06-22 12:13:55 +0000170
drh75897232000-05-29 14:26:00 +0000171/*
drhd68eee02009-12-11 03:44:18 +0000172** CAPI3REF: Test To See If The Library Is Threadsafe
173**
174** ^The sqlite3_threadsafe() function returns zero if and only if
175** SQLite was compiled mutexing code omitted due to the
176** [SQLITE_THREADSAFE] compile-time option being set to 0.
drhb67e8bf2007-08-30 20:09:48 +0000177**
drh33c1be32008-01-30 16:16:14 +0000178** SQLite can be compiled with or without mutexes. When
drh6aa5f152009-08-19 15:57:07 +0000179** the [SQLITE_THREADSAFE] C preprocessor macro is 1 or 2, mutexes
drhafacce02008-09-02 21:35:03 +0000180** are enabled and SQLite is threadsafe. When the
181** [SQLITE_THREADSAFE] macro is 0,
drh33c1be32008-01-30 16:16:14 +0000182** the mutexes are omitted. Without the mutexes, it is not safe
mihailim362cc832008-06-21 06:16:42 +0000183** to use SQLite concurrently from more than one thread.
drhb67e8bf2007-08-30 20:09:48 +0000184**
mihailim362cc832008-06-21 06:16:42 +0000185** Enabling mutexes incurs a measurable performance penalty.
drh33c1be32008-01-30 16:16:14 +0000186** So if speed is of utmost importance, it makes sense to disable
187** the mutexes. But for maximum safety, mutexes should be enabled.
drhd68eee02009-12-11 03:44:18 +0000188** ^The default behavior is for mutexes to be enabled.
drh33c1be32008-01-30 16:16:14 +0000189**
drh6aa5f152009-08-19 15:57:07 +0000190** This interface can be used by an application to make sure that the
drh33c1be32008-01-30 16:16:14 +0000191** version of SQLite that it is linking against was compiled with
drh4766b292008-06-26 02:53:02 +0000192** the desired setting of the [SQLITE_THREADSAFE] macro.
193**
194** This interface only reports on the compile-time mutex setting
195** of the [SQLITE_THREADSAFE] flag. If SQLite is compiled with
drhd68eee02009-12-11 03:44:18 +0000196** SQLITE_THREADSAFE=1 or =2 then mutexes are enabled by default but
drh4766b292008-06-26 02:53:02 +0000197** can be fully or partially disabled using a call to [sqlite3_config()]
198** with the verbs [SQLITE_CONFIG_SINGLETHREAD], [SQLITE_CONFIG_MULTITHREAD],
drhd68eee02009-12-11 03:44:18 +0000199** or [SQLITE_CONFIG_MUTEX]. ^(The return value of the
200** sqlite3_threadsafe() function shows only the compile-time setting of
201** thread safety, not any run-time changes to that setting made by
202** sqlite3_config(). In other words, the return value from sqlite3_threadsafe()
203** is unchanged by calls to sqlite3_config().)^
drh33c1be32008-01-30 16:16:14 +0000204**
drhafacce02008-09-02 21:35:03 +0000205** See the [threading mode] documentation for additional information.
drhb67e8bf2007-08-30 20:09:48 +0000206*/
207int sqlite3_threadsafe(void);
208
209/*
drhd68eee02009-12-11 03:44:18 +0000210** CAPI3REF: Database Connection Handle
drha06f17f2008-05-11 11:07:06 +0000211** KEYWORDS: {database connection} {database connections}
drh6ed48bf2007-06-14 20:57:18 +0000212**
mihailim362cc832008-06-21 06:16:42 +0000213** Each open SQLite database is represented by a pointer to an instance of
214** the opaque structure named "sqlite3". It is useful to think of an sqlite3
drh8bacf972007-08-25 16:21:29 +0000215** pointer as an object. The [sqlite3_open()], [sqlite3_open16()], and
mihailim362cc832008-06-21 06:16:42 +0000216** [sqlite3_open_v2()] interfaces are its constructors, and [sqlite3_close()]
217** is its destructor. There are many other interfaces (such as
218** [sqlite3_prepare_v2()], [sqlite3_create_function()], and
219** [sqlite3_busy_timeout()] to name but three) that are methods on an
220** sqlite3 object.
drh75897232000-05-29 14:26:00 +0000221*/
222typedef struct sqlite3 sqlite3;
223
drh75897232000-05-29 14:26:00 +0000224/*
drhd68eee02009-12-11 03:44:18 +0000225** CAPI3REF: 64-Bit Integer Types
drh33c1be32008-01-30 16:16:14 +0000226** KEYWORDS: sqlite_int64 sqlite_uint64
drh6ed48bf2007-06-14 20:57:18 +0000227**
drh33c1be32008-01-30 16:16:14 +0000228** Because there is no cross-platform way to specify 64-bit integer types
drhfddfa2d2007-12-05 18:05:16 +0000229** SQLite includes typedefs for 64-bit signed and unsigned integers.
drh6ed48bf2007-06-14 20:57:18 +0000230**
mihailim362cc832008-06-21 06:16:42 +0000231** The sqlite3_int64 and sqlite3_uint64 are the preferred type definitions.
232** The sqlite_int64 and sqlite_uint64 types are supported for backwards
233** compatibility only.
drh33c1be32008-01-30 16:16:14 +0000234**
drhd68eee02009-12-11 03:44:18 +0000235** ^The sqlite3_int64 and sqlite_int64 types can store integer values
236** between -9223372036854775808 and +9223372036854775807 inclusive. ^The
237** sqlite3_uint64 and sqlite_uint64 types can store integer values
238** between 0 and +18446744073709551615 inclusive.
drh75897232000-05-29 14:26:00 +0000239*/
drh27436af2006-03-28 23:57:17 +0000240#ifdef SQLITE_INT64_TYPE
drh9b8f4472006-04-04 01:54:55 +0000241 typedef SQLITE_INT64_TYPE sqlite_int64;
drh27436af2006-03-28 23:57:17 +0000242 typedef unsigned SQLITE_INT64_TYPE sqlite_uint64;
243#elif defined(_MSC_VER) || defined(__BORLANDC__)
drh75897232000-05-29 14:26:00 +0000244 typedef __int64 sqlite_int64;
245 typedef unsigned __int64 sqlite_uint64;
246#else
247 typedef long long int sqlite_int64;
248 typedef unsigned long long int sqlite_uint64;
249#endif
drh6d2069d2007-08-14 01:58:53 +0000250typedef sqlite_int64 sqlite3_int64;
251typedef sqlite_uint64 sqlite3_uint64;
drh75897232000-05-29 14:26:00 +0000252
drhb37df7b2005-10-13 02:09:49 +0000253/*
254** If compiling for a processor that lacks floating point support,
mihailim362cc832008-06-21 06:16:42 +0000255** substitute integer for floating-point.
drhb37df7b2005-10-13 02:09:49 +0000256*/
257#ifdef SQLITE_OMIT_FLOATING_POINT
drh6d2069d2007-08-14 01:58:53 +0000258# define double sqlite3_int64
drhb37df7b2005-10-13 02:09:49 +0000259#endif
drh75897232000-05-29 14:26:00 +0000260
261/*
drhd68eee02009-12-11 03:44:18 +0000262** CAPI3REF: Closing A Database Connection
drh75897232000-05-29 14:26:00 +0000263**
drhd68eee02009-12-11 03:44:18 +0000264** ^The sqlite3_close() routine is the destructor for the [sqlite3] object.
265** ^Calls to sqlite3_close() return SQLITE_OK if the [sqlite3] object is
drh9b8d0272010-08-09 15:44:21 +0000266** successfully destroyed and all associated resources are deallocated.
drh33c1be32008-01-30 16:16:14 +0000267**
drh7db29fb2009-10-20 14:23:09 +0000268** Applications must [sqlite3_finalize | finalize] all [prepared statements]
mihailim15194222008-06-22 09:55:14 +0000269** and [sqlite3_blob_close | close] all [BLOB handles] associated with
drhd68eee02009-12-11 03:44:18 +0000270** the [sqlite3] object prior to attempting to close the object. ^If
271** sqlite3_close() is called on a [database connection] that still has
272** outstanding [prepared statements] or [BLOB handles], then it returns
273** SQLITE_BUSY.
drh55b0cf02008-06-19 17:54:33 +0000274**
drhd68eee02009-12-11 03:44:18 +0000275** ^If [sqlite3_close()] is invoked while a transaction is open,
drh55b0cf02008-06-19 17:54:33 +0000276** the transaction is automatically rolled back.
drh33c1be32008-01-30 16:16:14 +0000277**
drh8b39db12009-02-18 18:37:58 +0000278** The C parameter to [sqlite3_close(C)] must be either a NULL
279** pointer or an [sqlite3] object pointer obtained
280** from [sqlite3_open()], [sqlite3_open16()], or
281** [sqlite3_open_v2()], and not previously closed.
drhd68eee02009-12-11 03:44:18 +0000282** ^Calling sqlite3_close() with a NULL pointer argument is a
283** harmless no-op.
drh75897232000-05-29 14:26:00 +0000284*/
danielk1977f9d64d22004-06-19 08:18:07 +0000285int sqlite3_close(sqlite3 *);
drh75897232000-05-29 14:26:00 +0000286
287/*
288** The type for a callback function.
drh6ed48bf2007-06-14 20:57:18 +0000289** This is legacy and deprecated. It is included for historical
290** compatibility and is not documented.
drh75897232000-05-29 14:26:00 +0000291*/
drh12057d52004-09-06 17:34:12 +0000292typedef int (*sqlite3_callback)(void*,int,char**, char**);
drh75897232000-05-29 14:26:00 +0000293
294/*
drhd68eee02009-12-11 03:44:18 +0000295** CAPI3REF: One-Step Query Execution Interface
drh6ed48bf2007-06-14 20:57:18 +0000296**
drhd68eee02009-12-11 03:44:18 +0000297** The sqlite3_exec() interface is a convenience wrapper around
298** [sqlite3_prepare_v2()], [sqlite3_step()], and [sqlite3_finalize()],
299** that allows an application to run multiple statements of SQL
300** without having to use a lot of C code.
drh75897232000-05-29 14:26:00 +0000301**
drhd68eee02009-12-11 03:44:18 +0000302** ^The sqlite3_exec() interface runs zero or more UTF-8 encoded,
303** semicolon-separate SQL statements passed into its 2nd argument,
304** in the context of the [database connection] passed in as its 1st
305** argument. ^If the callback function of the 3rd argument to
306** sqlite3_exec() is not NULL, then it is invoked for each result row
307** coming out of the evaluated SQL statements. ^The 4th argument to
308** to sqlite3_exec() is relayed through to the 1st argument of each
309** callback invocation. ^If the callback pointer to sqlite3_exec()
310** is NULL, then no callback is ever invoked and result rows are
311** ignored.
drh35c61902008-05-20 15:44:30 +0000312**
drhd68eee02009-12-11 03:44:18 +0000313** ^If an error occurs while evaluating the SQL statements passed into
314** sqlite3_exec(), then execution of the current statement stops and
315** subsequent statements are skipped. ^If the 5th parameter to sqlite3_exec()
316** is not NULL then any error message is written into memory obtained
317** from [sqlite3_malloc()] and passed back through the 5th parameter.
318** To avoid memory leaks, the application should invoke [sqlite3_free()]
319** on error message strings returned through the 5th parameter of
320** of sqlite3_exec() after the error message string is no longer needed.
321** ^If the 5th parameter to sqlite3_exec() is not NULL and no errors
322** occur, then sqlite3_exec() sets the pointer in its 5th parameter to
323** NULL before returning.
drh35c61902008-05-20 15:44:30 +0000324**
drhd68eee02009-12-11 03:44:18 +0000325** ^If an sqlite3_exec() callback returns non-zero, the sqlite3_exec()
326** routine returns SQLITE_ABORT without invoking the callback again and
327** without running any subsequent SQL statements.
drh75897232000-05-29 14:26:00 +0000328**
drhd68eee02009-12-11 03:44:18 +0000329** ^The 2nd argument to the sqlite3_exec() callback function is the
330** number of columns in the result. ^The 3rd argument to the sqlite3_exec()
331** callback is an array of pointers to strings obtained as if from
332** [sqlite3_column_text()], one for each column. ^If an element of a
333** result row is NULL then the corresponding string pointer for the
334** sqlite3_exec() callback is a NULL pointer. ^The 4th argument to the
335** sqlite3_exec() callback is an array of pointers to strings where each
336** entry represents the name of corresponding result column as obtained
337** from [sqlite3_column_name()].
mihailima3f64902008-06-21 13:35:56 +0000338**
drhd68eee02009-12-11 03:44:18 +0000339** ^If the 2nd parameter to sqlite3_exec() is a NULL pointer, a pointer
340** to an empty string, or a pointer that contains only whitespace and/or
341** SQL comments, then no SQL statements are evaluated and the database
342** is not changed.
drh75897232000-05-29 14:26:00 +0000343**
drhd68eee02009-12-11 03:44:18 +0000344** Restrictions:
drh75897232000-05-29 14:26:00 +0000345**
drhd68eee02009-12-11 03:44:18 +0000346** <ul>
347** <li> The application must insure that the 1st parameter to sqlite3_exec()
348** is a valid and open [database connection].
349** <li> The application must not close [database connection] specified by
350** the 1st parameter to sqlite3_exec() while sqlite3_exec() is running.
351** <li> The application must not modify the SQL statement text passed into
352** the 2nd parameter of sqlite3_exec() while sqlite3_exec() is running.
353** </ul>
drh75897232000-05-29 14:26:00 +0000354*/
danielk19776f8a5032004-05-10 10:34:51 +0000355int sqlite3_exec(
drh6ed48bf2007-06-14 20:57:18 +0000356 sqlite3*, /* An open database */
shane236ce972008-05-30 15:35:30 +0000357 const char *sql, /* SQL to be evaluated */
drh6ed48bf2007-06-14 20:57:18 +0000358 int (*callback)(void*,int,char**,char**), /* Callback function */
359 void *, /* 1st argument to callback */
360 char **errmsg /* Error msg written here */
drh75897232000-05-29 14:26:00 +0000361);
362
drh58b95762000-06-02 01:17:37 +0000363/*
drhd68eee02009-12-11 03:44:18 +0000364** CAPI3REF: Result Codes
drh33c1be32008-01-30 16:16:14 +0000365** KEYWORDS: SQLITE_OK {error code} {error codes}
mihailimefc8e8a2008-06-21 16:47:09 +0000366** KEYWORDS: {result code} {result codes}
drh6ed48bf2007-06-14 20:57:18 +0000367**
368** Many SQLite functions return an integer result code from the set shown
drh33c1be32008-01-30 16:16:14 +0000369** here in order to indicates success or failure.
drh6ed48bf2007-06-14 20:57:18 +0000370**
drh4766b292008-06-26 02:53:02 +0000371** New error codes may be added in future versions of SQLite.
372**
drh6ed48bf2007-06-14 20:57:18 +0000373** See also: [SQLITE_IOERR_READ | extended result codes]
drh58b95762000-06-02 01:17:37 +0000374*/
drh717e6402001-09-27 03:22:32 +0000375#define SQLITE_OK 0 /* Successful result */
drh15b9a152006-01-31 20:49:13 +0000376/* beginning-of-error-codes */
drh717e6402001-09-27 03:22:32 +0000377#define SQLITE_ERROR 1 /* SQL error or missing database */
drh89e0dde2007-12-12 12:25:21 +0000378#define SQLITE_INTERNAL 2 /* Internal logic error in SQLite */
drh717e6402001-09-27 03:22:32 +0000379#define SQLITE_PERM 3 /* Access permission denied */
380#define SQLITE_ABORT 4 /* Callback routine requested an abort */
381#define SQLITE_BUSY 5 /* The database file is locked */
382#define SQLITE_LOCKED 6 /* A table in the database is locked */
383#define SQLITE_NOMEM 7 /* A malloc() failed */
384#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000385#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000386#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
387#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
drh2db0bbc2005-08-11 02:10:18 +0000388#define SQLITE_NOTFOUND 12 /* NOT USED. Table or record not found */
drh717e6402001-09-27 03:22:32 +0000389#define SQLITE_FULL 13 /* Insertion failed because database is full */
390#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
drhaab4c022010-06-02 14:45:51 +0000391#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000392#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000393#define SQLITE_SCHEMA 17 /* The database schema changed */
drhc797d4d2007-05-08 01:08:49 +0000394#define SQLITE_TOOBIG 18 /* String or BLOB exceeds size limit */
danielk19776eb91d22007-09-21 04:27:02 +0000395#define SQLITE_CONSTRAINT 19 /* Abort due to constraint violation */
drh8aff1012001-12-22 14:49:24 +0000396#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000397#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000398#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000399#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000400#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000401#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000402#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000403#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
404#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh15b9a152006-01-31 20:49:13 +0000405/* end-of-error-codes */
drh717e6402001-09-27 03:22:32 +0000406
drhaf9ff332002-01-16 21:00:27 +0000407/*
drhd68eee02009-12-11 03:44:18 +0000408** CAPI3REF: Extended Result Codes
drh33c1be32008-01-30 16:16:14 +0000409** KEYWORDS: {extended error code} {extended error codes}
mihailimefc8e8a2008-06-21 16:47:09 +0000410** KEYWORDS: {extended result code} {extended result codes}
drh4ac285a2006-09-15 07:28:50 +0000411**
drh6ed48bf2007-06-14 20:57:18 +0000412** In its default configuration, SQLite API routines return one of 26 integer
mihailim362cc832008-06-21 06:16:42 +0000413** [SQLITE_OK | result codes]. However, experience has shown that many of
414** these result codes are too coarse-grained. They do not provide as
drhf5befa02007-12-06 02:42:07 +0000415** much information about problems as programmers might like. In an effort to
drh6ed48bf2007-06-14 20:57:18 +0000416** address this, newer versions of SQLite (version 3.3.8 and later) include
417** support for additional result codes that provide more detailed information
drh33c1be32008-01-30 16:16:14 +0000418** about errors. The extended result codes are enabled or disabled
mihailim362cc832008-06-21 06:16:42 +0000419** on a per database connection basis using the
420** [sqlite3_extended_result_codes()] API.
mihailima3f64902008-06-21 13:35:56 +0000421**
drh33c1be32008-01-30 16:16:14 +0000422** Some of the available extended result codes are listed here.
423** One may expect the number of extended result codes will be expand
424** over time. Software that uses extended result codes should expect
425** to see new result codes in future releases of SQLite.
drh4ac285a2006-09-15 07:28:50 +0000426**
427** The SQLITE_OK result code will never be extended. It will always
428** be exactly zero.
drh4ac285a2006-09-15 07:28:50 +0000429*/
danielk1977861f7452008-06-05 11:39:11 +0000430#define SQLITE_IOERR_READ (SQLITE_IOERR | (1<<8))
431#define SQLITE_IOERR_SHORT_READ (SQLITE_IOERR | (2<<8))
432#define SQLITE_IOERR_WRITE (SQLITE_IOERR | (3<<8))
433#define SQLITE_IOERR_FSYNC (SQLITE_IOERR | (4<<8))
434#define SQLITE_IOERR_DIR_FSYNC (SQLITE_IOERR | (5<<8))
435#define SQLITE_IOERR_TRUNCATE (SQLITE_IOERR | (6<<8))
436#define SQLITE_IOERR_FSTAT (SQLITE_IOERR | (7<<8))
437#define SQLITE_IOERR_UNLOCK (SQLITE_IOERR | (8<<8))
438#define SQLITE_IOERR_RDLOCK (SQLITE_IOERR | (9<<8))
439#define SQLITE_IOERR_DELETE (SQLITE_IOERR | (10<<8))
440#define SQLITE_IOERR_BLOCKED (SQLITE_IOERR | (11<<8))
441#define SQLITE_IOERR_NOMEM (SQLITE_IOERR | (12<<8))
442#define SQLITE_IOERR_ACCESS (SQLITE_IOERR | (13<<8))
443#define SQLITE_IOERR_CHECKRESERVEDLOCK (SQLITE_IOERR | (14<<8))
aswift5b1a2562008-08-22 00:22:35 +0000444#define SQLITE_IOERR_LOCK (SQLITE_IOERR | (15<<8))
aswiftaebf4132008-11-21 00:10:35 +0000445#define SQLITE_IOERR_CLOSE (SQLITE_IOERR | (16<<8))
446#define SQLITE_IOERR_DIR_CLOSE (SQLITE_IOERR | (17<<8))
drhaab4c022010-06-02 14:45:51 +0000447#define SQLITE_IOERR_SHMOPEN (SQLITE_IOERR | (18<<8))
448#define SQLITE_IOERR_SHMSIZE (SQLITE_IOERR | (19<<8))
449#define SQLITE_IOERR_SHMLOCK (SQLITE_IOERR | (20<<8))
drh73b64e42010-05-30 19:55:15 +0000450#define SQLITE_LOCKED_SHAREDCACHE (SQLITE_LOCKED | (1<<8))
451#define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8))
drh8b3cf822010-06-01 21:02:51 +0000452#define SQLITE_CANTOPEN_NOTEMPDIR (SQLITE_CANTOPEN | (1<<8))
danielk1977404ca072009-03-16 13:19:36 +0000453
drh4ac285a2006-09-15 07:28:50 +0000454/*
drhd68eee02009-12-11 03:44:18 +0000455** CAPI3REF: Flags For File Open Operations
drh6d2069d2007-08-14 01:58:53 +0000456**
mlcreechb2799412008-03-07 03:20:31 +0000457** These bit values are intended for use in the
drh33c1be32008-01-30 16:16:14 +0000458** 3rd parameter to the [sqlite3_open_v2()] interface and
459** in the 4th parameter to the xOpen method of the
drhd84f9462007-08-15 11:28:56 +0000460** [sqlite3_vfs] object.
drh6d2069d2007-08-14 01:58:53 +0000461*/
shane089b0a42009-05-14 03:21:28 +0000462#define SQLITE_OPEN_READONLY 0x00000001 /* Ok for sqlite3_open_v2() */
463#define SQLITE_OPEN_READWRITE 0x00000002 /* Ok for sqlite3_open_v2() */
464#define SQLITE_OPEN_CREATE 0x00000004 /* Ok for sqlite3_open_v2() */
465#define SQLITE_OPEN_DELETEONCLOSE 0x00000008 /* VFS only */
466#define SQLITE_OPEN_EXCLUSIVE 0x00000010 /* VFS only */
drh7ed97b92010-01-20 13:07:21 +0000467#define SQLITE_OPEN_AUTOPROXY 0x00000020 /* VFS only */
shane089b0a42009-05-14 03:21:28 +0000468#define SQLITE_OPEN_MAIN_DB 0x00000100 /* VFS only */
469#define SQLITE_OPEN_TEMP_DB 0x00000200 /* VFS only */
470#define SQLITE_OPEN_TRANSIENT_DB 0x00000400 /* VFS only */
471#define SQLITE_OPEN_MAIN_JOURNAL 0x00000800 /* VFS only */
472#define SQLITE_OPEN_TEMP_JOURNAL 0x00001000 /* VFS only */
473#define SQLITE_OPEN_SUBJOURNAL 0x00002000 /* VFS only */
474#define SQLITE_OPEN_MASTER_JOURNAL 0x00004000 /* VFS only */
475#define SQLITE_OPEN_NOMUTEX 0x00008000 /* Ok for sqlite3_open_v2() */
476#define SQLITE_OPEN_FULLMUTEX 0x00010000 /* Ok for sqlite3_open_v2() */
drhf1f12682009-09-09 14:17:52 +0000477#define SQLITE_OPEN_SHAREDCACHE 0x00020000 /* Ok for sqlite3_open_v2() */
478#define SQLITE_OPEN_PRIVATECACHE 0x00040000 /* Ok for sqlite3_open_v2() */
danddb0ac42010-07-14 14:48:58 +0000479#define SQLITE_OPEN_WAL 0x00080000 /* VFS only */
drh6d2069d2007-08-14 01:58:53 +0000480
481/*
drhd68eee02009-12-11 03:44:18 +0000482** CAPI3REF: Device Characteristics
drh6d2069d2007-08-14 01:58:53 +0000483**
dan0c173602010-07-13 18:45:10 +0000484** The xDeviceCharacteristics method of the [sqlite3_io_methods]
drhfddfa2d2007-12-05 18:05:16 +0000485** object returns an integer which is a vector of the these
drh6d2069d2007-08-14 01:58:53 +0000486** bit values expressing I/O characteristics of the mass storage
487** device that holds the file that the [sqlite3_io_methods]
drh33c1be32008-01-30 16:16:14 +0000488** refers to.
drh6d2069d2007-08-14 01:58:53 +0000489**
drh33c1be32008-01-30 16:16:14 +0000490** The SQLITE_IOCAP_ATOMIC property means that all writes of
491** any size are atomic. The SQLITE_IOCAP_ATOMICnnn values
drh6d2069d2007-08-14 01:58:53 +0000492** mean that writes of blocks that are nnn bytes in size and
493** are aligned to an address which is an integer multiple of
drh33c1be32008-01-30 16:16:14 +0000494** nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means
drh6d2069d2007-08-14 01:58:53 +0000495** that when data is appended to a file, the data is appended
496** first then the size of the file is extended, never the other
drh33c1be32008-01-30 16:16:14 +0000497** way around. The SQLITE_IOCAP_SEQUENTIAL property means that
drh6d2069d2007-08-14 01:58:53 +0000498** information is written to disk in the same order as calls
499** to xWrite().
500*/
dan8ce49d62010-06-19 18:12:02 +0000501#define SQLITE_IOCAP_ATOMIC 0x00000001
502#define SQLITE_IOCAP_ATOMIC512 0x00000002
503#define SQLITE_IOCAP_ATOMIC1K 0x00000004
504#define SQLITE_IOCAP_ATOMIC2K 0x00000008
505#define SQLITE_IOCAP_ATOMIC4K 0x00000010
506#define SQLITE_IOCAP_ATOMIC8K 0x00000020
507#define SQLITE_IOCAP_ATOMIC16K 0x00000040
508#define SQLITE_IOCAP_ATOMIC32K 0x00000080
509#define SQLITE_IOCAP_ATOMIC64K 0x00000100
510#define SQLITE_IOCAP_SAFE_APPEND 0x00000200
511#define SQLITE_IOCAP_SEQUENTIAL 0x00000400
512#define SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN 0x00000800
drh6d2069d2007-08-14 01:58:53 +0000513
514/*
drhd68eee02009-12-11 03:44:18 +0000515** CAPI3REF: File Locking Levels
drh6d2069d2007-08-14 01:58:53 +0000516**
drh33c1be32008-01-30 16:16:14 +0000517** SQLite uses one of these integer values as the second
drh6d2069d2007-08-14 01:58:53 +0000518** argument to calls it makes to the xLock() and xUnlock() methods
drh33c1be32008-01-30 16:16:14 +0000519** of an [sqlite3_io_methods] object.
drh6d2069d2007-08-14 01:58:53 +0000520*/
521#define SQLITE_LOCK_NONE 0
522#define SQLITE_LOCK_SHARED 1
523#define SQLITE_LOCK_RESERVED 2
524#define SQLITE_LOCK_PENDING 3
525#define SQLITE_LOCK_EXCLUSIVE 4
526
527/*
drhd68eee02009-12-11 03:44:18 +0000528** CAPI3REF: Synchronization Type Flags
drh6d2069d2007-08-14 01:58:53 +0000529**
drh33c1be32008-01-30 16:16:14 +0000530** When SQLite invokes the xSync() method of an
mlcreechb2799412008-03-07 03:20:31 +0000531** [sqlite3_io_methods] object it uses a combination of
drhfddfa2d2007-12-05 18:05:16 +0000532** these integer values as the second argument.
drh6d2069d2007-08-14 01:58:53 +0000533**
drh33c1be32008-01-30 16:16:14 +0000534** When the SQLITE_SYNC_DATAONLY flag is used, it means that the
drh6d2069d2007-08-14 01:58:53 +0000535** sync operation only needs to flush data to mass storage. Inode
drheb0d6292009-04-04 14:04:58 +0000536** information need not be flushed. If the lower four bits of the flag
537** equal SQLITE_SYNC_NORMAL, that means to use normal fsync() semantics.
538** If the lower four bits equal SQLITE_SYNC_FULL, that means
shane7ba429a2008-11-10 17:08:49 +0000539** to use Mac OS X style fullsync instead of fsync().
drh6d2069d2007-08-14 01:58:53 +0000540*/
drh6d2069d2007-08-14 01:58:53 +0000541#define SQLITE_SYNC_NORMAL 0x00002
542#define SQLITE_SYNC_FULL 0x00003
543#define SQLITE_SYNC_DATAONLY 0x00010
544
drh6d2069d2007-08-14 01:58:53 +0000545/*
drhd68eee02009-12-11 03:44:18 +0000546** CAPI3REF: OS Interface Open File Handle
drh6d2069d2007-08-14 01:58:53 +0000547**
drh6aa5f152009-08-19 15:57:07 +0000548** An [sqlite3_file] object represents an open file in the
549** [sqlite3_vfs | OS interface layer]. Individual OS interface
550** implementations will
drh6d2069d2007-08-14 01:58:53 +0000551** want to subclass this object by appending additional fields
drh4ff7fa02007-09-01 18:17:21 +0000552** for their own use. The pMethods entry is a pointer to an
drhd84f9462007-08-15 11:28:56 +0000553** [sqlite3_io_methods] object that defines methods for performing
554** I/O operations on the open file.
drh6d2069d2007-08-14 01:58:53 +0000555*/
556typedef struct sqlite3_file sqlite3_file;
557struct sqlite3_file {
drh153c62c2007-08-24 03:51:33 +0000558 const struct sqlite3_io_methods *pMethods; /* Methods for an open file */
drh6d2069d2007-08-14 01:58:53 +0000559};
560
561/*
drhd68eee02009-12-11 03:44:18 +0000562** CAPI3REF: OS Interface File Virtual Methods Object
drh6d2069d2007-08-14 01:58:53 +0000563**
drh4766b292008-06-26 02:53:02 +0000564** Every file opened by the [sqlite3_vfs] xOpen method populates an
565** [sqlite3_file] object (or, more commonly, a subclass of the
566** [sqlite3_file] object) with a pointer to an instance of this object.
567** This object defines the methods used to perform various operations
568** against the open file represented by the [sqlite3_file] object.
drhd84f9462007-08-15 11:28:56 +0000569**
drh9afedcc2009-06-19 22:50:31 +0000570** If the xOpen method sets the sqlite3_file.pMethods element
571** to a non-NULL pointer, then the sqlite3_io_methods.xClose method
572** may be invoked even if the xOpen reported that it failed. The
573** only way to prevent a call to xClose following a failed xOpen
574** is for the xOpen to set the sqlite3_file.pMethods element to NULL.
575**
drhfddfa2d2007-12-05 18:05:16 +0000576** The flags argument to xSync may be one of [SQLITE_SYNC_NORMAL] or
577** [SQLITE_SYNC_FULL]. The first choice is the normal fsync().
shane7ba429a2008-11-10 17:08:49 +0000578** The second choice is a Mac OS X style fullsync. The [SQLITE_SYNC_DATAONLY]
mihailim362cc832008-06-21 06:16:42 +0000579** flag may be ORed in to indicate that only the data of the file
580** and not its inode needs to be synced.
mihailima3f64902008-06-21 13:35:56 +0000581**
drhd84f9462007-08-15 11:28:56 +0000582** The integer values to xLock() and xUnlock() are one of
drh4ff7fa02007-09-01 18:17:21 +0000583** <ul>
584** <li> [SQLITE_LOCK_NONE],
drh79491ab2007-09-04 12:00:00 +0000585** <li> [SQLITE_LOCK_SHARED],
drh4ff7fa02007-09-01 18:17:21 +0000586** <li> [SQLITE_LOCK_RESERVED],
587** <li> [SQLITE_LOCK_PENDING], or
588** <li> [SQLITE_LOCK_EXCLUSIVE].
589** </ul>
mihailima3f64902008-06-21 13:35:56 +0000590** xLock() increases the lock. xUnlock() decreases the lock.
mihailim362cc832008-06-21 06:16:42 +0000591** The xCheckReservedLock() method checks whether any database connection,
592** either in this process or in some other process, is holding a RESERVED,
drhd84f9462007-08-15 11:28:56 +0000593** PENDING, or EXCLUSIVE lock on the file. It returns true
mihailim362cc832008-06-21 06:16:42 +0000594** if such a lock exists and false otherwise.
mihailima3f64902008-06-21 13:35:56 +0000595**
drhcc6bb3e2007-08-31 16:11:35 +0000596** The xFileControl() method is a generic interface that allows custom
597** VFS implementations to directly control an open file using the
mihailim362cc832008-06-21 06:16:42 +0000598** [sqlite3_file_control()] interface. The second "op" argument is an
mihailima3f64902008-06-21 13:35:56 +0000599** integer opcode. The third argument is a generic pointer intended to
mihailim362cc832008-06-21 06:16:42 +0000600** point to a structure that may contain arguments or space in which to
drhcc6bb3e2007-08-31 16:11:35 +0000601** write return values. Potential uses for xFileControl() might be
602** functions to enable blocking locks with timeouts, to change the
603** locking strategy (for example to use dot-file locks), to inquire
drh9e33c2c2007-08-31 18:34:59 +0000604** about the status of a lock, or to break stale locks. The SQLite
mihailima3f64902008-06-21 13:35:56 +0000605** core reserves all opcodes less than 100 for its own use.
drh4ff7fa02007-09-01 18:17:21 +0000606** A [SQLITE_FCNTL_LOCKSTATE | list of opcodes] less than 100 is available.
mihailim362cc832008-06-21 06:16:42 +0000607** Applications that define a custom xFileControl method should use opcodes
drh9e33c2c2007-08-31 18:34:59 +0000608** greater than 100 to avoid conflicts.
drhd84f9462007-08-15 11:28:56 +0000609**
610** The xSectorSize() method returns the sector size of the
611** device that underlies the file. The sector size is the
612** minimum write that can be performed without disturbing
613** other bytes in the file. The xDeviceCharacteristics()
614** method returns a bit vector describing behaviors of the
615** underlying device:
616**
617** <ul>
drh4ff7fa02007-09-01 18:17:21 +0000618** <li> [SQLITE_IOCAP_ATOMIC]
619** <li> [SQLITE_IOCAP_ATOMIC512]
620** <li> [SQLITE_IOCAP_ATOMIC1K]
621** <li> [SQLITE_IOCAP_ATOMIC2K]
622** <li> [SQLITE_IOCAP_ATOMIC4K]
623** <li> [SQLITE_IOCAP_ATOMIC8K]
624** <li> [SQLITE_IOCAP_ATOMIC16K]
625** <li> [SQLITE_IOCAP_ATOMIC32K]
626** <li> [SQLITE_IOCAP_ATOMIC64K]
627** <li> [SQLITE_IOCAP_SAFE_APPEND]
628** <li> [SQLITE_IOCAP_SEQUENTIAL]
drhd84f9462007-08-15 11:28:56 +0000629** </ul>
630**
631** The SQLITE_IOCAP_ATOMIC property means that all writes of
632** any size are atomic. The SQLITE_IOCAP_ATOMICnnn values
633** mean that writes of blocks that are nnn bytes in size and
634** are aligned to an address which is an integer multiple of
635** nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means
636** that when data is appended to a file, the data is appended
637** first then the size of the file is extended, never the other
638** way around. The SQLITE_IOCAP_SEQUENTIAL property means that
639** information is written to disk in the same order as calls
640** to xWrite().
drh4c17c3f2008-11-07 00:06:18 +0000641**
642** If xRead() returns SQLITE_IOERR_SHORT_READ it must also fill
643** in the unread portions of the buffer with zeros. A VFS that
644** fails to zero-fill short reads might seem to work. However,
645** failure to zero-fill short reads will eventually lead to
646** database corruption.
drh6d2069d2007-08-14 01:58:53 +0000647*/
648typedef struct sqlite3_io_methods sqlite3_io_methods;
649struct sqlite3_io_methods {
650 int iVersion;
651 int (*xClose)(sqlite3_file*);
drh79491ab2007-09-04 12:00:00 +0000652 int (*xRead)(sqlite3_file*, void*, int iAmt, sqlite3_int64 iOfst);
653 int (*xWrite)(sqlite3_file*, const void*, int iAmt, sqlite3_int64 iOfst);
654 int (*xTruncate)(sqlite3_file*, sqlite3_int64 size);
drh6d2069d2007-08-14 01:58:53 +0000655 int (*xSync)(sqlite3_file*, int flags);
drh79491ab2007-09-04 12:00:00 +0000656 int (*xFileSize)(sqlite3_file*, sqlite3_int64 *pSize);
drh6d2069d2007-08-14 01:58:53 +0000657 int (*xLock)(sqlite3_file*, int);
658 int (*xUnlock)(sqlite3_file*, int);
danielk1977861f7452008-06-05 11:39:11 +0000659 int (*xCheckReservedLock)(sqlite3_file*, int *pResOut);
drhcc6bb3e2007-08-31 16:11:35 +0000660 int (*xFileControl)(sqlite3_file*, int op, void *pArg);
drh6d2069d2007-08-14 01:58:53 +0000661 int (*xSectorSize)(sqlite3_file*);
662 int (*xDeviceCharacteristics)(sqlite3_file*);
drhd9e5c4f2010-05-12 18:01:39 +0000663 /* Methods above are valid for version 1 */
danda9fe0c2010-07-13 18:44:03 +0000664 int (*xShmMap)(sqlite3_file*, int iPg, int pgsz, int, void volatile**);
drh73b64e42010-05-30 19:55:15 +0000665 int (*xShmLock)(sqlite3_file*, int offset, int n, int flags);
drh286a2882010-05-20 23:51:06 +0000666 void (*xShmBarrier)(sqlite3_file*);
danaf6ea4e2010-07-13 14:33:48 +0000667 int (*xShmUnmap)(sqlite3_file*, int deleteFlag);
drhd9e5c4f2010-05-12 18:01:39 +0000668 /* Methods above are valid for version 2 */
drh6d2069d2007-08-14 01:58:53 +0000669 /* Additional methods may be added in future releases */
670};
671
672/*
drhd68eee02009-12-11 03:44:18 +0000673** CAPI3REF: Standard File Control Opcodes
drh9e33c2c2007-08-31 18:34:59 +0000674**
675** These integer constants are opcodes for the xFileControl method
mihailim362cc832008-06-21 06:16:42 +0000676** of the [sqlite3_io_methods] object and for the [sqlite3_file_control()]
drh9e33c2c2007-08-31 18:34:59 +0000677** interface.
678**
drh33c1be32008-01-30 16:16:14 +0000679** The [SQLITE_FCNTL_LOCKSTATE] opcode is used for debugging. This
mlcreechb2799412008-03-07 03:20:31 +0000680** opcode causes the xFileControl method to write the current state of
drh9e33c2c2007-08-31 18:34:59 +0000681** the lock (one of [SQLITE_LOCK_NONE], [SQLITE_LOCK_SHARED],
682** [SQLITE_LOCK_RESERVED], [SQLITE_LOCK_PENDING], or [SQLITE_LOCK_EXCLUSIVE])
drh33c1be32008-01-30 16:16:14 +0000683** into an integer that the pArg argument points to. This capability
drh9e33c2c2007-08-31 18:34:59 +0000684** is used during testing and only needs to be supported when SQLITE_TEST
685** is defined.
drh9ff27ec2010-05-19 19:26:05 +0000686**
687** The [SQLITE_FCNTL_SIZE_HINT] opcode is used by SQLite to give the VFS
688** layer a hint of how large the database file will grow to be during the
689** current transaction. This hint is not guaranteed to be accurate but it
690** is often close. The underlying VFS might choose to preallocate database
691** file space based on this hint in order to help writes to the database
692** file run faster.
dan502019c2010-07-28 14:26:17 +0000693**
694** The [SQLITE_FCNTL_CHUNK_SIZE] opcode is used to request that the VFS
695** extends and truncates the database file in chunks of a size specified
696** by the user. The fourth argument to [sqlite3_file_control()] should
697** point to an integer (type int) containing the new chunk-size to use
698** for the nominated database. Allocating database file space in large
699** chunks (say 1MB at a time), may reduce file-system fragmentation and
700** improve performance on some systems.
drh9e33c2c2007-08-31 18:34:59 +0000701*/
702#define SQLITE_FCNTL_LOCKSTATE 1
aswiftaebf4132008-11-21 00:10:35 +0000703#define SQLITE_GET_LOCKPROXYFILE 2
704#define SQLITE_SET_LOCKPROXYFILE 3
705#define SQLITE_LAST_ERRNO 4
drh9ff27ec2010-05-19 19:26:05 +0000706#define SQLITE_FCNTL_SIZE_HINT 5
dan6e09d692010-07-27 18:34:15 +0000707#define SQLITE_FCNTL_CHUNK_SIZE 6
drh9e33c2c2007-08-31 18:34:59 +0000708
709/*
drhd68eee02009-12-11 03:44:18 +0000710** CAPI3REF: Mutex Handle
drh6d2069d2007-08-14 01:58:53 +0000711**
drhd84f9462007-08-15 11:28:56 +0000712** The mutex module within SQLite defines [sqlite3_mutex] to be an
drh33c1be32008-01-30 16:16:14 +0000713** abstract type for a mutex object. The SQLite core never looks
714** at the internal representation of an [sqlite3_mutex]. It only
drhd84f9462007-08-15 11:28:56 +0000715** deals with pointers to the [sqlite3_mutex] object.
drh6bdec4a2007-08-16 19:40:16 +0000716**
717** Mutexes are created using [sqlite3_mutex_alloc()].
drh6d2069d2007-08-14 01:58:53 +0000718*/
719typedef struct sqlite3_mutex sqlite3_mutex;
720
721/*
drhd68eee02009-12-11 03:44:18 +0000722** CAPI3REF: OS Interface Object
drh6d2069d2007-08-14 01:58:53 +0000723**
mihailim362cc832008-06-21 06:16:42 +0000724** An instance of the sqlite3_vfs object defines the interface between
725** the SQLite core and the underlying operating system. The "vfs"
drhd84f9462007-08-15 11:28:56 +0000726** in the name of the object stands for "virtual file system".
drh6d2069d2007-08-14 01:58:53 +0000727**
mihailim362cc832008-06-21 06:16:42 +0000728** The value of the iVersion field is initially 1 but may be larger in
729** future versions of SQLite. Additional fields may be appended to this
drh4766b292008-06-26 02:53:02 +0000730** object when the iVersion value is increased. Note that the structure
731** of the sqlite3_vfs object changes in the transaction between
732** SQLite version 3.5.9 and 3.6.0 and yet the iVersion field was not
733** modified.
drh6bdec4a2007-08-16 19:40:16 +0000734**
drh4ff7fa02007-09-01 18:17:21 +0000735** The szOsFile field is the size of the subclassed [sqlite3_file]
drhd84f9462007-08-15 11:28:56 +0000736** structure used by this VFS. mxPathname is the maximum length of
737** a pathname in this VFS.
738**
drhb4d58ae2008-02-21 20:17:06 +0000739** Registered sqlite3_vfs objects are kept on a linked list formed by
drh79491ab2007-09-04 12:00:00 +0000740** the pNext pointer. The [sqlite3_vfs_register()]
741** and [sqlite3_vfs_unregister()] interfaces manage this list
742** in a thread-safe way. The [sqlite3_vfs_find()] interface
drh4766b292008-06-26 02:53:02 +0000743** searches the list. Neither the application code nor the VFS
744** implementation should use the pNext pointer.
drhd84f9462007-08-15 11:28:56 +0000745**
mihailima3f64902008-06-21 13:35:56 +0000746** The pNext field is the only field in the sqlite3_vfs
drh1cc8c442007-08-24 16:08:29 +0000747** structure that SQLite will ever modify. SQLite will only access
748** or modify this field while holding a particular static mutex.
749** The application should never modify anything within the sqlite3_vfs
750** object once the object has been registered.
751**
drhd84f9462007-08-15 11:28:56 +0000752** The zName field holds the name of the VFS module. The name must
753** be unique across all VFS modules.
754**
drh032ca702008-12-10 11:44:30 +0000755** SQLite will guarantee that the zFilename parameter to xOpen
drh4766b292008-06-26 02:53:02 +0000756** is either a NULL pointer or string obtained
757** from xFullPathname(). SQLite further guarantees that
758** the string will be valid and unchanged until xClose() is
drh9afedcc2009-06-19 22:50:31 +0000759** called. Because of the previous sentence,
drh4766b292008-06-26 02:53:02 +0000760** the [sqlite3_file] can safely store a pointer to the
drh6d2069d2007-08-14 01:58:53 +0000761** filename if it needs to remember the filename for some reason.
drh4766b292008-06-26 02:53:02 +0000762** If the zFilename parameter is xOpen is a NULL pointer then xOpen
drh9afedcc2009-06-19 22:50:31 +0000763** must invent its own temporary name for the file. Whenever the
drh4766b292008-06-26 02:53:02 +0000764** xFilename parameter is NULL it will also be the case that the
765** flags parameter will include [SQLITE_OPEN_DELETEONCLOSE].
drhd84f9462007-08-15 11:28:56 +0000766**
drh032ca702008-12-10 11:44:30 +0000767** The flags argument to xOpen() includes all bits set in
drhf5befa02007-12-06 02:42:07 +0000768** the flags argument to [sqlite3_open_v2()]. Or if [sqlite3_open()]
769** or [sqlite3_open16()] is used, then flags includes at least
drh032ca702008-12-10 11:44:30 +0000770** [SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE].
drh6d2069d2007-08-14 01:58:53 +0000771** If xOpen() opens a file read-only then it sets *pOutFlags to
mihailim362cc832008-06-21 06:16:42 +0000772** include [SQLITE_OPEN_READONLY]. Other bits in *pOutFlags may be set.
773**
drh032ca702008-12-10 11:44:30 +0000774** SQLite will also add one of the following flags to the xOpen()
drh6d2069d2007-08-14 01:58:53 +0000775** call, depending on the object being opened:
mihailim362cc832008-06-21 06:16:42 +0000776**
drh6d2069d2007-08-14 01:58:53 +0000777** <ul>
778** <li> [SQLITE_OPEN_MAIN_DB]
779** <li> [SQLITE_OPEN_MAIN_JOURNAL]
780** <li> [SQLITE_OPEN_TEMP_DB]
781** <li> [SQLITE_OPEN_TEMP_JOURNAL]
drh33f4e022007-09-03 15:19:34 +0000782** <li> [SQLITE_OPEN_TRANSIENT_DB]
drh6d2069d2007-08-14 01:58:53 +0000783** <li> [SQLITE_OPEN_SUBJOURNAL]
784** <li> [SQLITE_OPEN_MASTER_JOURNAL]
drh032ca702008-12-10 11:44:30 +0000785** </ul>
drhd84f9462007-08-15 11:28:56 +0000786**
drh6d2069d2007-08-14 01:58:53 +0000787** The file I/O implementation can use the object type flags to
mihailim362cc832008-06-21 06:16:42 +0000788** change the way it deals with files. For example, an application
mlcreechb2799412008-03-07 03:20:31 +0000789** that does not care about crash recovery or rollback might make
790** the open of a journal file a no-op. Writes to this journal would
mihailim362cc832008-06-21 06:16:42 +0000791** also be no-ops, and any attempt to read the journal would return
792** SQLITE_IOERR. Or the implementation might recognize that a database
793** file will be doing page-aligned sector reads and writes in a random
mlcreechb2799412008-03-07 03:20:31 +0000794** order and set up its I/O subsystem accordingly.
mihailim362cc832008-06-21 06:16:42 +0000795**
796** SQLite might also add one of the following flags to the xOpen method:
797**
drh6d2069d2007-08-14 01:58:53 +0000798** <ul>
799** <li> [SQLITE_OPEN_DELETEONCLOSE]
800** <li> [SQLITE_OPEN_EXCLUSIVE]
801** </ul>
mihailim362cc832008-06-21 06:16:42 +0000802**
drh032ca702008-12-10 11:44:30 +0000803** The [SQLITE_OPEN_DELETEONCLOSE] flag means the file should be
804** deleted when it is closed. The [SQLITE_OPEN_DELETEONCLOSE]
mihailim362cc832008-06-21 06:16:42 +0000805** will be set for TEMP databases, journals and for subjournals.
mihailim04bcc002008-06-22 10:21:27 +0000806**
shane089b0a42009-05-14 03:21:28 +0000807** The [SQLITE_OPEN_EXCLUSIVE] flag is always used in conjunction
808** with the [SQLITE_OPEN_CREATE] flag, which are both directly
809** analogous to the O_EXCL and O_CREAT flags of the POSIX open()
810** API. The SQLITE_OPEN_EXCLUSIVE flag, when paired with the
811** SQLITE_OPEN_CREATE, is used to indicate that file should always
812** be created, and that it is an error if it already exists.
813** It is <i>not</i> used to indicate the file should be opened
814** for exclusive access.
mihailim362cc832008-06-21 06:16:42 +0000815**
drh032ca702008-12-10 11:44:30 +0000816** At least szOsFile bytes of memory are allocated by SQLite
mihailim362cc832008-06-21 06:16:42 +0000817** to hold the [sqlite3_file] structure passed as the third
drh032ca702008-12-10 11:44:30 +0000818** argument to xOpen. The xOpen method does not have to
drh9afedcc2009-06-19 22:50:31 +0000819** allocate the structure; it should just fill it in. Note that
820** the xOpen method must set the sqlite3_file.pMethods to either
821** a valid [sqlite3_io_methods] object or to NULL. xOpen must do
822** this even if the open fails. SQLite expects that the sqlite3_file.pMethods
823** element will be valid after xOpen returns regardless of the success
824** or failure of the xOpen call.
mihailim362cc832008-06-21 06:16:42 +0000825**
drh032ca702008-12-10 11:44:30 +0000826** The flags argument to xAccess() may be [SQLITE_ACCESS_EXISTS]
mihailim362cc832008-06-21 06:16:42 +0000827** to test for the existence of a file, or [SQLITE_ACCESS_READWRITE] to
828** test whether a file is readable and writable, or [SQLITE_ACCESS_READ]
drh032ca702008-12-10 11:44:30 +0000829** to test whether a file is at least readable. The file can be a
drh6d2069d2007-08-14 01:58:53 +0000830** directory.
mihailim362cc832008-06-21 06:16:42 +0000831**
drh032ca702008-12-10 11:44:30 +0000832** SQLite will always allocate at least mxPathname+1 bytes for the
833** output buffer xFullPathname. The exact size of the output buffer
834** is also passed as a parameter to both methods. If the output buffer
mihailim362cc832008-06-21 06:16:42 +0000835** is not large enough, [SQLITE_CANTOPEN] should be returned. Since this is
836** handled as a fatal error by SQLite, vfs implementations should endeavor
837** to prevent this by setting mxPathname to a sufficiently large value.
838**
drh2667be52010-07-03 17:13:31 +0000839** The xRandomness(), xSleep(), xCurrentTime(), and xCurrentTimeInt64()
840** interfaces are not strictly a part of the filesystem, but they are
drhd84f9462007-08-15 11:28:56 +0000841** included in the VFS structure for completeness.
drh6d2069d2007-08-14 01:58:53 +0000842** The xRandomness() function attempts to return nBytes bytes
843** of good-quality randomness into zOut. The return value is
mihailim362cc832008-06-21 06:16:42 +0000844** the actual number of bytes of randomness obtained.
845** The xSleep() method causes the calling thread to sleep for at
drhd84f9462007-08-15 11:28:56 +0000846** least the number of microseconds given. The xCurrentTime()
drh2667be52010-07-03 17:13:31 +0000847** method returns a Julian Day Number for the current date and time as
848** a floating point value.
849** The xCurrentTimeInt64() method returns, as an integer, the Julian
850** Day Number multipled by 86400000 (the number of milliseconds in
851** a 24-hour day).
852** ^SQLite will use the xCurrentTimeInt64() method to get the current
853** date and time if that method is available (if iVersion is 2 or
854** greater and the function pointer is not NULL) and will fall back
855** to xCurrentTime() if xCurrentTimeInt64() is unavailable.
drh6d2069d2007-08-14 01:58:53 +0000856*/
drhd84f9462007-08-15 11:28:56 +0000857typedef struct sqlite3_vfs sqlite3_vfs;
858struct sqlite3_vfs {
drhf2424c52010-04-26 00:04:55 +0000859 int iVersion; /* Structure version number (currently 2) */
drh6d2069d2007-08-14 01:58:53 +0000860 int szOsFile; /* Size of subclassed sqlite3_file */
drh6d2069d2007-08-14 01:58:53 +0000861 int mxPathname; /* Maximum file pathname length */
drhd84f9462007-08-15 11:28:56 +0000862 sqlite3_vfs *pNext; /* Next registered VFS */
drhd84f9462007-08-15 11:28:56 +0000863 const char *zName; /* Name of this virtual file system */
drh1cc8c442007-08-24 16:08:29 +0000864 void *pAppData; /* Pointer to application-specific data */
drh153c62c2007-08-24 03:51:33 +0000865 int (*xOpen)(sqlite3_vfs*, const char *zName, sqlite3_file*,
drh6d2069d2007-08-14 01:58:53 +0000866 int flags, int *pOutFlags);
drh153c62c2007-08-24 03:51:33 +0000867 int (*xDelete)(sqlite3_vfs*, const char *zName, int syncDir);
danielk1977861f7452008-06-05 11:39:11 +0000868 int (*xAccess)(sqlite3_vfs*, const char *zName, int flags, int *pResOut);
danielk1977adfb9b02007-09-17 07:02:56 +0000869 int (*xFullPathname)(sqlite3_vfs*, const char *zName, int nOut, char *zOut);
drh153c62c2007-08-24 03:51:33 +0000870 void *(*xDlOpen)(sqlite3_vfs*, const char *zFilename);
871 void (*xDlError)(sqlite3_vfs*, int nByte, char *zErrMsg);
drh1875f7a2008-12-08 18:19:17 +0000872 void (*(*xDlSym)(sqlite3_vfs*,void*, const char *zSymbol))(void);
drh153c62c2007-08-24 03:51:33 +0000873 void (*xDlClose)(sqlite3_vfs*, void*);
874 int (*xRandomness)(sqlite3_vfs*, int nByte, char *zOut);
875 int (*xSleep)(sqlite3_vfs*, int microseconds);
876 int (*xCurrentTime)(sqlite3_vfs*, double*);
danielk1977bcb97fe2008-06-06 15:49:29 +0000877 int (*xGetLastError)(sqlite3_vfs*, int, char *);
drhf2424c52010-04-26 00:04:55 +0000878 /*
879 ** The methods above are in version 1 of the sqlite_vfs object
880 ** definition. Those that follow are added in version 2 or later
881 */
drhf2424c52010-04-26 00:04:55 +0000882 int (*xCurrentTimeInt64)(sqlite3_vfs*, sqlite3_int64*);
883 /*
884 ** The methods above are in versions 1 and 2 of the sqlite_vfs object.
885 ** New fields may be appended in figure versions. The iVersion
886 ** value will increment whenever this happens.
887 */
drh6d2069d2007-08-14 01:58:53 +0000888};
889
drh50d3f902007-08-27 21:10:36 +0000890/*
drhd68eee02009-12-11 03:44:18 +0000891** CAPI3REF: Flags for the xAccess VFS method
drh50d3f902007-08-27 21:10:36 +0000892**
drh032ca702008-12-10 11:44:30 +0000893** These integer constants can be used as the third parameter to
drhfb434032009-12-11 23:11:26 +0000894** the xAccess method of an [sqlite3_vfs] object. They determine
mihailim04bcc002008-06-22 10:21:27 +0000895** what kind of permissions the xAccess method is looking for.
drh032ca702008-12-10 11:44:30 +0000896** With SQLITE_ACCESS_EXISTS, the xAccess method
mihailim04bcc002008-06-22 10:21:27 +0000897** simply checks whether the file exists.
drh032ca702008-12-10 11:44:30 +0000898** With SQLITE_ACCESS_READWRITE, the xAccess method
drh21032452010-07-13 14:48:27 +0000899** checks whether the named directory is both readable and writable
900** (in other words, if files can be added, removed, and renamed within
901** the directory).
902** The SQLITE_ACCESS_READWRITE constant is currently used only by the
903** [temp_store_directory pragma], though this could change in a future
904** release of SQLite.
drh032ca702008-12-10 11:44:30 +0000905** With SQLITE_ACCESS_READ, the xAccess method
drh21032452010-07-13 14:48:27 +0000906** checks whether the file is readable. The SQLITE_ACCESS_READ constant is
907** currently unused, though it might be used in a future release of
908** SQLite.
drh50d3f902007-08-27 21:10:36 +0000909*/
danielk1977b4b47412007-08-17 15:53:36 +0000910#define SQLITE_ACCESS_EXISTS 0
drh21032452010-07-13 14:48:27 +0000911#define SQLITE_ACCESS_READWRITE 1 /* Used by PRAGMA temp_store_directory */
912#define SQLITE_ACCESS_READ 2 /* Unused */
danielk1977b4b47412007-08-17 15:53:36 +0000913
drh6d2069d2007-08-14 01:58:53 +0000914/*
drhf2424c52010-04-26 00:04:55 +0000915** CAPI3REF: Flags for the xShmLock VFS method
916**
drh73b64e42010-05-30 19:55:15 +0000917** These integer constants define the various locking operations
918** allowed by the xShmLock method of [sqlite3_io_methods]. The
919** following are the only legal combinations of flags to the
920** xShmLock method:
921**
922** <ul>
923** <li> SQLITE_SHM_LOCK | SQLITE_SHM_SHARED
924** <li> SQLITE_SHM_LOCK | SQLITE_SHM_EXCLUSIVE
925** <li> SQLITE_SHM_UNLOCK | SQLITE_SHM_SHARED
926** <li> SQLITE_SHM_UNLOCK | SQLITE_SHM_EXCLUSIVE
927** </ul>
928**
929** When unlocking, the same SHARED or EXCLUSIVE flag must be supplied as
930** was given no the corresponding lock.
931**
932** The xShmLock method can transition between unlocked and SHARED or
933** between unlocked and EXCLUSIVE. It cannot transition between SHARED
934** and EXCLUSIVE.
drhf2424c52010-04-26 00:04:55 +0000935*/
drh73b64e42010-05-30 19:55:15 +0000936#define SQLITE_SHM_UNLOCK 1
937#define SQLITE_SHM_LOCK 2
938#define SQLITE_SHM_SHARED 4
939#define SQLITE_SHM_EXCLUSIVE 8
940
941/*
942** CAPI3REF: Maximum xShmLock index
943**
944** The xShmLock method on [sqlite3_io_methods] may use values
945** between 0 and this upper bound as its "offset" argument.
946** The SQLite core will never attempt to acquire or release a
947** lock outside of this range
948*/
949#define SQLITE_SHM_NLOCK 8
950
drhf2424c52010-04-26 00:04:55 +0000951
952/*
drhd68eee02009-12-11 03:44:18 +0000953** CAPI3REF: Initialize The SQLite Library
drh673299b2008-06-09 21:57:22 +0000954**
drhd68eee02009-12-11 03:44:18 +0000955** ^The sqlite3_initialize() routine initializes the
956** SQLite library. ^The sqlite3_shutdown() routine
drhcb041342008-06-12 00:07:29 +0000957** deallocates any resources that were allocated by sqlite3_initialize().
drh481aa742009-11-05 18:46:02 +0000958** These routines are designed to aid in process initialization and
drh9524f4b2009-10-20 15:27:55 +0000959** shutdown on embedded systems. Workstation applications using
960** SQLite normally do not need to invoke either of these routines.
drh673299b2008-06-09 21:57:22 +0000961**
drhcb041342008-06-12 00:07:29 +0000962** A call to sqlite3_initialize() is an "effective" call if it is
963** the first time sqlite3_initialize() is invoked during the lifetime of
964** the process, or if it is the first time sqlite3_initialize() is invoked
drhd68eee02009-12-11 03:44:18 +0000965** following a call to sqlite3_shutdown(). ^(Only an effective call
drhcb041342008-06-12 00:07:29 +0000966** of sqlite3_initialize() does any initialization. All other calls
drhd68eee02009-12-11 03:44:18 +0000967** are harmless no-ops.)^
drhcb041342008-06-12 00:07:29 +0000968**
drhd1a24402009-04-19 12:23:58 +0000969** A call to sqlite3_shutdown() is an "effective" call if it is the first
drhd68eee02009-12-11 03:44:18 +0000970** call to sqlite3_shutdown() since the last sqlite3_initialize(). ^(Only
drhd1a24402009-04-19 12:23:58 +0000971** an effective call to sqlite3_shutdown() does any deinitialization.
drhd68eee02009-12-11 03:44:18 +0000972** All other valid calls to sqlite3_shutdown() are harmless no-ops.)^
drhd1a24402009-04-19 12:23:58 +0000973**
drh9524f4b2009-10-20 15:27:55 +0000974** The sqlite3_initialize() interface is threadsafe, but sqlite3_shutdown()
975** is not. The sqlite3_shutdown() interface must only be called from a
976** single thread. All open [database connections] must be closed and all
977** other SQLite resources must be deallocated prior to invoking
978** sqlite3_shutdown().
979**
drhd68eee02009-12-11 03:44:18 +0000980** Among other things, ^sqlite3_initialize() will invoke
981** sqlite3_os_init(). Similarly, ^sqlite3_shutdown()
drh9524f4b2009-10-20 15:27:55 +0000982** will invoke sqlite3_os_end().
drh673299b2008-06-09 21:57:22 +0000983**
drhd68eee02009-12-11 03:44:18 +0000984** ^The sqlite3_initialize() routine returns [SQLITE_OK] on success.
985** ^If for some reason, sqlite3_initialize() is unable to initialize
drhce5a5a02008-06-10 17:41:44 +0000986** the library (perhaps it is unable to allocate a needed resource such
drhadfae6c2008-10-10 17:26:35 +0000987** as a mutex) it returns an [error code] other than [SQLITE_OK].
drh673299b2008-06-09 21:57:22 +0000988**
drhd68eee02009-12-11 03:44:18 +0000989** ^The sqlite3_initialize() routine is called internally by many other
drhcb041342008-06-12 00:07:29 +0000990** SQLite interfaces so that an application usually does not need to
drhce5a5a02008-06-10 17:41:44 +0000991** invoke sqlite3_initialize() directly. For example, [sqlite3_open()]
992** calls sqlite3_initialize() so the SQLite library will be automatically
993** initialized when [sqlite3_open()] is called if it has not be initialized
drhd68eee02009-12-11 03:44:18 +0000994** already. ^However, if SQLite is compiled with the [SQLITE_OMIT_AUTOINIT]
drhcb041342008-06-12 00:07:29 +0000995** compile-time option, then the automatic calls to sqlite3_initialize()
996** are omitted and the application must call sqlite3_initialize() directly
997** prior to using any other SQLite interface. For maximum portability,
998** it is recommended that applications always invoke sqlite3_initialize()
999** directly prior to using any other SQLite interface. Future releases
1000** of SQLite may require this. In other words, the behavior exhibited
drhadfae6c2008-10-10 17:26:35 +00001001** when SQLite is compiled with [SQLITE_OMIT_AUTOINIT] might become the
drhcb041342008-06-12 00:07:29 +00001002** default behavior in some future release of SQLite.
drh673299b2008-06-09 21:57:22 +00001003**
drhcb041342008-06-12 00:07:29 +00001004** The sqlite3_os_init() routine does operating-system specific
1005** initialization of the SQLite library. The sqlite3_os_end()
1006** routine undoes the effect of sqlite3_os_init(). Typical tasks
1007** performed by these routines include allocation or deallocation
1008** of static resources, initialization of global variables,
1009** setting up a default [sqlite3_vfs] module, or setting up
mihailima3f64902008-06-21 13:35:56 +00001010** a default configuration using [sqlite3_config()].
drh673299b2008-06-09 21:57:22 +00001011**
drhcb041342008-06-12 00:07:29 +00001012** The application should never invoke either sqlite3_os_init()
1013** or sqlite3_os_end() directly. The application should only invoke
1014** sqlite3_initialize() and sqlite3_shutdown(). The sqlite3_os_init()
mihailima3f64902008-06-21 13:35:56 +00001015** interface is called automatically by sqlite3_initialize() and
drhcb041342008-06-12 00:07:29 +00001016** sqlite3_os_end() is called by sqlite3_shutdown(). Appropriate
1017** implementations for sqlite3_os_init() and sqlite3_os_end()
shane7c7c3112009-08-17 15:31:23 +00001018** are built into SQLite when it is compiled for Unix, Windows, or OS/2.
drh6aa5f152009-08-19 15:57:07 +00001019** When [custom builds | built for other platforms]
1020** (using the [SQLITE_OS_OTHER=1] compile-time
drhcb041342008-06-12 00:07:29 +00001021** option) the application must supply a suitable implementation for
1022** sqlite3_os_init() and sqlite3_os_end(). An application-supplied
1023** implementation of sqlite3_os_init() or sqlite3_os_end()
drhadfae6c2008-10-10 17:26:35 +00001024** must return [SQLITE_OK] on success and some other [error code] upon
drhcb041342008-06-12 00:07:29 +00001025** failure.
drh673299b2008-06-09 21:57:22 +00001026*/
drhce5a5a02008-06-10 17:41:44 +00001027int sqlite3_initialize(void);
drh673299b2008-06-09 21:57:22 +00001028int sqlite3_shutdown(void);
drhcb041342008-06-12 00:07:29 +00001029int sqlite3_os_init(void);
1030int sqlite3_os_end(void);
drh673299b2008-06-09 21:57:22 +00001031
drhce5a5a02008-06-10 17:41:44 +00001032/*
drhd68eee02009-12-11 03:44:18 +00001033** CAPI3REF: Configuring The SQLite Library
drhce5a5a02008-06-10 17:41:44 +00001034**
1035** The sqlite3_config() interface is used to make global configuration
1036** changes to SQLite in order to tune SQLite to the specific needs of
1037** the application. The default configuration is recommended for most
1038** applications and so this routine is usually not necessary. It is
1039** provided to support rare applications with unusual needs.
1040**
1041** The sqlite3_config() interface is not threadsafe. The application
1042** must insure that no other SQLite interfaces are invoked by other
1043** threads while sqlite3_config() is running. Furthermore, sqlite3_config()
1044** may only be invoked prior to library initialization using
1045** [sqlite3_initialize()] or after shutdown by [sqlite3_shutdown()].
drhd68eee02009-12-11 03:44:18 +00001046** ^If sqlite3_config() is called after [sqlite3_initialize()] and before
1047** [sqlite3_shutdown()] then it will return SQLITE_MISUSE.
1048** Note, however, that ^sqlite3_config() can be called as part of the
drh40257ff2008-06-13 18:24:27 +00001049** implementation of an application-defined [sqlite3_os_init()].
drhce5a5a02008-06-10 17:41:44 +00001050**
1051** The first argument to sqlite3_config() is an integer
1052** [SQLITE_CONFIG_SINGLETHREAD | configuration option] that determines
1053** what property of SQLite is to be configured. Subsequent arguments
1054** vary depending on the [SQLITE_CONFIG_SINGLETHREAD | configuration option]
1055** in the first argument.
1056**
drhd68eee02009-12-11 03:44:18 +00001057** ^When a configuration option is set, sqlite3_config() returns [SQLITE_OK].
1058** ^If the option is unknown or SQLite is unable to set the option
drh40257ff2008-06-13 18:24:27 +00001059** then this routine returns a non-zero [error code].
drhce5a5a02008-06-10 17:41:44 +00001060*/
drh9f8da322010-03-10 20:06:37 +00001061int sqlite3_config(int, ...);
drhce5a5a02008-06-10 17:41:44 +00001062
1063/*
drhd68eee02009-12-11 03:44:18 +00001064** CAPI3REF: Configure database connections
drh633e6d52008-07-28 19:34:53 +00001065**
1066** The sqlite3_db_config() interface is used to make configuration
drh2462e322008-07-31 14:47:54 +00001067** changes to a [database connection]. The interface is similar to
1068** [sqlite3_config()] except that the changes apply to a single
1069** [database connection] (specified in the first argument). The
drhd68eee02009-12-11 03:44:18 +00001070** sqlite3_db_config() interface should only be used immediately after
drh2462e322008-07-31 14:47:54 +00001071** the database connection is created using [sqlite3_open()],
1072** [sqlite3_open16()], or [sqlite3_open_v2()].
1073**
1074** The second argument to sqlite3_db_config(D,V,...) is the
1075** configuration verb - an integer code that indicates what
1076** aspect of the [database connection] is being configured.
drhe9d1c722008-08-04 20:13:26 +00001077** The only choice for this value is [SQLITE_DBCONFIG_LOOKASIDE].
drh2462e322008-07-31 14:47:54 +00001078** New verbs are likely to be added in future releases of SQLite.
drhe9d1c722008-08-04 20:13:26 +00001079** Additional arguments depend on the verb.
drhf8cecda2008-10-10 23:48:25 +00001080**
drhd68eee02009-12-11 03:44:18 +00001081** ^Calls to sqlite3_db_config() return SQLITE_OK if and only if
1082** the call is considered successful.
drh633e6d52008-07-28 19:34:53 +00001083*/
drh9f8da322010-03-10 20:06:37 +00001084int sqlite3_db_config(sqlite3*, int op, ...);
drh633e6d52008-07-28 19:34:53 +00001085
1086/*
drhfb434032009-12-11 23:11:26 +00001087** CAPI3REF: Memory Allocation Routines
drhfec00ea2008-06-14 16:56:21 +00001088**
1089** An instance of this object defines the interface between SQLite
mihailima3f64902008-06-21 13:35:56 +00001090** and low-level memory allocation routines.
drhfec00ea2008-06-14 16:56:21 +00001091**
1092** This object is used in only one place in the SQLite interface.
1093** A pointer to an instance of this object is the argument to
drh4766b292008-06-26 02:53:02 +00001094** [sqlite3_config()] when the configuration option is
drh6aa5f152009-08-19 15:57:07 +00001095** [SQLITE_CONFIG_MALLOC] or [SQLITE_CONFIG_GETMALLOC].
1096** By creating an instance of this object
1097** and passing it to [sqlite3_config]([SQLITE_CONFIG_MALLOC])
1098** during configuration, an application can specify an alternative
1099** memory allocation subsystem for SQLite to use for all of its
1100** dynamic memory needs.
drhfec00ea2008-06-14 16:56:21 +00001101**
drh6aa5f152009-08-19 15:57:07 +00001102** Note that SQLite comes with several [built-in memory allocators]
1103** that are perfectly adequate for the overwhelming majority of applications
drhfec00ea2008-06-14 16:56:21 +00001104** and that this object is only useful to a tiny minority of applications
1105** with specialized memory allocation requirements. This object is
1106** also used during testing of SQLite in order to specify an alternative
1107** memory allocator that simulates memory out-of-memory conditions in
1108** order to verify that SQLite recovers gracefully from such
1109** conditions.
1110**
drh6aa5f152009-08-19 15:57:07 +00001111** The xMalloc and xFree methods must work like the
1112** malloc() and free() functions from the standard C library.
1113** The xRealloc method must work like realloc() from the standard C library
1114** with the exception that if the second argument to xRealloc is zero,
1115** xRealloc must be a no-op - it must not perform any allocation or
drhd68eee02009-12-11 03:44:18 +00001116** deallocation. ^SQLite guarantees that the second argument to
drh6aa5f152009-08-19 15:57:07 +00001117** xRealloc is always a value returned by a prior call to xRoundup.
1118** And so in cases where xRoundup always returns a positive number,
1119** xRealloc can perform exactly as the standard library realloc() and
1120** still be in compliance with this specification.
drhfec00ea2008-06-14 16:56:21 +00001121**
1122** xSize should return the allocated size of a memory allocation
1123** previously obtained from xMalloc or xRealloc. The allocated size
1124** is always at least as big as the requested size but may be larger.
1125**
1126** The xRoundup method returns what would be the allocated size of
1127** a memory allocation given a particular requested size. Most memory
1128** allocators round up memory allocations at least to the next multiple
mihailima3f64902008-06-21 13:35:56 +00001129** of 8. Some allocators round up to a larger multiple or to a power of 2.
drh6aa5f152009-08-19 15:57:07 +00001130** Every memory allocation request coming in through [sqlite3_malloc()]
1131** or [sqlite3_realloc()] first calls xRoundup. If xRoundup returns 0,
1132** that causes the corresponding memory allocation to fail.
drhe5ae5732008-06-15 02:51:47 +00001133**
drhfec00ea2008-06-14 16:56:21 +00001134** The xInit method initializes the memory allocator. (For example,
1135** it might allocate any require mutexes or initialize internal data
1136** structures. The xShutdown method is invoked (indirectly) by
1137** [sqlite3_shutdown()] and should deallocate any resources acquired
1138** by xInit. The pAppData pointer is used as the only parameter to
1139** xInit and xShutdown.
drh9ac06502009-08-17 13:42:29 +00001140**
1141** SQLite holds the [SQLITE_MUTEX_STATIC_MASTER] mutex when it invokes
1142** the xInit method, so the xInit method need not be threadsafe. The
1143** xShutdown method is only called from [sqlite3_shutdown()] so it does
drh6aa5f152009-08-19 15:57:07 +00001144** not need to be threadsafe either. For all other methods, SQLite
1145** holds the [SQLITE_MUTEX_STATIC_MEM] mutex as long as the
1146** [SQLITE_CONFIG_MEMSTATUS] configuration option is turned on (which
1147** it is by default) and so the methods are automatically serialized.
1148** However, if [SQLITE_CONFIG_MEMSTATUS] is disabled, then the other
1149** methods must be threadsafe or else make their own arrangements for
1150** serialization.
drh9ac06502009-08-17 13:42:29 +00001151**
1152** SQLite will never invoke xInit() more than once without an intervening
1153** call to xShutdown().
drhfec00ea2008-06-14 16:56:21 +00001154*/
1155typedef struct sqlite3_mem_methods sqlite3_mem_methods;
1156struct sqlite3_mem_methods {
1157 void *(*xMalloc)(int); /* Memory allocation function */
1158 void (*xFree)(void*); /* Free a prior allocation */
1159 void *(*xRealloc)(void*,int); /* Resize an allocation */
1160 int (*xSize)(void*); /* Return the size of an allocation */
1161 int (*xRoundup)(int); /* Round up request size to allocation size */
1162 int (*xInit)(void*); /* Initialize the memory allocator */
1163 void (*xShutdown)(void*); /* Deinitialize the memory allocator */
1164 void *pAppData; /* Argument to xInit() and xShutdown() */
1165};
1166
1167/*
drhfb434032009-12-11 23:11:26 +00001168** CAPI3REF: Configuration Options
drhce5a5a02008-06-10 17:41:44 +00001169**
1170** These constants are the available integer configuration options that
1171** can be passed as the first argument to the [sqlite3_config()] interface.
mihailima3f64902008-06-21 13:35:56 +00001172**
drha911abe2008-07-16 13:29:51 +00001173** New configuration options may be added in future releases of SQLite.
1174** Existing configuration options might be discontinued. Applications
1175** should check the return code from [sqlite3_config()] to make sure that
1176** the call worked. The [sqlite3_config()] interface will return a
1177** non-zero [error code] if a discontinued or unsupported configuration option
1178** is invoked.
1179**
drhce5a5a02008-06-10 17:41:44 +00001180** <dl>
1181** <dt>SQLITE_CONFIG_SINGLETHREAD</dt>
drhd68eee02009-12-11 03:44:18 +00001182** <dd>There are no arguments to this option. ^This option sets the
1183** [threading mode] to Single-thread. In other words, it disables
drhce5a5a02008-06-10 17:41:44 +00001184** all mutexing and puts SQLite into a mode where it can only be used
drhd68eee02009-12-11 03:44:18 +00001185** by a single thread. ^If SQLite is compiled with
1186** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1187** it is not possible to change the [threading mode] from its default
1188** value of Single-thread and so [sqlite3_config()] will return
1189** [SQLITE_ERROR] if called with the SQLITE_CONFIG_SINGLETHREAD
1190** configuration option.</dd>
drhce5a5a02008-06-10 17:41:44 +00001191**
1192** <dt>SQLITE_CONFIG_MULTITHREAD</dt>
drhd68eee02009-12-11 03:44:18 +00001193** <dd>There are no arguments to this option. ^This option sets the
1194** [threading mode] to Multi-thread. In other words, it disables
drhce5a5a02008-06-10 17:41:44 +00001195** mutexing on [database connection] and [prepared statement] objects.
1196** The application is responsible for serializing access to
1197** [database connections] and [prepared statements]. But other mutexes
1198** are enabled so that SQLite will be safe to use in a multi-threaded
drhafacce02008-09-02 21:35:03 +00001199** environment as long as no two threads attempt to use the same
drhd68eee02009-12-11 03:44:18 +00001200** [database connection] at the same time. ^If SQLite is compiled with
1201** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1202** it is not possible to set the Multi-thread [threading mode] and
1203** [sqlite3_config()] will return [SQLITE_ERROR] if called with the
1204** SQLITE_CONFIG_MULTITHREAD configuration option.</dd>
drhce5a5a02008-06-10 17:41:44 +00001205**
1206** <dt>SQLITE_CONFIG_SERIALIZED</dt>
drhd68eee02009-12-11 03:44:18 +00001207** <dd>There are no arguments to this option. ^This option sets the
1208** [threading mode] to Serialized. In other words, this option enables
drhce5a5a02008-06-10 17:41:44 +00001209** all mutexes including the recursive
1210** mutexes on [database connection] and [prepared statement] objects.
1211** In this mode (which is the default when SQLite is compiled with
drh4766b292008-06-26 02:53:02 +00001212** [SQLITE_THREADSAFE=1]) the SQLite library will itself serialize access
drhce5a5a02008-06-10 17:41:44 +00001213** to [database connections] and [prepared statements] so that the
1214** application is free to use the same [database connection] or the
drh31d38cf2008-07-12 20:35:08 +00001215** same [prepared statement] in different threads at the same time.
drhd68eee02009-12-11 03:44:18 +00001216** ^If SQLite is compiled with
1217** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1218** it is not possible to set the Serialized [threading mode] and
1219** [sqlite3_config()] will return [SQLITE_ERROR] if called with the
1220** SQLITE_CONFIG_SERIALIZED configuration option.</dd>
drhce5a5a02008-06-10 17:41:44 +00001221**
1222** <dt>SQLITE_CONFIG_MALLOC</dt>
drhd68eee02009-12-11 03:44:18 +00001223** <dd> ^(This option takes a single argument which is a pointer to an
mihailimdb4f2ad2008-06-21 11:20:48 +00001224** instance of the [sqlite3_mem_methods] structure. The argument specifies
1225** alternative low-level memory allocation routines to be used in place of
drhd68eee02009-12-11 03:44:18 +00001226** the memory allocation routines built into SQLite.)^ ^SQLite makes
1227** its own private copy of the content of the [sqlite3_mem_methods] structure
1228** before the [sqlite3_config()] call returns.</dd>
drhce5a5a02008-06-10 17:41:44 +00001229**
drh33589792008-06-18 13:27:46 +00001230** <dt>SQLITE_CONFIG_GETMALLOC</dt>
drhd68eee02009-12-11 03:44:18 +00001231** <dd> ^(This option takes a single argument which is a pointer to an
drh33589792008-06-18 13:27:46 +00001232** instance of the [sqlite3_mem_methods] structure. The [sqlite3_mem_methods]
drhd68eee02009-12-11 03:44:18 +00001233** structure is filled with the currently defined memory allocation routines.)^
drh33589792008-06-18 13:27:46 +00001234** This option can be used to overload the default memory allocation
1235** routines with a wrapper that simulations memory allocation failure or
drhd68eee02009-12-11 03:44:18 +00001236** tracks memory usage, for example. </dd>
drh33589792008-06-18 13:27:46 +00001237**
drhfec00ea2008-06-14 16:56:21 +00001238** <dt>SQLITE_CONFIG_MEMSTATUS</dt>
drhd68eee02009-12-11 03:44:18 +00001239** <dd> ^This option takes single argument of type int, interpreted as a
danielk197795c232d2008-07-28 05:22:35 +00001240** boolean, which enables or disables the collection of memory allocation
drhd68eee02009-12-11 03:44:18 +00001241** statistics. ^(When memory allocation statistics are disabled, the
1242** following SQLite interfaces become non-operational:
drhce5a5a02008-06-10 17:41:44 +00001243** <ul>
1244** <li> [sqlite3_memory_used()]
1245** <li> [sqlite3_memory_highwater()]
1246** <li> [sqlite3_soft_heap_limit()]
drh0a60a382008-07-31 17:16:05 +00001247** <li> [sqlite3_status()]
drhd68eee02009-12-11 03:44:18 +00001248** </ul>)^
1249** ^Memory allocation statistics are enabled by default unless SQLite is
1250** compiled with [SQLITE_DEFAULT_MEMSTATUS]=0 in which case memory
1251** allocation statistics are disabled by default.
drhce5a5a02008-06-10 17:41:44 +00001252** </dd>
drh33589792008-06-18 13:27:46 +00001253**
1254** <dt>SQLITE_CONFIG_SCRATCH</dt>
drhd68eee02009-12-11 03:44:18 +00001255** <dd> ^This option specifies a static memory buffer that SQLite can use for
drh6860da02009-06-09 19:53:58 +00001256** scratch memory. There are three arguments: A pointer an 8-byte
1257** aligned memory buffer from which the scrach allocations will be
1258** drawn, the size of each scratch allocation (sz),
1259** and the maximum number of scratch allocations (N). The sz
drh0a60a382008-07-31 17:16:05 +00001260** argument must be a multiple of 16. The sz parameter should be a few bytes
drh6860da02009-06-09 19:53:58 +00001261** larger than the actual scratch space required due to internal overhead.
drhd68eee02009-12-11 03:44:18 +00001262** The first argument must be a pointer to an 8-byte aligned buffer
drh6860da02009-06-09 19:53:58 +00001263** of at least sz*N bytes of memory.
drhd68eee02009-12-11 03:44:18 +00001264** ^SQLite will use no more than one scratch buffer per thread. So
1265** N should be set to the expected maximum number of threads. ^SQLite will
1266** never require a scratch buffer that is more than 6 times the database
1267** page size. ^If SQLite needs needs additional scratch memory beyond
1268** what is provided by this configuration option, then
1269** [sqlite3_malloc()] will be used to obtain the memory needed.</dd>
drh33589792008-06-18 13:27:46 +00001270**
1271** <dt>SQLITE_CONFIG_PAGECACHE</dt>
drhd68eee02009-12-11 03:44:18 +00001272** <dd> ^This option specifies a static memory buffer that SQLite can use for
drh21614742008-11-18 19:18:08 +00001273** the database page cache with the default page cache implemenation.
1274** This configuration should not be used if an application-define page
1275** cache implementation is loaded using the SQLITE_CONFIG_PCACHE option.
drh6860da02009-06-09 19:53:58 +00001276** There are three arguments to this option: A pointer to 8-byte aligned
mihailimdb4f2ad2008-06-21 11:20:48 +00001277** memory, the size of each page buffer (sz), and the number of pages (N).
drh6860da02009-06-09 19:53:58 +00001278** The sz argument should be the size of the largest database page
1279** (a power of two between 512 and 32768) plus a little extra for each
drhd68eee02009-12-11 03:44:18 +00001280** page header. ^The page header size is 20 to 40 bytes depending on
1281** the host architecture. ^It is harmless, apart from the wasted memory,
drh6860da02009-06-09 19:53:58 +00001282** to make sz a little too large. The first
drh0a60a382008-07-31 17:16:05 +00001283** argument should point to an allocation of at least sz*N bytes of memory.
drhd68eee02009-12-11 03:44:18 +00001284** ^SQLite will use the memory provided by the first argument to satisfy its
1285** memory needs for the first N pages that it adds to cache. ^If additional
mihailimdb4f2ad2008-06-21 11:20:48 +00001286** page cache memory is needed beyond what is provided by this option, then
drh0a60a382008-07-31 17:16:05 +00001287** SQLite goes to [sqlite3_malloc()] for the additional storage space.
drhd68eee02009-12-11 03:44:18 +00001288** ^The implementation might use one or more of the N buffers to hold
drh6860da02009-06-09 19:53:58 +00001289** memory accounting information. The pointer in the first argument must
1290** be aligned to an 8-byte boundary or subsequent behavior of SQLite
1291** will be undefined.</dd>
drh33589792008-06-18 13:27:46 +00001292**
1293** <dt>SQLITE_CONFIG_HEAP</dt>
drhd68eee02009-12-11 03:44:18 +00001294** <dd> ^This option specifies a static memory buffer that SQLite will use
drh33589792008-06-18 13:27:46 +00001295** for all of its dynamic memory allocation needs beyond those provided
1296** for by [SQLITE_CONFIG_SCRATCH] and [SQLITE_CONFIG_PAGECACHE].
drh6860da02009-06-09 19:53:58 +00001297** There are three arguments: An 8-byte aligned pointer to the memory,
1298** the number of bytes in the memory buffer, and the minimum allocation size.
drhd68eee02009-12-11 03:44:18 +00001299** ^If the first pointer (the memory pointer) is NULL, then SQLite reverts
drh8a42cbd2008-07-10 18:13:42 +00001300** to using its default memory allocator (the system malloc() implementation),
drhd68eee02009-12-11 03:44:18 +00001301** undoing any prior invocation of [SQLITE_CONFIG_MALLOC]. ^If the
drh8a42cbd2008-07-10 18:13:42 +00001302** memory pointer is not NULL and either [SQLITE_ENABLE_MEMSYS3] or
1303** [SQLITE_ENABLE_MEMSYS5] are defined, then the alternative memory
drh39bf74a2009-06-09 18:02:10 +00001304** allocator is engaged to handle all of SQLites memory allocation needs.
1305** The first pointer (the memory pointer) must be aligned to an 8-byte
drh6860da02009-06-09 19:53:58 +00001306** boundary or subsequent behavior of SQLite will be undefined.</dd>
drh33589792008-06-18 13:27:46 +00001307**
1308** <dt>SQLITE_CONFIG_MUTEX</dt>
drhd68eee02009-12-11 03:44:18 +00001309** <dd> ^(This option takes a single argument which is a pointer to an
mihailimdb4f2ad2008-06-21 11:20:48 +00001310** instance of the [sqlite3_mutex_methods] structure. The argument specifies
drh33589792008-06-18 13:27:46 +00001311** alternative low-level mutex routines to be used in place
drhd68eee02009-12-11 03:44:18 +00001312** the mutex routines built into SQLite.)^ ^SQLite makes a copy of the
1313** content of the [sqlite3_mutex_methods] structure before the call to
1314** [sqlite3_config()] returns. ^If SQLite is compiled with
1315** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1316** the entire mutexing subsystem is omitted from the build and hence calls to
1317** [sqlite3_config()] with the SQLITE_CONFIG_MUTEX configuration option will
1318** return [SQLITE_ERROR].</dd>
drh33589792008-06-18 13:27:46 +00001319**
drh584ff182008-07-14 18:38:17 +00001320** <dt>SQLITE_CONFIG_GETMUTEX</dt>
drhd68eee02009-12-11 03:44:18 +00001321** <dd> ^(This option takes a single argument which is a pointer to an
drh33589792008-06-18 13:27:46 +00001322** instance of the [sqlite3_mutex_methods] structure. The
1323** [sqlite3_mutex_methods]
drhd68eee02009-12-11 03:44:18 +00001324** structure is filled with the currently defined mutex routines.)^
drh33589792008-06-18 13:27:46 +00001325** This option can be used to overload the default mutex allocation
1326** routines with a wrapper used to track mutex usage for performance
drhd68eee02009-12-11 03:44:18 +00001327** profiling or testing, for example. ^If SQLite is compiled with
1328** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then
1329** the entire mutexing subsystem is omitted from the build and hence calls to
1330** [sqlite3_config()] with the SQLITE_CONFIG_GETMUTEX configuration option will
1331** return [SQLITE_ERROR].</dd>
drh633e6d52008-07-28 19:34:53 +00001332**
1333** <dt>SQLITE_CONFIG_LOOKASIDE</dt>
drhd68eee02009-12-11 03:44:18 +00001334** <dd> ^(This option takes two arguments that determine the default
drh9be37f62009-12-12 23:57:36 +00001335** memory allocation for the lookaside memory allocator on each
1336** [database connection]. The first argument is the
drh633e6d52008-07-28 19:34:53 +00001337** size of each lookaside buffer slot and the second is the number of
drhd68eee02009-12-11 03:44:18 +00001338** slots allocated to each database connection.)^ ^(This option sets the
1339** <i>default</i> lookaside size. The [SQLITE_DBCONFIG_LOOKASIDE]
drh6aa5f152009-08-19 15:57:07 +00001340** verb to [sqlite3_db_config()] can be used to change the lookaside
drhd68eee02009-12-11 03:44:18 +00001341** configuration on individual connections.)^ </dd>
drh633e6d52008-07-28 19:34:53 +00001342**
drh21614742008-11-18 19:18:08 +00001343** <dt>SQLITE_CONFIG_PCACHE</dt>
drhd68eee02009-12-11 03:44:18 +00001344** <dd> ^(This option takes a single argument which is a pointer to
drh21614742008-11-18 19:18:08 +00001345** an [sqlite3_pcache_methods] object. This object specifies the interface
drhd68eee02009-12-11 03:44:18 +00001346** to a custom page cache implementation.)^ ^SQLite makes a copy of the
drh21614742008-11-18 19:18:08 +00001347** object and uses it for page cache memory allocations.</dd>
1348**
1349** <dt>SQLITE_CONFIG_GETPCACHE</dt>
drhd68eee02009-12-11 03:44:18 +00001350** <dd> ^(This option takes a single argument which is a pointer to an
drh21614742008-11-18 19:18:08 +00001351** [sqlite3_pcache_methods] object. SQLite copies of the current
drhd68eee02009-12-11 03:44:18 +00001352** page cache implementation into that object.)^ </dd>
drh21614742008-11-18 19:18:08 +00001353**
drhd3d986d2010-03-31 13:57:56 +00001354** <dt>SQLITE_CONFIG_LOG</dt>
1355** <dd> ^The SQLITE_CONFIG_LOG option takes two arguments: a pointer to a
1356** function with a call signature of void(*)(void*,int,const char*),
1357** and a pointer to void. ^If the function pointer is not NULL, it is
1358** invoked by [sqlite3_log()] to process each logging event. ^If the
1359** function pointer is NULL, the [sqlite3_log()] interface becomes a no-op.
1360** ^The void pointer that is the second argument to SQLITE_CONFIG_LOG is
1361** passed through as the first parameter to the application-defined logger
1362** function whenever that function is invoked. ^The second parameter to
1363** the logger function is a copy of the first parameter to the corresponding
1364** [sqlite3_log()] call and is intended to be a [result code] or an
1365** [extended result code]. ^The third parameter passed to the logger is
1366** log message after formatting via [sqlite3_snprintf()].
1367** The SQLite logging interface is not reentrant; the logger function
1368** supplied by the application must not invoke any SQLite interface.
1369** In a multi-threaded application, the application-defined logger
1370** function must be threadsafe. </dd>
1371**
drh633e6d52008-07-28 19:34:53 +00001372** </dl>
mihailima3f64902008-06-21 13:35:56 +00001373*/
drh40257ff2008-06-13 18:24:27 +00001374#define SQLITE_CONFIG_SINGLETHREAD 1 /* nil */
1375#define SQLITE_CONFIG_MULTITHREAD 2 /* nil */
1376#define SQLITE_CONFIG_SERIALIZED 3 /* nil */
drhfec00ea2008-06-14 16:56:21 +00001377#define SQLITE_CONFIG_MALLOC 4 /* sqlite3_mem_methods* */
drh33589792008-06-18 13:27:46 +00001378#define SQLITE_CONFIG_GETMALLOC 5 /* sqlite3_mem_methods* */
1379#define SQLITE_CONFIG_SCRATCH 6 /* void*, int sz, int N */
1380#define SQLITE_CONFIG_PAGECACHE 7 /* void*, int sz, int N */
1381#define SQLITE_CONFIG_HEAP 8 /* void*, int nByte, int min */
1382#define SQLITE_CONFIG_MEMSTATUS 9 /* boolean */
1383#define SQLITE_CONFIG_MUTEX 10 /* sqlite3_mutex_methods* */
1384#define SQLITE_CONFIG_GETMUTEX 11 /* sqlite3_mutex_methods* */
shane2479de32008-11-10 18:05:35 +00001385/* previously SQLITE_CONFIG_CHUNKALLOC 12 which is now unused. */
drh633e6d52008-07-28 19:34:53 +00001386#define SQLITE_CONFIG_LOOKASIDE 13 /* int int */
danielk1977bc2ca9e2008-11-13 14:28:28 +00001387#define SQLITE_CONFIG_PCACHE 14 /* sqlite3_pcache_methods* */
1388#define SQLITE_CONFIG_GETPCACHE 15 /* sqlite3_pcache_methods* */
drh3f280702010-02-18 18:45:09 +00001389#define SQLITE_CONFIG_LOG 16 /* xFunc, void* */
danielk19772d340812008-07-24 08:20:40 +00001390
drhe9d1c722008-08-04 20:13:26 +00001391/*
drh9f8da322010-03-10 20:06:37 +00001392** CAPI3REF: Database Connection Configuration Options
drhe9d1c722008-08-04 20:13:26 +00001393**
1394** These constants are the available integer configuration options that
1395** can be passed as the second argument to the [sqlite3_db_config()] interface.
1396**
1397** New configuration options may be added in future releases of SQLite.
1398** Existing configuration options might be discontinued. Applications
1399** should check the return code from [sqlite3_db_config()] to make sure that
drhd68eee02009-12-11 03:44:18 +00001400** the call worked. ^The [sqlite3_db_config()] interface will return a
drhe9d1c722008-08-04 20:13:26 +00001401** non-zero [error code] if a discontinued or unsupported configuration option
1402** is invoked.
1403**
1404** <dl>
1405** <dt>SQLITE_DBCONFIG_LOOKASIDE</dt>
drhd68eee02009-12-11 03:44:18 +00001406** <dd> ^This option takes three additional arguments that determine the
drhe9d1c722008-08-04 20:13:26 +00001407** [lookaside memory allocator] configuration for the [database connection].
drhd68eee02009-12-11 03:44:18 +00001408** ^The first argument (the third parameter to [sqlite3_db_config()] is a
drh6aa5f152009-08-19 15:57:07 +00001409** pointer to an memory buffer to use for lookaside memory.
drhd68eee02009-12-11 03:44:18 +00001410** ^The first argument after the SQLITE_DBCONFIG_LOOKASIDE verb
1411** may be NULL in which case SQLite will allocate the
1412** lookaside buffer itself using [sqlite3_malloc()]. ^The second argument is the
1413** size of each lookaside buffer slot. ^The third argument is the number of
drhe9d1c722008-08-04 20:13:26 +00001414** slots. The size of the buffer in the first argument must be greater than
drh6aa5f152009-08-19 15:57:07 +00001415** or equal to the product of the second and third arguments. The buffer
drhd68eee02009-12-11 03:44:18 +00001416** must be aligned to an 8-byte boundary. ^If the second argument to
1417** SQLITE_DBCONFIG_LOOKASIDE is not a multiple of 8, it is internally
1418** rounded down to the next smaller
drh6aa5f152009-08-19 15:57:07 +00001419** multiple of 8. See also: [SQLITE_CONFIG_LOOKASIDE]</dd>
drhe9d1c722008-08-04 20:13:26 +00001420**
1421** </dl>
1422*/
1423#define SQLITE_DBCONFIG_LOOKASIDE 1001 /* void* int int */
1424
drhce5a5a02008-06-10 17:41:44 +00001425
drh673299b2008-06-09 21:57:22 +00001426/*
drhd68eee02009-12-11 03:44:18 +00001427** CAPI3REF: Enable Or Disable Extended Result Codes
drh6ed48bf2007-06-14 20:57:18 +00001428**
drhd68eee02009-12-11 03:44:18 +00001429** ^The sqlite3_extended_result_codes() routine enables or disables the
1430** [extended result codes] feature of SQLite. ^The extended result
1431** codes are disabled by default for historical compatibility.
drh4ac285a2006-09-15 07:28:50 +00001432*/
1433int sqlite3_extended_result_codes(sqlite3*, int onoff);
1434
1435/*
drhd68eee02009-12-11 03:44:18 +00001436** CAPI3REF: Last Insert Rowid
drh6ed48bf2007-06-14 20:57:18 +00001437**
drhd68eee02009-12-11 03:44:18 +00001438** ^Each entry in an SQLite table has a unique 64-bit signed
1439** integer key called the [ROWID | "rowid"]. ^The rowid is always available
drhfddfa2d2007-12-05 18:05:16 +00001440** as an undeclared column named ROWID, OID, or _ROWID_ as long as those
drhd68eee02009-12-11 03:44:18 +00001441** names are not also used by explicitly declared columns. ^If
drh49c3d572008-12-15 22:51:38 +00001442** the table has a column of type [INTEGER PRIMARY KEY] then that column
mlcreechb2799412008-03-07 03:20:31 +00001443** is another alias for the rowid.
drh6ed48bf2007-06-14 20:57:18 +00001444**
drhd68eee02009-12-11 03:44:18 +00001445** ^This routine returns the [rowid] of the most recent
drhf8cecda2008-10-10 23:48:25 +00001446** successful [INSERT] into the database from the [database connection]
drhd68eee02009-12-11 03:44:18 +00001447** in the first argument. ^If no successful [INSERT]s
mihailimdb4f2ad2008-06-21 11:20:48 +00001448** have ever occurred on that database connection, zero is returned.
drh6ed48bf2007-06-14 20:57:18 +00001449**
drhd68eee02009-12-11 03:44:18 +00001450** ^(If an [INSERT] occurs within a trigger, then the [rowid] of the inserted
mihailimdb4f2ad2008-06-21 11:20:48 +00001451** row is returned by this routine as long as the trigger is running.
1452** But once the trigger terminates, the value returned by this routine
drhd68eee02009-12-11 03:44:18 +00001453** reverts to the last value inserted before the trigger fired.)^
drhe30f4422007-08-21 16:15:55 +00001454**
drhd68eee02009-12-11 03:44:18 +00001455** ^An [INSERT] that fails due to a constraint violation is not a
drhf8cecda2008-10-10 23:48:25 +00001456** successful [INSERT] and does not change the value returned by this
drhd68eee02009-12-11 03:44:18 +00001457** routine. ^Thus INSERT OR FAIL, INSERT OR IGNORE, INSERT OR ROLLBACK,
drhdc1d9f12007-10-27 16:25:16 +00001458** and INSERT OR ABORT make no changes to the return value of this
drhd68eee02009-12-11 03:44:18 +00001459** routine when their insertion fails. ^(When INSERT OR REPLACE
drhdc1d9f12007-10-27 16:25:16 +00001460** encounters a constraint violation, it does not fail. The
1461** INSERT continues to completion after deleting rows that caused
1462** the constraint problem so INSERT OR REPLACE will always change
drhd68eee02009-12-11 03:44:18 +00001463** the return value of this interface.)^
drhdc1d9f12007-10-27 16:25:16 +00001464**
drhd68eee02009-12-11 03:44:18 +00001465** ^For the purposes of this routine, an [INSERT] is considered to
drh33c1be32008-01-30 16:16:14 +00001466** be successful even if it is subsequently rolled back.
1467**
drha94cc422009-12-03 01:01:02 +00001468** This function is accessible to SQL statements via the
1469** [last_insert_rowid() SQL function].
1470**
drh8b39db12009-02-18 18:37:58 +00001471** If a separate thread performs a new [INSERT] on the same
1472** database connection while the [sqlite3_last_insert_rowid()]
1473** function is running and thus changes the last insert [rowid],
1474** then the value returned by [sqlite3_last_insert_rowid()] is
1475** unpredictable and might not equal either the old or the new
1476** last insert [rowid].
drhaf9ff332002-01-16 21:00:27 +00001477*/
drh6d2069d2007-08-14 01:58:53 +00001478sqlite3_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +00001479
drhc8d30ac2002-04-12 10:08:59 +00001480/*
drhd68eee02009-12-11 03:44:18 +00001481** CAPI3REF: Count The Number Of Rows Modified
drh6ed48bf2007-06-14 20:57:18 +00001482**
drhd68eee02009-12-11 03:44:18 +00001483** ^This function returns the number of database rows that were changed
drhfddfa2d2007-12-05 18:05:16 +00001484** or inserted or deleted by the most recently completed SQL statement
mihailimdb4f2ad2008-06-21 11:20:48 +00001485** on the [database connection] specified by the first parameter.
drhd68eee02009-12-11 03:44:18 +00001486** ^(Only changes that are directly specified by the [INSERT], [UPDATE],
drhf8cecda2008-10-10 23:48:25 +00001487** or [DELETE] statement are counted. Auxiliary changes caused by
drhd68eee02009-12-11 03:44:18 +00001488** triggers or [foreign key actions] are not counted.)^ Use the
danb6163092009-10-07 10:43:26 +00001489** [sqlite3_total_changes()] function to find the total number of changes
1490** including changes caused by triggers and foreign key actions.
drh6ed48bf2007-06-14 20:57:18 +00001491**
drhd68eee02009-12-11 03:44:18 +00001492** ^Changes to a view that are simulated by an [INSTEAD OF trigger]
drhd9c20d72009-04-29 14:33:44 +00001493** are not counted. Only real table changes are counted.
1494**
drhd68eee02009-12-11 03:44:18 +00001495** ^(A "row change" is a change to a single row of a single table
drh33c1be32008-01-30 16:16:14 +00001496** caused by an INSERT, DELETE, or UPDATE statement. Rows that
drhd9c20d72009-04-29 14:33:44 +00001497** are changed as side effects of [REPLACE] constraint resolution,
1498** rollback, ABORT processing, [DROP TABLE], or by any other
drhd68eee02009-12-11 03:44:18 +00001499** mechanisms do not count as direct row changes.)^
drh33c1be32008-01-30 16:16:14 +00001500**
1501** A "trigger context" is a scope of execution that begins and
drhd9c20d72009-04-29 14:33:44 +00001502** ends with the script of a [CREATE TRIGGER | trigger].
1503** Most SQL statements are
drh33c1be32008-01-30 16:16:14 +00001504** evaluated outside of any trigger. This is the "top level"
1505** trigger context. If a trigger fires from the top level, a
1506** new trigger context is entered for the duration of that one
1507** trigger. Subtriggers create subcontexts for their duration.
1508**
drhd68eee02009-12-11 03:44:18 +00001509** ^Calling [sqlite3_exec()] or [sqlite3_step()] recursively does
drh33c1be32008-01-30 16:16:14 +00001510** not create a new trigger context.
1511**
drhd68eee02009-12-11 03:44:18 +00001512** ^This function returns the number of direct row changes in the
drh33c1be32008-01-30 16:16:14 +00001513** most recent INSERT, UPDATE, or DELETE statement within the same
1514** trigger context.
1515**
drhd68eee02009-12-11 03:44:18 +00001516** ^Thus, when called from the top level, this function returns the
drh33c1be32008-01-30 16:16:14 +00001517** number of changes in the most recent INSERT, UPDATE, or DELETE
drhd68eee02009-12-11 03:44:18 +00001518** that also occurred at the top level. ^(Within the body of a trigger,
mihailimdb4f2ad2008-06-21 11:20:48 +00001519** the sqlite3_changes() interface can be called to find the number of
drh930cc582007-03-28 13:07:40 +00001520** changes in the most recently completed INSERT, UPDATE, or DELETE
drhf5befa02007-12-06 02:42:07 +00001521** statement within the body of the same trigger.
mihailimdb4f2ad2008-06-21 11:20:48 +00001522** However, the number returned does not include changes
drhd68eee02009-12-11 03:44:18 +00001523** caused by subtriggers since those have their own context.)^
drhc8d30ac2002-04-12 10:08:59 +00001524**
drha94cc422009-12-03 01:01:02 +00001525** See also the [sqlite3_total_changes()] interface, the
1526** [count_changes pragma], and the [changes() SQL function].
drhe30f4422007-08-21 16:15:55 +00001527**
drh8b39db12009-02-18 18:37:58 +00001528** If a separate thread makes changes on the same database connection
1529** while [sqlite3_changes()] is running then the value returned
1530** is unpredictable and not meaningful.
drhc8d30ac2002-04-12 10:08:59 +00001531*/
danielk1977f9d64d22004-06-19 08:18:07 +00001532int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +00001533
rdcf146a772004-02-25 22:51:06 +00001534/*
drhd68eee02009-12-11 03:44:18 +00001535** CAPI3REF: Total Number Of Rows Modified
mihailimdb4f2ad2008-06-21 11:20:48 +00001536**
drhd68eee02009-12-11 03:44:18 +00001537** ^This function returns the number of row changes caused by [INSERT],
drhd9c20d72009-04-29 14:33:44 +00001538** [UPDATE] or [DELETE] statements since the [database connection] was opened.
drhd68eee02009-12-11 03:44:18 +00001539** ^(The count returned by sqlite3_total_changes() includes all changes
1540** from all [CREATE TRIGGER | trigger] contexts and changes made by
1541** [foreign key actions]. However,
drhd9c20d72009-04-29 14:33:44 +00001542** the count does not include changes used to implement [REPLACE] constraints,
1543** do rollbacks or ABORT processing, or [DROP TABLE] processing. The
drh4fb08662009-05-22 01:02:26 +00001544** count does not include rows of views that fire an [INSTEAD OF trigger],
1545** though if the INSTEAD OF trigger makes changes of its own, those changes
drhd68eee02009-12-11 03:44:18 +00001546** are counted.)^
1547** ^The sqlite3_total_changes() function counts the changes as soon as
1548** the statement that makes them is completed (when the statement handle
1549** is passed to [sqlite3_reset()] or [sqlite3_finalize()]).
drh6ed48bf2007-06-14 20:57:18 +00001550**
drha94cc422009-12-03 01:01:02 +00001551** See also the [sqlite3_changes()] interface, the
1552** [count_changes pragma], and the [total_changes() SQL function].
drh33c1be32008-01-30 16:16:14 +00001553**
drh8b39db12009-02-18 18:37:58 +00001554** If a separate thread makes changes on the same database connection
1555** while [sqlite3_total_changes()] is running then the value
1556** returned is unpredictable and not meaningful.
rdcf146a772004-02-25 22:51:06 +00001557*/
danielk1977b28af712004-06-21 06:50:26 +00001558int sqlite3_total_changes(sqlite3*);
1559
drh6ed48bf2007-06-14 20:57:18 +00001560/*
drhd68eee02009-12-11 03:44:18 +00001561** CAPI3REF: Interrupt A Long-Running Query
drh6ed48bf2007-06-14 20:57:18 +00001562**
drhd68eee02009-12-11 03:44:18 +00001563** ^This function causes any pending database operation to abort and
drh33c1be32008-01-30 16:16:14 +00001564** return at its earliest opportunity. This routine is typically
mihailimebe796c2008-06-21 20:11:17 +00001565** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +00001566** or Ctrl-C where the user wants a long query operation to halt
1567** immediately.
drh930cc582007-03-28 13:07:40 +00001568**
drhd68eee02009-12-11 03:44:18 +00001569** ^It is safe to call this routine from a thread different from the
drh33c1be32008-01-30 16:16:14 +00001570** thread that is currently running the database operation. But it
mihailimdb4f2ad2008-06-21 11:20:48 +00001571** is not safe to call this routine with a [database connection] that
drh871f6ca2007-08-14 18:03:14 +00001572** is closed or might close before sqlite3_interrupt() returns.
drh6ed48bf2007-06-14 20:57:18 +00001573**
drhd68eee02009-12-11 03:44:18 +00001574** ^If an SQL operation is very nearly finished at the time when
mihailimdb4f2ad2008-06-21 11:20:48 +00001575** sqlite3_interrupt() is called, then it might not have an opportunity
1576** to be interrupted and might continue to completion.
1577**
drhd68eee02009-12-11 03:44:18 +00001578** ^An SQL operation that is interrupted will return [SQLITE_INTERRUPT].
1579** ^If the interrupted SQL operation is an INSERT, UPDATE, or DELETE
mihailimdb4f2ad2008-06-21 11:20:48 +00001580** that is inside an explicit transaction, then the entire transaction
1581** will be rolled back automatically.
1582**
drhdf6473a2009-12-13 22:20:08 +00001583** ^The sqlite3_interrupt(D) call is in effect until all currently running
1584** SQL statements on [database connection] D complete. ^Any new SQL statements
drhd2b68432009-04-20 12:31:46 +00001585** that are started after the sqlite3_interrupt() call and before the
1586** running statements reaches zero are interrupted as if they had been
drhdf6473a2009-12-13 22:20:08 +00001587** running prior to the sqlite3_interrupt() call. ^New SQL statements
drhd2b68432009-04-20 12:31:46 +00001588** that are started after the running statement count reaches zero are
drhdf6473a2009-12-13 22:20:08 +00001589** not effected by the sqlite3_interrupt().
drhd68eee02009-12-11 03:44:18 +00001590** ^A call to sqlite3_interrupt(D) that occurs when there are no running
drhd2b68432009-04-20 12:31:46 +00001591** SQL statements is a no-op and has no effect on SQL statements
1592** that are started after the sqlite3_interrupt() call returns.
drh33c1be32008-01-30 16:16:14 +00001593**
drh8b39db12009-02-18 18:37:58 +00001594** If the database connection closes while [sqlite3_interrupt()]
1595** is running then bad things will likely happen.
drh4c504392000-10-16 22:06:40 +00001596*/
danielk1977f9d64d22004-06-19 08:18:07 +00001597void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +00001598
drh6ed48bf2007-06-14 20:57:18 +00001599/*
drhd68eee02009-12-11 03:44:18 +00001600** CAPI3REF: Determine If An SQL Statement Is Complete
drh75897232000-05-29 14:26:00 +00001601**
drh709915d2009-04-28 04:46:41 +00001602** These routines are useful during command-line input to determine if the
1603** currently entered text seems to form a complete SQL statement or
drhf5befa02007-12-06 02:42:07 +00001604** if additional input is needed before sending the text into
drhd68eee02009-12-11 03:44:18 +00001605** SQLite for parsing. ^These routines return 1 if the input string
1606** appears to be a complete SQL statement. ^A statement is judged to be
drh709915d2009-04-28 04:46:41 +00001607** complete if it ends with a semicolon token and is not a prefix of a
drhd68eee02009-12-11 03:44:18 +00001608** well-formed CREATE TRIGGER statement. ^Semicolons that are embedded within
drh33c1be32008-01-30 16:16:14 +00001609** string literals or quoted identifier names or comments are not
1610** independent tokens (they are part of the token in which they are
drhd68eee02009-12-11 03:44:18 +00001611** embedded) and thus do not count as a statement terminator. ^Whitespace
drh709915d2009-04-28 04:46:41 +00001612** and comments that follow the final semicolon are ignored.
1613**
drhd68eee02009-12-11 03:44:18 +00001614** ^These routines return 0 if the statement is incomplete. ^If a
drh709915d2009-04-28 04:46:41 +00001615** memory allocation fails, then SQLITE_NOMEM is returned.
drh33c1be32008-01-30 16:16:14 +00001616**
drhd68eee02009-12-11 03:44:18 +00001617** ^These routines do not parse the SQL statements thus
mihailimdb4f2ad2008-06-21 11:20:48 +00001618** will not detect syntactically incorrect SQL.
drhfddfa2d2007-12-05 18:05:16 +00001619**
drhd68eee02009-12-11 03:44:18 +00001620** ^(If SQLite has not been initialized using [sqlite3_initialize()] prior
drh709915d2009-04-28 04:46:41 +00001621** to invoking sqlite3_complete16() then sqlite3_initialize() is invoked
1622** automatically by sqlite3_complete16(). If that initialization fails,
1623** then the return value from sqlite3_complete16() will be non-zero
drhd68eee02009-12-11 03:44:18 +00001624** regardless of whether or not the input SQL is complete.)^
drh33c1be32008-01-30 16:16:14 +00001625**
drh8b39db12009-02-18 18:37:58 +00001626** The input to [sqlite3_complete()] must be a zero-terminated
1627** UTF-8 string.
drh33c1be32008-01-30 16:16:14 +00001628**
drh8b39db12009-02-18 18:37:58 +00001629** The input to [sqlite3_complete16()] must be a zero-terminated
1630** UTF-16 string in native byte order.
drh75897232000-05-29 14:26:00 +00001631*/
danielk19776f8a5032004-05-10 10:34:51 +00001632int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +00001633int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +00001634
drh2dfbbca2000-07-28 14:32:48 +00001635/*
drhd68eee02009-12-11 03:44:18 +00001636** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
drh6ed48bf2007-06-14 20:57:18 +00001637**
drhd68eee02009-12-11 03:44:18 +00001638** ^This routine sets a callback function that might be invoked whenever
mihailimdb4f2ad2008-06-21 11:20:48 +00001639** an attempt is made to open a database table that another thread
1640** or process has locked.
1641**
drhd68eee02009-12-11 03:44:18 +00001642** ^If the busy callback is NULL, then [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED]
1643** is returned immediately upon encountering the lock. ^If the busy callback
1644** is not NULL, then the callback might be invoked with two arguments.
mihailimdb4f2ad2008-06-21 11:20:48 +00001645**
drhd68eee02009-12-11 03:44:18 +00001646** ^The first argument to the busy handler is a copy of the void* pointer which
1647** is the third argument to sqlite3_busy_handler(). ^The second argument to
1648** the busy handler callback is the number of times that the busy handler has
1649** been invoked for this locking event. ^If the
drh6ed48bf2007-06-14 20:57:18 +00001650** busy callback returns 0, then no additional attempts are made to
1651** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
drhd68eee02009-12-11 03:44:18 +00001652** ^If the callback returns non-zero, then another attempt
drhfddfa2d2007-12-05 18:05:16 +00001653** is made to open the database for reading and the cycle repeats.
drh2dfbbca2000-07-28 14:32:48 +00001654**
mihailimdb4f2ad2008-06-21 11:20:48 +00001655** The presence of a busy handler does not guarantee that it will be invoked
drhd68eee02009-12-11 03:44:18 +00001656** when there is lock contention. ^If SQLite determines that invoking the busy
mihailimdb4f2ad2008-06-21 11:20:48 +00001657** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
1658** or [SQLITE_IOERR_BLOCKED] instead of invoking the busy handler.
drh86939b52007-01-10 12:54:51 +00001659** Consider a scenario where one process is holding a read lock that
1660** it is trying to promote to a reserved lock and
1661** a second process is holding a reserved lock that it is trying
1662** to promote to an exclusive lock. The first process cannot proceed
1663** because it is blocked by the second and the second process cannot
1664** proceed because it is blocked by the first. If both processes
drhf5befa02007-12-06 02:42:07 +00001665** invoke the busy handlers, neither will make any progress. Therefore,
drh6ed48bf2007-06-14 20:57:18 +00001666** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
drh86939b52007-01-10 12:54:51 +00001667** will induce the first process to release its read lock and allow
1668** the second process to proceed.
1669**
drhd68eee02009-12-11 03:44:18 +00001670** ^The default busy callback is NULL.
drh2dfbbca2000-07-28 14:32:48 +00001671**
drhd68eee02009-12-11 03:44:18 +00001672** ^The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED]
drhfddfa2d2007-12-05 18:05:16 +00001673** when SQLite is in the middle of a large transaction where all the
drh33c1be32008-01-30 16:16:14 +00001674** changes will not fit into the in-memory cache. SQLite will
drh6ed48bf2007-06-14 20:57:18 +00001675** already hold a RESERVED lock on the database file, but it needs
1676** to promote this lock to EXCLUSIVE so that it can spill cache
1677** pages into the database file without harm to concurrent
drhd68eee02009-12-11 03:44:18 +00001678** readers. ^If it is unable to promote the lock, then the in-memory
drh6ed48bf2007-06-14 20:57:18 +00001679** cache will be left in an inconsistent state and so the error
1680** code is promoted from the relatively benign [SQLITE_BUSY] to
drhd68eee02009-12-11 03:44:18 +00001681** the more severe [SQLITE_IOERR_BLOCKED]. ^This error code promotion
drh33c1be32008-01-30 16:16:14 +00001682** forces an automatic rollback of the changes. See the
mihailimdb4f2ad2008-06-21 11:20:48 +00001683** <a href="/cvstrac/wiki?p=CorruptionFollowingBusyError">
drh6ed48bf2007-06-14 20:57:18 +00001684** CorruptionFollowingBusyError</a> wiki page for a discussion of why
1685** this is important.
mihailimdb4f2ad2008-06-21 11:20:48 +00001686**
drhd68eee02009-12-11 03:44:18 +00001687** ^(There can only be a single busy handler defined for each
mihailimdb4f2ad2008-06-21 11:20:48 +00001688** [database connection]. Setting a new busy handler clears any
drhd68eee02009-12-11 03:44:18 +00001689** previously set handler.)^ ^Note that calling [sqlite3_busy_timeout()]
mihailimdb4f2ad2008-06-21 11:20:48 +00001690** will also set or clear the busy handler.
drhd677b3d2007-08-20 22:48:41 +00001691**
drhc8075422008-09-10 13:09:23 +00001692** The busy callback should not take any actions which modify the
1693** database connection that invoked the busy handler. Any such actions
1694** result in undefined behavior.
1695**
drh8b39db12009-02-18 18:37:58 +00001696** A busy handler must not close the database connection
1697** or [prepared statement] that invoked the busy handler.
drh2dfbbca2000-07-28 14:32:48 +00001698*/
danielk1977f9d64d22004-06-19 08:18:07 +00001699int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +00001700
1701/*
drhd68eee02009-12-11 03:44:18 +00001702** CAPI3REF: Set A Busy Timeout
drh6ed48bf2007-06-14 20:57:18 +00001703**
drhd68eee02009-12-11 03:44:18 +00001704** ^This routine sets a [sqlite3_busy_handler | busy handler] that sleeps
1705** for a specified amount of time when a table is locked. ^The handler
mihailimdb4f2ad2008-06-21 11:20:48 +00001706** will sleep multiple times until at least "ms" milliseconds of sleeping
drhd68eee02009-12-11 03:44:18 +00001707** have accumulated. ^After at least "ms" milliseconds of sleeping,
mihailimdb4f2ad2008-06-21 11:20:48 +00001708** the handler returns 0 which causes [sqlite3_step()] to return
1709** [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
drh2dfbbca2000-07-28 14:32:48 +00001710**
drhd68eee02009-12-11 03:44:18 +00001711** ^Calling this routine with an argument less than or equal to zero
drh2dfbbca2000-07-28 14:32:48 +00001712** turns off all busy handlers.
drh6ed48bf2007-06-14 20:57:18 +00001713**
drhd68eee02009-12-11 03:44:18 +00001714** ^(There can only be a single busy handler for a particular
mihailimdb4f2ad2008-06-21 11:20:48 +00001715** [database connection] any any given moment. If another busy handler
1716** was defined (using [sqlite3_busy_handler()]) prior to calling
drhd68eee02009-12-11 03:44:18 +00001717** this routine, that other busy handler is cleared.)^
drh2dfbbca2000-07-28 14:32:48 +00001718*/
danielk1977f9d64d22004-06-19 08:18:07 +00001719int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +00001720
drhe3710332000-09-29 13:30:53 +00001721/*
drhd68eee02009-12-11 03:44:18 +00001722** CAPI3REF: Convenience Routines For Running Queries
drh6ed48bf2007-06-14 20:57:18 +00001723**
drh33c1be32008-01-30 16:16:14 +00001724** Definition: A <b>result table</b> is memory data structure created by the
1725** [sqlite3_get_table()] interface. A result table records the
1726** complete query results from one or more queries.
drha18c5682000-10-08 22:20:57 +00001727**
drh33c1be32008-01-30 16:16:14 +00001728** The table conceptually has a number of rows and columns. But
1729** these numbers are not part of the result table itself. These
1730** numbers are obtained separately. Let N be the number of rows
1731** and M be the number of columns.
1732**
mihailimdb4f2ad2008-06-21 11:20:48 +00001733** A result table is an array of pointers to zero-terminated UTF-8 strings.
1734** There are (N+1)*M elements in the array. The first M pointers point
1735** to zero-terminated strings that contain the names of the columns.
1736** The remaining entries all point to query results. NULL values result
1737** in NULL pointers. All other values are in their UTF-8 zero-terminated
1738** string representation as returned by [sqlite3_column_text()].
drh33c1be32008-01-30 16:16:14 +00001739**
mihailimdb4f2ad2008-06-21 11:20:48 +00001740** A result table might consist of one or more memory allocations.
drh33c1be32008-01-30 16:16:14 +00001741** It is not safe to pass a result table directly to [sqlite3_free()].
1742** A result table should be deallocated using [sqlite3_free_table()].
1743**
1744** As an example of the result table format, suppose a query result
1745** is as follows:
drha18c5682000-10-08 22:20:57 +00001746**
drh8bacf972007-08-25 16:21:29 +00001747** <blockquote><pre>
drha18c5682000-10-08 22:20:57 +00001748** Name | Age
1749** -----------------------
1750** Alice | 43
1751** Bob | 28
1752** Cindy | 21
drh8bacf972007-08-25 16:21:29 +00001753** </pre></blockquote>
drha18c5682000-10-08 22:20:57 +00001754**
drh33c1be32008-01-30 16:16:14 +00001755** There are two column (M==2) and three rows (N==3). Thus the
1756** result table has 8 entries. Suppose the result table is stored
1757** in an array names azResult. Then azResult holds this content:
drha18c5682000-10-08 22:20:57 +00001758**
drh8bacf972007-08-25 16:21:29 +00001759** <blockquote><pre>
1760** azResult&#91;0] = "Name";
1761** azResult&#91;1] = "Age";
1762** azResult&#91;2] = "Alice";
1763** azResult&#91;3] = "43";
1764** azResult&#91;4] = "Bob";
1765** azResult&#91;5] = "28";
1766** azResult&#91;6] = "Cindy";
1767** azResult&#91;7] = "21";
1768** </pre></blockquote>
drha18c5682000-10-08 22:20:57 +00001769**
drhd68eee02009-12-11 03:44:18 +00001770** ^The sqlite3_get_table() function evaluates one or more
drh33c1be32008-01-30 16:16:14 +00001771** semicolon-separated SQL statements in the zero-terminated UTF-8
drhd68eee02009-12-11 03:44:18 +00001772** string of its 2nd parameter and returns a result table to the
drh33c1be32008-01-30 16:16:14 +00001773** pointer given in its 3rd parameter.
drha18c5682000-10-08 22:20:57 +00001774**
drhd68eee02009-12-11 03:44:18 +00001775** After the application has finished with the result from sqlite3_get_table(),
1776** it should pass the result table pointer to sqlite3_free_table() in order to
mihailimdb4f2ad2008-06-21 11:20:48 +00001777** release the memory that was malloced. Because of the way the
drh33c1be32008-01-30 16:16:14 +00001778** [sqlite3_malloc()] happens within sqlite3_get_table(), the calling
mihailimdb4f2ad2008-06-21 11:20:48 +00001779** function must not try to call [sqlite3_free()] directly. Only
drh33c1be32008-01-30 16:16:14 +00001780** [sqlite3_free_table()] is able to release the memory properly and safely.
drhe3710332000-09-29 13:30:53 +00001781**
drhd68eee02009-12-11 03:44:18 +00001782** ^(The sqlite3_get_table() interface is implemented as a wrapper around
drh33c1be32008-01-30 16:16:14 +00001783** [sqlite3_exec()]. The sqlite3_get_table() routine does not have access
1784** to any internal data structures of SQLite. It uses only the public
1785** interface defined here. As a consequence, errors that occur in the
1786** wrapper layer outside of the internal [sqlite3_exec()] call are not
drhd68eee02009-12-11 03:44:18 +00001787** reflected in subsequent calls to [sqlite3_errcode()] or
1788** [sqlite3_errmsg()].)^
drhe3710332000-09-29 13:30:53 +00001789*/
danielk19776f8a5032004-05-10 10:34:51 +00001790int sqlite3_get_table(
drhcf538f42008-06-27 14:51:52 +00001791 sqlite3 *db, /* An open database */
1792 const char *zSql, /* SQL to be evaluated */
1793 char ***pazResult, /* Results of the query */
1794 int *pnRow, /* Number of result rows written here */
1795 int *pnColumn, /* Number of result columns written here */
1796 char **pzErrmsg /* Error msg written here */
drhe3710332000-09-29 13:30:53 +00001797);
danielk19776f8a5032004-05-10 10:34:51 +00001798void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +00001799
drha18c5682000-10-08 22:20:57 +00001800/*
drhd68eee02009-12-11 03:44:18 +00001801** CAPI3REF: Formatted String Printing Functions
drh6ed48bf2007-06-14 20:57:18 +00001802**
shane7c7c3112009-08-17 15:31:23 +00001803** These routines are work-alikes of the "printf()" family of functions
drh6ed48bf2007-06-14 20:57:18 +00001804** from the standard C library.
1805**
drhd68eee02009-12-11 03:44:18 +00001806** ^The sqlite3_mprintf() and sqlite3_vmprintf() routines write their
drh6d2069d2007-08-14 01:58:53 +00001807** results into memory obtained from [sqlite3_malloc()].
drh33c1be32008-01-30 16:16:14 +00001808** The strings returned by these two routines should be
drhd68eee02009-12-11 03:44:18 +00001809** released by [sqlite3_free()]. ^Both routines return a
drh6ed48bf2007-06-14 20:57:18 +00001810** NULL pointer if [sqlite3_malloc()] is unable to allocate enough
1811** memory to hold the resulting string.
1812**
drhd68eee02009-12-11 03:44:18 +00001813** ^(In sqlite3_snprintf() routine is similar to "snprintf()" from
drh6ed48bf2007-06-14 20:57:18 +00001814** the standard C library. The result is written into the
1815** buffer supplied as the second parameter whose size is given by
drh33c1be32008-01-30 16:16:14 +00001816** the first parameter. Note that the order of the
drhd68eee02009-12-11 03:44:18 +00001817** first two parameters is reversed from snprintf().)^ This is an
drh6ed48bf2007-06-14 20:57:18 +00001818** historical accident that cannot be fixed without breaking
drhd68eee02009-12-11 03:44:18 +00001819** backwards compatibility. ^(Note also that sqlite3_snprintf()
drh6ed48bf2007-06-14 20:57:18 +00001820** returns a pointer to its buffer instead of the number of
drhd68eee02009-12-11 03:44:18 +00001821** characters actually written into the buffer.)^ We admit that
drh6ed48bf2007-06-14 20:57:18 +00001822** the number of characters written would be a more useful return
1823** value but we cannot change the implementation of sqlite3_snprintf()
1824** now without breaking compatibility.
1825**
drhd68eee02009-12-11 03:44:18 +00001826** ^As long as the buffer size is greater than zero, sqlite3_snprintf()
1827** guarantees that the buffer is always zero-terminated. ^The first
drh6ed48bf2007-06-14 20:57:18 +00001828** parameter "n" is the total size of the buffer, including space for
drh33c1be32008-01-30 16:16:14 +00001829** the zero terminator. So the longest string that can be completely
drh6ed48bf2007-06-14 20:57:18 +00001830** written will be n-1 characters.
1831**
1832** These routines all implement some additional formatting
drh4f26d6c2004-05-26 23:25:30 +00001833** options that are useful for constructing SQL statements.
shane26b34032008-05-23 17:21:09 +00001834** All of the usual printf() formatting options apply. In addition, there
drh153c62c2007-08-24 03:51:33 +00001835** is are "%q", "%Q", and "%z" options.
drh6ed48bf2007-06-14 20:57:18 +00001836**
drhd68eee02009-12-11 03:44:18 +00001837** ^(The %q option works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +00001838** string from the argument list. But %q also doubles every '\'' character.
drhd68eee02009-12-11 03:44:18 +00001839** %q is designed for use inside a string literal.)^ By doubling each '\''
drh66b89c82000-11-28 20:47:17 +00001840** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +00001841** the string.
1842**
mihailimdb4f2ad2008-06-21 11:20:48 +00001843** For example, assume the string variable zText contains text as follows:
drha18c5682000-10-08 22:20:57 +00001844**
drh6ed48bf2007-06-14 20:57:18 +00001845** <blockquote><pre>
1846** char *zText = "It's a happy day!";
1847** </pre></blockquote>
drha18c5682000-10-08 22:20:57 +00001848**
drh6ed48bf2007-06-14 20:57:18 +00001849** One can use this text in an SQL statement as follows:
drha18c5682000-10-08 22:20:57 +00001850**
drh6ed48bf2007-06-14 20:57:18 +00001851** <blockquote><pre>
1852** char *zSQL = sqlite3_mprintf("INSERT INTO table VALUES('%q')", zText);
1853** sqlite3_exec(db, zSQL, 0, 0, 0);
1854** sqlite3_free(zSQL);
1855** </pre></blockquote>
drha18c5682000-10-08 22:20:57 +00001856**
1857** Because the %q format string is used, the '\'' character in zText
1858** is escaped and the SQL generated is as follows:
1859**
drh6ed48bf2007-06-14 20:57:18 +00001860** <blockquote><pre>
1861** INSERT INTO table1 VALUES('It''s a happy day!')
1862** </pre></blockquote>
drha18c5682000-10-08 22:20:57 +00001863**
1864** This is correct. Had we used %s instead of %q, the generated SQL
1865** would have looked like this:
1866**
drh6ed48bf2007-06-14 20:57:18 +00001867** <blockquote><pre>
1868** INSERT INTO table1 VALUES('It's a happy day!');
1869** </pre></blockquote>
drha18c5682000-10-08 22:20:57 +00001870**
mihailimdb4f2ad2008-06-21 11:20:48 +00001871** This second example is an SQL syntax error. As a general rule you should
1872** always use %q instead of %s when inserting text into a string literal.
drh6ed48bf2007-06-14 20:57:18 +00001873**
drhd68eee02009-12-11 03:44:18 +00001874** ^(The %Q option works like %q except it also adds single quotes around
mihailimdb4f2ad2008-06-21 11:20:48 +00001875** the outside of the total string. Additionally, if the parameter in the
1876** argument list is a NULL pointer, %Q substitutes the text "NULL" (without
drhd68eee02009-12-11 03:44:18 +00001877** single quotes).)^ So, for example, one could say:
drh6ed48bf2007-06-14 20:57:18 +00001878**
1879** <blockquote><pre>
1880** char *zSQL = sqlite3_mprintf("INSERT INTO table VALUES(%Q)", zText);
1881** sqlite3_exec(db, zSQL, 0, 0, 0);
1882** sqlite3_free(zSQL);
1883** </pre></blockquote>
1884**
1885** The code above will render a correct SQL statement in the zSQL
1886** variable even if the zText variable is a NULL pointer.
drh153c62c2007-08-24 03:51:33 +00001887**
drhd68eee02009-12-11 03:44:18 +00001888** ^(The "%z" formatting option works like "%s" but with the
drh153c62c2007-08-24 03:51:33 +00001889** addition that after the string has been read and copied into
drhd68eee02009-12-11 03:44:18 +00001890** the result, [sqlite3_free()] is called on the input string.)^
drha18c5682000-10-08 22:20:57 +00001891*/
danielk19776f8a5032004-05-10 10:34:51 +00001892char *sqlite3_mprintf(const char*,...);
1893char *sqlite3_vmprintf(const char*, va_list);
drhfeac5f82004-08-01 00:10:45 +00001894char *sqlite3_snprintf(int,char*,const char*, ...);
drh5191b7e2002-03-08 02:12:00 +00001895
drh28dd4792006-06-26 21:35:44 +00001896/*
drhd68eee02009-12-11 03:44:18 +00001897** CAPI3REF: Memory Allocation Subsystem
drhd84f9462007-08-15 11:28:56 +00001898**
drhd68eee02009-12-11 03:44:18 +00001899** The SQLite core uses these three routines for all of its own
drh33c1be32008-01-30 16:16:14 +00001900** internal memory allocation needs. "Core" in the previous sentence
drhf5befa02007-12-06 02:42:07 +00001901** does not include operating-system specific VFS implementation. The
shane26b34032008-05-23 17:21:09 +00001902** Windows VFS uses native malloc() and free() for some operations.
drhd64621d2007-11-05 17:54:17 +00001903**
drhd68eee02009-12-11 03:44:18 +00001904** ^The sqlite3_malloc() routine returns a pointer to a block
drhfddfa2d2007-12-05 18:05:16 +00001905** of memory at least N bytes in length, where N is the parameter.
drhd68eee02009-12-11 03:44:18 +00001906** ^If sqlite3_malloc() is unable to obtain sufficient free
1907** memory, it returns a NULL pointer. ^If the parameter N to
drhfddfa2d2007-12-05 18:05:16 +00001908** sqlite3_malloc() is zero or negative then sqlite3_malloc() returns
1909** a NULL pointer.
1910**
drhd68eee02009-12-11 03:44:18 +00001911** ^Calling sqlite3_free() with a pointer previously returned
drhfddfa2d2007-12-05 18:05:16 +00001912** by sqlite3_malloc() or sqlite3_realloc() releases that memory so
drhd68eee02009-12-11 03:44:18 +00001913** that it might be reused. ^The sqlite3_free() routine is
drhfddfa2d2007-12-05 18:05:16 +00001914** a no-op if is called with a NULL pointer. Passing a NULL pointer
drh33c1be32008-01-30 16:16:14 +00001915** to sqlite3_free() is harmless. After being freed, memory
drhfddfa2d2007-12-05 18:05:16 +00001916** should neither be read nor written. Even reading previously freed
1917** memory might result in a segmentation fault or other severe error.
drh33c1be32008-01-30 16:16:14 +00001918** Memory corruption, a segmentation fault, or other severe error
drhfddfa2d2007-12-05 18:05:16 +00001919** might result if sqlite3_free() is called with a non-NULL pointer that
drh7b228b32008-10-17 15:10:37 +00001920** was not obtained from sqlite3_malloc() or sqlite3_realloc().
drhfddfa2d2007-12-05 18:05:16 +00001921**
drhd68eee02009-12-11 03:44:18 +00001922** ^(The sqlite3_realloc() interface attempts to resize a
drhfddfa2d2007-12-05 18:05:16 +00001923** prior memory allocation to be at least N bytes, where N is the
1924** second parameter. The memory allocation to be resized is the first
drhd68eee02009-12-11 03:44:18 +00001925** parameter.)^ ^ If the first parameter to sqlite3_realloc()
drhfddfa2d2007-12-05 18:05:16 +00001926** is a NULL pointer then its behavior is identical to calling
1927** sqlite3_malloc(N) where N is the second parameter to sqlite3_realloc().
drhd68eee02009-12-11 03:44:18 +00001928** ^If the second parameter to sqlite3_realloc() is zero or
drhfddfa2d2007-12-05 18:05:16 +00001929** negative then the behavior is exactly the same as calling
1930** sqlite3_free(P) where P is the first parameter to sqlite3_realloc().
drhd68eee02009-12-11 03:44:18 +00001931** ^sqlite3_realloc() returns a pointer to a memory allocation
drhfddfa2d2007-12-05 18:05:16 +00001932** of at least N bytes in size or NULL if sufficient memory is unavailable.
drhd68eee02009-12-11 03:44:18 +00001933** ^If M is the size of the prior allocation, then min(N,M) bytes
drhfddfa2d2007-12-05 18:05:16 +00001934** of the prior allocation are copied into the beginning of buffer returned
1935** by sqlite3_realloc() and the prior allocation is freed.
drhd68eee02009-12-11 03:44:18 +00001936** ^If sqlite3_realloc() returns NULL, then the prior allocation
drhfddfa2d2007-12-05 18:05:16 +00001937** is not freed.
1938**
drhd68eee02009-12-11 03:44:18 +00001939** ^The memory returned by sqlite3_malloc() and sqlite3_realloc()
1940** is always aligned to at least an 8 byte boundary.
drhd64621d2007-11-05 17:54:17 +00001941**
1942** In SQLite version 3.5.0 and 3.5.1, it was possible to define
1943** the SQLITE_OMIT_MEMORY_ALLOCATION which would cause the built-in
1944** implementation of these routines to be omitted. That capability
mihailimdb4f2ad2008-06-21 11:20:48 +00001945** is no longer provided. Only built-in memory allocators can be used.
drh8bacf972007-08-25 16:21:29 +00001946**
shane26b34032008-05-23 17:21:09 +00001947** The Windows OS interface layer calls
drh8bacf972007-08-25 16:21:29 +00001948** the system malloc() and free() directly when converting
1949** filenames between the UTF-8 encoding used by SQLite
shane26b34032008-05-23 17:21:09 +00001950** and whatever filename encoding is used by the particular Windows
drh8bacf972007-08-25 16:21:29 +00001951** installation. Memory allocation errors are detected, but
1952** they are reported back as [SQLITE_CANTOPEN] or
1953** [SQLITE_IOERR] rather than [SQLITE_NOMEM].
drh33c1be32008-01-30 16:16:14 +00001954**
drh8b39db12009-02-18 18:37:58 +00001955** The pointer arguments to [sqlite3_free()] and [sqlite3_realloc()]
1956** must be either NULL or else pointers obtained from a prior
1957** invocation of [sqlite3_malloc()] or [sqlite3_realloc()] that have
1958** not yet been released.
drh33c1be32008-01-30 16:16:14 +00001959**
drh8b39db12009-02-18 18:37:58 +00001960** The application must not read or write any part of
1961** a block of memory after it has been released using
1962** [sqlite3_free()] or [sqlite3_realloc()].
drh28dd4792006-06-26 21:35:44 +00001963*/
drhf3a65f72007-08-22 20:18:21 +00001964void *sqlite3_malloc(int);
1965void *sqlite3_realloc(void*, int);
drh28dd4792006-06-26 21:35:44 +00001966void sqlite3_free(void*);
1967
drh5191b7e2002-03-08 02:12:00 +00001968/*
drhd68eee02009-12-11 03:44:18 +00001969** CAPI3REF: Memory Allocator Statistics
drhd84f9462007-08-15 11:28:56 +00001970**
drh33c1be32008-01-30 16:16:14 +00001971** SQLite provides these two interfaces for reporting on the status
1972** of the [sqlite3_malloc()], [sqlite3_free()], and [sqlite3_realloc()]
mihailimdb4f2ad2008-06-21 11:20:48 +00001973** routines, which form the built-in memory allocation subsystem.
drhd84f9462007-08-15 11:28:56 +00001974**
drhd68eee02009-12-11 03:44:18 +00001975** ^The [sqlite3_memory_used()] routine returns the number of bytes
1976** of memory currently outstanding (malloced but not freed).
1977** ^The [sqlite3_memory_highwater()] routine returns the maximum
1978** value of [sqlite3_memory_used()] since the high-water mark
1979** was last reset. ^The values returned by [sqlite3_memory_used()] and
1980** [sqlite3_memory_highwater()] include any overhead
1981** added by SQLite in its implementation of [sqlite3_malloc()],
1982** but not overhead added by the any underlying system library
1983** routines that [sqlite3_malloc()] may call.
1984**
1985** ^The memory high-water mark is reset to the current value of
1986** [sqlite3_memory_used()] if and only if the parameter to
1987** [sqlite3_memory_highwater()] is true. ^The value returned
1988** by [sqlite3_memory_highwater(1)] is the high-water mark
1989** prior to the reset.
drhd84f9462007-08-15 11:28:56 +00001990*/
drh153c62c2007-08-24 03:51:33 +00001991sqlite3_int64 sqlite3_memory_used(void);
1992sqlite3_int64 sqlite3_memory_highwater(int resetFlag);
drhd84f9462007-08-15 11:28:56 +00001993
1994/*
drhd68eee02009-12-11 03:44:18 +00001995** CAPI3REF: Pseudo-Random Number Generator
drh2fa18682008-03-19 14:15:34 +00001996**
1997** SQLite contains a high-quality pseudo-random number generator (PRNG) used to
drh49c3d572008-12-15 22:51:38 +00001998** select random [ROWID | ROWIDs] when inserting new records into a table that
1999** already uses the largest possible [ROWID]. The PRNG is also used for
drh2fa18682008-03-19 14:15:34 +00002000** the build-in random() and randomblob() SQL functions. This interface allows
shane26b34032008-05-23 17:21:09 +00002001** applications to access the same PRNG for other purposes.
drh2fa18682008-03-19 14:15:34 +00002002**
drhd68eee02009-12-11 03:44:18 +00002003** ^A call to this routine stores N bytes of randomness into buffer P.
drh2fa18682008-03-19 14:15:34 +00002004**
drhd68eee02009-12-11 03:44:18 +00002005** ^The first time this routine is invoked (either internally or by
drh2fa18682008-03-19 14:15:34 +00002006** the application) the PRNG is seeded using randomness obtained
2007** from the xRandomness method of the default [sqlite3_vfs] object.
drhd68eee02009-12-11 03:44:18 +00002008** ^On all subsequent invocations, the pseudo-randomness is generated
drh2fa18682008-03-19 14:15:34 +00002009** internally and without recourse to the [sqlite3_vfs] xRandomness
2010** method.
drh2fa18682008-03-19 14:15:34 +00002011*/
2012void sqlite3_randomness(int N, void *P);
2013
2014/*
drhd68eee02009-12-11 03:44:18 +00002015** CAPI3REF: Compile-Time Authorization Callbacks
drhfddfa2d2007-12-05 18:05:16 +00002016**
drhd68eee02009-12-11 03:44:18 +00002017** ^This routine registers a authorizer callback with a particular
drhf47ce562008-03-20 18:00:49 +00002018** [database connection], supplied in the first argument.
drhd68eee02009-12-11 03:44:18 +00002019** ^The authorizer callback is invoked as SQL statements are being compiled
drh6ed48bf2007-06-14 20:57:18 +00002020** by [sqlite3_prepare()] or its variants [sqlite3_prepare_v2()],
drhd68eee02009-12-11 03:44:18 +00002021** [sqlite3_prepare16()] and [sqlite3_prepare16_v2()]. ^At various
drh6ed48bf2007-06-14 20:57:18 +00002022** points during the compilation process, as logic is being created
2023** to perform various actions, the authorizer callback is invoked to
drhd68eee02009-12-11 03:44:18 +00002024** see if those actions are allowed. ^The authorizer callback should
drhf47ce562008-03-20 18:00:49 +00002025** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the
drh6ed48bf2007-06-14 20:57:18 +00002026** specific action but allow the SQL statement to continue to be
2027** compiled, or [SQLITE_DENY] to cause the entire SQL statement to be
drhd68eee02009-12-11 03:44:18 +00002028** rejected with an error. ^If the authorizer callback returns
drhf5befa02007-12-06 02:42:07 +00002029** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY]
mihailima3f64902008-06-21 13:35:56 +00002030** then the [sqlite3_prepare_v2()] or equivalent call that triggered
drh33c1be32008-01-30 16:16:14 +00002031** the authorizer will fail with an error message.
drh6ed48bf2007-06-14 20:57:18 +00002032**
drhf5befa02007-12-06 02:42:07 +00002033** When the callback returns [SQLITE_OK], that means the operation
drhd68eee02009-12-11 03:44:18 +00002034** requested is ok. ^When the callback returns [SQLITE_DENY], the
drhf5befa02007-12-06 02:42:07 +00002035** [sqlite3_prepare_v2()] or equivalent call that triggered the
drh33c1be32008-01-30 16:16:14 +00002036** authorizer will fail with an error message explaining that
drh959b5302009-04-30 15:59:56 +00002037** access is denied.
drh6ed48bf2007-06-14 20:57:18 +00002038**
drhd68eee02009-12-11 03:44:18 +00002039** ^The first parameter to the authorizer callback is a copy of the third
2040** parameter to the sqlite3_set_authorizer() interface. ^The second parameter
mihailima3f64902008-06-21 13:35:56 +00002041** to the callback is an integer [SQLITE_COPY | action code] that specifies
drhd68eee02009-12-11 03:44:18 +00002042** the particular action to be authorized. ^The third through sixth parameters
mihailima3f64902008-06-21 13:35:56 +00002043** to the callback are zero-terminated strings that contain additional
2044** details about the action to be authorized.
drh6ed48bf2007-06-14 20:57:18 +00002045**
drhd68eee02009-12-11 03:44:18 +00002046** ^If the action code is [SQLITE_READ]
drh959b5302009-04-30 15:59:56 +00002047** and the callback returns [SQLITE_IGNORE] then the
2048** [prepared statement] statement is constructed to substitute
2049** a NULL value in place of the table column that would have
2050** been read if [SQLITE_OK] had been returned. The [SQLITE_IGNORE]
2051** return can be used to deny an untrusted user access to individual
2052** columns of a table.
drhd68eee02009-12-11 03:44:18 +00002053** ^If the action code is [SQLITE_DELETE] and the callback returns
drh959b5302009-04-30 15:59:56 +00002054** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the
2055** [truncate optimization] is disabled and all rows are deleted individually.
2056**
drhf47ce562008-03-20 18:00:49 +00002057** An authorizer is used when [sqlite3_prepare | preparing]
mihailimebe796c2008-06-21 20:11:17 +00002058** SQL statements from an untrusted source, to ensure that the SQL statements
2059** do not try to access data they are not allowed to see, or that they do not
2060** try to execute malicious statements that damage the database. For
drh6ed48bf2007-06-14 20:57:18 +00002061** example, an application may allow a user to enter arbitrary
2062** SQL queries for evaluation by a database. But the application does
2063** not want the user to be able to make arbitrary changes to the
2064** database. An authorizer could then be put in place while the
drhf47ce562008-03-20 18:00:49 +00002065** user-entered SQL is being [sqlite3_prepare | prepared] that
2066** disallows everything except [SELECT] statements.
2067**
2068** Applications that need to process SQL from untrusted sources
2069** might also consider lowering resource limits using [sqlite3_limit()]
2070** and limiting database size using the [max_page_count] [PRAGMA]
2071** in addition to using an authorizer.
drh6ed48bf2007-06-14 20:57:18 +00002072**
drhd68eee02009-12-11 03:44:18 +00002073** ^(Only a single authorizer can be in place on a database connection
drh6ed48bf2007-06-14 20:57:18 +00002074** at a time. Each call to sqlite3_set_authorizer overrides the
drhd68eee02009-12-11 03:44:18 +00002075** previous call.)^ ^Disable the authorizer by installing a NULL callback.
drh33c1be32008-01-30 16:16:14 +00002076** The authorizer is disabled by default.
drh6ed48bf2007-06-14 20:57:18 +00002077**
drhc8075422008-09-10 13:09:23 +00002078** The authorizer callback must not do anything that will modify
2079** the database connection that invoked the authorizer callback.
2080** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
2081** database connections for the meaning of "modify" in this paragraph.
2082**
drhd68eee02009-12-11 03:44:18 +00002083** ^When [sqlite3_prepare_v2()] is used to prepare a statement, the
shane7c7c3112009-08-17 15:31:23 +00002084** statement might be re-prepared during [sqlite3_step()] due to a
drh7b37c5d2008-08-12 14:51:29 +00002085** schema change. Hence, the application should ensure that the
2086** correct authorizer callback remains in place during the [sqlite3_step()].
2087**
drhd68eee02009-12-11 03:44:18 +00002088** ^Note that the authorizer callback is invoked only during
drh33c1be32008-01-30 16:16:14 +00002089** [sqlite3_prepare()] or its variants. Authorization is not
drh959b5302009-04-30 15:59:56 +00002090** performed during statement evaluation in [sqlite3_step()], unless
2091** as stated in the previous paragraph, sqlite3_step() invokes
2092** sqlite3_prepare_v2() to reprepare a statement after a schema change.
drhed6c8672003-01-12 18:02:16 +00002093*/
danielk19776f8a5032004-05-10 10:34:51 +00002094int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +00002095 sqlite3*,
drhe22a3342003-04-22 20:30:37 +00002096 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +00002097 void *pUserData
drhed6c8672003-01-12 18:02:16 +00002098);
2099
2100/*
drhd68eee02009-12-11 03:44:18 +00002101** CAPI3REF: Authorizer Return Codes
drh6ed48bf2007-06-14 20:57:18 +00002102**
2103** The [sqlite3_set_authorizer | authorizer callback function] must
2104** return either [SQLITE_OK] or one of these two constants in order
2105** to signal SQLite whether or not the action is permitted. See the
2106** [sqlite3_set_authorizer | authorizer documentation] for additional
2107** information.
2108*/
2109#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
2110#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
2111
2112/*
drhd68eee02009-12-11 03:44:18 +00002113** CAPI3REF: Authorizer Action Codes
drh6ed48bf2007-06-14 20:57:18 +00002114**
2115** The [sqlite3_set_authorizer()] interface registers a callback function
mihailima3f64902008-06-21 13:35:56 +00002116** that is invoked to authorize certain SQL statement actions. The
drh6ed48bf2007-06-14 20:57:18 +00002117** second parameter to the callback is an integer code that specifies
2118** what action is being authorized. These are the integer action codes that
drh33c1be32008-01-30 16:16:14 +00002119** the authorizer callback may be passed.
drh6ed48bf2007-06-14 20:57:18 +00002120**
mihailima3f64902008-06-21 13:35:56 +00002121** These action code values signify what kind of operation is to be
drh33c1be32008-01-30 16:16:14 +00002122** authorized. The 3rd and 4th parameters to the authorization
drhf5befa02007-12-06 02:42:07 +00002123** callback function will be parameters or NULL depending on which of these
drh7a98b852009-12-13 23:03:01 +00002124** codes is used as the second parameter. ^(The 5th parameter to the
mihailima3f64902008-06-21 13:35:56 +00002125** authorizer callback is the name of the database ("main", "temp",
drh7a98b852009-12-13 23:03:01 +00002126** etc.) if applicable.)^ ^The 6th parameter to the authorizer callback
drh5cf590c2003-04-24 01:45:04 +00002127** is the name of the inner-most trigger or view that is responsible for
mihailima3f64902008-06-21 13:35:56 +00002128** the access attempt or NULL if this access attempt is directly from
drh6ed48bf2007-06-14 20:57:18 +00002129** top-level SQL code.
drhed6c8672003-01-12 18:02:16 +00002130*/
drh6ed48bf2007-06-14 20:57:18 +00002131/******************************************* 3rd ************ 4th ***********/
drhe5f9c642003-01-13 23:27:31 +00002132#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
2133#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
2134#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
2135#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +00002136#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +00002137#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +00002138#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +00002139#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
2140#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +00002141#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +00002142#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +00002143#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +00002144#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +00002145#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +00002146#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +00002147#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +00002148#define SQLITE_DROP_VIEW 17 /* View Name NULL */
2149#define SQLITE_INSERT 18 /* Table Name NULL */
2150#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
2151#define SQLITE_READ 20 /* Table Name Column Name */
2152#define SQLITE_SELECT 21 /* NULL NULL */
danielk1977ab9b7032008-12-30 06:24:58 +00002153#define SQLITE_TRANSACTION 22 /* Operation NULL */
drhe5f9c642003-01-13 23:27:31 +00002154#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +00002155#define SQLITE_ATTACH 24 /* Filename NULL */
2156#define SQLITE_DETACH 25 /* Database Name NULL */
danielk19771c8c23c2004-11-12 15:53:37 +00002157#define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */
danielk19771d54df82004-11-23 15:41:16 +00002158#define SQLITE_REINDEX 27 /* Index Name NULL */
drhe6e04962005-07-23 02:17:03 +00002159#define SQLITE_ANALYZE 28 /* Table Name NULL */
danielk1977f1a381e2006-06-16 08:01:02 +00002160#define SQLITE_CREATE_VTABLE 29 /* Table Name Module Name */
2161#define SQLITE_DROP_VTABLE 30 /* Table Name Module Name */
drh2e904c52008-11-10 23:54:05 +00002162#define SQLITE_FUNCTION 31 /* NULL Function Name */
danielk1977ab9b7032008-12-30 06:24:58 +00002163#define SQLITE_SAVEPOINT 32 /* Operation Savepoint Name */
drh6ed48bf2007-06-14 20:57:18 +00002164#define SQLITE_COPY 0 /* No longer used */
drhed6c8672003-01-12 18:02:16 +00002165
2166/*
drhd68eee02009-12-11 03:44:18 +00002167** CAPI3REF: Tracing And Profiling Functions
drh6ed48bf2007-06-14 20:57:18 +00002168**
2169** These routines register callback functions that can be used for
2170** tracing and profiling the execution of SQL statements.
drhfddfa2d2007-12-05 18:05:16 +00002171**
drhd68eee02009-12-11 03:44:18 +00002172** ^The callback function registered by sqlite3_trace() is invoked at
drh33c1be32008-01-30 16:16:14 +00002173** various times when an SQL statement is being run by [sqlite3_step()].
drhd68eee02009-12-11 03:44:18 +00002174** ^The sqlite3_trace() callback is invoked with a UTF-8 rendering of the
2175** SQL statement text as the statement first begins executing.
2176** ^(Additional sqlite3_trace() callbacks might occur
shane26b34032008-05-23 17:21:09 +00002177** as each triggered subprogram is entered. The callbacks for triggers
drhd68eee02009-12-11 03:44:18 +00002178** contain a UTF-8 SQL comment that identifies the trigger.)^
mihailima3f64902008-06-21 13:35:56 +00002179**
drhd68eee02009-12-11 03:44:18 +00002180** ^The callback function registered by sqlite3_profile() is invoked
2181** as each SQL statement finishes. ^The profile callback contains
drh33c1be32008-01-30 16:16:14 +00002182** the original statement text and an estimate of wall-clock time
drhdf0db0f2010-07-29 10:07:21 +00002183** of how long that statement took to run. ^The profile callback
2184** time is in units of nanoseconds, however the current implementation
2185** is only capable of millisecond resolution so the six least significant
2186** digits in the time are meaningless. Future versions of SQLite
2187** might provide greater resolution on the profiler callback. The
2188** sqlite3_profile() function is considered experimental and is
2189** subject to change in future versions of SQLite.
drh18de4822003-01-16 16:28:53 +00002190*/
drh9f8da322010-03-10 20:06:37 +00002191void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
shanea79c3cc2008-08-11 17:27:01 +00002192SQLITE_EXPERIMENTAL void *sqlite3_profile(sqlite3*,
drh6d2069d2007-08-14 01:58:53 +00002193 void(*xProfile)(void*,const char*,sqlite3_uint64), void*);
drh18de4822003-01-16 16:28:53 +00002194
danielk1977348bb5d2003-10-18 09:37:26 +00002195/*
drhd68eee02009-12-11 03:44:18 +00002196** CAPI3REF: Query Progress Callbacks
drh6ed48bf2007-06-14 20:57:18 +00002197**
drhd68eee02009-12-11 03:44:18 +00002198** ^This routine configures a callback function - the
drhfddfa2d2007-12-05 18:05:16 +00002199** progress callback - that is invoked periodically during long
2200** running calls to [sqlite3_exec()], [sqlite3_step()] and
mihailima3f64902008-06-21 13:35:56 +00002201** [sqlite3_get_table()]. An example use for this
drh6ed48bf2007-06-14 20:57:18 +00002202** interface is to keep a GUI updated during a large query.
danielk1977348bb5d2003-10-18 09:37:26 +00002203**
drhd68eee02009-12-11 03:44:18 +00002204** ^If the progress callback returns non-zero, the operation is
drh33c1be32008-01-30 16:16:14 +00002205** interrupted. This feature can be used to implement a
drhc8075422008-09-10 13:09:23 +00002206** "Cancel" button on a GUI progress dialog box.
2207**
2208** The progress handler must not do anything that will modify
2209** the database connection that invoked the progress handler.
2210** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
2211** database connections for the meaning of "modify" in this paragraph.
danielk1977348bb5d2003-10-18 09:37:26 +00002212**
danielk1977348bb5d2003-10-18 09:37:26 +00002213*/
danielk1977f9d64d22004-06-19 08:18:07 +00002214void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +00002215
drhaa940ea2004-01-15 02:44:03 +00002216/*
drhd68eee02009-12-11 03:44:18 +00002217** CAPI3REF: Opening A New Database Connection
drhaa940ea2004-01-15 02:44:03 +00002218**
drhd68eee02009-12-11 03:44:18 +00002219** ^These routines open an SQLite database file whose name is given by the
2220** filename argument. ^The filename argument is interpreted as UTF-8 for
mihailima3f64902008-06-21 13:35:56 +00002221** sqlite3_open() and sqlite3_open_v2() and as UTF-16 in the native byte
drhd68eee02009-12-11 03:44:18 +00002222** order for sqlite3_open16(). ^(A [database connection] handle is usually
mihailima3f64902008-06-21 13:35:56 +00002223** returned in *ppDb, even if an error occurs. The only exception is that
2224** if SQLite is unable to allocate memory to hold the [sqlite3] object,
2225** a NULL will be written into *ppDb instead of a pointer to the [sqlite3]
drhd68eee02009-12-11 03:44:18 +00002226** object.)^ ^(If the database is opened (and/or created) successfully, then
2227** [SQLITE_OK] is returned. Otherwise an [error code] is returned.)^ ^The
mihailima3f64902008-06-21 13:35:56 +00002228** [sqlite3_errmsg()] or [sqlite3_errmsg16()] routines can be used to obtain
drhd68eee02009-12-11 03:44:18 +00002229** an English language description of the error following a failure of any
2230** of the sqlite3_open() routines.
drh22fbcb82004-02-01 01:22:50 +00002231**
drhd68eee02009-12-11 03:44:18 +00002232** ^The default encoding for the database will be UTF-8 if
mihailima3f64902008-06-21 13:35:56 +00002233** sqlite3_open() or sqlite3_open_v2() is called and
2234** UTF-16 in the native byte order if sqlite3_open16() is used.
danielk197765904932004-05-26 06:18:37 +00002235**
drh33c1be32008-01-30 16:16:14 +00002236** Whether or not an error occurs when it is opened, resources
mihailima3f64902008-06-21 13:35:56 +00002237** associated with the [database connection] handle should be released by
2238** passing it to [sqlite3_close()] when it is no longer required.
drh6d2069d2007-08-14 01:58:53 +00002239**
mihailima3f64902008-06-21 13:35:56 +00002240** The sqlite3_open_v2() interface works like sqlite3_open()
shane26b34032008-05-23 17:21:09 +00002241** except that it accepts two additional parameters for additional control
drhd68eee02009-12-11 03:44:18 +00002242** over the new database connection. ^(The flags parameter to
2243** sqlite3_open_v2() can take one of
danielk19779a6284c2008-07-10 17:52:49 +00002244** the following three values, optionally combined with the
drhf1f12682009-09-09 14:17:52 +00002245** [SQLITE_OPEN_NOMUTEX], [SQLITE_OPEN_FULLMUTEX], [SQLITE_OPEN_SHAREDCACHE],
drhd68eee02009-12-11 03:44:18 +00002246** and/or [SQLITE_OPEN_PRIVATECACHE] flags:)^
drh6d2069d2007-08-14 01:58:53 +00002247**
mihailima3f64902008-06-21 13:35:56 +00002248** <dl>
drhd68eee02009-12-11 03:44:18 +00002249** ^(<dt>[SQLITE_OPEN_READONLY]</dt>
mihailima3f64902008-06-21 13:35:56 +00002250** <dd>The database is opened in read-only mode. If the database does not
drhd68eee02009-12-11 03:44:18 +00002251** already exist, an error is returned.</dd>)^
drh6d2069d2007-08-14 01:58:53 +00002252**
drhd68eee02009-12-11 03:44:18 +00002253** ^(<dt>[SQLITE_OPEN_READWRITE]</dt>
mihailima3f64902008-06-21 13:35:56 +00002254** <dd>The database is opened for reading and writing if possible, or reading
2255** only if the file is write protected by the operating system. In either
drhd68eee02009-12-11 03:44:18 +00002256** case the database must already exist, otherwise an error is returned.</dd>)^
drh9da9d962007-08-28 15:47:44 +00002257**
drhd68eee02009-12-11 03:44:18 +00002258** ^(<dt>[SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE]</dt>
mihailima3f64902008-06-21 13:35:56 +00002259** <dd>The database is opened for reading and writing, and is creates it if
2260** it does not already exist. This is the behavior that is always used for
drhd68eee02009-12-11 03:44:18 +00002261** sqlite3_open() and sqlite3_open16().</dd>)^
mihailima3f64902008-06-21 13:35:56 +00002262** </dl>
2263**
2264** If the 3rd parameter to sqlite3_open_v2() is not one of the
danielk19779a6284c2008-07-10 17:52:49 +00002265** combinations shown above or one of the combinations shown above combined
drhf1f12682009-09-09 14:17:52 +00002266** with the [SQLITE_OPEN_NOMUTEX], [SQLITE_OPEN_FULLMUTEX],
drh357b5f92010-08-24 18:07:57 +00002267** [SQLITE_OPEN_SHAREDCACHE] and/or [SQLITE_OPEN_PRIVATECACHE] flags,
drhafacce02008-09-02 21:35:03 +00002268** then the behavior is undefined.
danielk19779a6284c2008-07-10 17:52:49 +00002269**
drhd68eee02009-12-11 03:44:18 +00002270** ^If the [SQLITE_OPEN_NOMUTEX] flag is set, then the database connection
drhafacce02008-09-02 21:35:03 +00002271** opens in the multi-thread [threading mode] as long as the single-thread
drhd68eee02009-12-11 03:44:18 +00002272** mode has not been set at compile-time or start-time. ^If the
drhafacce02008-09-02 21:35:03 +00002273** [SQLITE_OPEN_FULLMUTEX] flag is set then the database connection opens
2274** in the serialized [threading mode] unless single-thread was
2275** previously selected at compile-time or start-time.
drhd68eee02009-12-11 03:44:18 +00002276** ^The [SQLITE_OPEN_SHAREDCACHE] flag causes the database connection to be
drhf1f12682009-09-09 14:17:52 +00002277** eligible to use [shared cache mode], regardless of whether or not shared
drhd68eee02009-12-11 03:44:18 +00002278** cache is enabled using [sqlite3_enable_shared_cache()]. ^The
drhf1f12682009-09-09 14:17:52 +00002279** [SQLITE_OPEN_PRIVATECACHE] flag causes the database connection to not
2280** participate in [shared cache mode] even if it is enabled.
drhd9b97cf2008-04-10 13:38:17 +00002281**
drhd68eee02009-12-11 03:44:18 +00002282** ^If the filename is ":memory:", then a private, temporary in-memory database
2283** is created for the connection. ^This in-memory database will vanish when
mihailima3f64902008-06-21 13:35:56 +00002284** the database connection is closed. Future versions of SQLite might
2285** make use of additional special filenames that begin with the ":" character.
2286** It is recommended that when a database filename actually does begin with
2287** a ":" character you should prefix the filename with a pathname such as
2288** "./" to avoid ambiguity.
drh6d2069d2007-08-14 01:58:53 +00002289**
drhd68eee02009-12-11 03:44:18 +00002290** ^If the filename is an empty string, then a private, temporary
2291** on-disk database will be created. ^This private database will be
drh3f3b6352007-09-03 20:32:45 +00002292** automatically deleted as soon as the database connection is closed.
2293**
drhd68eee02009-12-11 03:44:18 +00002294** ^The fourth parameter to sqlite3_open_v2() is the name of the
mihailima3f64902008-06-21 13:35:56 +00002295** [sqlite3_vfs] object that defines the operating system interface that
drhd68eee02009-12-11 03:44:18 +00002296** the new database connection should use. ^If the fourth parameter is
mihailima3f64902008-06-21 13:35:56 +00002297** a NULL pointer then the default [sqlite3_vfs] object is used.
drh6ed48bf2007-06-14 20:57:18 +00002298**
shane26b34032008-05-23 17:21:09 +00002299** <b>Note to Windows users:</b> The encoding used for the filename argument
mihailima3f64902008-06-21 13:35:56 +00002300** of sqlite3_open() and sqlite3_open_v2() must be UTF-8, not whatever
drh9da9d962007-08-28 15:47:44 +00002301** codepage is currently defined. Filenames containing international
2302** characters must be converted to UTF-8 prior to passing them into
mihailima3f64902008-06-21 13:35:56 +00002303** sqlite3_open() or sqlite3_open_v2().
danielk197765904932004-05-26 06:18:37 +00002304*/
2305int sqlite3_open(
2306 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +00002307 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +00002308);
danielk197765904932004-05-26 06:18:37 +00002309int sqlite3_open16(
2310 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +00002311 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +00002312);
drh6d2069d2007-08-14 01:58:53 +00002313int sqlite3_open_v2(
drh428e2822007-08-30 16:23:19 +00002314 const char *filename, /* Database filename (UTF-8) */
drh6d2069d2007-08-14 01:58:53 +00002315 sqlite3 **ppDb, /* OUT: SQLite db handle */
2316 int flags, /* Flags */
drhd84f9462007-08-15 11:28:56 +00002317 const char *zVfs /* Name of VFS module to use */
drh6d2069d2007-08-14 01:58:53 +00002318);
danielk1977295ba552004-05-19 10:34:51 +00002319
danielk197765904932004-05-26 06:18:37 +00002320/*
drhd68eee02009-12-11 03:44:18 +00002321** CAPI3REF: Error Codes And Messages
drh6ed48bf2007-06-14 20:57:18 +00002322**
drhd68eee02009-12-11 03:44:18 +00002323** ^The sqlite3_errcode() interface returns the numeric [result code] or
mihailimefc8e8a2008-06-21 16:47:09 +00002324** [extended result code] for the most recent failed sqlite3_* API call
2325** associated with a [database connection]. If a prior API call failed
2326** but the most recent API call succeeded, the return value from
drhd68eee02009-12-11 03:44:18 +00002327** sqlite3_errcode() is undefined. ^The sqlite3_extended_errcode()
drh99dfe5e2008-10-30 15:03:15 +00002328** interface is the same except that it always returns the
2329** [extended result code] even when extended result codes are
2330** disabled.
drh6ed48bf2007-06-14 20:57:18 +00002331**
drhd68eee02009-12-11 03:44:18 +00002332** ^The sqlite3_errmsg() and sqlite3_errmsg16() return English-language
mihailimebe796c2008-06-21 20:11:17 +00002333** text that describes the error, as either UTF-8 or UTF-16 respectively.
drhd68eee02009-12-11 03:44:18 +00002334** ^(Memory to hold the error message string is managed internally.
mihailimefc8e8a2008-06-21 16:47:09 +00002335** The application does not need to worry about freeing the result.
mlcreech27358862008-03-01 23:34:46 +00002336** However, the error string might be overwritten or deallocated by
drhd68eee02009-12-11 03:44:18 +00002337** subsequent calls to other SQLite interface functions.)^
danielk197765904932004-05-26 06:18:37 +00002338**
drh2838b472008-11-04 14:48:22 +00002339** When the serialized [threading mode] is in use, it might be the
2340** case that a second error occurs on a separate thread in between
2341** the time of the first error and the call to these interfaces.
2342** When that happens, the second error will be reported since these
2343** interfaces always report the most recent result. To avoid
2344** this, each thread can obtain exclusive use of the [database connection] D
2345** by invoking [sqlite3_mutex_enter]([sqlite3_db_mutex](D)) before beginning
2346** to use D and invoking [sqlite3_mutex_leave]([sqlite3_db_mutex](D)) after
2347** all calls to the interfaces listed here are completed.
2348**
drhd55d57e2008-07-07 17:53:07 +00002349** If an interface fails with SQLITE_MISUSE, that means the interface
2350** was invoked incorrectly by the application. In that case, the
2351** error code and message may or may not be set.
danielk197765904932004-05-26 06:18:37 +00002352*/
2353int sqlite3_errcode(sqlite3 *db);
drh99dfe5e2008-10-30 15:03:15 +00002354int sqlite3_extended_errcode(sqlite3 *db);
danielk197765904932004-05-26 06:18:37 +00002355const char *sqlite3_errmsg(sqlite3*);
danielk197765904932004-05-26 06:18:37 +00002356const void *sqlite3_errmsg16(sqlite3*);
2357
2358/*
drhd68eee02009-12-11 03:44:18 +00002359** CAPI3REF: SQL Statement Object
drh33c1be32008-01-30 16:16:14 +00002360** KEYWORDS: {prepared statement} {prepared statements}
drh6ed48bf2007-06-14 20:57:18 +00002361**
mihailimefc8e8a2008-06-21 16:47:09 +00002362** An instance of this object represents a single SQL statement.
2363** This object is variously known as a "prepared statement" or a
drh6ed48bf2007-06-14 20:57:18 +00002364** "compiled SQL statement" or simply as a "statement".
mihailimefc8e8a2008-06-21 16:47:09 +00002365**
drh6ed48bf2007-06-14 20:57:18 +00002366** The life of a statement object goes something like this:
2367**
2368** <ol>
2369** <li> Create the object using [sqlite3_prepare_v2()] or a related
2370** function.
mihailimefc8e8a2008-06-21 16:47:09 +00002371** <li> Bind values to [host parameters] using the sqlite3_bind_*()
2372** interfaces.
drh6ed48bf2007-06-14 20:57:18 +00002373** <li> Run the SQL by calling [sqlite3_step()] one or more times.
2374** <li> Reset the statement using [sqlite3_reset()] then go back
2375** to step 2. Do this zero or more times.
2376** <li> Destroy the object using [sqlite3_finalize()].
2377** </ol>
2378**
2379** Refer to documentation on individual methods above for additional
2380** information.
danielk197765904932004-05-26 06:18:37 +00002381*/
danielk1977fc57d7b2004-05-26 02:04:57 +00002382typedef struct sqlite3_stmt sqlite3_stmt;
2383
danielk1977e3209e42004-05-20 01:40:18 +00002384/*
drhd68eee02009-12-11 03:44:18 +00002385** CAPI3REF: Run-time Limits
drhcaa639f2008-03-20 00:32:20 +00002386**
drhd68eee02009-12-11 03:44:18 +00002387** ^(This interface allows the size of various constructs to be limited
drhcaa639f2008-03-20 00:32:20 +00002388** on a connection by connection basis. The first parameter is the
2389** [database connection] whose limit is to be set or queried. The
2390** second parameter is one of the [limit categories] that define a
2391** class of constructs to be size limited. The third parameter is the
drhd68eee02009-12-11 03:44:18 +00002392** new limit for that construct. The function returns the old limit.)^
drhcaa639f2008-03-20 00:32:20 +00002393**
drhd68eee02009-12-11 03:44:18 +00002394** ^If the new limit is a negative number, the limit is unchanged.
2395** ^(For the limit category of SQLITE_LIMIT_XYZ there is a
drhae1a8802009-02-11 15:04:40 +00002396** [limits | hard upper bound]
2397** set by a compile-time C preprocessor macro named
2398** [limits | SQLITE_MAX_XYZ].
drhd68eee02009-12-11 03:44:18 +00002399** (The "_LIMIT_" in the name is changed to "_MAX_".))^
2400** ^Attempts to increase a limit above its hard upper bound are
drh7a98b852009-12-13 23:03:01 +00002401** silently truncated to the hard upper bound.
drhcaa639f2008-03-20 00:32:20 +00002402**
drhd68eee02009-12-11 03:44:18 +00002403** Run-time limits are intended for use in applications that manage
drhbb4957f2008-03-20 14:03:29 +00002404** both their own internal database and also databases that are controlled
2405** by untrusted external sources. An example application might be a
drh46f33ef2009-02-11 15:23:35 +00002406** web browser that has its own databases for storing history and
shane26b34032008-05-23 17:21:09 +00002407** separate databases controlled by JavaScript applications downloaded
shane236ce972008-05-30 15:35:30 +00002408** off the Internet. The internal databases can be given the
drhbb4957f2008-03-20 14:03:29 +00002409** large, default limits. Databases managed by external sources can
2410** be given much smaller limits designed to prevent a denial of service
mihailimefc8e8a2008-06-21 16:47:09 +00002411** attack. Developers might also want to use the [sqlite3_set_authorizer()]
drhf47ce562008-03-20 18:00:49 +00002412** interface to further control untrusted SQL. The size of the database
2413** created by an untrusted script can be contained using the
2414** [max_page_count] [PRAGMA].
drhbb4957f2008-03-20 14:03:29 +00002415**
drha911abe2008-07-16 13:29:51 +00002416** New run-time limit categories may be added in future releases.
drhcaa639f2008-03-20 00:32:20 +00002417*/
2418int sqlite3_limit(sqlite3*, int id, int newVal);
2419
2420/*
drhd68eee02009-12-11 03:44:18 +00002421** CAPI3REF: Run-Time Limit Categories
drhe7ae4e22009-11-02 15:51:52 +00002422** KEYWORDS: {limit category} {*limit categories}
mihailimefc8e8a2008-06-21 16:47:09 +00002423**
drh46f33ef2009-02-11 15:23:35 +00002424** These constants define various performance limits
2425** that can be lowered at run-time using [sqlite3_limit()].
2426** The synopsis of the meanings of the various limits is shown below.
2427** Additional information is available at [limits | Limits in SQLite].
drhbb4957f2008-03-20 14:03:29 +00002428**
2429** <dl>
drhd68eee02009-12-11 03:44:18 +00002430** ^(<dt>SQLITE_LIMIT_LENGTH</dt>
2431** <dd>The maximum size of any string or BLOB or table row.<dd>)^
drhbb4957f2008-03-20 14:03:29 +00002432**
drhd68eee02009-12-11 03:44:18 +00002433** ^(<dt>SQLITE_LIMIT_SQL_LENGTH</dt>
drhdf6473a2009-12-13 22:20:08 +00002434** <dd>The maximum length of an SQL statement, in bytes.</dd>)^
drhbb4957f2008-03-20 14:03:29 +00002435**
drhd68eee02009-12-11 03:44:18 +00002436** ^(<dt>SQLITE_LIMIT_COLUMN</dt>
drhbb4957f2008-03-20 14:03:29 +00002437** <dd>The maximum number of columns in a table definition or in the
drh46f33ef2009-02-11 15:23:35 +00002438** result set of a [SELECT] or the maximum number of columns in an index
drhd68eee02009-12-11 03:44:18 +00002439** or in an ORDER BY or GROUP BY clause.</dd>)^
drhbb4957f2008-03-20 14:03:29 +00002440**
drhd68eee02009-12-11 03:44:18 +00002441** ^(<dt>SQLITE_LIMIT_EXPR_DEPTH</dt>
2442** <dd>The maximum depth of the parse tree on any expression.</dd>)^
drhbb4957f2008-03-20 14:03:29 +00002443**
drhd68eee02009-12-11 03:44:18 +00002444** ^(<dt>SQLITE_LIMIT_COMPOUND_SELECT</dt>
2445** <dd>The maximum number of terms in a compound SELECT statement.</dd>)^
drhbb4957f2008-03-20 14:03:29 +00002446**
drhd68eee02009-12-11 03:44:18 +00002447** ^(<dt>SQLITE_LIMIT_VDBE_OP</dt>
drhbb4957f2008-03-20 14:03:29 +00002448** <dd>The maximum number of instructions in a virtual machine program
drhd68eee02009-12-11 03:44:18 +00002449** used to implement an SQL statement.</dd>)^
drhbb4957f2008-03-20 14:03:29 +00002450**
drhd68eee02009-12-11 03:44:18 +00002451** ^(<dt>SQLITE_LIMIT_FUNCTION_ARG</dt>
2452** <dd>The maximum number of arguments on a function.</dd>)^
drhbb4957f2008-03-20 14:03:29 +00002453**
drhd68eee02009-12-11 03:44:18 +00002454** ^(<dt>SQLITE_LIMIT_ATTACHED</dt>
drh7a98b852009-12-13 23:03:01 +00002455** <dd>The maximum number of [ATTACH | attached databases].)^</dd>
drhbb4957f2008-03-20 14:03:29 +00002456**
drh7a98b852009-12-13 23:03:01 +00002457** ^(<dt>SQLITE_LIMIT_LIKE_PATTERN_LENGTH</dt>
drh46f33ef2009-02-11 15:23:35 +00002458** <dd>The maximum length of the pattern argument to the [LIKE] or
drhd68eee02009-12-11 03:44:18 +00002459** [GLOB] operators.</dd>)^
drhbb4957f2008-03-20 14:03:29 +00002460**
drhd68eee02009-12-11 03:44:18 +00002461** ^(<dt>SQLITE_LIMIT_VARIABLE_NUMBER</dt>
drhbb4957f2008-03-20 14:03:29 +00002462** <dd>The maximum number of variables in an SQL statement that can
drhd68eee02009-12-11 03:44:18 +00002463** be bound.</dd>)^
drh417168a2009-09-07 18:14:02 +00002464**
drhd68eee02009-12-11 03:44:18 +00002465** ^(<dt>SQLITE_LIMIT_TRIGGER_DEPTH</dt>
2466** <dd>The maximum depth of recursion for triggers.</dd>)^
drhbb4957f2008-03-20 14:03:29 +00002467** </dl>
drhcaa639f2008-03-20 00:32:20 +00002468*/
2469#define SQLITE_LIMIT_LENGTH 0
2470#define SQLITE_LIMIT_SQL_LENGTH 1
2471#define SQLITE_LIMIT_COLUMN 2
2472#define SQLITE_LIMIT_EXPR_DEPTH 3
2473#define SQLITE_LIMIT_COMPOUND_SELECT 4
2474#define SQLITE_LIMIT_VDBE_OP 5
2475#define SQLITE_LIMIT_FUNCTION_ARG 6
2476#define SQLITE_LIMIT_ATTACHED 7
drhb1a6c3c2008-03-20 16:30:17 +00002477#define SQLITE_LIMIT_LIKE_PATTERN_LENGTH 8
2478#define SQLITE_LIMIT_VARIABLE_NUMBER 9
drh417168a2009-09-07 18:14:02 +00002479#define SQLITE_LIMIT_TRIGGER_DEPTH 10
drhcaa639f2008-03-20 00:32:20 +00002480
2481/*
drhd68eee02009-12-11 03:44:18 +00002482** CAPI3REF: Compiling An SQL Statement
mihailimefc8e8a2008-06-21 16:47:09 +00002483** KEYWORDS: {SQL statement compiler}
danielk197765904932004-05-26 06:18:37 +00002484**
drh6ed48bf2007-06-14 20:57:18 +00002485** To execute an SQL query, it must first be compiled into a byte-code
mihailimefc8e8a2008-06-21 16:47:09 +00002486** program using one of these routines.
drh6ed48bf2007-06-14 20:57:18 +00002487**
mihailimefc8e8a2008-06-21 16:47:09 +00002488** The first argument, "db", is a [database connection] obtained from a
drh860e0772009-04-02 18:32:26 +00002489** prior successful call to [sqlite3_open()], [sqlite3_open_v2()] or
2490** [sqlite3_open16()]. The database connection must not have been closed.
mihailimefc8e8a2008-06-21 16:47:09 +00002491**
2492** The second argument, "zSql", is the statement to be compiled, encoded
drh6ed48bf2007-06-14 20:57:18 +00002493** as either UTF-8 or UTF-16. The sqlite3_prepare() and sqlite3_prepare_v2()
mihailimefc8e8a2008-06-21 16:47:09 +00002494** interfaces use UTF-8, and sqlite3_prepare16() and sqlite3_prepare16_v2()
mihailim04bcc002008-06-22 10:21:27 +00002495** use UTF-16.
drh21f06722007-07-19 12:41:39 +00002496**
drhd68eee02009-12-11 03:44:18 +00002497** ^If the nByte argument is less than zero, then zSql is read up to the
2498** first zero terminator. ^If nByte is non-negative, then it is the maximum
2499** number of bytes read from zSql. ^When nByte is non-negative, the
mihailimefc8e8a2008-06-21 16:47:09 +00002500** zSql string ends at either the first '\000' or '\u0000' character or
drhb08c2a72008-04-16 00:28:13 +00002501** the nByte-th byte, whichever comes first. If the caller knows
danielk19773a2c8c82008-04-03 14:36:25 +00002502** that the supplied string is nul-terminated, then there is a small
mihailimefc8e8a2008-06-21 16:47:09 +00002503** performance advantage to be gained by passing an nByte parameter that
2504** is equal to the number of bytes in the input string <i>including</i>
mihailim04bcc002008-06-22 10:21:27 +00002505** the nul-terminator bytes.
danielk197765904932004-05-26 06:18:37 +00002506**
drhd68eee02009-12-11 03:44:18 +00002507** ^If pzTail is not NULL then *pzTail is made to point to the first byte
drh860e0772009-04-02 18:32:26 +00002508** past the end of the first SQL statement in zSql. These routines only
2509** compile the first statement in zSql, so *pzTail is left pointing to
2510** what remains uncompiled.
danielk197765904932004-05-26 06:18:37 +00002511**
drhd68eee02009-12-11 03:44:18 +00002512** ^*ppStmt is left pointing to a compiled [prepared statement] that can be
2513** executed using [sqlite3_step()]. ^If there is an error, *ppStmt is set
2514** to NULL. ^If the input text contains no SQL (if the input is an empty
mihailimefc8e8a2008-06-21 16:47:09 +00002515** string or a comment) then *ppStmt is set to NULL.
drh860e0772009-04-02 18:32:26 +00002516** The calling procedure is responsible for deleting the compiled
mihailimefc8e8a2008-06-21 16:47:09 +00002517** SQL statement using [sqlite3_finalize()] after it has finished with it.
drh860e0772009-04-02 18:32:26 +00002518** ppStmt may not be NULL.
danielk197765904932004-05-26 06:18:37 +00002519**
drhd68eee02009-12-11 03:44:18 +00002520** ^On success, the sqlite3_prepare() family of routines return [SQLITE_OK];
2521** otherwise an [error code] is returned.
drh6ed48bf2007-06-14 20:57:18 +00002522**
2523** The sqlite3_prepare_v2() and sqlite3_prepare16_v2() interfaces are
2524** recommended for all new programs. The two older interfaces are retained
2525** for backwards compatibility, but their use is discouraged.
drhd68eee02009-12-11 03:44:18 +00002526** ^In the "v2" interfaces, the prepared statement
mihailimefc8e8a2008-06-21 16:47:09 +00002527** that is returned (the [sqlite3_stmt] object) contains a copy of the
mihailim04bcc002008-06-22 10:21:27 +00002528** original SQL text. This causes the [sqlite3_step()] interface to
drh481aa742009-11-05 18:46:02 +00002529** behave differently in three ways:
drh6ed48bf2007-06-14 20:57:18 +00002530**
2531** <ol>
drh33c1be32008-01-30 16:16:14 +00002532** <li>
drhd68eee02009-12-11 03:44:18 +00002533** ^If the database schema changes, instead of returning [SQLITE_SCHEMA] as it
drh6ed48bf2007-06-14 20:57:18 +00002534** always used to do, [sqlite3_step()] will automatically recompile the SQL
drhd68eee02009-12-11 03:44:18 +00002535** statement and try to run it again. ^If the schema has changed in
drhfddfa2d2007-12-05 18:05:16 +00002536** a way that makes the statement no longer valid, [sqlite3_step()] will still
mihailimefc8e8a2008-06-21 16:47:09 +00002537** return [SQLITE_SCHEMA]. But unlike the legacy behavior, [SQLITE_SCHEMA] is
2538** now a fatal error. Calling [sqlite3_prepare_v2()] again will not make the
drh33c1be32008-01-30 16:16:14 +00002539** error go away. Note: use [sqlite3_errmsg()] to find the text
mihailim04bcc002008-06-22 10:21:27 +00002540** of the parsing error that results in an [SQLITE_SCHEMA] return.
drh6ed48bf2007-06-14 20:57:18 +00002541** </li>
2542**
2543** <li>
drhd68eee02009-12-11 03:44:18 +00002544** ^When an error occurs, [sqlite3_step()] will return one of the detailed
2545** [error codes] or [extended error codes]. ^The legacy behavior was that
mihailimefc8e8a2008-06-21 16:47:09 +00002546** [sqlite3_step()] would only return a generic [SQLITE_ERROR] result code
drhdf6473a2009-12-13 22:20:08 +00002547** and the application would have to make a second call to [sqlite3_reset()]
2548** in order to find the underlying cause of the problem. With the "v2" prepare
mihailimefc8e8a2008-06-21 16:47:09 +00002549** interfaces, the underlying reason for the error is returned immediately.
drh6ed48bf2007-06-14 20:57:18 +00002550** </li>
drh4b5af772009-10-20 14:08:41 +00002551**
2552** <li>
2553** ^If the value of a [parameter | host parameter] in the WHERE clause might
2554** change the query plan for a statement, then the statement may be
2555** automatically recompiled (as if there had been a schema change) on the first
2556** [sqlite3_step()] call following any change to the
2557** [sqlite3_bind_text | bindings] of the [parameter].
2558** </li>
drh6ed48bf2007-06-14 20:57:18 +00002559** </ol>
danielk197765904932004-05-26 06:18:37 +00002560*/
2561int sqlite3_prepare(
2562 sqlite3 *db, /* Database handle */
2563 const char *zSql, /* SQL statement, UTF-8 encoded */
drh21f06722007-07-19 12:41:39 +00002564 int nByte, /* Maximum length of zSql in bytes. */
danielk197765904932004-05-26 06:18:37 +00002565 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
2566 const char **pzTail /* OUT: Pointer to unused portion of zSql */
2567);
drh6ed48bf2007-06-14 20:57:18 +00002568int sqlite3_prepare_v2(
2569 sqlite3 *db, /* Database handle */
2570 const char *zSql, /* SQL statement, UTF-8 encoded */
drh21f06722007-07-19 12:41:39 +00002571 int nByte, /* Maximum length of zSql in bytes. */
drh6ed48bf2007-06-14 20:57:18 +00002572 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
2573 const char **pzTail /* OUT: Pointer to unused portion of zSql */
2574);
danielk197765904932004-05-26 06:18:37 +00002575int sqlite3_prepare16(
2576 sqlite3 *db, /* Database handle */
2577 const void *zSql, /* SQL statement, UTF-16 encoded */
drh21f06722007-07-19 12:41:39 +00002578 int nByte, /* Maximum length of zSql in bytes. */
danielk197765904932004-05-26 06:18:37 +00002579 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
2580 const void **pzTail /* OUT: Pointer to unused portion of zSql */
2581);
drhb900aaf2006-11-09 00:24:53 +00002582int sqlite3_prepare16_v2(
2583 sqlite3 *db, /* Database handle */
2584 const void *zSql, /* SQL statement, UTF-16 encoded */
drh21f06722007-07-19 12:41:39 +00002585 int nByte, /* Maximum length of zSql in bytes. */
drhb900aaf2006-11-09 00:24:53 +00002586 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
2587 const void **pzTail /* OUT: Pointer to unused portion of zSql */
2588);
2589
2590/*
drhd68eee02009-12-11 03:44:18 +00002591** CAPI3REF: Retrieving Statement SQL
danielk1977d0e2a852007-11-14 06:48:48 +00002592**
drhd68eee02009-12-11 03:44:18 +00002593** ^This interface can be used to retrieve a saved copy of the original
mihailimefc8e8a2008-06-21 16:47:09 +00002594** SQL text used to create a [prepared statement] if that statement was
2595** compiled using either [sqlite3_prepare_v2()] or [sqlite3_prepare16_v2()].
danielk1977d0e2a852007-11-14 06:48:48 +00002596*/
2597const char *sqlite3_sql(sqlite3_stmt *pStmt);
2598
2599/*
drhd68eee02009-12-11 03:44:18 +00002600** CAPI3REF: Dynamically Typed Value Object
drhaa28e142008-03-18 13:47:20 +00002601** KEYWORDS: {protected sqlite3_value} {unprotected sqlite3_value}
drh6ed48bf2007-06-14 20:57:18 +00002602**
drh33c1be32008-01-30 16:16:14 +00002603** SQLite uses the sqlite3_value object to represent all values
mihailimefc8e8a2008-06-21 16:47:09 +00002604** that can be stored in a database table. SQLite uses dynamic typing
drhd68eee02009-12-11 03:44:18 +00002605** for the values it stores. ^Values stored in sqlite3_value objects
mihailimefc8e8a2008-06-21 16:47:09 +00002606** can be integers, floating point values, strings, BLOBs, or NULL.
drhaa28e142008-03-18 13:47:20 +00002607**
2608** An sqlite3_value object may be either "protected" or "unprotected".
2609** Some interfaces require a protected sqlite3_value. Other interfaces
2610** will accept either a protected or an unprotected sqlite3_value.
mihailimefc8e8a2008-06-21 16:47:09 +00002611** Every interface that accepts sqlite3_value arguments specifies
drhaa28e142008-03-18 13:47:20 +00002612** whether or not it requires a protected sqlite3_value.
2613**
2614** The terms "protected" and "unprotected" refer to whether or not
2615** a mutex is held. A internal mutex is held for a protected
2616** sqlite3_value object but no mutex is held for an unprotected
2617** sqlite3_value object. If SQLite is compiled to be single-threaded
drh4766b292008-06-26 02:53:02 +00002618** (with [SQLITE_THREADSAFE=0] and with [sqlite3_threadsafe()] returning 0)
drh4ead1482008-06-26 18:16:05 +00002619** or if SQLite is run in one of reduced mutex modes
2620** [SQLITE_CONFIG_SINGLETHREAD] or [SQLITE_CONFIG_MULTITHREAD]
mihailimefc8e8a2008-06-21 16:47:09 +00002621** then there is no distinction between protected and unprotected
2622** sqlite3_value objects and they can be used interchangeably. However,
2623** for maximum code portability it is recommended that applications
2624** still make the distinction between between protected and unprotected
drh4ead1482008-06-26 18:16:05 +00002625** sqlite3_value objects even when not strictly required.
drhaa28e142008-03-18 13:47:20 +00002626**
drhd68eee02009-12-11 03:44:18 +00002627** ^The sqlite3_value objects that are passed as parameters into the
mihailimefc8e8a2008-06-21 16:47:09 +00002628** implementation of [application-defined SQL functions] are protected.
drhd68eee02009-12-11 03:44:18 +00002629** ^The sqlite3_value object returned by
drhaa28e142008-03-18 13:47:20 +00002630** [sqlite3_column_value()] is unprotected.
2631** Unprotected sqlite3_value objects may only be used with
mihailimefc8e8a2008-06-21 16:47:09 +00002632** [sqlite3_result_value()] and [sqlite3_bind_value()].
drhce5a5a02008-06-10 17:41:44 +00002633** The [sqlite3_value_blob | sqlite3_value_type()] family of
2634** interfaces require protected sqlite3_value objects.
drhf4479502004-05-27 03:12:53 +00002635*/
drhf4479502004-05-27 03:12:53 +00002636typedef struct Mem sqlite3_value;
2637
2638/*
drhfb434032009-12-11 23:11:26 +00002639** CAPI3REF: SQL Function Context Object
drh4f26d6c2004-05-26 23:25:30 +00002640**
drh6ed48bf2007-06-14 20:57:18 +00002641** The context in which an SQL function executes is stored in an
drhd68eee02009-12-11 03:44:18 +00002642** sqlite3_context object. ^A pointer to an sqlite3_context object
mihailimefc8e8a2008-06-21 16:47:09 +00002643** is always first parameter to [application-defined SQL functions].
2644** The application-defined SQL function implementation will pass this
2645** pointer through into calls to [sqlite3_result_int | sqlite3_result()],
2646** [sqlite3_aggregate_context()], [sqlite3_user_data()],
2647** [sqlite3_context_db_handle()], [sqlite3_get_auxdata()],
2648** and/or [sqlite3_set_auxdata()].
drh6ed48bf2007-06-14 20:57:18 +00002649*/
2650typedef struct sqlite3_context sqlite3_context;
2651
2652/*
drhfb434032009-12-11 23:11:26 +00002653** CAPI3REF: Binding Values To Prepared Statements
mihailimefc8e8a2008-06-21 16:47:09 +00002654** KEYWORDS: {host parameter} {host parameters} {host parameter name}
mihailimebe796c2008-06-21 20:11:17 +00002655** KEYWORDS: {SQL parameter} {SQL parameters} {parameter binding}
drh6ed48bf2007-06-14 20:57:18 +00002656**
drhd68eee02009-12-11 03:44:18 +00002657** ^(In the SQL statement text input to [sqlite3_prepare_v2()] and its variants,
drh333ceb92009-08-25 14:59:37 +00002658** literals may be replaced by a [parameter] that matches one of following
2659** templates:
drh6ed48bf2007-06-14 20:57:18 +00002660**
2661** <ul>
2662** <li> ?
2663** <li> ?NNN
drh33c1be32008-01-30 16:16:14 +00002664** <li> :VVV
2665** <li> @VVV
drh6ed48bf2007-06-14 20:57:18 +00002666** <li> $VVV
2667** </ul>
2668**
drh333ceb92009-08-25 14:59:37 +00002669** In the templates above, NNN represents an integer literal,
drh9b8d0272010-08-09 15:44:21 +00002670** and VVV represents an alphanumeric identifier.)^ ^The values of these
mihailimefc8e8a2008-06-21 16:47:09 +00002671** parameters (also called "host parameter names" or "SQL parameters")
drh6ed48bf2007-06-14 20:57:18 +00002672** can be set using the sqlite3_bind_*() routines defined here.
2673**
drhd68eee02009-12-11 03:44:18 +00002674** ^The first argument to the sqlite3_bind_*() routines is always
mihailimefc8e8a2008-06-21 16:47:09 +00002675** a pointer to the [sqlite3_stmt] object returned from
2676** [sqlite3_prepare_v2()] or its variants.
2677**
drhd68eee02009-12-11 03:44:18 +00002678** ^The second argument is the index of the SQL parameter to be set.
2679** ^The leftmost SQL parameter has an index of 1. ^When the same named
mihailimefc8e8a2008-06-21 16:47:09 +00002680** SQL parameter is used more than once, second and subsequent
2681** occurrences have the same index as the first occurrence.
drhd68eee02009-12-11 03:44:18 +00002682** ^The index for named parameters can be looked up using the
2683** [sqlite3_bind_parameter_index()] API if desired. ^The index
drhf5befa02007-12-06 02:42:07 +00002684** for "?NNN" parameters is the value of NNN.
drhd68eee02009-12-11 03:44:18 +00002685** ^The NNN value must be between 1 and the [sqlite3_limit()]
drh4ead1482008-06-26 18:16:05 +00002686** parameter [SQLITE_LIMIT_VARIABLE_NUMBER] (default value: 999).
drh6ed48bf2007-06-14 20:57:18 +00002687**
drhd68eee02009-12-11 03:44:18 +00002688** ^The third argument is the value to bind to the parameter.
drh6ed48bf2007-06-14 20:57:18 +00002689**
drhd68eee02009-12-11 03:44:18 +00002690** ^(In those routines that have a fourth argument, its value is the
mihailimefc8e8a2008-06-21 16:47:09 +00002691** number of bytes in the parameter. To be clear: the value is the
drhd68eee02009-12-11 03:44:18 +00002692** number of <u>bytes</u> in the value, not the number of characters.)^
2693** ^If the fourth parameter is negative, the length of the string is
shane26b34032008-05-23 17:21:09 +00002694** the number of bytes up to the first zero terminator.
drh4f26d6c2004-05-26 23:25:30 +00002695**
drhd68eee02009-12-11 03:44:18 +00002696** ^The fifth argument to sqlite3_bind_blob(), sqlite3_bind_text(), and
drh900dfba2004-07-21 15:21:36 +00002697** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or
drhd68eee02009-12-11 03:44:18 +00002698** string after SQLite has finished with it. ^If the fifth argument is
drh33c1be32008-01-30 16:16:14 +00002699** the special value [SQLITE_STATIC], then SQLite assumes that the
drhfddfa2d2007-12-05 18:05:16 +00002700** information is in static, unmanaged space and does not need to be freed.
drhd68eee02009-12-11 03:44:18 +00002701** ^If the fifth argument has the value [SQLITE_TRANSIENT], then
drhfddfa2d2007-12-05 18:05:16 +00002702** SQLite makes its own private copy of the data immediately, before
drh33c1be32008-01-30 16:16:14 +00002703** the sqlite3_bind_*() routine returns.
drh4f26d6c2004-05-26 23:25:30 +00002704**
drhd68eee02009-12-11 03:44:18 +00002705** ^The sqlite3_bind_zeroblob() routine binds a BLOB of length N that
2706** is filled with zeroes. ^A zeroblob uses a fixed amount of memory
mihailimefc8e8a2008-06-21 16:47:09 +00002707** (just an integer to hold its size) while it is being processed.
shane26b34032008-05-23 17:21:09 +00002708** Zeroblobs are intended to serve as placeholders for BLOBs whose
mihailimefc8e8a2008-06-21 16:47:09 +00002709** content is later written using
2710** [sqlite3_blob_open | incremental BLOB I/O] routines.
drhd68eee02009-12-11 03:44:18 +00002711** ^A negative value for the zeroblob results in a zero-length BLOB.
drh6ed48bf2007-06-14 20:57:18 +00002712**
drhd68eee02009-12-11 03:44:18 +00002713** ^If any of the sqlite3_bind_*() routines are called with a NULL pointer
2714** for the [prepared statement] or with a prepared statement for which
2715** [sqlite3_step()] has been called more recently than [sqlite3_reset()],
2716** then the call will return [SQLITE_MISUSE]. If any sqlite3_bind_()
2717** routine is passed a [prepared statement] that has been finalized, the
2718** result is undefined and probably harmful.
drh6ed48bf2007-06-14 20:57:18 +00002719**
drhd68eee02009-12-11 03:44:18 +00002720** ^Bindings are not cleared by the [sqlite3_reset()] routine.
2721** ^Unbound parameters are interpreted as NULL.
2722**
2723** ^The sqlite3_bind_* routines return [SQLITE_OK] on success or an
2724** [error code] if anything goes wrong.
2725** ^[SQLITE_RANGE] is returned if the parameter
2726** index is out of range. ^[SQLITE_NOMEM] is returned if malloc() fails.
drh33c1be32008-01-30 16:16:14 +00002727**
2728** See also: [sqlite3_bind_parameter_count()],
mihailimefc8e8a2008-06-21 16:47:09 +00002729** [sqlite3_bind_parameter_name()], and [sqlite3_bind_parameter_index()].
drh4f26d6c2004-05-26 23:25:30 +00002730*/
danielk1977d8123362004-06-12 09:25:12 +00002731int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +00002732int sqlite3_bind_double(sqlite3_stmt*, int, double);
2733int sqlite3_bind_int(sqlite3_stmt*, int, int);
drh6d2069d2007-08-14 01:58:53 +00002734int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite3_int64);
drhf4479502004-05-27 03:12:53 +00002735int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +00002736int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
2737int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +00002738int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drhb026e052007-05-02 01:34:31 +00002739int sqlite3_bind_zeroblob(sqlite3_stmt*, int, int n);
drh4f26d6c2004-05-26 23:25:30 +00002740
2741/*
drhd68eee02009-12-11 03:44:18 +00002742** CAPI3REF: Number Of SQL Parameters
drh6ed48bf2007-06-14 20:57:18 +00002743**
drhd68eee02009-12-11 03:44:18 +00002744** ^This routine can be used to find the number of [SQL parameters]
mihailimefc8e8a2008-06-21 16:47:09 +00002745** in a [prepared statement]. SQL parameters are tokens of the
drh33c1be32008-01-30 16:16:14 +00002746** form "?", "?NNN", ":AAA", "$AAA", or "@AAA" that serve as
shane26b34032008-05-23 17:21:09 +00002747** placeholders for values that are [sqlite3_bind_blob | bound]
drh33c1be32008-01-30 16:16:14 +00002748** to the parameters at a later time.
drh605264d2007-08-21 15:13:19 +00002749**
drhd68eee02009-12-11 03:44:18 +00002750** ^(This routine actually returns the index of the largest (rightmost)
mihailimefc8e8a2008-06-21 16:47:09 +00002751** parameter. For all forms except ?NNN, this will correspond to the
drhd68eee02009-12-11 03:44:18 +00002752** number of unique parameters. If parameters of the ?NNN form are used,
2753** there may be gaps in the list.)^
drh33c1be32008-01-30 16:16:14 +00002754**
2755** See also: [sqlite3_bind_blob|sqlite3_bind()],
2756** [sqlite3_bind_parameter_name()], and
2757** [sqlite3_bind_parameter_index()].
drh75f6a032004-07-15 14:15:00 +00002758*/
2759int sqlite3_bind_parameter_count(sqlite3_stmt*);
2760
2761/*
drhd68eee02009-12-11 03:44:18 +00002762** CAPI3REF: Name Of A Host Parameter
drh6ed48bf2007-06-14 20:57:18 +00002763**
drhd68eee02009-12-11 03:44:18 +00002764** ^The sqlite3_bind_parameter_name(P,N) interface returns
2765** the name of the N-th [SQL parameter] in the [prepared statement] P.
2766** ^(SQL parameters of the form "?NNN" or ":AAA" or "@AAA" or "$AAA"
drhe1b3e802008-04-27 22:29:01 +00002767** have a name which is the string "?NNN" or ":AAA" or "@AAA" or "$AAA"
2768** respectively.
2769** In other words, the initial ":" or "$" or "@" or "?"
drhd68eee02009-12-11 03:44:18 +00002770** is included as part of the name.)^
2771** ^Parameters of the form "?" without a following integer have no name
drhdf6473a2009-12-13 22:20:08 +00002772** and are referred to as "nameless" or "anonymous parameters".
drh6ed48bf2007-06-14 20:57:18 +00002773**
drhd68eee02009-12-11 03:44:18 +00002774** ^The first host parameter has an index of 1, not 0.
drh6ed48bf2007-06-14 20:57:18 +00002775**
drhd68eee02009-12-11 03:44:18 +00002776** ^If the value N is out of range or if the N-th parameter is
2777** nameless, then NULL is returned. ^The returned string is
mihailimefc8e8a2008-06-21 16:47:09 +00002778** always in UTF-8 encoding even if the named parameter was
drhfddfa2d2007-12-05 18:05:16 +00002779** originally specified as UTF-16 in [sqlite3_prepare16()] or
2780** [sqlite3_prepare16_v2()].
drh33c1be32008-01-30 16:16:14 +00002781**
2782** See also: [sqlite3_bind_blob|sqlite3_bind()],
2783** [sqlite3_bind_parameter_count()], and
2784** [sqlite3_bind_parameter_index()].
drh895d7472004-08-20 16:02:39 +00002785*/
2786const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
2787
2788/*
drhd68eee02009-12-11 03:44:18 +00002789** CAPI3REF: Index Of A Parameter With A Given Name
drh6ed48bf2007-06-14 20:57:18 +00002790**
drhd68eee02009-12-11 03:44:18 +00002791** ^Return the index of an SQL parameter given its name. ^The
drh33c1be32008-01-30 16:16:14 +00002792** index value returned is suitable for use as the second
drhd68eee02009-12-11 03:44:18 +00002793** parameter to [sqlite3_bind_blob|sqlite3_bind()]. ^A zero
2794** is returned if no matching parameter is found. ^The parameter
drh33c1be32008-01-30 16:16:14 +00002795** name must be given in UTF-8 even if the original statement
2796** was prepared from UTF-16 text using [sqlite3_prepare16_v2()].
2797**
2798** See also: [sqlite3_bind_blob|sqlite3_bind()],
2799** [sqlite3_bind_parameter_count()], and
2800** [sqlite3_bind_parameter_index()].
drhfa6bc002004-09-07 16:19:52 +00002801*/
2802int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
2803
2804/*
drhd68eee02009-12-11 03:44:18 +00002805** CAPI3REF: Reset All Bindings On A Prepared Statement
drh6ed48bf2007-06-14 20:57:18 +00002806**
drhd68eee02009-12-11 03:44:18 +00002807** ^Contrary to the intuition of many, [sqlite3_reset()] does not reset
mihailimefc8e8a2008-06-21 16:47:09 +00002808** the [sqlite3_bind_blob | bindings] on a [prepared statement].
drhd68eee02009-12-11 03:44:18 +00002809** ^Use this routine to reset all host parameters to NULL.
danielk1977600dd0b2005-01-20 01:14:23 +00002810*/
2811int sqlite3_clear_bindings(sqlite3_stmt*);
2812
2813/*
drhd68eee02009-12-11 03:44:18 +00002814** CAPI3REF: Number Of Columns In A Result Set
drh6ed48bf2007-06-14 20:57:18 +00002815**
drhd68eee02009-12-11 03:44:18 +00002816** ^Return the number of columns in the result set returned by the
2817** [prepared statement]. ^This routine returns 0 if pStmt is an SQL
drh4ead1482008-06-26 18:16:05 +00002818** statement that does not return data (for example an [UPDATE]).
danielk197765904932004-05-26 06:18:37 +00002819*/
2820int sqlite3_column_count(sqlite3_stmt *pStmt);
2821
2822/*
drhd68eee02009-12-11 03:44:18 +00002823** CAPI3REF: Column Names In A Result Set
drh6ed48bf2007-06-14 20:57:18 +00002824**
drhd68eee02009-12-11 03:44:18 +00002825** ^These routines return the name assigned to a particular column
2826** in the result set of a [SELECT] statement. ^The sqlite3_column_name()
mihailimefc8e8a2008-06-21 16:47:09 +00002827** interface returns a pointer to a zero-terminated UTF-8 string
drhf5befa02007-12-06 02:42:07 +00002828** and sqlite3_column_name16() returns a pointer to a zero-terminated
drhd68eee02009-12-11 03:44:18 +00002829** UTF-16 string. ^The first parameter is the [prepared statement]
2830** that implements the [SELECT] statement. ^The second parameter is the
2831** column number. ^The leftmost column is number 0.
drh6ed48bf2007-06-14 20:57:18 +00002832**
drhd68eee02009-12-11 03:44:18 +00002833** ^The returned string pointer is valid until either the [prepared statement]
mihailimefc8e8a2008-06-21 16:47:09 +00002834** is destroyed by [sqlite3_finalize()] or until the next call to
2835** sqlite3_column_name() or sqlite3_column_name16() on the same column.
drh4a50aac2007-08-23 02:47:53 +00002836**
drhd68eee02009-12-11 03:44:18 +00002837** ^If sqlite3_malloc() fails during the processing of either routine
drh4a50aac2007-08-23 02:47:53 +00002838** (for example during a conversion from UTF-8 to UTF-16) then a
2839** NULL pointer is returned.
drh33c1be32008-01-30 16:16:14 +00002840**
drhd68eee02009-12-11 03:44:18 +00002841** ^The name of a result column is the value of the "AS" clause for
drh33c1be32008-01-30 16:16:14 +00002842** that column, if there is an AS clause. If there is no AS clause
2843** then the name of the column is unspecified and may change from
2844** one release of SQLite to the next.
danielk197765904932004-05-26 06:18:37 +00002845*/
drh6ed48bf2007-06-14 20:57:18 +00002846const char *sqlite3_column_name(sqlite3_stmt*, int N);
2847const void *sqlite3_column_name16(sqlite3_stmt*, int N);
danielk197765904932004-05-26 06:18:37 +00002848
2849/*
drhd68eee02009-12-11 03:44:18 +00002850** CAPI3REF: Source Of Data In A Query Result
drh6ed48bf2007-06-14 20:57:18 +00002851**
drh9be37f62009-12-12 23:57:36 +00002852** ^These routines provide a means to determine the database, table, and
2853** table column that is the origin of a particular result column in
2854** [SELECT] statement.
drhd68eee02009-12-11 03:44:18 +00002855** ^The name of the database or table or column can be returned as
2856** either a UTF-8 or UTF-16 string. ^The _database_ routines return
drhbf2564f2007-06-21 15:25:05 +00002857** the database name, the _table_ routines return the table name, and
drh33c1be32008-01-30 16:16:14 +00002858** the origin_ routines return the column name.
drhd68eee02009-12-11 03:44:18 +00002859** ^The returned string is valid until the [prepared statement] is destroyed
mihailim1c492652008-06-21 18:02:16 +00002860** using [sqlite3_finalize()] or until the same information is requested
drhbf2564f2007-06-21 15:25:05 +00002861** again in a different encoding.
2862**
drhd68eee02009-12-11 03:44:18 +00002863** ^The names returned are the original un-aliased names of the
drhbf2564f2007-06-21 15:25:05 +00002864** database, table, and column.
drh6ed48bf2007-06-14 20:57:18 +00002865**
drh9be37f62009-12-12 23:57:36 +00002866** ^The first argument to these interfaces is a [prepared statement].
2867** ^These functions return information about the Nth result column returned by
danielk1977955de522006-02-10 02:27:42 +00002868** the statement, where N is the second function argument.
drh9be37f62009-12-12 23:57:36 +00002869** ^The left-most column is column 0 for these routines.
danielk1977955de522006-02-10 02:27:42 +00002870**
drhd68eee02009-12-11 03:44:18 +00002871** ^If the Nth column returned by the statement is an expression or
mihailim1c492652008-06-21 18:02:16 +00002872** subquery and is not a column value, then all of these functions return
drhd68eee02009-12-11 03:44:18 +00002873** NULL. ^These routine might also return NULL if a memory allocation error
drhdf6473a2009-12-13 22:20:08 +00002874** occurs. ^Otherwise, they return the name of the attached database, table,
drhd68eee02009-12-11 03:44:18 +00002875** or column that query result column was extracted from.
danielk1977955de522006-02-10 02:27:42 +00002876**
drh9be37f62009-12-12 23:57:36 +00002877** ^As with all other SQLite APIs, those whose names end with "16" return
2878** UTF-16 encoded strings and the other functions return UTF-8.
danielk19774b1ae992006-02-10 03:06:10 +00002879**
drhd68eee02009-12-11 03:44:18 +00002880** ^These APIs are only available if the library was compiled with the
drh9be37f62009-12-12 23:57:36 +00002881** [SQLITE_ENABLE_COLUMN_METADATA] C-preprocessor symbol.
drh32bc3f62007-08-21 20:25:39 +00002882**
2883** If two or more threads call one or more of these routines against the same
2884** prepared statement and column at the same time then the results are
2885** undefined.
drh33c1be32008-01-30 16:16:14 +00002886**
drh8b39db12009-02-18 18:37:58 +00002887** If two or more threads call one or more
2888** [sqlite3_column_database_name | column metadata interfaces]
2889** for the same [prepared statement] and result column
2890** at the same time then the results are undefined.
danielk1977955de522006-02-10 02:27:42 +00002891*/
2892const char *sqlite3_column_database_name(sqlite3_stmt*,int);
2893const void *sqlite3_column_database_name16(sqlite3_stmt*,int);
2894const char *sqlite3_column_table_name(sqlite3_stmt*,int);
2895const void *sqlite3_column_table_name16(sqlite3_stmt*,int);
2896const char *sqlite3_column_origin_name(sqlite3_stmt*,int);
2897const void *sqlite3_column_origin_name16(sqlite3_stmt*,int);
2898
2899/*
drhd68eee02009-12-11 03:44:18 +00002900** CAPI3REF: Declared Datatype Of A Query Result
drh6ed48bf2007-06-14 20:57:18 +00002901**
drhd68eee02009-12-11 03:44:18 +00002902** ^(The first parameter is a [prepared statement].
drh4ead1482008-06-26 18:16:05 +00002903** If this statement is a [SELECT] statement and the Nth column of the
2904** returned result set of that [SELECT] is a table column (not an
drh6ed48bf2007-06-14 20:57:18 +00002905** expression or subquery) then the declared type of the table
drhdf6473a2009-12-13 22:20:08 +00002906** column is returned.)^ ^If the Nth column of the result set is an
drh6ed48bf2007-06-14 20:57:18 +00002907** expression or subquery, then a NULL pointer is returned.
drhd68eee02009-12-11 03:44:18 +00002908** ^The returned string is always UTF-8 encoded.
mihailim1c492652008-06-21 18:02:16 +00002909**
drhd68eee02009-12-11 03:44:18 +00002910** ^(For example, given the database schema:
danielk197765904932004-05-26 06:18:37 +00002911**
2912** CREATE TABLE t1(c1 VARIANT);
2913**
mihailim1c492652008-06-21 18:02:16 +00002914** and the following statement to be compiled:
danielk197765904932004-05-26 06:18:37 +00002915**
danielk1977955de522006-02-10 02:27:42 +00002916** SELECT c1 + 1, c1 FROM t1;
danielk197765904932004-05-26 06:18:37 +00002917**
mihailim1c492652008-06-21 18:02:16 +00002918** this routine would return the string "VARIANT" for the second result
drhd68eee02009-12-11 03:44:18 +00002919** column (i==1), and a NULL pointer for the first result column (i==0).)^
drh6ed48bf2007-06-14 20:57:18 +00002920**
drhd68eee02009-12-11 03:44:18 +00002921** ^SQLite uses dynamic run-time typing. ^So just because a column
drh6ed48bf2007-06-14 20:57:18 +00002922** is declared to contain a particular type does not mean that the
2923** data stored in that column is of the declared type. SQLite is
drhd68eee02009-12-11 03:44:18 +00002924** strongly typed, but the typing is dynamic not static. ^Type
drh6ed48bf2007-06-14 20:57:18 +00002925** is associated with individual values, not with the containers
2926** used to hold those values.
danielk197765904932004-05-26 06:18:37 +00002927*/
drh33c1be32008-01-30 16:16:14 +00002928const char *sqlite3_column_decltype(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +00002929const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
2930
mihailimebe796c2008-06-21 20:11:17 +00002931/*
drhd68eee02009-12-11 03:44:18 +00002932** CAPI3REF: Evaluate An SQL Statement
danielk1977106bb232004-05-21 10:08:53 +00002933**
mihailim1c492652008-06-21 18:02:16 +00002934** After a [prepared statement] has been prepared using either
2935** [sqlite3_prepare_v2()] or [sqlite3_prepare16_v2()] or one of the legacy
2936** interfaces [sqlite3_prepare()] or [sqlite3_prepare16()], this function
2937** must be called one or more times to evaluate the statement.
danielk1977106bb232004-05-21 10:08:53 +00002938**
mihailim1c492652008-06-21 18:02:16 +00002939** The details of the behavior of the sqlite3_step() interface depend
drh6ed48bf2007-06-14 20:57:18 +00002940** on whether the statement was prepared using the newer "v2" interface
2941** [sqlite3_prepare_v2()] and [sqlite3_prepare16_v2()] or the older legacy
2942** interface [sqlite3_prepare()] and [sqlite3_prepare16()]. The use of the
2943** new "v2" interface is recommended for new applications but the legacy
2944** interface will continue to be supported.
danielk1977106bb232004-05-21 10:08:53 +00002945**
drhd68eee02009-12-11 03:44:18 +00002946** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
drh6ed48bf2007-06-14 20:57:18 +00002947** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE].
drhd68eee02009-12-11 03:44:18 +00002948** ^With the "v2" interface, any of the other [result codes] or
mihailim1c492652008-06-21 18:02:16 +00002949** [extended result codes] might be returned as well.
drh6ed48bf2007-06-14 20:57:18 +00002950**
drhd68eee02009-12-11 03:44:18 +00002951** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
2952** database locks it needs to do its job. ^If the statement is a [COMMIT]
drh6ed48bf2007-06-14 20:57:18 +00002953** or occurs outside of an explicit transaction, then you can retry the
drh4ead1482008-06-26 18:16:05 +00002954** statement. If the statement is not a [COMMIT] and occurs within a
drh6ed48bf2007-06-14 20:57:18 +00002955** explicit transaction then you should rollback the transaction before
2956** continuing.
2957**
drhd68eee02009-12-11 03:44:18 +00002958** ^[SQLITE_DONE] means that the statement has finished executing
danielk1977106bb232004-05-21 10:08:53 +00002959** successfully. sqlite3_step() should not be called again on this virtual
drh6ed48bf2007-06-14 20:57:18 +00002960** machine without first calling [sqlite3_reset()] to reset the virtual
2961** machine back to its initial state.
danielk1977106bb232004-05-21 10:08:53 +00002962**
drhd68eee02009-12-11 03:44:18 +00002963** ^If the SQL statement being executed returns any data, then [SQLITE_ROW]
mihailim1c492652008-06-21 18:02:16 +00002964** is returned each time a new row of data is ready for processing by the
2965** caller. The values may be accessed using the [column access functions].
drh6ed48bf2007-06-14 20:57:18 +00002966** sqlite3_step() is called again to retrieve the next row of data.
mihailim1c492652008-06-21 18:02:16 +00002967**
drhd68eee02009-12-11 03:44:18 +00002968** ^[SQLITE_ERROR] means that a run-time error (such as a constraint
danielk1977106bb232004-05-21 10:08:53 +00002969** violation) has occurred. sqlite3_step() should not be called again on
drh6ed48bf2007-06-14 20:57:18 +00002970** the VM. More information may be found by calling [sqlite3_errmsg()].
drhd68eee02009-12-11 03:44:18 +00002971** ^With the legacy interface, a more specific error code (for example,
drh6ed48bf2007-06-14 20:57:18 +00002972** [SQLITE_INTERRUPT], [SQLITE_SCHEMA], [SQLITE_CORRUPT], and so forth)
2973** can be obtained by calling [sqlite3_reset()] on the
drhd68eee02009-12-11 03:44:18 +00002974** [prepared statement]. ^In the "v2" interface,
drh6ed48bf2007-06-14 20:57:18 +00002975** the more specific error code is returned directly by sqlite3_step().
danielk1977106bb232004-05-21 10:08:53 +00002976**
drh6ed48bf2007-06-14 20:57:18 +00002977** [SQLITE_MISUSE] means that the this routine was called inappropriately.
drh33c1be32008-01-30 16:16:14 +00002978** Perhaps it was called on a [prepared statement] that has
mihailim1c492652008-06-21 18:02:16 +00002979** already been [sqlite3_finalize | finalized] or on one that had
drh6ed48bf2007-06-14 20:57:18 +00002980** previously returned [SQLITE_ERROR] or [SQLITE_DONE]. Or it could
2981** be the case that the same database connection is being used by two or
2982** more threads at the same moment in time.
2983**
drh3674bfd2010-04-17 12:53:19 +00002984** For all versions of SQLite up to and including 3.6.23.1, it was required
2985** after sqlite3_step() returned anything other than [SQLITE_ROW] that
2986** [sqlite3_reset()] be called before any subsequent invocation of
2987** sqlite3_step(). Failure to invoke [sqlite3_reset()] in this way would
2988** result in an [SQLITE_MISUSE] return from sqlite3_step(). But after
2989** version 3.6.23.1, sqlite3_step() began calling [sqlite3_reset()]
2990** automatically in this circumstance rather than returning [SQLITE_MISUSE].
2991**
mihailim1c492652008-06-21 18:02:16 +00002992** <b>Goofy Interface Alert:</b> In the legacy interface, the sqlite3_step()
2993** API always returns a generic error code, [SQLITE_ERROR], following any
2994** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
2995** [sqlite3_reset()] or [sqlite3_finalize()] in order to find one of the
2996** specific [error codes] that better describes the error.
drh6ed48bf2007-06-14 20:57:18 +00002997** We admit that this is a goofy design. The problem has been fixed
2998** with the "v2" interface. If you prepare all of your SQL statements
2999** using either [sqlite3_prepare_v2()] or [sqlite3_prepare16_v2()] instead
mihailim1c492652008-06-21 18:02:16 +00003000** of the legacy [sqlite3_prepare()] and [sqlite3_prepare16()] interfaces,
3001** then the more specific [error codes] are returned directly
drh6ed48bf2007-06-14 20:57:18 +00003002** by sqlite3_step(). The use of the "v2" interface is recommended.
danielk1977106bb232004-05-21 10:08:53 +00003003*/
danielk197717240fd2004-05-26 00:07:25 +00003004int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +00003005
danielk1977106bb232004-05-21 10:08:53 +00003006/*
drhd68eee02009-12-11 03:44:18 +00003007** CAPI3REF: Number of columns in a result set
drh6ed48bf2007-06-14 20:57:18 +00003008**
drhfb434032009-12-11 23:11:26 +00003009** ^The sqlite3_data_count(P) the number of columns in the
3010** of the result set of [prepared statement] P.
danielk1977106bb232004-05-21 10:08:53 +00003011*/
danielk197793d46752004-05-23 13:30:58 +00003012int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +00003013
drh4f26d6c2004-05-26 23:25:30 +00003014/*
drhd68eee02009-12-11 03:44:18 +00003015** CAPI3REF: Fundamental Datatypes
drh33c1be32008-01-30 16:16:14 +00003016** KEYWORDS: SQLITE_TEXT
drh6ed48bf2007-06-14 20:57:18 +00003017**
drhfb434032009-12-11 23:11:26 +00003018** ^(Every value in SQLite has one of five fundamental datatypes:
drh6ed48bf2007-06-14 20:57:18 +00003019**
3020** <ul>
3021** <li> 64-bit signed integer
3022** <li> 64-bit IEEE floating point number
3023** <li> string
3024** <li> BLOB
3025** <li> NULL
drhfb434032009-12-11 23:11:26 +00003026** </ul>)^
drh6ed48bf2007-06-14 20:57:18 +00003027**
3028** These constants are codes for each of those types.
3029**
3030** Note that the SQLITE_TEXT constant was also used in SQLite version 2
3031** for a completely different meaning. Software that links against both
mihailim1c492652008-06-21 18:02:16 +00003032** SQLite version 2 and SQLite version 3 should use SQLITE3_TEXT, not
drh6ed48bf2007-06-14 20:57:18 +00003033** SQLITE_TEXT.
drh4f26d6c2004-05-26 23:25:30 +00003034*/
drh9c054832004-05-31 18:51:57 +00003035#define SQLITE_INTEGER 1
3036#define SQLITE_FLOAT 2
drh9c054832004-05-31 18:51:57 +00003037#define SQLITE_BLOB 4
3038#define SQLITE_NULL 5
drh1e284f42004-10-06 15:52:01 +00003039#ifdef SQLITE_TEXT
3040# undef SQLITE_TEXT
3041#else
3042# define SQLITE_TEXT 3
3043#endif
3044#define SQLITE3_TEXT 3
3045
3046/*
drhd68eee02009-12-11 03:44:18 +00003047** CAPI3REF: Result Values From A Query
mihailim1c492652008-06-21 18:02:16 +00003048** KEYWORDS: {column access functions}
drh6ed48bf2007-06-14 20:57:18 +00003049**
drhd68eee02009-12-11 03:44:18 +00003050** These routines form the "result set" interface.
drh33c1be32008-01-30 16:16:14 +00003051**
drhd68eee02009-12-11 03:44:18 +00003052** ^These routines return information about a single column of the current
3053** result row of a query. ^In every case the first argument is a pointer
mihailim1c492652008-06-21 18:02:16 +00003054** to the [prepared statement] that is being evaluated (the [sqlite3_stmt*]
3055** that was returned from [sqlite3_prepare_v2()] or one of its variants)
3056** and the second argument is the index of the column for which information
drhd68eee02009-12-11 03:44:18 +00003057** should be returned. ^The leftmost column of the result set has the index 0.
3058** ^The number of columns in the result can be determined using
drhedc17552009-10-22 00:14:05 +00003059** [sqlite3_column_count()].
danielk1977106bb232004-05-21 10:08:53 +00003060**
mihailim1c492652008-06-21 18:02:16 +00003061** If the SQL statement does not currently point to a valid row, or if the
3062** column index is out of range, the result is undefined.
drh32bc3f62007-08-21 20:25:39 +00003063** These routines may only be called when the most recent call to
3064** [sqlite3_step()] has returned [SQLITE_ROW] and neither
mihailim1c492652008-06-21 18:02:16 +00003065** [sqlite3_reset()] nor [sqlite3_finalize()] have been called subsequently.
drh32bc3f62007-08-21 20:25:39 +00003066** If any of these routines are called after [sqlite3_reset()] or
3067** [sqlite3_finalize()] or after [sqlite3_step()] has returned
3068** something other than [SQLITE_ROW], the results are undefined.
3069** If [sqlite3_step()] or [sqlite3_reset()] or [sqlite3_finalize()]
3070** are called from a different thread while any of these routines
mihailim1c492652008-06-21 18:02:16 +00003071** are pending, then the results are undefined.
drh6ed48bf2007-06-14 20:57:18 +00003072**
drhd68eee02009-12-11 03:44:18 +00003073** ^The sqlite3_column_type() routine returns the
drh6ed48bf2007-06-14 20:57:18 +00003074** [SQLITE_INTEGER | datatype code] for the initial data type
drhd68eee02009-12-11 03:44:18 +00003075** of the result column. ^The returned value is one of [SQLITE_INTEGER],
drh6ed48bf2007-06-14 20:57:18 +00003076** [SQLITE_FLOAT], [SQLITE_TEXT], [SQLITE_BLOB], or [SQLITE_NULL]. The value
3077** returned by sqlite3_column_type() is only meaningful if no type
3078** conversions have occurred as described below. After a type conversion,
3079** the value returned by sqlite3_column_type() is undefined. Future
3080** versions of SQLite may change the behavior of sqlite3_column_type()
3081** following a type conversion.
3082**
drhd68eee02009-12-11 03:44:18 +00003083** ^If the result is a BLOB or UTF-8 string then the sqlite3_column_bytes()
drh6ed48bf2007-06-14 20:57:18 +00003084** routine returns the number of bytes in that BLOB or string.
drhd68eee02009-12-11 03:44:18 +00003085** ^If the result is a UTF-16 string, then sqlite3_column_bytes() converts
drh6ed48bf2007-06-14 20:57:18 +00003086** the string to UTF-8 and then returns the number of bytes.
drhd68eee02009-12-11 03:44:18 +00003087** ^If the result is a numeric value then sqlite3_column_bytes() uses
mihailimebe796c2008-06-21 20:11:17 +00003088** [sqlite3_snprintf()] to convert that value to a UTF-8 string and returns
drh6ed48bf2007-06-14 20:57:18 +00003089** the number of bytes in that string.
drhd68eee02009-12-11 03:44:18 +00003090** ^The value returned does not include the zero terminator at the end
3091** of the string. ^For clarity: the value returned is the number of
drh6ed48bf2007-06-14 20:57:18 +00003092** bytes in the string, not the number of characters.
3093**
drhd68eee02009-12-11 03:44:18 +00003094** ^Strings returned by sqlite3_column_text() and sqlite3_column_text16(),
3095** even empty strings, are always zero terminated. ^The return
mihailim04bcc002008-06-22 10:21:27 +00003096** value from sqlite3_column_blob() for a zero-length BLOB is an arbitrary
drhc0b3abb2007-09-04 12:18:41 +00003097** pointer, possibly even a NULL pointer.
3098**
drhd68eee02009-12-11 03:44:18 +00003099** ^The sqlite3_column_bytes16() routine is similar to sqlite3_column_bytes()
mihailim1c492652008-06-21 18:02:16 +00003100** but leaves the result in UTF-16 in native byte order instead of UTF-8.
drhd68eee02009-12-11 03:44:18 +00003101** ^The zero terminator is not included in this count.
drh4f26d6c2004-05-26 23:25:30 +00003102**
drhd68eee02009-12-11 03:44:18 +00003103** ^The object returned by [sqlite3_column_value()] is an
drhaa28e142008-03-18 13:47:20 +00003104** [unprotected sqlite3_value] object. An unprotected sqlite3_value object
3105** may only be used with [sqlite3_bind_value()] and [sqlite3_result_value()].
3106** If the [unprotected sqlite3_value] object returned by
3107** [sqlite3_column_value()] is used in any other way, including calls
mihailim1c492652008-06-21 18:02:16 +00003108** to routines like [sqlite3_value_int()], [sqlite3_value_text()],
3109** or [sqlite3_value_bytes()], then the behavior is undefined.
drhaa28e142008-03-18 13:47:20 +00003110**
drhd68eee02009-12-11 03:44:18 +00003111** These routines attempt to convert the value where appropriate. ^For
drh4f26d6c2004-05-26 23:25:30 +00003112** example, if the internal representation is FLOAT and a text result
mihailim1c492652008-06-21 18:02:16 +00003113** is requested, [sqlite3_snprintf()] is used internally to perform the
drhd68eee02009-12-11 03:44:18 +00003114** conversion automatically. ^(The following table details the conversions
mihailim1c492652008-06-21 18:02:16 +00003115** that are applied:
drh4f26d6c2004-05-26 23:25:30 +00003116**
drh6ed48bf2007-06-14 20:57:18 +00003117** <blockquote>
3118** <table border="1">
drh8bacf972007-08-25 16:21:29 +00003119** <tr><th> Internal<br>Type <th> Requested<br>Type <th> Conversion
drh4f26d6c2004-05-26 23:25:30 +00003120**
drh6ed48bf2007-06-14 20:57:18 +00003121** <tr><td> NULL <td> INTEGER <td> Result is 0
3122** <tr><td> NULL <td> FLOAT <td> Result is 0.0
3123** <tr><td> NULL <td> TEXT <td> Result is NULL pointer
3124** <tr><td> NULL <td> BLOB <td> Result is NULL pointer
3125** <tr><td> INTEGER <td> FLOAT <td> Convert from integer to float
3126** <tr><td> INTEGER <td> TEXT <td> ASCII rendering of the integer
mihailim1c492652008-06-21 18:02:16 +00003127** <tr><td> INTEGER <td> BLOB <td> Same as INTEGER->TEXT
drh6ed48bf2007-06-14 20:57:18 +00003128** <tr><td> FLOAT <td> INTEGER <td> Convert from float to integer
3129** <tr><td> FLOAT <td> TEXT <td> ASCII rendering of the float
3130** <tr><td> FLOAT <td> BLOB <td> Same as FLOAT->TEXT
3131** <tr><td> TEXT <td> INTEGER <td> Use atoi()
3132** <tr><td> TEXT <td> FLOAT <td> Use atof()
3133** <tr><td> TEXT <td> BLOB <td> No change
3134** <tr><td> BLOB <td> INTEGER <td> Convert to TEXT then use atoi()
3135** <tr><td> BLOB <td> FLOAT <td> Convert to TEXT then use atof()
3136** <tr><td> BLOB <td> TEXT <td> Add a zero terminator if needed
3137** </table>
drhd68eee02009-12-11 03:44:18 +00003138** </blockquote>)^
drh4f26d6c2004-05-26 23:25:30 +00003139**
drh6ed48bf2007-06-14 20:57:18 +00003140** The table above makes reference to standard C library functions atoi()
3141** and atof(). SQLite does not really use these functions. It has its
shane26b34032008-05-23 17:21:09 +00003142** own equivalent internal routines. The atoi() and atof() names are
drh6ed48bf2007-06-14 20:57:18 +00003143** used in the table for brevity and because they are familiar to most
3144** C programmers.
3145**
drhd68eee02009-12-11 03:44:18 +00003146** ^Note that when type conversions occur, pointers returned by prior
drh6ed48bf2007-06-14 20:57:18 +00003147** calls to sqlite3_column_blob(), sqlite3_column_text(), and/or
mihailim1c492652008-06-21 18:02:16 +00003148** sqlite3_column_text16() may be invalidated.
drhd68eee02009-12-11 03:44:18 +00003149** ^(Type conversions and pointer invalidations might occur
drh6ed48bf2007-06-14 20:57:18 +00003150** in the following cases:
3151**
3152** <ul>
mihailim1c492652008-06-21 18:02:16 +00003153** <li> The initial content is a BLOB and sqlite3_column_text() or
3154** sqlite3_column_text16() is called. A zero-terminator might
3155** need to be added to the string.</li>
3156** <li> The initial content is UTF-8 text and sqlite3_column_bytes16() or
3157** sqlite3_column_text16() is called. The content must be converted
3158** to UTF-16.</li>
3159** <li> The initial content is UTF-16 text and sqlite3_column_bytes() or
3160** sqlite3_column_text() is called. The content must be converted
3161** to UTF-8.</li>
drhd68eee02009-12-11 03:44:18 +00003162** </ul>)^
drh6ed48bf2007-06-14 20:57:18 +00003163**
drhd68eee02009-12-11 03:44:18 +00003164** ^Conversions between UTF-16be and UTF-16le are always done in place and do
drh6ed48bf2007-06-14 20:57:18 +00003165** not invalidate a prior pointer, though of course the content of the buffer
3166** that the prior pointer points to will have been modified. Other kinds
mihailim1c492652008-06-21 18:02:16 +00003167** of conversion are done in place when it is possible, but sometimes they
3168** are not possible and in those cases prior pointers are invalidated.
drh6ed48bf2007-06-14 20:57:18 +00003169**
drhd68eee02009-12-11 03:44:18 +00003170** ^(The safest and easiest to remember policy is to invoke these routines
drh6ed48bf2007-06-14 20:57:18 +00003171** in one of the following ways:
3172**
mihailim1c492652008-06-21 18:02:16 +00003173** <ul>
drh6ed48bf2007-06-14 20:57:18 +00003174** <li>sqlite3_column_text() followed by sqlite3_column_bytes()</li>
3175** <li>sqlite3_column_blob() followed by sqlite3_column_bytes()</li>
3176** <li>sqlite3_column_text16() followed by sqlite3_column_bytes16()</li>
drhd68eee02009-12-11 03:44:18 +00003177** </ul>)^
drh6ed48bf2007-06-14 20:57:18 +00003178**
mihailim1c492652008-06-21 18:02:16 +00003179** In other words, you should call sqlite3_column_text(),
3180** sqlite3_column_blob(), or sqlite3_column_text16() first to force the result
3181** into the desired format, then invoke sqlite3_column_bytes() or
3182** sqlite3_column_bytes16() to find the size of the result. Do not mix calls
3183** to sqlite3_column_text() or sqlite3_column_blob() with calls to
3184** sqlite3_column_bytes16(), and do not mix calls to sqlite3_column_text16()
3185** with calls to sqlite3_column_bytes().
drh32bc3f62007-08-21 20:25:39 +00003186**
drhd68eee02009-12-11 03:44:18 +00003187** ^The pointers returned are valid until a type conversion occurs as
drh32bc3f62007-08-21 20:25:39 +00003188** described above, or until [sqlite3_step()] or [sqlite3_reset()] or
drhd68eee02009-12-11 03:44:18 +00003189** [sqlite3_finalize()] is called. ^The memory space used to hold strings
mihailim04bcc002008-06-22 10:21:27 +00003190** and BLOBs is freed automatically. Do <b>not</b> pass the pointers returned
mihailim1c492652008-06-21 18:02:16 +00003191** [sqlite3_column_blob()], [sqlite3_column_text()], etc. into
drh32bc3f62007-08-21 20:25:39 +00003192** [sqlite3_free()].
drh4a50aac2007-08-23 02:47:53 +00003193**
drhd68eee02009-12-11 03:44:18 +00003194** ^(If a memory allocation error occurs during the evaluation of any
drh4a50aac2007-08-23 02:47:53 +00003195** of these routines, a default value is returned. The default value
3196** is either the integer 0, the floating point number 0.0, or a NULL
3197** pointer. Subsequent calls to [sqlite3_errcode()] will return
drhd68eee02009-12-11 03:44:18 +00003198** [SQLITE_NOMEM].)^
danielk1977106bb232004-05-21 10:08:53 +00003199*/
drhf4479502004-05-27 03:12:53 +00003200const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
3201int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
3202int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
3203double sqlite3_column_double(sqlite3_stmt*, int iCol);
3204int sqlite3_column_int(sqlite3_stmt*, int iCol);
drh6d2069d2007-08-14 01:58:53 +00003205sqlite3_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +00003206const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
3207const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +00003208int sqlite3_column_type(sqlite3_stmt*, int iCol);
drh4be8b512006-06-13 23:51:34 +00003209sqlite3_value *sqlite3_column_value(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +00003210
danielk197765904932004-05-26 06:18:37 +00003211/*
drhd68eee02009-12-11 03:44:18 +00003212** CAPI3REF: Destroy A Prepared Statement Object
drh6ed48bf2007-06-14 20:57:18 +00003213**
drhd68eee02009-12-11 03:44:18 +00003214** ^The sqlite3_finalize() function is called to delete a [prepared statement].
3215** ^If the statement was executed successfully or not executed at all, then
3216** SQLITE_OK is returned. ^If execution of the statement failed then an
mihailimebe796c2008-06-21 20:11:17 +00003217** [error code] or [extended error code] is returned.
danielk197765904932004-05-26 06:18:37 +00003218**
drhd68eee02009-12-11 03:44:18 +00003219** ^This routine can be called at any point during the execution of the
3220** [prepared statement]. ^If the virtual machine has not
drh6ed48bf2007-06-14 20:57:18 +00003221** completed execution when this routine is called, that is like
mihailimebe796c2008-06-21 20:11:17 +00003222** encountering an error or an [sqlite3_interrupt | interrupt].
drhd68eee02009-12-11 03:44:18 +00003223** ^Incomplete updates may be rolled back and transactions canceled,
mihailimebe796c2008-06-21 20:11:17 +00003224** depending on the circumstances, and the
drh33c1be32008-01-30 16:16:14 +00003225** [error code] returned will be [SQLITE_ABORT].
danielk197765904932004-05-26 06:18:37 +00003226*/
3227int sqlite3_finalize(sqlite3_stmt *pStmt);
3228
3229/*
drhd68eee02009-12-11 03:44:18 +00003230** CAPI3REF: Reset A Prepared Statement Object
drh6ed48bf2007-06-14 20:57:18 +00003231**
mihailimebe796c2008-06-21 20:11:17 +00003232** The sqlite3_reset() function is called to reset a [prepared statement]
3233** object back to its initial state, ready to be re-executed.
drhd68eee02009-12-11 03:44:18 +00003234** ^Any SQL statement variables that had values bound to them using
drh6ed48bf2007-06-14 20:57:18 +00003235** the [sqlite3_bind_blob | sqlite3_bind_*() API] retain their values.
3236** Use [sqlite3_clear_bindings()] to reset the bindings.
drh33c1be32008-01-30 16:16:14 +00003237**
drhd68eee02009-12-11 03:44:18 +00003238** ^The [sqlite3_reset(S)] interface resets the [prepared statement] S
3239** back to the beginning of its program.
drh33c1be32008-01-30 16:16:14 +00003240**
drhd68eee02009-12-11 03:44:18 +00003241** ^If the most recent call to [sqlite3_step(S)] for the
3242** [prepared statement] S returned [SQLITE_ROW] or [SQLITE_DONE],
3243** or if [sqlite3_step(S)] has never before been called on S,
3244** then [sqlite3_reset(S)] returns [SQLITE_OK].
drh33c1be32008-01-30 16:16:14 +00003245**
drhd68eee02009-12-11 03:44:18 +00003246** ^If the most recent call to [sqlite3_step(S)] for the
3247** [prepared statement] S indicated an error, then
3248** [sqlite3_reset(S)] returns an appropriate [error code].
drh33c1be32008-01-30 16:16:14 +00003249**
drhd68eee02009-12-11 03:44:18 +00003250** ^The [sqlite3_reset(S)] interface does not change the values
3251** of any [sqlite3_bind_blob|bindings] on the [prepared statement] S.
danielk197765904932004-05-26 06:18:37 +00003252*/
3253int sqlite3_reset(sqlite3_stmt *pStmt);
3254
3255/*
drhd68eee02009-12-11 03:44:18 +00003256** CAPI3REF: Create Or Redefine SQL Functions
mihailimefc8e8a2008-06-21 16:47:09 +00003257** KEYWORDS: {function creation routines}
3258** KEYWORDS: {application-defined SQL function}
3259** KEYWORDS: {application-defined SQL functions}
drh6ed48bf2007-06-14 20:57:18 +00003260**
drhd68eee02009-12-11 03:44:18 +00003261** ^These two functions (collectively known as "function creation routines")
mihailimebe796c2008-06-21 20:11:17 +00003262** are used to add SQL functions or aggregates or to redefine the behavior
3263** of existing SQL functions or aggregates. The only difference between the
3264** two is that the second parameter, the name of the (scalar) function or
3265** aggregate, is encoded in UTF-8 for sqlite3_create_function() and UTF-16
3266** for sqlite3_create_function16().
danielk197765904932004-05-26 06:18:37 +00003267**
drhdf6473a2009-12-13 22:20:08 +00003268** ^The first parameter is the [database connection] to which the SQL
3269** function is to be added. ^If an application uses more than one database
3270** connection then application-defined SQL functions must be added
3271** to each database connection separately.
danielk197765904932004-05-26 06:18:37 +00003272**
mihailimebe796c2008-06-21 20:11:17 +00003273** The second parameter is the name of the SQL function to be created or
drhd68eee02009-12-11 03:44:18 +00003274** redefined. ^The length of the name is limited to 255 bytes, exclusive of
mihailimebe796c2008-06-21 20:11:17 +00003275** the zero-terminator. Note that the name length limit is in bytes, not
drhd68eee02009-12-11 03:44:18 +00003276** characters. ^Any attempt to create a function with a longer name
mihailimebe796c2008-06-21 20:11:17 +00003277** will result in [SQLITE_ERROR] being returned.
drh6ed48bf2007-06-14 20:57:18 +00003278**
drhd68eee02009-12-11 03:44:18 +00003279** ^The third parameter (nArg)
drhc8075422008-09-10 13:09:23 +00003280** is the number of arguments that the SQL function or
drhd68eee02009-12-11 03:44:18 +00003281** aggregate takes. ^If this parameter is -1, then the SQL function or
drh97602f82009-05-24 11:07:49 +00003282** aggregate may take any number of arguments between 0 and the limit
3283** set by [sqlite3_limit]([SQLITE_LIMIT_FUNCTION_ARG]). If the third
drh09943b52009-05-24 21:59:27 +00003284** parameter is less than -1 or greater than 127 then the behavior is
3285** undefined.
danielk197765904932004-05-26 06:18:37 +00003286**
mihailimebe796c2008-06-21 20:11:17 +00003287** The fourth parameter, eTextRep, specifies what
drh6ed48bf2007-06-14 20:57:18 +00003288** [SQLITE_UTF8 | text encoding] this SQL function prefers for
3289** its parameters. Any SQL function implementation should be able to work
3290** work with UTF-8, UTF-16le, or UTF-16be. But some implementations may be
drhd68eee02009-12-11 03:44:18 +00003291** more efficient with one encoding than another. ^An application may
drh6d2069d2007-08-14 01:58:53 +00003292** invoke sqlite3_create_function() or sqlite3_create_function16() multiple
drh6ed48bf2007-06-14 20:57:18 +00003293** times with the same function but with different values of eTextRep.
drhd68eee02009-12-11 03:44:18 +00003294** ^When multiple implementations of the same function are available, SQLite
drh6ed48bf2007-06-14 20:57:18 +00003295** will pick the one that involves the least amount of data conversion.
mihailimebe796c2008-06-21 20:11:17 +00003296** If there is only a single implementation which does not care what text
3297** encoding is used, then the fourth argument should be [SQLITE_ANY].
drh6ed48bf2007-06-14 20:57:18 +00003298**
drhd68eee02009-12-11 03:44:18 +00003299** ^(The fifth parameter is an arbitrary pointer. The implementation of the
3300** function can gain access to this pointer using [sqlite3_user_data()].)^
danielk1977d02eb1f2004-06-06 09:44:03 +00003301**
danielk197765904932004-05-26 06:18:37 +00003302** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
mihailimebe796c2008-06-21 20:11:17 +00003303** pointers to C-language functions that implement the SQL function or
drhd68eee02009-12-11 03:44:18 +00003304** aggregate. ^A scalar SQL function requires an implementation of the xFunc
3305** callback only; NULL pointers should be passed as the xStep and xFinal
3306** parameters. ^An aggregate SQL function requires an implementation of xStep
3307** and xFinal and NULL should be passed for xFunc. ^To delete an existing
mihailimebe796c2008-06-21 20:11:17 +00003308** SQL function or aggregate, pass NULL for all three function callbacks.
drh6ed48bf2007-06-14 20:57:18 +00003309**
drhd68eee02009-12-11 03:44:18 +00003310** ^It is permitted to register multiple implementations of the same
drh6ed48bf2007-06-14 20:57:18 +00003311** functions with the same name but with either differing numbers of
drhd68eee02009-12-11 03:44:18 +00003312** arguments or differing preferred text encodings. ^SQLite will use
drh6aa5f152009-08-19 15:57:07 +00003313** the implementation that most closely matches the way in which the
drhd68eee02009-12-11 03:44:18 +00003314** SQL function is used. ^A function implementation with a non-negative
drhc8075422008-09-10 13:09:23 +00003315** nArg parameter is a better match than a function implementation with
drhd68eee02009-12-11 03:44:18 +00003316** a negative nArg. ^A function where the preferred text encoding
drhc8075422008-09-10 13:09:23 +00003317** matches the database encoding is a better
3318** match than a function where the encoding is different.
drhd68eee02009-12-11 03:44:18 +00003319** ^A function where the encoding difference is between UTF16le and UTF16be
drhc8075422008-09-10 13:09:23 +00003320** is a closer match than a function where the encoding difference is
3321** between UTF8 and UTF16.
3322**
drhd68eee02009-12-11 03:44:18 +00003323** ^Built-in functions may be overloaded by new application-defined functions.
3324** ^The first application-defined function with a given name overrides all
drhc8075422008-09-10 13:09:23 +00003325** built-in functions in the same [database connection] with the same name.
drhd68eee02009-12-11 03:44:18 +00003326** ^Subsequent application-defined functions of the same name only override
drhc8075422008-09-10 13:09:23 +00003327** prior application-defined functions that are an exact match for the
3328** number of parameters and preferred encoding.
3329**
drhd68eee02009-12-11 03:44:18 +00003330** ^An application-defined function is permitted to call other
drhc8075422008-09-10 13:09:23 +00003331** SQLite interfaces. However, such calls must not
3332** close the database connection nor finalize or reset the prepared
3333** statement in which the function is running.
danielk197765904932004-05-26 06:18:37 +00003334*/
3335int sqlite3_create_function(
drh33c1be32008-01-30 16:16:14 +00003336 sqlite3 *db,
danielk197765904932004-05-26 06:18:37 +00003337 const char *zFunctionName,
3338 int nArg,
3339 int eTextRep,
drh33c1be32008-01-30 16:16:14 +00003340 void *pApp,
danielk197765904932004-05-26 06:18:37 +00003341 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
3342 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
3343 void (*xFinal)(sqlite3_context*)
3344);
3345int sqlite3_create_function16(
drh33c1be32008-01-30 16:16:14 +00003346 sqlite3 *db,
danielk197765904932004-05-26 06:18:37 +00003347 const void *zFunctionName,
3348 int nArg,
3349 int eTextRep,
drh33c1be32008-01-30 16:16:14 +00003350 void *pApp,
danielk197765904932004-05-26 06:18:37 +00003351 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
3352 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
3353 void (*xFinal)(sqlite3_context*)
3354);
3355
3356/*
drhd68eee02009-12-11 03:44:18 +00003357** CAPI3REF: Text Encodings
drh6ed48bf2007-06-14 20:57:18 +00003358**
3359** These constant define integer codes that represent the various
3360** text encodings supported by SQLite.
danielk197765904932004-05-26 06:18:37 +00003361*/
drh6ed48bf2007-06-14 20:57:18 +00003362#define SQLITE_UTF8 1
3363#define SQLITE_UTF16LE 2
3364#define SQLITE_UTF16BE 3
3365#define SQLITE_UTF16 4 /* Use native byte order */
3366#define SQLITE_ANY 5 /* sqlite3_create_function only */
3367#define SQLITE_UTF16_ALIGNED 8 /* sqlite3_create_collation only */
danielk197765904932004-05-26 06:18:37 +00003368
danielk19770ffba6b2004-05-24 09:10:10 +00003369/*
drhd5a68d32008-08-04 13:44:57 +00003370** CAPI3REF: Deprecated Functions
3371** DEPRECATED
drh6ed48bf2007-06-14 20:57:18 +00003372**
drhd5a68d32008-08-04 13:44:57 +00003373** These functions are [deprecated]. In order to maintain
3374** backwards compatibility with older code, these functions continue
3375** to be supported. However, new applications should avoid
drh6ed48bf2007-06-14 20:57:18 +00003376** the use of these functions. To help encourage people to avoid
shane7ba429a2008-11-10 17:08:49 +00003377** using these functions, we are not going to tell you what they do.
drh6ed48bf2007-06-14 20:57:18 +00003378*/
shaneeec556d2008-10-12 00:27:53 +00003379#ifndef SQLITE_OMIT_DEPRECATED
shanea79c3cc2008-08-11 17:27:01 +00003380SQLITE_DEPRECATED int sqlite3_aggregate_count(sqlite3_context*);
3381SQLITE_DEPRECATED int sqlite3_expired(sqlite3_stmt*);
3382SQLITE_DEPRECATED int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*);
3383SQLITE_DEPRECATED int sqlite3_global_recover(void);
3384SQLITE_DEPRECATED void sqlite3_thread_cleanup(void);
3385SQLITE_DEPRECATED int sqlite3_memory_alarm(void(*)(void*,sqlite3_int64,int),void*,sqlite3_int64);
shaneeec556d2008-10-12 00:27:53 +00003386#endif
drh6ed48bf2007-06-14 20:57:18 +00003387
3388/*
drhd68eee02009-12-11 03:44:18 +00003389** CAPI3REF: Obtaining SQL Function Parameter Values
drh6ed48bf2007-06-14 20:57:18 +00003390**
3391** The C-language implementation of SQL functions and aggregates uses
3392** this set of interface routines to access the parameter values on
3393** the function or aggregate.
3394**
3395** The xFunc (for scalar functions) or xStep (for aggregates) parameters
3396** to [sqlite3_create_function()] and [sqlite3_create_function16()]
3397** define callbacks that implement the SQL functions and aggregates.
3398** The 4th parameter to these callbacks is an array of pointers to
drhaa28e142008-03-18 13:47:20 +00003399** [protected sqlite3_value] objects. There is one [sqlite3_value] object for
drh6ed48bf2007-06-14 20:57:18 +00003400** each parameter to the SQL function. These routines are used to
3401** extract values from the [sqlite3_value] objects.
3402**
drhaa28e142008-03-18 13:47:20 +00003403** These routines work only with [protected sqlite3_value] objects.
3404** Any attempt to use these routines on an [unprotected sqlite3_value]
3405** object results in undefined behavior.
3406**
drhd68eee02009-12-11 03:44:18 +00003407** ^These routines work just like the corresponding [column access functions]
mihailim1c492652008-06-21 18:02:16 +00003408** except that these routines take a single [protected sqlite3_value] object
3409** pointer instead of a [sqlite3_stmt*] pointer and an integer column number.
drh6ed48bf2007-06-14 20:57:18 +00003410**
drhd68eee02009-12-11 03:44:18 +00003411** ^The sqlite3_value_text16() interface extracts a UTF-16 string
3412** in the native byte-order of the host machine. ^The
drh6ed48bf2007-06-14 20:57:18 +00003413** sqlite3_value_text16be() and sqlite3_value_text16le() interfaces
mihailimebe796c2008-06-21 20:11:17 +00003414** extract UTF-16 strings as big-endian and little-endian respectively.
drh6ed48bf2007-06-14 20:57:18 +00003415**
drhd68eee02009-12-11 03:44:18 +00003416** ^(The sqlite3_value_numeric_type() interface attempts to apply
drh6ed48bf2007-06-14 20:57:18 +00003417** numeric affinity to the value. This means that an attempt is
3418** made to convert the value to an integer or floating point. If
drhf5befa02007-12-06 02:42:07 +00003419** such a conversion is possible without loss of information (in other
mihailimebe796c2008-06-21 20:11:17 +00003420** words, if the value is a string that looks like a number)
3421** then the conversion is performed. Otherwise no conversion occurs.
drhd68eee02009-12-11 03:44:18 +00003422** The [SQLITE_INTEGER | datatype] after conversion is returned.)^
drh6ed48bf2007-06-14 20:57:18 +00003423**
mihailimebe796c2008-06-21 20:11:17 +00003424** Please pay particular attention to the fact that the pointer returned
3425** from [sqlite3_value_blob()], [sqlite3_value_text()], or
drh6ed48bf2007-06-14 20:57:18 +00003426** [sqlite3_value_text16()] can be invalidated by a subsequent call to
drh6d2069d2007-08-14 01:58:53 +00003427** [sqlite3_value_bytes()], [sqlite3_value_bytes16()], [sqlite3_value_text()],
mihailimebe796c2008-06-21 20:11:17 +00003428** or [sqlite3_value_text16()].
drhe53831d2007-08-17 01:14:38 +00003429**
3430** These routines must be called from the same thread as
drhaa28e142008-03-18 13:47:20 +00003431** the SQL function that supplied the [sqlite3_value*] parameters.
danielk19770ffba6b2004-05-24 09:10:10 +00003432*/
drhf4479502004-05-27 03:12:53 +00003433const void *sqlite3_value_blob(sqlite3_value*);
3434int sqlite3_value_bytes(sqlite3_value*);
3435int sqlite3_value_bytes16(sqlite3_value*);
3436double sqlite3_value_double(sqlite3_value*);
3437int sqlite3_value_int(sqlite3_value*);
drh6d2069d2007-08-14 01:58:53 +00003438sqlite3_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +00003439const unsigned char *sqlite3_value_text(sqlite3_value*);
3440const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +00003441const void *sqlite3_value_text16le(sqlite3_value*);
3442const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +00003443int sqlite3_value_type(sqlite3_value*);
drh29d72102006-02-09 22:13:41 +00003444int sqlite3_value_numeric_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +00003445
3446/*
drhd68eee02009-12-11 03:44:18 +00003447** CAPI3REF: Obtain Aggregate Function Context
drh6ed48bf2007-06-14 20:57:18 +00003448**
drh9b8d0272010-08-09 15:44:21 +00003449** Implementations of aggregate SQL functions use this
drhd68eee02009-12-11 03:44:18 +00003450** routine to allocate memory for storing their state.
mihailimebe796c2008-06-21 20:11:17 +00003451**
drhd68eee02009-12-11 03:44:18 +00003452** ^The first time the sqlite3_aggregate_context(C,N) routine is called
3453** for a particular aggregate function, SQLite
3454** allocates N of memory, zeroes out that memory, and returns a pointer
3455** to the new memory. ^On second and subsequent calls to
3456** sqlite3_aggregate_context() for the same aggregate function instance,
3457** the same buffer is returned. Sqlite3_aggregate_context() is normally
3458** called once for each invocation of the xStep callback and then one
3459** last time when the xFinal callback is invoked. ^(When no rows match
3460** an aggregate query, the xStep() callback of the aggregate function
3461** implementation is never called and xFinal() is called exactly once.
3462** In those cases, sqlite3_aggregate_context() might be called for the
3463** first time from within xFinal().)^
danielk19770ae8b832004-05-25 12:05:56 +00003464**
drhd68eee02009-12-11 03:44:18 +00003465** ^The sqlite3_aggregate_context(C,N) routine returns a NULL pointer if N is
3466** less than or equal to zero or if a memory allocate error occurs.
drh6ed48bf2007-06-14 20:57:18 +00003467**
drhd68eee02009-12-11 03:44:18 +00003468** ^(The amount of space allocated by sqlite3_aggregate_context(C,N) is
3469** determined by the N parameter on first successful call. Changing the
3470** value of N in subsequent call to sqlite3_aggregate_context() within
3471** the same aggregate function instance will not resize the memory
3472** allocation.)^
3473**
3474** ^SQLite automatically frees the memory allocated by
3475** sqlite3_aggregate_context() when the aggregate query concludes.
3476**
3477** The first parameter must be a copy of the
mihailimebe796c2008-06-21 20:11:17 +00003478** [sqlite3_context | SQL function context] that is the first parameter
drhd68eee02009-12-11 03:44:18 +00003479** to the xStep or xFinal callback routine that implements the aggregate
3480** function.
drhe53831d2007-08-17 01:14:38 +00003481**
3482** This routine must be called from the same thread in which
drh605264d2007-08-21 15:13:19 +00003483** the aggregate SQL function is running.
danielk19770ae8b832004-05-25 12:05:56 +00003484*/
drh4f26d6c2004-05-26 23:25:30 +00003485void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +00003486
3487/*
drhd68eee02009-12-11 03:44:18 +00003488** CAPI3REF: User Data For Functions
drh6ed48bf2007-06-14 20:57:18 +00003489**
drhd68eee02009-12-11 03:44:18 +00003490** ^The sqlite3_user_data() interface returns a copy of
drhf5befa02007-12-06 02:42:07 +00003491** the pointer that was the pUserData parameter (the 5th parameter)
shane26b34032008-05-23 17:21:09 +00003492** of the [sqlite3_create_function()]
drhf5befa02007-12-06 02:42:07 +00003493** and [sqlite3_create_function16()] routines that originally
drhfa4a4b92008-03-19 21:45:51 +00003494** registered the application defined function.
3495**
drhd68eee02009-12-11 03:44:18 +00003496** This routine must be called from the same thread in which
3497** the application-defined function is running.
3498*/
3499void *sqlite3_user_data(sqlite3_context*);
3500
3501/*
3502** CAPI3REF: Database Connection For Functions
3503**
3504** ^The sqlite3_context_db_handle() interface returns a copy of
3505** the pointer to the [database connection] (the 1st parameter)
3506** of the [sqlite3_create_function()]
3507** and [sqlite3_create_function16()] routines that originally
3508** registered the application defined function.
drhfa4a4b92008-03-19 21:45:51 +00003509*/
3510sqlite3 *sqlite3_context_db_handle(sqlite3_context*);
3511
3512/*
drhd68eee02009-12-11 03:44:18 +00003513** CAPI3REF: Function Auxiliary Data
drh6ed48bf2007-06-14 20:57:18 +00003514**
3515** The following two functions may be used by scalar SQL functions to
mihailimebe796c2008-06-21 20:11:17 +00003516** associate metadata with argument values. If the same value is passed to
drh6ed48bf2007-06-14 20:57:18 +00003517** multiple invocations of the same SQL function during query execution, under
mihailimebe796c2008-06-21 20:11:17 +00003518** some circumstances the associated metadata may be preserved. This may
danielk1977682f68b2004-06-05 10:22:17 +00003519** be used, for example, to add a regular-expression matching scalar
3520** function. The compiled version of the regular expression is stored as
mihailimebe796c2008-06-21 20:11:17 +00003521** metadata associated with the SQL value passed as the regular expression
drh6ed48bf2007-06-14 20:57:18 +00003522** pattern. The compiled regular expression can be reused on multiple
3523** invocations of the same function so that the original pattern string
3524** does not need to be recompiled on each invocation.
danielk1977682f68b2004-06-05 10:22:17 +00003525**
drhd68eee02009-12-11 03:44:18 +00003526** ^The sqlite3_get_auxdata() interface returns a pointer to the metadata
drhf5befa02007-12-06 02:42:07 +00003527** associated by the sqlite3_set_auxdata() function with the Nth argument
drhd68eee02009-12-11 03:44:18 +00003528** value to the application-defined function. ^If no metadata has been ever
mihailimebe796c2008-06-21 20:11:17 +00003529** been set for the Nth argument of the function, or if the corresponding
3530** function parameter has changed since the meta-data was set,
3531** then sqlite3_get_auxdata() returns a NULL pointer.
danielk1977682f68b2004-06-05 10:22:17 +00003532**
drhd68eee02009-12-11 03:44:18 +00003533** ^The sqlite3_set_auxdata() interface saves the metadata
mihailimebe796c2008-06-21 20:11:17 +00003534** pointed to by its 3rd parameter as the metadata for the N-th
drhafc91042008-02-21 02:09:45 +00003535** argument of the application-defined function. Subsequent
drhf5befa02007-12-06 02:42:07 +00003536** calls to sqlite3_get_auxdata() might return this data, if it has
mihailimebe796c2008-06-21 20:11:17 +00003537** not been destroyed.
drhd68eee02009-12-11 03:44:18 +00003538** ^If it is not NULL, SQLite will invoke the destructor
drhf5befa02007-12-06 02:42:07 +00003539** function given by the 4th parameter to sqlite3_set_auxdata() on
mihailimebe796c2008-06-21 20:11:17 +00003540** the metadata when the corresponding function parameter changes
drhafc91042008-02-21 02:09:45 +00003541** or when the SQL statement completes, whichever comes first.
3542**
mihailimebe796c2008-06-21 20:11:17 +00003543** SQLite is free to call the destructor and drop metadata on any
drhd68eee02009-12-11 03:44:18 +00003544** parameter of any function at any time. ^The only guarantee is that
mihailimebe796c2008-06-21 20:11:17 +00003545** the destructor will be called before the metadata is dropped.
danielk1977682f68b2004-06-05 10:22:17 +00003546**
drhd68eee02009-12-11 03:44:18 +00003547** ^(In practice, metadata is preserved between function calls for
danielk1977682f68b2004-06-05 10:22:17 +00003548** expressions that are constant at compile time. This includes literal
drhd68eee02009-12-11 03:44:18 +00003549** values and [parameters].)^
drhe53831d2007-08-17 01:14:38 +00003550**
drhb21c8cd2007-08-21 19:33:56 +00003551** These routines must be called from the same thread in which
3552** the SQL function is running.
danielk1977682f68b2004-06-05 10:22:17 +00003553*/
drhf5befa02007-12-06 02:42:07 +00003554void *sqlite3_get_auxdata(sqlite3_context*, int N);
3555void sqlite3_set_auxdata(sqlite3_context*, int N, void*, void (*)(void*));
danielk1977682f68b2004-06-05 10:22:17 +00003556
drha2854222004-06-17 19:04:17 +00003557
3558/*
drhd68eee02009-12-11 03:44:18 +00003559** CAPI3REF: Constants Defining Special Destructor Behavior
drh6ed48bf2007-06-14 20:57:18 +00003560**
mihailimebe796c2008-06-21 20:11:17 +00003561** These are special values for the destructor that is passed in as the
drhd68eee02009-12-11 03:44:18 +00003562** final argument to routines like [sqlite3_result_blob()]. ^If the destructor
drha2854222004-06-17 19:04:17 +00003563** argument is SQLITE_STATIC, it means that the content pointer is constant
drhd68eee02009-12-11 03:44:18 +00003564** and will never change. It does not need to be destroyed. ^The
drha2854222004-06-17 19:04:17 +00003565** SQLITE_TRANSIENT value means that the content will likely change in
3566** the near future and that SQLite should make its own private copy of
3567** the content before returning.
drh6c9121a2007-01-26 00:51:43 +00003568**
3569** The typedef is necessary to work around problems in certain
3570** C++ compilers. See ticket #2191.
drha2854222004-06-17 19:04:17 +00003571*/
drh6c9121a2007-01-26 00:51:43 +00003572typedef void (*sqlite3_destructor_type)(void*);
3573#define SQLITE_STATIC ((sqlite3_destructor_type)0)
3574#define SQLITE_TRANSIENT ((sqlite3_destructor_type)-1)
danielk1977d8123362004-06-12 09:25:12 +00003575
danielk1977682f68b2004-06-05 10:22:17 +00003576/*
drhd68eee02009-12-11 03:44:18 +00003577** CAPI3REF: Setting The Result Of An SQL Function
drh6ed48bf2007-06-14 20:57:18 +00003578**
3579** These routines are used by the xFunc or xFinal callbacks that
3580** implement SQL functions and aggregates. See
3581** [sqlite3_create_function()] and [sqlite3_create_function16()]
3582** for additional information.
3583**
mihailimebe796c2008-06-21 20:11:17 +00003584** These functions work very much like the [parameter binding] family of
3585** functions used to bind values to host parameters in prepared statements.
3586** Refer to the [SQL parameter] documentation for additional information.
drh6ed48bf2007-06-14 20:57:18 +00003587**
drhd68eee02009-12-11 03:44:18 +00003588** ^The sqlite3_result_blob() interface sets the result from
mihailimebe796c2008-06-21 20:11:17 +00003589** an application-defined function to be the BLOB whose content is pointed
drhf5befa02007-12-06 02:42:07 +00003590** to by the second parameter and which is N bytes long where N is the
mihailimebe796c2008-06-21 20:11:17 +00003591** third parameter.
3592**
drhd68eee02009-12-11 03:44:18 +00003593** ^The sqlite3_result_zeroblob() interfaces set the result of
mihailimebe796c2008-06-21 20:11:17 +00003594** the application-defined function to be a BLOB containing all zero
drhf5befa02007-12-06 02:42:07 +00003595** bytes and N bytes in size, where N is the value of the 2nd parameter.
drh6ed48bf2007-06-14 20:57:18 +00003596**
drhd68eee02009-12-11 03:44:18 +00003597** ^The sqlite3_result_double() interface sets the result from
mihailimebe796c2008-06-21 20:11:17 +00003598** an application-defined function to be a floating point value specified
drhf5befa02007-12-06 02:42:07 +00003599** by its 2nd argument.
drhe53831d2007-08-17 01:14:38 +00003600**
drhd68eee02009-12-11 03:44:18 +00003601** ^The sqlite3_result_error() and sqlite3_result_error16() functions
drhf5befa02007-12-06 02:42:07 +00003602** cause the implemented SQL function to throw an exception.
drhd68eee02009-12-11 03:44:18 +00003603** ^SQLite uses the string pointed to by the
drhf5befa02007-12-06 02:42:07 +00003604** 2nd parameter of sqlite3_result_error() or sqlite3_result_error16()
drhd68eee02009-12-11 03:44:18 +00003605** as the text of an error message. ^SQLite interprets the error
3606** message string from sqlite3_result_error() as UTF-8. ^SQLite
mihailimebe796c2008-06-21 20:11:17 +00003607** interprets the string from sqlite3_result_error16() as UTF-16 in native
drhd68eee02009-12-11 03:44:18 +00003608** byte order. ^If the third parameter to sqlite3_result_error()
drhf5befa02007-12-06 02:42:07 +00003609** or sqlite3_result_error16() is negative then SQLite takes as the error
3610** message all text up through the first zero character.
drhd68eee02009-12-11 03:44:18 +00003611** ^If the third parameter to sqlite3_result_error() or
drhf5befa02007-12-06 02:42:07 +00003612** sqlite3_result_error16() is non-negative then SQLite takes that many
3613** bytes (not characters) from the 2nd parameter as the error message.
drhd68eee02009-12-11 03:44:18 +00003614** ^The sqlite3_result_error() and sqlite3_result_error16()
mihailimebe796c2008-06-21 20:11:17 +00003615** routines make a private copy of the error message text before
drhafc91042008-02-21 02:09:45 +00003616** they return. Hence, the calling function can deallocate or
drhf5befa02007-12-06 02:42:07 +00003617** modify the text after they return without harm.
drhd68eee02009-12-11 03:44:18 +00003618** ^The sqlite3_result_error_code() function changes the error code
3619** returned by SQLite as a result of an error in a function. ^By default,
3620** the error code is SQLITE_ERROR. ^A subsequent call to sqlite3_result_error()
drh00e087b2008-04-10 17:14:07 +00003621** or sqlite3_result_error16() resets the error code to SQLITE_ERROR.
drhf5befa02007-12-06 02:42:07 +00003622**
drhd68eee02009-12-11 03:44:18 +00003623** ^The sqlite3_result_toobig() interface causes SQLite to throw an error
drhdf6473a2009-12-13 22:20:08 +00003624** indicating that a string or BLOB is too long to represent.
mihailimebe796c2008-06-21 20:11:17 +00003625**
drhd68eee02009-12-11 03:44:18 +00003626** ^The sqlite3_result_nomem() interface causes SQLite to throw an error
mihailimebe796c2008-06-21 20:11:17 +00003627** indicating that a memory allocation failed.
drhf5befa02007-12-06 02:42:07 +00003628**
drhd68eee02009-12-11 03:44:18 +00003629** ^The sqlite3_result_int() interface sets the return value
drhf5befa02007-12-06 02:42:07 +00003630** of the application-defined function to be the 32-bit signed integer
3631** value given in the 2nd argument.
drhd68eee02009-12-11 03:44:18 +00003632** ^The sqlite3_result_int64() interface sets the return value
drhf5befa02007-12-06 02:42:07 +00003633** of the application-defined function to be the 64-bit signed integer
3634** value given in the 2nd argument.
3635**
drhd68eee02009-12-11 03:44:18 +00003636** ^The sqlite3_result_null() interface sets the return value
drhf5befa02007-12-06 02:42:07 +00003637** of the application-defined function to be NULL.
3638**
drhd68eee02009-12-11 03:44:18 +00003639** ^The sqlite3_result_text(), sqlite3_result_text16(),
drhf5befa02007-12-06 02:42:07 +00003640** sqlite3_result_text16le(), and sqlite3_result_text16be() interfaces
3641** set the return value of the application-defined function to be
3642** a text string which is represented as UTF-8, UTF-16 native byte order,
3643** UTF-16 little endian, or UTF-16 big endian, respectively.
drhd68eee02009-12-11 03:44:18 +00003644** ^SQLite takes the text result from the application from
drhf5befa02007-12-06 02:42:07 +00003645** the 2nd parameter of the sqlite3_result_text* interfaces.
drhd68eee02009-12-11 03:44:18 +00003646** ^If the 3rd parameter to the sqlite3_result_text* interfaces
mihailimebe796c2008-06-21 20:11:17 +00003647** is negative, then SQLite takes result text from the 2nd parameter
drhf5befa02007-12-06 02:42:07 +00003648** through the first zero character.
drhd68eee02009-12-11 03:44:18 +00003649** ^If the 3rd parameter to the sqlite3_result_text* interfaces
drhf5befa02007-12-06 02:42:07 +00003650** is non-negative, then as many bytes (not characters) of the text
3651** pointed to by the 2nd parameter are taken as the application-defined
3652** function result.
drhd68eee02009-12-11 03:44:18 +00003653** ^If the 4th parameter to the sqlite3_result_text* interfaces
drhf5befa02007-12-06 02:42:07 +00003654** or sqlite3_result_blob is a non-NULL pointer, then SQLite calls that
mihailimebe796c2008-06-21 20:11:17 +00003655** function as the destructor on the text or BLOB result when it has
drhf5befa02007-12-06 02:42:07 +00003656** finished using that result.
drhd68eee02009-12-11 03:44:18 +00003657** ^If the 4th parameter to the sqlite3_result_text* interfaces or to
mihailimebe796c2008-06-21 20:11:17 +00003658** sqlite3_result_blob is the special constant SQLITE_STATIC, then SQLite
3659** assumes that the text or BLOB result is in constant space and does not
drh9e42f8a2009-08-13 20:15:29 +00003660** copy the content of the parameter nor call a destructor on the content
3661** when it has finished using that result.
drhd68eee02009-12-11 03:44:18 +00003662** ^If the 4th parameter to the sqlite3_result_text* interfaces
drhf5befa02007-12-06 02:42:07 +00003663** or sqlite3_result_blob is the special constant SQLITE_TRANSIENT
3664** then SQLite makes a copy of the result into space obtained from
3665** from [sqlite3_malloc()] before it returns.
3666**
drhd68eee02009-12-11 03:44:18 +00003667** ^The sqlite3_result_value() interface sets the result of
drhaa28e142008-03-18 13:47:20 +00003668** the application-defined function to be a copy the
drhd68eee02009-12-11 03:44:18 +00003669** [unprotected sqlite3_value] object specified by the 2nd parameter. ^The
drhf5befa02007-12-06 02:42:07 +00003670** sqlite3_result_value() interface makes a copy of the [sqlite3_value]
mihailimebe796c2008-06-21 20:11:17 +00003671** so that the [sqlite3_value] specified in the parameter may change or
drhf5befa02007-12-06 02:42:07 +00003672** be deallocated after sqlite3_result_value() returns without harm.
drhd68eee02009-12-11 03:44:18 +00003673** ^A [protected sqlite3_value] object may always be used where an
drhaa28e142008-03-18 13:47:20 +00003674** [unprotected sqlite3_value] object is required, so either
3675** kind of [sqlite3_value] object can be used with this interface.
drhf5befa02007-12-06 02:42:07 +00003676**
mihailimebe796c2008-06-21 20:11:17 +00003677** If these routines are called from within the different thread
shane26b34032008-05-23 17:21:09 +00003678** than the one containing the application-defined function that received
drhf5befa02007-12-06 02:42:07 +00003679** the [sqlite3_context] pointer, the results are undefined.
danielk19777e18c252004-05-25 11:47:24 +00003680*/
danielk1977d8123362004-06-12 09:25:12 +00003681void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00003682void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +00003683void sqlite3_result_error(sqlite3_context*, const char*, int);
3684void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh6ed48bf2007-06-14 20:57:18 +00003685void sqlite3_result_error_toobig(sqlite3_context*);
danielk1977a1644fd2007-08-29 12:31:25 +00003686void sqlite3_result_error_nomem(sqlite3_context*);
drh69544ec2008-02-06 14:11:34 +00003687void sqlite3_result_error_code(sqlite3_context*, int);
drh4f26d6c2004-05-26 23:25:30 +00003688void sqlite3_result_int(sqlite3_context*, int);
drh6d2069d2007-08-14 01:58:53 +00003689void sqlite3_result_int64(sqlite3_context*, sqlite3_int64);
drh4f26d6c2004-05-26 23:25:30 +00003690void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +00003691void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
3692void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
3693void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
3694void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00003695void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhb026e052007-05-02 01:34:31 +00003696void sqlite3_result_zeroblob(sqlite3_context*, int n);
drhf9b596e2004-05-26 16:54:42 +00003697
drh52619df2004-06-11 17:48:02 +00003698/*
drhd68eee02009-12-11 03:44:18 +00003699** CAPI3REF: Define New Collating Sequences
drh6ed48bf2007-06-14 20:57:18 +00003700**
3701** These functions are used to add new collation sequences to the
mihailimebe796c2008-06-21 20:11:17 +00003702** [database connection] specified as the first argument.
danielk19777cedc8d2004-06-10 10:50:08 +00003703**
drhd68eee02009-12-11 03:44:18 +00003704** ^The name of the new collation sequence is specified as a UTF-8 string
drh6ed48bf2007-06-14 20:57:18 +00003705** for sqlite3_create_collation() and sqlite3_create_collation_v2()
drhd68eee02009-12-11 03:44:18 +00003706** and a UTF-16 string for sqlite3_create_collation16(). ^In all cases
drh6ed48bf2007-06-14 20:57:18 +00003707** the name is passed as the second function argument.
danielk19777cedc8d2004-06-10 10:50:08 +00003708**
drhd68eee02009-12-11 03:44:18 +00003709** ^The third argument may be one of the constants [SQLITE_UTF8],
drh51c7d862009-04-27 18:46:06 +00003710** [SQLITE_UTF16LE], or [SQLITE_UTF16BE], indicating that the user-supplied
danielk19777cedc8d2004-06-10 10:50:08 +00003711** routine expects to be passed pointers to strings encoded using UTF-8,
drhd68eee02009-12-11 03:44:18 +00003712** UTF-16 little-endian, or UTF-16 big-endian, respectively. ^The
drh51c7d862009-04-27 18:46:06 +00003713** third argument might also be [SQLITE_UTF16] to indicate that the routine
3714** expects pointers to be UTF-16 strings in the native byte order, or the
3715** argument can be [SQLITE_UTF16_ALIGNED] if the
drh4145f832007-10-12 18:30:12 +00003716** the routine expects pointers to 16-bit word aligned strings
drh51c7d862009-04-27 18:46:06 +00003717** of UTF-16 in the native byte order.
danielk19777cedc8d2004-06-10 10:50:08 +00003718**
3719** A pointer to the user supplied routine must be passed as the fifth
drhd68eee02009-12-11 03:44:18 +00003720** argument. ^If it is NULL, this is the same as deleting the collation
drh9b8d0272010-08-09 15:44:21 +00003721** sequence (so that SQLite cannot call it any more).
drhd68eee02009-12-11 03:44:18 +00003722** ^Each time the application supplied function is invoked, it is passed
mihailimebe796c2008-06-21 20:11:17 +00003723** as its first parameter a copy of the void* passed as the fourth argument
3724** to sqlite3_create_collation() or sqlite3_create_collation16().
danielk19777cedc8d2004-06-10 10:50:08 +00003725**
drhd68eee02009-12-11 03:44:18 +00003726** ^The remaining arguments to the application-supplied routine are two strings,
drh33c1be32008-01-30 16:16:14 +00003727** each represented by a (length, data) pair and encoded in the encoding
danielk19777cedc8d2004-06-10 10:50:08 +00003728** that was passed as the third argument when the collation sequence was
drhfb434032009-12-11 23:11:26 +00003729** registered. The application defined collation routine should
mihailimebe796c2008-06-21 20:11:17 +00003730** return negative, zero or positive if the first string is less than,
3731** equal to, or greater than the second string. i.e. (STRING1 - STRING2).
drh6ed48bf2007-06-14 20:57:18 +00003732**
drhd68eee02009-12-11 03:44:18 +00003733** ^The sqlite3_create_collation_v2() works like sqlite3_create_collation()
shane26b34032008-05-23 17:21:09 +00003734** except that it takes an extra argument which is a destructor for
drhd68eee02009-12-11 03:44:18 +00003735** the collation. ^The destructor is called when the collation is
drh6ed48bf2007-06-14 20:57:18 +00003736** destroyed and is passed a copy of the fourth parameter void* pointer
drhf5befa02007-12-06 02:42:07 +00003737** of the sqlite3_create_collation_v2().
drhd68eee02009-12-11 03:44:18 +00003738** ^Collations are destroyed when they are overridden by later calls to the
mihailimebe796c2008-06-21 20:11:17 +00003739** collation creation functions or when the [database connection] is closed
3740** using [sqlite3_close()].
drhafc91042008-02-21 02:09:45 +00003741**
drh51c7d862009-04-27 18:46:06 +00003742** See also: [sqlite3_collation_needed()] and [sqlite3_collation_needed16()].
danielk19777cedc8d2004-06-10 10:50:08 +00003743*/
danielk19770202b292004-06-09 09:55:16 +00003744int sqlite3_create_collation(
3745 sqlite3*,
3746 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00003747 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00003748 void*,
3749 int(*xCompare)(void*,int,const void*,int,const void*)
3750);
drh6ed48bf2007-06-14 20:57:18 +00003751int sqlite3_create_collation_v2(
3752 sqlite3*,
3753 const char *zName,
3754 int eTextRep,
3755 void*,
3756 int(*xCompare)(void*,int,const void*,int,const void*),
3757 void(*xDestroy)(void*)
3758);
danielk19770202b292004-06-09 09:55:16 +00003759int sqlite3_create_collation16(
3760 sqlite3*,
mihailimbda2e622008-06-23 11:23:14 +00003761 const void *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00003762 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00003763 void*,
3764 int(*xCompare)(void*,int,const void*,int,const void*)
3765);
3766
danielk19777cedc8d2004-06-10 10:50:08 +00003767/*
drhfb434032009-12-11 23:11:26 +00003768** CAPI3REF: Collation Needed Callbacks
danielk1977a393c032007-05-07 14:58:53 +00003769**
drhd68eee02009-12-11 03:44:18 +00003770** ^To avoid having to register all collation sequences before a database
danielk19777cedc8d2004-06-10 10:50:08 +00003771** can be used, a single callback function may be registered with the
drh9be37f62009-12-12 23:57:36 +00003772** [database connection] to be invoked whenever an undefined collation
mihailimdc884822008-06-22 08:58:50 +00003773** sequence is required.
danielk19777cedc8d2004-06-10 10:50:08 +00003774**
drhd68eee02009-12-11 03:44:18 +00003775** ^If the function is registered using the sqlite3_collation_needed() API,
danielk19777cedc8d2004-06-10 10:50:08 +00003776** then it is passed the names of undefined collation sequences as strings
drhd68eee02009-12-11 03:44:18 +00003777** encoded in UTF-8. ^If sqlite3_collation_needed16() is used,
mihailimdc884822008-06-22 08:58:50 +00003778** the names are passed as UTF-16 in machine native byte order.
drh9be37f62009-12-12 23:57:36 +00003779** ^A call to either function replaces the existing collation-needed callback.
danielk19777cedc8d2004-06-10 10:50:08 +00003780**
drhd68eee02009-12-11 03:44:18 +00003781** ^(When the callback is invoked, the first argument passed is a copy
danielk19777cedc8d2004-06-10 10:50:08 +00003782** of the second argument to sqlite3_collation_needed() or
drhafc91042008-02-21 02:09:45 +00003783** sqlite3_collation_needed16(). The second argument is the database
mihailimdc884822008-06-22 08:58:50 +00003784** connection. The third argument is one of [SQLITE_UTF8], [SQLITE_UTF16BE],
3785** or [SQLITE_UTF16LE], indicating the most desirable form of the collation
3786** sequence function required. The fourth parameter is the name of the
drhd68eee02009-12-11 03:44:18 +00003787** required collation sequence.)^
danielk19777cedc8d2004-06-10 10:50:08 +00003788**
drh6ed48bf2007-06-14 20:57:18 +00003789** The callback function should register the desired collation using
3790** [sqlite3_create_collation()], [sqlite3_create_collation16()], or
3791** [sqlite3_create_collation_v2()].
danielk19777cedc8d2004-06-10 10:50:08 +00003792*/
3793int sqlite3_collation_needed(
3794 sqlite3*,
3795 void*,
3796 void(*)(void*,sqlite3*,int eTextRep,const char*)
3797);
3798int sqlite3_collation_needed16(
3799 sqlite3*,
3800 void*,
3801 void(*)(void*,sqlite3*,int eTextRep,const void*)
3802);
3803
drhd4542142010-03-30 11:57:01 +00003804#ifdef SQLITE_HAS_CODEC
drh2011d5f2004-07-22 02:40:37 +00003805/*
3806** Specify the key for an encrypted database. This routine should be
3807** called right after sqlite3_open().
3808**
3809** The code to implement this API is not available in the public release
3810** of SQLite.
3811*/
3812int sqlite3_key(
3813 sqlite3 *db, /* Database to be rekeyed */
3814 const void *pKey, int nKey /* The key */
3815);
3816
3817/*
3818** Change the key on an open database. If the current database is not
3819** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the
3820** database is decrypted.
3821**
3822** The code to implement this API is not available in the public release
3823** of SQLite.
3824*/
3825int sqlite3_rekey(
3826 sqlite3 *db, /* Database to be rekeyed */
3827 const void *pKey, int nKey /* The new key */
3828);
danielk19770202b292004-06-09 09:55:16 +00003829
drhab3f9fe2004-08-14 17:10:10 +00003830/*
shaneh959dda62010-01-28 19:56:27 +00003831** Specify the activation key for a SEE database. Unless
3832** activated, none of the SEE routines will work.
3833*/
drha7564662010-02-22 19:32:31 +00003834void sqlite3_activate_see(
3835 const char *zPassPhrase /* Activation phrase */
3836);
3837#endif
3838
3839#ifdef SQLITE_ENABLE_CEROD
shaneh959dda62010-01-28 19:56:27 +00003840/*
3841** Specify the activation key for a CEROD database. Unless
3842** activated, none of the CEROD routines will work.
3843*/
drha7564662010-02-22 19:32:31 +00003844void sqlite3_activate_cerod(
3845 const char *zPassPhrase /* Activation phrase */
3846);
shaneh959dda62010-01-28 19:56:27 +00003847#endif
3848
3849/*
drhd68eee02009-12-11 03:44:18 +00003850** CAPI3REF: Suspend Execution For A Short Time
drh6ed48bf2007-06-14 20:57:18 +00003851**
drhd68eee02009-12-11 03:44:18 +00003852** ^The sqlite3_sleep() function causes the current thread to suspend execution
drhfddfa2d2007-12-05 18:05:16 +00003853** for at least a number of milliseconds specified in its parameter.
danielk1977600dd0b2005-01-20 01:14:23 +00003854**
drhd68eee02009-12-11 03:44:18 +00003855** ^If the operating system does not support sleep requests with
mihailimdc884822008-06-22 08:58:50 +00003856** millisecond time resolution, then the time will be rounded up to
drhd68eee02009-12-11 03:44:18 +00003857** the nearest second. ^The number of milliseconds of sleep actually
danielk1977600dd0b2005-01-20 01:14:23 +00003858** requested from the operating system is returned.
drh8bacf972007-08-25 16:21:29 +00003859**
drhd68eee02009-12-11 03:44:18 +00003860** ^SQLite implements this interface by calling the xSleep()
drhafc91042008-02-21 02:09:45 +00003861** method of the default [sqlite3_vfs] object.
danielk1977600dd0b2005-01-20 01:14:23 +00003862*/
3863int sqlite3_sleep(int);
3864
3865/*
drhd68eee02009-12-11 03:44:18 +00003866** CAPI3REF: Name Of The Folder Holding Temporary Files
drhd89bd002005-01-22 03:03:54 +00003867**
drh7a98b852009-12-13 23:03:01 +00003868** ^(If this global variable is made to point to a string which is
shane26b34032008-05-23 17:21:09 +00003869** the name of a folder (a.k.a. directory), then all temporary files
drhd68eee02009-12-11 03:44:18 +00003870** created by SQLite when using a built-in [sqlite3_vfs | VFS]
drh7a98b852009-12-13 23:03:01 +00003871** will be placed in that directory.)^ ^If this variable
mihailimdc884822008-06-22 08:58:50 +00003872** is a NULL pointer, then SQLite performs a search for an appropriate
3873** temporary file directory.
drhab3f9fe2004-08-14 17:10:10 +00003874**
drh1a25f112009-04-06 15:55:03 +00003875** It is not safe to read or modify this variable in more than one
3876** thread at a time. It is not safe to read or modify this variable
3877** if a [database connection] is being used at the same time in a separate
3878** thread.
3879** It is intended that this variable be set once
drh4ff7fa02007-09-01 18:17:21 +00003880** as part of process initialization and before any SQLite interface
drh1a25f112009-04-06 15:55:03 +00003881** routines have been called and that this variable remain unchanged
3882** thereafter.
3883**
drhd68eee02009-12-11 03:44:18 +00003884** ^The [temp_store_directory pragma] may modify this variable and cause
3885** it to point to memory obtained from [sqlite3_malloc]. ^Furthermore,
drh1a25f112009-04-06 15:55:03 +00003886** the [temp_store_directory pragma] always assumes that any string
3887** that this variable points to is held in memory obtained from
3888** [sqlite3_malloc] and the pragma may attempt to free that memory
3889** using [sqlite3_free].
3890** Hence, if this variable is modified directly, either it should be
3891** made NULL or made to point to memory obtained from [sqlite3_malloc]
3892** or else the use of the [temp_store_directory pragma] should be avoided.
drhab3f9fe2004-08-14 17:10:10 +00003893*/
drh73be5012007-08-08 12:11:21 +00003894SQLITE_EXTERN char *sqlite3_temp_directory;
drhab3f9fe2004-08-14 17:10:10 +00003895
danielk19776b456a22005-03-21 04:04:02 +00003896/*
drhd68eee02009-12-11 03:44:18 +00003897** CAPI3REF: Test For Auto-Commit Mode
mihailim15194222008-06-22 09:55:14 +00003898** KEYWORDS: {autocommit mode}
danielk19776b456a22005-03-21 04:04:02 +00003899**
drhd68eee02009-12-11 03:44:18 +00003900** ^The sqlite3_get_autocommit() interface returns non-zero or
drhf5befa02007-12-06 02:42:07 +00003901** zero if the given database connection is or is not in autocommit mode,
drhd68eee02009-12-11 03:44:18 +00003902** respectively. ^Autocommit mode is on by default.
3903** ^Autocommit mode is disabled by a [BEGIN] statement.
3904** ^Autocommit mode is re-enabled by a [COMMIT] or [ROLLBACK].
drhe30f4422007-08-21 16:15:55 +00003905**
drh7c3472a2007-10-03 20:15:28 +00003906** If certain kinds of errors occur on a statement within a multi-statement
mihailimdc884822008-06-22 08:58:50 +00003907** transaction (errors including [SQLITE_FULL], [SQLITE_IOERR],
drh7c3472a2007-10-03 20:15:28 +00003908** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
drh33c1be32008-01-30 16:16:14 +00003909** transaction might be rolled back automatically. The only way to
mihailimdc884822008-06-22 08:58:50 +00003910** find out whether SQLite automatically rolled back the transaction after
drh33c1be32008-01-30 16:16:14 +00003911** an error is to use this function.
drh7c3472a2007-10-03 20:15:28 +00003912**
drh8b39db12009-02-18 18:37:58 +00003913** If another thread changes the autocommit status of the database
3914** connection while this routine is running, then the return value
3915** is undefined.
drh3e1d8e62005-05-26 16:23:34 +00003916*/
3917int sqlite3_get_autocommit(sqlite3*);
3918
drh51942bc2005-06-12 22:01:42 +00003919/*
drhd68eee02009-12-11 03:44:18 +00003920** CAPI3REF: Find The Database Handle Of A Prepared Statement
drh6ed48bf2007-06-14 20:57:18 +00003921**
drhd68eee02009-12-11 03:44:18 +00003922** ^The sqlite3_db_handle interface returns the [database connection] handle
3923** to which a [prepared statement] belongs. ^The [database connection]
3924** returned by sqlite3_db_handle is the same [database connection]
3925** that was the first argument
mihailimdc884822008-06-22 08:58:50 +00003926** to the [sqlite3_prepare_v2()] call (or its variants) that was used to
3927** create the statement in the first place.
drh51942bc2005-06-12 22:01:42 +00003928*/
3929sqlite3 *sqlite3_db_handle(sqlite3_stmt*);
drh3e1d8e62005-05-26 16:23:34 +00003930
drhbb5a9c32008-06-19 02:52:25 +00003931/*
drhd68eee02009-12-11 03:44:18 +00003932** CAPI3REF: Find the next prepared statement
drhbb5a9c32008-06-19 02:52:25 +00003933**
drhd68eee02009-12-11 03:44:18 +00003934** ^This interface returns a pointer to the next [prepared statement] after
3935** pStmt associated with the [database connection] pDb. ^If pStmt is NULL
mihailimdc884822008-06-22 08:58:50 +00003936** then this interface returns a pointer to the first prepared statement
drhd68eee02009-12-11 03:44:18 +00003937** associated with the database connection pDb. ^If no prepared statement
mihailimdc884822008-06-22 08:58:50 +00003938** satisfies the conditions of this routine, it returns NULL.
drhbb5a9c32008-06-19 02:52:25 +00003939**
drh8b39db12009-02-18 18:37:58 +00003940** The [database connection] pointer D in a call to
3941** [sqlite3_next_stmt(D,S)] must refer to an open database
3942** connection and in particular must not be a NULL pointer.
drhbb5a9c32008-06-19 02:52:25 +00003943*/
3944sqlite3_stmt *sqlite3_next_stmt(sqlite3 *pDb, sqlite3_stmt *pStmt);
3945
drhb37df7b2005-10-13 02:09:49 +00003946/*
drhfb434032009-12-11 23:11:26 +00003947** CAPI3REF: Commit And Rollback Notification Callbacks
drh6ed48bf2007-06-14 20:57:18 +00003948**
drhd68eee02009-12-11 03:44:18 +00003949** ^The sqlite3_commit_hook() interface registers a callback
drhabda6112009-05-14 22:37:47 +00003950** function to be invoked whenever a transaction is [COMMIT | committed].
drhd68eee02009-12-11 03:44:18 +00003951** ^Any callback set by a previous call to sqlite3_commit_hook()
drhf5befa02007-12-06 02:42:07 +00003952** for the same database connection is overridden.
drhd68eee02009-12-11 03:44:18 +00003953** ^The sqlite3_rollback_hook() interface registers a callback
drhabda6112009-05-14 22:37:47 +00003954** function to be invoked whenever a transaction is [ROLLBACK | rolled back].
drhd68eee02009-12-11 03:44:18 +00003955** ^Any callback set by a previous call to sqlite3_rollback_hook()
drhf5befa02007-12-06 02:42:07 +00003956** for the same database connection is overridden.
drhd68eee02009-12-11 03:44:18 +00003957** ^The pArg argument is passed through to the callback.
3958** ^If the callback on a commit hook function returns non-zero,
mihailimdc884822008-06-22 08:58:50 +00003959** then the commit is converted into a rollback.
drh6ed48bf2007-06-14 20:57:18 +00003960**
drhd68eee02009-12-11 03:44:18 +00003961** ^The sqlite3_commit_hook(D,C,P) and sqlite3_rollback_hook(D,C,P) functions
3962** return the P argument from the previous call of the same function
3963** on the same [database connection] D, or NULL for
3964** the first call for each function on D.
drh6ed48bf2007-06-14 20:57:18 +00003965**
drhc8075422008-09-10 13:09:23 +00003966** The callback implementation must not do anything that will modify
3967** the database connection that invoked the callback. Any actions
3968** to modify the database connection must be deferred until after the
3969** completion of the [sqlite3_step()] call that triggered the commit
3970** or rollback hook in the first place.
3971** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
3972** database connections for the meaning of "modify" in this paragraph.
3973**
drhd68eee02009-12-11 03:44:18 +00003974** ^Registering a NULL function disables the callback.
drh6ed48bf2007-06-14 20:57:18 +00003975**
drhd68eee02009-12-11 03:44:18 +00003976** ^When the commit hook callback routine returns zero, the [COMMIT]
3977** operation is allowed to continue normally. ^If the commit hook
drhabda6112009-05-14 22:37:47 +00003978** returns non-zero, then the [COMMIT] is converted into a [ROLLBACK].
drhd68eee02009-12-11 03:44:18 +00003979** ^The rollback hook is invoked on a rollback that results from a commit
drhabda6112009-05-14 22:37:47 +00003980** hook returning non-zero, just as it would be with any other rollback.
3981**
drhd68eee02009-12-11 03:44:18 +00003982** ^For the purposes of this API, a transaction is said to have been
drh6ed48bf2007-06-14 20:57:18 +00003983** rolled back if an explicit "ROLLBACK" statement is executed, or
drhf5befa02007-12-06 02:42:07 +00003984** an error or constraint causes an implicit rollback to occur.
drhd68eee02009-12-11 03:44:18 +00003985** ^The rollback callback is not invoked if a transaction is
drhf5befa02007-12-06 02:42:07 +00003986** automatically rolled back because the database connection is closed.
drh6ed48bf2007-06-14 20:57:18 +00003987**
drhabda6112009-05-14 22:37:47 +00003988** See also the [sqlite3_update_hook()] interface.
drh6ed48bf2007-06-14 20:57:18 +00003989*/
3990void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
3991void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*);
3992
3993/*
drhd68eee02009-12-11 03:44:18 +00003994** CAPI3REF: Data Change Notification Callbacks
drh6ed48bf2007-06-14 20:57:18 +00003995**
drhd68eee02009-12-11 03:44:18 +00003996** ^The sqlite3_update_hook() interface registers a callback function
mihailimdc884822008-06-22 08:58:50 +00003997** with the [database connection] identified by the first argument
3998** to be invoked whenever a row is updated, inserted or deleted.
drhd68eee02009-12-11 03:44:18 +00003999** ^Any callback set by a previous call to this function
mihailimdc884822008-06-22 08:58:50 +00004000** for the same database connection is overridden.
danielk197794eb6a12005-12-15 15:22:08 +00004001**
drhd68eee02009-12-11 03:44:18 +00004002** ^The second argument is a pointer to the function to invoke when a
mihailimdc884822008-06-22 08:58:50 +00004003** row is updated, inserted or deleted.
drhd68eee02009-12-11 03:44:18 +00004004** ^The first argument to the callback is a copy of the third argument
mihailimdc884822008-06-22 08:58:50 +00004005** to sqlite3_update_hook().
drhd68eee02009-12-11 03:44:18 +00004006** ^The second callback argument is one of [SQLITE_INSERT], [SQLITE_DELETE],
mihailimdc884822008-06-22 08:58:50 +00004007** or [SQLITE_UPDATE], depending on the operation that caused the callback
4008** to be invoked.
drhd68eee02009-12-11 03:44:18 +00004009** ^The third and fourth arguments to the callback contain pointers to the
mihailimdc884822008-06-22 08:58:50 +00004010** database and table name containing the affected row.
drhd68eee02009-12-11 03:44:18 +00004011** ^The final callback parameter is the [rowid] of the row.
4012** ^In the case of an update, this is the [rowid] after the update takes place.
danielk197794eb6a12005-12-15 15:22:08 +00004013**
drhd68eee02009-12-11 03:44:18 +00004014** ^(The update hook is not invoked when internal system tables are
4015** modified (i.e. sqlite_master and sqlite_sequence).)^
danielk197771fd80b2005-12-16 06:54:01 +00004016**
drhd68eee02009-12-11 03:44:18 +00004017** ^In the current implementation, the update hook
drhabda6112009-05-14 22:37:47 +00004018** is not invoked when duplication rows are deleted because of an
drhd68eee02009-12-11 03:44:18 +00004019** [ON CONFLICT | ON CONFLICT REPLACE] clause. ^Nor is the update hook
drhabda6112009-05-14 22:37:47 +00004020** invoked when rows are deleted using the [truncate optimization].
4021** The exceptions defined in this paragraph might change in a future
4022** release of SQLite.
4023**
drhc8075422008-09-10 13:09:23 +00004024** The update hook implementation must not do anything that will modify
4025** the database connection that invoked the update hook. Any actions
4026** to modify the database connection must be deferred until after the
4027** completion of the [sqlite3_step()] call that triggered the update hook.
4028** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
4029** database connections for the meaning of "modify" in this paragraph.
4030**
drhd68eee02009-12-11 03:44:18 +00004031** ^The sqlite3_update_hook(D,C,P) function
4032** returns the P argument from the previous call
4033** on the same [database connection] D, or NULL for
4034** the first call on D.
drhafc91042008-02-21 02:09:45 +00004035**
drhabda6112009-05-14 22:37:47 +00004036** See also the [sqlite3_commit_hook()] and [sqlite3_rollback_hook()]
4037** interfaces.
danielk197794eb6a12005-12-15 15:22:08 +00004038*/
danielk197771fd80b2005-12-16 06:54:01 +00004039void *sqlite3_update_hook(
danielk197794eb6a12005-12-15 15:22:08 +00004040 sqlite3*,
drh6d2069d2007-08-14 01:58:53 +00004041 void(*)(void *,int ,char const *,char const *,sqlite3_int64),
danielk197794eb6a12005-12-15 15:22:08 +00004042 void*
4043);
danielk197713a68c32005-12-15 10:11:30 +00004044
danielk1977f3f06bb2005-12-16 15:24:28 +00004045/*
drhd68eee02009-12-11 03:44:18 +00004046** CAPI3REF: Enable Or Disable Shared Pager Cache
drhe33b0ed2009-08-06 17:40:45 +00004047** KEYWORDS: {shared cache}
danielk1977f3f06bb2005-12-16 15:24:28 +00004048**
drhd68eee02009-12-11 03:44:18 +00004049** ^(This routine enables or disables the sharing of the database cache
mihailimdc884822008-06-22 08:58:50 +00004050** and schema data structures between [database connection | connections]
4051** to the same database. Sharing is enabled if the argument is true
drhd68eee02009-12-11 03:44:18 +00004052** and disabled if the argument is false.)^
danielk1977f3f06bb2005-12-16 15:24:28 +00004053**
drhd68eee02009-12-11 03:44:18 +00004054** ^Cache sharing is enabled and disabled for an entire process.
mihailimdc884822008-06-22 08:58:50 +00004055** This is a change as of SQLite version 3.5.0. In prior versions of SQLite,
4056** sharing was enabled or disabled for each thread separately.
drh6ed48bf2007-06-14 20:57:18 +00004057**
drhd68eee02009-12-11 03:44:18 +00004058** ^(The cache sharing mode set by this interface effects all subsequent
drhe30f4422007-08-21 16:15:55 +00004059** calls to [sqlite3_open()], [sqlite3_open_v2()], and [sqlite3_open16()].
drhafc91042008-02-21 02:09:45 +00004060** Existing database connections continue use the sharing mode
drhd68eee02009-12-11 03:44:18 +00004061** that was in effect at the time they were opened.)^
drh6ed48bf2007-06-14 20:57:18 +00004062**
drhd68eee02009-12-11 03:44:18 +00004063** ^(This routine returns [SQLITE_OK] if shared cache was enabled or disabled
4064** successfully. An [error code] is returned otherwise.)^
drh6ed48bf2007-06-14 20:57:18 +00004065**
drhd68eee02009-12-11 03:44:18 +00004066** ^Shared cache is disabled by default. But this might change in
drh4ff7fa02007-09-01 18:17:21 +00004067** future releases of SQLite. Applications that care about shared
4068** cache setting should set it explicitly.
drhafc91042008-02-21 02:09:45 +00004069**
drhaff46972009-02-12 17:07:34 +00004070** See Also: [SQLite Shared-Cache Mode]
danielk1977aef0bf62005-12-30 16:28:01 +00004071*/
4072int sqlite3_enable_shared_cache(int);
4073
4074/*
drhd68eee02009-12-11 03:44:18 +00004075** CAPI3REF: Attempt To Free Heap Memory
drh6ed48bf2007-06-14 20:57:18 +00004076**
drhd68eee02009-12-11 03:44:18 +00004077** ^The sqlite3_release_memory() interface attempts to free N bytes
mihailim04bcc002008-06-22 10:21:27 +00004078** of heap memory by deallocating non-essential memory allocations
drhd68eee02009-12-11 03:44:18 +00004079** held by the database library. Memory used to cache database
mihailim04bcc002008-06-22 10:21:27 +00004080** pages to improve performance is an example of non-essential memory.
drhd68eee02009-12-11 03:44:18 +00004081** ^sqlite3_release_memory() returns the number of bytes actually freed,
mihailim04bcc002008-06-22 10:21:27 +00004082** which might be more or less than the amount requested.
danielk197752622822006-01-09 09:59:49 +00004083*/
4084int sqlite3_release_memory(int);
4085
4086/*
drhd68eee02009-12-11 03:44:18 +00004087** CAPI3REF: Impose A Limit On Heap Size
drh6ed48bf2007-06-14 20:57:18 +00004088**
drhd68eee02009-12-11 03:44:18 +00004089** ^The sqlite3_soft_heap_limit() interface places a "soft" limit
mihailimdc884822008-06-22 08:58:50 +00004090** on the amount of heap memory that may be allocated by SQLite.
drhd68eee02009-12-11 03:44:18 +00004091** ^If an internal allocation is requested that would exceed the
mihailimdc884822008-06-22 08:58:50 +00004092** soft heap limit, [sqlite3_release_memory()] is invoked one or
4093** more times to free up some space before the allocation is performed.
danielk197752622822006-01-09 09:59:49 +00004094**
drhdf6473a2009-12-13 22:20:08 +00004095** ^The limit is called "soft" because if [sqlite3_release_memory()]
mihailimdc884822008-06-22 08:58:50 +00004096** cannot free sufficient memory to prevent the limit from being exceeded,
drhe30f4422007-08-21 16:15:55 +00004097** the memory is allocated anyway and the current operation proceeds.
drh6ed48bf2007-06-14 20:57:18 +00004098**
drhd68eee02009-12-11 03:44:18 +00004099** ^A negative or zero value for N means that there is no soft heap limit and
drhe30f4422007-08-21 16:15:55 +00004100** [sqlite3_release_memory()] will only be called when memory is exhausted.
drhd68eee02009-12-11 03:44:18 +00004101** ^The default value for the soft heap limit is zero.
drh6ed48bf2007-06-14 20:57:18 +00004102**
drhd68eee02009-12-11 03:44:18 +00004103** ^(SQLite makes a best effort to honor the soft heap limit.
shane26b34032008-05-23 17:21:09 +00004104** But if the soft heap limit cannot be honored, execution will
drhd68eee02009-12-11 03:44:18 +00004105** continue without error or notification.)^ This is why the limit is
drh6ed48bf2007-06-14 20:57:18 +00004106** called a "soft" limit. It is advisory only.
4107**
drhe30f4422007-08-21 16:15:55 +00004108** Prior to SQLite version 3.5.0, this routine only constrained the memory
4109** allocated by a single thread - the same thread in which this routine
4110** runs. Beginning with SQLite version 3.5.0, the soft heap limit is
drhafc91042008-02-21 02:09:45 +00004111** applied to all threads. The value specified for the soft heap limit
4112** is an upper bound on the total memory allocation for all threads. In
drh8bacf972007-08-25 16:21:29 +00004113** version 3.5.0 there is no mechanism for limiting the heap usage for
4114** individual threads.
danielk197752622822006-01-09 09:59:49 +00004115*/
drhd2d4a6b2006-01-10 15:18:27 +00004116void sqlite3_soft_heap_limit(int);
danielk197752622822006-01-09 09:59:49 +00004117
4118/*
drhfb434032009-12-11 23:11:26 +00004119** CAPI3REF: Extract Metadata About A Column Of A Table
drh6ed48bf2007-06-14 20:57:18 +00004120**
drhd68eee02009-12-11 03:44:18 +00004121** ^This routine returns metadata about a specific column of a specific
mihailimdc884822008-06-22 08:58:50 +00004122** database table accessible using the [database connection] handle
4123** passed as the first function argument.
danielk1977deb802c2006-02-09 13:43:28 +00004124**
drhd68eee02009-12-11 03:44:18 +00004125** ^The column is identified by the second, third and fourth parameters to
drhdf6473a2009-12-13 22:20:08 +00004126** this function. ^The second parameter is either the name of the database
4127** (i.e. "main", "temp", or an attached database) containing the specified
4128** table or NULL. ^If it is NULL, then all attached databases are searched
mihailimdc884822008-06-22 08:58:50 +00004129** for the table using the same algorithm used by the database engine to
drh7a98b852009-12-13 23:03:01 +00004130** resolve unqualified table references.
danielk1977deb802c2006-02-09 13:43:28 +00004131**
drhd68eee02009-12-11 03:44:18 +00004132** ^The third and fourth parameters to this function are the table and column
mihailimdc884822008-06-22 08:58:50 +00004133** name of the desired column, respectively. Neither of these parameters
danielk1977deb802c2006-02-09 13:43:28 +00004134** may be NULL.
4135**
drhd68eee02009-12-11 03:44:18 +00004136** ^Metadata is returned by writing to the memory locations passed as the 5th
4137** and subsequent parameters to this function. ^Any of these arguments may be
mihailimdc884822008-06-22 08:58:50 +00004138** NULL, in which case the corresponding element of metadata is omitted.
mihailim15194222008-06-22 09:55:14 +00004139**
drhd68eee02009-12-11 03:44:18 +00004140** ^(<blockquote>
mihailimdc884822008-06-22 08:58:50 +00004141** <table border="1">
4142** <tr><th> Parameter <th> Output<br>Type <th> Description
danielk1977deb802c2006-02-09 13:43:28 +00004143**
mihailimdc884822008-06-22 08:58:50 +00004144** <tr><td> 5th <td> const char* <td> Data type
4145** <tr><td> 6th <td> const char* <td> Name of default collation sequence
4146** <tr><td> 7th <td> int <td> True if column has a NOT NULL constraint
4147** <tr><td> 8th <td> int <td> True if column is part of the PRIMARY KEY
drh49c3d572008-12-15 22:51:38 +00004148** <tr><td> 9th <td> int <td> True if column is [AUTOINCREMENT]
mihailimdc884822008-06-22 08:58:50 +00004149** </table>
drhd68eee02009-12-11 03:44:18 +00004150** </blockquote>)^
danielk1977deb802c2006-02-09 13:43:28 +00004151**
drhd68eee02009-12-11 03:44:18 +00004152** ^The memory pointed to by the character pointers returned for the
mihailimdc884822008-06-22 08:58:50 +00004153** declaration type and collation sequence is valid only until the next
4154** call to any SQLite API function.
danielk1977deb802c2006-02-09 13:43:28 +00004155**
drhd68eee02009-12-11 03:44:18 +00004156** ^If the specified table is actually a view, an [error code] is returned.
danielk1977deb802c2006-02-09 13:43:28 +00004157**
drhd68eee02009-12-11 03:44:18 +00004158** ^If the specified column is "rowid", "oid" or "_rowid_" and an
drh49c3d572008-12-15 22:51:38 +00004159** [INTEGER PRIMARY KEY] column has been explicitly declared, then the output
drhd68eee02009-12-11 03:44:18 +00004160** parameters are set for the explicitly declared column. ^(If there is no
drh49c3d572008-12-15 22:51:38 +00004161** explicitly declared [INTEGER PRIMARY KEY] column, then the output
mihailimdc884822008-06-22 08:58:50 +00004162** parameters are set as follows:
danielk1977deb802c2006-02-09 13:43:28 +00004163**
drh6ed48bf2007-06-14 20:57:18 +00004164** <pre>
danielk1977deb802c2006-02-09 13:43:28 +00004165** data type: "INTEGER"
4166** collation sequence: "BINARY"
4167** not null: 0
4168** primary key: 1
4169** auto increment: 0
drhd68eee02009-12-11 03:44:18 +00004170** </pre>)^
danielk1977deb802c2006-02-09 13:43:28 +00004171**
drhd68eee02009-12-11 03:44:18 +00004172** ^(This function may load one or more schemas from database files. If an
danielk1977deb802c2006-02-09 13:43:28 +00004173** error occurs during this process, or if the requested table or column
mihailimdc884822008-06-22 08:58:50 +00004174** cannot be found, an [error code] is returned and an error message left
drhd68eee02009-12-11 03:44:18 +00004175** in the [database connection] (to be retrieved using sqlite3_errmsg()).)^
danielk19774b1ae992006-02-10 03:06:10 +00004176**
drhd68eee02009-12-11 03:44:18 +00004177** ^This API is only available if the library was compiled with the
drh4ead1482008-06-26 18:16:05 +00004178** [SQLITE_ENABLE_COLUMN_METADATA] C-preprocessor symbol defined.
danielk1977deb802c2006-02-09 13:43:28 +00004179*/
4180int sqlite3_table_column_metadata(
4181 sqlite3 *db, /* Connection handle */
4182 const char *zDbName, /* Database name or NULL */
4183 const char *zTableName, /* Table name */
4184 const char *zColumnName, /* Column name */
4185 char const **pzDataType, /* OUTPUT: Declared data type */
4186 char const **pzCollSeq, /* OUTPUT: Collation sequence name */
4187 int *pNotNull, /* OUTPUT: True if NOT NULL constraint exists */
4188 int *pPrimaryKey, /* OUTPUT: True if column part of PK */
drh98c94802007-10-01 13:50:31 +00004189 int *pAutoinc /* OUTPUT: True if column is auto-increment */
danielk1977deb802c2006-02-09 13:43:28 +00004190);
4191
4192/*
drhd68eee02009-12-11 03:44:18 +00004193** CAPI3REF: Load An Extension
drh1e397f82006-06-08 15:28:43 +00004194**
drhd68eee02009-12-11 03:44:18 +00004195** ^This interface loads an SQLite extension library from the named file.
drh1e397f82006-06-08 15:28:43 +00004196**
drhd68eee02009-12-11 03:44:18 +00004197** ^The sqlite3_load_extension() interface attempts to load an
4198** SQLite extension library contained in the file zFile.
drh1e397f82006-06-08 15:28:43 +00004199**
drhd68eee02009-12-11 03:44:18 +00004200** ^The entry point is zProc.
4201** ^zProc may be 0, in which case the name of the entry point
4202** defaults to "sqlite3_extension_init".
4203** ^The sqlite3_load_extension() interface returns
4204** [SQLITE_OK] on success and [SQLITE_ERROR] if something goes wrong.
4205** ^If an error occurs and pzErrMsg is not 0, then the
4206** [sqlite3_load_extension()] interface shall attempt to
4207** fill *pzErrMsg with error message text stored in memory
4208** obtained from [sqlite3_malloc()]. The calling function
4209** should free this memory by calling [sqlite3_free()].
mihailimdc884822008-06-22 08:58:50 +00004210**
drhd68eee02009-12-11 03:44:18 +00004211** ^Extension loading must be enabled using
4212** [sqlite3_enable_load_extension()] prior to calling this API,
4213** otherwise an error will be returned.
drha94cc422009-12-03 01:01:02 +00004214**
4215** See also the [load_extension() SQL function].
drh1e397f82006-06-08 15:28:43 +00004216*/
4217int sqlite3_load_extension(
4218 sqlite3 *db, /* Load the extension into this database connection */
4219 const char *zFile, /* Name of the shared library containing extension */
4220 const char *zProc, /* Entry point. Derived from zFile if 0 */
4221 char **pzErrMsg /* Put error message here if not 0 */
4222);
4223
4224/*
drhd68eee02009-12-11 03:44:18 +00004225** CAPI3REF: Enable Or Disable Extension Loading
drh6ed48bf2007-06-14 20:57:18 +00004226**
drhd68eee02009-12-11 03:44:18 +00004227** ^So as not to open security holes in older applications that are
drh6ed48bf2007-06-14 20:57:18 +00004228** unprepared to deal with extension loading, and as a means of disabling
mihailimdc884822008-06-22 08:58:50 +00004229** extension loading while evaluating user-entered SQL, the following API
4230** is provided to turn the [sqlite3_load_extension()] mechanism on and off.
drhc2e87a32006-06-27 15:16:14 +00004231**
drhd68eee02009-12-11 03:44:18 +00004232** ^Extension loading is off by default. See ticket #1863.
4233** ^Call the sqlite3_enable_load_extension() routine with onoff==1
4234** to turn extension loading on and call it with onoff==0 to turn
4235** it back off again.
drhc2e87a32006-06-27 15:16:14 +00004236*/
4237int sqlite3_enable_load_extension(sqlite3 *db, int onoff);
4238
4239/*
drhd68eee02009-12-11 03:44:18 +00004240** CAPI3REF: Automatically Load An Extensions
drh9eff6162006-06-12 21:59:13 +00004241**
drhd68eee02009-12-11 03:44:18 +00004242** ^This API can be invoked at program startup in order to register
drh1409be62006-08-23 20:07:20 +00004243** one or more statically linked extensions that will be available
drhd68eee02009-12-11 03:44:18 +00004244** to all new [database connections].
mihailimdc884822008-06-22 08:58:50 +00004245**
drhd68eee02009-12-11 03:44:18 +00004246** ^(This routine stores a pointer to the extension entry point
4247** in an array that is obtained from [sqlite3_malloc()]. That memory
4248** is deallocated by [sqlite3_reset_auto_extension()].)^
mihailimdc884822008-06-22 08:58:50 +00004249**
drhd68eee02009-12-11 03:44:18 +00004250** ^This function registers an extension entry point that is
4251** automatically invoked whenever a new [database connection]
4252** is opened using [sqlite3_open()], [sqlite3_open16()],
4253** or [sqlite3_open_v2()].
4254** ^Duplicate extensions are detected so calling this routine
4255** multiple times with the same extension is harmless.
4256** ^Automatic extensions apply across all threads.
drh1409be62006-08-23 20:07:20 +00004257*/
drh1875f7a2008-12-08 18:19:17 +00004258int sqlite3_auto_extension(void (*xEntryPoint)(void));
drh1409be62006-08-23 20:07:20 +00004259
drh1409be62006-08-23 20:07:20 +00004260/*
drhd68eee02009-12-11 03:44:18 +00004261** CAPI3REF: Reset Automatic Extension Loading
drh1409be62006-08-23 20:07:20 +00004262**
drhd68eee02009-12-11 03:44:18 +00004263** ^(This function disables all previously registered automatic
4264** extensions. It undoes the effect of all prior
4265** [sqlite3_auto_extension()] calls.)^
drh6ed48bf2007-06-14 20:57:18 +00004266**
drhd68eee02009-12-11 03:44:18 +00004267** ^This function disables automatic extensions in all threads.
drh1409be62006-08-23 20:07:20 +00004268*/
4269void sqlite3_reset_auto_extension(void);
4270
drh1409be62006-08-23 20:07:20 +00004271/*
drh9eff6162006-06-12 21:59:13 +00004272** The interface to the virtual-table mechanism is currently considered
4273** to be experimental. The interface might change in incompatible ways.
4274** If this is a problem for you, do not use the interface at this time.
4275**
shane26b34032008-05-23 17:21:09 +00004276** When the virtual-table mechanism stabilizes, we will declare the
drh9eff6162006-06-12 21:59:13 +00004277** interface fixed, support it indefinitely, and remove this comment.
4278*/
4279
4280/*
4281** Structures used by the virtual table interface
drhe09daa92006-06-10 13:29:31 +00004282*/
4283typedef struct sqlite3_vtab sqlite3_vtab;
4284typedef struct sqlite3_index_info sqlite3_index_info;
4285typedef struct sqlite3_vtab_cursor sqlite3_vtab_cursor;
4286typedef struct sqlite3_module sqlite3_module;
drh9eff6162006-06-12 21:59:13 +00004287
4288/*
drhd68eee02009-12-11 03:44:18 +00004289** CAPI3REF: Virtual Table Object
drh9cff9dc2009-04-13 14:43:40 +00004290** KEYWORDS: sqlite3_module {virtual table module}
drhb4d58ae2008-02-21 20:17:06 +00004291**
drh9cff9dc2009-04-13 14:43:40 +00004292** This structure, sometimes called a a "virtual table module",
4293** defines the implementation of a [virtual tables].
4294** This structure consists mostly of methods for the module.
mihailim15194222008-06-22 09:55:14 +00004295**
drhd68eee02009-12-11 03:44:18 +00004296** ^A virtual table module is created by filling in a persistent
drh9cff9dc2009-04-13 14:43:40 +00004297** instance of this structure and passing a pointer to that instance
4298** to [sqlite3_create_module()] or [sqlite3_create_module_v2()].
drhd68eee02009-12-11 03:44:18 +00004299** ^The registration remains valid until it is replaced by a different
drh9cff9dc2009-04-13 14:43:40 +00004300** module or until the [database connection] closes. The content
4301** of this structure must not change while it is registered with
4302** any database connection.
drh9eff6162006-06-12 21:59:13 +00004303*/
drhe09daa92006-06-10 13:29:31 +00004304struct sqlite3_module {
4305 int iVersion;
danielk19779da9d472006-06-14 06:58:15 +00004306 int (*xCreate)(sqlite3*, void *pAux,
drhe4102962006-09-11 00:34:22 +00004307 int argc, const char *const*argv,
drh4ca8aac2006-09-10 17:31:58 +00004308 sqlite3_vtab **ppVTab, char**);
danielk19779da9d472006-06-14 06:58:15 +00004309 int (*xConnect)(sqlite3*, void *pAux,
drhe4102962006-09-11 00:34:22 +00004310 int argc, const char *const*argv,
drh4ca8aac2006-09-10 17:31:58 +00004311 sqlite3_vtab **ppVTab, char**);
drhe09daa92006-06-10 13:29:31 +00004312 int (*xBestIndex)(sqlite3_vtab *pVTab, sqlite3_index_info*);
4313 int (*xDisconnect)(sqlite3_vtab *pVTab);
4314 int (*xDestroy)(sqlite3_vtab *pVTab);
4315 int (*xOpen)(sqlite3_vtab *pVTab, sqlite3_vtab_cursor **ppCursor);
4316 int (*xClose)(sqlite3_vtab_cursor*);
drh4be8b512006-06-13 23:51:34 +00004317 int (*xFilter)(sqlite3_vtab_cursor*, int idxNum, const char *idxStr,
drhe09daa92006-06-10 13:29:31 +00004318 int argc, sqlite3_value **argv);
4319 int (*xNext)(sqlite3_vtab_cursor*);
danielk1977a298e902006-06-22 09:53:48 +00004320 int (*xEof)(sqlite3_vtab_cursor*);
drhe09daa92006-06-10 13:29:31 +00004321 int (*xColumn)(sqlite3_vtab_cursor*, sqlite3_context*, int);
drh6d2069d2007-08-14 01:58:53 +00004322 int (*xRowid)(sqlite3_vtab_cursor*, sqlite3_int64 *pRowid);
4323 int (*xUpdate)(sqlite3_vtab *, int, sqlite3_value **, sqlite3_int64 *);
drhe09daa92006-06-10 13:29:31 +00004324 int (*xBegin)(sqlite3_vtab *pVTab);
4325 int (*xSync)(sqlite3_vtab *pVTab);
4326 int (*xCommit)(sqlite3_vtab *pVTab);
4327 int (*xRollback)(sqlite3_vtab *pVTab);
drhb7f6f682006-07-08 17:06:43 +00004328 int (*xFindFunction)(sqlite3_vtab *pVtab, int nArg, const char *zName,
drhe94b0c32006-07-08 18:09:15 +00004329 void (**pxFunc)(sqlite3_context*,int,sqlite3_value**),
4330 void **ppArg);
danielk1977182c4ba2007-06-27 15:53:34 +00004331 int (*xRename)(sqlite3_vtab *pVtab, const char *zNew);
drhe09daa92006-06-10 13:29:31 +00004332};
drh9eff6162006-06-12 21:59:13 +00004333
4334/*
drhd68eee02009-12-11 03:44:18 +00004335** CAPI3REF: Virtual Table Indexing Information
drhb4d58ae2008-02-21 20:17:06 +00004336** KEYWORDS: sqlite3_index_info
4337**
drh6ba8e962010-07-22 11:40:34 +00004338** The sqlite3_index_info structure and its substructures is used as part
4339** of the [virtual table] interface to
drh9cff9dc2009-04-13 14:43:40 +00004340** pass information into and receive the reply from the [xBestIndex]
4341** method of a [virtual table module]. The fields under **Inputs** are the
drh9eff6162006-06-12 21:59:13 +00004342** inputs to xBestIndex and are read-only. xBestIndex inserts its
4343** results into the **Outputs** fields.
4344**
drhd68eee02009-12-11 03:44:18 +00004345** ^(The aConstraint[] array records WHERE clause constraints of the form:
drh9eff6162006-06-12 21:59:13 +00004346**
drh6ba8e962010-07-22 11:40:34 +00004347** <blockquote>column OP expr</blockquote>
drh9eff6162006-06-12 21:59:13 +00004348**
drhdf6473a2009-12-13 22:20:08 +00004349** where OP is =, &lt;, &lt;=, &gt;, or &gt;=.)^ ^(The particular operator is
drh6ba8e962010-07-22 11:40:34 +00004350** stored in aConstraint[].op using one of the
4351** [SQLITE_INDEX_CONSTRAINT_EQ | SQLITE_INDEX_CONSTRAINT_ values].)^
4352** ^(The index of the column is stored in
drh7a98b852009-12-13 23:03:01 +00004353** aConstraint[].iColumn.)^ ^(aConstraint[].usable is TRUE if the
drh9eff6162006-06-12 21:59:13 +00004354** expr on the right-hand side can be evaluated (and thus the constraint
drhd68eee02009-12-11 03:44:18 +00004355** is usable) and false if it cannot.)^
drh9eff6162006-06-12 21:59:13 +00004356**
drhd68eee02009-12-11 03:44:18 +00004357** ^The optimizer automatically inverts terms of the form "expr OP column"
drh98c94802007-10-01 13:50:31 +00004358** and makes other simplifications to the WHERE clause in an attempt to
drh9eff6162006-06-12 21:59:13 +00004359** get as many WHERE clause terms into the form shown above as possible.
drhdf6473a2009-12-13 22:20:08 +00004360** ^The aConstraint[] array only reports WHERE clause terms that are
4361** relevant to the particular virtual table being queried.
drh9eff6162006-06-12 21:59:13 +00004362**
drhd68eee02009-12-11 03:44:18 +00004363** ^Information about the ORDER BY clause is stored in aOrderBy[].
4364** ^Each term of aOrderBy records a column of the ORDER BY clause.
drh9eff6162006-06-12 21:59:13 +00004365**
drh9cff9dc2009-04-13 14:43:40 +00004366** The [xBestIndex] method must fill aConstraintUsage[] with information
drhd68eee02009-12-11 03:44:18 +00004367** about what parameters to pass to xFilter. ^If argvIndex>0 then
drh9eff6162006-06-12 21:59:13 +00004368** the right-hand side of the corresponding aConstraint[] is evaluated
drhd68eee02009-12-11 03:44:18 +00004369** and becomes the argvIndex-th entry in argv. ^(If aConstraintUsage[].omit
drh9eff6162006-06-12 21:59:13 +00004370** is true, then the constraint is assumed to be fully handled by the
drhd68eee02009-12-11 03:44:18 +00004371** virtual table and is not checked again by SQLite.)^
drh9eff6162006-06-12 21:59:13 +00004372**
drhd68eee02009-12-11 03:44:18 +00004373** ^The idxNum and idxPtr values are recorded and passed into the
drh9cff9dc2009-04-13 14:43:40 +00004374** [xFilter] method.
drh7a98b852009-12-13 23:03:01 +00004375** ^[sqlite3_free()] is used to free idxPtr if and only if
drh9cff9dc2009-04-13 14:43:40 +00004376** needToFreeIdxPtr is true.
drh9eff6162006-06-12 21:59:13 +00004377**
drhd68eee02009-12-11 03:44:18 +00004378** ^The orderByConsumed means that output from [xFilter]/[xNext] will occur in
drh9eff6162006-06-12 21:59:13 +00004379** the correct order to satisfy the ORDER BY clause so that no separate
4380** sorting step is required.
4381**
drhd68eee02009-12-11 03:44:18 +00004382** ^The estimatedCost value is an estimate of the cost of doing the
drh9eff6162006-06-12 21:59:13 +00004383** particular lookup. A full scan of a table with N entries should have
4384** a cost of N. A binary search of a table of N entries should have a
4385** cost of approximately log(N).
4386*/
drhe09daa92006-06-10 13:29:31 +00004387struct sqlite3_index_info {
4388 /* Inputs */
drh6cca08c2007-09-21 12:43:16 +00004389 int nConstraint; /* Number of entries in aConstraint */
4390 struct sqlite3_index_constraint {
drh9eff6162006-06-12 21:59:13 +00004391 int iColumn; /* Column on left-hand side of constraint */
4392 unsigned char op; /* Constraint operator */
4393 unsigned char usable; /* True if this constraint is usable */
4394 int iTermOffset; /* Used internally - xBestIndex should ignore */
drh6cca08c2007-09-21 12:43:16 +00004395 } *aConstraint; /* Table of WHERE clause constraints */
4396 int nOrderBy; /* Number of terms in the ORDER BY clause */
4397 struct sqlite3_index_orderby {
drh9eff6162006-06-12 21:59:13 +00004398 int iColumn; /* Column number */
4399 unsigned char desc; /* True for DESC. False for ASC. */
drh6cca08c2007-09-21 12:43:16 +00004400 } *aOrderBy; /* The ORDER BY clause */
drhe09daa92006-06-10 13:29:31 +00004401 /* Outputs */
drh9eff6162006-06-12 21:59:13 +00004402 struct sqlite3_index_constraint_usage {
4403 int argvIndex; /* if >0, constraint is part of argv to xFilter */
4404 unsigned char omit; /* Do not code a test for this constraint */
drh6cca08c2007-09-21 12:43:16 +00004405 } *aConstraintUsage;
drh4be8b512006-06-13 23:51:34 +00004406 int idxNum; /* Number used to identify the index */
4407 char *idxStr; /* String, possibly obtained from sqlite3_malloc */
4408 int needToFreeIdxStr; /* Free idxStr using sqlite3_free() if true */
drh9eff6162006-06-12 21:59:13 +00004409 int orderByConsumed; /* True if output is already ordered */
4410 double estimatedCost; /* Estimated cost of using this index */
drhe09daa92006-06-10 13:29:31 +00004411};
drh6ba8e962010-07-22 11:40:34 +00004412
4413/*
4414** CAPI3REF: Virtual Table Constraint Operator Codes
4415**
4416** These macros defined the allowed values for the
4417** [sqlite3_index_info].aConstraint[].op field. Each value represents
4418** an operator that is part of a constraint term in the wHERE clause of
4419** a query that uses a [virtual table].
4420*/
drh9eff6162006-06-12 21:59:13 +00004421#define SQLITE_INDEX_CONSTRAINT_EQ 2
4422#define SQLITE_INDEX_CONSTRAINT_GT 4
4423#define SQLITE_INDEX_CONSTRAINT_LE 8
4424#define SQLITE_INDEX_CONSTRAINT_LT 16
4425#define SQLITE_INDEX_CONSTRAINT_GE 32
4426#define SQLITE_INDEX_CONSTRAINT_MATCH 64
4427
4428/*
drhd68eee02009-12-11 03:44:18 +00004429** CAPI3REF: Register A Virtual Table Implementation
drhb4d58ae2008-02-21 20:17:06 +00004430**
drhfb434032009-12-11 23:11:26 +00004431** ^These routines are used to register a new [virtual table module] name.
drhd68eee02009-12-11 03:44:18 +00004432** ^Module names must be registered before
drhdf6473a2009-12-13 22:20:08 +00004433** creating a new [virtual table] using the module and before using a
drh9cff9dc2009-04-13 14:43:40 +00004434** preexisting [virtual table] for the module.
mihailim15194222008-06-22 09:55:14 +00004435**
drhd68eee02009-12-11 03:44:18 +00004436** ^The module name is registered on the [database connection] specified
4437** by the first parameter. ^The name of the module is given by the
4438** second parameter. ^The third parameter is a pointer to
4439** the implementation of the [virtual table module]. ^The fourth
drh9cff9dc2009-04-13 14:43:40 +00004440** parameter is an arbitrary client data pointer that is passed through
4441** into the [xCreate] and [xConnect] methods of the virtual table module
4442** when a new virtual table is be being created or reinitialized.
4443**
drhfb434032009-12-11 23:11:26 +00004444** ^The sqlite3_create_module_v2() interface has a fifth parameter which
4445** is a pointer to a destructor for the pClientData. ^SQLite will
4446** invoke the destructor function (if it is not NULL) when SQLite
4447** no longer needs the pClientData pointer. ^The sqlite3_create_module()
4448** interface is equivalent to sqlite3_create_module_v2() with a NULL
4449** destructor.
drh9eff6162006-06-12 21:59:13 +00004450*/
drh9f8da322010-03-10 20:06:37 +00004451int sqlite3_create_module(
drh9eff6162006-06-12 21:59:13 +00004452 sqlite3 *db, /* SQLite connection to register module with */
4453 const char *zName, /* Name of the module */
drh9cff9dc2009-04-13 14:43:40 +00004454 const sqlite3_module *p, /* Methods for the module */
4455 void *pClientData /* Client data for xCreate/xConnect */
drhb9bb7c12006-06-11 23:41:55 +00004456);
drh9f8da322010-03-10 20:06:37 +00004457int sqlite3_create_module_v2(
danielk1977832a58a2007-06-22 15:21:15 +00004458 sqlite3 *db, /* SQLite connection to register module with */
4459 const char *zName, /* Name of the module */
drh9cff9dc2009-04-13 14:43:40 +00004460 const sqlite3_module *p, /* Methods for the module */
4461 void *pClientData, /* Client data for xCreate/xConnect */
danielk1977832a58a2007-06-22 15:21:15 +00004462 void(*xDestroy)(void*) /* Module destructor function */
4463);
4464
4465/*
drhd68eee02009-12-11 03:44:18 +00004466** CAPI3REF: Virtual Table Instance Object
drhb4d58ae2008-02-21 20:17:06 +00004467** KEYWORDS: sqlite3_vtab
4468**
drh9cff9dc2009-04-13 14:43:40 +00004469** Every [virtual table module] implementation uses a subclass
drhd68eee02009-12-11 03:44:18 +00004470** of this object to describe a particular instance
drh9cff9dc2009-04-13 14:43:40 +00004471** of the [virtual table]. Each subclass will
mihailim15194222008-06-22 09:55:14 +00004472** be tailored to the specific needs of the module implementation.
4473** The purpose of this superclass is to define certain fields that are
4474** common to all module implementations.
drhfe1368e2006-09-10 17:08:29 +00004475**
drhd68eee02009-12-11 03:44:18 +00004476** ^Virtual tables methods can set an error message by assigning a
mihailim15194222008-06-22 09:55:14 +00004477** string obtained from [sqlite3_mprintf()] to zErrMsg. The method should
4478** take care that any prior string is freed by a call to [sqlite3_free()]
drhd68eee02009-12-11 03:44:18 +00004479** prior to assigning a new string to zErrMsg. ^After the error message
drhfe1368e2006-09-10 17:08:29 +00004480** is delivered up to the client application, the string will be automatically
drh9cff9dc2009-04-13 14:43:40 +00004481** freed by sqlite3_free() and the zErrMsg field will be zeroed.
drh9eff6162006-06-12 21:59:13 +00004482*/
4483struct sqlite3_vtab {
drha967e882006-06-13 01:04:52 +00004484 const sqlite3_module *pModule; /* The module for this virtual table */
danielk1977595a5232009-07-24 17:58:53 +00004485 int nRef; /* NO LONGER USED */
drh4ca8aac2006-09-10 17:31:58 +00004486 char *zErrMsg; /* Error message from sqlite3_mprintf() */
drh9eff6162006-06-12 21:59:13 +00004487 /* Virtual table implementations will typically add additional fields */
4488};
4489
drhb4d58ae2008-02-21 20:17:06 +00004490/*
drhd68eee02009-12-11 03:44:18 +00004491** CAPI3REF: Virtual Table Cursor Object
drh9cff9dc2009-04-13 14:43:40 +00004492** KEYWORDS: sqlite3_vtab_cursor {virtual table cursor}
drhb4d58ae2008-02-21 20:17:06 +00004493**
drh9cff9dc2009-04-13 14:43:40 +00004494** Every [virtual table module] implementation uses a subclass of the
4495** following structure to describe cursors that point into the
4496** [virtual table] and are used
drh9eff6162006-06-12 21:59:13 +00004497** to loop through the virtual table. Cursors are created using the
drh9cff9dc2009-04-13 14:43:40 +00004498** [sqlite3_module.xOpen | xOpen] method of the module and are destroyed
drhd68eee02009-12-11 03:44:18 +00004499** by the [sqlite3_module.xClose | xClose] method. Cursors are used
drh9cff9dc2009-04-13 14:43:40 +00004500** by the [xFilter], [xNext], [xEof], [xColumn], and [xRowid] methods
4501** of the module. Each module implementation will define
drh9eff6162006-06-12 21:59:13 +00004502** the content of a cursor structure to suit its own needs.
4503**
4504** This superclass exists in order to define fields of the cursor that
4505** are common to all implementations.
4506*/
4507struct sqlite3_vtab_cursor {
4508 sqlite3_vtab *pVtab; /* Virtual table of this cursor */
4509 /* Virtual table implementations will typically add additional fields */
4510};
4511
4512/*
drhd68eee02009-12-11 03:44:18 +00004513** CAPI3REF: Declare The Schema Of A Virtual Table
drhb4d58ae2008-02-21 20:17:06 +00004514**
drhd68eee02009-12-11 03:44:18 +00004515** ^The [xCreate] and [xConnect] methods of a
drh9cff9dc2009-04-13 14:43:40 +00004516** [virtual table module] call this interface
drh9eff6162006-06-12 21:59:13 +00004517** to declare the format (the names and datatypes of the columns) of
4518** the virtual tables they implement.
4519*/
drh9f8da322010-03-10 20:06:37 +00004520int sqlite3_declare_vtab(sqlite3*, const char *zSQL);
drhe09daa92006-06-10 13:29:31 +00004521
4522/*
drhd68eee02009-12-11 03:44:18 +00004523** CAPI3REF: Overload A Function For A Virtual Table
drhb4d58ae2008-02-21 20:17:06 +00004524**
drhd68eee02009-12-11 03:44:18 +00004525** ^(Virtual tables can provide alternative implementations of functions
drh9cff9dc2009-04-13 14:43:40 +00004526** using the [xFindFunction] method of the [virtual table module].
4527** But global versions of those functions
drh7a98b852009-12-13 23:03:01 +00004528** must exist in order to be overloaded.)^
drhb7481e72006-09-16 21:45:14 +00004529**
drhd68eee02009-12-11 03:44:18 +00004530** ^(This API makes sure a global version of a function with a particular
drhb7481e72006-09-16 21:45:14 +00004531** name and number of parameters exists. If no such function exists
drhd68eee02009-12-11 03:44:18 +00004532** before this API is called, a new function is created.)^ ^The implementation
drhb7481e72006-09-16 21:45:14 +00004533** of the new function always causes an exception to be thrown. So
4534** the new function is not good for anything by itself. Its only
shane26b34032008-05-23 17:21:09 +00004535** purpose is to be a placeholder function that can be overloaded
drh9cff9dc2009-04-13 14:43:40 +00004536** by a [virtual table].
drhb7481e72006-09-16 21:45:14 +00004537*/
drh9f8da322010-03-10 20:06:37 +00004538int sqlite3_overload_function(sqlite3*, const char *zFuncName, int nArg);
drhb7481e72006-09-16 21:45:14 +00004539
4540/*
drh9eff6162006-06-12 21:59:13 +00004541** The interface to the virtual-table mechanism defined above (back up
4542** to a comment remarkably similar to this one) is currently considered
4543** to be experimental. The interface might change in incompatible ways.
4544** If this is a problem for you, do not use the interface at this time.
4545**
drh98c94802007-10-01 13:50:31 +00004546** When the virtual-table mechanism stabilizes, we will declare the
drh9eff6162006-06-12 21:59:13 +00004547** interface fixed, support it indefinitely, and remove this comment.
drh9eff6162006-06-12 21:59:13 +00004548*/
4549
danielk19778cbadb02007-05-03 16:31:26 +00004550/*
drhd68eee02009-12-11 03:44:18 +00004551** CAPI3REF: A Handle To An Open BLOB
mihailim15194222008-06-22 09:55:14 +00004552** KEYWORDS: {BLOB handle} {BLOB handles}
drh6ed48bf2007-06-14 20:57:18 +00004553**
drhb4d58ae2008-02-21 20:17:06 +00004554** An instance of this object represents an open BLOB on which
mihailim1c492652008-06-21 18:02:16 +00004555** [sqlite3_blob_open | incremental BLOB I/O] can be performed.
drhd68eee02009-12-11 03:44:18 +00004556** ^Objects of this type are created by [sqlite3_blob_open()]
mihailim15194222008-06-22 09:55:14 +00004557** and destroyed by [sqlite3_blob_close()].
drhd68eee02009-12-11 03:44:18 +00004558** ^The [sqlite3_blob_read()] and [sqlite3_blob_write()] interfaces
mihailim15194222008-06-22 09:55:14 +00004559** can be used to read or write small subsections of the BLOB.
drhd68eee02009-12-11 03:44:18 +00004560** ^The [sqlite3_blob_bytes()] interface returns the size of the BLOB in bytes.
danielk19778cbadb02007-05-03 16:31:26 +00004561*/
danielk1977b4e9af92007-05-01 17:49:49 +00004562typedef struct sqlite3_blob sqlite3_blob;
4563
danielk19778cbadb02007-05-03 16:31:26 +00004564/*
drhfb434032009-12-11 23:11:26 +00004565** CAPI3REF: Open A BLOB For Incremental I/O
drh6ed48bf2007-06-14 20:57:18 +00004566**
drhd68eee02009-12-11 03:44:18 +00004567** ^(This interfaces opens a [BLOB handle | handle] to the BLOB located
drhf84ddc12008-03-24 12:51:46 +00004568** in row iRow, column zColumn, table zTable in database zDb;
mihailim15194222008-06-22 09:55:14 +00004569** in other words, the same BLOB that would be selected by:
danielk19778cbadb02007-05-03 16:31:26 +00004570**
drh6ed48bf2007-06-14 20:57:18 +00004571** <pre>
drh49c3d572008-12-15 22:51:38 +00004572** SELECT zColumn FROM zDb.zTable WHERE [rowid] = iRow;
drhd68eee02009-12-11 03:44:18 +00004573** </pre>)^
danielk19778cbadb02007-05-03 16:31:26 +00004574**
drhd68eee02009-12-11 03:44:18 +00004575** ^If the flags parameter is non-zero, then the BLOB is opened for read
4576** and write access. ^If it is zero, the BLOB is opened for read access.
4577** ^It is not possible to open a column that is part of an index or primary
danfedd4802009-10-07 11:29:40 +00004578** key for writing. ^If [foreign key constraints] are enabled, it is
drhc4ad1e92009-10-10 14:29:30 +00004579** not possible to open a column that is part of a [child key] for writing.
danielk19778cbadb02007-05-03 16:31:26 +00004580**
drhd68eee02009-12-11 03:44:18 +00004581** ^Note that the database name is not the filename that contains
drhf84ddc12008-03-24 12:51:46 +00004582** the database but rather the symbolic name of the database that
drhd68eee02009-12-11 03:44:18 +00004583** appears after the AS keyword when the database is connected using [ATTACH].
4584** ^For the main database file, the database name is "main".
4585** ^For TEMP tables, the database name is "temp".
drhf84ddc12008-03-24 12:51:46 +00004586**
drhd68eee02009-12-11 03:44:18 +00004587** ^(On success, [SQLITE_OK] is returned and the new [BLOB handle] is written
drhabda6112009-05-14 22:37:47 +00004588** to *ppBlob. Otherwise an [error code] is returned and *ppBlob is set
drhd68eee02009-12-11 03:44:18 +00004589** to be a null pointer.)^
4590** ^This function sets the [database connection] error code and message
drhabda6112009-05-14 22:37:47 +00004591** accessible via [sqlite3_errcode()] and [sqlite3_errmsg()] and related
drhd68eee02009-12-11 03:44:18 +00004592** functions. ^Note that the *ppBlob variable is always initialized in a
drhabda6112009-05-14 22:37:47 +00004593** way that makes it safe to invoke [sqlite3_blob_close()] on *ppBlob
4594** regardless of the success or failure of this routine.
mihailim15194222008-06-22 09:55:14 +00004595**
drhd68eee02009-12-11 03:44:18 +00004596** ^(If the row that a BLOB handle points to is modified by an
drh9de1b352008-06-26 15:04:57 +00004597** [UPDATE], [DELETE], or by [ON CONFLICT] side-effects
4598** then the BLOB handle is marked as "expired".
4599** This is true if any column of the row is changed, even a column
drhd68eee02009-12-11 03:44:18 +00004600** other than the one the BLOB handle is open on.)^
4601** ^Calls to [sqlite3_blob_read()] and [sqlite3_blob_write()] for
drh9de1b352008-06-26 15:04:57 +00004602** a expired BLOB handle fail with an return code of [SQLITE_ABORT].
drhd68eee02009-12-11 03:44:18 +00004603** ^(Changes written into a BLOB prior to the BLOB expiring are not
drhdf6473a2009-12-13 22:20:08 +00004604** rolled back by the expiration of the BLOB. Such changes will eventually
drhd68eee02009-12-11 03:44:18 +00004605** commit if the transaction continues to completion.)^
drh9de1b352008-06-26 15:04:57 +00004606**
drhd68eee02009-12-11 03:44:18 +00004607** ^Use the [sqlite3_blob_bytes()] interface to determine the size of
4608** the opened blob. ^The size of a blob may not be changed by this
drh9e42f8a2009-08-13 20:15:29 +00004609** interface. Use the [UPDATE] SQL command to change the size of a
drhabda6112009-05-14 22:37:47 +00004610** blob.
4611**
drhd68eee02009-12-11 03:44:18 +00004612** ^The [sqlite3_bind_zeroblob()] and [sqlite3_result_zeroblob()] interfaces
drhabda6112009-05-14 22:37:47 +00004613** and the built-in [zeroblob] SQL function can be used, if desired,
4614** to create an empty, zero-filled blob in which to read or write using
4615** this interface.
4616**
4617** To avoid a resource leak, every open [BLOB handle] should eventually
4618** be released by a call to [sqlite3_blob_close()].
danielk19778cbadb02007-05-03 16:31:26 +00004619*/
danielk1977b4e9af92007-05-01 17:49:49 +00004620int sqlite3_blob_open(
4621 sqlite3*,
4622 const char *zDb,
4623 const char *zTable,
4624 const char *zColumn,
drh6d2069d2007-08-14 01:58:53 +00004625 sqlite3_int64 iRow,
danielk1977b4e9af92007-05-01 17:49:49 +00004626 int flags,
4627 sqlite3_blob **ppBlob
4628);
4629
danielk19778cbadb02007-05-03 16:31:26 +00004630/*
drhd68eee02009-12-11 03:44:18 +00004631** CAPI3REF: Close A BLOB Handle
drh6ed48bf2007-06-14 20:57:18 +00004632**
drhd68eee02009-12-11 03:44:18 +00004633** ^Closes an open [BLOB handle].
drh2dd62be2007-12-04 13:22:43 +00004634**
drhd68eee02009-12-11 03:44:18 +00004635** ^Closing a BLOB shall cause the current transaction to commit
drhf5befa02007-12-06 02:42:07 +00004636** if there are no other BLOBs, no pending prepared statements, and the
mihailim15194222008-06-22 09:55:14 +00004637** database connection is in [autocommit mode].
drhd68eee02009-12-11 03:44:18 +00004638** ^If any writes were made to the BLOB, they might be held in cache
drhabda6112009-05-14 22:37:47 +00004639** until the close operation if they will fit.
mihailim15194222008-06-22 09:55:14 +00004640**
drhd68eee02009-12-11 03:44:18 +00004641** ^(Closing the BLOB often forces the changes
drh2dd62be2007-12-04 13:22:43 +00004642** out to disk and so if any I/O errors occur, they will likely occur
drhabda6112009-05-14 22:37:47 +00004643** at the time when the BLOB is closed. Any errors that occur during
drhd68eee02009-12-11 03:44:18 +00004644** closing are reported as a non-zero return value.)^
drh2dd62be2007-12-04 13:22:43 +00004645**
drhd68eee02009-12-11 03:44:18 +00004646** ^(The BLOB is closed unconditionally. Even if this routine returns
4647** an error code, the BLOB is still closed.)^
drhb4d58ae2008-02-21 20:17:06 +00004648**
drhd68eee02009-12-11 03:44:18 +00004649** ^Calling this routine with a null pointer (such as would be returned
4650** by a failed call to [sqlite3_blob_open()]) is a harmless no-op.
danielk19778cbadb02007-05-03 16:31:26 +00004651*/
danielk1977b4e9af92007-05-01 17:49:49 +00004652int sqlite3_blob_close(sqlite3_blob *);
4653
danielk19778cbadb02007-05-03 16:31:26 +00004654/*
drhd68eee02009-12-11 03:44:18 +00004655** CAPI3REF: Return The Size Of An Open BLOB
drh6ed48bf2007-06-14 20:57:18 +00004656**
drhd68eee02009-12-11 03:44:18 +00004657** ^Returns the size in bytes of the BLOB accessible via the
4658** successfully opened [BLOB handle] in its only argument. ^The
drhabda6112009-05-14 22:37:47 +00004659** incremental blob I/O routines can only read or overwriting existing
4660** blob content; they cannot change the size of a blob.
4661**
4662** This routine only works on a [BLOB handle] which has been created
4663** by a prior successful call to [sqlite3_blob_open()] and which has not
4664** been closed by [sqlite3_blob_close()]. Passing any other pointer in
4665** to this routine results in undefined and probably undesirable behavior.
danielk19778cbadb02007-05-03 16:31:26 +00004666*/
danielk1977b4e9af92007-05-01 17:49:49 +00004667int sqlite3_blob_bytes(sqlite3_blob *);
4668
drh9eff6162006-06-12 21:59:13 +00004669/*
drhd68eee02009-12-11 03:44:18 +00004670** CAPI3REF: Read Data From A BLOB Incrementally
drh6ed48bf2007-06-14 20:57:18 +00004671**
drhd68eee02009-12-11 03:44:18 +00004672** ^(This function is used to read data from an open [BLOB handle] into a
mihailim15194222008-06-22 09:55:14 +00004673** caller-supplied buffer. N bytes of data are copied into buffer Z
drhd68eee02009-12-11 03:44:18 +00004674** from the open BLOB, starting at offset iOffset.)^
danielk19778cbadb02007-05-03 16:31:26 +00004675**
drhd68eee02009-12-11 03:44:18 +00004676** ^If offset iOffset is less than N bytes from the end of the BLOB,
4677** [SQLITE_ERROR] is returned and no data is read. ^If N or iOffset is
mihailim15194222008-06-22 09:55:14 +00004678** less than zero, [SQLITE_ERROR] is returned and no data is read.
drhd68eee02009-12-11 03:44:18 +00004679** ^The size of the blob (and hence the maximum value of N+iOffset)
drhabda6112009-05-14 22:37:47 +00004680** can be determined using the [sqlite3_blob_bytes()] interface.
drhf5befa02007-12-06 02:42:07 +00004681**
drhd68eee02009-12-11 03:44:18 +00004682** ^An attempt to read from an expired [BLOB handle] fails with an
drh9de1b352008-06-26 15:04:57 +00004683** error code of [SQLITE_ABORT].
4684**
drhd68eee02009-12-11 03:44:18 +00004685** ^(On success, sqlite3_blob_read() returns SQLITE_OK.
4686** Otherwise, an [error code] or an [extended error code] is returned.)^
drhb4d58ae2008-02-21 20:17:06 +00004687**
drhabda6112009-05-14 22:37:47 +00004688** This routine only works on a [BLOB handle] which has been created
4689** by a prior successful call to [sqlite3_blob_open()] and which has not
4690** been closed by [sqlite3_blob_close()]. Passing any other pointer in
4691** to this routine results in undefined and probably undesirable behavior.
4692**
4693** See also: [sqlite3_blob_write()].
danielk19778cbadb02007-05-03 16:31:26 +00004694*/
drhb4d58ae2008-02-21 20:17:06 +00004695int sqlite3_blob_read(sqlite3_blob *, void *Z, int N, int iOffset);
danielk19778cbadb02007-05-03 16:31:26 +00004696
4697/*
drhd68eee02009-12-11 03:44:18 +00004698** CAPI3REF: Write Data Into A BLOB Incrementally
drh6ed48bf2007-06-14 20:57:18 +00004699**
drhd68eee02009-12-11 03:44:18 +00004700** ^This function is used to write data into an open [BLOB handle] from a
4701** caller-supplied buffer. ^N bytes of data are copied from the buffer Z
mihailim15194222008-06-22 09:55:14 +00004702** into the open BLOB, starting at offset iOffset.
danielk19778cbadb02007-05-03 16:31:26 +00004703**
drhd68eee02009-12-11 03:44:18 +00004704** ^If the [BLOB handle] passed as the first argument was not opened for
mihailim15194222008-06-22 09:55:14 +00004705** writing (the flags parameter to [sqlite3_blob_open()] was zero),
4706** this function returns [SQLITE_READONLY].
danielk19778cbadb02007-05-03 16:31:26 +00004707**
drhd68eee02009-12-11 03:44:18 +00004708** ^This function may only modify the contents of the BLOB; it is
mihailim15194222008-06-22 09:55:14 +00004709** not possible to increase the size of a BLOB using this API.
drhd68eee02009-12-11 03:44:18 +00004710** ^If offset iOffset is less than N bytes from the end of the BLOB,
4711** [SQLITE_ERROR] is returned and no data is written. ^If N is
drhf5befa02007-12-06 02:42:07 +00004712** less than zero [SQLITE_ERROR] is returned and no data is written.
drhabda6112009-05-14 22:37:47 +00004713** The size of the BLOB (and hence the maximum value of N+iOffset)
4714** can be determined using the [sqlite3_blob_bytes()] interface.
danielk19778cbadb02007-05-03 16:31:26 +00004715**
drhd68eee02009-12-11 03:44:18 +00004716** ^An attempt to write to an expired [BLOB handle] fails with an
4717** error code of [SQLITE_ABORT]. ^Writes to the BLOB that occurred
drh9de1b352008-06-26 15:04:57 +00004718** before the [BLOB handle] expired are not rolled back by the
4719** expiration of the handle, though of course those changes might
4720** have been overwritten by the statement that expired the BLOB handle
4721** or by other independent statements.
4722**
drhd68eee02009-12-11 03:44:18 +00004723** ^(On success, sqlite3_blob_write() returns SQLITE_OK.
4724** Otherwise, an [error code] or an [extended error code] is returned.)^
drhb4d58ae2008-02-21 20:17:06 +00004725**
drhabda6112009-05-14 22:37:47 +00004726** This routine only works on a [BLOB handle] which has been created
4727** by a prior successful call to [sqlite3_blob_open()] and which has not
4728** been closed by [sqlite3_blob_close()]. Passing any other pointer in
4729** to this routine results in undefined and probably undesirable behavior.
4730**
4731** See also: [sqlite3_blob_read()].
danielk19778cbadb02007-05-03 16:31:26 +00004732*/
4733int sqlite3_blob_write(sqlite3_blob *, const void *z, int n, int iOffset);
4734
drhd84f9462007-08-15 11:28:56 +00004735/*
drhd68eee02009-12-11 03:44:18 +00004736** CAPI3REF: Virtual File System Objects
drhd84f9462007-08-15 11:28:56 +00004737**
4738** A virtual filesystem (VFS) is an [sqlite3_vfs] object
4739** that SQLite uses to interact
drhb4d58ae2008-02-21 20:17:06 +00004740** with the underlying operating system. Most SQLite builds come with a
drhd84f9462007-08-15 11:28:56 +00004741** single default VFS that is appropriate for the host computer.
4742** New VFSes can be registered and existing VFSes can be unregistered.
4743** The following interfaces are provided.
4744**
drhd68eee02009-12-11 03:44:18 +00004745** ^The sqlite3_vfs_find() interface returns a pointer to a VFS given its name.
4746** ^Names are case sensitive.
4747** ^Names are zero-terminated UTF-8 strings.
4748** ^If there is no match, a NULL pointer is returned.
4749** ^If zVfsName is NULL then the default VFS is returned.
drhd84f9462007-08-15 11:28:56 +00004750**
drhd68eee02009-12-11 03:44:18 +00004751** ^New VFSes are registered with sqlite3_vfs_register().
4752** ^Each new VFS becomes the default VFS if the makeDflt flag is set.
4753** ^The same VFS can be registered multiple times without injury.
4754** ^To make an existing VFS into the default VFS, register it again
drhb4d58ae2008-02-21 20:17:06 +00004755** with the makeDflt flag set. If two different VFSes with the
4756** same name are registered, the behavior is undefined. If a
drhb6f5cf32007-08-28 15:21:45 +00004757** VFS is registered with a name that is NULL or an empty string,
4758** then the behavior is undefined.
mihailim15194222008-06-22 09:55:14 +00004759**
drhd68eee02009-12-11 03:44:18 +00004760** ^Unregister a VFS with the sqlite3_vfs_unregister() interface.
4761** ^(If the default VFS is unregistered, another VFS is chosen as
4762** the default. The choice for the new VFS is arbitrary.)^
drhd84f9462007-08-15 11:28:56 +00004763*/
drhd677b3d2007-08-20 22:48:41 +00004764sqlite3_vfs *sqlite3_vfs_find(const char *zVfsName);
drhd677b3d2007-08-20 22:48:41 +00004765int sqlite3_vfs_register(sqlite3_vfs*, int makeDflt);
4766int sqlite3_vfs_unregister(sqlite3_vfs*);
drhd84f9462007-08-15 11:28:56 +00004767
4768/*
drhd68eee02009-12-11 03:44:18 +00004769** CAPI3REF: Mutexes
drhd84f9462007-08-15 11:28:56 +00004770**
4771** The SQLite core uses these routines for thread
danielk19774a9d1f62008-06-19 08:51:23 +00004772** synchronization. Though they are intended for internal
drhd84f9462007-08-15 11:28:56 +00004773** use by SQLite, code that links against SQLite is
4774** permitted to use any of these routines.
4775**
mihailim15194222008-06-22 09:55:14 +00004776** The SQLite source code contains multiple implementations
drh8bacf972007-08-25 16:21:29 +00004777** of these mutex routines. An appropriate implementation
drhd68eee02009-12-11 03:44:18 +00004778** is selected automatically at compile-time. ^(The following
drh8bacf972007-08-25 16:21:29 +00004779** implementations are available in the SQLite core:
drhd84f9462007-08-15 11:28:56 +00004780**
4781** <ul>
drhc7ce76a2007-08-30 14:10:30 +00004782** <li> SQLITE_MUTEX_OS2
drhd84f9462007-08-15 11:28:56 +00004783** <li> SQLITE_MUTEX_PTHREAD
drhc7ce76a2007-08-30 14:10:30 +00004784** <li> SQLITE_MUTEX_W32
drhd84f9462007-08-15 11:28:56 +00004785** <li> SQLITE_MUTEX_NOOP
drhd68eee02009-12-11 03:44:18 +00004786** </ul>)^
drhd84f9462007-08-15 11:28:56 +00004787**
drhd68eee02009-12-11 03:44:18 +00004788** ^The SQLITE_MUTEX_NOOP implementation is a set of routines
mihailim15194222008-06-22 09:55:14 +00004789** that does no real locking and is appropriate for use in
drhd68eee02009-12-11 03:44:18 +00004790** a single-threaded application. ^The SQLITE_MUTEX_OS2,
drhc7ce76a2007-08-30 14:10:30 +00004791** SQLITE_MUTEX_PTHREAD, and SQLITE_MUTEX_W32 implementations
shane26b34032008-05-23 17:21:09 +00004792** are appropriate for use on OS/2, Unix, and Windows.
mihailim15194222008-06-22 09:55:14 +00004793**
drhd68eee02009-12-11 03:44:18 +00004794** ^(If SQLite is compiled with the SQLITE_MUTEX_APPDEF preprocessor
drh8bacf972007-08-25 16:21:29 +00004795** macro defined (with "-DSQLITE_MUTEX_APPDEF=1"), then no mutex
danielk19774a9d1f62008-06-19 08:51:23 +00004796** implementation is included with the library. In this case the
4797** application must supply a custom mutex implementation using the
4798** [SQLITE_CONFIG_MUTEX] option of the sqlite3_config() function
mihailim15194222008-06-22 09:55:14 +00004799** before calling sqlite3_initialize() or any other public sqlite3_
drhd68eee02009-12-11 03:44:18 +00004800** function that calls sqlite3_initialize().)^
drhcb041342008-06-12 00:07:29 +00004801**
drhd68eee02009-12-11 03:44:18 +00004802** ^The sqlite3_mutex_alloc() routine allocates a new
4803** mutex and returns a pointer to it. ^If it returns NULL
4804** that means that a mutex could not be allocated. ^SQLite
4805** will unwind its stack and return an error. ^(The argument
drh6bdec4a2007-08-16 19:40:16 +00004806** to sqlite3_mutex_alloc() is one of these integer constants:
4807**
4808** <ul>
4809** <li> SQLITE_MUTEX_FAST
4810** <li> SQLITE_MUTEX_RECURSIVE
4811** <li> SQLITE_MUTEX_STATIC_MASTER
4812** <li> SQLITE_MUTEX_STATIC_MEM
drh86f8c192007-08-22 00:39:19 +00004813** <li> SQLITE_MUTEX_STATIC_MEM2
drh6bdec4a2007-08-16 19:40:16 +00004814** <li> SQLITE_MUTEX_STATIC_PRNG
danielk19779f61c2f2007-08-27 17:27:49 +00004815** <li> SQLITE_MUTEX_STATIC_LRU
danielk1977dfb316d2008-03-26 18:34:43 +00004816** <li> SQLITE_MUTEX_STATIC_LRU2
drhd68eee02009-12-11 03:44:18 +00004817** </ul>)^
drh6bdec4a2007-08-16 19:40:16 +00004818**
drhd68eee02009-12-11 03:44:18 +00004819** ^The first two constants (SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE)
4820** cause sqlite3_mutex_alloc() to create
4821** a new mutex. ^The new mutex is recursive when SQLITE_MUTEX_RECURSIVE
4822** is used but not necessarily so when SQLITE_MUTEX_FAST is used.
drh6bdec4a2007-08-16 19:40:16 +00004823** The mutex implementation does not need to make a distinction
4824** between SQLITE_MUTEX_RECURSIVE and SQLITE_MUTEX_FAST if it does
drhd68eee02009-12-11 03:44:18 +00004825** not want to. ^SQLite will only request a recursive mutex in
4826** cases where it really needs one. ^If a faster non-recursive mutex
drh6bdec4a2007-08-16 19:40:16 +00004827** implementation is available on the host platform, the mutex subsystem
4828** might return such a mutex in response to SQLITE_MUTEX_FAST.
4829**
drhd68eee02009-12-11 03:44:18 +00004830** ^The other allowed parameters to sqlite3_mutex_alloc() (anything other
4831** than SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE) each return
4832** a pointer to a static preexisting mutex. ^Six static mutexes are
drh6bdec4a2007-08-16 19:40:16 +00004833** used by the current version of SQLite. Future versions of SQLite
4834** may add additional static mutexes. Static mutexes are for internal
4835** use by SQLite only. Applications that use SQLite mutexes should
4836** use only the dynamic mutexes returned by SQLITE_MUTEX_FAST or
4837** SQLITE_MUTEX_RECURSIVE.
4838**
drhd68eee02009-12-11 03:44:18 +00004839** ^Note that if one of the dynamic mutex parameters (SQLITE_MUTEX_FAST
drh6bdec4a2007-08-16 19:40:16 +00004840** or SQLITE_MUTEX_RECURSIVE) is used then sqlite3_mutex_alloc()
drhd68eee02009-12-11 03:44:18 +00004841** returns a different mutex on every call. ^But for the static
drh6bdec4a2007-08-16 19:40:16 +00004842** mutex types, the same mutex is returned on every call that has
mihailim04bcc002008-06-22 10:21:27 +00004843** the same type number.
drhd84f9462007-08-15 11:28:56 +00004844**
drhd68eee02009-12-11 03:44:18 +00004845** ^The sqlite3_mutex_free() routine deallocates a previously
4846** allocated dynamic mutex. ^SQLite is careful to deallocate every
4847** dynamic mutex that it allocates. The dynamic mutexes must not be in
4848** use when they are deallocated. Attempting to deallocate a static
4849** mutex results in undefined behavior. ^SQLite never deallocates
4850** a static mutex.
drhd84f9462007-08-15 11:28:56 +00004851**
drhd68eee02009-12-11 03:44:18 +00004852** ^The sqlite3_mutex_enter() and sqlite3_mutex_try() routines attempt
4853** to enter a mutex. ^If another thread is already within the mutex,
drh6bdec4a2007-08-16 19:40:16 +00004854** sqlite3_mutex_enter() will block and sqlite3_mutex_try() will return
drhd68eee02009-12-11 03:44:18 +00004855** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
4856** upon successful entry. ^(Mutexes created using
drhf5befa02007-12-06 02:42:07 +00004857** SQLITE_MUTEX_RECURSIVE can be entered multiple times by the same thread.
drhd68eee02009-12-11 03:44:18 +00004858** In such cases the,
drh6bdec4a2007-08-16 19:40:16 +00004859** mutex must be exited an equal number of times before another thread
drhd68eee02009-12-11 03:44:18 +00004860** can enter.)^ ^(If the same thread tries to enter any other
drhf5befa02007-12-06 02:42:07 +00004861** kind of mutex more than once, the behavior is undefined.
drhd68eee02009-12-11 03:44:18 +00004862** SQLite will never exhibit
4863** such behavior in its own use of mutexes.)^
drhd84f9462007-08-15 11:28:56 +00004864**
drhd68eee02009-12-11 03:44:18 +00004865** ^(Some systems (for example, Windows 95) do not support the operation
mihailim15194222008-06-22 09:55:14 +00004866** implemented by sqlite3_mutex_try(). On those systems, sqlite3_mutex_try()
drhd68eee02009-12-11 03:44:18 +00004867** will always return SQLITE_BUSY. The SQLite core only ever uses
4868** sqlite3_mutex_try() as an optimization so this is acceptable behavior.)^
drhca49cba2007-09-04 22:31:36 +00004869**
drhd68eee02009-12-11 03:44:18 +00004870** ^The sqlite3_mutex_leave() routine exits a mutex that was
4871** previously entered by the same thread. ^(The behavior
drh8bacf972007-08-25 16:21:29 +00004872** is undefined if the mutex is not currently entered by the
drhd68eee02009-12-11 03:44:18 +00004873** calling thread or is not currently allocated. SQLite will
4874** never do either.)^
drh8bacf972007-08-25 16:21:29 +00004875**
drhd68eee02009-12-11 03:44:18 +00004876** ^If the argument to sqlite3_mutex_enter(), sqlite3_mutex_try(), or
drh40257ff2008-06-13 18:24:27 +00004877** sqlite3_mutex_leave() is a NULL pointer, then all three routines
4878** behave as no-ops.
4879**
drh8bacf972007-08-25 16:21:29 +00004880** See also: [sqlite3_mutex_held()] and [sqlite3_mutex_notheld()].
4881*/
4882sqlite3_mutex *sqlite3_mutex_alloc(int);
4883void sqlite3_mutex_free(sqlite3_mutex*);
4884void sqlite3_mutex_enter(sqlite3_mutex*);
4885int sqlite3_mutex_try(sqlite3_mutex*);
4886void sqlite3_mutex_leave(sqlite3_mutex*);
4887
drh56a40a82008-06-18 13:47:03 +00004888/*
drhd68eee02009-12-11 03:44:18 +00004889** CAPI3REF: Mutex Methods Object
drh56a40a82008-06-18 13:47:03 +00004890**
4891** An instance of this structure defines the low-level routines
danielk19774a9d1f62008-06-19 08:51:23 +00004892** used to allocate and use mutexes.
4893**
4894** Usually, the default mutex implementations provided by SQLite are
mihailim15194222008-06-22 09:55:14 +00004895** sufficient, however the user has the option of substituting a custom
4896** implementation for specialized deployments or systems for which SQLite
danielk19774a9d1f62008-06-19 08:51:23 +00004897** does not provide a suitable implementation. In this case, the user
4898** creates and populates an instance of this structure to pass
mihailim15194222008-06-22 09:55:14 +00004899** to sqlite3_config() along with the [SQLITE_CONFIG_MUTEX] option.
danielk19774a9d1f62008-06-19 08:51:23 +00004900** Additionally, an instance of this structure can be used as an
4901** output variable when querying the system for the current mutex
4902** implementation, using the [SQLITE_CONFIG_GETMUTEX] option.
4903**
drhd68eee02009-12-11 03:44:18 +00004904** ^The xMutexInit method defined by this structure is invoked as
danielk19774a9d1f62008-06-19 08:51:23 +00004905** part of system initialization by the sqlite3_initialize() function.
drhd68eee02009-12-11 03:44:18 +00004906** ^The xMutexInit routine is calle by SQLite exactly once for each
mihailim15194222008-06-22 09:55:14 +00004907** effective call to [sqlite3_initialize()].
danielk19774a9d1f62008-06-19 08:51:23 +00004908**
drhd68eee02009-12-11 03:44:18 +00004909** ^The xMutexEnd method defined by this structure is invoked as
danielk19774a9d1f62008-06-19 08:51:23 +00004910** part of system shutdown by the sqlite3_shutdown() function. The
4911** implementation of this method is expected to release all outstanding
4912** resources obtained by the mutex methods implementation, especially
drhd68eee02009-12-11 03:44:18 +00004913** those obtained by the xMutexInit method. ^The xMutexEnd()
4914** interface is invoked exactly once for each call to [sqlite3_shutdown()].
danielk19774a9d1f62008-06-19 08:51:23 +00004915**
drhd68eee02009-12-11 03:44:18 +00004916** ^(The remaining seven methods defined by this structure (xMutexAlloc,
danielk19774a9d1f62008-06-19 08:51:23 +00004917** xMutexFree, xMutexEnter, xMutexTry, xMutexLeave, xMutexHeld and
4918** xMutexNotheld) implement the following interfaces (respectively):
drh56a40a82008-06-18 13:47:03 +00004919**
4920** <ul>
danielk19774a9d1f62008-06-19 08:51:23 +00004921** <li> [sqlite3_mutex_alloc()] </li>
4922** <li> [sqlite3_mutex_free()] </li>
4923** <li> [sqlite3_mutex_enter()] </li>
4924** <li> [sqlite3_mutex_try()] </li>
4925** <li> [sqlite3_mutex_leave()] </li>
4926** <li> [sqlite3_mutex_held()] </li>
4927** <li> [sqlite3_mutex_notheld()] </li>
drhd68eee02009-12-11 03:44:18 +00004928** </ul>)^
danielk19774a9d1f62008-06-19 08:51:23 +00004929**
4930** The only difference is that the public sqlite3_XXX functions enumerated
4931** above silently ignore any invocations that pass a NULL pointer instead
4932** of a valid mutex handle. The implementations of the methods defined
4933** by this structure are not required to handle this case, the results
4934** of passing a NULL pointer instead of a valid mutex handle are undefined
4935** (i.e. it is acceptable to provide an implementation that segfaults if
4936** it is passed a NULL pointer).
drh9ac06502009-08-17 13:42:29 +00004937**
drhd68eee02009-12-11 03:44:18 +00004938** The xMutexInit() method must be threadsafe. ^It must be harmless to
drh9b8d0272010-08-09 15:44:21 +00004939** invoke xMutexInit() multiple times within the same process and without
drh9ac06502009-08-17 13:42:29 +00004940** intervening calls to xMutexEnd(). Second and subsequent calls to
4941** xMutexInit() must be no-ops.
4942**
drhd68eee02009-12-11 03:44:18 +00004943** ^xMutexInit() must not use SQLite memory allocation ([sqlite3_malloc()]
4944** and its associates). ^Similarly, xMutexAlloc() must not use SQLite memory
4945** allocation for a static mutex. ^However xMutexAlloc() may use SQLite
drh9ac06502009-08-17 13:42:29 +00004946** memory allocation for a fast or recursive mutex.
4947**
drhd68eee02009-12-11 03:44:18 +00004948** ^SQLite will invoke the xMutexEnd() method when [sqlite3_shutdown()] is
drh9ac06502009-08-17 13:42:29 +00004949** called, but only if the prior call to xMutexInit returned SQLITE_OK.
4950** If xMutexInit fails in any way, it is expected to clean up after itself
4951** prior to returning.
drh56a40a82008-06-18 13:47:03 +00004952*/
danielk19776d2ab0e2008-06-17 17:21:18 +00004953typedef struct sqlite3_mutex_methods sqlite3_mutex_methods;
4954struct sqlite3_mutex_methods {
4955 int (*xMutexInit)(void);
danielk19774a9d1f62008-06-19 08:51:23 +00004956 int (*xMutexEnd)(void);
danielk19776d2ab0e2008-06-17 17:21:18 +00004957 sqlite3_mutex *(*xMutexAlloc)(int);
4958 void (*xMutexFree)(sqlite3_mutex *);
4959 void (*xMutexEnter)(sqlite3_mutex *);
4960 int (*xMutexTry)(sqlite3_mutex *);
4961 void (*xMutexLeave)(sqlite3_mutex *);
danielk19776d2ab0e2008-06-17 17:21:18 +00004962 int (*xMutexHeld)(sqlite3_mutex *);
4963 int (*xMutexNotheld)(sqlite3_mutex *);
4964};
4965
drh8bacf972007-08-25 16:21:29 +00004966/*
drhd68eee02009-12-11 03:44:18 +00004967** CAPI3REF: Mutex Verification Routines
drhd677b3d2007-08-20 22:48:41 +00004968**
4969** The sqlite3_mutex_held() and sqlite3_mutex_notheld() routines
drhd68eee02009-12-11 03:44:18 +00004970** are intended for use inside assert() statements. ^The SQLite core
drhf77a2ff2007-08-25 14:49:36 +00004971** never uses these routines except inside an assert() and applications
drhd68eee02009-12-11 03:44:18 +00004972** are advised to follow the lead of the core. ^The SQLite core only
drh8bacf972007-08-25 16:21:29 +00004973** provides implementations for these routines when it is compiled
drhd68eee02009-12-11 03:44:18 +00004974** with the SQLITE_DEBUG flag. ^External mutex implementations
drh8bacf972007-08-25 16:21:29 +00004975** are only required to provide these routines if SQLITE_DEBUG is
4976** defined and if NDEBUG is not defined.
4977**
drhd68eee02009-12-11 03:44:18 +00004978** ^These routines should return true if the mutex in their argument
mihailim04bcc002008-06-22 10:21:27 +00004979** is held or not held, respectively, by the calling thread.
drh8bacf972007-08-25 16:21:29 +00004980**
drhd68eee02009-12-11 03:44:18 +00004981** ^The implementation is not required to provided versions of these
mihailim04bcc002008-06-22 10:21:27 +00004982** routines that actually work. If the implementation does not provide working
4983** versions of these routines, it should at least provide stubs that always
4984** return true so that one does not get spurious assertion failures.
drhd677b3d2007-08-20 22:48:41 +00004985**
drhd68eee02009-12-11 03:44:18 +00004986** ^If the argument to sqlite3_mutex_held() is a NULL pointer then
4987** the routine should return 1. This seems counter-intuitive since
drhd677b3d2007-08-20 22:48:41 +00004988** clearly the mutex cannot be held if it does not exist. But the
4989** the reason the mutex does not exist is because the build is not
4990** using mutexes. And we do not want the assert() containing the
4991** call to sqlite3_mutex_held() to fail, so a non-zero return is
drhd68eee02009-12-11 03:44:18 +00004992** the appropriate thing to do. ^The sqlite3_mutex_notheld()
drhd677b3d2007-08-20 22:48:41 +00004993** interface should also return 1 when given a NULL pointer.
drhd84f9462007-08-15 11:28:56 +00004994*/
drh0edb3cf2009-12-10 01:17:29 +00004995#ifndef NDEBUG
drhd677b3d2007-08-20 22:48:41 +00004996int sqlite3_mutex_held(sqlite3_mutex*);
4997int sqlite3_mutex_notheld(sqlite3_mutex*);
drh0edb3cf2009-12-10 01:17:29 +00004998#endif
drh32bc3f62007-08-21 20:25:39 +00004999
5000/*
drhd68eee02009-12-11 03:44:18 +00005001** CAPI3REF: Mutex Types
drh32bc3f62007-08-21 20:25:39 +00005002**
drhd5a68d32008-08-04 13:44:57 +00005003** The [sqlite3_mutex_alloc()] interface takes a single argument
mihailim04bcc002008-06-22 10:21:27 +00005004** which is one of these integer constants.
drhd5a68d32008-08-04 13:44:57 +00005005**
5006** The set of static mutexes may change from one SQLite release to the
5007** next. Applications that override the built-in mutex logic must be
5008** prepared to accommodate additional static mutexes.
drh32bc3f62007-08-21 20:25:39 +00005009*/
drh6bdec4a2007-08-16 19:40:16 +00005010#define SQLITE_MUTEX_FAST 0
5011#define SQLITE_MUTEX_RECURSIVE 1
5012#define SQLITE_MUTEX_STATIC_MASTER 2
drh86f8c192007-08-22 00:39:19 +00005013#define SQLITE_MUTEX_STATIC_MEM 3 /* sqlite3_malloc() */
drh7555d8e2009-03-20 13:15:30 +00005014#define SQLITE_MUTEX_STATIC_MEM2 4 /* NOT USED */
5015#define SQLITE_MUTEX_STATIC_OPEN 4 /* sqlite3BtreeOpen() */
drh86f8c192007-08-22 00:39:19 +00005016#define SQLITE_MUTEX_STATIC_PRNG 5 /* sqlite3_random() */
danielk19779f61c2f2007-08-27 17:27:49 +00005017#define SQLITE_MUTEX_STATIC_LRU 6 /* lru page list */
danielk1977dfb316d2008-03-26 18:34:43 +00005018#define SQLITE_MUTEX_STATIC_LRU2 7 /* lru page list */
drh6d2069d2007-08-14 01:58:53 +00005019
drhcc6bb3e2007-08-31 16:11:35 +00005020/*
drhd68eee02009-12-11 03:44:18 +00005021** CAPI3REF: Retrieve the mutex for a database connection
drh4413d0e2008-11-04 13:46:27 +00005022**
drhd68eee02009-12-11 03:44:18 +00005023** ^This interface returns a pointer the [sqlite3_mutex] object that
drh4413d0e2008-11-04 13:46:27 +00005024** serializes access to the [database connection] given in the argument
5025** when the [threading mode] is Serialized.
drhd68eee02009-12-11 03:44:18 +00005026** ^If the [threading mode] is Single-thread or Multi-thread then this
drh4413d0e2008-11-04 13:46:27 +00005027** routine returns a NULL pointer.
5028*/
5029sqlite3_mutex *sqlite3_db_mutex(sqlite3*);
5030
5031/*
drhfb434032009-12-11 23:11:26 +00005032** CAPI3REF: Low-Level Control Of Database Files
drhcc6bb3e2007-08-31 16:11:35 +00005033**
drhd68eee02009-12-11 03:44:18 +00005034** ^The [sqlite3_file_control()] interface makes a direct call to the
drhcc6bb3e2007-08-31 16:11:35 +00005035** xFileControl method for the [sqlite3_io_methods] object associated
drhd68eee02009-12-11 03:44:18 +00005036** with a particular database identified by the second argument. ^The
5037** name of the database "main" for the main database or "temp" for the
5038** TEMP database, or the name that appears after the AS keyword for
5039** databases that are added using the [ATTACH] SQL command.
5040** ^A NULL pointer can be used in place of "main" to refer to the
5041** main database file.
5042** ^The third and fourth parameters to this routine
drhcc6bb3e2007-08-31 16:11:35 +00005043** are passed directly through to the second and third parameters of
drhd68eee02009-12-11 03:44:18 +00005044** the xFileControl method. ^The return value of the xFileControl
drhcc6bb3e2007-08-31 16:11:35 +00005045** method becomes the return value of this routine.
5046**
drhd68eee02009-12-11 03:44:18 +00005047** ^If the second parameter (zDbName) does not match the name of any
5048** open database file, then SQLITE_ERROR is returned. ^This error
drhcc6bb3e2007-08-31 16:11:35 +00005049** code is not remembered and will not be recalled by [sqlite3_errcode()]
drhd68eee02009-12-11 03:44:18 +00005050** or [sqlite3_errmsg()]. The underlying xFileControl method might
5051** also return SQLITE_ERROR. There is no way to distinguish between
drhcc6bb3e2007-08-31 16:11:35 +00005052** an incorrect zDbName and an SQLITE_ERROR return from the underlying
drhd68eee02009-12-11 03:44:18 +00005053** xFileControl method.
drh4ff7fa02007-09-01 18:17:21 +00005054**
5055** See also: [SQLITE_FCNTL_LOCKSTATE]
drhcc6bb3e2007-08-31 16:11:35 +00005056*/
5057int sqlite3_file_control(sqlite3*, const char *zDbName, int op, void*);
drh6d2069d2007-08-14 01:58:53 +00005058
danielk19778cbadb02007-05-03 16:31:26 +00005059/*
drhd68eee02009-12-11 03:44:18 +00005060** CAPI3REF: Testing Interface
drhed13d982008-01-31 14:43:24 +00005061**
drhd68eee02009-12-11 03:44:18 +00005062** ^The sqlite3_test_control() interface is used to read out internal
drhed13d982008-01-31 14:43:24 +00005063** state of SQLite and to inject faults into SQLite for testing
drhd68eee02009-12-11 03:44:18 +00005064** purposes. ^The first parameter is an operation code that determines
drhed13d982008-01-31 14:43:24 +00005065** the number, meaning, and operation of all subsequent parameters.
5066**
5067** This interface is not for use by applications. It exists solely
5068** for verifying the correct operation of the SQLite library. Depending
5069** on how the SQLite library is compiled, this interface might not exist.
5070**
5071** The details of the operation codes, their meanings, the parameters
5072** they take, and what they do are all subject to change without notice.
5073** Unlike most of the SQLite API, this function is not guaranteed to
5074** operate consistently from one release to the next.
5075*/
5076int sqlite3_test_control(int op, ...);
5077
5078/*
drhd68eee02009-12-11 03:44:18 +00005079** CAPI3REF: Testing Interface Operation Codes
drhed13d982008-01-31 14:43:24 +00005080**
5081** These constants are the valid operation code parameters used
5082** as the first argument to [sqlite3_test_control()].
5083**
shane26b34032008-05-23 17:21:09 +00005084** These parameters and their meanings are subject to change
drhed13d982008-01-31 14:43:24 +00005085** without notice. These values are for testing purposes only.
5086** Applications should not use any of these parameters or the
5087** [sqlite3_test_control()] interface.
5088*/
drh07096f62009-12-22 23:52:32 +00005089#define SQLITE_TESTCTRL_FIRST 5
drh2fa18682008-03-19 14:15:34 +00005090#define SQLITE_TESTCTRL_PRNG_SAVE 5
5091#define SQLITE_TESTCTRL_PRNG_RESTORE 6
5092#define SQLITE_TESTCTRL_PRNG_RESET 7
drh3088d592008-03-21 16:45:47 +00005093#define SQLITE_TESTCTRL_BITVEC_TEST 8
danielk1977d09414c2008-06-19 18:17:49 +00005094#define SQLITE_TESTCTRL_FAULT_INSTALL 9
danielk19772d1d86f2008-06-20 14:59:51 +00005095#define SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS 10
drhc7a3bb92009-02-05 16:31:45 +00005096#define SQLITE_TESTCTRL_PENDING_BYTE 11
drhf3af63f2009-05-09 18:59:42 +00005097#define SQLITE_TESTCTRL_ASSERT 12
5098#define SQLITE_TESTCTRL_ALWAYS 13
drhc046e3e2009-07-15 11:26:44 +00005099#define SQLITE_TESTCTRL_RESERVE 14
drh07096f62009-12-22 23:52:32 +00005100#define SQLITE_TESTCTRL_OPTIMIZATIONS 15
drh0e857732010-01-02 03:21:35 +00005101#define SQLITE_TESTCTRL_ISKEYWORD 16
drh23e35722010-06-10 14:07:40 +00005102#define SQLITE_TESTCTRL_PGHDRSZ 17
5103#define SQLITE_TESTCTRL_LAST 17
drhed13d982008-01-31 14:43:24 +00005104
drhf7141992008-06-19 00:16:08 +00005105/*
drhd68eee02009-12-11 03:44:18 +00005106** CAPI3REF: SQLite Runtime Status
drhf7141992008-06-19 00:16:08 +00005107**
drhd68eee02009-12-11 03:44:18 +00005108** ^This interface is used to retrieve runtime status information
drh9b8d0272010-08-09 15:44:21 +00005109** about the performance of SQLite, and optionally to reset various
drhd68eee02009-12-11 03:44:18 +00005110** highwater marks. ^The first argument is an integer code for
drhdf6473a2009-12-13 22:20:08 +00005111** the specific parameter to measure. ^(Recognized integer codes
5112** are of the form [SQLITE_STATUS_MEMORY_USED | SQLITE_STATUS_...].)^
drhd68eee02009-12-11 03:44:18 +00005113** ^The current value of the parameter is returned into *pCurrent.
5114** ^The highest recorded value is returned in *pHighwater. ^If the
drhf7141992008-06-19 00:16:08 +00005115** resetFlag is true, then the highest record value is reset after
drhd68eee02009-12-11 03:44:18 +00005116** *pHighwater is written. ^(Some parameters do not record the highest
drhf7141992008-06-19 00:16:08 +00005117** value. For those parameters
drhd68eee02009-12-11 03:44:18 +00005118** nothing is written into *pHighwater and the resetFlag is ignored.)^
5119** ^(Other parameters record only the highwater mark and not the current
5120** value. For these latter parameters nothing is written into *pCurrent.)^
drhf7141992008-06-19 00:16:08 +00005121**
drhd68eee02009-12-11 03:44:18 +00005122** ^The sqlite3_db_status() routine returns SQLITE_OK on success and a
5123** non-zero [error code] on failure.
drhf7141992008-06-19 00:16:08 +00005124**
drh6aa5f152009-08-19 15:57:07 +00005125** This routine is threadsafe but is not atomic. This routine can be
drhf7141992008-06-19 00:16:08 +00005126** called while other threads are running the same or different SQLite
5127** interfaces. However the values returned in *pCurrent and
5128** *pHighwater reflect the status of SQLite at different points in time
5129** and it is possible that another thread might change the parameter
5130** in between the times when *pCurrent and *pHighwater are written.
5131**
drh2462e322008-07-31 14:47:54 +00005132** See also: [sqlite3_db_status()]
drhf7141992008-06-19 00:16:08 +00005133*/
drh9f8da322010-03-10 20:06:37 +00005134int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetFlag);
drh2462e322008-07-31 14:47:54 +00005135
danielk1977075c23a2008-09-01 18:34:20 +00005136
drhf7141992008-06-19 00:16:08 +00005137/*
drhd68eee02009-12-11 03:44:18 +00005138** CAPI3REF: Status Parameters
drhf7141992008-06-19 00:16:08 +00005139**
5140** These integer constants designate various run-time status parameters
5141** that can be returned by [sqlite3_status()].
5142**
5143** <dl>
drhd68eee02009-12-11 03:44:18 +00005144** ^(<dt>SQLITE_STATUS_MEMORY_USED</dt>
drhf7141992008-06-19 00:16:08 +00005145** <dd>This parameter is the current amount of memory checked out
mihailim15194222008-06-22 09:55:14 +00005146** using [sqlite3_malloc()], either directly or indirectly. The
drhf7141992008-06-19 00:16:08 +00005147** figure includes calls made to [sqlite3_malloc()] by the application
5148** and internal memory usage by the SQLite library. Scratch memory
5149** controlled by [SQLITE_CONFIG_SCRATCH] and auxiliary page-cache
5150** memory controlled by [SQLITE_CONFIG_PAGECACHE] is not included in
5151** this parameter. The amount returned is the sum of the allocation
drhd68eee02009-12-11 03:44:18 +00005152** sizes as reported by the xSize method in [sqlite3_mem_methods].</dd>)^
drhf7141992008-06-19 00:16:08 +00005153**
drhd68eee02009-12-11 03:44:18 +00005154** ^(<dt>SQLITE_STATUS_MALLOC_SIZE</dt>
drhe50135e2008-08-05 17:53:22 +00005155** <dd>This parameter records the largest memory allocation request
5156** handed to [sqlite3_malloc()] or [sqlite3_realloc()] (or their
5157** internal equivalents). Only the value returned in the
5158** *pHighwater parameter to [sqlite3_status()] is of interest.
drhd68eee02009-12-11 03:44:18 +00005159** The value written into the *pCurrent parameter is undefined.</dd>)^
drhe50135e2008-08-05 17:53:22 +00005160**
drh154a3192010-07-28 15:49:02 +00005161** ^(<dt>SQLITE_STATUS_MALLOC_COUNT</dt>
5162** <dd>This parameter records the number of separate memory allocations.</dd>)^
5163**
drhd68eee02009-12-11 03:44:18 +00005164** ^(<dt>SQLITE_STATUS_PAGECACHE_USED</dt>
drhf7141992008-06-19 00:16:08 +00005165** <dd>This parameter returns the number of pages used out of the
drhe50135e2008-08-05 17:53:22 +00005166** [pagecache memory allocator] that was configured using
5167** [SQLITE_CONFIG_PAGECACHE]. The
drhd68eee02009-12-11 03:44:18 +00005168** value returned is in pages, not in bytes.</dd>)^
drhf7141992008-06-19 00:16:08 +00005169**
drhd68eee02009-12-11 03:44:18 +00005170** ^(<dt>SQLITE_STATUS_PAGECACHE_OVERFLOW</dt>
drhf7141992008-06-19 00:16:08 +00005171** <dd>This parameter returns the number of bytes of page cache
5172** allocation which could not be statisfied by the [SQLITE_CONFIG_PAGECACHE]
drhe50135e2008-08-05 17:53:22 +00005173** buffer and where forced to overflow to [sqlite3_malloc()]. The
5174** returned value includes allocations that overflowed because they
5175** where too large (they were larger than the "sz" parameter to
5176** [SQLITE_CONFIG_PAGECACHE]) and allocations that overflowed because
drhd68eee02009-12-11 03:44:18 +00005177** no space was left in the page cache.</dd>)^
drhe50135e2008-08-05 17:53:22 +00005178**
drhd68eee02009-12-11 03:44:18 +00005179** ^(<dt>SQLITE_STATUS_PAGECACHE_SIZE</dt>
drhe50135e2008-08-05 17:53:22 +00005180** <dd>This parameter records the largest memory allocation request
5181** handed to [pagecache memory allocator]. Only the value returned in the
5182** *pHighwater parameter to [sqlite3_status()] is of interest.
drhd68eee02009-12-11 03:44:18 +00005183** The value written into the *pCurrent parameter is undefined.</dd>)^
drhf7141992008-06-19 00:16:08 +00005184**
drhd68eee02009-12-11 03:44:18 +00005185** ^(<dt>SQLITE_STATUS_SCRATCH_USED</dt>
drhf7141992008-06-19 00:16:08 +00005186** <dd>This parameter returns the number of allocations used out of the
drhe50135e2008-08-05 17:53:22 +00005187** [scratch memory allocator] configured using
drhf7141992008-06-19 00:16:08 +00005188** [SQLITE_CONFIG_SCRATCH]. The value returned is in allocations, not
drhe50135e2008-08-05 17:53:22 +00005189** in bytes. Since a single thread may only have one scratch allocation
drhf7141992008-06-19 00:16:08 +00005190** outstanding at time, this parameter also reports the number of threads
drhd68eee02009-12-11 03:44:18 +00005191** using scratch memory at the same time.</dd>)^
drhf7141992008-06-19 00:16:08 +00005192**
drhd68eee02009-12-11 03:44:18 +00005193** ^(<dt>SQLITE_STATUS_SCRATCH_OVERFLOW</dt>
drhf7141992008-06-19 00:16:08 +00005194** <dd>This parameter returns the number of bytes of scratch memory
5195** allocation which could not be statisfied by the [SQLITE_CONFIG_SCRATCH]
drhe50135e2008-08-05 17:53:22 +00005196** buffer and where forced to overflow to [sqlite3_malloc()]. The values
5197** returned include overflows because the requested allocation was too
5198** larger (that is, because the requested allocation was larger than the
5199** "sz" parameter to [SQLITE_CONFIG_SCRATCH]) and because no scratch buffer
5200** slots were available.
drhd68eee02009-12-11 03:44:18 +00005201** </dd>)^
drhf7141992008-06-19 00:16:08 +00005202**
drhd68eee02009-12-11 03:44:18 +00005203** ^(<dt>SQLITE_STATUS_SCRATCH_SIZE</dt>
drhf7141992008-06-19 00:16:08 +00005204** <dd>This parameter records the largest memory allocation request
drhe50135e2008-08-05 17:53:22 +00005205** handed to [scratch memory allocator]. Only the value returned in the
5206** *pHighwater parameter to [sqlite3_status()] is of interest.
drhd68eee02009-12-11 03:44:18 +00005207** The value written into the *pCurrent parameter is undefined.</dd>)^
drhec424a52008-07-25 15:39:03 +00005208**
drhd68eee02009-12-11 03:44:18 +00005209** ^(<dt>SQLITE_STATUS_PARSER_STACK</dt>
drhec424a52008-07-25 15:39:03 +00005210** <dd>This parameter records the deepest parser stack. It is only
drhd68eee02009-12-11 03:44:18 +00005211** meaningful if SQLite is compiled with [YYTRACKMAXSTACKDEPTH].</dd>)^
drhf7141992008-06-19 00:16:08 +00005212** </dl>
5213**
5214** New status parameters may be added from time to time.
5215*/
5216#define SQLITE_STATUS_MEMORY_USED 0
5217#define SQLITE_STATUS_PAGECACHE_USED 1
5218#define SQLITE_STATUS_PAGECACHE_OVERFLOW 2
5219#define SQLITE_STATUS_SCRATCH_USED 3
5220#define SQLITE_STATUS_SCRATCH_OVERFLOW 4
5221#define SQLITE_STATUS_MALLOC_SIZE 5
drhec424a52008-07-25 15:39:03 +00005222#define SQLITE_STATUS_PARSER_STACK 6
drhe50135e2008-08-05 17:53:22 +00005223#define SQLITE_STATUS_PAGECACHE_SIZE 7
5224#define SQLITE_STATUS_SCRATCH_SIZE 8
drheafc43b2010-07-26 18:43:40 +00005225#define SQLITE_STATUS_MALLOC_COUNT 9
drhf7141992008-06-19 00:16:08 +00005226
drh633e6d52008-07-28 19:34:53 +00005227/*
drhd68eee02009-12-11 03:44:18 +00005228** CAPI3REF: Database Connection Status
drhd1d38482008-10-07 23:46:38 +00005229**
drhd68eee02009-12-11 03:44:18 +00005230** ^This interface is used to retrieve runtime status information
5231** about a single [database connection]. ^The first argument is the
5232** database connection object to be interrogated. ^The second argument
drh63da0892010-03-10 21:42:07 +00005233** is an integer constant, taken from the set of
5234** [SQLITE_DBSTATUS_LOOKASIDE_USED | SQLITE_DBSTATUS_*] macros, that
drh9b8d0272010-08-09 15:44:21 +00005235** determines the parameter to interrogate. The set of
drh63da0892010-03-10 21:42:07 +00005236** [SQLITE_DBSTATUS_LOOKASIDE_USED | SQLITE_DBSTATUS_*] macros is likely
5237** to grow in future releases of SQLite.
drhd1d38482008-10-07 23:46:38 +00005238**
drhd68eee02009-12-11 03:44:18 +00005239** ^The current value of the requested parameter is written into *pCur
5240** and the highest instantaneous value is written into *pHiwtr. ^If
drhd1d38482008-10-07 23:46:38 +00005241** the resetFlg is true, then the highest instantaneous value is
5242** reset back down to the current value.
5243**
5244** See also: [sqlite3_status()] and [sqlite3_stmt_status()].
5245*/
drh9f8da322010-03-10 20:06:37 +00005246int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int resetFlg);
drhd1d38482008-10-07 23:46:38 +00005247
5248/*
drhd68eee02009-12-11 03:44:18 +00005249** CAPI3REF: Status Parameters for database connections
drh633e6d52008-07-28 19:34:53 +00005250**
drh6aa5f152009-08-19 15:57:07 +00005251** These constants are the available integer "verbs" that can be passed as
5252** the second argument to the [sqlite3_db_status()] interface.
5253**
5254** New verbs may be added in future releases of SQLite. Existing verbs
5255** might be discontinued. Applications should check the return code from
5256** [sqlite3_db_status()] to make sure that the call worked.
5257** The [sqlite3_db_status()] interface will return a non-zero error code
5258** if a discontinued or unsupported verb is invoked.
drh633e6d52008-07-28 19:34:53 +00005259**
5260** <dl>
drhd68eee02009-12-11 03:44:18 +00005261** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_USED</dt>
drh633e6d52008-07-28 19:34:53 +00005262** <dd>This parameter returns the number of lookaside memory slots currently
drhd68eee02009-12-11 03:44:18 +00005263** checked out.</dd>)^
drh63da0892010-03-10 21:42:07 +00005264**
drh643f35e2010-07-26 11:59:40 +00005265** ^(<dt>SQLITE_DBSTATUS_CACHE_USED</dt>
5266** <dd>This parameter returns the approximate number of of bytes of heap
5267** memory used by all pager caches associated with the database connection.)^
drh63da0892010-03-10 21:42:07 +00005268** ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_USED is always 0.
drh643f35e2010-07-26 11:59:40 +00005269**
5270** ^(<dt>SQLITE_DBSTATUS_SCHEMA_USED</dt>
5271** <dd>This parameter returns the approximate number of of bytes of heap
drh39539802010-07-28 15:52:09 +00005272** memory used to store the schema for all databases associated
drh643f35e2010-07-26 11:59:40 +00005273** with the connection - main, temp, and any [ATTACH]-ed databases.)^
5274** ^The full amount of memory used by the schemas is reported, even if the
5275** schema memory is shared with other database connections due to
5276** [shared cache mode] being enabled.
5277** ^The highwater mark associated with SQLITE_DBSTATUS_SCHEMA_USED is always 0.
5278**
5279** ^(<dt>SQLITE_DBSTATUS_STMT_USED</dt>
5280** <dd>This parameter returns the approximate number of of bytes of heap
5281** and lookaside memory used by all prepared statements associated with
5282** the database connection.)^
5283** ^The highwater mark associated with SQLITE_DBSTATUS_STMT_USED is always 0.
drh300c18a2010-07-21 16:16:28 +00005284** </dd>
drh633e6d52008-07-28 19:34:53 +00005285** </dl>
5286*/
5287#define SQLITE_DBSTATUS_LOOKASIDE_USED 0
drh63da0892010-03-10 21:42:07 +00005288#define SQLITE_DBSTATUS_CACHE_USED 1
dand46def72010-07-24 11:28:28 +00005289#define SQLITE_DBSTATUS_SCHEMA_USED 2
5290#define SQLITE_DBSTATUS_STMT_USED 3
5291#define SQLITE_DBSTATUS_MAX 3 /* Largest defined DBSTATUS */
drhed13d982008-01-31 14:43:24 +00005292
drhd1d38482008-10-07 23:46:38 +00005293
5294/*
drhd68eee02009-12-11 03:44:18 +00005295** CAPI3REF: Prepared Statement Status
drhd1d38482008-10-07 23:46:38 +00005296**
drhd68eee02009-12-11 03:44:18 +00005297** ^(Each prepared statement maintains various
drhd1d38482008-10-07 23:46:38 +00005298** [SQLITE_STMTSTATUS_SORT | counters] that measure the number
drh9be37f62009-12-12 23:57:36 +00005299** of times it has performed specific operations.)^ These counters can
drhd1d38482008-10-07 23:46:38 +00005300** be used to monitor the performance characteristics of the prepared
5301** statements. For example, if the number of table steps greatly exceeds
5302** the number of table searches or result rows, that would tend to indicate
5303** that the prepared statement is using a full table scan rather than
5304** an index.
5305**
drhd68eee02009-12-11 03:44:18 +00005306** ^(This interface is used to retrieve and reset counter values from
drhd1d38482008-10-07 23:46:38 +00005307** a [prepared statement]. The first argument is the prepared statement
5308** object to be interrogated. The second argument
5309** is an integer code for a specific [SQLITE_STMTSTATUS_SORT | counter]
drhd68eee02009-12-11 03:44:18 +00005310** to be interrogated.)^
5311** ^The current value of the requested counter is returned.
5312** ^If the resetFlg is true, then the counter is reset to zero after this
drhd1d38482008-10-07 23:46:38 +00005313** interface call returns.
5314**
5315** See also: [sqlite3_status()] and [sqlite3_db_status()].
5316*/
drh9f8da322010-03-10 20:06:37 +00005317int sqlite3_stmt_status(sqlite3_stmt*, int op,int resetFlg);
drhd1d38482008-10-07 23:46:38 +00005318
5319/*
drhd68eee02009-12-11 03:44:18 +00005320** CAPI3REF: Status Parameters for prepared statements
drhd1d38482008-10-07 23:46:38 +00005321**
5322** These preprocessor macros define integer codes that name counter
5323** values associated with the [sqlite3_stmt_status()] interface.
5324** The meanings of the various counters are as follows:
5325**
5326** <dl>
5327** <dt>SQLITE_STMTSTATUS_FULLSCAN_STEP</dt>
drhd68eee02009-12-11 03:44:18 +00005328** <dd>^This is the number of times that SQLite has stepped forward in
drhd1d38482008-10-07 23:46:38 +00005329** a table as part of a full table scan. Large numbers for this counter
5330** may indicate opportunities for performance improvement through
5331** careful use of indices.</dd>
5332**
5333** <dt>SQLITE_STMTSTATUS_SORT</dt>
drhd68eee02009-12-11 03:44:18 +00005334** <dd>^This is the number of sort operations that have occurred.
drhd1d38482008-10-07 23:46:38 +00005335** A non-zero value in this counter may indicate an opportunity to
5336** improvement performance through careful use of indices.</dd>
5337**
drha21a64d2010-04-06 22:33:55 +00005338** <dt>SQLITE_STMTSTATUS_AUTOINDEX</dt>
5339** <dd>^This is the number of rows inserted into transient indices that
5340** were created automatically in order to help joins run faster.
5341** A non-zero value in this counter may indicate an opportunity to
5342** improvement performance by adding permanent indices that do not
5343** need to be reinitialized each time the statement is run.</dd>
5344**
drhd1d38482008-10-07 23:46:38 +00005345** </dl>
5346*/
5347#define SQLITE_STMTSTATUS_FULLSCAN_STEP 1
5348#define SQLITE_STMTSTATUS_SORT 2
drha21a64d2010-04-06 22:33:55 +00005349#define SQLITE_STMTSTATUS_AUTOINDEX 3
drhd1d38482008-10-07 23:46:38 +00005350
drhed13d982008-01-31 14:43:24 +00005351/*
drh21614742008-11-18 19:18:08 +00005352** CAPI3REF: Custom Page Cache Object
drh21614742008-11-18 19:18:08 +00005353**
danielk1977bc2ca9e2008-11-13 14:28:28 +00005354** The sqlite3_pcache type is opaque. It is implemented by
5355** the pluggable module. The SQLite core has no knowledge of
5356** its size or internal structure and never deals with the
5357** sqlite3_pcache object except by holding and passing pointers
5358** to the object.
drh21614742008-11-18 19:18:08 +00005359**
5360** See [sqlite3_pcache_methods] for additional information.
danielk1977bc2ca9e2008-11-13 14:28:28 +00005361*/
5362typedef struct sqlite3_pcache sqlite3_pcache;
5363
5364/*
drh21614742008-11-18 19:18:08 +00005365** CAPI3REF: Application Defined Page Cache.
drh67fba282009-08-26 00:26:51 +00005366** KEYWORDS: {page cache}
danielk1977bc2ca9e2008-11-13 14:28:28 +00005367**
drhd68eee02009-12-11 03:44:18 +00005368** ^(The [sqlite3_config]([SQLITE_CONFIG_PCACHE], ...) interface can
danielk1977bc2ca9e2008-11-13 14:28:28 +00005369** register an alternative page cache implementation by passing in an
drhdf6473a2009-12-13 22:20:08 +00005370** instance of the sqlite3_pcache_methods structure.)^ The majority of the
shane7c7c3112009-08-17 15:31:23 +00005371** heap memory used by SQLite is used by the page cache to cache data read
danielk1977bc2ca9e2008-11-13 14:28:28 +00005372** from, or ready to be written to, the database file. By implementing a
5373** custom page cache using this API, an application can control more
shane7c7c3112009-08-17 15:31:23 +00005374** precisely the amount of memory consumed by SQLite, the way in which
drh67fba282009-08-26 00:26:51 +00005375** that memory is allocated and released, and the policies used to
danielk1977bc2ca9e2008-11-13 14:28:28 +00005376** determine exactly which parts of a database file are cached and for
5377** how long.
5378**
drhd68eee02009-12-11 03:44:18 +00005379** ^(The contents of the sqlite3_pcache_methods structure are copied to an
drh67fba282009-08-26 00:26:51 +00005380** internal buffer by SQLite within the call to [sqlite3_config]. Hence
5381** the application may discard the parameter after the call to
drhd68eee02009-12-11 03:44:18 +00005382** [sqlite3_config()] returns.)^
danielk1977bc2ca9e2008-11-13 14:28:28 +00005383**
drhd68eee02009-12-11 03:44:18 +00005384** ^The xInit() method is called once for each call to [sqlite3_initialize()]
drh9be37f62009-12-12 23:57:36 +00005385** (usually only once during the lifetime of the process). ^(The xInit()
5386** method is passed a copy of the sqlite3_pcache_methods.pArg value.)^
5387** ^The xInit() method can set up up global structures and/or any mutexes
5388** required by the custom page cache implementation.
shane7c7c3112009-08-17 15:31:23 +00005389**
drhd68eee02009-12-11 03:44:18 +00005390** ^The xShutdown() method is called from within [sqlite3_shutdown()],
shane7c7c3112009-08-17 15:31:23 +00005391** if the application invokes this API. It can be used to clean up
5392** any outstanding resources before process shutdown, if required.
5393**
drhd68eee02009-12-11 03:44:18 +00005394** ^SQLite holds a [SQLITE_MUTEX_RECURSIVE] mutex when it invokes
5395** the xInit method, so the xInit method need not be threadsafe. ^The
shane7c7c3112009-08-17 15:31:23 +00005396** xShutdown method is only called from [sqlite3_shutdown()] so it does
5397** not need to be threadsafe either. All other methods must be threadsafe
5398** in multithreaded applications.
5399**
drhd68eee02009-12-11 03:44:18 +00005400** ^SQLite will never invoke xInit() more than once without an intervening
shane7c7c3112009-08-17 15:31:23 +00005401** call to xShutdown().
danielk1977bc2ca9e2008-11-13 14:28:28 +00005402**
drhd68eee02009-12-11 03:44:18 +00005403** ^The xCreate() method is used to construct a new cache instance. SQLite
drh67fba282009-08-26 00:26:51 +00005404** will typically create one cache instance for each open database file,
drhd68eee02009-12-11 03:44:18 +00005405** though this is not guaranteed. ^The
danielk1977bc2ca9e2008-11-13 14:28:28 +00005406** first parameter, szPage, is the size in bytes of the pages that must
drhd68eee02009-12-11 03:44:18 +00005407** be allocated by the cache. ^szPage will not be a power of two. ^szPage
drh67fba282009-08-26 00:26:51 +00005408** will the page size of the database file that is to be cached plus an
drhd68eee02009-12-11 03:44:18 +00005409** increment (here called "R") of about 100 or 200. ^SQLite will use the
drh67fba282009-08-26 00:26:51 +00005410** extra R bytes on each page to store metadata about the underlying
5411** database page on disk. The value of R depends
5412** on the SQLite version, the target platform, and how SQLite was compiled.
drhd68eee02009-12-11 03:44:18 +00005413** ^R is constant for a particular build of SQLite. ^The second argument to
drh67fba282009-08-26 00:26:51 +00005414** xCreate(), bPurgeable, is true if the cache being created will
5415** be used to cache database pages of a file stored on disk, or
drhd68eee02009-12-11 03:44:18 +00005416** false if it is used for an in-memory database. ^The cache implementation
drh67fba282009-08-26 00:26:51 +00005417** does not have to do anything special based with the value of bPurgeable;
drhd68eee02009-12-11 03:44:18 +00005418** it is purely advisory. ^On a cache where bPurgeable is false, SQLite will
drh67fba282009-08-26 00:26:51 +00005419** never invoke xUnpin() except to deliberately delete a page.
drhd68eee02009-12-11 03:44:18 +00005420** ^In other words, a cache created with bPurgeable set to false will
drh67fba282009-08-26 00:26:51 +00005421** never contain any unpinned pages.
danielk1977bc2ca9e2008-11-13 14:28:28 +00005422**
drhd68eee02009-12-11 03:44:18 +00005423** ^(The xCachesize() method may be called at any time by SQLite to set the
danielk1977bc2ca9e2008-11-13 14:28:28 +00005424** suggested maximum cache-size (number of pages stored by) the cache
5425** instance passed as the first argument. This is the value configured using
drh7a98b852009-12-13 23:03:01 +00005426** the SQLite "[PRAGMA cache_size]" command.)^ ^As with the bPurgeable
5427** parameter, the implementation is not required to do anything with this
drh67fba282009-08-26 00:26:51 +00005428** value; it is advisory only.
danielk1977bc2ca9e2008-11-13 14:28:28 +00005429**
drhd68eee02009-12-11 03:44:18 +00005430** ^The xPagecount() method should return the number of pages currently
drh67fba282009-08-26 00:26:51 +00005431** stored in the cache.
danielk1977bc2ca9e2008-11-13 14:28:28 +00005432**
drh7a98b852009-12-13 23:03:01 +00005433** ^The xFetch() method is used to fetch a page and return a pointer to it.
5434** ^A 'page', in this context, is a buffer of szPage bytes aligned at an
5435** 8-byte boundary. ^The page to be fetched is determined by the key. ^The
danielk1977bc2ca9e2008-11-13 14:28:28 +00005436** mimimum key value is 1. After it has been retrieved using xFetch, the page
drh67fba282009-08-26 00:26:51 +00005437** is considered to be "pinned".
danielk1977bc2ca9e2008-11-13 14:28:28 +00005438**
drhd68eee02009-12-11 03:44:18 +00005439** ^If the requested page is already in the page cache, then the page cache
drh67fba282009-08-26 00:26:51 +00005440** implementation must return a pointer to the page buffer with its content
drhd68eee02009-12-11 03:44:18 +00005441** intact. ^(If the requested page is not already in the cache, then the
drh67fba282009-08-26 00:26:51 +00005442** behavior of the cache implementation is determined by the value of the
5443** createFlag parameter passed to xFetch, according to the following table:
danielk1977bc2ca9e2008-11-13 14:28:28 +00005444**
5445** <table border=1 width=85% align=center>
drh67fba282009-08-26 00:26:51 +00005446** <tr><th> createFlag <th> Behaviour when page is not already in cache
5447** <tr><td> 0 <td> Do not allocate a new page. Return NULL.
5448** <tr><td> 1 <td> Allocate a new page if it easy and convenient to do so.
5449** Otherwise return NULL.
5450** <tr><td> 2 <td> Make every effort to allocate a new page. Only return
5451** NULL if allocating a new page is effectively impossible.
drhd68eee02009-12-11 03:44:18 +00005452** </table>)^
danielk1977bc2ca9e2008-11-13 14:28:28 +00005453**
drh67fba282009-08-26 00:26:51 +00005454** SQLite will normally invoke xFetch() with a createFlag of 0 or 1. If
5455** a call to xFetch() with createFlag==1 returns NULL, then SQLite will
5456** attempt to unpin one or more cache pages by spilling the content of
5457** pinned pages to disk and synching the operating system disk cache. After
5458** attempting to unpin pages, the xFetch() method will be invoked again with
5459** a createFlag of 2.
5460**
drhd68eee02009-12-11 03:44:18 +00005461** ^xUnpin() is called by SQLite with a pointer to a currently pinned page
5462** as its second argument. ^(If the third parameter, discard, is non-zero,
danielk1977bc2ca9e2008-11-13 14:28:28 +00005463** then the page should be evicted from the cache. In this case SQLite
5464** assumes that the next time the page is retrieved from the cache using
drhd68eee02009-12-11 03:44:18 +00005465** the xFetch() method, it will be zeroed.)^ ^If the discard parameter is
5466** zero, then the page is considered to be unpinned. ^The cache implementation
drh67fba282009-08-26 00:26:51 +00005467** may choose to evict unpinned pages at any time.
danielk1977bc2ca9e2008-11-13 14:28:28 +00005468**
drhd68eee02009-12-11 03:44:18 +00005469** ^(The cache is not required to perform any reference counting. A single
danielk1977bc2ca9e2008-11-13 14:28:28 +00005470** call to xUnpin() unpins the page regardless of the number of prior calls
drhd68eee02009-12-11 03:44:18 +00005471** to xFetch().)^
danielk1977bc2ca9e2008-11-13 14:28:28 +00005472**
drhd68eee02009-12-11 03:44:18 +00005473** ^The xRekey() method is used to change the key value associated with the
5474** page passed as the second argument from oldKey to newKey. ^If the cache
drhb232c232008-11-19 01:20:26 +00005475** previously contains an entry associated with newKey, it should be
drhd68eee02009-12-11 03:44:18 +00005476** discarded. ^Any prior cache entry associated with newKey is guaranteed not
drhb232c232008-11-19 01:20:26 +00005477** to be pinned.
danielk1977bc2ca9e2008-11-13 14:28:28 +00005478**
drhd68eee02009-12-11 03:44:18 +00005479** ^When SQLite calls the xTruncate() method, the cache must discard all
danielk1977bc2ca9e2008-11-13 14:28:28 +00005480** existing cache entries with page numbers (keys) greater than or equal
drhd68eee02009-12-11 03:44:18 +00005481** to the value of the iLimit parameter passed to xTruncate(). ^If any
danielk1977bc2ca9e2008-11-13 14:28:28 +00005482** of these pages are pinned, they are implicitly unpinned, meaning that
5483** they can be safely discarded.
5484**
drhd68eee02009-12-11 03:44:18 +00005485** ^The xDestroy() method is used to delete a cache allocated by xCreate().
5486** All resources associated with the specified cache should be freed. ^After
drh21614742008-11-18 19:18:08 +00005487** calling the xDestroy() method, SQLite considers the [sqlite3_pcache*]
danielk1977bc2ca9e2008-11-13 14:28:28 +00005488** handle invalid, and will not use it with any other sqlite3_pcache_methods
5489** functions.
5490*/
5491typedef struct sqlite3_pcache_methods sqlite3_pcache_methods;
5492struct sqlite3_pcache_methods {
5493 void *pArg;
5494 int (*xInit)(void*);
5495 void (*xShutdown)(void*);
5496 sqlite3_pcache *(*xCreate)(int szPage, int bPurgeable);
5497 void (*xCachesize)(sqlite3_pcache*, int nCachesize);
5498 int (*xPagecount)(sqlite3_pcache*);
5499 void *(*xFetch)(sqlite3_pcache*, unsigned key, int createFlag);
5500 void (*xUnpin)(sqlite3_pcache*, void*, int discard);
5501 void (*xRekey)(sqlite3_pcache*, void*, unsigned oldKey, unsigned newKey);
5502 void (*xTruncate)(sqlite3_pcache*, unsigned iLimit);
5503 void (*xDestroy)(sqlite3_pcache*);
5504};
5505
5506/*
drh27b3b842009-02-03 18:25:13 +00005507** CAPI3REF: Online Backup Object
drh27b3b842009-02-03 18:25:13 +00005508**
5509** The sqlite3_backup object records state information about an ongoing
drhd68eee02009-12-11 03:44:18 +00005510** online backup operation. ^The sqlite3_backup object is created by
drh27b3b842009-02-03 18:25:13 +00005511** a call to [sqlite3_backup_init()] and is destroyed by a call to
5512** [sqlite3_backup_finish()].
drh52224a72009-02-10 13:41:42 +00005513**
5514** See Also: [Using the SQLite Online Backup API]
drh27b3b842009-02-03 18:25:13 +00005515*/
5516typedef struct sqlite3_backup sqlite3_backup;
5517
5518/*
danielk197704103022009-02-03 16:51:24 +00005519** CAPI3REF: Online Backup API.
danielk197704103022009-02-03 16:51:24 +00005520**
drhd68eee02009-12-11 03:44:18 +00005521** The backup API copies the content of one database into another.
5522** It is useful either for creating backups of databases or
danielk197704103022009-02-03 16:51:24 +00005523** for copying in-memory databases to or from persistent files.
5524**
drh52224a72009-02-10 13:41:42 +00005525** See Also: [Using the SQLite Online Backup API]
5526**
drhd68eee02009-12-11 03:44:18 +00005527** ^Exclusive access is required to the destination database for the
5528** duration of the operation. ^However the source database is only
5529** read-locked while it is actually being read; it is not locked
5530** continuously for the entire backup operation. ^Thus, the backup may be
5531** performed on a live source database without preventing other users from
drhdf6473a2009-12-13 22:20:08 +00005532** reading or writing to the source database while the backup is underway.
danielk197704103022009-02-03 16:51:24 +00005533**
drhd68eee02009-12-11 03:44:18 +00005534** ^(To perform a backup operation:
danielk197704103022009-02-03 16:51:24 +00005535** <ol>
drh62b5d2d2009-02-03 18:47:22 +00005536** <li><b>sqlite3_backup_init()</b> is called once to initialize the
5537** backup,
5538** <li><b>sqlite3_backup_step()</b> is called one or more times to transfer
danielk197704103022009-02-03 16:51:24 +00005539** the data between the two databases, and finally
drh62b5d2d2009-02-03 18:47:22 +00005540** <li><b>sqlite3_backup_finish()</b> is called to release all resources
danielk197704103022009-02-03 16:51:24 +00005541** associated with the backup operation.
drhd68eee02009-12-11 03:44:18 +00005542** </ol>)^
danielk197704103022009-02-03 16:51:24 +00005543** There should be exactly one call to sqlite3_backup_finish() for each
5544** successful call to sqlite3_backup_init().
5545**
5546** <b>sqlite3_backup_init()</b>
5547**
drhd68eee02009-12-11 03:44:18 +00005548** ^The D and N arguments to sqlite3_backup_init(D,N,S,M) are the
5549** [database connection] associated with the destination database
5550** and the database name, respectively.
5551** ^The database name is "main" for the main database, "temp" for the
5552** temporary database, or the name specified after the AS keyword in
5553** an [ATTACH] statement for an attached database.
5554** ^The S and M arguments passed to
5555** sqlite3_backup_init(D,N,S,M) identify the [database connection]
5556** and database name of the source database, respectively.
5557** ^The source and destination [database connections] (parameters S and D)
5558** must be different or else sqlite3_backup_init(D,N,S,M) will file with
5559** an error.
danielk197704103022009-02-03 16:51:24 +00005560**
drhd68eee02009-12-11 03:44:18 +00005561** ^If an error occurs within sqlite3_backup_init(D,N,S,M), then NULL is
5562** returned and an error code and error message are store3d in the
5563** destination [database connection] D.
5564** ^The error code and message for the failed call to sqlite3_backup_init()
5565** can be retrieved using the [sqlite3_errcode()], [sqlite3_errmsg()], and/or
5566** [sqlite3_errmsg16()] functions.
5567** ^A successful call to sqlite3_backup_init() returns a pointer to an
5568** [sqlite3_backup] object.
5569** ^The [sqlite3_backup] object may be used with the sqlite3_backup_step() and
danielk197704103022009-02-03 16:51:24 +00005570** sqlite3_backup_finish() functions to perform the specified backup
5571** operation.
5572**
5573** <b>sqlite3_backup_step()</b>
5574**
drhd68eee02009-12-11 03:44:18 +00005575** ^Function sqlite3_backup_step(B,N) will copy up to N pages between
5576** the source and destination databases specified by [sqlite3_backup] object B.
drh9be37f62009-12-12 23:57:36 +00005577** ^If N is negative, all remaining source pages are copied.
drhd68eee02009-12-11 03:44:18 +00005578** ^If sqlite3_backup_step(B,N) successfully copies N pages and there
5579** are still more pages to be copied, then the function resturns [SQLITE_OK].
5580** ^If sqlite3_backup_step(B,N) successfully finishes copying all pages
5581** from source to destination, then it returns [SQLITE_DONE].
5582** ^If an error occurs while running sqlite3_backup_step(B,N),
5583** then an [error code] is returned. ^As well as [SQLITE_OK] and
drh62b5d2d2009-02-03 18:47:22 +00005584** [SQLITE_DONE], a call to sqlite3_backup_step() may return [SQLITE_READONLY],
5585** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
5586** [SQLITE_IOERR_ACCESS | SQLITE_IOERR_XXX] extended error code.
danielk197704103022009-02-03 16:51:24 +00005587**
drh3289c5e2010-05-05 16:23:26 +00005588** ^(The sqlite3_backup_step() might return [SQLITE_READONLY] if
5589** <ol>
5590** <li> the destination database was opened read-only, or
5591** <li> the destination database is using write-ahead-log journaling
5592** and the destination and source page sizes differ, or
5593** <li> The destination database is an in-memory database and the
5594** destination and source page sizes differ.
5595** </ol>)^
danielk197704103022009-02-03 16:51:24 +00005596**
drhd68eee02009-12-11 03:44:18 +00005597** ^If sqlite3_backup_step() cannot obtain a required file-system lock, then
drh62b5d2d2009-02-03 18:47:22 +00005598** the [sqlite3_busy_handler | busy-handler function]
drhd68eee02009-12-11 03:44:18 +00005599** is invoked (if one is specified). ^If the
danielk197704103022009-02-03 16:51:24 +00005600** busy-handler returns non-zero before the lock is available, then
drhd68eee02009-12-11 03:44:18 +00005601** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
5602** sqlite3_backup_step() can be retried later. ^If the source
drh62b5d2d2009-02-03 18:47:22 +00005603** [database connection]
danielk197704103022009-02-03 16:51:24 +00005604** is being used to write to the source database when sqlite3_backup_step()
drhd68eee02009-12-11 03:44:18 +00005605** is called, then [SQLITE_LOCKED] is returned immediately. ^Again, in this
5606** case the call to sqlite3_backup_step() can be retried later on. ^(If
drh62b5d2d2009-02-03 18:47:22 +00005607** [SQLITE_IOERR_ACCESS | SQLITE_IOERR_XXX], [SQLITE_NOMEM], or
5608** [SQLITE_READONLY] is returned, then
danielk197704103022009-02-03 16:51:24 +00005609** there is no point in retrying the call to sqlite3_backup_step(). These
drhd68eee02009-12-11 03:44:18 +00005610** errors are considered fatal.)^ The application must accept
danielk197704103022009-02-03 16:51:24 +00005611** that the backup operation has failed and pass the backup operation handle
5612** to the sqlite3_backup_finish() to release associated resources.
5613**
drhd68eee02009-12-11 03:44:18 +00005614** ^The first call to sqlite3_backup_step() obtains an exclusive lock
5615** on the destination file. ^The exclusive lock is not released until either
danielk197704103022009-02-03 16:51:24 +00005616** sqlite3_backup_finish() is called or the backup operation is complete
drhd68eee02009-12-11 03:44:18 +00005617** and sqlite3_backup_step() returns [SQLITE_DONE]. ^Every call to
5618** sqlite3_backup_step() obtains a [shared lock] on the source database that
5619** lasts for the duration of the sqlite3_backup_step() call.
5620** ^Because the source database is not locked between calls to
5621** sqlite3_backup_step(), the source database may be modified mid-way
5622** through the backup process. ^If the source database is modified by an
danielk197704103022009-02-03 16:51:24 +00005623** external process or via a database connection other than the one being
drhd68eee02009-12-11 03:44:18 +00005624** used by the backup operation, then the backup will be automatically
5625** restarted by the next call to sqlite3_backup_step(). ^If the source
danielk197704103022009-02-03 16:51:24 +00005626** database is modified by the using the same database connection as is used
drhd68eee02009-12-11 03:44:18 +00005627** by the backup operation, then the backup database is automatically
danielk197704103022009-02-03 16:51:24 +00005628** updated at the same time.
5629**
5630** <b>sqlite3_backup_finish()</b>
5631**
drhd68eee02009-12-11 03:44:18 +00005632** When sqlite3_backup_step() has returned [SQLITE_DONE], or when the
5633** application wishes to abandon the backup operation, the application
5634** should destroy the [sqlite3_backup] by passing it to sqlite3_backup_finish().
5635** ^The sqlite3_backup_finish() interfaces releases all
5636** resources associated with the [sqlite3_backup] object.
5637** ^If sqlite3_backup_step() has not yet returned [SQLITE_DONE], then any
5638** active write-transaction on the destination database is rolled back.
5639** The [sqlite3_backup] object is invalid
danielk197704103022009-02-03 16:51:24 +00005640** and may not be used following a call to sqlite3_backup_finish().
5641**
drhd68eee02009-12-11 03:44:18 +00005642** ^The value returned by sqlite3_backup_finish is [SQLITE_OK] if no
5643** sqlite3_backup_step() errors occurred, regardless or whether or not
5644** sqlite3_backup_step() completed.
5645** ^If an out-of-memory condition or IO error occurred during any prior
5646** sqlite3_backup_step() call on the same [sqlite3_backup] object, then
5647** sqlite3_backup_finish() returns the corresponding [error code].
danielk197704103022009-02-03 16:51:24 +00005648**
drhd68eee02009-12-11 03:44:18 +00005649** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
5650** is not a permanent error and does not affect the return value of
danielk197704103022009-02-03 16:51:24 +00005651** sqlite3_backup_finish().
5652**
5653** <b>sqlite3_backup_remaining(), sqlite3_backup_pagecount()</b>
5654**
drhd68eee02009-12-11 03:44:18 +00005655** ^Each call to sqlite3_backup_step() sets two values inside
5656** the [sqlite3_backup] object: the number of pages still to be backed
drh9b8d0272010-08-09 15:44:21 +00005657** up and the total number of pages in the source database file.
drhd68eee02009-12-11 03:44:18 +00005658** The sqlite3_backup_remaining() and sqlite3_backup_pagecount() interfaces
5659** retrieve these two values, respectively.
danielk197704103022009-02-03 16:51:24 +00005660**
drhd68eee02009-12-11 03:44:18 +00005661** ^The values returned by these functions are only updated by
5662** sqlite3_backup_step(). ^If the source database is modified during a backup
danielk197704103022009-02-03 16:51:24 +00005663** operation, then the values are not updated to account for any extra
5664** pages that need to be updated or the size of the source database file
5665** changing.
5666**
5667** <b>Concurrent Usage of Database Handles</b>
5668**
drhd68eee02009-12-11 03:44:18 +00005669** ^The source [database connection] may be used by the application for other
danielk197704103022009-02-03 16:51:24 +00005670** purposes while a backup operation is underway or being initialized.
drhd68eee02009-12-11 03:44:18 +00005671** ^If SQLite is compiled and configured to support threadsafe database
danielk197704103022009-02-03 16:51:24 +00005672** connections, then the source database connection may be used concurrently
5673** from within other threads.
5674**
drhd68eee02009-12-11 03:44:18 +00005675** However, the application must guarantee that the destination
5676** [database connection] is not passed to any other API (by any thread) after
danielk197704103022009-02-03 16:51:24 +00005677** sqlite3_backup_init() is called and before the corresponding call to
drhd68eee02009-12-11 03:44:18 +00005678** sqlite3_backup_finish(). SQLite does not currently check to see
5679** if the application incorrectly accesses the destination [database connection]
5680** and so no error code is reported, but the operations may malfunction
5681** nevertheless. Use of the destination database connection while a
5682** backup is in progress might also also cause a mutex deadlock.
danielk197704103022009-02-03 16:51:24 +00005683**
drhd68eee02009-12-11 03:44:18 +00005684** If running in [shared cache mode], the application must
danielk197704103022009-02-03 16:51:24 +00005685** guarantee that the shared cache used by the destination database
5686** is not accessed while the backup is running. In practice this means
drhd68eee02009-12-11 03:44:18 +00005687** that the application must guarantee that the disk file being
danielk197704103022009-02-03 16:51:24 +00005688** backed up to is not accessed by any connection within the process,
5689** not just the specific connection that was passed to sqlite3_backup_init().
5690**
drh27b3b842009-02-03 18:25:13 +00005691** The [sqlite3_backup] object itself is partially threadsafe. Multiple
danielk197704103022009-02-03 16:51:24 +00005692** threads may safely make multiple concurrent calls to sqlite3_backup_step().
5693** However, the sqlite3_backup_remaining() and sqlite3_backup_pagecount()
5694** APIs are not strictly speaking threadsafe. If they are invoked at the
5695** same time as another thread is invoking sqlite3_backup_step() it is
5696** possible that they return invalid values.
5697*/
danielk197704103022009-02-03 16:51:24 +00005698sqlite3_backup *sqlite3_backup_init(
5699 sqlite3 *pDest, /* Destination database handle */
5700 const char *zDestName, /* Destination database name */
5701 sqlite3 *pSource, /* Source database handle */
5702 const char *zSourceName /* Source database name */
5703);
5704int sqlite3_backup_step(sqlite3_backup *p, int nPage);
5705int sqlite3_backup_finish(sqlite3_backup *p);
5706int sqlite3_backup_remaining(sqlite3_backup *p);
5707int sqlite3_backup_pagecount(sqlite3_backup *p);
5708
5709/*
danielk1977404ca072009-03-16 13:19:36 +00005710** CAPI3REF: Unlock Notification
danielk1977404ca072009-03-16 13:19:36 +00005711**
drhd68eee02009-12-11 03:44:18 +00005712** ^When running in shared-cache mode, a database operation may fail with
drh89487472009-03-16 13:37:02 +00005713** an [SQLITE_LOCKED] error if the required locks on the shared-cache or
danielk1977404ca072009-03-16 13:19:36 +00005714** individual tables within the shared-cache cannot be obtained. See
5715** [SQLite Shared-Cache Mode] for a description of shared-cache locking.
drhd68eee02009-12-11 03:44:18 +00005716** ^This API may be used to register a callback that SQLite will invoke
danielk1977404ca072009-03-16 13:19:36 +00005717** when the connection currently holding the required lock relinquishes it.
drhd68eee02009-12-11 03:44:18 +00005718** ^This API is only available if the library was compiled with the
drh89487472009-03-16 13:37:02 +00005719** [SQLITE_ENABLE_UNLOCK_NOTIFY] C-preprocessor symbol defined.
danielk1977404ca072009-03-16 13:19:36 +00005720**
5721** See Also: [Using the SQLite Unlock Notification Feature].
5722**
drhd68eee02009-12-11 03:44:18 +00005723** ^Shared-cache locks are released when a database connection concludes
danielk1977404ca072009-03-16 13:19:36 +00005724** its current transaction, either by committing it or rolling it back.
5725**
drhd68eee02009-12-11 03:44:18 +00005726** ^When a connection (known as the blocked connection) fails to obtain a
danielk1977404ca072009-03-16 13:19:36 +00005727** shared-cache lock and SQLITE_LOCKED is returned to the caller, the
5728** identity of the database connection (the blocking connection) that
drhd68eee02009-12-11 03:44:18 +00005729** has locked the required resource is stored internally. ^After an
danielk1977404ca072009-03-16 13:19:36 +00005730** application receives an SQLITE_LOCKED error, it may call the
5731** sqlite3_unlock_notify() method with the blocked connection handle as
5732** the first argument to register for a callback that will be invoked
drhd68eee02009-12-11 03:44:18 +00005733** when the blocking connections current transaction is concluded. ^The
danielk1977404ca072009-03-16 13:19:36 +00005734** callback is invoked from within the [sqlite3_step] or [sqlite3_close]
5735** call that concludes the blocking connections transaction.
5736**
drhd68eee02009-12-11 03:44:18 +00005737** ^(If sqlite3_unlock_notify() is called in a multi-threaded application,
danielk1977404ca072009-03-16 13:19:36 +00005738** there is a chance that the blocking connection will have already
5739** concluded its transaction by the time sqlite3_unlock_notify() is invoked.
5740** If this happens, then the specified callback is invoked immediately,
drhd68eee02009-12-11 03:44:18 +00005741** from within the call to sqlite3_unlock_notify().)^
danielk1977404ca072009-03-16 13:19:36 +00005742**
drhd68eee02009-12-11 03:44:18 +00005743** ^If the blocked connection is attempting to obtain a write-lock on a
danielk1977404ca072009-03-16 13:19:36 +00005744** shared-cache table, and more than one other connection currently holds
5745** a read-lock on the same table, then SQLite arbitrarily selects one of
5746** the other connections to use as the blocking connection.
5747**
drhd68eee02009-12-11 03:44:18 +00005748** ^(There may be at most one unlock-notify callback registered by a
danielk1977404ca072009-03-16 13:19:36 +00005749** blocked connection. If sqlite3_unlock_notify() is called when the
5750** blocked connection already has a registered unlock-notify callback,
drh7a98b852009-12-13 23:03:01 +00005751** then the new callback replaces the old.)^ ^If sqlite3_unlock_notify() is
danielk1977404ca072009-03-16 13:19:36 +00005752** called with a NULL pointer as its second argument, then any existing
drh9b8d0272010-08-09 15:44:21 +00005753** unlock-notify callback is canceled. ^The blocked connections
danielk1977404ca072009-03-16 13:19:36 +00005754** unlock-notify callback may also be canceled by closing the blocked
5755** connection using [sqlite3_close()].
5756**
5757** The unlock-notify callback is not reentrant. If an application invokes
5758** any sqlite3_xxx API functions from within an unlock-notify callback, a
5759** crash or deadlock may be the result.
5760**
drhd68eee02009-12-11 03:44:18 +00005761** ^Unless deadlock is detected (see below), sqlite3_unlock_notify() always
danielk1977404ca072009-03-16 13:19:36 +00005762** returns SQLITE_OK.
5763**
5764** <b>Callback Invocation Details</b>
5765**
5766** When an unlock-notify callback is registered, the application provides a
5767** single void* pointer that is passed to the callback when it is invoked.
5768** However, the signature of the callback function allows SQLite to pass
5769** it an array of void* context pointers. The first argument passed to
5770** an unlock-notify callback is a pointer to an array of void* pointers,
5771** and the second is the number of entries in the array.
5772**
5773** When a blocking connections transaction is concluded, there may be
5774** more than one blocked connection that has registered for an unlock-notify
drhd68eee02009-12-11 03:44:18 +00005775** callback. ^If two or more such blocked connections have specified the
danielk1977404ca072009-03-16 13:19:36 +00005776** same callback function, then instead of invoking the callback function
5777** multiple times, it is invoked once with the set of void* context pointers
5778** specified by the blocked connections bundled together into an array.
5779** This gives the application an opportunity to prioritize any actions
5780** related to the set of unblocked database connections.
5781**
5782** <b>Deadlock Detection</b>
5783**
5784** Assuming that after registering for an unlock-notify callback a
5785** database waits for the callback to be issued before taking any further
5786** action (a reasonable assumption), then using this API may cause the
5787** application to deadlock. For example, if connection X is waiting for
5788** connection Y's transaction to be concluded, and similarly connection
5789** Y is waiting on connection X's transaction, then neither connection
5790** will proceed and the system may remain deadlocked indefinitely.
5791**
5792** To avoid this scenario, the sqlite3_unlock_notify() performs deadlock
drhd68eee02009-12-11 03:44:18 +00005793** detection. ^If a given call to sqlite3_unlock_notify() would put the
danielk1977404ca072009-03-16 13:19:36 +00005794** system in a deadlocked state, then SQLITE_LOCKED is returned and no
5795** unlock-notify callback is registered. The system is said to be in
5796** a deadlocked state if connection A has registered for an unlock-notify
5797** callback on the conclusion of connection B's transaction, and connection
5798** B has itself registered for an unlock-notify callback when connection
drhd68eee02009-12-11 03:44:18 +00005799** A's transaction is concluded. ^Indirect deadlock is also detected, so
danielk1977404ca072009-03-16 13:19:36 +00005800** the system is also considered to be deadlocked if connection B has
5801** registered for an unlock-notify callback on the conclusion of connection
drhd68eee02009-12-11 03:44:18 +00005802** C's transaction, where connection C is waiting on connection A. ^Any
danielk1977404ca072009-03-16 13:19:36 +00005803** number of levels of indirection are allowed.
5804**
5805** <b>The "DROP TABLE" Exception</b>
5806**
5807** When a call to [sqlite3_step()] returns SQLITE_LOCKED, it is almost
5808** always appropriate to call sqlite3_unlock_notify(). There is however,
5809** one exception. When executing a "DROP TABLE" or "DROP INDEX" statement,
5810** SQLite checks if there are any currently executing SELECT statements
5811** that belong to the same connection. If there are, SQLITE_LOCKED is
5812** returned. In this case there is no "blocking connection", so invoking
5813** sqlite3_unlock_notify() results in the unlock-notify callback being
5814** invoked immediately. If the application then re-attempts the "DROP TABLE"
5815** or "DROP INDEX" query, an infinite loop might be the result.
5816**
5817** One way around this problem is to check the extended error code returned
drhd68eee02009-12-11 03:44:18 +00005818** by an sqlite3_step() call. ^(If there is a blocking connection, then the
danielk1977404ca072009-03-16 13:19:36 +00005819** extended error code is set to SQLITE_LOCKED_SHAREDCACHE. Otherwise, in
5820** the special "DROP TABLE/INDEX" case, the extended error code is just
drhd68eee02009-12-11 03:44:18 +00005821** SQLITE_LOCKED.)^
danielk1977404ca072009-03-16 13:19:36 +00005822*/
5823int sqlite3_unlock_notify(
5824 sqlite3 *pBlocked, /* Waiting connection */
5825 void (*xNotify)(void **apArg, int nArg), /* Callback function to invoke */
5826 void *pNotifyArg /* Argument to pass to xNotify */
5827);
5828
danielk1977ee0484c2009-07-28 16:44:26 +00005829
5830/*
5831** CAPI3REF: String Comparison
danielk1977ee0484c2009-07-28 16:44:26 +00005832**
drhd68eee02009-12-11 03:44:18 +00005833** ^The [sqlite3_strnicmp()] API allows applications and extensions to
danielk1977ee0484c2009-07-28 16:44:26 +00005834** compare the contents of two buffers containing UTF-8 strings in a
drh9b8d0272010-08-09 15:44:21 +00005835** case-independent fashion, using the same definition of case independence
danielk1977ee0484c2009-07-28 16:44:26 +00005836** that SQLite uses internally when comparing identifiers.
5837*/
5838int sqlite3_strnicmp(const char *, const char *, int);
5839
danielk1977404ca072009-03-16 13:19:36 +00005840/*
drh3f280702010-02-18 18:45:09 +00005841** CAPI3REF: Error Logging Interface
drh3f280702010-02-18 18:45:09 +00005842**
5843** ^The [sqlite3_log()] interface writes a message into the error log
drh71caabf2010-02-26 15:39:24 +00005844** established by the [SQLITE_CONFIG_LOG] option to [sqlite3_config()].
drhbee80652010-02-25 21:27:58 +00005845** ^If logging is enabled, the zFormat string and subsequent arguments are
drhd3d986d2010-03-31 13:57:56 +00005846** used with [sqlite3_snprintf()] to generate the final output string.
drh3f280702010-02-18 18:45:09 +00005847**
5848** The sqlite3_log() interface is intended for use by extensions such as
5849** virtual tables, collating functions, and SQL functions. While there is
5850** nothing to prevent an application from calling sqlite3_log(), doing so
5851** is considered bad form.
drhbee80652010-02-25 21:27:58 +00005852**
5853** The zFormat string must not be NULL.
drh7c0c4602010-03-03 22:25:18 +00005854**
5855** To avoid deadlocks and other threading problems, the sqlite3_log() routine
5856** will not use dynamically allocated memory. The log message is stored in
5857** a fixed-length buffer on the stack. If the log message is longer than
5858** a few hundred characters, it will be truncated to the length of the
5859** buffer.
drh3f280702010-02-18 18:45:09 +00005860*/
drha7564662010-02-22 19:32:31 +00005861void sqlite3_log(int iErrCode, const char *zFormat, ...);
drh3f280702010-02-18 18:45:09 +00005862
5863/*
drh833bf962010-04-28 14:42:19 +00005864** CAPI3REF: Write-Ahead Log Commit Hook
dan8d22a172010-04-19 18:03:51 +00005865**
drh005e19c2010-05-07 13:57:11 +00005866** ^The [sqlite3_wal_hook()] function is used to register a callback that
dan8d22a172010-04-19 18:03:51 +00005867** will be invoked each time a database connection commits data to a
drh005e19c2010-05-07 13:57:11 +00005868** [write-ahead log] (i.e. whenever a transaction is committed in
5869** [journal_mode | journal_mode=WAL mode]).
dan8d22a172010-04-19 18:03:51 +00005870**
drh005e19c2010-05-07 13:57:11 +00005871** ^The callback is invoked by SQLite after the commit has taken place and
dan8d22a172010-04-19 18:03:51 +00005872** the associated write-lock on the database released, so the implementation
drh005e19c2010-05-07 13:57:11 +00005873** may read, write or [checkpoint] the database as required.
dan8d22a172010-04-19 18:03:51 +00005874**
drh005e19c2010-05-07 13:57:11 +00005875** ^The first parameter passed to the callback function when it is invoked
drh833bf962010-04-28 14:42:19 +00005876** is a copy of the third parameter passed to sqlite3_wal_hook() when
drh005e19c2010-05-07 13:57:11 +00005877** registering the callback. ^The second is a copy of the database handle.
5878** ^The third parameter is the name of the database that was written to -
drhcc3af512010-06-15 12:09:06 +00005879** either "main" or the name of an [ATTACH]-ed database. ^The fourth parameter
drh005e19c2010-05-07 13:57:11 +00005880** is the number of pages currently in the write-ahead log file,
5881** including those that were just committed.
dan8d22a172010-04-19 18:03:51 +00005882**
drhcc3af512010-06-15 12:09:06 +00005883** The callback function should normally return [SQLITE_OK]. ^If an error
drh5def0842010-05-05 20:00:25 +00005884** code is returned, that error will propagate back up through the
5885** SQLite code base to cause the statement that provoked the callback
dan982d4c02010-05-15 10:24:46 +00005886** to report an error, though the commit will have still occurred. If the
drhcc3af512010-06-15 12:09:06 +00005887** callback returns [SQLITE_ROW] or [SQLITE_DONE], or if it returns a value
dan982d4c02010-05-15 10:24:46 +00005888** that does not correspond to any valid SQLite error code, the results
5889** are undefined.
dan8d22a172010-04-19 18:03:51 +00005890**
drh005e19c2010-05-07 13:57:11 +00005891** A single database handle may have at most a single write-ahead log callback
5892** registered at one time. ^Calling [sqlite3_wal_hook()] replaces any
drhcc3af512010-06-15 12:09:06 +00005893** previously registered write-ahead log callback. ^Note that the
drh005e19c2010-05-07 13:57:11 +00005894** [sqlite3_wal_autocheckpoint()] interface and the
5895** [wal_autocheckpoint pragma] both invoke [sqlite3_wal_hook()] and will
5896** those overwrite any prior [sqlite3_wal_hook()] settings.
dan8d22a172010-04-19 18:03:51 +00005897*/
drh833bf962010-04-28 14:42:19 +00005898void *sqlite3_wal_hook(
dan8d22a172010-04-19 18:03:51 +00005899 sqlite3*,
5900 int(*)(void *,sqlite3*,const char*,int),
5901 void*
5902);
5903
5904/*
dan586b9c82010-05-03 08:04:49 +00005905** CAPI3REF: Configure an auto-checkpoint
drh324e46d2010-05-03 18:51:41 +00005906**
drh005e19c2010-05-07 13:57:11 +00005907** ^The [sqlite3_wal_autocheckpoint(D,N)] is a wrapper around
drh324e46d2010-05-03 18:51:41 +00005908** [sqlite3_wal_hook()] that causes any database on [database connection] D
drh005e19c2010-05-07 13:57:11 +00005909** to automatically [checkpoint]
drh324e46d2010-05-03 18:51:41 +00005910** after committing a transaction if there are N or
drh005e19c2010-05-07 13:57:11 +00005911** more frames in the [write-ahead log] file. ^Passing zero or
drh324e46d2010-05-03 18:51:41 +00005912** a negative value as the nFrame parameter disables automatic
5913** checkpoints entirely.
5914**
drh005e19c2010-05-07 13:57:11 +00005915** ^The callback registered by this function replaces any existing callback
5916** registered using [sqlite3_wal_hook()]. ^Likewise, registering a callback
drh324e46d2010-05-03 18:51:41 +00005917** using [sqlite3_wal_hook()] disables the automatic checkpoint mechanism
5918** configured by this function.
drh005e19c2010-05-07 13:57:11 +00005919**
5920** ^The [wal_autocheckpoint pragma] can be used to invoke this interface
5921** from SQL.
5922**
5923** ^Every new [database connection] defaults to having the auto-checkpoint
5924** enabled with a threshold of 1000 pages. The use of this interface
5925** is only necessary if the default setting is found to be suboptimal
5926** for a particular application.
dan586b9c82010-05-03 08:04:49 +00005927*/
5928int sqlite3_wal_autocheckpoint(sqlite3 *db, int N);
5929
5930/*
5931** CAPI3REF: Checkpoint a database
drh324e46d2010-05-03 18:51:41 +00005932**
drh005e19c2010-05-07 13:57:11 +00005933** ^The [sqlite3_wal_checkpoint(D,X)] interface causes database named X
5934** on [database connection] D to be [checkpointed]. ^If X is NULL or an
drh324e46d2010-05-03 18:51:41 +00005935** empty string, then a checkpoint is run on all databases of
drh6a2607a2010-05-07 18:23:24 +00005936** connection D. ^If the database connection D is not in
drh005e19c2010-05-07 13:57:11 +00005937** [WAL | write-ahead log mode] then this interface is a harmless no-op.
5938**
drh6a2607a2010-05-07 18:23:24 +00005939** ^The [wal_checkpoint pragma] can be used to invoke this interface
5940** from SQL. ^The [sqlite3_wal_autocheckpoint()] interface and the
drh005e19c2010-05-07 13:57:11 +00005941** [wal_autocheckpoint pragma] can be used to cause this interface to be
5942** run whenever the WAL reaches a certain size threshold.
dan586b9c82010-05-03 08:04:49 +00005943*/
5944int sqlite3_wal_checkpoint(sqlite3 *db, const char *zDb);
5945
5946/*
drhb37df7b2005-10-13 02:09:49 +00005947** Undo the hack that converts floating point types to integer for
5948** builds on processors without floating point support.
5949*/
5950#ifdef SQLITE_OMIT_FLOATING_POINT
5951# undef double
5952#endif
5953
drh382c0242001-10-06 16:33:02 +00005954#ifdef __cplusplus
5955} /* End of the 'extern "C"' block */
5956#endif
danielk19774adee202004-05-08 08:23:19 +00005957#endif