blob: 3e8b02266df5f1f7bfc77012f4f799146fa0d675 [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**
drh15b9a152006-01-31 20:49:13 +000015** @(#) $Id: sqlite.h.in,v 1.157 2006/01/31 20:49:13 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*/
81#if defined(_MSC_VER) || defined(__BORLANDC__)
82 typedef __int64 sqlite_int64;
drh1211de32004-07-26 12:24:22 +000083 typedef unsigned __int64 sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000084#else
85 typedef long long int sqlite_int64;
drh1211de32004-07-26 12:24:22 +000086 typedef unsigned long long int sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000087#endif
88
drhb37df7b2005-10-13 02:09:49 +000089/*
90** If compiling for a processor that lacks floating point support,
91** substitute integer for floating-point
92*/
93#ifdef SQLITE_OMIT_FLOATING_POINT
94# define double sqlite_int64
95#endif
drhefad9992004-06-22 12:13:55 +000096
97/*
drh75897232000-05-29 14:26:00 +000098** A function to close the database.
99**
100** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +0000101** returned from sqlite3_open() and the corresponding database will by closed.
danielk197796d81f92004-06-19 03:33:57 +0000102**
103** All SQL statements prepared using sqlite3_prepare() or
104** sqlite3_prepare16() must be deallocated using sqlite3_finalize() before
105** this routine is called. Otherwise, SQLITE_BUSY is returned and the
106** database connection remains open.
drh75897232000-05-29 14:26:00 +0000107*/
danielk1977f9d64d22004-06-19 08:18:07 +0000108int sqlite3_close(sqlite3 *);
drh75897232000-05-29 14:26:00 +0000109
110/*
111** The type for a callback function.
112*/
drh12057d52004-09-06 17:34:12 +0000113typedef int (*sqlite3_callback)(void*,int,char**, char**);
drh75897232000-05-29 14:26:00 +0000114
115/*
116** A function to executes one or more statements of SQL.
117**
118** If one or more of the SQL statements are queries, then
119** the callback function specified by the 3rd parameter is
120** invoked once for each row of the query result. This callback
121** should normally return 0. If the callback returns a non-zero
122** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +0000123** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +0000124**
125** The 4th parameter is an arbitrary pointer that is passed
126** to the callback function as its first parameter.
127**
128** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +0000129** columns in the query result. The 3rd parameter to the callback
130** is an array of strings holding the values for each column.
131** The 4th parameter to the callback is an array of strings holding
132** the names of each column.
drh75897232000-05-29 14:26:00 +0000133**
134** The callback function may be NULL, even for queries. A NULL
135** callback is not an error. It just means that no callback
136** will be invoked.
137**
138** If an error occurs while parsing or evaluating the SQL (but
139** not while executing the callback) then an appropriate error
140** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +0000141** *errmsg is made to point to that message. The calling function
142** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +0000143** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +0000144** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +0000145**
146** The return value is is SQLITE_OK if there are no errors and
147** some other return code if there is an error. The particular
148** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +0000149**
150** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000151** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +0000152** behavior can be modified somewhat using the sqlite3_busy_handler()
153** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000154*/
danielk19776f8a5032004-05-10 10:34:51 +0000155int sqlite3_exec(
drh12057d52004-09-06 17:34:12 +0000156 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000157 const char *sql, /* SQL to be executed */
drh12057d52004-09-06 17:34:12 +0000158 sqlite3_callback, /* Callback function */
drh75897232000-05-29 14:26:00 +0000159 void *, /* 1st argument to callback function */
160 char **errmsg /* Error msg written here */
161);
162
drh58b95762000-06-02 01:17:37 +0000163/*
danielk19776f8a5032004-05-10 10:34:51 +0000164** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000165*/
drh717e6402001-09-27 03:22:32 +0000166#define SQLITE_OK 0 /* Successful result */
drh15b9a152006-01-31 20:49:13 +0000167/* beginning-of-error-codes */
drh717e6402001-09-27 03:22:32 +0000168#define SQLITE_ERROR 1 /* SQL error or missing database */
drh2db0bbc2005-08-11 02:10:18 +0000169#define SQLITE_INTERNAL 2 /* NOT USED. Internal logic error in SQLite */
drh717e6402001-09-27 03:22:32 +0000170#define SQLITE_PERM 3 /* Access permission denied */
171#define SQLITE_ABORT 4 /* Callback routine requested an abort */
172#define SQLITE_BUSY 5 /* The database file is locked */
173#define SQLITE_LOCKED 6 /* A table in the database is locked */
174#define SQLITE_NOMEM 7 /* A malloc() failed */
175#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000176#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000177#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
178#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
drh2db0bbc2005-08-11 02:10:18 +0000179#define SQLITE_NOTFOUND 12 /* NOT USED. Table or record not found */
drh717e6402001-09-27 03:22:32 +0000180#define SQLITE_FULL 13 /* Insertion failed because database is full */
181#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
182#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000183#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000184#define SQLITE_SCHEMA 17 /* The database schema changed */
drh2db0bbc2005-08-11 02:10:18 +0000185#define SQLITE_TOOBIG 18 /* NOT USED. Too much data for one row */
drh717e6402001-09-27 03:22:32 +0000186#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000187#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000188#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000189#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000190#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000191#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000192#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000193#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000194#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
195#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh15b9a152006-01-31 20:49:13 +0000196/* end-of-error-codes */
drh717e6402001-09-27 03:22:32 +0000197
drhaf9ff332002-01-16 21:00:27 +0000198/*
199** Each entry in an SQLite table has a unique integer key. (The key is
200** the value of the INTEGER PRIMARY KEY column if there is such a column,
201** otherwise the key is generated at random. The unique key is always
202** available as the ROWID, OID, or _ROWID_ column.) The following routine
203** returns the integer key of the most recent insert in the database.
204**
205** This function is similar to the mysql_insert_id() function from MySQL.
206*/
drhefad9992004-06-22 12:13:55 +0000207sqlite_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000208
drhc8d30ac2002-04-12 10:08:59 +0000209/*
210** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000211** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000212**
213** All changes are counted, even if they were later undone by a
214** ROLLBACK or ABORT. Except, changes associated with creating and
215** dropping tables are not counted.
216**
danielk19776f8a5032004-05-10 10:34:51 +0000217** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000218** in the inner, recursive call are counted together with the changes
219** in the outer call.
220**
221** SQLite implements the command "DELETE FROM table" without a WHERE clause
222** by dropping and recreating the table. (This is much faster than going
223** through and deleting individual elements form the table.) Because of
224** this optimization, the change count for "DELETE FROM table" will be
225** zero regardless of the number of elements that were originally in the
226** table. To get an accurate count of the number of rows deleted, use
227** "DELETE FROM table WHERE 1" instead.
228*/
danielk1977f9d64d22004-06-19 08:18:07 +0000229int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000230
rdcf146a772004-02-25 22:51:06 +0000231/*
danielk1977b28af712004-06-21 06:50:26 +0000232** This function returns the number of database rows that have been
233** modified by INSERT, UPDATE or DELETE statements since the database handle
234** was opened. This includes UPDATE, INSERT and DELETE statements executed
235** as part of trigger programs. All changes are counted as soon as the
236** statement that makes them is completed (when the statement handle is
237** passed to sqlite3_reset() or sqlite_finalise()).
rdcf146a772004-02-25 22:51:06 +0000238**
239** SQLite implements the command "DELETE FROM table" without a WHERE clause
240** by dropping and recreating the table. (This is much faster than going
241** through and deleting individual elements form the table.) Because of
242** this optimization, the change count for "DELETE FROM table" will be
243** zero regardless of the number of elements that were originally in the
244** table. To get an accurate count of the number of rows deleted, use
245** "DELETE FROM table WHERE 1" instead.
rdcf146a772004-02-25 22:51:06 +0000246*/
danielk1977b28af712004-06-21 06:50:26 +0000247int sqlite3_total_changes(sqlite3*);
248
drh4c504392000-10-16 22:06:40 +0000249/* This function causes any pending database operation to abort and
250** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000251** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000252** or Ctrl-C where the user wants a long query operation to halt
253** immediately.
254*/
danielk1977f9d64d22004-06-19 08:18:07 +0000255void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000256
drheec553b2000-06-02 01:51:20 +0000257
danielk197761de0d12004-05-27 23:56:16 +0000258/* These functions return true if the given input string comprises
259** one or more complete SQL statements. For the sqlite3_complete() call,
260** the parameter must be a nul-terminated UTF-8 string. For
261** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
262** is required.
drh75897232000-05-29 14:26:00 +0000263**
264** The algorithm is simple. If the last token other than spaces
265** and comments is a semicolon, then return true. otherwise return
266** false.
267*/
danielk19776f8a5032004-05-10 10:34:51 +0000268int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000269int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000270
drh2dfbbca2000-07-28 14:32:48 +0000271/*
272** This routine identifies a callback function that is invoked
273** whenever an attempt is made to open a database table that is
274** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000275** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000276** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000277** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000278** second argument is the name of the locked table and the third
279** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000280** busy callback returns 0, then sqlite3_exec() immediately returns
281** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000282** tries to open the table again and the cycle repeats.
283**
284** The default busy callback is NULL.
285**
286** Sqlite is re-entrant, so the busy handler may start a new query.
287** (It is not clear why anyone would every want to do this, but it
288** is allowed, in theory.) But the busy handler may not close the
289** database. Closing the database from a busy handler will delete
290** data structures out from under the executing query and will
291** probably result in a coredump.
292*/
danielk1977f9d64d22004-06-19 08:18:07 +0000293int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000294
295/*
296** This routine sets a busy handler that sleeps for a while when a
297** table is locked. The handler will sleep multiple times until
298** at least "ms" milleseconds of sleeping have been done. After
299** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000300** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000301**
302** Calling this routine with an argument less than or equal to zero
303** turns off all busy handlers.
304*/
danielk1977f9d64d22004-06-19 08:18:07 +0000305int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000306
drhe3710332000-09-29 13:30:53 +0000307/*
danielk19776f8a5032004-05-10 10:34:51 +0000308** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000309** Instead of invoking a user-supplied callback for each row of the
310** result, this routine remembers each row of the result in memory
311** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000312** query has finished.
313**
314** As an example, suppose the query result where this table:
315**
316** Name | Age
317** -----------------------
318** Alice | 43
319** Bob | 28
320** Cindy | 21
321**
322** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000323** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000324**
325** azResult[0] = "Name";
326** azResult[1] = "Age";
327** azResult[2] = "Alice";
328** azResult[3] = "43";
329** azResult[4] = "Bob";
330** azResult[5] = "28";
331** azResult[6] = "Cindy";
332** azResult[7] = "21";
333**
334** Notice that there is an extra row of data containing the column
335** headers. But the *nrow return value is still 3. *ncolumn is
336** set to 2. In general, the number of values inserted into azResult
337** will be ((*nrow) + 1)*(*ncolumn).
338**
339** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000340** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000341** release the memory that was malloc-ed. Because of the way the
342** malloc() happens, the calling function must not try to call
danielk197799b214d2005-02-02 01:13:38 +0000343** free() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000344** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000345**
danielk19776f8a5032004-05-10 10:34:51 +0000346** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000347*/
danielk19776f8a5032004-05-10 10:34:51 +0000348int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000349 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000350 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000351 char ***resultp, /* Result written to a char *[] that this points to */
352 int *nrow, /* Number of result rows written here */
353 int *ncolumn, /* Number of result columns written here */
354 char **errmsg /* Error msg written here */
355);
356
357/*
danielk19776f8a5032004-05-10 10:34:51 +0000358** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000359*/
danielk19776f8a5032004-05-10 10:34:51 +0000360void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000361
drha18c5682000-10-08 22:20:57 +0000362/*
drh4f26d6c2004-05-26 23:25:30 +0000363** The following routines are variants of the "sprintf()" from the
364** standard C library. The resulting string is written into memory
365** obtained from malloc() so that there is never a possiblity of buffer
366** overflow. These routines also implement some additional formatting
367** options that are useful for constructing SQL statements.
368**
369** The strings returned by these routines should be freed by calling
370** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000371**
372** All of the usual printf formatting options apply. In addition, there
373** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000374** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000375** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000376** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000377** the string.
378**
379** For example, so some string variable contains text as follows:
380**
381** char *zText = "It's a happy day!";
382**
383** We can use this text in an SQL statement as follows:
384**
drh3224b322005-09-08 10:58:51 +0000385** char *z = sqlite3_mprintf("INSERT INTO TABLES('%q')", zText);
386** sqlite3_exec(db, z, callback1, 0, 0);
387** sqlite3_free(z);
drha18c5682000-10-08 22:20:57 +0000388**
389** Because the %q format string is used, the '\'' character in zText
390** is escaped and the SQL generated is as follows:
391**
392** INSERT INTO table1 VALUES('It''s a happy day!')
393**
394** This is correct. Had we used %s instead of %q, the generated SQL
395** would have looked like this:
396**
397** INSERT INTO table1 VALUES('It's a happy day!');
398**
399** This second example is an SQL syntax error. As a general rule you
400** should always use %q instead of %s when inserting text into a string
401** literal.
402*/
danielk19776f8a5032004-05-10 10:34:51 +0000403char *sqlite3_mprintf(const char*,...);
404char *sqlite3_vmprintf(const char*, va_list);
drh4f26d6c2004-05-26 23:25:30 +0000405void sqlite3_free(char *z);
drhfeac5f82004-08-01 00:10:45 +0000406char *sqlite3_snprintf(int,char*,const char*, ...);
drh5191b7e2002-03-08 02:12:00 +0000407
drh1211de32004-07-26 12:24:22 +0000408#ifndef SQLITE_OMIT_AUTHORIZATION
drh5191b7e2002-03-08 02:12:00 +0000409/*
drhed6c8672003-01-12 18:02:16 +0000410** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000411** callback is invoked (at compile-time, not at run-time) for each
412** attempt to access a column of a table in the database. The callback
413** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
414** SQL statement should be aborted with an error and SQLITE_IGNORE
415** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000416*/
danielk19776f8a5032004-05-10 10:34:51 +0000417int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000418 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000419 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000420 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000421);
drh1211de32004-07-26 12:24:22 +0000422#endif
drhed6c8672003-01-12 18:02:16 +0000423
424/*
425** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000426** be one of the values below. These values signify what kind of operation
427** is to be authorized. The 3rd and 4th parameters to the authorization
428** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000429** codes is used as the second parameter. The 5th parameter is the name
430** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000431** is the name of the inner-most trigger or view that is responsible for
432** the access attempt or NULL if this access attempt is directly from
433** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000434**
435** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000436*/
drh77ad4e42003-01-14 02:49:27 +0000437#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000438#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
439#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
440#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
441#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000442#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000443#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000444#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000445#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
446#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000447#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000448#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000449#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000450#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000451#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000452#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000453#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000454#define SQLITE_DROP_VIEW 17 /* View Name NULL */
455#define SQLITE_INSERT 18 /* Table Name NULL */
456#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
457#define SQLITE_READ 20 /* Table Name Column Name */
458#define SQLITE_SELECT 21 /* NULL NULL */
459#define SQLITE_TRANSACTION 22 /* NULL NULL */
460#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000461#define SQLITE_ATTACH 24 /* Filename NULL */
462#define SQLITE_DETACH 25 /* Database Name NULL */
danielk19771c8c23c2004-11-12 15:53:37 +0000463#define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */
danielk19771d54df82004-11-23 15:41:16 +0000464#define SQLITE_REINDEX 27 /* Index Name NULL */
drhe6e04962005-07-23 02:17:03 +0000465#define SQLITE_ANALYZE 28 /* Table Name NULL */
drh81e293b2003-06-06 19:00:42 +0000466
drhed6c8672003-01-12 18:02:16 +0000467
468/*
469** The return value of the authorization function should be one of the
470** following constants:
471*/
472/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
473#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
474#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
475
476/*
drh19e2d372005-08-29 23:00:03 +0000477** Register a function for tracing SQL command evaluation. The function
478** registered by sqlite3_trace() is invoked at the first sqlite3_step()
479** for the evaluation of an SQL statement. The function registered by
480** sqlite3_profile() runs at the end of each SQL statement and includes
481** information on how long that statement ran.
482**
483** The sqlite3_profile() API is currently considered experimental and
484** is subject to change.
drh18de4822003-01-16 16:28:53 +0000485*/
danielk1977f9d64d22004-06-19 08:18:07 +0000486void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh19e2d372005-08-29 23:00:03 +0000487void *sqlite3_profile(sqlite3*,
488 void(*xProfile)(void*,const char*,sqlite_uint64), void*);
drh18de4822003-01-16 16:28:53 +0000489
danielk1977348bb5d2003-10-18 09:37:26 +0000490/*
491** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000492** is invoked periodically during long running calls to sqlite3_exec(),
danielk19772097e942004-11-20 06:05:56 +0000493** sqlite3_step() and sqlite3_get_table(). An example use for this API is to
494** keep a GUI updated during a large query.
danielk1977348bb5d2003-10-18 09:37:26 +0000495**
496** The progress callback is invoked once for every N virtual machine opcodes,
497** where N is the second argument to this function. The progress callback
498** itself is identified by the third argument to this function. The fourth
499** argument to this function is a void pointer passed to the progress callback
500** function each time it is invoked.
501**
danielk19776f8a5032004-05-10 10:34:51 +0000502** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000503** in less than N opcodes being executed, then the progress callback is not
504** invoked.
505**
danielk1977348bb5d2003-10-18 09:37:26 +0000506** To remove the progress callback altogether, pass NULL as the third
507** argument to this function.
508**
509** If the progress callback returns a result other than 0, then the current
510** query is immediately terminated and any database changes rolled back. If the
511** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000512** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000513**
514******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000515*/
danielk1977f9d64d22004-06-19 08:18:07 +0000516void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000517
drhaa940ea2004-01-15 02:44:03 +0000518/*
519** Register a callback function to be invoked whenever a new transaction
520** is committed. The pArg argument is passed through to the callback.
521** callback. If the callback function returns non-zero, then the commit
522** is converted into a rollback.
523**
524** If another function was previously registered, its pArg value is returned.
525** Otherwise NULL is returned.
526**
527** Registering a NULL function disables the callback.
528**
529******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
530*/
danielk1977f9d64d22004-06-19 08:18:07 +0000531void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000532
drh22fbcb82004-02-01 01:22:50 +0000533/*
drh4f26d6c2004-05-26 23:25:30 +0000534** Open the sqlite database file "filename". The "filename" is UTF-8
535** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
536** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
537** if an error occurs. If the database is opened (or created) successfully,
538** then SQLITE_OK is returned. Otherwise an error code is returned. The
539** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
540** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000541**
drh4f26d6c2004-05-26 23:25:30 +0000542** If the database file does not exist, then a new database is created.
543** The encoding for the database is UTF-8 if sqlite3_open() is called and
544** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000545**
546** Whether or not an error occurs when it is opened, resources associated
547** with the sqlite3* handle should be released by passing it to
548** sqlite3_close() when it is no longer required.
549*/
550int sqlite3_open(
551 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000552 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000553);
danielk197765904932004-05-26 06:18:37 +0000554int sqlite3_open16(
555 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000556 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000557);
danielk1977295ba552004-05-19 10:34:51 +0000558
danielk197765904932004-05-26 06:18:37 +0000559/*
560** Return the error code for the most recent sqlite3_* API call associated
561** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
562** API call was successful.
563**
564** Calls to many sqlite3_* functions set the error code and string returned
565** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
566** (overwriting the previous values). Note that calls to sqlite3_errcode(),
567** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
568** results of future invocations.
569**
570** Assuming no other intervening sqlite3_* API calls are made, the error
571** code returned by this function is associated with the same error as
572** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
573*/
574int sqlite3_errcode(sqlite3 *db);
575
576/*
577** Return a pointer to a UTF-8 encoded string describing in english the
578** error condition for the most recent sqlite3_* API call. The returned
579** string is always terminated by an 0x00 byte.
580**
581** The string "not an error" is returned when the most recent API call was
582** successful.
583*/
584const char *sqlite3_errmsg(sqlite3*);
585
586/*
587** Return a pointer to a UTF-16 native byte order encoded string describing
588** in english the error condition for the most recent sqlite3_* API call.
589** The returned string is always terminated by a pair of 0x00 bytes.
590**
591** The string "not an error" is returned when the most recent API call was
592** successful.
593*/
594const void *sqlite3_errmsg16(sqlite3*);
595
596/*
597** An instance of the following opaque structure is used to represent
598** a compiled SQL statment.
599*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000600typedef struct sqlite3_stmt sqlite3_stmt;
601
danielk1977e3209e42004-05-20 01:40:18 +0000602/*
danielk197765904932004-05-26 06:18:37 +0000603** To execute an SQL query, it must first be compiled into a byte-code
604** program using one of the following routines. The only difference between
605** them is that the second argument, specifying the SQL statement to
606** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
607** function and UTF-16 for sqlite3_prepare16().
608**
609** The first parameter "db" is an SQLite database handle. The second
610** parameter "zSql" is the statement to be compiled, encoded as either
611** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
612** than zero, then zSql is read up to the first nul terminator. If
613** "nBytes" is not less than zero, then it is the length of the string zSql
614** in bytes (not characters).
615**
616** *pzTail is made to point to the first byte past the end of the first
617** SQL statement in zSql. This routine only compiles the first statement
618** in zSql, so *pzTail is left pointing to what remains uncompiled.
619**
620** *ppStmt is left pointing to a compiled SQL statement that can be
621** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
622** set to NULL. If the input text contained no SQL (if the input is and
623** empty string or a comment) then *ppStmt is set to NULL.
624**
625** On success, SQLITE_OK is returned. Otherwise an error code is returned.
626*/
627int sqlite3_prepare(
628 sqlite3 *db, /* Database handle */
629 const char *zSql, /* SQL statement, UTF-8 encoded */
630 int nBytes, /* Length of zSql in bytes. */
631 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
632 const char **pzTail /* OUT: Pointer to unused portion of zSql */
633);
634int sqlite3_prepare16(
635 sqlite3 *db, /* Database handle */
636 const void *zSql, /* SQL statement, UTF-16 encoded */
637 int nBytes, /* Length of zSql in bytes. */
638 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
639 const void **pzTail /* OUT: Pointer to unused portion of zSql */
640);
641
642/*
drhf4479502004-05-27 03:12:53 +0000643** Pointers to the following two opaque structures are used to communicate
644** with the implementations of user-defined functions.
645*/
646typedef struct sqlite3_context sqlite3_context;
647typedef struct Mem sqlite3_value;
648
649/*
drh4f26d6c2004-05-26 23:25:30 +0000650** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
drh32c0d4f2004-12-07 02:14:51 +0000651** one or more literals can be replace by parameters "?" or ":AAA" or
652** "$VVV" where AAA is an identifer and VVV is a variable name according
653** to the syntax rules of the TCL programming language.
654** The value of these parameters (also called "host parameter names") can
655** be set using the routines listed below.
drh4f26d6c2004-05-26 23:25:30 +0000656**
657** In every case, the first parameter is a pointer to the sqlite3_stmt
658** structure returned from sqlite3_prepare(). The second parameter is the
drh32c0d4f2004-12-07 02:14:51 +0000659** index of the parameter. The first parameter as an index of 1. For
660** named parameters (":AAA" or "$VVV") you can use
661** sqlite3_bind_parameter_index() to get the correct index value given
662** the parameters name. If the same named parameter occurs more than
663** once, it is assigned the same index each time.
drh4f26d6c2004-05-26 23:25:30 +0000664**
drh900dfba2004-07-21 15:21:36 +0000665** The fifth parameter to sqlite3_bind_blob(), sqlite3_bind_text(), and
666** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or
667** text after SQLite has finished with it. If the fifth argument is the
668** special value SQLITE_STATIC, then the library assumes that the information
669** is in static, unmanaged space and does not need to be freed. If the
670** fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its
671** own private copy of the data.
drh4f26d6c2004-05-26 23:25:30 +0000672**
673** The sqlite3_bind_* routine must be called before sqlite3_step() after
drh32c0d4f2004-12-07 02:14:51 +0000674** an sqlite3_prepare() or sqlite3_reset(). Unbound parameterss are
675** interpreted as NULL.
drh4f26d6c2004-05-26 23:25:30 +0000676*/
danielk1977d8123362004-06-12 09:25:12 +0000677int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000678int sqlite3_bind_double(sqlite3_stmt*, int, double);
679int sqlite3_bind_int(sqlite3_stmt*, int, int);
drhefad9992004-06-22 12:13:55 +0000680int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64);
drhf4479502004-05-27 03:12:53 +0000681int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000682int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
683int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000684int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000685
686/*
drh32c0d4f2004-12-07 02:14:51 +0000687** Return the number of parameters in a compiled SQL statement. This
drh75f6a032004-07-15 14:15:00 +0000688** routine was added to support DBD::SQLite.
drh75f6a032004-07-15 14:15:00 +0000689*/
690int sqlite3_bind_parameter_count(sqlite3_stmt*);
691
692/*
drh32c0d4f2004-12-07 02:14:51 +0000693** Return the name of the i-th parameter. Ordinary parameters "?" are
694** nameless and a NULL is returned. For parameters of the form :AAA or
695** $VVV the complete text of the parameter name is returned, including
696** the initial ":" or "$". NULL is returned if the index is out of range.
drh895d7472004-08-20 16:02:39 +0000697*/
698const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
699
700/*
drhfa6bc002004-09-07 16:19:52 +0000701** Return the index of a parameter with the given name. The name
702** must match exactly. If no parameter with the given name is found,
703** return 0.
704*/
705int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
706
707/*
danielk1977600dd0b2005-01-20 01:14:23 +0000708** Set all the parameters in the compiled SQL statement to NULL.
danielk1977600dd0b2005-01-20 01:14:23 +0000709*/
710int sqlite3_clear_bindings(sqlite3_stmt*);
711
712/*
danielk197765904932004-05-26 06:18:37 +0000713** Return the number of columns in the result set returned by the compiled
714** SQL statement. This routine returns 0 if pStmt is an SQL statement
715** that does not return data (for example an UPDATE).
716*/
717int sqlite3_column_count(sqlite3_stmt *pStmt);
718
719/*
720** The first parameter is a compiled SQL statement. This function returns
721** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000722** second function parameter. The string returned is UTF-8 for
723** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000724*/
725const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000726const void *sqlite3_column_name16(sqlite3_stmt*,int);
727
728/*
729** The first parameter is a compiled SQL statement. If this statement
730** is a SELECT statement, the Nth column of the returned result set
731** of the SELECT is a table column then the declared type of the table
732** column is returned. If the Nth column of the result set is not at table
733** column, then a NULL pointer is returned. The returned string is always
734** UTF-8 encoded. For example, in the database schema:
735**
736** CREATE TABLE t1(c1 VARIANT);
737**
738** And the following statement compiled:
739**
740** SELECT c1 + 1, 0 FROM t1;
741**
742** Then this routine would return the string "VARIANT" for the second
743** result column (i==1), and a NULL pointer for the first result column
744** (i==0).
745*/
746const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
747
748/*
749** The first parameter is a compiled SQL statement. If this statement
750** is a SELECT statement, the Nth column of the returned result set
751** of the SELECT is a table column then the declared type of the table
752** column is returned. If the Nth column of the result set is not at table
753** column, then a NULL pointer is returned. The returned string is always
754** UTF-16 encoded. For example, in the database schema:
755**
drh4f26d6c2004-05-26 23:25:30 +0000756** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000757**
758** And the following statement compiled:
759**
760** SELECT c1 + 1, 0 FROM t1;
761**
drh4f26d6c2004-05-26 23:25:30 +0000762** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000763** result column (i==1), and a NULL pointer for the first result column
764** (i==0).
765*/
766const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
767
danielk1977106bb232004-05-21 10:08:53 +0000768/*
769** After an SQL query has been compiled with a call to either
770** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
771** called one or more times to execute the statement.
772**
773** The return value will be either SQLITE_BUSY, SQLITE_DONE,
774** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
775**
776** SQLITE_BUSY means that the database engine attempted to open
777** a locked database and there is no busy callback registered.
778** Call sqlite3_step() again to retry the open.
779**
780** SQLITE_DONE means that the statement has finished executing
781** successfully. sqlite3_step() should not be called again on this virtual
782** machine.
783**
784** If the SQL statement being executed returns any data, then
785** SQLITE_ROW is returned each time a new row of data is ready
786** for processing by the caller. The values may be accessed using
787** the sqlite3_column_*() functions described below. sqlite3_step()
788** is called again to retrieve the next row of data.
789**
790** SQLITE_ERROR means that a run-time error (such as a constraint
791** violation) has occurred. sqlite3_step() should not be called again on
792** the VM. More information may be found by calling sqlite3_errmsg().
793**
794** SQLITE_MISUSE means that the this routine was called inappropriately.
795** Perhaps it was called on a virtual machine that had already been
796** finalized or on one that had previously returned SQLITE_ERROR or
797** SQLITE_DONE. Or it could be the case the the same database connection
798** is being used simulataneously by two or more threads.
799*/
danielk197717240fd2004-05-26 00:07:25 +0000800int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000801
danielk1977106bb232004-05-21 10:08:53 +0000802/*
803** Return the number of values in the current row of the result set.
804**
805** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
806** will return the same value as the sqlite3_column_count() function.
807** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
808** error code, or before sqlite3_step() has been called on a
809** compiled SQL statement, this routine returns zero.
810*/
danielk197793d46752004-05-23 13:30:58 +0000811int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000812
drh4f26d6c2004-05-26 23:25:30 +0000813/*
814** Values are stored in the database in one of the following fundamental
815** types.
816*/
drh9c054832004-05-31 18:51:57 +0000817#define SQLITE_INTEGER 1
818#define SQLITE_FLOAT 2
drh1e284f42004-10-06 15:52:01 +0000819/* #define SQLITE_TEXT 3 // See below */
drh9c054832004-05-31 18:51:57 +0000820#define SQLITE_BLOB 4
821#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000822
danielk1977106bb232004-05-21 10:08:53 +0000823/*
drh1e284f42004-10-06 15:52:01 +0000824** SQLite version 2 defines SQLITE_TEXT differently. To allow both
825** version 2 and version 3 to be included, undefine them both if a
826** conflict is seen. Define SQLITE3_TEXT to be the version 3 value.
827*/
828#ifdef SQLITE_TEXT
829# undef SQLITE_TEXT
830#else
831# define SQLITE_TEXT 3
832#endif
833#define SQLITE3_TEXT 3
834
835/*
drh4f26d6c2004-05-26 23:25:30 +0000836** The next group of routines returns information about the information
837** in a single column of the current result row of a query. In every
838** case the first parameter is a pointer to the SQL statement that is being
839** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
840** the second argument is the index of the column for which information
841** should be returned. iCol is zero-indexed. The left-most column as an
842** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000843**
drh4f26d6c2004-05-26 23:25:30 +0000844** If the SQL statement is not currently point to a valid row, or if the
845** the colulmn index is out of range, the result is undefined.
846**
847** These routines attempt to convert the value where appropriate. For
848** example, if the internal representation is FLOAT and a text result
849** is requested, sprintf() is used internally to do the conversion
850** automatically. The following table details the conversions that
851** are applied:
852**
853** Internal Type Requested Type Conversion
854** ------------- -------------- --------------------------
855** NULL INTEGER Result is 0
856** NULL FLOAT Result is 0.0
857** NULL TEXT Result is an empty string
858** NULL BLOB Result is a zero-length BLOB
859** INTEGER FLOAT Convert from integer to float
860** INTEGER TEXT ASCII rendering of the integer
861** INTEGER BLOB Same as for INTEGER->TEXT
862** FLOAT INTEGER Convert from float to integer
863** FLOAT TEXT ASCII rendering of the float
864** FLOAT BLOB Same as FLOAT->TEXT
865** TEXT INTEGER Use atoi()
866** TEXT FLOAT Use atof()
867** TEXT BLOB No change
868** BLOB INTEGER Convert to TEXT then use atoi()
869** BLOB FLOAT Convert to TEXT then use atof()
870** BLOB TEXT Add a \000 terminator if needed
871**
872** The following access routines are provided:
873**
874** _type() Return the datatype of the result. This is one of
875** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
876** or SQLITE_NULL.
877** _blob() Return the value of a BLOB.
878** _bytes() Return the number of bytes in a BLOB value or the number
879** of bytes in a TEXT value represented as UTF-8. The \000
880** terminator is included in the byte count for TEXT values.
881** _bytes16() Return the number of bytes in a BLOB value or the number
882** of bytes in a TEXT value represented as UTF-16. The \u0000
883** terminator is included in the byte count for TEXT values.
884** _double() Return a FLOAT value.
885** _int() Return an INTEGER value in the host computer's native
886** integer representation. This might be either a 32- or 64-bit
887** integer depending on the host.
888** _int64() Return an INTEGER value as a 64-bit signed integer.
889** _text() Return the value as UTF-8 text.
890** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000891*/
drhf4479502004-05-27 03:12:53 +0000892const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
893int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
894int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
895double sqlite3_column_double(sqlite3_stmt*, int iCol);
896int sqlite3_column_int(sqlite3_stmt*, int iCol);
drhefad9992004-06-22 12:13:55 +0000897sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +0000898const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
899const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000900int sqlite3_column_type(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000901
danielk197765904932004-05-26 06:18:37 +0000902/*
903** The sqlite3_finalize() function is called to delete a compiled
904** SQL statement obtained by a previous call to sqlite3_prepare()
905** or sqlite3_prepare16(). If the statement was executed successfully, or
906** not executed at all, then SQLITE_OK is returned. If execution of the
907** statement failed then an error code is returned.
908**
909** This routine can be called at any point during the execution of the
910** virtual machine. If the virtual machine has not completed execution
911** when this routine is called, that is like encountering an error or
912** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
913** rolled back and transactions cancelled, depending on the circumstances,
914** and the result code returned will be SQLITE_ABORT.
915*/
916int sqlite3_finalize(sqlite3_stmt *pStmt);
917
918/*
919** The sqlite3_reset() function is called to reset a compiled SQL
920** statement obtained by a previous call to sqlite3_prepare() or
921** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
922** Any SQL statement variables that had values bound to them using
923** the sqlite3_bind_*() API retain their values.
924*/
925int sqlite3_reset(sqlite3_stmt *pStmt);
926
927/*
danielk197765904932004-05-26 06:18:37 +0000928** The following two functions are used to add user functions or aggregates
929** implemented in C to the SQL langauge interpreted by SQLite. The
930** difference only between the two is that the second parameter, the
931** name of the (scalar) function or aggregate, is encoded in UTF-8 for
932** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
933**
934** The first argument is the database handle that the new function or
935** aggregate is to be added to. If a single program uses more than one
936** database handle internally, then user functions or aggregates must
937** be added individually to each database handle with which they will be
938** used.
939**
940** The third parameter is the number of arguments that the function or
941** aggregate takes. If this parameter is negative, then the function or
942** aggregate may take any number of arguments.
943**
danielk1977d8123362004-06-12 09:25:12 +0000944** The fourth parameter is one of SQLITE_UTF* values defined below,
945** indicating the encoding that the function is most likely to handle
946** values in. This does not change the behaviour of the programming
947** interface. However, if two versions of the same function are registered
948** with different encoding values, SQLite invokes the version likely to
949** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +0000950**
danielk197765904932004-05-26 06:18:37 +0000951** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
952** pointers to user implemented C functions that implement the user
953** function or aggregate. A scalar function requires an implementation of
954** the xFunc callback only, NULL pointers should be passed as the xStep
955** and xFinal parameters. An aggregate function requires an implementation
956** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
957** existing user function or aggregate, pass NULL for all three function
958** callback. Specifying an inconstent set of callback values, such as an
959** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
960** returned.
961*/
962int sqlite3_create_function(
963 sqlite3 *,
964 const char *zFunctionName,
965 int nArg,
966 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000967 void*,
968 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
969 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
970 void (*xFinal)(sqlite3_context*)
971);
972int sqlite3_create_function16(
973 sqlite3*,
974 const void *zFunctionName,
975 int nArg,
976 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000977 void*,
978 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
979 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
980 void (*xFinal)(sqlite3_context*)
981);
982
983/*
danielk197765904932004-05-26 06:18:37 +0000984** The next routine returns the number of calls to xStep for a particular
985** aggregate function instance. The current call to xStep counts so this
986** routine always returns at least 1.
987*/
988int sqlite3_aggregate_count(sqlite3_context*);
989
danielk19770ffba6b2004-05-24 09:10:10 +0000990/*
drh4f26d6c2004-05-26 23:25:30 +0000991** The next group of routines returns information about parameters to
992** a user-defined function. Function implementations use these routines
993** to access their parameters. These routines are the same as the
994** sqlite3_column_* routines except that these routines take a single
995** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
996** column number.
danielk19770ffba6b2004-05-24 09:10:10 +0000997*/
drhf4479502004-05-27 03:12:53 +0000998const void *sqlite3_value_blob(sqlite3_value*);
999int sqlite3_value_bytes(sqlite3_value*);
1000int sqlite3_value_bytes16(sqlite3_value*);
1001double sqlite3_value_double(sqlite3_value*);
1002int sqlite3_value_int(sqlite3_value*);
drhefad9992004-06-22 12:13:55 +00001003sqlite_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +00001004const unsigned char *sqlite3_value_text(sqlite3_value*);
1005const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +00001006const void *sqlite3_value_text16le(sqlite3_value*);
1007const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +00001008int sqlite3_value_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +00001009
1010/*
danielk19770ae8b832004-05-25 12:05:56 +00001011** Aggregate functions use the following routine to allocate
1012** a structure for storing their state. The first time this routine
1013** is called for a particular aggregate, a new structure of size nBytes
1014** is allocated, zeroed, and returned. On subsequent calls (for the
1015** same aggregate instance) the same buffer is returned. The implementation
1016** of the aggregate can use the returned buffer to accumulate data.
1017**
1018** The buffer allocated is freed automatically by SQLite.
1019*/
drh4f26d6c2004-05-26 23:25:30 +00001020void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +00001021
1022/*
drhc0f2a012005-07-09 02:39:40 +00001023** The pUserData parameter to the sqlite3_create_function()
1024** routine used to register user functions is available to
1025** the implementation of the function using this call.
danielk19777e18c252004-05-25 11:47:24 +00001026*/
1027void *sqlite3_user_data(sqlite3_context*);
1028
1029/*
danielk1977682f68b2004-06-05 10:22:17 +00001030** The following two functions may be used by scalar user functions to
1031** associate meta-data with argument values. If the same value is passed to
1032** multiple invocations of the user-function during query execution, under
1033** some circumstances the associated meta-data may be preserved. This may
1034** be used, for example, to add a regular-expression matching scalar
1035** function. The compiled version of the regular expression is stored as
1036** meta-data associated with the SQL value passed as the regular expression
1037** pattern.
1038**
1039** Calling sqlite3_get_auxdata() returns a pointer to the meta data
1040** associated with the Nth argument value to the current user function
1041** call, where N is the second parameter. If no meta-data has been set for
1042** that value, then a NULL pointer is returned.
1043**
1044** The sqlite3_set_auxdata() is used to associate meta data with a user
1045** function argument. The third parameter is a pointer to the meta data
1046** to be associated with the Nth user function argument value. The fourth
1047** parameter specifies a 'delete function' that will be called on the meta
1048** data pointer to release it when it is no longer required. If the delete
1049** function pointer is NULL, it is not invoked.
1050**
1051** In practice, meta-data is preserved between function calls for
1052** expressions that are constant at compile time. This includes literal
1053** values and SQL variables.
1054*/
1055void *sqlite3_get_auxdata(sqlite3_context*, int);
1056void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
1057
drha2854222004-06-17 19:04:17 +00001058
1059/*
1060** These are special value for the destructor that is passed in as the
1061** final argument to routines like sqlite3_result_blob(). If the destructor
1062** argument is SQLITE_STATIC, it means that the content pointer is constant
1063** and will never change. It does not need to be destroyed. The
1064** SQLITE_TRANSIENT value means that the content will likely change in
1065** the near future and that SQLite should make its own private copy of
1066** the content before returning.
1067*/
danielk1977d8123362004-06-12 09:25:12 +00001068#define SQLITE_STATIC ((void(*)(void *))0)
1069#define SQLITE_TRANSIENT ((void(*)(void *))-1)
1070
danielk1977682f68b2004-06-05 10:22:17 +00001071/*
drh4f26d6c2004-05-26 23:25:30 +00001072** User-defined functions invoke the following routines in order to
1073** set their return value.
danielk19777e18c252004-05-25 11:47:24 +00001074*/
danielk1977d8123362004-06-12 09:25:12 +00001075void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001076void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +00001077void sqlite3_result_error(sqlite3_context*, const char*, int);
1078void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +00001079void sqlite3_result_int(sqlite3_context*, int);
drhefad9992004-06-22 12:13:55 +00001080void sqlite3_result_int64(sqlite3_context*, sqlite_int64);
drh4f26d6c2004-05-26 23:25:30 +00001081void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +00001082void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
1083void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
1084void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
1085void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001086void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +00001087
drh52619df2004-06-11 17:48:02 +00001088/*
1089** These are the allowed values for the eTextRep argument to
1090** sqlite3_create_collation and sqlite3_create_function.
1091*/
danielk1977466be562004-06-10 02:16:01 +00001092#define SQLITE_UTF8 1
danielk1977dc8453f2004-06-12 00:42:34 +00001093#define SQLITE_UTF16LE 2
1094#define SQLITE_UTF16BE 3
1095#define SQLITE_UTF16 4 /* Use native byte order */
drh52619df2004-06-11 17:48:02 +00001096#define SQLITE_ANY 5 /* sqlite3_create_function only */
danielk1977466be562004-06-10 02:16:01 +00001097
danielk19777cedc8d2004-06-10 10:50:08 +00001098/*
1099** These two functions are used to add new collation sequences to the
1100** sqlite3 handle specified as the first argument.
1101**
1102** The name of the new collation sequence is specified as a UTF-8 string
1103** for sqlite3_create_collation() and a UTF-16 string for
1104** sqlite3_create_collation16(). In both cases the name is passed as the
1105** second function argument.
1106**
1107** The third argument must be one of the constants SQLITE_UTF8,
1108** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1109** routine expects to be passed pointers to strings encoded using UTF-8,
1110** UTF-16 little-endian or UTF-16 big-endian respectively.
1111**
1112** A pointer to the user supplied routine must be passed as the fifth
1113** argument. If it is NULL, this is the same as deleting the collation
1114** sequence (so that SQLite cannot call it anymore). Each time the user
1115** supplied function is invoked, it is passed a copy of the void* passed as
1116** the fourth argument to sqlite3_create_collation() or
1117** sqlite3_create_collation16() as its first parameter.
1118**
1119** The remaining arguments to the user-supplied routine are two strings,
1120** each represented by a [length, data] pair and encoded in the encoding
1121** that was passed as the third argument when the collation sequence was
1122** registered. The user routine should return negative, zero or positive if
1123** the first string is less than, equal to, or greater than the second
1124** string. i.e. (STRING1 - STRING2).
1125*/
danielk19770202b292004-06-09 09:55:16 +00001126int sqlite3_create_collation(
1127 sqlite3*,
1128 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001129 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001130 void*,
1131 int(*xCompare)(void*,int,const void*,int,const void*)
1132);
1133int sqlite3_create_collation16(
1134 sqlite3*,
1135 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001136 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001137 void*,
1138 int(*xCompare)(void*,int,const void*,int,const void*)
1139);
1140
danielk19777cedc8d2004-06-10 10:50:08 +00001141/*
1142** To avoid having to register all collation sequences before a database
1143** can be used, a single callback function may be registered with the
1144** database handle to be called whenever an undefined collation sequence is
1145** required.
1146**
1147** If the function is registered using the sqlite3_collation_needed() API,
1148** then it is passed the names of undefined collation sequences as strings
1149** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1150** are passed as UTF-16 in machine native byte order. A call to either
1151** function replaces any existing callback.
1152**
1153** When the user-function is invoked, the first argument passed is a copy
1154** of the second argument to sqlite3_collation_needed() or
1155** sqlite3_collation_needed16(). The second argument is the database
1156** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1157** SQLITE_UTF16LE, indicating the most desirable form of the collation
1158** sequence function required. The fourth parameter is the name of the
1159** required collation sequence.
1160**
1161** The collation sequence is returned to SQLite by a collation-needed
1162** callback using the sqlite3_create_collation() or
1163** sqlite3_create_collation16() APIs, described above.
1164*/
1165int sqlite3_collation_needed(
1166 sqlite3*,
1167 void*,
1168 void(*)(void*,sqlite3*,int eTextRep,const char*)
1169);
1170int sqlite3_collation_needed16(
1171 sqlite3*,
1172 void*,
1173 void(*)(void*,sqlite3*,int eTextRep,const void*)
1174);
1175
drh2011d5f2004-07-22 02:40:37 +00001176/*
1177** Specify the key for an encrypted database. This routine should be
1178** called right after sqlite3_open().
1179**
1180** The code to implement this API is not available in the public release
1181** of SQLite.
1182*/
1183int sqlite3_key(
1184 sqlite3 *db, /* Database to be rekeyed */
1185 const void *pKey, int nKey /* The key */
1186);
1187
1188/*
1189** Change the key on an open database. If the current database is not
1190** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the
1191** database is decrypted.
1192**
1193** The code to implement this API is not available in the public release
1194** of SQLite.
1195*/
1196int sqlite3_rekey(
1197 sqlite3 *db, /* Database to be rekeyed */
1198 const void *pKey, int nKey /* The new key */
1199);
danielk19770202b292004-06-09 09:55:16 +00001200
drhab3f9fe2004-08-14 17:10:10 +00001201/*
danielk1977600dd0b2005-01-20 01:14:23 +00001202** Sleep for a little while. The second parameter is the number of
1203** miliseconds to sleep for.
1204**
1205** If the operating system does not support sleep requests with
1206** milisecond time resolution, then the time will be rounded up to
1207** the nearest second. The number of miliseconds of sleep actually
1208** requested from the operating system is returned.
danielk1977600dd0b2005-01-20 01:14:23 +00001209*/
1210int sqlite3_sleep(int);
1211
1212/*
drh65efb652005-06-12 22:12:39 +00001213** Return TRUE (non-zero) if the statement supplied as an argument needs
drhd89bd002005-01-22 03:03:54 +00001214** to be recompiled. A statement needs to be recompiled whenever the
1215** execution environment changes in a way that would alter the program
1216** that sqlite3_prepare() generates. For example, if new functions or
1217** collating sequences are registered or if an authorizer function is
1218** added or changed.
1219**
drhd89bd002005-01-22 03:03:54 +00001220*/
1221int sqlite3_expired(sqlite3_stmt*);
1222
1223/*
drhf8db1bc2005-04-22 02:38:37 +00001224** Move all bindings from the first prepared statement over to the second.
1225** This routine is useful, for example, if the first prepared statement
1226** fails with an SQLITE_SCHEMA error. The same SQL can be prepared into
1227** the second prepared statement then all of the bindings transfered over
1228** to the second statement before the first statement is finalized.
drhf8db1bc2005-04-22 02:38:37 +00001229*/
1230int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*);
1231
1232/*
tpoindex9a09a3c2004-12-20 19:01:32 +00001233** If the following global variable is made to point to a
drhab3f9fe2004-08-14 17:10:10 +00001234** string which is the name of a directory, then all temporary files
1235** created by SQLite will be placed in that directory. If this variable
1236** is NULL pointer, then SQLite does a search for an appropriate temporary
1237** file directory.
1238**
danielk19776b456a22005-03-21 04:04:02 +00001239** Once sqlite3_open() has been called, changing this variable will invalidate
1240** the current temporary database, if any.
drhab3f9fe2004-08-14 17:10:10 +00001241*/
tpoindex9a09a3c2004-12-20 19:01:32 +00001242extern char *sqlite3_temp_directory;
drhab3f9fe2004-08-14 17:10:10 +00001243
danielk19776b456a22005-03-21 04:04:02 +00001244/*
1245** This function is called to recover from a malloc() failure that occured
1246** within the SQLite library. Normally, after a single malloc() fails the
1247** library refuses to function (all major calls return SQLITE_NOMEM).
drh9a7e6082005-03-31 22:26:19 +00001248** This function restores the library state so that it can be used again.
danielk19776b456a22005-03-21 04:04:02 +00001249**
1250** All existing statements (sqlite3_stmt pointers) must be finalized or
1251** reset before this call is made. Otherwise, SQLITE_BUSY is returned.
1252** If any in-memory databases are in use, either as a main or TEMP
1253** database, SQLITE_ERROR is returned. In either of these cases, the
1254** library is not reset and remains unusable.
1255**
1256** This function is *not* threadsafe. Calling this from within a threaded
1257** application when threads other than the caller have used SQLite is
1258** dangerous and will almost certainly result in malfunctions.
1259**
1260** This functionality can be omitted from a build by defining the
1261** SQLITE_OMIT_GLOBALRECOVER at compile time.
1262*/
drhd9cb6ac2005-10-20 07:28:17 +00001263int sqlite3_global_recover(void);
danielk19776b456a22005-03-21 04:04:02 +00001264
drh3e1d8e62005-05-26 16:23:34 +00001265/*
1266** Test to see whether or not the database connection is in autocommit
1267** mode. Return TRUE if it is and FALSE if not. Autocommit mode is on
1268** by default. Autocommit is disabled by a BEGIN statement and reenabled
1269** by the next COMMIT or ROLLBACK.
drh3e1d8e62005-05-26 16:23:34 +00001270*/
1271int sqlite3_get_autocommit(sqlite3*);
1272
drh51942bc2005-06-12 22:01:42 +00001273/*
1274** Return the sqlite3* database handle to which the prepared statement given
1275** in the argument belongs. This is the same database handle that was
1276** the first argument to the sqlite3_prepare() that was used to create
1277** the statement in the first place.
1278*/
1279sqlite3 *sqlite3_db_handle(sqlite3_stmt*);
drh3e1d8e62005-05-26 16:23:34 +00001280
drhb37df7b2005-10-13 02:09:49 +00001281/*
danielk197794eb6a12005-12-15 15:22:08 +00001282** Register a callback function with the database connection identified by the
1283** first argument to be invoked whenever a row is updated, inserted or deleted.
1284** Any callback set by a previous call to this function for the same
1285** database connection is overridden.
1286**
1287** The second argument is a pointer to the function to invoke when a
1288** row is updated, inserted or deleted. The first argument to the callback is
1289** a copy of the third argument to sqlite3_update_hook. The second callback
1290** argument is one of SQLITE_INSERT, SQLITE_DELETE or SQLITE_UPDATE, depending
1291** on the operation that caused the callback to be invoked. The third and
1292** fourth arguments to the callback contain pointers to the database and
1293** table name containing the affected row. The final callback parameter is
1294** the rowid of the row. In the case of an update, this is the rowid after
1295** the update takes place.
1296**
1297** The update hook is not invoked when internal system tables are
1298** modified (i.e. sqlite_master and sqlite_sequence).
danielk197771fd80b2005-12-16 06:54:01 +00001299**
1300** If another function was previously registered, its pArg value is returned.
1301** Otherwise NULL is returned.
danielk197794eb6a12005-12-15 15:22:08 +00001302*/
danielk197771fd80b2005-12-16 06:54:01 +00001303void *sqlite3_update_hook(
danielk197794eb6a12005-12-15 15:22:08 +00001304 sqlite3*,
1305 void(*)(void *,int ,char const *,char const *,sqlite_int64),
1306 void*
1307);
danielk197713a68c32005-12-15 10:11:30 +00001308
danielk1977f3f06bb2005-12-16 15:24:28 +00001309/*
1310** Register a callback to be invoked whenever a transaction is rolled
1311** back.
1312**
1313** The new callback function overrides any existing rollback-hook
1314** callback. If there was an existing callback, then it's pArg value
1315** (the third argument to sqlite3_rollback_hook() when it was registered)
1316** is returned. Otherwise, NULL is returned.
1317**
1318** For the purposes of this API, a transaction is said to have been
1319** rolled back if an explicit "ROLLBACK" statement is executed, or
1320** an error or constraint causes an implicit rollback to occur. The
1321** callback is not invoked if a transaction is automatically rolled
1322** back because the database connection is closed.
1323*/
danielk197771fd80b2005-12-16 06:54:01 +00001324void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*);
1325
danielk19777ddad962005-12-12 06:53:03 +00001326/*
danielk1977aef0bf62005-12-30 16:28:01 +00001327** This function is only available if the library is compiled without
1328** the SQLITE_OMIT_SHARED_CACHE macro defined. It is used to enable or
1329** disable (if the argument is true or false, respectively) the
1330** "shared pager" feature.
1331*/
1332int sqlite3_enable_shared_cache(int);
1333
1334/*
danielk197752622822006-01-09 09:59:49 +00001335** Attempt to free N bytes of heap memory by deallocating non-essential
1336** memory allocations held by the database library (example: memory
1337** used to cache database pages to improve performance).
1338**
drh6f7adc82006-01-11 21:41:20 +00001339** This function is not a part of standard builds. It is only created
1340** if SQLite is compiled with the SQLITE_ENABLE_MEMORY_MANAGEMENT macro.
danielk197752622822006-01-09 09:59:49 +00001341*/
1342int sqlite3_release_memory(int);
1343
1344/*
1345** Place a "soft" limit on the amount of heap memory that may be allocated by
1346** SQLite within the current thread. If an internal allocation is requested
1347** that would exceed the specified limit, sqlite3_release_memory() is invoked
1348** one or more times to free up some space before the allocation is made.
1349**
1350** The limit is called "soft", because if sqlite3_release_memory() cannot free
1351** sufficient memory to prevent the limit from being exceeded, the memory is
1352** allocated anyway and the current operation proceeds.
1353**
drh6f7adc82006-01-11 21:41:20 +00001354** This function is only available if the library was compiled with the
1355** SQLITE_ENABLE_MEMORY_MANAGEMENT option set.
danielk197752622822006-01-09 09:59:49 +00001356** memory-management has been enabled.
1357*/
drhd2d4a6b2006-01-10 15:18:27 +00001358void sqlite3_soft_heap_limit(int);
danielk197752622822006-01-09 09:59:49 +00001359
1360/*
drh6f7adc82006-01-11 21:41:20 +00001361** This routine makes sure that all thread-local storage has been
1362** deallocated for the current thread.
1363**
1364** This routine is not technically necessary. All thread-local storage
1365** will be automatically deallocated once memory-management and
1366** shared-cache are disabled and the soft heap limit has been set
1367** to zero. This routine is provided as a convenience for users who
1368** want to make absolutely sure they have not forgotten something
1369** prior to killing off a thread.
1370*/
1371void sqlite3_thread_cleanup(void);
1372
1373/*
drhb37df7b2005-10-13 02:09:49 +00001374** Undo the hack that converts floating point types to integer for
1375** builds on processors without floating point support.
1376*/
1377#ifdef SQLITE_OMIT_FLOATING_POINT
1378# undef double
1379#endif
1380
drh382c0242001-10-06 16:33:02 +00001381#ifdef __cplusplus
1382} /* End of the 'extern "C"' block */
1383#endif
danielk19774adee202004-05-08 08:23:19 +00001384#endif