blob: fa6830bd90a93cf11e24748ffd3038f948da12c6 [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
drh75897232000-05-29 14:26:00 +000013** presents to client programs.
14**
danielk1977e965ac72007-06-13 15:22:28 +000015** @(#) $Id: sqlite.h.in,v 1.211 2007/06/13 15:22:28 danielk1977 Exp $
drh75897232000-05-29 14:26:00 +000016*/
drh12057d52004-09-06 17:34:12 +000017#ifndef _SQLITE3_H_
18#define _SQLITE3_H_
drha18c5682000-10-08 22:20:57 +000019#include <stdarg.h> /* Needed for the definition of va_list */
drh75897232000-05-29 14:26:00 +000020
21/*
drh382c0242001-10-06 16:33:02 +000022** Make sure we can call this stuff from C++.
23*/
24#ifdef __cplusplus
25extern "C" {
26#endif
27
28/*
drhb86ccfb2003-01-28 23:13:10 +000029** The version of the SQLite library.
30*/
drh1e284f42004-10-06 15:52:01 +000031#ifdef SQLITE_VERSION
32# undef SQLITE_VERSION
drh1e284f42004-10-06 15:52:01 +000033#endif
danielk197799ba19e2005-02-05 07:33:34 +000034#define SQLITE_VERSION "--VERS--"
35
36/*
37** The format of the version string is "X.Y.Z<trailing string>", where
38** X is the major version number, Y is the minor version number and Z
39** is the release number. The trailing string is often "alpha" or "beta".
40** For example "3.1.1beta".
41**
42** The SQLITE_VERSION_NUMBER is an integer with the value
danielk1977e48b1f12007-05-24 09:44:10 +000043** (X*1000000 + Y*1000 + Z). For example, for version "3.1.1beta",
danielk197799ba19e2005-02-05 07:33:34 +000044** SQLITE_VERSION_NUMBER is set to 3001001. To detect if they are using
45** version 3.1.1 or greater at compile time, programs may use the test
46** (SQLITE_VERSION_NUMBER>=3001001).
47*/
48#ifdef SQLITE_VERSION_NUMBER
49# undef SQLITE_VERSION_NUMBER
50#endif
51#define SQLITE_VERSION_NUMBER --VERSION-NUMBER--
drhb86ccfb2003-01-28 23:13:10 +000052
53/*
drhb217a572000-08-22 13:40:18 +000054** The version string is also compiled into the library so that a program
55** can check to make sure that the lib*.a file and the *.h file are from
drh6f3a3ef2004-08-28 18:21:21 +000056** the same version. The sqlite3_libversion() function returns a pointer
57** to the sqlite3_version variable - useful in DLLs which cannot access
58** global variables.
drhb217a572000-08-22 13:40:18 +000059*/
danielk19776f8a5032004-05-10 10:34:51 +000060extern const char sqlite3_version[];
drha3f70cb2004-09-30 14:24:50 +000061const char *sqlite3_libversion(void);
drh303aaa72000-08-17 10:22:34 +000062
63/*
danielk197799ba19e2005-02-05 07:33:34 +000064** Return the value of the SQLITE_VERSION_NUMBER macro when the
65** library was compiled.
66*/
67int sqlite3_libversion_number(void);
68
69/*
drh75897232000-05-29 14:26:00 +000070** Each open sqlite database is represented by an instance of the
71** following opaque structure.
72*/
drh9bb575f2004-09-06 17:24:11 +000073typedef struct sqlite3 sqlite3;
danielk197765904932004-05-26 06:18:37 +000074
drh75897232000-05-29 14:26:00 +000075
76/*
drhefad9992004-06-22 12:13:55 +000077** Some compilers do not support the "long long" datatype. So we have
78** to do a typedef that for 64-bit integers that depends on what compiler
79** is being used.
80*/
drh27436af2006-03-28 23:57:17 +000081#ifdef SQLITE_INT64_TYPE
drh9b8f4472006-04-04 01:54:55 +000082 typedef SQLITE_INT64_TYPE sqlite_int64;
drh27436af2006-03-28 23:57:17 +000083 typedef unsigned SQLITE_INT64_TYPE sqlite_uint64;
84#elif defined(_MSC_VER) || defined(__BORLANDC__)
drhefad9992004-06-22 12:13:55 +000085 typedef __int64 sqlite_int64;
drh1211de32004-07-26 12:24:22 +000086 typedef unsigned __int64 sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000087#else
88 typedef long long int sqlite_int64;
drh1211de32004-07-26 12:24:22 +000089 typedef unsigned long long int sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000090#endif
91
drhb37df7b2005-10-13 02:09:49 +000092/*
93** If compiling for a processor that lacks floating point support,
94** substitute integer for floating-point
95*/
96#ifdef SQLITE_OMIT_FLOATING_POINT
97# define double sqlite_int64
98#endif
drhefad9992004-06-22 12:13:55 +000099
100/*
drh75897232000-05-29 14:26:00 +0000101** A function to close the database.
102**
103** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +0000104** returned from sqlite3_open() and the corresponding database will by closed.
danielk197796d81f92004-06-19 03:33:57 +0000105**
106** All SQL statements prepared using sqlite3_prepare() or
107** sqlite3_prepare16() must be deallocated using sqlite3_finalize() before
108** this routine is called. Otherwise, SQLITE_BUSY is returned and the
109** database connection remains open.
drh75897232000-05-29 14:26:00 +0000110*/
danielk1977f9d64d22004-06-19 08:18:07 +0000111int sqlite3_close(sqlite3 *);
drh75897232000-05-29 14:26:00 +0000112
113/*
114** The type for a callback function.
115*/
drh12057d52004-09-06 17:34:12 +0000116typedef int (*sqlite3_callback)(void*,int,char**, char**);
drh75897232000-05-29 14:26:00 +0000117
118/*
119** A function to executes one or more statements of SQL.
120**
121** If one or more of the SQL statements are queries, then
122** the callback function specified by the 3rd parameter is
123** invoked once for each row of the query result. This callback
124** should normally return 0. If the callback returns a non-zero
125** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +0000126** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +0000127**
drha09883f2007-01-10 12:57:29 +0000128** The 1st parameter is an arbitrary pointer that is passed
drh75897232000-05-29 14:26:00 +0000129** to the callback function as its first parameter.
130**
131** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +0000132** columns in the query result. The 3rd parameter to the callback
133** is an array of strings holding the values for each column.
134** The 4th parameter to the callback is an array of strings holding
135** the names of each column.
drh75897232000-05-29 14:26:00 +0000136**
137** The callback function may be NULL, even for queries. A NULL
138** callback is not an error. It just means that no callback
139** will be invoked.
140**
141** If an error occurs while parsing or evaluating the SQL (but
142** not while executing the callback) then an appropriate error
143** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +0000144** *errmsg is made to point to that message. The calling function
145** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +0000146** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +0000147** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +0000148**
149** The return value is is SQLITE_OK if there are no errors and
150** some other return code if there is an error. The particular
151** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +0000152**
153** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000154** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +0000155** behavior can be modified somewhat using the sqlite3_busy_handler()
156** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000157*/
danielk19776f8a5032004-05-10 10:34:51 +0000158int sqlite3_exec(
drh12057d52004-09-06 17:34:12 +0000159 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000160 const char *sql, /* SQL to be executed */
drh12057d52004-09-06 17:34:12 +0000161 sqlite3_callback, /* Callback function */
drh75897232000-05-29 14:26:00 +0000162 void *, /* 1st argument to callback function */
163 char **errmsg /* Error msg written here */
164);
165
drh58b95762000-06-02 01:17:37 +0000166/*
danielk19776f8a5032004-05-10 10:34:51 +0000167** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000168*/
drh717e6402001-09-27 03:22:32 +0000169#define SQLITE_OK 0 /* Successful result */
drh15b9a152006-01-31 20:49:13 +0000170/* beginning-of-error-codes */
drh717e6402001-09-27 03:22:32 +0000171#define SQLITE_ERROR 1 /* SQL error or missing database */
drh2db0bbc2005-08-11 02:10:18 +0000172#define SQLITE_INTERNAL 2 /* NOT USED. Internal logic error in SQLite */
drh717e6402001-09-27 03:22:32 +0000173#define SQLITE_PERM 3 /* Access permission denied */
174#define SQLITE_ABORT 4 /* Callback routine requested an abort */
175#define SQLITE_BUSY 5 /* The database file is locked */
176#define SQLITE_LOCKED 6 /* A table in the database is locked */
177#define SQLITE_NOMEM 7 /* A malloc() failed */
178#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000179#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000180#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
181#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
drh2db0bbc2005-08-11 02:10:18 +0000182#define SQLITE_NOTFOUND 12 /* NOT USED. Table or record not found */
drh717e6402001-09-27 03:22:32 +0000183#define SQLITE_FULL 13 /* Insertion failed because database is full */
184#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
drh4f0ee682007-03-30 20:43:40 +0000185#define SQLITE_PROTOCOL 15 /* NOT USED. Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000186#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000187#define SQLITE_SCHEMA 17 /* The database schema changed */
drhc797d4d2007-05-08 01:08:49 +0000188#define SQLITE_TOOBIG 18 /* String or BLOB exceeds size limit */
drh717e6402001-09-27 03:22:32 +0000189#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000190#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000191#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000192#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000193#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000194#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000195#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000196#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000197#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
198#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh15b9a152006-01-31 20:49:13 +0000199/* end-of-error-codes */
drh717e6402001-09-27 03:22:32 +0000200
drhaf9ff332002-01-16 21:00:27 +0000201/*
drh4ac285a2006-09-15 07:28:50 +0000202** Using the sqlite3_extended_result_codes() API, you can cause
203** SQLite to return result codes with additional information in
204** their upper bits. The lower 8 bits will be the same as the
205** primary result codes above. But the upper bits might contain
206** more specific error information.
207**
208** To extract the primary result code from an extended result code,
209** simply mask off the lower 8 bits.
210**
211** primary = extended & 0xff;
212**
213** New result error codes may be added from time to time. Software
214** that uses the extended result codes should plan accordingly and be
215** sure to always handle new unknown codes gracefully.
216**
217** The SQLITE_OK result code will never be extended. It will always
218** be exactly zero.
219**
220** The extended result codes always have the primary result code
221** as a prefix. Primary result codes only contain a single "_"
222** character. Extended result codes contain two or more "_" characters.
223*/
224#define SQLITE_IOERR_READ (SQLITE_IOERR | (1<<8))
225#define SQLITE_IOERR_SHORT_READ (SQLITE_IOERR | (2<<8))
226#define SQLITE_IOERR_WRITE (SQLITE_IOERR | (3<<8))
227#define SQLITE_IOERR_FSYNC (SQLITE_IOERR | (4<<8))
228#define SQLITE_IOERR_DIR_FSYNC (SQLITE_IOERR | (5<<8))
229#define SQLITE_IOERR_TRUNCATE (SQLITE_IOERR | (6<<8))
230#define SQLITE_IOERR_FSTAT (SQLITE_IOERR | (7<<8))
231#define SQLITE_IOERR_UNLOCK (SQLITE_IOERR | (8<<8))
232#define SQLITE_IOERR_RDLOCK (SQLITE_IOERR | (9<<8))
danielk1977979f38e2007-03-27 16:19:51 +0000233#define SQLITE_IOERR_DELETE (SQLITE_IOERR | (10<<8))
danielk1977e965ac72007-06-13 15:22:28 +0000234#define SQLITE_IOERR_BLOCKED (SQLITE_IOERR | (11<<8))
drh4ac285a2006-09-15 07:28:50 +0000235
236/*
237** Enable or disable the extended result codes.
238*/
239int sqlite3_extended_result_codes(sqlite3*, int onoff);
240
241/*
drhaf9ff332002-01-16 21:00:27 +0000242** Each entry in an SQLite table has a unique integer key. (The key is
243** the value of the INTEGER PRIMARY KEY column if there is such a column,
drh930cc582007-03-28 13:07:40 +0000244** otherwise the key is generated automatically. The unique key is always
drhaf9ff332002-01-16 21:00:27 +0000245** available as the ROWID, OID, or _ROWID_ column.) The following routine
246** returns the integer key of the most recent insert in the database.
drhaf9ff332002-01-16 21:00:27 +0000247*/
drhefad9992004-06-22 12:13:55 +0000248sqlite_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000249
drhc8d30ac2002-04-12 10:08:59 +0000250/*
251** This function returns the number of database rows that were changed
drh930cc582007-03-28 13:07:40 +0000252** (or inserted or deleted) by the most recent SQL statement. Only
253** changes that are directly specified by the INSERT, UPDATE, or
254** DELETE statement are counted. Auxiliary changes caused by
255** triggers are not counted. Within the body of a trigger, however,
256** the sqlite3_changes() API can be called to find the number of
257** changes in the most recently completed INSERT, UPDATE, or DELETE
258** statement within the body of the trigger.
drhc8d30ac2002-04-12 10:08:59 +0000259**
260** All changes are counted, even if they were later undone by a
261** ROLLBACK or ABORT. Except, changes associated with creating and
262** dropping tables are not counted.
263**
drh930cc582007-03-28 13:07:40 +0000264** If a callback invokes sqlite3_exec() or sqlite3_step() recursively,
265** then the changes in the inner, recursive call are counted together
266** with the changes in the outer call.
drhc8d30ac2002-04-12 10:08:59 +0000267**
268** SQLite implements the command "DELETE FROM table" without a WHERE clause
269** by dropping and recreating the table. (This is much faster than going
270** through and deleting individual elements form the table.) Because of
271** this optimization, the change count for "DELETE FROM table" will be
272** zero regardless of the number of elements that were originally in the
273** table. To get an accurate count of the number of rows deleted, use
274** "DELETE FROM table WHERE 1" instead.
275*/
danielk1977f9d64d22004-06-19 08:18:07 +0000276int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000277
rdcf146a772004-02-25 22:51:06 +0000278/*
danielk1977b28af712004-06-21 06:50:26 +0000279** This function returns the number of database rows that have been
280** modified by INSERT, UPDATE or DELETE statements since the database handle
281** was opened. This includes UPDATE, INSERT and DELETE statements executed
282** as part of trigger programs. All changes are counted as soon as the
283** statement that makes them is completed (when the statement handle is
284** passed to sqlite3_reset() or sqlite_finalise()).
rdcf146a772004-02-25 22:51:06 +0000285**
286** SQLite implements the command "DELETE FROM table" without a WHERE clause
287** by dropping and recreating the table. (This is much faster than going
288** through and deleting individual elements form the table.) Because of
289** this optimization, the change count for "DELETE FROM table" will be
290** zero regardless of the number of elements that were originally in the
291** table. To get an accurate count of the number of rows deleted, use
292** "DELETE FROM table WHERE 1" instead.
rdcf146a772004-02-25 22:51:06 +0000293*/
danielk1977b28af712004-06-21 06:50:26 +0000294int sqlite3_total_changes(sqlite3*);
295
drh4c504392000-10-16 22:06:40 +0000296/* This function causes any pending database operation to abort and
297** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000298** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000299** or Ctrl-C where the user wants a long query operation to halt
300** immediately.
drh930cc582007-03-28 13:07:40 +0000301**
302** It is safe to call this routine from a different thread that the
303** thread that is currently running the database operation.
drh4c504392000-10-16 22:06:40 +0000304*/
danielk1977f9d64d22004-06-19 08:18:07 +0000305void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000306
drheec553b2000-06-02 01:51:20 +0000307
danielk197761de0d12004-05-27 23:56:16 +0000308/* These functions return true if the given input string comprises
309** one or more complete SQL statements. For the sqlite3_complete() call,
310** the parameter must be a nul-terminated UTF-8 string. For
311** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
312** is required.
drh75897232000-05-29 14:26:00 +0000313**
drh930cc582007-03-28 13:07:40 +0000314** This routine is useful for command-line input to see of the user has
315** entered a complete statement of SQL or if the current statement needs
316** to be continued on the next line. The algorithm is simple. If the
317** last token other than spaces and comments is a semicolon, then return
318** true. Actually, the algorithm is a little more complicated than that
319** in order to deal with triggers, but the basic idea is the same: the
320** statement is not complete unless it ends in a semicolon.
drh75897232000-05-29 14:26:00 +0000321*/
danielk19776f8a5032004-05-10 10:34:51 +0000322int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000323int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000324
drh2dfbbca2000-07-28 14:32:48 +0000325/*
326** This routine identifies a callback function that is invoked
327** whenever an attempt is made to open a database table that is
328** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000329** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000330** it finds a locked table. If the busy callback is not NULL, then
drh86939b52007-01-10 12:54:51 +0000331** sqlite3_exec() invokes the callback with two arguments. The
332** first argument to the handler is a copy of the void* pointer which
333** is the third argument to this routine. The second argument to
334** the handler is the number of times that the busy handler has
335** been invoked for this locking event. If the
danielk19776f8a5032004-05-10 10:34:51 +0000336** busy callback returns 0, then sqlite3_exec() immediately returns
337** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000338** tries to open the table again and the cycle repeats.
339**
drh86939b52007-01-10 12:54:51 +0000340** The presence of a busy handler does not guarantee that
341** it will be invoked when there is lock contention.
342** If SQLite determines that invoking the busy handler could result in
343** a deadlock, it will return SQLITE_BUSY instead.
344** Consider a scenario where one process is holding a read lock that
345** it is trying to promote to a reserved lock and
346** a second process is holding a reserved lock that it is trying
347** to promote to an exclusive lock. The first process cannot proceed
348** because it is blocked by the second and the second process cannot
349** proceed because it is blocked by the first. If both processes
350** invoke the busy handlers, neither will make any progress. Therefore,
351** SQLite returns SQLITE_BUSY for the first process, hoping that this
352** will induce the first process to release its read lock and allow
353** the second process to proceed.
354**
drh2dfbbca2000-07-28 14:32:48 +0000355** The default busy callback is NULL.
356**
357** Sqlite is re-entrant, so the busy handler may start a new query.
drhe2791952007-05-15 02:45:18 +0000358** (It is not clear why anyone would ever want to do this, but it
drh2dfbbca2000-07-28 14:32:48 +0000359** is allowed, in theory.) But the busy handler may not close the
360** database. Closing the database from a busy handler will delete
361** data structures out from under the executing query and will
362** probably result in a coredump.
363*/
danielk1977f9d64d22004-06-19 08:18:07 +0000364int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000365
366/*
367** This routine sets a busy handler that sleeps for a while when a
368** table is locked. The handler will sleep multiple times until
369** at least "ms" milleseconds of sleeping have been done. After
370** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000371** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000372**
373** Calling this routine with an argument less than or equal to zero
374** turns off all busy handlers.
375*/
danielk1977f9d64d22004-06-19 08:18:07 +0000376int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000377
drhe3710332000-09-29 13:30:53 +0000378/*
danielk19776f8a5032004-05-10 10:34:51 +0000379** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000380** Instead of invoking a user-supplied callback for each row of the
381** result, this routine remembers each row of the result in memory
382** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000383** query has finished.
384**
385** As an example, suppose the query result where this table:
386**
387** Name | Age
388** -----------------------
389** Alice | 43
390** Bob | 28
391** Cindy | 21
392**
393** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000394** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000395**
396** azResult[0] = "Name";
397** azResult[1] = "Age";
398** azResult[2] = "Alice";
399** azResult[3] = "43";
400** azResult[4] = "Bob";
401** azResult[5] = "28";
402** azResult[6] = "Cindy";
403** azResult[7] = "21";
404**
405** Notice that there is an extra row of data containing the column
406** headers. But the *nrow return value is still 3. *ncolumn is
407** set to 2. In general, the number of values inserted into azResult
408** will be ((*nrow) + 1)*(*ncolumn).
409**
410** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000411** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000412** release the memory that was malloc-ed. Because of the way the
413** malloc() happens, the calling function must not try to call
danielk197799b214d2005-02-02 01:13:38 +0000414** free() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000415** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000416**
danielk19776f8a5032004-05-10 10:34:51 +0000417** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000418*/
danielk19776f8a5032004-05-10 10:34:51 +0000419int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000420 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000421 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000422 char ***resultp, /* Result written to a char *[] that this points to */
423 int *nrow, /* Number of result rows written here */
424 int *ncolumn, /* Number of result columns written here */
425 char **errmsg /* Error msg written here */
426);
427
428/*
danielk19776f8a5032004-05-10 10:34:51 +0000429** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000430*/
danielk19776f8a5032004-05-10 10:34:51 +0000431void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000432
drha18c5682000-10-08 22:20:57 +0000433/*
drh4f26d6c2004-05-26 23:25:30 +0000434** The following routines are variants of the "sprintf()" from the
435** standard C library. The resulting string is written into memory
436** obtained from malloc() so that there is never a possiblity of buffer
437** overflow. These routines also implement some additional formatting
438** options that are useful for constructing SQL statements.
439**
440** The strings returned by these routines should be freed by calling
441** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000442**
443** All of the usual printf formatting options apply. In addition, there
444** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000445** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000446** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000447** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000448** the string.
449**
450** For example, so some string variable contains text as follows:
451**
452** char *zText = "It's a happy day!";
453**
454** We can use this text in an SQL statement as follows:
455**
drh3224b322005-09-08 10:58:51 +0000456** char *z = sqlite3_mprintf("INSERT INTO TABLES('%q')", zText);
457** sqlite3_exec(db, z, callback1, 0, 0);
458** sqlite3_free(z);
drha18c5682000-10-08 22:20:57 +0000459**
460** Because the %q format string is used, the '\'' character in zText
461** is escaped and the SQL generated is as follows:
462**
463** INSERT INTO table1 VALUES('It''s a happy day!')
464**
465** This is correct. Had we used %s instead of %q, the generated SQL
466** would have looked like this:
467**
468** INSERT INTO table1 VALUES('It's a happy day!');
469**
470** This second example is an SQL syntax error. As a general rule you
471** should always use %q instead of %s when inserting text into a string
472** literal.
473*/
danielk19776f8a5032004-05-10 10:34:51 +0000474char *sqlite3_mprintf(const char*,...);
475char *sqlite3_vmprintf(const char*, va_list);
drhfeac5f82004-08-01 00:10:45 +0000476char *sqlite3_snprintf(int,char*,const char*, ...);
drh5191b7e2002-03-08 02:12:00 +0000477
drh28dd4792006-06-26 21:35:44 +0000478/*
479** SQLite uses its own memory allocator. On many installations, this
480** memory allocator is identical to the standard malloc()/realloc()/free()
481** and can be used interchangable. On others, the implementations are
482** different. For maximum portability, it is best not to mix calls
483** to the standard malloc/realloc/free with the sqlite versions.
484*/
485void *sqlite3_malloc(int);
486void *sqlite3_realloc(void*, int);
487void sqlite3_free(void*);
488
drh1211de32004-07-26 12:24:22 +0000489#ifndef SQLITE_OMIT_AUTHORIZATION
drh5191b7e2002-03-08 02:12:00 +0000490/*
drhed6c8672003-01-12 18:02:16 +0000491** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000492** callback is invoked (at compile-time, not at run-time) for each
493** attempt to access a column of a table in the database. The callback
494** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
495** SQL statement should be aborted with an error and SQLITE_IGNORE
496** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000497*/
danielk19776f8a5032004-05-10 10:34:51 +0000498int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000499 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000500 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000501 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000502);
drh1211de32004-07-26 12:24:22 +0000503#endif
drhed6c8672003-01-12 18:02:16 +0000504
505/*
506** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000507** be one of the values below. These values signify what kind of operation
508** is to be authorized. The 3rd and 4th parameters to the authorization
509** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000510** codes is used as the second parameter. The 5th parameter is the name
511** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000512** is the name of the inner-most trigger or view that is responsible for
513** the access attempt or NULL if this access attempt is directly from
514** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000515**
516** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000517*/
drh77ad4e42003-01-14 02:49:27 +0000518#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000519#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
520#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
521#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
522#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000523#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000524#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000525#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000526#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
527#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000528#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000529#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000530#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000531#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000532#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000533#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000534#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000535#define SQLITE_DROP_VIEW 17 /* View Name NULL */
536#define SQLITE_INSERT 18 /* Table Name NULL */
537#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
538#define SQLITE_READ 20 /* Table Name Column Name */
539#define SQLITE_SELECT 21 /* NULL NULL */
540#define SQLITE_TRANSACTION 22 /* NULL NULL */
541#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000542#define SQLITE_ATTACH 24 /* Filename NULL */
543#define SQLITE_DETACH 25 /* Database Name NULL */
danielk19771c8c23c2004-11-12 15:53:37 +0000544#define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */
danielk19771d54df82004-11-23 15:41:16 +0000545#define SQLITE_REINDEX 27 /* Index Name NULL */
drhe6e04962005-07-23 02:17:03 +0000546#define SQLITE_ANALYZE 28 /* Table Name NULL */
danielk1977f1a381e2006-06-16 08:01:02 +0000547#define SQLITE_CREATE_VTABLE 29 /* Table Name Module Name */
548#define SQLITE_DROP_VTABLE 30 /* Table Name Module Name */
drh5169bbc2006-08-24 14:59:45 +0000549#define SQLITE_FUNCTION 31 /* Function Name NULL */
drhed6c8672003-01-12 18:02:16 +0000550
551/*
552** The return value of the authorization function should be one of the
553** following constants:
554*/
555/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
556#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
557#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
558
559/*
drh19e2d372005-08-29 23:00:03 +0000560** Register a function for tracing SQL command evaluation. The function
561** registered by sqlite3_trace() is invoked at the first sqlite3_step()
562** for the evaluation of an SQL statement. The function registered by
563** sqlite3_profile() runs at the end of each SQL statement and includes
564** information on how long that statement ran.
565**
566** The sqlite3_profile() API is currently considered experimental and
567** is subject to change.
drh18de4822003-01-16 16:28:53 +0000568*/
danielk1977f9d64d22004-06-19 08:18:07 +0000569void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh19e2d372005-08-29 23:00:03 +0000570void *sqlite3_profile(sqlite3*,
571 void(*xProfile)(void*,const char*,sqlite_uint64), void*);
drh18de4822003-01-16 16:28:53 +0000572
danielk1977348bb5d2003-10-18 09:37:26 +0000573/*
574** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000575** is invoked periodically during long running calls to sqlite3_exec(),
danielk19772097e942004-11-20 06:05:56 +0000576** sqlite3_step() and sqlite3_get_table(). An example use for this API is to
577** keep a GUI updated during a large query.
danielk1977348bb5d2003-10-18 09:37:26 +0000578**
579** The progress callback is invoked once for every N virtual machine opcodes,
580** where N is the second argument to this function. The progress callback
581** itself is identified by the third argument to this function. The fourth
582** argument to this function is a void pointer passed to the progress callback
583** function each time it is invoked.
584**
danielk19776f8a5032004-05-10 10:34:51 +0000585** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000586** in less than N opcodes being executed, then the progress callback is not
587** invoked.
588**
danielk1977348bb5d2003-10-18 09:37:26 +0000589** To remove the progress callback altogether, pass NULL as the third
590** argument to this function.
591**
592** If the progress callback returns a result other than 0, then the current
593** query is immediately terminated and any database changes rolled back. If the
594** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000595** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000596**
597******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000598*/
danielk1977f9d64d22004-06-19 08:18:07 +0000599void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000600
drhaa940ea2004-01-15 02:44:03 +0000601/*
602** Register a callback function to be invoked whenever a new transaction
603** is committed. The pArg argument is passed through to the callback.
604** callback. If the callback function returns non-zero, then the commit
605** is converted into a rollback.
606**
607** If another function was previously registered, its pArg value is returned.
608** Otherwise NULL is returned.
609**
610** Registering a NULL function disables the callback.
611**
612******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
613*/
danielk1977f9d64d22004-06-19 08:18:07 +0000614void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000615
drh22fbcb82004-02-01 01:22:50 +0000616/*
drh4f26d6c2004-05-26 23:25:30 +0000617** Open the sqlite database file "filename". The "filename" is UTF-8
618** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
619** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
620** if an error occurs. If the database is opened (or created) successfully,
621** then SQLITE_OK is returned. Otherwise an error code is returned. The
622** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
623** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000624**
drh4f26d6c2004-05-26 23:25:30 +0000625** If the database file does not exist, then a new database is created.
626** The encoding for the database is UTF-8 if sqlite3_open() is called and
627** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000628**
629** Whether or not an error occurs when it is opened, resources associated
630** with the sqlite3* handle should be released by passing it to
631** sqlite3_close() when it is no longer required.
632*/
633int sqlite3_open(
634 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000635 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000636);
danielk197765904932004-05-26 06:18:37 +0000637int sqlite3_open16(
638 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000639 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000640);
danielk1977295ba552004-05-19 10:34:51 +0000641
danielk197765904932004-05-26 06:18:37 +0000642/*
643** Return the error code for the most recent sqlite3_* API call associated
644** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
645** API call was successful.
646**
647** Calls to many sqlite3_* functions set the error code and string returned
648** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
649** (overwriting the previous values). Note that calls to sqlite3_errcode(),
650** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
651** results of future invocations.
652**
653** Assuming no other intervening sqlite3_* API calls are made, the error
654** code returned by this function is associated with the same error as
655** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
656*/
657int sqlite3_errcode(sqlite3 *db);
658
659/*
660** Return a pointer to a UTF-8 encoded string describing in english the
661** error condition for the most recent sqlite3_* API call. The returned
662** string is always terminated by an 0x00 byte.
663**
664** The string "not an error" is returned when the most recent API call was
665** successful.
666*/
667const char *sqlite3_errmsg(sqlite3*);
668
669/*
670** Return a pointer to a UTF-16 native byte order encoded string describing
671** in english the error condition for the most recent sqlite3_* API call.
672** The returned string is always terminated by a pair of 0x00 bytes.
673**
674** The string "not an error" is returned when the most recent API call was
675** successful.
676*/
677const void *sqlite3_errmsg16(sqlite3*);
678
679/*
680** An instance of the following opaque structure is used to represent
681** a compiled SQL statment.
682*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000683typedef struct sqlite3_stmt sqlite3_stmt;
684
danielk1977e3209e42004-05-20 01:40:18 +0000685/*
danielk197765904932004-05-26 06:18:37 +0000686** To execute an SQL query, it must first be compiled into a byte-code
687** program using one of the following routines. The only difference between
688** them is that the second argument, specifying the SQL statement to
689** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
690** function and UTF-16 for sqlite3_prepare16().
691**
692** The first parameter "db" is an SQLite database handle. The second
693** parameter "zSql" is the statement to be compiled, encoded as either
694** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
695** than zero, then zSql is read up to the first nul terminator. If
696** "nBytes" is not less than zero, then it is the length of the string zSql
697** in bytes (not characters).
698**
699** *pzTail is made to point to the first byte past the end of the first
700** SQL statement in zSql. This routine only compiles the first statement
701** in zSql, so *pzTail is left pointing to what remains uncompiled.
702**
703** *ppStmt is left pointing to a compiled SQL statement that can be
704** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
705** set to NULL. If the input text contained no SQL (if the input is and
706** empty string or a comment) then *ppStmt is set to NULL.
707**
708** On success, SQLITE_OK is returned. Otherwise an error code is returned.
709*/
710int sqlite3_prepare(
711 sqlite3 *db, /* Database handle */
712 const char *zSql, /* SQL statement, UTF-8 encoded */
713 int nBytes, /* Length of zSql in bytes. */
714 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
715 const char **pzTail /* OUT: Pointer to unused portion of zSql */
716);
717int sqlite3_prepare16(
718 sqlite3 *db, /* Database handle */
719 const void *zSql, /* SQL statement, UTF-16 encoded */
720 int nBytes, /* Length of zSql in bytes. */
721 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
722 const void **pzTail /* OUT: Pointer to unused portion of zSql */
723);
724
725/*
drhb900aaf2006-11-09 00:24:53 +0000726** Newer versions of the prepare API work just like the legacy versions
727** but with one exception: The a copy of the SQL text is saved in the
728** sqlite3_stmt structure that is returned. If this copy exists, it
729** modifieds the behavior of sqlite3_step() slightly. First, sqlite3_step()
730** will no longer return an SQLITE_SCHEMA error but will instead automatically
731** rerun the compiler to rebuild the prepared statement. Secondly,
732** sqlite3_step() now turns a full result code - the result code that
733** use used to have to call sqlite3_reset() to get.
734*/
735int sqlite3_prepare_v2(
736 sqlite3 *db, /* Database handle */
737 const char *zSql, /* SQL statement, UTF-8 encoded */
738 int nBytes, /* Length of zSql in bytes. */
739 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
740 const char **pzTail /* OUT: Pointer to unused portion of zSql */
741);
742int sqlite3_prepare16_v2(
743 sqlite3 *db, /* Database handle */
744 const void *zSql, /* SQL statement, UTF-16 encoded */
745 int nBytes, /* Length of zSql in bytes. */
746 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
747 const void **pzTail /* OUT: Pointer to unused portion of zSql */
748);
749
750/*
drhf4479502004-05-27 03:12:53 +0000751** Pointers to the following two opaque structures are used to communicate
752** with the implementations of user-defined functions.
753*/
754typedef struct sqlite3_context sqlite3_context;
755typedef struct Mem sqlite3_value;
756
757/*
drh4f26d6c2004-05-26 23:25:30 +0000758** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
drh930cc582007-03-28 13:07:40 +0000759** one or more literals can be replace by parameters "?" or "?NNN" or
760** ":AAA" or "@AAA" or "$VVV" where NNN is a integer, AAA is an identifer,
761** and VVV is a variable name according to the syntax rules of the
762** TCL programming language. The value of these parameters (also called
763** "host parameter names") can be set using the routines listed below.
drh4f26d6c2004-05-26 23:25:30 +0000764**
drh930cc582007-03-28 13:07:40 +0000765** In every case, the first argument is a pointer to the sqlite3_stmt
766** structure returned from sqlite3_prepare(). The second argument is the
767** index of the host parameter name. The first host parameter as an index
768** of 1. For named host parameters (":AAA" or "$VVV") you can use
drh32c0d4f2004-12-07 02:14:51 +0000769** sqlite3_bind_parameter_index() to get the correct index value given
drh930cc582007-03-28 13:07:40 +0000770** the parameter name. If the same named parameter occurs more than
drh32c0d4f2004-12-07 02:14:51 +0000771** once, it is assigned the same index each time.
drh4f26d6c2004-05-26 23:25:30 +0000772**
drh930cc582007-03-28 13:07:40 +0000773** The fifth argument to sqlite3_bind_blob(), sqlite3_bind_text(), and
drh900dfba2004-07-21 15:21:36 +0000774** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or
775** text after SQLite has finished with it. If the fifth argument is the
776** special value SQLITE_STATIC, then the library assumes that the information
777** is in static, unmanaged space and does not need to be freed. If the
778** fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its
drh930cc582007-03-28 13:07:40 +0000779** own private copy of the data before the sqlite3_bind_* routine returns.
drh4f26d6c2004-05-26 23:25:30 +0000780**
drh930cc582007-03-28 13:07:40 +0000781** The sqlite3_bind_* routine must be called before sqlite3_step() and after
782** an sqlite3_prepare() or sqlite3_reset(). Bindings persist across
783** multiple calls to sqlite3_reset() and sqlite3_step(). Unbound parameters
784** are interpreted as NULL.
drh4f26d6c2004-05-26 23:25:30 +0000785*/
danielk1977d8123362004-06-12 09:25:12 +0000786int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000787int sqlite3_bind_double(sqlite3_stmt*, int, double);
788int sqlite3_bind_int(sqlite3_stmt*, int, int);
drhefad9992004-06-22 12:13:55 +0000789int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64);
drhf4479502004-05-27 03:12:53 +0000790int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000791int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
792int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000793int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drhb026e052007-05-02 01:34:31 +0000794int sqlite3_bind_zeroblob(sqlite3_stmt*, int, int n);
drh4f26d6c2004-05-26 23:25:30 +0000795
796/*
drh930cc582007-03-28 13:07:40 +0000797** Return the number of host parameters in a compiled SQL statement. This
drh75f6a032004-07-15 14:15:00 +0000798** routine was added to support DBD::SQLite.
drh75f6a032004-07-15 14:15:00 +0000799*/
800int sqlite3_bind_parameter_count(sqlite3_stmt*);
801
802/*
drh930cc582007-03-28 13:07:40 +0000803** Return the name of the i-th name parameter. Ordinary parameters "?" are
drh32c0d4f2004-12-07 02:14:51 +0000804** nameless and a NULL is returned. For parameters of the form :AAA or
805** $VVV the complete text of the parameter name is returned, including
806** the initial ":" or "$". NULL is returned if the index is out of range.
drh895d7472004-08-20 16:02:39 +0000807*/
808const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
809
810/*
drhfa6bc002004-09-07 16:19:52 +0000811** Return the index of a parameter with the given name. The name
812** must match exactly. If no parameter with the given name is found,
813** return 0.
814*/
815int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
816
817/*
danielk1977600dd0b2005-01-20 01:14:23 +0000818** Set all the parameters in the compiled SQL statement to NULL.
danielk1977600dd0b2005-01-20 01:14:23 +0000819*/
820int sqlite3_clear_bindings(sqlite3_stmt*);
821
822/*
danielk197765904932004-05-26 06:18:37 +0000823** Return the number of columns in the result set returned by the compiled
824** SQL statement. This routine returns 0 if pStmt is an SQL statement
825** that does not return data (for example an UPDATE).
826*/
827int sqlite3_column_count(sqlite3_stmt *pStmt);
828
829/*
830** The first parameter is a compiled SQL statement. This function returns
831** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000832** second function parameter. The string returned is UTF-8 for
833** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000834*/
835const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000836const void *sqlite3_column_name16(sqlite3_stmt*,int);
837
838/*
drh930cc582007-03-28 13:07:40 +0000839** The first argument to the following calls is a compiled SQL statement.
danielk1977955de522006-02-10 02:27:42 +0000840** These functions return information about the Nth column returned by
841** the statement, where N is the second function argument.
842**
843** If the Nth column returned by the statement is not a column value,
844** then all of the functions return NULL. Otherwise, the return the
845** name of the attached database, table and column that the expression
846** extracts a value from.
847**
848** As with all other SQLite APIs, those postfixed with "16" return UTF-16
849** encoded strings, the other functions return UTF-8. The memory containing
850** the returned strings is valid until the statement handle is finalized().
danielk19774b1ae992006-02-10 03:06:10 +0000851**
852** These APIs are only available if the library was compiled with the
853** SQLITE_ENABLE_COLUMN_METADATA preprocessor symbol defined.
danielk1977955de522006-02-10 02:27:42 +0000854*/
855const char *sqlite3_column_database_name(sqlite3_stmt*,int);
856const void *sqlite3_column_database_name16(sqlite3_stmt*,int);
857const char *sqlite3_column_table_name(sqlite3_stmt*,int);
858const void *sqlite3_column_table_name16(sqlite3_stmt*,int);
859const char *sqlite3_column_origin_name(sqlite3_stmt*,int);
860const void *sqlite3_column_origin_name16(sqlite3_stmt*,int);
861
862/*
danielk197765904932004-05-26 06:18:37 +0000863** The first parameter is a compiled SQL statement. If this statement
864** is a SELECT statement, the Nth column of the returned result set
865** of the SELECT is a table column then the declared type of the table
866** column is returned. If the Nth column of the result set is not at table
867** column, then a NULL pointer is returned. The returned string is always
868** UTF-8 encoded. For example, in the database schema:
869**
870** CREATE TABLE t1(c1 VARIANT);
871**
872** And the following statement compiled:
873**
danielk1977955de522006-02-10 02:27:42 +0000874** SELECT c1 + 1, c1 FROM t1;
danielk197765904932004-05-26 06:18:37 +0000875**
876** Then this routine would return the string "VARIANT" for the second
877** result column (i==1), and a NULL pointer for the first result column
878** (i==0).
879*/
880const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
881
882/*
883** The first parameter is a compiled SQL statement. If this statement
884** is a SELECT statement, the Nth column of the returned result set
885** of the SELECT is a table column then the declared type of the table
886** column is returned. If the Nth column of the result set is not at table
887** column, then a NULL pointer is returned. The returned string is always
888** UTF-16 encoded. For example, in the database schema:
889**
drh4f26d6c2004-05-26 23:25:30 +0000890** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000891**
892** And the following statement compiled:
893**
danielk1977955de522006-02-10 02:27:42 +0000894** SELECT c1 + 1, c1 FROM t1;
danielk197765904932004-05-26 06:18:37 +0000895**
drh4f26d6c2004-05-26 23:25:30 +0000896** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000897** result column (i==1), and a NULL pointer for the first result column
898** (i==0).
899*/
900const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
901
danielk1977106bb232004-05-21 10:08:53 +0000902/*
903** After an SQL query has been compiled with a call to either
904** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
905** called one or more times to execute the statement.
906**
907** The return value will be either SQLITE_BUSY, SQLITE_DONE,
908** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
909**
910** SQLITE_BUSY means that the database engine attempted to open
911** a locked database and there is no busy callback registered.
912** Call sqlite3_step() again to retry the open.
913**
914** SQLITE_DONE means that the statement has finished executing
915** successfully. sqlite3_step() should not be called again on this virtual
916** machine.
917**
918** If the SQL statement being executed returns any data, then
919** SQLITE_ROW is returned each time a new row of data is ready
920** for processing by the caller. The values may be accessed using
921** the sqlite3_column_*() functions described below. sqlite3_step()
922** is called again to retrieve the next row of data.
923**
924** SQLITE_ERROR means that a run-time error (such as a constraint
925** violation) has occurred. sqlite3_step() should not be called again on
926** the VM. More information may be found by calling sqlite3_errmsg().
927**
928** SQLITE_MISUSE means that the this routine was called inappropriately.
929** Perhaps it was called on a virtual machine that had already been
930** finalized or on one that had previously returned SQLITE_ERROR or
931** SQLITE_DONE. Or it could be the case the the same database connection
932** is being used simulataneously by two or more threads.
933*/
danielk197717240fd2004-05-26 00:07:25 +0000934int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000935
danielk1977106bb232004-05-21 10:08:53 +0000936/*
937** Return the number of values in the current row of the result set.
938**
939** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
940** will return the same value as the sqlite3_column_count() function.
941** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
942** error code, or before sqlite3_step() has been called on a
943** compiled SQL statement, this routine returns zero.
944*/
danielk197793d46752004-05-23 13:30:58 +0000945int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000946
drh4f26d6c2004-05-26 23:25:30 +0000947/*
948** Values are stored in the database in one of the following fundamental
949** types.
950*/
drh9c054832004-05-31 18:51:57 +0000951#define SQLITE_INTEGER 1
952#define SQLITE_FLOAT 2
drh1e284f42004-10-06 15:52:01 +0000953/* #define SQLITE_TEXT 3 // See below */
drh9c054832004-05-31 18:51:57 +0000954#define SQLITE_BLOB 4
955#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000956
danielk1977106bb232004-05-21 10:08:53 +0000957/*
drh1e284f42004-10-06 15:52:01 +0000958** SQLite version 2 defines SQLITE_TEXT differently. To allow both
959** version 2 and version 3 to be included, undefine them both if a
960** conflict is seen. Define SQLITE3_TEXT to be the version 3 value.
961*/
962#ifdef SQLITE_TEXT
963# undef SQLITE_TEXT
964#else
965# define SQLITE_TEXT 3
966#endif
967#define SQLITE3_TEXT 3
968
969/*
drh4f26d6c2004-05-26 23:25:30 +0000970** The next group of routines returns information about the information
971** in a single column of the current result row of a query. In every
972** case the first parameter is a pointer to the SQL statement that is being
973** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
974** the second argument is the index of the column for which information
975** should be returned. iCol is zero-indexed. The left-most column as an
976** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000977**
drh4f26d6c2004-05-26 23:25:30 +0000978** If the SQL statement is not currently point to a valid row, or if the
979** the colulmn index is out of range, the result is undefined.
980**
981** These routines attempt to convert the value where appropriate. For
982** example, if the internal representation is FLOAT and a text result
983** is requested, sprintf() is used internally to do the conversion
984** automatically. The following table details the conversions that
985** are applied:
986**
987** Internal Type Requested Type Conversion
988** ------------- -------------- --------------------------
989** NULL INTEGER Result is 0
990** NULL FLOAT Result is 0.0
991** NULL TEXT Result is an empty string
992** NULL BLOB Result is a zero-length BLOB
993** INTEGER FLOAT Convert from integer to float
994** INTEGER TEXT ASCII rendering of the integer
995** INTEGER BLOB Same as for INTEGER->TEXT
996** FLOAT INTEGER Convert from float to integer
997** FLOAT TEXT ASCII rendering of the float
998** FLOAT BLOB Same as FLOAT->TEXT
999** TEXT INTEGER Use atoi()
1000** TEXT FLOAT Use atof()
1001** TEXT BLOB No change
1002** BLOB INTEGER Convert to TEXT then use atoi()
1003** BLOB FLOAT Convert to TEXT then use atof()
1004** BLOB TEXT Add a \000 terminator if needed
1005**
1006** The following access routines are provided:
1007**
1008** _type() Return the datatype of the result. This is one of
1009** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
1010** or SQLITE_NULL.
1011** _blob() Return the value of a BLOB.
1012** _bytes() Return the number of bytes in a BLOB value or the number
1013** of bytes in a TEXT value represented as UTF-8. The \000
1014** terminator is included in the byte count for TEXT values.
1015** _bytes16() Return the number of bytes in a BLOB value or the number
1016** of bytes in a TEXT value represented as UTF-16. The \u0000
1017** terminator is included in the byte count for TEXT values.
1018** _double() Return a FLOAT value.
1019** _int() Return an INTEGER value in the host computer's native
1020** integer representation. This might be either a 32- or 64-bit
1021** integer depending on the host.
1022** _int64() Return an INTEGER value as a 64-bit signed integer.
1023** _text() Return the value as UTF-8 text.
1024** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +00001025*/
drhf4479502004-05-27 03:12:53 +00001026const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
1027int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
1028int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
1029double sqlite3_column_double(sqlite3_stmt*, int iCol);
1030int sqlite3_column_int(sqlite3_stmt*, int iCol);
drhefad9992004-06-22 12:13:55 +00001031sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +00001032const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
1033const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +00001034int sqlite3_column_type(sqlite3_stmt*, int iCol);
drh29d72102006-02-09 22:13:41 +00001035int sqlite3_column_numeric_type(sqlite3_stmt*, int iCol);
drh4be8b512006-06-13 23:51:34 +00001036sqlite3_value *sqlite3_column_value(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +00001037
danielk197765904932004-05-26 06:18:37 +00001038/*
1039** The sqlite3_finalize() function is called to delete a compiled
1040** SQL statement obtained by a previous call to sqlite3_prepare()
1041** or sqlite3_prepare16(). If the statement was executed successfully, or
1042** not executed at all, then SQLITE_OK is returned. If execution of the
1043** statement failed then an error code is returned.
1044**
1045** This routine can be called at any point during the execution of the
1046** virtual machine. If the virtual machine has not completed execution
1047** when this routine is called, that is like encountering an error or
1048** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
1049** rolled back and transactions cancelled, depending on the circumstances,
1050** and the result code returned will be SQLITE_ABORT.
1051*/
1052int sqlite3_finalize(sqlite3_stmt *pStmt);
1053
1054/*
1055** The sqlite3_reset() function is called to reset a compiled SQL
1056** statement obtained by a previous call to sqlite3_prepare() or
1057** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
1058** Any SQL statement variables that had values bound to them using
1059** the sqlite3_bind_*() API retain their values.
1060*/
1061int sqlite3_reset(sqlite3_stmt *pStmt);
1062
1063/*
danielk197765904932004-05-26 06:18:37 +00001064** The following two functions are used to add user functions or aggregates
1065** implemented in C to the SQL langauge interpreted by SQLite. The
1066** difference only between the two is that the second parameter, the
1067** name of the (scalar) function or aggregate, is encoded in UTF-8 for
1068** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
1069**
1070** The first argument is the database handle that the new function or
1071** aggregate is to be added to. If a single program uses more than one
1072** database handle internally, then user functions or aggregates must
1073** be added individually to each database handle with which they will be
1074** used.
1075**
1076** The third parameter is the number of arguments that the function or
1077** aggregate takes. If this parameter is negative, then the function or
1078** aggregate may take any number of arguments.
1079**
danielk1977d8123362004-06-12 09:25:12 +00001080** The fourth parameter is one of SQLITE_UTF* values defined below,
1081** indicating the encoding that the function is most likely to handle
1082** values in. This does not change the behaviour of the programming
1083** interface. However, if two versions of the same function are registered
1084** with different encoding values, SQLite invokes the version likely to
1085** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +00001086**
danielk197765904932004-05-26 06:18:37 +00001087** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
1088** pointers to user implemented C functions that implement the user
1089** function or aggregate. A scalar function requires an implementation of
1090** the xFunc callback only, NULL pointers should be passed as the xStep
1091** and xFinal parameters. An aggregate function requires an implementation
1092** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
1093** existing user function or aggregate, pass NULL for all three function
1094** callback. Specifying an inconstent set of callback values, such as an
1095** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
1096** returned.
1097*/
1098int sqlite3_create_function(
1099 sqlite3 *,
1100 const char *zFunctionName,
1101 int nArg,
1102 int eTextRep,
danielk197765904932004-05-26 06:18:37 +00001103 void*,
1104 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
1105 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
1106 void (*xFinal)(sqlite3_context*)
1107);
1108int sqlite3_create_function16(
1109 sqlite3*,
1110 const void *zFunctionName,
1111 int nArg,
1112 int eTextRep,
danielk197765904932004-05-26 06:18:37 +00001113 void*,
1114 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
1115 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
1116 void (*xFinal)(sqlite3_context*)
1117);
1118
1119/*
drhcf85a512006-02-09 18:35:29 +00001120** This function is deprecated. Do not use it. It continues to exist
1121** so as not to break legacy code. But new code should avoid using it.
danielk197765904932004-05-26 06:18:37 +00001122*/
1123int sqlite3_aggregate_count(sqlite3_context*);
1124
danielk19770ffba6b2004-05-24 09:10:10 +00001125/*
drh4f26d6c2004-05-26 23:25:30 +00001126** The next group of routines returns information about parameters to
1127** a user-defined function. Function implementations use these routines
1128** to access their parameters. These routines are the same as the
1129** sqlite3_column_* routines except that these routines take a single
1130** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
1131** column number.
danielk19770ffba6b2004-05-24 09:10:10 +00001132*/
drhf4479502004-05-27 03:12:53 +00001133const void *sqlite3_value_blob(sqlite3_value*);
1134int sqlite3_value_bytes(sqlite3_value*);
1135int sqlite3_value_bytes16(sqlite3_value*);
1136double sqlite3_value_double(sqlite3_value*);
1137int sqlite3_value_int(sqlite3_value*);
drhefad9992004-06-22 12:13:55 +00001138sqlite_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +00001139const unsigned char *sqlite3_value_text(sqlite3_value*);
1140const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +00001141const void *sqlite3_value_text16le(sqlite3_value*);
1142const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +00001143int sqlite3_value_type(sqlite3_value*);
drh29d72102006-02-09 22:13:41 +00001144int sqlite3_value_numeric_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +00001145
1146/*
danielk19770ae8b832004-05-25 12:05:56 +00001147** Aggregate functions use the following routine to allocate
1148** a structure for storing their state. The first time this routine
1149** is called for a particular aggregate, a new structure of size nBytes
1150** is allocated, zeroed, and returned. On subsequent calls (for the
1151** same aggregate instance) the same buffer is returned. The implementation
1152** of the aggregate can use the returned buffer to accumulate data.
1153**
1154** The buffer allocated is freed automatically by SQLite.
1155*/
drh4f26d6c2004-05-26 23:25:30 +00001156void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +00001157
1158/*
drhc0f2a012005-07-09 02:39:40 +00001159** The pUserData parameter to the sqlite3_create_function()
1160** routine used to register user functions is available to
1161** the implementation of the function using this call.
danielk19777e18c252004-05-25 11:47:24 +00001162*/
1163void *sqlite3_user_data(sqlite3_context*);
1164
1165/*
danielk1977682f68b2004-06-05 10:22:17 +00001166** The following two functions may be used by scalar user functions to
1167** associate meta-data with argument values. If the same value is passed to
1168** multiple invocations of the user-function during query execution, under
1169** some circumstances the associated meta-data may be preserved. This may
1170** be used, for example, to add a regular-expression matching scalar
1171** function. The compiled version of the regular expression is stored as
1172** meta-data associated with the SQL value passed as the regular expression
1173** pattern.
1174**
1175** Calling sqlite3_get_auxdata() returns a pointer to the meta data
1176** associated with the Nth argument value to the current user function
1177** call, where N is the second parameter. If no meta-data has been set for
1178** that value, then a NULL pointer is returned.
1179**
1180** The sqlite3_set_auxdata() is used to associate meta data with a user
1181** function argument. The third parameter is a pointer to the meta data
1182** to be associated with the Nth user function argument value. The fourth
1183** parameter specifies a 'delete function' that will be called on the meta
1184** data pointer to release it when it is no longer required. If the delete
1185** function pointer is NULL, it is not invoked.
1186**
1187** In practice, meta-data is preserved between function calls for
1188** expressions that are constant at compile time. This includes literal
1189** values and SQL variables.
1190*/
1191void *sqlite3_get_auxdata(sqlite3_context*, int);
1192void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
1193
drha2854222004-06-17 19:04:17 +00001194
1195/*
1196** These are special value for the destructor that is passed in as the
1197** final argument to routines like sqlite3_result_blob(). If the destructor
1198** argument is SQLITE_STATIC, it means that the content pointer is constant
1199** and will never change. It does not need to be destroyed. The
1200** SQLITE_TRANSIENT value means that the content will likely change in
1201** the near future and that SQLite should make its own private copy of
1202** the content before returning.
drh6c9121a2007-01-26 00:51:43 +00001203**
1204** The typedef is necessary to work around problems in certain
1205** C++ compilers. See ticket #2191.
drha2854222004-06-17 19:04:17 +00001206*/
drh6c9121a2007-01-26 00:51:43 +00001207typedef void (*sqlite3_destructor_type)(void*);
1208#define SQLITE_STATIC ((sqlite3_destructor_type)0)
1209#define SQLITE_TRANSIENT ((sqlite3_destructor_type)-1)
danielk1977d8123362004-06-12 09:25:12 +00001210
danielk1977682f68b2004-06-05 10:22:17 +00001211/*
drh4f26d6c2004-05-26 23:25:30 +00001212** User-defined functions invoke the following routines in order to
1213** set their return value.
danielk19777e18c252004-05-25 11:47:24 +00001214*/
danielk1977d8123362004-06-12 09:25:12 +00001215void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001216void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +00001217void sqlite3_result_error(sqlite3_context*, const char*, int);
1218void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +00001219void sqlite3_result_int(sqlite3_context*, int);
drhefad9992004-06-22 12:13:55 +00001220void sqlite3_result_int64(sqlite3_context*, sqlite_int64);
drh4f26d6c2004-05-26 23:25:30 +00001221void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +00001222void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
1223void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
1224void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
1225void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001226void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhb026e052007-05-02 01:34:31 +00001227void sqlite3_result_zeroblob(sqlite3_context*, int n);
drha0206bc2007-05-08 15:15:02 +00001228void sqlite3_result_error_toobig(sqlite3_context*);
drhf9b596e2004-05-26 16:54:42 +00001229
drh52619df2004-06-11 17:48:02 +00001230/*
1231** These are the allowed values for the eTextRep argument to
1232** sqlite3_create_collation and sqlite3_create_function.
1233*/
drh7d9bd4e2006-02-16 18:16:36 +00001234#define SQLITE_UTF8 1
1235#define SQLITE_UTF16LE 2
1236#define SQLITE_UTF16BE 3
1237#define SQLITE_UTF16 4 /* Use native byte order */
1238#define SQLITE_ANY 5 /* sqlite3_create_function only */
1239#define SQLITE_UTF16_ALIGNED 8 /* sqlite3_create_collation only */
danielk1977466be562004-06-10 02:16:01 +00001240
danielk19777cedc8d2004-06-10 10:50:08 +00001241/*
1242** These two functions are used to add new collation sequences to the
1243** sqlite3 handle specified as the first argument.
1244**
1245** The name of the new collation sequence is specified as a UTF-8 string
1246** for sqlite3_create_collation() and a UTF-16 string for
1247** sqlite3_create_collation16(). In both cases the name is passed as the
1248** second function argument.
1249**
1250** The third argument must be one of the constants SQLITE_UTF8,
1251** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1252** routine expects to be passed pointers to strings encoded using UTF-8,
1253** UTF-16 little-endian or UTF-16 big-endian respectively.
1254**
1255** A pointer to the user supplied routine must be passed as the fifth
1256** argument. If it is NULL, this is the same as deleting the collation
1257** sequence (so that SQLite cannot call it anymore). Each time the user
1258** supplied function is invoked, it is passed a copy of the void* passed as
1259** the fourth argument to sqlite3_create_collation() or
1260** sqlite3_create_collation16() as its first parameter.
1261**
1262** The remaining arguments to the user-supplied routine are two strings,
1263** each represented by a [length, data] pair and encoded in the encoding
1264** that was passed as the third argument when the collation sequence was
1265** registered. The user routine should return negative, zero or positive if
1266** the first string is less than, equal to, or greater than the second
1267** string. i.e. (STRING1 - STRING2).
1268*/
danielk19770202b292004-06-09 09:55:16 +00001269int sqlite3_create_collation(
1270 sqlite3*,
1271 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001272 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001273 void*,
1274 int(*xCompare)(void*,int,const void*,int,const void*)
1275);
1276int sqlite3_create_collation16(
1277 sqlite3*,
1278 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001279 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001280 void*,
1281 int(*xCompare)(void*,int,const void*,int,const void*)
1282);
1283
danielk19777cedc8d2004-06-10 10:50:08 +00001284/*
danielk1977a9808b32007-05-07 09:32:45 +00001285****** EXPERIMENTAL - subject to change without notice **************
danielk1977a393c032007-05-07 14:58:53 +00001286**
1287** The following experimental API is identical to the
1288** sqlite3_create_collation() function described above except that it
1289** allows a destructor callback function - xDestroy - for the new
1290** collation sequence to be specified. If this function returns
1291** successfully, the destructor function will be invoked exactly once
1292** by SQLite when one of the following occurs:
1293**
1294** * The collation sequence is overidden by a subsequent call
1295** to create_collation(), create_collation16() or
1296** create_collation_v2(), or
1297**
1298** * The database handle is closed.
1299**
1300** The argument passed to the destructor function is a copy of
1301** the void* pointer passed as the 4th argument to this function.
danielk1977a9808b32007-05-07 09:32:45 +00001302*/
danielk1977a393c032007-05-07 14:58:53 +00001303int sqlite3_create_collation_v2(
danielk1977a9808b32007-05-07 09:32:45 +00001304 sqlite3*,
1305 const char *zName,
1306 int eTextRep,
1307 void*,
1308 int(*xCompare)(void*,int,const void*,int,const void*),
danielk1977a393c032007-05-07 14:58:53 +00001309 void(*xDestroy)(void*)
danielk1977a9808b32007-05-07 09:32:45 +00001310);
1311
1312/*
danielk19777cedc8d2004-06-10 10:50:08 +00001313** To avoid having to register all collation sequences before a database
1314** can be used, a single callback function may be registered with the
1315** database handle to be called whenever an undefined collation sequence is
1316** required.
1317**
1318** If the function is registered using the sqlite3_collation_needed() API,
1319** then it is passed the names of undefined collation sequences as strings
1320** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1321** are passed as UTF-16 in machine native byte order. A call to either
1322** function replaces any existing callback.
1323**
1324** When the user-function is invoked, the first argument passed is a copy
1325** of the second argument to sqlite3_collation_needed() or
1326** sqlite3_collation_needed16(). The second argument is the database
1327** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1328** SQLITE_UTF16LE, indicating the most desirable form of the collation
1329** sequence function required. The fourth parameter is the name of the
1330** required collation sequence.
1331**
1332** The collation sequence is returned to SQLite by a collation-needed
1333** callback using the sqlite3_create_collation() or
1334** sqlite3_create_collation16() APIs, described above.
1335*/
1336int sqlite3_collation_needed(
1337 sqlite3*,
1338 void*,
1339 void(*)(void*,sqlite3*,int eTextRep,const char*)
1340);
1341int sqlite3_collation_needed16(
1342 sqlite3*,
1343 void*,
1344 void(*)(void*,sqlite3*,int eTextRep,const void*)
1345);
1346
drh2011d5f2004-07-22 02:40:37 +00001347/*
1348** Specify the key for an encrypted database. This routine should be
1349** called right after sqlite3_open().
1350**
1351** The code to implement this API is not available in the public release
1352** of SQLite.
1353*/
1354int sqlite3_key(
1355 sqlite3 *db, /* Database to be rekeyed */
1356 const void *pKey, int nKey /* The key */
1357);
1358
1359/*
1360** Change the key on an open database. If the current database is not
1361** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the
1362** database is decrypted.
1363**
1364** The code to implement this API is not available in the public release
1365** of SQLite.
1366*/
1367int sqlite3_rekey(
1368 sqlite3 *db, /* Database to be rekeyed */
1369 const void *pKey, int nKey /* The new key */
1370);
danielk19770202b292004-06-09 09:55:16 +00001371
drhab3f9fe2004-08-14 17:10:10 +00001372/*
danielk1977600dd0b2005-01-20 01:14:23 +00001373** Sleep for a little while. The second parameter is the number of
1374** miliseconds to sleep for.
1375**
1376** If the operating system does not support sleep requests with
1377** milisecond time resolution, then the time will be rounded up to
1378** the nearest second. The number of miliseconds of sleep actually
1379** requested from the operating system is returned.
danielk1977600dd0b2005-01-20 01:14:23 +00001380*/
1381int sqlite3_sleep(int);
1382
1383/*
drh65efb652005-06-12 22:12:39 +00001384** Return TRUE (non-zero) if the statement supplied as an argument needs
drhd89bd002005-01-22 03:03:54 +00001385** to be recompiled. A statement needs to be recompiled whenever the
1386** execution environment changes in a way that would alter the program
1387** that sqlite3_prepare() generates. For example, if new functions or
1388** collating sequences are registered or if an authorizer function is
1389** added or changed.
1390**
drhd89bd002005-01-22 03:03:54 +00001391*/
1392int sqlite3_expired(sqlite3_stmt*);
1393
1394/*
drhf8db1bc2005-04-22 02:38:37 +00001395** Move all bindings from the first prepared statement over to the second.
1396** This routine is useful, for example, if the first prepared statement
1397** fails with an SQLITE_SCHEMA error. The same SQL can be prepared into
1398** the second prepared statement then all of the bindings transfered over
1399** to the second statement before the first statement is finalized.
drhf8db1bc2005-04-22 02:38:37 +00001400*/
1401int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*);
1402
1403/*
tpoindex9a09a3c2004-12-20 19:01:32 +00001404** If the following global variable is made to point to a
drhab3f9fe2004-08-14 17:10:10 +00001405** string which is the name of a directory, then all temporary files
1406** created by SQLite will be placed in that directory. If this variable
1407** is NULL pointer, then SQLite does a search for an appropriate temporary
1408** file directory.
1409**
danielk19776b456a22005-03-21 04:04:02 +00001410** Once sqlite3_open() has been called, changing this variable will invalidate
1411** the current temporary database, if any.
drhab3f9fe2004-08-14 17:10:10 +00001412*/
tpoindex9a09a3c2004-12-20 19:01:32 +00001413extern char *sqlite3_temp_directory;
drhab3f9fe2004-08-14 17:10:10 +00001414
danielk19776b456a22005-03-21 04:04:02 +00001415/*
1416** This function is called to recover from a malloc() failure that occured
1417** within the SQLite library. Normally, after a single malloc() fails the
1418** library refuses to function (all major calls return SQLITE_NOMEM).
drh9a7e6082005-03-31 22:26:19 +00001419** This function restores the library state so that it can be used again.
danielk19776b456a22005-03-21 04:04:02 +00001420**
1421** All existing statements (sqlite3_stmt pointers) must be finalized or
1422** reset before this call is made. Otherwise, SQLITE_BUSY is returned.
1423** If any in-memory databases are in use, either as a main or TEMP
1424** database, SQLITE_ERROR is returned. In either of these cases, the
1425** library is not reset and remains unusable.
1426**
1427** This function is *not* threadsafe. Calling this from within a threaded
1428** application when threads other than the caller have used SQLite is
1429** dangerous and will almost certainly result in malfunctions.
1430**
1431** This functionality can be omitted from a build by defining the
1432** SQLITE_OMIT_GLOBALRECOVER at compile time.
1433*/
drhd9cb6ac2005-10-20 07:28:17 +00001434int sqlite3_global_recover(void);
danielk19776b456a22005-03-21 04:04:02 +00001435
drh3e1d8e62005-05-26 16:23:34 +00001436/*
1437** Test to see whether or not the database connection is in autocommit
1438** mode. Return TRUE if it is and FALSE if not. Autocommit mode is on
1439** by default. Autocommit is disabled by a BEGIN statement and reenabled
1440** by the next COMMIT or ROLLBACK.
drh3e1d8e62005-05-26 16:23:34 +00001441*/
1442int sqlite3_get_autocommit(sqlite3*);
1443
drh51942bc2005-06-12 22:01:42 +00001444/*
1445** Return the sqlite3* database handle to which the prepared statement given
1446** in the argument belongs. This is the same database handle that was
1447** the first argument to the sqlite3_prepare() that was used to create
1448** the statement in the first place.
1449*/
1450sqlite3 *sqlite3_db_handle(sqlite3_stmt*);
drh3e1d8e62005-05-26 16:23:34 +00001451
drhb37df7b2005-10-13 02:09:49 +00001452/*
danielk197794eb6a12005-12-15 15:22:08 +00001453** Register a callback function with the database connection identified by the
1454** first argument to be invoked whenever a row is updated, inserted or deleted.
1455** Any callback set by a previous call to this function for the same
1456** database connection is overridden.
1457**
1458** The second argument is a pointer to the function to invoke when a
1459** row is updated, inserted or deleted. The first argument to the callback is
1460** a copy of the third argument to sqlite3_update_hook. The second callback
1461** argument is one of SQLITE_INSERT, SQLITE_DELETE or SQLITE_UPDATE, depending
1462** on the operation that caused the callback to be invoked. The third and
1463** fourth arguments to the callback contain pointers to the database and
1464** table name containing the affected row. The final callback parameter is
1465** the rowid of the row. In the case of an update, this is the rowid after
1466** the update takes place.
1467**
1468** The update hook is not invoked when internal system tables are
1469** modified (i.e. sqlite_master and sqlite_sequence).
danielk197771fd80b2005-12-16 06:54:01 +00001470**
1471** If another function was previously registered, its pArg value is returned.
1472** Otherwise NULL is returned.
danielk197794eb6a12005-12-15 15:22:08 +00001473*/
danielk197771fd80b2005-12-16 06:54:01 +00001474void *sqlite3_update_hook(
danielk197794eb6a12005-12-15 15:22:08 +00001475 sqlite3*,
1476 void(*)(void *,int ,char const *,char const *,sqlite_int64),
1477 void*
1478);
danielk197713a68c32005-12-15 10:11:30 +00001479
danielk1977f3f06bb2005-12-16 15:24:28 +00001480/*
1481** Register a callback to be invoked whenever a transaction is rolled
1482** back.
1483**
1484** The new callback function overrides any existing rollback-hook
1485** callback. If there was an existing callback, then it's pArg value
1486** (the third argument to sqlite3_rollback_hook() when it was registered)
1487** is returned. Otherwise, NULL is returned.
1488**
1489** For the purposes of this API, a transaction is said to have been
1490** rolled back if an explicit "ROLLBACK" statement is executed, or
1491** an error or constraint causes an implicit rollback to occur. The
1492** callback is not invoked if a transaction is automatically rolled
1493** back because the database connection is closed.
1494*/
danielk197771fd80b2005-12-16 06:54:01 +00001495void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*);
1496
danielk19777ddad962005-12-12 06:53:03 +00001497/*
danielk1977aef0bf62005-12-30 16:28:01 +00001498** This function is only available if the library is compiled without
1499** the SQLITE_OMIT_SHARED_CACHE macro defined. It is used to enable or
1500** disable (if the argument is true or false, respectively) the
1501** "shared pager" feature.
1502*/
1503int sqlite3_enable_shared_cache(int);
1504
1505/*
danielk197752622822006-01-09 09:59:49 +00001506** Attempt to free N bytes of heap memory by deallocating non-essential
1507** memory allocations held by the database library (example: memory
1508** used to cache database pages to improve performance).
1509**
drh6f7adc82006-01-11 21:41:20 +00001510** This function is not a part of standard builds. It is only created
1511** if SQLite is compiled with the SQLITE_ENABLE_MEMORY_MANAGEMENT macro.
danielk197752622822006-01-09 09:59:49 +00001512*/
1513int sqlite3_release_memory(int);
1514
1515/*
1516** Place a "soft" limit on the amount of heap memory that may be allocated by
1517** SQLite within the current thread. If an internal allocation is requested
1518** that would exceed the specified limit, sqlite3_release_memory() is invoked
1519** one or more times to free up some space before the allocation is made.
1520**
1521** The limit is called "soft", because if sqlite3_release_memory() cannot free
1522** sufficient memory to prevent the limit from being exceeded, the memory is
1523** allocated anyway and the current operation proceeds.
1524**
drh6f7adc82006-01-11 21:41:20 +00001525** This function is only available if the library was compiled with the
1526** SQLITE_ENABLE_MEMORY_MANAGEMENT option set.
danielk197752622822006-01-09 09:59:49 +00001527** memory-management has been enabled.
1528*/
drhd2d4a6b2006-01-10 15:18:27 +00001529void sqlite3_soft_heap_limit(int);
danielk197752622822006-01-09 09:59:49 +00001530
1531/*
drh6f7adc82006-01-11 21:41:20 +00001532** This routine makes sure that all thread-local storage has been
1533** deallocated for the current thread.
1534**
1535** This routine is not technically necessary. All thread-local storage
1536** will be automatically deallocated once memory-management and
1537** shared-cache are disabled and the soft heap limit has been set
1538** to zero. This routine is provided as a convenience for users who
1539** want to make absolutely sure they have not forgotten something
1540** prior to killing off a thread.
1541*/
1542void sqlite3_thread_cleanup(void);
1543
1544/*
danielk1977deb802c2006-02-09 13:43:28 +00001545** Return meta information about a specific column of a specific database
1546** table accessible using the connection handle passed as the first function
1547** argument.
1548**
1549** The column is identified by the second, third and fourth parameters to
1550** this function. The second parameter is either the name of the database
1551** (i.e. "main", "temp" or an attached database) containing the specified
1552** table or NULL. If it is NULL, then all attached databases are searched
1553** for the table using the same algorithm as the database engine uses to
1554** resolve unqualified table references.
1555**
1556** The third and fourth parameters to this function are the table and column
1557** name of the desired column, respectively. Neither of these parameters
1558** may be NULL.
1559**
1560** Meta information is returned by writing to the memory locations passed as
1561** the 5th and subsequent parameters to this function. Any of these
1562** arguments may be NULL, in which case the corresponding element of meta
1563** information is ommitted.
1564**
1565** Parameter Output Type Description
1566** -----------------------------------
1567**
1568** 5th const char* Data type
1569** 6th const char* Name of the default collation sequence
1570** 7th int True if the column has a NOT NULL constraint
1571** 8th int True if the column is part of the PRIMARY KEY
1572** 9th int True if the column is AUTOINCREMENT
1573**
1574**
1575** The memory pointed to by the character pointers returned for the
1576** declaration type and collation sequence is valid only until the next
1577** call to any sqlite API function.
1578**
1579** If the specified table is actually a view, then an error is returned.
1580**
1581** If the specified column is "rowid", "oid" or "_rowid_" and an
1582** INTEGER PRIMARY KEY column has been explicitly declared, then the output
1583** parameters are set for the explicitly declared column. If there is no
1584** explicitly declared IPK column, then the output parameters are set as
1585** follows:
1586**
1587** data type: "INTEGER"
1588** collation sequence: "BINARY"
1589** not null: 0
1590** primary key: 1
1591** auto increment: 0
1592**
1593** This function may load one or more schemas from database files. If an
1594** error occurs during this process, or if the requested table or column
1595** cannot be found, an SQLITE error code is returned and an error message
1596** left in the database handle (to be retrieved using sqlite3_errmsg()).
danielk19774b1ae992006-02-10 03:06:10 +00001597**
1598** This API is only available if the library was compiled with the
1599** SQLITE_ENABLE_COLUMN_METADATA preprocessor symbol defined.
danielk1977deb802c2006-02-09 13:43:28 +00001600*/
1601int sqlite3_table_column_metadata(
1602 sqlite3 *db, /* Connection handle */
1603 const char *zDbName, /* Database name or NULL */
1604 const char *zTableName, /* Table name */
1605 const char *zColumnName, /* Column name */
1606 char const **pzDataType, /* OUTPUT: Declared data type */
1607 char const **pzCollSeq, /* OUTPUT: Collation sequence name */
1608 int *pNotNull, /* OUTPUT: True if NOT NULL constraint exists */
1609 int *pPrimaryKey, /* OUTPUT: True if column part of PK */
1610 int *pAutoinc /* OUTPUT: True if colums is auto-increment */
1611);
1612
1613/*
drh1e397f82006-06-08 15:28:43 +00001614****** EXPERIMENTAL - subject to change without notice **************
1615**
1616** Attempt to load an SQLite extension library contained in the file
1617** zFile. The entry point is zProc. zProc may be 0 in which case the
drhc2e87a32006-06-27 15:16:14 +00001618** name of the entry point defaults to "sqlite3_extension_init".
drh1e397f82006-06-08 15:28:43 +00001619**
1620** Return SQLITE_OK on success and SQLITE_ERROR if something goes wrong.
1621**
1622** If an error occurs and pzErrMsg is not 0, then fill *pzErrMsg with
1623** error message text. The calling function should free this memory
1624** by calling sqlite3_free().
1625**
drhc2e87a32006-06-27 15:16:14 +00001626** Extension loading must be enabled using sqlite3_enable_load_extension()
1627** prior to calling this API or an error will be returned.
drh1e397f82006-06-08 15:28:43 +00001628**
1629****** EXPERIMENTAL - subject to change without notice **************
1630*/
1631int sqlite3_load_extension(
1632 sqlite3 *db, /* Load the extension into this database connection */
1633 const char *zFile, /* Name of the shared library containing extension */
1634 const char *zProc, /* Entry point. Derived from zFile if 0 */
1635 char **pzErrMsg /* Put error message here if not 0 */
1636);
1637
1638/*
drhc2e87a32006-06-27 15:16:14 +00001639** So as not to open security holes in older applications that are
1640** unprepared to deal with extension load, and as a means of disabling
1641** extension loading while executing user-entered SQL, the following
1642** API is provided to turn the extension loading mechanism on and
1643** off. It is off by default. See ticket #1863.
1644**
1645** Call this routine with onoff==1 to turn extension loading on
1646** and call it with onoff==0 to turn it back off again.
1647*/
1648int sqlite3_enable_load_extension(sqlite3 *db, int onoff);
1649
1650/*
drhe09daa92006-06-10 13:29:31 +00001651****** EXPERIMENTAL - subject to change without notice **************
drh9eff6162006-06-12 21:59:13 +00001652**
drh1409be62006-08-23 20:07:20 +00001653** Register an extension entry point that is automatically invoked
1654** whenever a new database connection is opened.
1655**
1656** This API can be invoked at program startup in order to register
1657** one or more statically linked extensions that will be available
1658** to all new database connections.
1659**
1660** Duplicate extensions are detected so calling this routine multiple
1661** times with the same extension is harmless.
1662**
1663** This routine stores a pointer to the extension in an array
1664** that is obtained from malloc(). If you run a memory leak
1665** checker on your program and it reports a leak because of this
1666** array, then invoke sqlite3_automatic_extension_reset() prior
1667** to shutdown to free the memory.
1668**
1669** Automatic extensions apply across all threads.
1670*/
1671int sqlite3_auto_extension(void *xEntryPoint);
1672
1673
1674/*
1675****** EXPERIMENTAL - subject to change without notice **************
1676**
1677** Disable all previously registered automatic extensions. This
1678** routine undoes the effect of all prior sqlite3_automatic_extension()
1679** calls.
1680**
1681** This call disabled automatic extensions in all threads.
1682*/
1683void sqlite3_reset_auto_extension(void);
1684
1685
1686/*
1687****** EXPERIMENTAL - subject to change without notice **************
1688**
drh9eff6162006-06-12 21:59:13 +00001689** The interface to the virtual-table mechanism is currently considered
1690** to be experimental. The interface might change in incompatible ways.
1691** If this is a problem for you, do not use the interface at this time.
1692**
1693** When the virtual-table mechanism stablizes, we will declare the
1694** interface fixed, support it indefinitely, and remove this comment.
1695*/
1696
1697/*
1698** Structures used by the virtual table interface
drhe09daa92006-06-10 13:29:31 +00001699*/
1700typedef struct sqlite3_vtab sqlite3_vtab;
1701typedef struct sqlite3_index_info sqlite3_index_info;
1702typedef struct sqlite3_vtab_cursor sqlite3_vtab_cursor;
1703typedef struct sqlite3_module sqlite3_module;
drh9eff6162006-06-12 21:59:13 +00001704
1705/*
1706** A module is a class of virtual tables. Each module is defined
1707** by an instance of the following structure. This structure consists
1708** mostly of methods for the module.
1709*/
drhe09daa92006-06-10 13:29:31 +00001710struct sqlite3_module {
1711 int iVersion;
danielk19779da9d472006-06-14 06:58:15 +00001712 int (*xCreate)(sqlite3*, void *pAux,
drhe4102962006-09-11 00:34:22 +00001713 int argc, const char *const*argv,
drh4ca8aac2006-09-10 17:31:58 +00001714 sqlite3_vtab **ppVTab, char**);
danielk19779da9d472006-06-14 06:58:15 +00001715 int (*xConnect)(sqlite3*, void *pAux,
drhe4102962006-09-11 00:34:22 +00001716 int argc, const char *const*argv,
drh4ca8aac2006-09-10 17:31:58 +00001717 sqlite3_vtab **ppVTab, char**);
drhe09daa92006-06-10 13:29:31 +00001718 int (*xBestIndex)(sqlite3_vtab *pVTab, sqlite3_index_info*);
1719 int (*xDisconnect)(sqlite3_vtab *pVTab);
1720 int (*xDestroy)(sqlite3_vtab *pVTab);
1721 int (*xOpen)(sqlite3_vtab *pVTab, sqlite3_vtab_cursor **ppCursor);
1722 int (*xClose)(sqlite3_vtab_cursor*);
drh4be8b512006-06-13 23:51:34 +00001723 int (*xFilter)(sqlite3_vtab_cursor*, int idxNum, const char *idxStr,
drhe09daa92006-06-10 13:29:31 +00001724 int argc, sqlite3_value **argv);
1725 int (*xNext)(sqlite3_vtab_cursor*);
danielk1977a298e902006-06-22 09:53:48 +00001726 int (*xEof)(sqlite3_vtab_cursor*);
drhe09daa92006-06-10 13:29:31 +00001727 int (*xColumn)(sqlite3_vtab_cursor*, sqlite3_context*, int);
1728 int (*xRowid)(sqlite3_vtab_cursor*, sqlite_int64 *pRowid);
danielk19771f6eec52006-06-16 06:17:47 +00001729 int (*xUpdate)(sqlite3_vtab *, int, sqlite3_value **, sqlite_int64 *);
drhe09daa92006-06-10 13:29:31 +00001730 int (*xBegin)(sqlite3_vtab *pVTab);
1731 int (*xSync)(sqlite3_vtab *pVTab);
1732 int (*xCommit)(sqlite3_vtab *pVTab);
1733 int (*xRollback)(sqlite3_vtab *pVTab);
drhb7f6f682006-07-08 17:06:43 +00001734 int (*xFindFunction)(sqlite3_vtab *pVtab, int nArg, const char *zName,
drhe94b0c32006-07-08 18:09:15 +00001735 void (**pxFunc)(sqlite3_context*,int,sqlite3_value**),
1736 void **ppArg);
drhe09daa92006-06-10 13:29:31 +00001737};
drh9eff6162006-06-12 21:59:13 +00001738
1739/*
1740** The sqlite3_index_info structure and its substructures is used to
1741** pass information into and receive the reply from the xBestIndex
1742** method of an sqlite3_module. The fields under **Inputs** are the
1743** inputs to xBestIndex and are read-only. xBestIndex inserts its
1744** results into the **Outputs** fields.
1745**
1746** The aConstraint[] array records WHERE clause constraints of the
1747** form:
1748**
1749** column OP expr
1750**
1751** Where OP is =, <, <=, >, or >=. The particular operator is stored
1752** in aConstraint[].op. The index of the column is stored in
1753** aConstraint[].iColumn. aConstraint[].usable is TRUE if the
1754** expr on the right-hand side can be evaluated (and thus the constraint
1755** is usable) and false if it cannot.
1756**
1757** The optimizer automatically inverts terms of the form "expr OP column"
1758** and makes other simplificatinos to the WHERE clause in an attempt to
1759** get as many WHERE clause terms into the form shown above as possible.
1760** The aConstraint[] array only reports WHERE clause terms in the correct
1761** form that refer to the particular virtual table being queried.
1762**
1763** Information about the ORDER BY clause is stored in aOrderBy[].
1764** Each term of aOrderBy records a column of the ORDER BY clause.
1765**
1766** The xBestIndex method must fill aConstraintUsage[] with information
danielk19775fac9f82006-06-13 14:16:58 +00001767** about what parameters to pass to xFilter. If argvIndex>0 then
drh9eff6162006-06-12 21:59:13 +00001768** the right-hand side of the corresponding aConstraint[] is evaluated
1769** and becomes the argvIndex-th entry in argv. If aConstraintUsage[].omit
1770** is true, then the constraint is assumed to be fully handled by the
1771** virtual table and is not checked again by SQLite.
1772**
drh4be8b512006-06-13 23:51:34 +00001773** The idxNum and idxPtr values are recorded and passed into xFilter.
1774** sqlite3_free() is used to free idxPtr if needToFreeIdxPtr is true.
drh9eff6162006-06-12 21:59:13 +00001775**
1776** The orderByConsumed means that output from xFilter will occur in
1777** the correct order to satisfy the ORDER BY clause so that no separate
1778** sorting step is required.
1779**
1780** The estimatedCost value is an estimate of the cost of doing the
1781** particular lookup. A full scan of a table with N entries should have
1782** a cost of N. A binary search of a table of N entries should have a
1783** cost of approximately log(N).
1784*/
drhe09daa92006-06-10 13:29:31 +00001785struct sqlite3_index_info {
1786 /* Inputs */
drh9eff6162006-06-12 21:59:13 +00001787 const int nConstraint; /* Number of entries in aConstraint */
1788 const struct sqlite3_index_constraint {
1789 int iColumn; /* Column on left-hand side of constraint */
1790 unsigned char op; /* Constraint operator */
1791 unsigned char usable; /* True if this constraint is usable */
1792 int iTermOffset; /* Used internally - xBestIndex should ignore */
1793 } *const aConstraint; /* Table of WHERE clause constraints */
1794 const int nOrderBy; /* Number of terms in the ORDER BY clause */
1795 const struct sqlite3_index_orderby {
1796 int iColumn; /* Column number */
1797 unsigned char desc; /* True for DESC. False for ASC. */
1798 } *const aOrderBy; /* The ORDER BY clause */
drhe09daa92006-06-10 13:29:31 +00001799
1800 /* Outputs */
drh9eff6162006-06-12 21:59:13 +00001801 struct sqlite3_index_constraint_usage {
1802 int argvIndex; /* if >0, constraint is part of argv to xFilter */
1803 unsigned char omit; /* Do not code a test for this constraint */
1804 } *const aConstraintUsage;
drh4be8b512006-06-13 23:51:34 +00001805 int idxNum; /* Number used to identify the index */
1806 char *idxStr; /* String, possibly obtained from sqlite3_malloc */
1807 int needToFreeIdxStr; /* Free idxStr using sqlite3_free() if true */
drh9eff6162006-06-12 21:59:13 +00001808 int orderByConsumed; /* True if output is already ordered */
1809 double estimatedCost; /* Estimated cost of using this index */
drhe09daa92006-06-10 13:29:31 +00001810};
drh9eff6162006-06-12 21:59:13 +00001811#define SQLITE_INDEX_CONSTRAINT_EQ 2
1812#define SQLITE_INDEX_CONSTRAINT_GT 4
1813#define SQLITE_INDEX_CONSTRAINT_LE 8
1814#define SQLITE_INDEX_CONSTRAINT_LT 16
1815#define SQLITE_INDEX_CONSTRAINT_GE 32
1816#define SQLITE_INDEX_CONSTRAINT_MATCH 64
1817
1818/*
1819** This routine is used to register a new module name with an SQLite
1820** connection. Module names must be registered before creating new
1821** virtual tables on the module, or before using preexisting virtual
1822** tables of the module.
1823*/
drhb9bb7c12006-06-11 23:41:55 +00001824int sqlite3_create_module(
drh9eff6162006-06-12 21:59:13 +00001825 sqlite3 *db, /* SQLite connection to register module with */
1826 const char *zName, /* Name of the module */
danielk1977d1ab1ba2006-06-15 04:28:13 +00001827 const sqlite3_module *, /* Methods for the module */
1828 void * /* Client data for xCreate/xConnect */
drhb9bb7c12006-06-11 23:41:55 +00001829);
drhe09daa92006-06-10 13:29:31 +00001830
drh9eff6162006-06-12 21:59:13 +00001831/*
1832** Every module implementation uses a subclass of the following structure
1833** to describe a particular instance of the module. Each subclass will
1834** be taylored to the specific needs of the module implementation. The
1835** purpose of this superclass is to define certain fields that are common
1836** to all module implementations.
drhfe1368e2006-09-10 17:08:29 +00001837**
1838** Virtual tables methods can set an error message by assigning a
1839** string obtained from sqlite3_mprintf() to zErrMsg. The method should
1840** take care that any prior string is freed by a call to sqlite3_free()
1841** prior to assigning a new string to zErrMsg. After the error message
1842** is delivered up to the client application, the string will be automatically
1843** freed by sqlite3_free() and the zErrMsg field will be zeroed. Note
1844** that sqlite3_mprintf() and sqlite3_free() are used on the zErrMsg field
1845** since virtual tables are commonly implemented in loadable extensions which
1846** do not have access to sqlite3MPrintf() or sqlite3Free().
drh9eff6162006-06-12 21:59:13 +00001847*/
1848struct sqlite3_vtab {
drha967e882006-06-13 01:04:52 +00001849 const sqlite3_module *pModule; /* The module for this virtual table */
danielk1977be718892006-06-23 08:05:19 +00001850 int nRef; /* Used internally */
drh4ca8aac2006-09-10 17:31:58 +00001851 char *zErrMsg; /* Error message from sqlite3_mprintf() */
drh9eff6162006-06-12 21:59:13 +00001852 /* Virtual table implementations will typically add additional fields */
1853};
1854
1855/* Every module implementation uses a subclass of the following structure
1856** to describe cursors that point into the virtual table and are used
1857** to loop through the virtual table. Cursors are created using the
1858** xOpen method of the module. Each module implementation will define
1859** the content of a cursor structure to suit its own needs.
1860**
1861** This superclass exists in order to define fields of the cursor that
1862** are common to all implementations.
1863*/
1864struct sqlite3_vtab_cursor {
1865 sqlite3_vtab *pVtab; /* Virtual table of this cursor */
1866 /* Virtual table implementations will typically add additional fields */
1867};
1868
1869/*
1870** The xCreate and xConnect methods of a module use the following API
1871** to declare the format (the names and datatypes of the columns) of
1872** the virtual tables they implement.
1873*/
danielk19777e6ebfb2006-06-12 11:24:37 +00001874int sqlite3_declare_vtab(sqlite3*, const char *zCreateTable);
drhe09daa92006-06-10 13:29:31 +00001875
1876/*
drhb7481e72006-09-16 21:45:14 +00001877** Virtual tables can provide alternative implementations of functions
1878** using the xFindFunction method. But global versions of those functions
1879** must exist in order to be overloaded.
1880**
1881** This API makes sure a global version of a function with a particular
1882** name and number of parameters exists. If no such function exists
1883** before this API is called, a new function is created. The implementation
1884** of the new function always causes an exception to be thrown. So
1885** the new function is not good for anything by itself. Its only
1886** purpose is to be a place-holder function that can be overloaded
1887** by virtual tables.
1888**
1889** This API should be considered part of the virtual table interface,
1890** which is experimental and subject to change.
1891*/
1892int sqlite3_overload_function(sqlite3*, const char *zFuncName, int nArg);
1893
1894/*
drh9eff6162006-06-12 21:59:13 +00001895** The interface to the virtual-table mechanism defined above (back up
1896** to a comment remarkably similar to this one) is currently considered
1897** to be experimental. The interface might change in incompatible ways.
1898** If this is a problem for you, do not use the interface at this time.
1899**
1900** When the virtual-table mechanism stablizes, we will declare the
1901** interface fixed, support it indefinitely, and remove this comment.
1902**
1903****** EXPERIMENTAL - subject to change without notice **************
1904*/
1905
danielk19778cbadb02007-05-03 16:31:26 +00001906/*
1907** An instance of the following opaque structure is used to
1908** represent an open blob handle.
1909*/
danielk1977b4e9af92007-05-01 17:49:49 +00001910typedef struct sqlite3_blob sqlite3_blob;
1911
danielk19778cbadb02007-05-03 16:31:26 +00001912/*
1913** Open a handle to the blob located in row iRow,, column zColumn,
1914** table zTable in database zDb. i.e. the same blob that would
1915** be selected by:
1916**
1917** "SELECT zColumn FROM zDb.zTable WHERE rowid = iRow;
1918**
1919** If the flags parameter is non-zero, the blob is opened for
1920** read and write access. If it is zero, the blob is opened for read
1921** access.
1922**
1923** On success, SQLITE_OK is returned and the new blob-handle is
1924** written to *ppBlob. Otherwise an error code is returned and
1925** any value written to *ppBlob should not be used by the caller.
1926** This function sets the database-handle error code and message
1927** accessible via sqlite3_errcode() and sqlite3_errmsg().
1928*/
danielk1977b4e9af92007-05-01 17:49:49 +00001929int sqlite3_blob_open(
1930 sqlite3*,
1931 const char *zDb,
1932 const char *zTable,
1933 const char *zColumn,
1934 sqlite_int64 iRow,
1935 int flags,
1936 sqlite3_blob **ppBlob
1937);
1938
danielk19778cbadb02007-05-03 16:31:26 +00001939/*
1940** Close an open blob handle.
1941*/
danielk1977b4e9af92007-05-01 17:49:49 +00001942int sqlite3_blob_close(sqlite3_blob *);
1943
danielk19778cbadb02007-05-03 16:31:26 +00001944/*
1945** Return the size in bytes of the blob accessible via the open
1946** blob-handle passed as an argument.
1947*/
danielk1977b4e9af92007-05-01 17:49:49 +00001948int sqlite3_blob_bytes(sqlite3_blob *);
1949
drh9eff6162006-06-12 21:59:13 +00001950/*
danielk19778cbadb02007-05-03 16:31:26 +00001951** This function is used to read data from an open blob-handle into
1952** a caller supplied buffer. n bytes of data are copied into buffer
1953** z from the open blob, starting at offset iOffset.
1954**
1955** On success, SQLITE_OK is returned. Otherwise, an SQLite error
1956** code.
1957*/
1958int sqlite3_blob_read(sqlite3_blob *, void *z, int n, int iOffset);
1959
1960/*
1961** This function is used to write data from an open blob-handle into
1962** a user supplied buffer. n bytes of data are copied from the buffer
1963** pointed to by z into the open blob, starting at offset iOffset.
1964**
1965** If the blob-handle passed as the first argument was not opened for
1966** writing (the flags parameter to sqlite3_blob_open was zero), this
1967** function returns SQLITE_READONLY.
1968**
1969** This function may only modify the contents of the blob, it is
1970** not possible to increase the size of a blob using this API. If
1971** offset iOffset is less than n bytes from the end of the blob,
1972** SQLITE_ERROR is returned and no data is written.
1973**
1974** On success, SQLITE_OK is returned. Otherwise, an SQLite error
1975** code. If an error occurs, this function sets the
1976*/
1977int sqlite3_blob_write(sqlite3_blob *, const void *z, int n, int iOffset);
1978
1979/*
drhb37df7b2005-10-13 02:09:49 +00001980** Undo the hack that converts floating point types to integer for
1981** builds on processors without floating point support.
1982*/
1983#ifdef SQLITE_OMIT_FLOATING_POINT
1984# undef double
1985#endif
1986
drh382c0242001-10-06 16:33:02 +00001987#ifdef __cplusplus
1988} /* End of the 'extern "C"' block */
1989#endif
danielk19774adee202004-05-08 08:23:19 +00001990#endif