blob: 6b179016b2cea0b140c844897b7685544e0ca69a [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**
drhc2e87a32006-06-27 15:16:14 +000015** @(#) $Id: sqlite.h.in,v 1.185 2006/06/27 15:16:15 drh 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
43** (X*100000 + Y*1000 + Z). For example, for version "3.1.1beta",
44** 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**
128** The 4th parameter is an arbitrary pointer that is passed
129** 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 */
185#define SQLITE_PROTOCOL 15 /* 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 */
drh2db0bbc2005-08-11 02:10:18 +0000188#define SQLITE_TOOBIG 18 /* NOT USED. Too much data for one row */
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/*
202** Each entry in an SQLite table has a unique integer key. (The key is
203** the value of the INTEGER PRIMARY KEY column if there is such a column,
204** otherwise the key is generated at random. The unique key is always
205** available as the ROWID, OID, or _ROWID_ column.) The following routine
206** returns the integer key of the most recent insert in the database.
207**
208** This function is similar to the mysql_insert_id() function from MySQL.
209*/
drhefad9992004-06-22 12:13:55 +0000210sqlite_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000211
drhc8d30ac2002-04-12 10:08:59 +0000212/*
213** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000214** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000215**
216** All changes are counted, even if they were later undone by a
217** ROLLBACK or ABORT. Except, changes associated with creating and
218** dropping tables are not counted.
219**
danielk19776f8a5032004-05-10 10:34:51 +0000220** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000221** in the inner, recursive call are counted together with the changes
222** in the outer call.
223**
224** SQLite implements the command "DELETE FROM table" without a WHERE clause
225** by dropping and recreating the table. (This is much faster than going
226** through and deleting individual elements form the table.) Because of
227** this optimization, the change count for "DELETE FROM table" will be
228** zero regardless of the number of elements that were originally in the
229** table. To get an accurate count of the number of rows deleted, use
230** "DELETE FROM table WHERE 1" instead.
231*/
danielk1977f9d64d22004-06-19 08:18:07 +0000232int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000233
rdcf146a772004-02-25 22:51:06 +0000234/*
danielk1977b28af712004-06-21 06:50:26 +0000235** This function returns the number of database rows that have been
236** modified by INSERT, UPDATE or DELETE statements since the database handle
237** was opened. This includes UPDATE, INSERT and DELETE statements executed
238** as part of trigger programs. All changes are counted as soon as the
239** statement that makes them is completed (when the statement handle is
240** passed to sqlite3_reset() or sqlite_finalise()).
rdcf146a772004-02-25 22:51:06 +0000241**
242** SQLite implements the command "DELETE FROM table" without a WHERE clause
243** by dropping and recreating the table. (This is much faster than going
244** through and deleting individual elements form the table.) Because of
245** this optimization, the change count for "DELETE FROM table" will be
246** zero regardless of the number of elements that were originally in the
247** table. To get an accurate count of the number of rows deleted, use
248** "DELETE FROM table WHERE 1" instead.
rdcf146a772004-02-25 22:51:06 +0000249*/
danielk1977b28af712004-06-21 06:50:26 +0000250int sqlite3_total_changes(sqlite3*);
251
drh4c504392000-10-16 22:06:40 +0000252/* This function causes any pending database operation to abort and
253** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000254** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000255** or Ctrl-C where the user wants a long query operation to halt
256** immediately.
257*/
danielk1977f9d64d22004-06-19 08:18:07 +0000258void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000259
drheec553b2000-06-02 01:51:20 +0000260
danielk197761de0d12004-05-27 23:56:16 +0000261/* These functions return true if the given input string comprises
262** one or more complete SQL statements. For the sqlite3_complete() call,
263** the parameter must be a nul-terminated UTF-8 string. For
264** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
265** is required.
drh75897232000-05-29 14:26:00 +0000266**
267** The algorithm is simple. If the last token other than spaces
268** and comments is a semicolon, then return true. otherwise return
269** false.
270*/
danielk19776f8a5032004-05-10 10:34:51 +0000271int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000272int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000273
drh2dfbbca2000-07-28 14:32:48 +0000274/*
275** This routine identifies a callback function that is invoked
276** whenever an attempt is made to open a database table that is
277** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000278** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000279** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000280** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000281** second argument is the name of the locked table and the third
282** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000283** busy callback returns 0, then sqlite3_exec() immediately returns
284** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000285** tries to open the table again and the cycle repeats.
286**
287** The default busy callback is NULL.
288**
289** Sqlite is re-entrant, so the busy handler may start a new query.
290** (It is not clear why anyone would every want to do this, but it
291** is allowed, in theory.) But the busy handler may not close the
292** database. Closing the database from a busy handler will delete
293** data structures out from under the executing query and will
294** probably result in a coredump.
295*/
danielk1977f9d64d22004-06-19 08:18:07 +0000296int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000297
298/*
299** This routine sets a busy handler that sleeps for a while when a
300** table is locked. The handler will sleep multiple times until
301** at least "ms" milleseconds of sleeping have been done. After
302** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000303** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000304**
305** Calling this routine with an argument less than or equal to zero
306** turns off all busy handlers.
307*/
danielk1977f9d64d22004-06-19 08:18:07 +0000308int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000309
drhe3710332000-09-29 13:30:53 +0000310/*
danielk19776f8a5032004-05-10 10:34:51 +0000311** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000312** Instead of invoking a user-supplied callback for each row of the
313** result, this routine remembers each row of the result in memory
314** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000315** query has finished.
316**
317** As an example, suppose the query result where this table:
318**
319** Name | Age
320** -----------------------
321** Alice | 43
322** Bob | 28
323** Cindy | 21
324**
325** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000326** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000327**
328** azResult[0] = "Name";
329** azResult[1] = "Age";
330** azResult[2] = "Alice";
331** azResult[3] = "43";
332** azResult[4] = "Bob";
333** azResult[5] = "28";
334** azResult[6] = "Cindy";
335** azResult[7] = "21";
336**
337** Notice that there is an extra row of data containing the column
338** headers. But the *nrow return value is still 3. *ncolumn is
339** set to 2. In general, the number of values inserted into azResult
340** will be ((*nrow) + 1)*(*ncolumn).
341**
342** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000343** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000344** release the memory that was malloc-ed. Because of the way the
345** malloc() happens, the calling function must not try to call
danielk197799b214d2005-02-02 01:13:38 +0000346** free() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000347** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000348**
danielk19776f8a5032004-05-10 10:34:51 +0000349** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000350*/
danielk19776f8a5032004-05-10 10:34:51 +0000351int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000352 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000353 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000354 char ***resultp, /* Result written to a char *[] that this points to */
355 int *nrow, /* Number of result rows written here */
356 int *ncolumn, /* Number of result columns written here */
357 char **errmsg /* Error msg written here */
358);
359
360/*
danielk19776f8a5032004-05-10 10:34:51 +0000361** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000362*/
danielk19776f8a5032004-05-10 10:34:51 +0000363void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000364
drha18c5682000-10-08 22:20:57 +0000365/*
drh4f26d6c2004-05-26 23:25:30 +0000366** The following routines are variants of the "sprintf()" from the
367** standard C library. The resulting string is written into memory
368** obtained from malloc() so that there is never a possiblity of buffer
369** overflow. These routines also implement some additional formatting
370** options that are useful for constructing SQL statements.
371**
372** The strings returned by these routines should be freed by calling
373** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000374**
375** All of the usual printf formatting options apply. In addition, there
376** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000377** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000378** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000379** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000380** the string.
381**
382** For example, so some string variable contains text as follows:
383**
384** char *zText = "It's a happy day!";
385**
386** We can use this text in an SQL statement as follows:
387**
drh3224b322005-09-08 10:58:51 +0000388** char *z = sqlite3_mprintf("INSERT INTO TABLES('%q')", zText);
389** sqlite3_exec(db, z, callback1, 0, 0);
390** sqlite3_free(z);
drha18c5682000-10-08 22:20:57 +0000391**
392** Because the %q format string is used, the '\'' character in zText
393** is escaped and the SQL generated is as follows:
394**
395** INSERT INTO table1 VALUES('It''s a happy day!')
396**
397** This is correct. Had we used %s instead of %q, the generated SQL
398** would have looked like this:
399**
400** INSERT INTO table1 VALUES('It's a happy day!');
401**
402** This second example is an SQL syntax error. As a general rule you
403** should always use %q instead of %s when inserting text into a string
404** literal.
405*/
danielk19776f8a5032004-05-10 10:34:51 +0000406char *sqlite3_mprintf(const char*,...);
407char *sqlite3_vmprintf(const char*, va_list);
drhfeac5f82004-08-01 00:10:45 +0000408char *sqlite3_snprintf(int,char*,const char*, ...);
drh5191b7e2002-03-08 02:12:00 +0000409
drh28dd4792006-06-26 21:35:44 +0000410/*
411** SQLite uses its own memory allocator. On many installations, this
412** memory allocator is identical to the standard malloc()/realloc()/free()
413** and can be used interchangable. On others, the implementations are
414** different. For maximum portability, it is best not to mix calls
415** to the standard malloc/realloc/free with the sqlite versions.
416*/
417void *sqlite3_malloc(int);
418void *sqlite3_realloc(void*, int);
419void sqlite3_free(void*);
420
drh1211de32004-07-26 12:24:22 +0000421#ifndef SQLITE_OMIT_AUTHORIZATION
drh5191b7e2002-03-08 02:12:00 +0000422/*
drhed6c8672003-01-12 18:02:16 +0000423** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000424** callback is invoked (at compile-time, not at run-time) for each
425** attempt to access a column of a table in the database. The callback
426** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
427** SQL statement should be aborted with an error and SQLITE_IGNORE
428** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000429*/
danielk19776f8a5032004-05-10 10:34:51 +0000430int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000431 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000432 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000433 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000434);
drh1211de32004-07-26 12:24:22 +0000435#endif
drhed6c8672003-01-12 18:02:16 +0000436
437/*
438** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000439** be one of the values below. These values signify what kind of operation
440** is to be authorized. The 3rd and 4th parameters to the authorization
441** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000442** codes is used as the second parameter. The 5th parameter is the name
443** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000444** is the name of the inner-most trigger or view that is responsible for
445** the access attempt or NULL if this access attempt is directly from
446** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000447**
448** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000449*/
drh77ad4e42003-01-14 02:49:27 +0000450#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000451#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
452#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
453#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
454#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000455#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000456#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000457#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000458#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
459#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000460#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000461#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000462#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000463#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000464#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000465#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000466#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000467#define SQLITE_DROP_VIEW 17 /* View Name NULL */
468#define SQLITE_INSERT 18 /* Table Name NULL */
469#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
470#define SQLITE_READ 20 /* Table Name Column Name */
471#define SQLITE_SELECT 21 /* NULL NULL */
472#define SQLITE_TRANSACTION 22 /* NULL NULL */
473#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000474#define SQLITE_ATTACH 24 /* Filename NULL */
475#define SQLITE_DETACH 25 /* Database Name NULL */
danielk19771c8c23c2004-11-12 15:53:37 +0000476#define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */
danielk19771d54df82004-11-23 15:41:16 +0000477#define SQLITE_REINDEX 27 /* Index Name NULL */
drhe6e04962005-07-23 02:17:03 +0000478#define SQLITE_ANALYZE 28 /* Table Name NULL */
danielk1977f1a381e2006-06-16 08:01:02 +0000479#define SQLITE_CREATE_VTABLE 29 /* Table Name Module Name */
480#define SQLITE_DROP_VTABLE 30 /* Table Name Module Name */
drhed6c8672003-01-12 18:02:16 +0000481
482/*
483** The return value of the authorization function should be one of the
484** following constants:
485*/
486/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
487#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
488#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
489
490/*
drh19e2d372005-08-29 23:00:03 +0000491** Register a function for tracing SQL command evaluation. The function
492** registered by sqlite3_trace() is invoked at the first sqlite3_step()
493** for the evaluation of an SQL statement. The function registered by
494** sqlite3_profile() runs at the end of each SQL statement and includes
495** information on how long that statement ran.
496**
497** The sqlite3_profile() API is currently considered experimental and
498** is subject to change.
drh18de4822003-01-16 16:28:53 +0000499*/
danielk1977f9d64d22004-06-19 08:18:07 +0000500void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh19e2d372005-08-29 23:00:03 +0000501void *sqlite3_profile(sqlite3*,
502 void(*xProfile)(void*,const char*,sqlite_uint64), void*);
drh18de4822003-01-16 16:28:53 +0000503
danielk1977348bb5d2003-10-18 09:37:26 +0000504/*
505** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000506** is invoked periodically during long running calls to sqlite3_exec(),
danielk19772097e942004-11-20 06:05:56 +0000507** sqlite3_step() and sqlite3_get_table(). An example use for this API is to
508** keep a GUI updated during a large query.
danielk1977348bb5d2003-10-18 09:37:26 +0000509**
510** The progress callback is invoked once for every N virtual machine opcodes,
511** where N is the second argument to this function. The progress callback
512** itself is identified by the third argument to this function. The fourth
513** argument to this function is a void pointer passed to the progress callback
514** function each time it is invoked.
515**
danielk19776f8a5032004-05-10 10:34:51 +0000516** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000517** in less than N opcodes being executed, then the progress callback is not
518** invoked.
519**
danielk1977348bb5d2003-10-18 09:37:26 +0000520** To remove the progress callback altogether, pass NULL as the third
521** argument to this function.
522**
523** If the progress callback returns a result other than 0, then the current
524** query is immediately terminated and any database changes rolled back. If the
525** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000526** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000527**
528******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000529*/
danielk1977f9d64d22004-06-19 08:18:07 +0000530void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000531
drhaa940ea2004-01-15 02:44:03 +0000532/*
533** Register a callback function to be invoked whenever a new transaction
534** is committed. The pArg argument is passed through to the callback.
535** callback. If the callback function returns non-zero, then the commit
536** is converted into a rollback.
537**
538** If another function was previously registered, its pArg value is returned.
539** Otherwise NULL is returned.
540**
541** Registering a NULL function disables the callback.
542**
543******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
544*/
danielk1977f9d64d22004-06-19 08:18:07 +0000545void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000546
drh22fbcb82004-02-01 01:22:50 +0000547/*
drh4f26d6c2004-05-26 23:25:30 +0000548** Open the sqlite database file "filename". The "filename" is UTF-8
549** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
550** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
551** if an error occurs. If the database is opened (or created) successfully,
552** then SQLITE_OK is returned. Otherwise an error code is returned. The
553** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
554** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000555**
drh4f26d6c2004-05-26 23:25:30 +0000556** If the database file does not exist, then a new database is created.
557** The encoding for the database is UTF-8 if sqlite3_open() is called and
558** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000559**
560** Whether or not an error occurs when it is opened, resources associated
561** with the sqlite3* handle should be released by passing it to
562** sqlite3_close() when it is no longer required.
563*/
564int sqlite3_open(
565 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000566 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000567);
danielk197765904932004-05-26 06:18:37 +0000568int sqlite3_open16(
569 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000570 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000571);
danielk1977295ba552004-05-19 10:34:51 +0000572
danielk197765904932004-05-26 06:18:37 +0000573/*
574** Return the error code for the most recent sqlite3_* API call associated
575** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
576** API call was successful.
577**
578** Calls to many sqlite3_* functions set the error code and string returned
579** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
580** (overwriting the previous values). Note that calls to sqlite3_errcode(),
581** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
582** results of future invocations.
583**
584** Assuming no other intervening sqlite3_* API calls are made, the error
585** code returned by this function is associated with the same error as
586** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
587*/
588int sqlite3_errcode(sqlite3 *db);
589
590/*
591** Return a pointer to a UTF-8 encoded string describing in english the
592** error condition for the most recent sqlite3_* API call. The returned
593** string is always terminated by an 0x00 byte.
594**
595** The string "not an error" is returned when the most recent API call was
596** successful.
597*/
598const char *sqlite3_errmsg(sqlite3*);
599
600/*
601** Return a pointer to a UTF-16 native byte order encoded string describing
602** in english the error condition for the most recent sqlite3_* API call.
603** The returned string is always terminated by a pair of 0x00 bytes.
604**
605** The string "not an error" is returned when the most recent API call was
606** successful.
607*/
608const void *sqlite3_errmsg16(sqlite3*);
609
610/*
611** An instance of the following opaque structure is used to represent
612** a compiled SQL statment.
613*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000614typedef struct sqlite3_stmt sqlite3_stmt;
615
danielk1977e3209e42004-05-20 01:40:18 +0000616/*
danielk197765904932004-05-26 06:18:37 +0000617** To execute an SQL query, it must first be compiled into a byte-code
618** program using one of the following routines. The only difference between
619** them is that the second argument, specifying the SQL statement to
620** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
621** function and UTF-16 for sqlite3_prepare16().
622**
623** The first parameter "db" is an SQLite database handle. The second
624** parameter "zSql" is the statement to be compiled, encoded as either
625** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
626** than zero, then zSql is read up to the first nul terminator. If
627** "nBytes" is not less than zero, then it is the length of the string zSql
628** in bytes (not characters).
629**
630** *pzTail is made to point to the first byte past the end of the first
631** SQL statement in zSql. This routine only compiles the first statement
632** in zSql, so *pzTail is left pointing to what remains uncompiled.
633**
634** *ppStmt is left pointing to a compiled SQL statement that can be
635** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
636** set to NULL. If the input text contained no SQL (if the input is and
637** empty string or a comment) then *ppStmt is set to NULL.
638**
639** On success, SQLITE_OK is returned. Otherwise an error code is returned.
640*/
641int sqlite3_prepare(
642 sqlite3 *db, /* Database handle */
643 const char *zSql, /* SQL statement, UTF-8 encoded */
644 int nBytes, /* Length of zSql in bytes. */
645 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
646 const char **pzTail /* OUT: Pointer to unused portion of zSql */
647);
648int sqlite3_prepare16(
649 sqlite3 *db, /* Database handle */
650 const void *zSql, /* SQL statement, UTF-16 encoded */
651 int nBytes, /* Length of zSql in bytes. */
652 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
653 const void **pzTail /* OUT: Pointer to unused portion of zSql */
654);
655
656/*
drhf4479502004-05-27 03:12:53 +0000657** Pointers to the following two opaque structures are used to communicate
658** with the implementations of user-defined functions.
659*/
660typedef struct sqlite3_context sqlite3_context;
661typedef struct Mem sqlite3_value;
662
663/*
drh4f26d6c2004-05-26 23:25:30 +0000664** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
drh32c0d4f2004-12-07 02:14:51 +0000665** one or more literals can be replace by parameters "?" or ":AAA" or
666** "$VVV" where AAA is an identifer and VVV is a variable name according
667** to the syntax rules of the TCL programming language.
668** The value of these parameters (also called "host parameter names") can
669** be set using the routines listed below.
drh4f26d6c2004-05-26 23:25:30 +0000670**
671** In every case, the first parameter is a pointer to the sqlite3_stmt
672** structure returned from sqlite3_prepare(). The second parameter is the
drh32c0d4f2004-12-07 02:14:51 +0000673** index of the parameter. The first parameter as an index of 1. For
674** named parameters (":AAA" or "$VVV") you can use
675** sqlite3_bind_parameter_index() to get the correct index value given
676** the parameters name. If the same named parameter occurs more than
677** once, it is assigned the same index each time.
drh4f26d6c2004-05-26 23:25:30 +0000678**
drh900dfba2004-07-21 15:21:36 +0000679** The fifth parameter to sqlite3_bind_blob(), sqlite3_bind_text(), and
680** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or
681** text after SQLite has finished with it. If the fifth argument is the
682** special value SQLITE_STATIC, then the library assumes that the information
683** is in static, unmanaged space and does not need to be freed. If the
684** fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its
685** own private copy of the data.
drh4f26d6c2004-05-26 23:25:30 +0000686**
687** The sqlite3_bind_* routine must be called before sqlite3_step() after
drh32c0d4f2004-12-07 02:14:51 +0000688** an sqlite3_prepare() or sqlite3_reset(). Unbound parameterss are
689** interpreted as NULL.
drh4f26d6c2004-05-26 23:25:30 +0000690*/
danielk1977d8123362004-06-12 09:25:12 +0000691int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000692int sqlite3_bind_double(sqlite3_stmt*, int, double);
693int sqlite3_bind_int(sqlite3_stmt*, int, int);
drhefad9992004-06-22 12:13:55 +0000694int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64);
drhf4479502004-05-27 03:12:53 +0000695int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000696int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
697int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000698int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000699
700/*
drh32c0d4f2004-12-07 02:14:51 +0000701** Return the number of parameters in a compiled SQL statement. This
drh75f6a032004-07-15 14:15:00 +0000702** routine was added to support DBD::SQLite.
drh75f6a032004-07-15 14:15:00 +0000703*/
704int sqlite3_bind_parameter_count(sqlite3_stmt*);
705
706/*
drh32c0d4f2004-12-07 02:14:51 +0000707** Return the name of the i-th parameter. Ordinary parameters "?" are
708** nameless and a NULL is returned. For parameters of the form :AAA or
709** $VVV the complete text of the parameter name is returned, including
710** the initial ":" or "$". NULL is returned if the index is out of range.
drh895d7472004-08-20 16:02:39 +0000711*/
712const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
713
714/*
drhfa6bc002004-09-07 16:19:52 +0000715** Return the index of a parameter with the given name. The name
716** must match exactly. If no parameter with the given name is found,
717** return 0.
718*/
719int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
720
721/*
danielk1977600dd0b2005-01-20 01:14:23 +0000722** Set all the parameters in the compiled SQL statement to NULL.
danielk1977600dd0b2005-01-20 01:14:23 +0000723*/
724int sqlite3_clear_bindings(sqlite3_stmt*);
725
726/*
danielk197765904932004-05-26 06:18:37 +0000727** Return the number of columns in the result set returned by the compiled
728** SQL statement. This routine returns 0 if pStmt is an SQL statement
729** that does not return data (for example an UPDATE).
730*/
731int sqlite3_column_count(sqlite3_stmt *pStmt);
732
733/*
734** The first parameter is a compiled SQL statement. This function returns
735** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000736** second function parameter. The string returned is UTF-8 for
737** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000738*/
739const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000740const void *sqlite3_column_name16(sqlite3_stmt*,int);
741
742/*
danielk1977955de522006-02-10 02:27:42 +0000743** The first parameter to the following calls is a compiled SQL statement.
744** These functions return information about the Nth column returned by
745** the statement, where N is the second function argument.
746**
747** If the Nth column returned by the statement is not a column value,
748** then all of the functions return NULL. Otherwise, the return the
749** name of the attached database, table and column that the expression
750** extracts a value from.
751**
752** As with all other SQLite APIs, those postfixed with "16" return UTF-16
753** encoded strings, the other functions return UTF-8. The memory containing
754** the returned strings is valid until the statement handle is finalized().
danielk19774b1ae992006-02-10 03:06:10 +0000755**
756** These APIs are only available if the library was compiled with the
757** SQLITE_ENABLE_COLUMN_METADATA preprocessor symbol defined.
danielk1977955de522006-02-10 02:27:42 +0000758*/
759const char *sqlite3_column_database_name(sqlite3_stmt*,int);
760const void *sqlite3_column_database_name16(sqlite3_stmt*,int);
761const char *sqlite3_column_table_name(sqlite3_stmt*,int);
762const void *sqlite3_column_table_name16(sqlite3_stmt*,int);
763const char *sqlite3_column_origin_name(sqlite3_stmt*,int);
764const void *sqlite3_column_origin_name16(sqlite3_stmt*,int);
765
766/*
danielk197765904932004-05-26 06:18:37 +0000767** The first parameter is a compiled SQL statement. If this statement
768** is a SELECT statement, the Nth column of the returned result set
769** of the SELECT is a table column then the declared type of the table
770** column is returned. If the Nth column of the result set is not at table
771** column, then a NULL pointer is returned. The returned string is always
772** UTF-8 encoded. For example, in the database schema:
773**
774** CREATE TABLE t1(c1 VARIANT);
775**
776** And the following statement compiled:
777**
danielk1977955de522006-02-10 02:27:42 +0000778** SELECT c1 + 1, c1 FROM t1;
danielk197765904932004-05-26 06:18:37 +0000779**
780** Then this routine would return the string "VARIANT" for the second
781** result column (i==1), and a NULL pointer for the first result column
782** (i==0).
783*/
784const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
785
786/*
787** The first parameter is a compiled SQL statement. If this statement
788** is a SELECT statement, the Nth column of the returned result set
789** of the SELECT is a table column then the declared type of the table
790** column is returned. If the Nth column of the result set is not at table
791** column, then a NULL pointer is returned. The returned string is always
792** UTF-16 encoded. For example, in the database schema:
793**
drh4f26d6c2004-05-26 23:25:30 +0000794** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000795**
796** And the following statement compiled:
797**
danielk1977955de522006-02-10 02:27:42 +0000798** SELECT c1 + 1, c1 FROM t1;
danielk197765904932004-05-26 06:18:37 +0000799**
drh4f26d6c2004-05-26 23:25:30 +0000800** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000801** result column (i==1), and a NULL pointer for the first result column
802** (i==0).
803*/
804const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
805
danielk1977106bb232004-05-21 10:08:53 +0000806/*
807** After an SQL query has been compiled with a call to either
808** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
809** called one or more times to execute the statement.
810**
811** The return value will be either SQLITE_BUSY, SQLITE_DONE,
812** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
813**
814** SQLITE_BUSY means that the database engine attempted to open
815** a locked database and there is no busy callback registered.
816** Call sqlite3_step() again to retry the open.
817**
818** SQLITE_DONE means that the statement has finished executing
819** successfully. sqlite3_step() should not be called again on this virtual
820** machine.
821**
822** If the SQL statement being executed returns any data, then
823** SQLITE_ROW is returned each time a new row of data is ready
824** for processing by the caller. The values may be accessed using
825** the sqlite3_column_*() functions described below. sqlite3_step()
826** is called again to retrieve the next row of data.
827**
828** SQLITE_ERROR means that a run-time error (such as a constraint
829** violation) has occurred. sqlite3_step() should not be called again on
830** the VM. More information may be found by calling sqlite3_errmsg().
831**
832** SQLITE_MISUSE means that the this routine was called inappropriately.
833** Perhaps it was called on a virtual machine that had already been
834** finalized or on one that had previously returned SQLITE_ERROR or
835** SQLITE_DONE. Or it could be the case the the same database connection
836** is being used simulataneously by two or more threads.
837*/
danielk197717240fd2004-05-26 00:07:25 +0000838int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000839
danielk1977106bb232004-05-21 10:08:53 +0000840/*
841** Return the number of values in the current row of the result set.
842**
843** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
844** will return the same value as the sqlite3_column_count() function.
845** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
846** error code, or before sqlite3_step() has been called on a
847** compiled SQL statement, this routine returns zero.
848*/
danielk197793d46752004-05-23 13:30:58 +0000849int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000850
drh4f26d6c2004-05-26 23:25:30 +0000851/*
852** Values are stored in the database in one of the following fundamental
853** types.
854*/
drh9c054832004-05-31 18:51:57 +0000855#define SQLITE_INTEGER 1
856#define SQLITE_FLOAT 2
drh1e284f42004-10-06 15:52:01 +0000857/* #define SQLITE_TEXT 3 // See below */
drh9c054832004-05-31 18:51:57 +0000858#define SQLITE_BLOB 4
859#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000860
danielk1977106bb232004-05-21 10:08:53 +0000861/*
drh1e284f42004-10-06 15:52:01 +0000862** SQLite version 2 defines SQLITE_TEXT differently. To allow both
863** version 2 and version 3 to be included, undefine them both if a
864** conflict is seen. Define SQLITE3_TEXT to be the version 3 value.
865*/
866#ifdef SQLITE_TEXT
867# undef SQLITE_TEXT
868#else
869# define SQLITE_TEXT 3
870#endif
871#define SQLITE3_TEXT 3
872
873/*
drh4f26d6c2004-05-26 23:25:30 +0000874** The next group of routines returns information about the information
875** in a single column of the current result row of a query. In every
876** case the first parameter is a pointer to the SQL statement that is being
877** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
878** the second argument is the index of the column for which information
879** should be returned. iCol is zero-indexed. The left-most column as an
880** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000881**
drh4f26d6c2004-05-26 23:25:30 +0000882** If the SQL statement is not currently point to a valid row, or if the
883** the colulmn index is out of range, the result is undefined.
884**
885** These routines attempt to convert the value where appropriate. For
886** example, if the internal representation is FLOAT and a text result
887** is requested, sprintf() is used internally to do the conversion
888** automatically. The following table details the conversions that
889** are applied:
890**
891** Internal Type Requested Type Conversion
892** ------------- -------------- --------------------------
893** NULL INTEGER Result is 0
894** NULL FLOAT Result is 0.0
895** NULL TEXT Result is an empty string
896** NULL BLOB Result is a zero-length BLOB
897** INTEGER FLOAT Convert from integer to float
898** INTEGER TEXT ASCII rendering of the integer
899** INTEGER BLOB Same as for INTEGER->TEXT
900** FLOAT INTEGER Convert from float to integer
901** FLOAT TEXT ASCII rendering of the float
902** FLOAT BLOB Same as FLOAT->TEXT
903** TEXT INTEGER Use atoi()
904** TEXT FLOAT Use atof()
905** TEXT BLOB No change
906** BLOB INTEGER Convert to TEXT then use atoi()
907** BLOB FLOAT Convert to TEXT then use atof()
908** BLOB TEXT Add a \000 terminator if needed
909**
910** The following access routines are provided:
911**
912** _type() Return the datatype of the result. This is one of
913** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
914** or SQLITE_NULL.
915** _blob() Return the value of a BLOB.
916** _bytes() Return the number of bytes in a BLOB value or the number
917** of bytes in a TEXT value represented as UTF-8. The \000
918** terminator is included in the byte count for TEXT values.
919** _bytes16() Return the number of bytes in a BLOB value or the number
920** of bytes in a TEXT value represented as UTF-16. The \u0000
921** terminator is included in the byte count for TEXT values.
922** _double() Return a FLOAT value.
923** _int() Return an INTEGER value in the host computer's native
924** integer representation. This might be either a 32- or 64-bit
925** integer depending on the host.
926** _int64() Return an INTEGER value as a 64-bit signed integer.
927** _text() Return the value as UTF-8 text.
928** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000929*/
drhf4479502004-05-27 03:12:53 +0000930const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
931int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
932int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
933double sqlite3_column_double(sqlite3_stmt*, int iCol);
934int sqlite3_column_int(sqlite3_stmt*, int iCol);
drhefad9992004-06-22 12:13:55 +0000935sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +0000936const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
937const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000938int sqlite3_column_type(sqlite3_stmt*, int iCol);
drh29d72102006-02-09 22:13:41 +0000939int sqlite3_column_numeric_type(sqlite3_stmt*, int iCol);
drh4be8b512006-06-13 23:51:34 +0000940sqlite3_value *sqlite3_column_value(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000941
danielk197765904932004-05-26 06:18:37 +0000942/*
943** The sqlite3_finalize() function is called to delete a compiled
944** SQL statement obtained by a previous call to sqlite3_prepare()
945** or sqlite3_prepare16(). If the statement was executed successfully, or
946** not executed at all, then SQLITE_OK is returned. If execution of the
947** statement failed then an error code is returned.
948**
949** This routine can be called at any point during the execution of the
950** virtual machine. If the virtual machine has not completed execution
951** when this routine is called, that is like encountering an error or
952** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
953** rolled back and transactions cancelled, depending on the circumstances,
954** and the result code returned will be SQLITE_ABORT.
955*/
956int sqlite3_finalize(sqlite3_stmt *pStmt);
957
958/*
959** The sqlite3_reset() function is called to reset a compiled SQL
960** statement obtained by a previous call to sqlite3_prepare() or
961** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
962** Any SQL statement variables that had values bound to them using
963** the sqlite3_bind_*() API retain their values.
964*/
965int sqlite3_reset(sqlite3_stmt *pStmt);
966
967/*
danielk197765904932004-05-26 06:18:37 +0000968** The following two functions are used to add user functions or aggregates
969** implemented in C to the SQL langauge interpreted by SQLite. The
970** difference only between the two is that the second parameter, the
971** name of the (scalar) function or aggregate, is encoded in UTF-8 for
972** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
973**
974** The first argument is the database handle that the new function or
975** aggregate is to be added to. If a single program uses more than one
976** database handle internally, then user functions or aggregates must
977** be added individually to each database handle with which they will be
978** used.
979**
980** The third parameter is the number of arguments that the function or
981** aggregate takes. If this parameter is negative, then the function or
982** aggregate may take any number of arguments.
983**
danielk1977d8123362004-06-12 09:25:12 +0000984** The fourth parameter is one of SQLITE_UTF* values defined below,
985** indicating the encoding that the function is most likely to handle
986** values in. This does not change the behaviour of the programming
987** interface. However, if two versions of the same function are registered
988** with different encoding values, SQLite invokes the version likely to
989** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +0000990**
danielk197765904932004-05-26 06:18:37 +0000991** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
992** pointers to user implemented C functions that implement the user
993** function or aggregate. A scalar function requires an implementation of
994** the xFunc callback only, NULL pointers should be passed as the xStep
995** and xFinal parameters. An aggregate function requires an implementation
996** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
997** existing user function or aggregate, pass NULL for all three function
998** callback. Specifying an inconstent set of callback values, such as an
999** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
1000** returned.
1001*/
1002int sqlite3_create_function(
1003 sqlite3 *,
1004 const char *zFunctionName,
1005 int nArg,
1006 int eTextRep,
danielk197765904932004-05-26 06:18:37 +00001007 void*,
1008 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
1009 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
1010 void (*xFinal)(sqlite3_context*)
1011);
1012int sqlite3_create_function16(
1013 sqlite3*,
1014 const void *zFunctionName,
1015 int nArg,
1016 int eTextRep,
danielk197765904932004-05-26 06:18:37 +00001017 void*,
1018 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
1019 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
1020 void (*xFinal)(sqlite3_context*)
1021);
1022
1023/*
drhcf85a512006-02-09 18:35:29 +00001024** This function is deprecated. Do not use it. It continues to exist
1025** so as not to break legacy code. But new code should avoid using it.
danielk197765904932004-05-26 06:18:37 +00001026*/
1027int sqlite3_aggregate_count(sqlite3_context*);
1028
danielk19770ffba6b2004-05-24 09:10:10 +00001029/*
drh4f26d6c2004-05-26 23:25:30 +00001030** The next group of routines returns information about parameters to
1031** a user-defined function. Function implementations use these routines
1032** to access their parameters. These routines are the same as the
1033** sqlite3_column_* routines except that these routines take a single
1034** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
1035** column number.
danielk19770ffba6b2004-05-24 09:10:10 +00001036*/
drhf4479502004-05-27 03:12:53 +00001037const void *sqlite3_value_blob(sqlite3_value*);
1038int sqlite3_value_bytes(sqlite3_value*);
1039int sqlite3_value_bytes16(sqlite3_value*);
1040double sqlite3_value_double(sqlite3_value*);
1041int sqlite3_value_int(sqlite3_value*);
drhefad9992004-06-22 12:13:55 +00001042sqlite_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +00001043const unsigned char *sqlite3_value_text(sqlite3_value*);
1044const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +00001045const void *sqlite3_value_text16le(sqlite3_value*);
1046const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +00001047int sqlite3_value_type(sqlite3_value*);
drh29d72102006-02-09 22:13:41 +00001048int sqlite3_value_numeric_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +00001049
1050/*
danielk19770ae8b832004-05-25 12:05:56 +00001051** Aggregate functions use the following routine to allocate
1052** a structure for storing their state. The first time this routine
1053** is called for a particular aggregate, a new structure of size nBytes
1054** is allocated, zeroed, and returned. On subsequent calls (for the
1055** same aggregate instance) the same buffer is returned. The implementation
1056** of the aggregate can use the returned buffer to accumulate data.
1057**
1058** The buffer allocated is freed automatically by SQLite.
1059*/
drh4f26d6c2004-05-26 23:25:30 +00001060void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +00001061
1062/*
drhc0f2a012005-07-09 02:39:40 +00001063** The pUserData parameter to the sqlite3_create_function()
1064** routine used to register user functions is available to
1065** the implementation of the function using this call.
danielk19777e18c252004-05-25 11:47:24 +00001066*/
1067void *sqlite3_user_data(sqlite3_context*);
1068
1069/*
danielk1977682f68b2004-06-05 10:22:17 +00001070** The following two functions may be used by scalar user functions to
1071** associate meta-data with argument values. If the same value is passed to
1072** multiple invocations of the user-function during query execution, under
1073** some circumstances the associated meta-data may be preserved. This may
1074** be used, for example, to add a regular-expression matching scalar
1075** function. The compiled version of the regular expression is stored as
1076** meta-data associated with the SQL value passed as the regular expression
1077** pattern.
1078**
1079** Calling sqlite3_get_auxdata() returns a pointer to the meta data
1080** associated with the Nth argument value to the current user function
1081** call, where N is the second parameter. If no meta-data has been set for
1082** that value, then a NULL pointer is returned.
1083**
1084** The sqlite3_set_auxdata() is used to associate meta data with a user
1085** function argument. The third parameter is a pointer to the meta data
1086** to be associated with the Nth user function argument value. The fourth
1087** parameter specifies a 'delete function' that will be called on the meta
1088** data pointer to release it when it is no longer required. If the delete
1089** function pointer is NULL, it is not invoked.
1090**
1091** In practice, meta-data is preserved between function calls for
1092** expressions that are constant at compile time. This includes literal
1093** values and SQL variables.
1094*/
1095void *sqlite3_get_auxdata(sqlite3_context*, int);
1096void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
1097
drha2854222004-06-17 19:04:17 +00001098
1099/*
1100** These are special value for the destructor that is passed in as the
1101** final argument to routines like sqlite3_result_blob(). If the destructor
1102** argument is SQLITE_STATIC, it means that the content pointer is constant
1103** and will never change. It does not need to be destroyed. The
1104** SQLITE_TRANSIENT value means that the content will likely change in
1105** the near future and that SQLite should make its own private copy of
1106** the content before returning.
1107*/
danielk1977d8123362004-06-12 09:25:12 +00001108#define SQLITE_STATIC ((void(*)(void *))0)
1109#define SQLITE_TRANSIENT ((void(*)(void *))-1)
1110
danielk1977682f68b2004-06-05 10:22:17 +00001111/*
drh4f26d6c2004-05-26 23:25:30 +00001112** User-defined functions invoke the following routines in order to
1113** set their return value.
danielk19777e18c252004-05-25 11:47:24 +00001114*/
danielk1977d8123362004-06-12 09:25:12 +00001115void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001116void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +00001117void sqlite3_result_error(sqlite3_context*, const char*, int);
1118void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +00001119void sqlite3_result_int(sqlite3_context*, int);
drhefad9992004-06-22 12:13:55 +00001120void sqlite3_result_int64(sqlite3_context*, sqlite_int64);
drh4f26d6c2004-05-26 23:25:30 +00001121void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +00001122void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
1123void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
1124void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
1125void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001126void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +00001127
drh52619df2004-06-11 17:48:02 +00001128/*
1129** These are the allowed values for the eTextRep argument to
1130** sqlite3_create_collation and sqlite3_create_function.
1131*/
drh7d9bd4e2006-02-16 18:16:36 +00001132#define SQLITE_UTF8 1
1133#define SQLITE_UTF16LE 2
1134#define SQLITE_UTF16BE 3
1135#define SQLITE_UTF16 4 /* Use native byte order */
1136#define SQLITE_ANY 5 /* sqlite3_create_function only */
1137#define SQLITE_UTF16_ALIGNED 8 /* sqlite3_create_collation only */
danielk1977466be562004-06-10 02:16:01 +00001138
danielk19777cedc8d2004-06-10 10:50:08 +00001139/*
1140** These two functions are used to add new collation sequences to the
1141** sqlite3 handle specified as the first argument.
1142**
1143** The name of the new collation sequence is specified as a UTF-8 string
1144** for sqlite3_create_collation() and a UTF-16 string for
1145** sqlite3_create_collation16(). In both cases the name is passed as the
1146** second function argument.
1147**
1148** The third argument must be one of the constants SQLITE_UTF8,
1149** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1150** routine expects to be passed pointers to strings encoded using UTF-8,
1151** UTF-16 little-endian or UTF-16 big-endian respectively.
1152**
1153** A pointer to the user supplied routine must be passed as the fifth
1154** argument. If it is NULL, this is the same as deleting the collation
1155** sequence (so that SQLite cannot call it anymore). Each time the user
1156** supplied function is invoked, it is passed a copy of the void* passed as
1157** the fourth argument to sqlite3_create_collation() or
1158** sqlite3_create_collation16() as its first parameter.
1159**
1160** The remaining arguments to the user-supplied routine are two strings,
1161** each represented by a [length, data] pair and encoded in the encoding
1162** that was passed as the third argument when the collation sequence was
1163** registered. The user routine should return negative, zero or positive if
1164** the first string is less than, equal to, or greater than the second
1165** string. i.e. (STRING1 - STRING2).
1166*/
danielk19770202b292004-06-09 09:55:16 +00001167int sqlite3_create_collation(
1168 sqlite3*,
1169 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001170 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001171 void*,
1172 int(*xCompare)(void*,int,const void*,int,const void*)
1173);
1174int sqlite3_create_collation16(
1175 sqlite3*,
1176 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001177 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001178 void*,
1179 int(*xCompare)(void*,int,const void*,int,const void*)
1180);
1181
danielk19777cedc8d2004-06-10 10:50:08 +00001182/*
1183** To avoid having to register all collation sequences before a database
1184** can be used, a single callback function may be registered with the
1185** database handle to be called whenever an undefined collation sequence is
1186** required.
1187**
1188** If the function is registered using the sqlite3_collation_needed() API,
1189** then it is passed the names of undefined collation sequences as strings
1190** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1191** are passed as UTF-16 in machine native byte order. A call to either
1192** function replaces any existing callback.
1193**
1194** When the user-function is invoked, the first argument passed is a copy
1195** of the second argument to sqlite3_collation_needed() or
1196** sqlite3_collation_needed16(). The second argument is the database
1197** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1198** SQLITE_UTF16LE, indicating the most desirable form of the collation
1199** sequence function required. The fourth parameter is the name of the
1200** required collation sequence.
1201**
1202** The collation sequence is returned to SQLite by a collation-needed
1203** callback using the sqlite3_create_collation() or
1204** sqlite3_create_collation16() APIs, described above.
1205*/
1206int sqlite3_collation_needed(
1207 sqlite3*,
1208 void*,
1209 void(*)(void*,sqlite3*,int eTextRep,const char*)
1210);
1211int sqlite3_collation_needed16(
1212 sqlite3*,
1213 void*,
1214 void(*)(void*,sqlite3*,int eTextRep,const void*)
1215);
1216
drh2011d5f2004-07-22 02:40:37 +00001217/*
1218** Specify the key for an encrypted database. This routine should be
1219** called right after sqlite3_open().
1220**
1221** The code to implement this API is not available in the public release
1222** of SQLite.
1223*/
1224int sqlite3_key(
1225 sqlite3 *db, /* Database to be rekeyed */
1226 const void *pKey, int nKey /* The key */
1227);
1228
1229/*
1230** Change the key on an open database. If the current database is not
1231** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the
1232** database is decrypted.
1233**
1234** The code to implement this API is not available in the public release
1235** of SQLite.
1236*/
1237int sqlite3_rekey(
1238 sqlite3 *db, /* Database to be rekeyed */
1239 const void *pKey, int nKey /* The new key */
1240);
danielk19770202b292004-06-09 09:55:16 +00001241
drhab3f9fe2004-08-14 17:10:10 +00001242/*
danielk1977600dd0b2005-01-20 01:14:23 +00001243** Sleep for a little while. The second parameter is the number of
1244** miliseconds to sleep for.
1245**
1246** If the operating system does not support sleep requests with
1247** milisecond time resolution, then the time will be rounded up to
1248** the nearest second. The number of miliseconds of sleep actually
1249** requested from the operating system is returned.
danielk1977600dd0b2005-01-20 01:14:23 +00001250*/
1251int sqlite3_sleep(int);
1252
1253/*
drh65efb652005-06-12 22:12:39 +00001254** Return TRUE (non-zero) if the statement supplied as an argument needs
drhd89bd002005-01-22 03:03:54 +00001255** to be recompiled. A statement needs to be recompiled whenever the
1256** execution environment changes in a way that would alter the program
1257** that sqlite3_prepare() generates. For example, if new functions or
1258** collating sequences are registered or if an authorizer function is
1259** added or changed.
1260**
drhd89bd002005-01-22 03:03:54 +00001261*/
1262int sqlite3_expired(sqlite3_stmt*);
1263
1264/*
drhf8db1bc2005-04-22 02:38:37 +00001265** Move all bindings from the first prepared statement over to the second.
1266** This routine is useful, for example, if the first prepared statement
1267** fails with an SQLITE_SCHEMA error. The same SQL can be prepared into
1268** the second prepared statement then all of the bindings transfered over
1269** to the second statement before the first statement is finalized.
drhf8db1bc2005-04-22 02:38:37 +00001270*/
1271int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*);
1272
1273/*
tpoindex9a09a3c2004-12-20 19:01:32 +00001274** If the following global variable is made to point to a
drhab3f9fe2004-08-14 17:10:10 +00001275** string which is the name of a directory, then all temporary files
1276** created by SQLite will be placed in that directory. If this variable
1277** is NULL pointer, then SQLite does a search for an appropriate temporary
1278** file directory.
1279**
danielk19776b456a22005-03-21 04:04:02 +00001280** Once sqlite3_open() has been called, changing this variable will invalidate
1281** the current temporary database, if any.
drhab3f9fe2004-08-14 17:10:10 +00001282*/
tpoindex9a09a3c2004-12-20 19:01:32 +00001283extern char *sqlite3_temp_directory;
drhab3f9fe2004-08-14 17:10:10 +00001284
danielk19776b456a22005-03-21 04:04:02 +00001285/*
1286** This function is called to recover from a malloc() failure that occured
1287** within the SQLite library. Normally, after a single malloc() fails the
1288** library refuses to function (all major calls return SQLITE_NOMEM).
drh9a7e6082005-03-31 22:26:19 +00001289** This function restores the library state so that it can be used again.
danielk19776b456a22005-03-21 04:04:02 +00001290**
1291** All existing statements (sqlite3_stmt pointers) must be finalized or
1292** reset before this call is made. Otherwise, SQLITE_BUSY is returned.
1293** If any in-memory databases are in use, either as a main or TEMP
1294** database, SQLITE_ERROR is returned. In either of these cases, the
1295** library is not reset and remains unusable.
1296**
1297** This function is *not* threadsafe. Calling this from within a threaded
1298** application when threads other than the caller have used SQLite is
1299** dangerous and will almost certainly result in malfunctions.
1300**
1301** This functionality can be omitted from a build by defining the
1302** SQLITE_OMIT_GLOBALRECOVER at compile time.
1303*/
drhd9cb6ac2005-10-20 07:28:17 +00001304int sqlite3_global_recover(void);
danielk19776b456a22005-03-21 04:04:02 +00001305
drh3e1d8e62005-05-26 16:23:34 +00001306/*
1307** Test to see whether or not the database connection is in autocommit
1308** mode. Return TRUE if it is and FALSE if not. Autocommit mode is on
1309** by default. Autocommit is disabled by a BEGIN statement and reenabled
1310** by the next COMMIT or ROLLBACK.
drh3e1d8e62005-05-26 16:23:34 +00001311*/
1312int sqlite3_get_autocommit(sqlite3*);
1313
drh51942bc2005-06-12 22:01:42 +00001314/*
1315** Return the sqlite3* database handle to which the prepared statement given
1316** in the argument belongs. This is the same database handle that was
1317** the first argument to the sqlite3_prepare() that was used to create
1318** the statement in the first place.
1319*/
1320sqlite3 *sqlite3_db_handle(sqlite3_stmt*);
drh3e1d8e62005-05-26 16:23:34 +00001321
drhb37df7b2005-10-13 02:09:49 +00001322/*
danielk197794eb6a12005-12-15 15:22:08 +00001323** Register a callback function with the database connection identified by the
1324** first argument to be invoked whenever a row is updated, inserted or deleted.
1325** Any callback set by a previous call to this function for the same
1326** database connection is overridden.
1327**
1328** The second argument is a pointer to the function to invoke when a
1329** row is updated, inserted or deleted. The first argument to the callback is
1330** a copy of the third argument to sqlite3_update_hook. The second callback
1331** argument is one of SQLITE_INSERT, SQLITE_DELETE or SQLITE_UPDATE, depending
1332** on the operation that caused the callback to be invoked. The third and
1333** fourth arguments to the callback contain pointers to the database and
1334** table name containing the affected row. The final callback parameter is
1335** the rowid of the row. In the case of an update, this is the rowid after
1336** the update takes place.
1337**
1338** The update hook is not invoked when internal system tables are
1339** modified (i.e. sqlite_master and sqlite_sequence).
danielk197771fd80b2005-12-16 06:54:01 +00001340**
1341** If another function was previously registered, its pArg value is returned.
1342** Otherwise NULL is returned.
danielk197794eb6a12005-12-15 15:22:08 +00001343*/
danielk197771fd80b2005-12-16 06:54:01 +00001344void *sqlite3_update_hook(
danielk197794eb6a12005-12-15 15:22:08 +00001345 sqlite3*,
1346 void(*)(void *,int ,char const *,char const *,sqlite_int64),
1347 void*
1348);
danielk197713a68c32005-12-15 10:11:30 +00001349
danielk1977f3f06bb2005-12-16 15:24:28 +00001350/*
1351** Register a callback to be invoked whenever a transaction is rolled
1352** back.
1353**
1354** The new callback function overrides any existing rollback-hook
1355** callback. If there was an existing callback, then it's pArg value
1356** (the third argument to sqlite3_rollback_hook() when it was registered)
1357** is returned. Otherwise, NULL is returned.
1358**
1359** For the purposes of this API, a transaction is said to have been
1360** rolled back if an explicit "ROLLBACK" statement is executed, or
1361** an error or constraint causes an implicit rollback to occur. The
1362** callback is not invoked if a transaction is automatically rolled
1363** back because the database connection is closed.
1364*/
danielk197771fd80b2005-12-16 06:54:01 +00001365void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*);
1366
danielk19777ddad962005-12-12 06:53:03 +00001367/*
danielk1977aef0bf62005-12-30 16:28:01 +00001368** This function is only available if the library is compiled without
1369** the SQLITE_OMIT_SHARED_CACHE macro defined. It is used to enable or
1370** disable (if the argument is true or false, respectively) the
1371** "shared pager" feature.
1372*/
1373int sqlite3_enable_shared_cache(int);
1374
1375/*
danielk197752622822006-01-09 09:59:49 +00001376** Attempt to free N bytes of heap memory by deallocating non-essential
1377** memory allocations held by the database library (example: memory
1378** used to cache database pages to improve performance).
1379**
drh6f7adc82006-01-11 21:41:20 +00001380** This function is not a part of standard builds. It is only created
1381** if SQLite is compiled with the SQLITE_ENABLE_MEMORY_MANAGEMENT macro.
danielk197752622822006-01-09 09:59:49 +00001382*/
1383int sqlite3_release_memory(int);
1384
1385/*
1386** Place a "soft" limit on the amount of heap memory that may be allocated by
1387** SQLite within the current thread. If an internal allocation is requested
1388** that would exceed the specified limit, sqlite3_release_memory() is invoked
1389** one or more times to free up some space before the allocation is made.
1390**
1391** The limit is called "soft", because if sqlite3_release_memory() cannot free
1392** sufficient memory to prevent the limit from being exceeded, the memory is
1393** allocated anyway and the current operation proceeds.
1394**
drh6f7adc82006-01-11 21:41:20 +00001395** This function is only available if the library was compiled with the
1396** SQLITE_ENABLE_MEMORY_MANAGEMENT option set.
danielk197752622822006-01-09 09:59:49 +00001397** memory-management has been enabled.
1398*/
drhd2d4a6b2006-01-10 15:18:27 +00001399void sqlite3_soft_heap_limit(int);
danielk197752622822006-01-09 09:59:49 +00001400
1401/*
drh6f7adc82006-01-11 21:41:20 +00001402** This routine makes sure that all thread-local storage has been
1403** deallocated for the current thread.
1404**
1405** This routine is not technically necessary. All thread-local storage
1406** will be automatically deallocated once memory-management and
1407** shared-cache are disabled and the soft heap limit has been set
1408** to zero. This routine is provided as a convenience for users who
1409** want to make absolutely sure they have not forgotten something
1410** prior to killing off a thread.
1411*/
1412void sqlite3_thread_cleanup(void);
1413
1414/*
danielk1977deb802c2006-02-09 13:43:28 +00001415** Return meta information about a specific column of a specific database
1416** table accessible using the connection handle passed as the first function
1417** argument.
1418**
1419** The column is identified by the second, third and fourth parameters to
1420** this function. The second parameter is either the name of the database
1421** (i.e. "main", "temp" or an attached database) containing the specified
1422** table or NULL. If it is NULL, then all attached databases are searched
1423** for the table using the same algorithm as the database engine uses to
1424** resolve unqualified table references.
1425**
1426** The third and fourth parameters to this function are the table and column
1427** name of the desired column, respectively. Neither of these parameters
1428** may be NULL.
1429**
1430** Meta information is returned by writing to the memory locations passed as
1431** the 5th and subsequent parameters to this function. Any of these
1432** arguments may be NULL, in which case the corresponding element of meta
1433** information is ommitted.
1434**
1435** Parameter Output Type Description
1436** -----------------------------------
1437**
1438** 5th const char* Data type
1439** 6th const char* Name of the default collation sequence
1440** 7th int True if the column has a NOT NULL constraint
1441** 8th int True if the column is part of the PRIMARY KEY
1442** 9th int True if the column is AUTOINCREMENT
1443**
1444**
1445** The memory pointed to by the character pointers returned for the
1446** declaration type and collation sequence is valid only until the next
1447** call to any sqlite API function.
1448**
1449** If the specified table is actually a view, then an error is returned.
1450**
1451** If the specified column is "rowid", "oid" or "_rowid_" and an
1452** INTEGER PRIMARY KEY column has been explicitly declared, then the output
1453** parameters are set for the explicitly declared column. If there is no
1454** explicitly declared IPK column, then the output parameters are set as
1455** follows:
1456**
1457** data type: "INTEGER"
1458** collation sequence: "BINARY"
1459** not null: 0
1460** primary key: 1
1461** auto increment: 0
1462**
1463** This function may load one or more schemas from database files. If an
1464** error occurs during this process, or if the requested table or column
1465** cannot be found, an SQLITE error code is returned and an error message
1466** left in the database handle (to be retrieved using sqlite3_errmsg()).
danielk19774b1ae992006-02-10 03:06:10 +00001467**
1468** This API is only available if the library was compiled with the
1469** SQLITE_ENABLE_COLUMN_METADATA preprocessor symbol defined.
danielk1977deb802c2006-02-09 13:43:28 +00001470*/
1471int sqlite3_table_column_metadata(
1472 sqlite3 *db, /* Connection handle */
1473 const char *zDbName, /* Database name or NULL */
1474 const char *zTableName, /* Table name */
1475 const char *zColumnName, /* Column name */
1476 char const **pzDataType, /* OUTPUT: Declared data type */
1477 char const **pzCollSeq, /* OUTPUT: Collation sequence name */
1478 int *pNotNull, /* OUTPUT: True if NOT NULL constraint exists */
1479 int *pPrimaryKey, /* OUTPUT: True if column part of PK */
1480 int *pAutoinc /* OUTPUT: True if colums is auto-increment */
1481);
1482
1483/*
drh1e397f82006-06-08 15:28:43 +00001484****** EXPERIMENTAL - subject to change without notice **************
1485**
1486** Attempt to load an SQLite extension library contained in the file
1487** zFile. The entry point is zProc. zProc may be 0 in which case the
drhc2e87a32006-06-27 15:16:14 +00001488** name of the entry point defaults to "sqlite3_extension_init".
drh1e397f82006-06-08 15:28:43 +00001489**
1490** Return SQLITE_OK on success and SQLITE_ERROR if something goes wrong.
1491**
1492** If an error occurs and pzErrMsg is not 0, then fill *pzErrMsg with
1493** error message text. The calling function should free this memory
1494** by calling sqlite3_free().
1495**
drhc2e87a32006-06-27 15:16:14 +00001496** Extension loading must be enabled using sqlite3_enable_load_extension()
1497** prior to calling this API or an error will be returned.
drh1e397f82006-06-08 15:28:43 +00001498**
1499****** EXPERIMENTAL - subject to change without notice **************
1500*/
1501int sqlite3_load_extension(
1502 sqlite3 *db, /* Load the extension into this database connection */
1503 const char *zFile, /* Name of the shared library containing extension */
1504 const char *zProc, /* Entry point. Derived from zFile if 0 */
1505 char **pzErrMsg /* Put error message here if not 0 */
1506);
1507
1508/*
drhc2e87a32006-06-27 15:16:14 +00001509** So as not to open security holes in older applications that are
1510** unprepared to deal with extension load, and as a means of disabling
1511** extension loading while executing user-entered SQL, the following
1512** API is provided to turn the extension loading mechanism on and
1513** off. It is off by default. See ticket #1863.
1514**
1515** Call this routine with onoff==1 to turn extension loading on
1516** and call it with onoff==0 to turn it back off again.
1517*/
1518int sqlite3_enable_load_extension(sqlite3 *db, int onoff);
1519
1520/*
drhe09daa92006-06-10 13:29:31 +00001521****** EXPERIMENTAL - subject to change without notice **************
drh9eff6162006-06-12 21:59:13 +00001522**
1523** The interface to the virtual-table mechanism is currently considered
1524** to be experimental. The interface might change in incompatible ways.
1525** If this is a problem for you, do not use the interface at this time.
1526**
1527** When the virtual-table mechanism stablizes, we will declare the
1528** interface fixed, support it indefinitely, and remove this comment.
1529*/
1530
1531/*
1532** Structures used by the virtual table interface
drhe09daa92006-06-10 13:29:31 +00001533*/
1534typedef struct sqlite3_vtab sqlite3_vtab;
1535typedef struct sqlite3_index_info sqlite3_index_info;
1536typedef struct sqlite3_vtab_cursor sqlite3_vtab_cursor;
1537typedef struct sqlite3_module sqlite3_module;
drh9eff6162006-06-12 21:59:13 +00001538
1539/*
1540** A module is a class of virtual tables. Each module is defined
1541** by an instance of the following structure. This structure consists
1542** mostly of methods for the module.
1543*/
drhe09daa92006-06-10 13:29:31 +00001544struct sqlite3_module {
1545 int iVersion;
danielk19779da9d472006-06-14 06:58:15 +00001546 int (*xCreate)(sqlite3*, void *pAux,
drhe09daa92006-06-10 13:29:31 +00001547 int argc, char **argv,
1548 sqlite3_vtab **ppVTab);
danielk19779da9d472006-06-14 06:58:15 +00001549 int (*xConnect)(sqlite3*, void *pAux,
drhe09daa92006-06-10 13:29:31 +00001550 int argc, char **argv,
1551 sqlite3_vtab **ppVTab);
1552 int (*xBestIndex)(sqlite3_vtab *pVTab, sqlite3_index_info*);
1553 int (*xDisconnect)(sqlite3_vtab *pVTab);
1554 int (*xDestroy)(sqlite3_vtab *pVTab);
1555 int (*xOpen)(sqlite3_vtab *pVTab, sqlite3_vtab_cursor **ppCursor);
1556 int (*xClose)(sqlite3_vtab_cursor*);
drh4be8b512006-06-13 23:51:34 +00001557 int (*xFilter)(sqlite3_vtab_cursor*, int idxNum, const char *idxStr,
drhe09daa92006-06-10 13:29:31 +00001558 int argc, sqlite3_value **argv);
1559 int (*xNext)(sqlite3_vtab_cursor*);
danielk1977a298e902006-06-22 09:53:48 +00001560 int (*xEof)(sqlite3_vtab_cursor*);
drhe09daa92006-06-10 13:29:31 +00001561 int (*xColumn)(sqlite3_vtab_cursor*, sqlite3_context*, int);
1562 int (*xRowid)(sqlite3_vtab_cursor*, sqlite_int64 *pRowid);
danielk19771f6eec52006-06-16 06:17:47 +00001563 int (*xUpdate)(sqlite3_vtab *, int, sqlite3_value **, sqlite_int64 *);
drhe09daa92006-06-10 13:29:31 +00001564 int (*xBegin)(sqlite3_vtab *pVTab);
1565 int (*xSync)(sqlite3_vtab *pVTab);
1566 int (*xCommit)(sqlite3_vtab *pVTab);
1567 int (*xRollback)(sqlite3_vtab *pVTab);
drhe09daa92006-06-10 13:29:31 +00001568};
drh9eff6162006-06-12 21:59:13 +00001569
1570/*
1571** The sqlite3_index_info structure and its substructures is used to
1572** pass information into and receive the reply from the xBestIndex
1573** method of an sqlite3_module. The fields under **Inputs** are the
1574** inputs to xBestIndex and are read-only. xBestIndex inserts its
1575** results into the **Outputs** fields.
1576**
1577** The aConstraint[] array records WHERE clause constraints of the
1578** form:
1579**
1580** column OP expr
1581**
1582** Where OP is =, <, <=, >, or >=. The particular operator is stored
1583** in aConstraint[].op. The index of the column is stored in
1584** aConstraint[].iColumn. aConstraint[].usable is TRUE if the
1585** expr on the right-hand side can be evaluated (and thus the constraint
1586** is usable) and false if it cannot.
1587**
1588** The optimizer automatically inverts terms of the form "expr OP column"
1589** and makes other simplificatinos to the WHERE clause in an attempt to
1590** get as many WHERE clause terms into the form shown above as possible.
1591** The aConstraint[] array only reports WHERE clause terms in the correct
1592** form that refer to the particular virtual table being queried.
1593**
1594** Information about the ORDER BY clause is stored in aOrderBy[].
1595** Each term of aOrderBy records a column of the ORDER BY clause.
1596**
1597** The xBestIndex method must fill aConstraintUsage[] with information
danielk19775fac9f82006-06-13 14:16:58 +00001598** about what parameters to pass to xFilter. If argvIndex>0 then
drh9eff6162006-06-12 21:59:13 +00001599** the right-hand side of the corresponding aConstraint[] is evaluated
1600** and becomes the argvIndex-th entry in argv. If aConstraintUsage[].omit
1601** is true, then the constraint is assumed to be fully handled by the
1602** virtual table and is not checked again by SQLite.
1603**
drh4be8b512006-06-13 23:51:34 +00001604** The idxNum and idxPtr values are recorded and passed into xFilter.
1605** sqlite3_free() is used to free idxPtr if needToFreeIdxPtr is true.
drh9eff6162006-06-12 21:59:13 +00001606**
1607** The orderByConsumed means that output from xFilter will occur in
1608** the correct order to satisfy the ORDER BY clause so that no separate
1609** sorting step is required.
1610**
1611** The estimatedCost value is an estimate of the cost of doing the
1612** particular lookup. A full scan of a table with N entries should have
1613** a cost of N. A binary search of a table of N entries should have a
1614** cost of approximately log(N).
1615*/
drhe09daa92006-06-10 13:29:31 +00001616struct sqlite3_index_info {
1617 /* Inputs */
drh9eff6162006-06-12 21:59:13 +00001618 const int nConstraint; /* Number of entries in aConstraint */
1619 const struct sqlite3_index_constraint {
1620 int iColumn; /* Column on left-hand side of constraint */
1621 unsigned char op; /* Constraint operator */
1622 unsigned char usable; /* True if this constraint is usable */
1623 int iTermOffset; /* Used internally - xBestIndex should ignore */
1624 } *const aConstraint; /* Table of WHERE clause constraints */
1625 const int nOrderBy; /* Number of terms in the ORDER BY clause */
1626 const struct sqlite3_index_orderby {
1627 int iColumn; /* Column number */
1628 unsigned char desc; /* True for DESC. False for ASC. */
1629 } *const aOrderBy; /* The ORDER BY clause */
drhe09daa92006-06-10 13:29:31 +00001630
1631 /* Outputs */
drh9eff6162006-06-12 21:59:13 +00001632 struct sqlite3_index_constraint_usage {
1633 int argvIndex; /* if >0, constraint is part of argv to xFilter */
1634 unsigned char omit; /* Do not code a test for this constraint */
1635 } *const aConstraintUsage;
drh4be8b512006-06-13 23:51:34 +00001636 int idxNum; /* Number used to identify the index */
1637 char *idxStr; /* String, possibly obtained from sqlite3_malloc */
1638 int needToFreeIdxStr; /* Free idxStr using sqlite3_free() if true */
drh9eff6162006-06-12 21:59:13 +00001639 int orderByConsumed; /* True if output is already ordered */
1640 double estimatedCost; /* Estimated cost of using this index */
drhe09daa92006-06-10 13:29:31 +00001641};
drh9eff6162006-06-12 21:59:13 +00001642#define SQLITE_INDEX_CONSTRAINT_EQ 2
1643#define SQLITE_INDEX_CONSTRAINT_GT 4
1644#define SQLITE_INDEX_CONSTRAINT_LE 8
1645#define SQLITE_INDEX_CONSTRAINT_LT 16
1646#define SQLITE_INDEX_CONSTRAINT_GE 32
1647#define SQLITE_INDEX_CONSTRAINT_MATCH 64
1648
1649/*
1650** This routine is used to register a new module name with an SQLite
1651** connection. Module names must be registered before creating new
1652** virtual tables on the module, or before using preexisting virtual
1653** tables of the module.
1654*/
drhb9bb7c12006-06-11 23:41:55 +00001655int sqlite3_create_module(
drh9eff6162006-06-12 21:59:13 +00001656 sqlite3 *db, /* SQLite connection to register module with */
1657 const char *zName, /* Name of the module */
danielk1977d1ab1ba2006-06-15 04:28:13 +00001658 const sqlite3_module *, /* Methods for the module */
1659 void * /* Client data for xCreate/xConnect */
drhb9bb7c12006-06-11 23:41:55 +00001660);
drhe09daa92006-06-10 13:29:31 +00001661
drh9eff6162006-06-12 21:59:13 +00001662/*
1663** Every module implementation uses a subclass of the following structure
1664** to describe a particular instance of the module. Each subclass will
1665** be taylored to the specific needs of the module implementation. The
1666** purpose of this superclass is to define certain fields that are common
1667** to all module implementations.
1668*/
1669struct sqlite3_vtab {
drha967e882006-06-13 01:04:52 +00001670 const sqlite3_module *pModule; /* The module for this virtual table */
danielk1977be718892006-06-23 08:05:19 +00001671 int nRef; /* Used internally */
drh9eff6162006-06-12 21:59:13 +00001672 /* Virtual table implementations will typically add additional fields */
1673};
1674
1675/* Every module implementation uses a subclass of the following structure
1676** to describe cursors that point into the virtual table and are used
1677** to loop through the virtual table. Cursors are created using the
1678** xOpen method of the module. Each module implementation will define
1679** the content of a cursor structure to suit its own needs.
1680**
1681** This superclass exists in order to define fields of the cursor that
1682** are common to all implementations.
1683*/
1684struct sqlite3_vtab_cursor {
1685 sqlite3_vtab *pVtab; /* Virtual table of this cursor */
1686 /* Virtual table implementations will typically add additional fields */
1687};
1688
1689/*
1690** The xCreate and xConnect methods of a module use the following API
1691** to declare the format (the names and datatypes of the columns) of
1692** the virtual tables they implement.
1693*/
danielk19777e6ebfb2006-06-12 11:24:37 +00001694int sqlite3_declare_vtab(sqlite3*, const char *zCreateTable);
drhe09daa92006-06-10 13:29:31 +00001695
1696/*
drh9eff6162006-06-12 21:59:13 +00001697** The interface to the virtual-table mechanism defined above (back up
1698** to a comment remarkably similar to this one) is currently considered
1699** to be experimental. The interface might change in incompatible ways.
1700** If this is a problem for you, do not use the interface at this time.
1701**
1702** When the virtual-table mechanism stablizes, we will declare the
1703** interface fixed, support it indefinitely, and remove this comment.
1704**
1705****** EXPERIMENTAL - subject to change without notice **************
1706*/
1707
1708/*
drhb37df7b2005-10-13 02:09:49 +00001709** Undo the hack that converts floating point types to integer for
1710** builds on processors without floating point support.
1711*/
1712#ifdef SQLITE_OMIT_FLOATING_POINT
1713# undef double
1714#endif
1715
drh382c0242001-10-06 16:33:02 +00001716#ifdef __cplusplus
1717} /* End of the 'extern "C"' block */
1718#endif
danielk19774adee202004-05-08 08:23:19 +00001719#endif