blob: b105b6709c01a59a2faa1832570993120987102c [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**
danielk19775591df52005-12-20 09:19:37 +000015** @(#) $Id: sqlite.h.in,v 1.151 2005/12/20 09:19:37 danielk1977 Exp $
drh75897232000-05-29 14:26:00 +000016*/
drh12057d52004-09-06 17:34:12 +000017#ifndef _SQLITE3_H_
18#define _SQLITE3_H_
drha18c5682000-10-08 22:20:57 +000019#include <stdarg.h> /* Needed for the definition of va_list */
drh75897232000-05-29 14:26:00 +000020
21/*
drh382c0242001-10-06 16:33:02 +000022** Make sure we can call this stuff from C++.
23*/
24#ifdef __cplusplus
25extern "C" {
26#endif
27
28/*
drhb86ccfb2003-01-28 23:13:10 +000029** The version of the SQLite library.
30*/
drh1e284f42004-10-06 15:52:01 +000031#ifdef SQLITE_VERSION
32# undef SQLITE_VERSION
drh1e284f42004-10-06 15:52:01 +000033#endif
danielk197799ba19e2005-02-05 07:33:34 +000034#define SQLITE_VERSION "--VERS--"
35
36/*
37** The format of the version string is "X.Y.Z<trailing string>", where
38** X is the major version number, Y is the minor version number and Z
39** is the release number. The trailing string is often "alpha" or "beta".
40** For example "3.1.1beta".
41**
42** The SQLITE_VERSION_NUMBER is an integer with the value
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 */
167#define SQLITE_ERROR 1 /* SQL error or missing database */
drh2db0bbc2005-08-11 02:10:18 +0000168#define SQLITE_INTERNAL 2 /* NOT USED. Internal logic error in SQLite */
drh717e6402001-09-27 03:22:32 +0000169#define SQLITE_PERM 3 /* Access permission denied */
170#define SQLITE_ABORT 4 /* Callback routine requested an abort */
171#define SQLITE_BUSY 5 /* The database file is locked */
172#define SQLITE_LOCKED 6 /* A table in the database is locked */
173#define SQLITE_NOMEM 7 /* A malloc() failed */
174#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000175#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000176#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
177#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
drh2db0bbc2005-08-11 02:10:18 +0000178#define SQLITE_NOTFOUND 12 /* NOT USED. Table or record not found */
drh717e6402001-09-27 03:22:32 +0000179#define SQLITE_FULL 13 /* Insertion failed because database is full */
180#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
181#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000182#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000183#define SQLITE_SCHEMA 17 /* The database schema changed */
drh2db0bbc2005-08-11 02:10:18 +0000184#define SQLITE_TOOBIG 18 /* NOT USED. Too much data for one row */
drh717e6402001-09-27 03:22:32 +0000185#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000186#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000187#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000188#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000189#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000190#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000191#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000192#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000193#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
194#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh717e6402001-09-27 03:22:32 +0000195
drhaf9ff332002-01-16 21:00:27 +0000196/*
197** Each entry in an SQLite table has a unique integer key. (The key is
198** the value of the INTEGER PRIMARY KEY column if there is such a column,
199** otherwise the key is generated at random. The unique key is always
200** available as the ROWID, OID, or _ROWID_ column.) The following routine
201** returns the integer key of the most recent insert in the database.
202**
203** This function is similar to the mysql_insert_id() function from MySQL.
204*/
drhefad9992004-06-22 12:13:55 +0000205sqlite_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000206
drhc8d30ac2002-04-12 10:08:59 +0000207/*
208** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000209** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000210**
211** All changes are counted, even if they were later undone by a
212** ROLLBACK or ABORT. Except, changes associated with creating and
213** dropping tables are not counted.
214**
danielk19776f8a5032004-05-10 10:34:51 +0000215** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000216** in the inner, recursive call are counted together with the changes
217** in the outer call.
218**
219** SQLite implements the command "DELETE FROM table" without a WHERE clause
220** by dropping and recreating the table. (This is much faster than going
221** through and deleting individual elements form the table.) Because of
222** this optimization, the change count for "DELETE FROM table" will be
223** zero regardless of the number of elements that were originally in the
224** table. To get an accurate count of the number of rows deleted, use
225** "DELETE FROM table WHERE 1" instead.
226*/
danielk1977f9d64d22004-06-19 08:18:07 +0000227int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000228
rdcf146a772004-02-25 22:51:06 +0000229/*
danielk1977b28af712004-06-21 06:50:26 +0000230** This function returns the number of database rows that have been
231** modified by INSERT, UPDATE or DELETE statements since the database handle
232** was opened. This includes UPDATE, INSERT and DELETE statements executed
233** as part of trigger programs. All changes are counted as soon as the
234** statement that makes them is completed (when the statement handle is
235** passed to sqlite3_reset() or sqlite_finalise()).
rdcf146a772004-02-25 22:51:06 +0000236**
237** SQLite implements the command "DELETE FROM table" without a WHERE clause
238** by dropping and recreating the table. (This is much faster than going
239** through and deleting individual elements form the table.) Because of
240** this optimization, the change count for "DELETE FROM table" will be
241** zero regardless of the number of elements that were originally in the
242** table. To get an accurate count of the number of rows deleted, use
243** "DELETE FROM table WHERE 1" instead.
rdcf146a772004-02-25 22:51:06 +0000244*/
danielk1977b28af712004-06-21 06:50:26 +0000245int sqlite3_total_changes(sqlite3*);
246
drh4c504392000-10-16 22:06:40 +0000247/* This function causes any pending database operation to abort and
248** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000249** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000250** or Ctrl-C where the user wants a long query operation to halt
251** immediately.
252*/
danielk1977f9d64d22004-06-19 08:18:07 +0000253void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000254
drheec553b2000-06-02 01:51:20 +0000255
danielk197761de0d12004-05-27 23:56:16 +0000256/* These functions return true if the given input string comprises
257** one or more complete SQL statements. For the sqlite3_complete() call,
258** the parameter must be a nul-terminated UTF-8 string. For
259** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
260** is required.
drh75897232000-05-29 14:26:00 +0000261**
262** The algorithm is simple. If the last token other than spaces
263** and comments is a semicolon, then return true. otherwise return
264** false.
265*/
danielk19776f8a5032004-05-10 10:34:51 +0000266int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000267int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000268
drh2dfbbca2000-07-28 14:32:48 +0000269/*
270** This routine identifies a callback function that is invoked
271** whenever an attempt is made to open a database table that is
272** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000273** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000274** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000275** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000276** second argument is the name of the locked table and the third
277** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000278** busy callback returns 0, then sqlite3_exec() immediately returns
279** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000280** tries to open the table again and the cycle repeats.
281**
282** The default busy callback is NULL.
283**
284** Sqlite is re-entrant, so the busy handler may start a new query.
285** (It is not clear why anyone would every want to do this, but it
286** is allowed, in theory.) But the busy handler may not close the
287** database. Closing the database from a busy handler will delete
288** data structures out from under the executing query and will
289** probably result in a coredump.
290*/
danielk1977f9d64d22004-06-19 08:18:07 +0000291int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000292
293/*
294** This routine sets a busy handler that sleeps for a while when a
295** table is locked. The handler will sleep multiple times until
296** at least "ms" milleseconds of sleeping have been done. After
297** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000298** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000299**
300** Calling this routine with an argument less than or equal to zero
301** turns off all busy handlers.
302*/
danielk1977f9d64d22004-06-19 08:18:07 +0000303int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000304
drhe3710332000-09-29 13:30:53 +0000305/*
danielk19776f8a5032004-05-10 10:34:51 +0000306** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000307** Instead of invoking a user-supplied callback for each row of the
308** result, this routine remembers each row of the result in memory
309** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000310** query has finished.
311**
312** As an example, suppose the query result where this table:
313**
314** Name | Age
315** -----------------------
316** Alice | 43
317** Bob | 28
318** Cindy | 21
319**
320** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000321** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000322**
323** azResult[0] = "Name";
324** azResult[1] = "Age";
325** azResult[2] = "Alice";
326** azResult[3] = "43";
327** azResult[4] = "Bob";
328** azResult[5] = "28";
329** azResult[6] = "Cindy";
330** azResult[7] = "21";
331**
332** Notice that there is an extra row of data containing the column
333** headers. But the *nrow return value is still 3. *ncolumn is
334** set to 2. In general, the number of values inserted into azResult
335** will be ((*nrow) + 1)*(*ncolumn).
336**
337** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000338** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000339** release the memory that was malloc-ed. Because of the way the
340** malloc() happens, the calling function must not try to call
danielk197799b214d2005-02-02 01:13:38 +0000341** free() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000342** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000343**
danielk19776f8a5032004-05-10 10:34:51 +0000344** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000345*/
danielk19776f8a5032004-05-10 10:34:51 +0000346int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000347 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000348 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000349 char ***resultp, /* Result written to a char *[] that this points to */
350 int *nrow, /* Number of result rows written here */
351 int *ncolumn, /* Number of result columns written here */
352 char **errmsg /* Error msg written here */
353);
354
355/*
danielk19776f8a5032004-05-10 10:34:51 +0000356** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000357*/
danielk19776f8a5032004-05-10 10:34:51 +0000358void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000359
drha18c5682000-10-08 22:20:57 +0000360/*
drh4f26d6c2004-05-26 23:25:30 +0000361** The following routines are variants of the "sprintf()" from the
362** standard C library. The resulting string is written into memory
363** obtained from malloc() so that there is never a possiblity of buffer
364** overflow. These routines also implement some additional formatting
365** options that are useful for constructing SQL statements.
366**
367** The strings returned by these routines should be freed by calling
368** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000369**
370** All of the usual printf formatting options apply. In addition, there
371** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000372** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000373** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000374** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000375** the string.
376**
377** For example, so some string variable contains text as follows:
378**
379** char *zText = "It's a happy day!";
380**
381** We can use this text in an SQL statement as follows:
382**
drh3224b322005-09-08 10:58:51 +0000383** char *z = sqlite3_mprintf("INSERT INTO TABLES('%q')", zText);
384** sqlite3_exec(db, z, callback1, 0, 0);
385** sqlite3_free(z);
drha18c5682000-10-08 22:20:57 +0000386**
387** Because the %q format string is used, the '\'' character in zText
388** is escaped and the SQL generated is as follows:
389**
390** INSERT INTO table1 VALUES('It''s a happy day!')
391**
392** This is correct. Had we used %s instead of %q, the generated SQL
393** would have looked like this:
394**
395** INSERT INTO table1 VALUES('It's a happy day!');
396**
397** This second example is an SQL syntax error. As a general rule you
398** should always use %q instead of %s when inserting text into a string
399** literal.
400*/
danielk19776f8a5032004-05-10 10:34:51 +0000401char *sqlite3_mprintf(const char*,...);
402char *sqlite3_vmprintf(const char*, va_list);
drh4f26d6c2004-05-26 23:25:30 +0000403void sqlite3_free(char *z);
drhfeac5f82004-08-01 00:10:45 +0000404char *sqlite3_snprintf(int,char*,const char*, ...);
drh5191b7e2002-03-08 02:12:00 +0000405
drh1211de32004-07-26 12:24:22 +0000406#ifndef SQLITE_OMIT_AUTHORIZATION
drh5191b7e2002-03-08 02:12:00 +0000407/*
drhed6c8672003-01-12 18:02:16 +0000408** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000409** callback is invoked (at compile-time, not at run-time) for each
410** attempt to access a column of a table in the database. The callback
411** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
412** SQL statement should be aborted with an error and SQLITE_IGNORE
413** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000414*/
danielk19776f8a5032004-05-10 10:34:51 +0000415int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000416 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000417 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000418 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000419);
drh1211de32004-07-26 12:24:22 +0000420#endif
drhed6c8672003-01-12 18:02:16 +0000421
422/*
423** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000424** be one of the values below. These values signify what kind of operation
425** is to be authorized. The 3rd and 4th parameters to the authorization
426** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000427** codes is used as the second parameter. The 5th parameter is the name
428** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000429** is the name of the inner-most trigger or view that is responsible for
430** the access attempt or NULL if this access attempt is directly from
431** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000432**
433** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000434*/
drh77ad4e42003-01-14 02:49:27 +0000435#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000436#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
437#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
438#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
439#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000440#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000441#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000442#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000443#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
444#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000445#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000446#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000447#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000448#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000449#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000450#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000451#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000452#define SQLITE_DROP_VIEW 17 /* View Name NULL */
453#define SQLITE_INSERT 18 /* Table Name NULL */
454#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
455#define SQLITE_READ 20 /* Table Name Column Name */
456#define SQLITE_SELECT 21 /* NULL NULL */
457#define SQLITE_TRANSACTION 22 /* NULL NULL */
458#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000459#define SQLITE_ATTACH 24 /* Filename NULL */
460#define SQLITE_DETACH 25 /* Database Name NULL */
danielk19771c8c23c2004-11-12 15:53:37 +0000461#define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */
danielk19771d54df82004-11-23 15:41:16 +0000462#define SQLITE_REINDEX 27 /* Index Name NULL */
drhe6e04962005-07-23 02:17:03 +0000463#define SQLITE_ANALYZE 28 /* Table Name NULL */
drh81e293b2003-06-06 19:00:42 +0000464
drhed6c8672003-01-12 18:02:16 +0000465
466/*
467** The return value of the authorization function should be one of the
468** following constants:
469*/
470/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
471#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
472#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
473
474/*
drh19e2d372005-08-29 23:00:03 +0000475** Register a function for tracing SQL command evaluation. The function
476** registered by sqlite3_trace() is invoked at the first sqlite3_step()
477** for the evaluation of an SQL statement. The function registered by
478** sqlite3_profile() runs at the end of each SQL statement and includes
479** information on how long that statement ran.
480**
481** The sqlite3_profile() API is currently considered experimental and
482** is subject to change.
drh18de4822003-01-16 16:28:53 +0000483*/
danielk1977f9d64d22004-06-19 08:18:07 +0000484void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh19e2d372005-08-29 23:00:03 +0000485void *sqlite3_profile(sqlite3*,
486 void(*xProfile)(void*,const char*,sqlite_uint64), void*);
drh18de4822003-01-16 16:28:53 +0000487
danielk1977348bb5d2003-10-18 09:37:26 +0000488/*
489** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000490** is invoked periodically during long running calls to sqlite3_exec(),
danielk19772097e942004-11-20 06:05:56 +0000491** sqlite3_step() and sqlite3_get_table(). An example use for this API is to
492** keep a GUI updated during a large query.
danielk1977348bb5d2003-10-18 09:37:26 +0000493**
494** The progress callback is invoked once for every N virtual machine opcodes,
495** where N is the second argument to this function. The progress callback
496** itself is identified by the third argument to this function. The fourth
497** argument to this function is a void pointer passed to the progress callback
498** function each time it is invoked.
499**
danielk19776f8a5032004-05-10 10:34:51 +0000500** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000501** in less than N opcodes being executed, then the progress callback is not
502** invoked.
503**
danielk1977348bb5d2003-10-18 09:37:26 +0000504** To remove the progress callback altogether, pass NULL as the third
505** argument to this function.
506**
507** If the progress callback returns a result other than 0, then the current
508** query is immediately terminated and any database changes rolled back. If the
509** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000510** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000511**
512******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000513*/
danielk1977f9d64d22004-06-19 08:18:07 +0000514void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000515
drhaa940ea2004-01-15 02:44:03 +0000516/*
517** Register a callback function to be invoked whenever a new transaction
518** is committed. The pArg argument is passed through to the callback.
519** callback. If the callback function returns non-zero, then the commit
520** is converted into a rollback.
521**
522** If another function was previously registered, its pArg value is returned.
523** Otherwise NULL is returned.
524**
525** Registering a NULL function disables the callback.
526**
527******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
528*/
danielk1977f9d64d22004-06-19 08:18:07 +0000529void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000530
drh22fbcb82004-02-01 01:22:50 +0000531/*
drh4f26d6c2004-05-26 23:25:30 +0000532** Open the sqlite database file "filename". The "filename" is UTF-8
533** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
534** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
535** if an error occurs. If the database is opened (or created) successfully,
536** then SQLITE_OK is returned. Otherwise an error code is returned. The
537** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
538** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000539**
drh4f26d6c2004-05-26 23:25:30 +0000540** If the database file does not exist, then a new database is created.
541** The encoding for the database is UTF-8 if sqlite3_open() is called and
542** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000543**
544** Whether or not an error occurs when it is opened, resources associated
545** with the sqlite3* handle should be released by passing it to
546** sqlite3_close() when it is no longer required.
547*/
548int sqlite3_open(
549 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000550 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000551);
danielk197765904932004-05-26 06:18:37 +0000552int sqlite3_open16(
553 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000554 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000555);
danielk1977295ba552004-05-19 10:34:51 +0000556
danielk197765904932004-05-26 06:18:37 +0000557/*
558** Return the error code for the most recent sqlite3_* API call associated
559** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
560** API call was successful.
561**
562** Calls to many sqlite3_* functions set the error code and string returned
563** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
564** (overwriting the previous values). Note that calls to sqlite3_errcode(),
565** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
566** results of future invocations.
567**
568** Assuming no other intervening sqlite3_* API calls are made, the error
569** code returned by this function is associated with the same error as
570** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
571*/
572int sqlite3_errcode(sqlite3 *db);
573
574/*
575** Return a pointer to a UTF-8 encoded string describing in english the
576** error condition for the most recent sqlite3_* API call. The returned
577** string is always terminated by an 0x00 byte.
578**
579** The string "not an error" is returned when the most recent API call was
580** successful.
581*/
582const char *sqlite3_errmsg(sqlite3*);
583
584/*
585** Return a pointer to a UTF-16 native byte order encoded string describing
586** in english the error condition for the most recent sqlite3_* API call.
587** The returned string is always terminated by a pair of 0x00 bytes.
588**
589** The string "not an error" is returned when the most recent API call was
590** successful.
591*/
592const void *sqlite3_errmsg16(sqlite3*);
593
594/*
595** An instance of the following opaque structure is used to represent
596** a compiled SQL statment.
597*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000598typedef struct sqlite3_stmt sqlite3_stmt;
599
danielk1977e3209e42004-05-20 01:40:18 +0000600/*
danielk197765904932004-05-26 06:18:37 +0000601** To execute an SQL query, it must first be compiled into a byte-code
602** program using one of the following routines. The only difference between
603** them is that the second argument, specifying the SQL statement to
604** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
605** function and UTF-16 for sqlite3_prepare16().
606**
607** The first parameter "db" is an SQLite database handle. The second
608** parameter "zSql" is the statement to be compiled, encoded as either
609** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
610** than zero, then zSql is read up to the first nul terminator. If
611** "nBytes" is not less than zero, then it is the length of the string zSql
612** in bytes (not characters).
613**
614** *pzTail is made to point to the first byte past the end of the first
615** SQL statement in zSql. This routine only compiles the first statement
616** in zSql, so *pzTail is left pointing to what remains uncompiled.
617**
618** *ppStmt is left pointing to a compiled SQL statement that can be
619** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
620** set to NULL. If the input text contained no SQL (if the input is and
621** empty string or a comment) then *ppStmt is set to NULL.
622**
623** On success, SQLITE_OK is returned. Otherwise an error code is returned.
624*/
625int sqlite3_prepare(
626 sqlite3 *db, /* Database handle */
627 const char *zSql, /* SQL statement, UTF-8 encoded */
628 int nBytes, /* Length of zSql in bytes. */
629 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
630 const char **pzTail /* OUT: Pointer to unused portion of zSql */
631);
632int sqlite3_prepare16(
633 sqlite3 *db, /* Database handle */
634 const void *zSql, /* SQL statement, UTF-16 encoded */
635 int nBytes, /* Length of zSql in bytes. */
636 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
637 const void **pzTail /* OUT: Pointer to unused portion of zSql */
638);
639
640/*
drhf4479502004-05-27 03:12:53 +0000641** Pointers to the following two opaque structures are used to communicate
642** with the implementations of user-defined functions.
643*/
644typedef struct sqlite3_context sqlite3_context;
645typedef struct Mem sqlite3_value;
646
647/*
drh4f26d6c2004-05-26 23:25:30 +0000648** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
drh32c0d4f2004-12-07 02:14:51 +0000649** one or more literals can be replace by parameters "?" or ":AAA" or
650** "$VVV" where AAA is an identifer and VVV is a variable name according
651** to the syntax rules of the TCL programming language.
652** The value of these parameters (also called "host parameter names") can
653** be set using the routines listed below.
drh4f26d6c2004-05-26 23:25:30 +0000654**
655** In every case, the first parameter is a pointer to the sqlite3_stmt
656** structure returned from sqlite3_prepare(). The second parameter is the
drh32c0d4f2004-12-07 02:14:51 +0000657** index of the parameter. The first parameter as an index of 1. For
658** named parameters (":AAA" or "$VVV") you can use
659** sqlite3_bind_parameter_index() to get the correct index value given
660** the parameters name. If the same named parameter occurs more than
661** once, it is assigned the same index each time.
drh4f26d6c2004-05-26 23:25:30 +0000662**
drh900dfba2004-07-21 15:21:36 +0000663** The fifth parameter to sqlite3_bind_blob(), sqlite3_bind_text(), and
664** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or
665** text after SQLite has finished with it. If the fifth argument is the
666** special value SQLITE_STATIC, then the library assumes that the information
667** is in static, unmanaged space and does not need to be freed. If the
668** fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its
669** own private copy of the data.
drh4f26d6c2004-05-26 23:25:30 +0000670**
671** The sqlite3_bind_* routine must be called before sqlite3_step() after
drh32c0d4f2004-12-07 02:14:51 +0000672** an sqlite3_prepare() or sqlite3_reset(). Unbound parameterss are
673** interpreted as NULL.
drh4f26d6c2004-05-26 23:25:30 +0000674*/
danielk1977d8123362004-06-12 09:25:12 +0000675int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000676int sqlite3_bind_double(sqlite3_stmt*, int, double);
677int sqlite3_bind_int(sqlite3_stmt*, int, int);
drhefad9992004-06-22 12:13:55 +0000678int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64);
drhf4479502004-05-27 03:12:53 +0000679int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000680int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
681int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000682int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000683
684/*
drh32c0d4f2004-12-07 02:14:51 +0000685** Return the number of parameters in a compiled SQL statement. This
drh75f6a032004-07-15 14:15:00 +0000686** routine was added to support DBD::SQLite.
drh75f6a032004-07-15 14:15:00 +0000687*/
688int sqlite3_bind_parameter_count(sqlite3_stmt*);
689
690/*
drh32c0d4f2004-12-07 02:14:51 +0000691** Return the name of the i-th parameter. Ordinary parameters "?" are
692** nameless and a NULL is returned. For parameters of the form :AAA or
693** $VVV the complete text of the parameter name is returned, including
694** the initial ":" or "$". NULL is returned if the index is out of range.
drh895d7472004-08-20 16:02:39 +0000695*/
696const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
697
698/*
drhfa6bc002004-09-07 16:19:52 +0000699** Return the index of a parameter with the given name. The name
700** must match exactly. If no parameter with the given name is found,
701** return 0.
702*/
703int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
704
705/*
danielk1977600dd0b2005-01-20 01:14:23 +0000706** Set all the parameters in the compiled SQL statement to NULL.
danielk1977600dd0b2005-01-20 01:14:23 +0000707*/
708int sqlite3_clear_bindings(sqlite3_stmt*);
709
710/*
danielk197765904932004-05-26 06:18:37 +0000711** Return the number of columns in the result set returned by the compiled
712** SQL statement. This routine returns 0 if pStmt is an SQL statement
713** that does not return data (for example an UPDATE).
714*/
715int sqlite3_column_count(sqlite3_stmt *pStmt);
716
717/*
718** The first parameter is a compiled SQL statement. This function returns
719** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000720** second function parameter. The string returned is UTF-8 for
721** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000722*/
723const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000724const void *sqlite3_column_name16(sqlite3_stmt*,int);
725
726/*
727** The first parameter is a compiled SQL statement. If this statement
728** is a SELECT statement, the Nth column of the returned result set
729** of the SELECT is a table column then the declared type of the table
730** column is returned. If the Nth column of the result set is not at table
731** column, then a NULL pointer is returned. The returned string is always
732** UTF-8 encoded. For example, in the database schema:
733**
734** CREATE TABLE t1(c1 VARIANT);
735**
736** And the following statement compiled:
737**
738** SELECT c1 + 1, 0 FROM t1;
739**
740** Then this routine would return the string "VARIANT" for the second
741** result column (i==1), and a NULL pointer for the first result column
742** (i==0).
743*/
744const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
745
746/*
747** The first parameter is a compiled SQL statement. If this statement
748** is a SELECT statement, the Nth column of the returned result set
749** of the SELECT is a table column then the declared type of the table
750** column is returned. If the Nth column of the result set is not at table
751** column, then a NULL pointer is returned. The returned string is always
752** UTF-16 encoded. For example, in the database schema:
753**
drh4f26d6c2004-05-26 23:25:30 +0000754** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000755**
756** And the following statement compiled:
757**
758** SELECT c1 + 1, 0 FROM t1;
759**
drh4f26d6c2004-05-26 23:25:30 +0000760** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000761** result column (i==1), and a NULL pointer for the first result column
762** (i==0).
763*/
764const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
765
danielk1977106bb232004-05-21 10:08:53 +0000766/*
767** After an SQL query has been compiled with a call to either
768** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
769** called one or more times to execute the statement.
770**
771** The return value will be either SQLITE_BUSY, SQLITE_DONE,
772** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
773**
774** SQLITE_BUSY means that the database engine attempted to open
775** a locked database and there is no busy callback registered.
776** Call sqlite3_step() again to retry the open.
777**
778** SQLITE_DONE means that the statement has finished executing
779** successfully. sqlite3_step() should not be called again on this virtual
780** machine.
781**
782** If the SQL statement being executed returns any data, then
783** SQLITE_ROW is returned each time a new row of data is ready
784** for processing by the caller. The values may be accessed using
785** the sqlite3_column_*() functions described below. sqlite3_step()
786** is called again to retrieve the next row of data.
787**
788** SQLITE_ERROR means that a run-time error (such as a constraint
789** violation) has occurred. sqlite3_step() should not be called again on
790** the VM. More information may be found by calling sqlite3_errmsg().
791**
792** SQLITE_MISUSE means that the this routine was called inappropriately.
793** Perhaps it was called on a virtual machine that had already been
794** finalized or on one that had previously returned SQLITE_ERROR or
795** SQLITE_DONE. Or it could be the case the the same database connection
796** is being used simulataneously by two or more threads.
797*/
danielk197717240fd2004-05-26 00:07:25 +0000798int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000799
danielk1977106bb232004-05-21 10:08:53 +0000800/*
801** Return the number of values in the current row of the result set.
802**
803** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
804** will return the same value as the sqlite3_column_count() function.
805** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
806** error code, or before sqlite3_step() has been called on a
807** compiled SQL statement, this routine returns zero.
808*/
danielk197793d46752004-05-23 13:30:58 +0000809int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000810
drh4f26d6c2004-05-26 23:25:30 +0000811/*
812** Values are stored in the database in one of the following fundamental
813** types.
814*/
drh9c054832004-05-31 18:51:57 +0000815#define SQLITE_INTEGER 1
816#define SQLITE_FLOAT 2
drh1e284f42004-10-06 15:52:01 +0000817/* #define SQLITE_TEXT 3 // See below */
drh9c054832004-05-31 18:51:57 +0000818#define SQLITE_BLOB 4
819#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000820
danielk1977106bb232004-05-21 10:08:53 +0000821/*
drh1e284f42004-10-06 15:52:01 +0000822** SQLite version 2 defines SQLITE_TEXT differently. To allow both
823** version 2 and version 3 to be included, undefine them both if a
824** conflict is seen. Define SQLITE3_TEXT to be the version 3 value.
825*/
826#ifdef SQLITE_TEXT
827# undef SQLITE_TEXT
828#else
829# define SQLITE_TEXT 3
830#endif
831#define SQLITE3_TEXT 3
832
833/*
drh4f26d6c2004-05-26 23:25:30 +0000834** The next group of routines returns information about the information
835** in a single column of the current result row of a query. In every
836** case the first parameter is a pointer to the SQL statement that is being
837** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
838** the second argument is the index of the column for which information
839** should be returned. iCol is zero-indexed. The left-most column as an
840** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000841**
drh4f26d6c2004-05-26 23:25:30 +0000842** If the SQL statement is not currently point to a valid row, or if the
843** the colulmn index is out of range, the result is undefined.
844**
845** These routines attempt to convert the value where appropriate. For
846** example, if the internal representation is FLOAT and a text result
847** is requested, sprintf() is used internally to do the conversion
848** automatically. The following table details the conversions that
849** are applied:
850**
851** Internal Type Requested Type Conversion
852** ------------- -------------- --------------------------
853** NULL INTEGER Result is 0
854** NULL FLOAT Result is 0.0
855** NULL TEXT Result is an empty string
856** NULL BLOB Result is a zero-length BLOB
857** INTEGER FLOAT Convert from integer to float
858** INTEGER TEXT ASCII rendering of the integer
859** INTEGER BLOB Same as for INTEGER->TEXT
860** FLOAT INTEGER Convert from float to integer
861** FLOAT TEXT ASCII rendering of the float
862** FLOAT BLOB Same as FLOAT->TEXT
863** TEXT INTEGER Use atoi()
864** TEXT FLOAT Use atof()
865** TEXT BLOB No change
866** BLOB INTEGER Convert to TEXT then use atoi()
867** BLOB FLOAT Convert to TEXT then use atof()
868** BLOB TEXT Add a \000 terminator if needed
869**
870** The following access routines are provided:
871**
872** _type() Return the datatype of the result. This is one of
873** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
874** or SQLITE_NULL.
875** _blob() Return the value of a BLOB.
876** _bytes() Return the number of bytes in a BLOB value or the number
877** of bytes in a TEXT value represented as UTF-8. The \000
878** terminator is included in the byte count for TEXT values.
879** _bytes16() Return the number of bytes in a BLOB value or the number
880** of bytes in a TEXT value represented as UTF-16. The \u0000
881** terminator is included in the byte count for TEXT values.
882** _double() Return a FLOAT value.
883** _int() Return an INTEGER value in the host computer's native
884** integer representation. This might be either a 32- or 64-bit
885** integer depending on the host.
886** _int64() Return an INTEGER value as a 64-bit signed integer.
887** _text() Return the value as UTF-8 text.
888** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000889*/
drhf4479502004-05-27 03:12:53 +0000890const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
891int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
892int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
893double sqlite3_column_double(sqlite3_stmt*, int iCol);
894int sqlite3_column_int(sqlite3_stmt*, int iCol);
drhefad9992004-06-22 12:13:55 +0000895sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +0000896const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
897const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000898int sqlite3_column_type(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000899
danielk197765904932004-05-26 06:18:37 +0000900/*
901** The sqlite3_finalize() function is called to delete a compiled
902** SQL statement obtained by a previous call to sqlite3_prepare()
903** or sqlite3_prepare16(). If the statement was executed successfully, or
904** not executed at all, then SQLITE_OK is returned. If execution of the
905** statement failed then an error code is returned.
906**
907** This routine can be called at any point during the execution of the
908** virtual machine. If the virtual machine has not completed execution
909** when this routine is called, that is like encountering an error or
910** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
911** rolled back and transactions cancelled, depending on the circumstances,
912** and the result code returned will be SQLITE_ABORT.
913*/
914int sqlite3_finalize(sqlite3_stmt *pStmt);
915
916/*
917** The sqlite3_reset() function is called to reset a compiled SQL
918** statement obtained by a previous call to sqlite3_prepare() or
919** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
920** Any SQL statement variables that had values bound to them using
921** the sqlite3_bind_*() API retain their values.
922*/
923int sqlite3_reset(sqlite3_stmt *pStmt);
924
925/*
danielk197765904932004-05-26 06:18:37 +0000926** The following two functions are used to add user functions or aggregates
927** implemented in C to the SQL langauge interpreted by SQLite. The
928** difference only between the two is that the second parameter, the
929** name of the (scalar) function or aggregate, is encoded in UTF-8 for
930** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
931**
932** The first argument is the database handle that the new function or
933** aggregate is to be added to. If a single program uses more than one
934** database handle internally, then user functions or aggregates must
935** be added individually to each database handle with which they will be
936** used.
937**
938** The third parameter is the number of arguments that the function or
939** aggregate takes. If this parameter is negative, then the function or
940** aggregate may take any number of arguments.
941**
danielk1977d8123362004-06-12 09:25:12 +0000942** The fourth parameter is one of SQLITE_UTF* values defined below,
943** indicating the encoding that the function is most likely to handle
944** values in. This does not change the behaviour of the programming
945** interface. However, if two versions of the same function are registered
946** with different encoding values, SQLite invokes the version likely to
947** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +0000948**
danielk197765904932004-05-26 06:18:37 +0000949** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
950** pointers to user implemented C functions that implement the user
951** function or aggregate. A scalar function requires an implementation of
952** the xFunc callback only, NULL pointers should be passed as the xStep
953** and xFinal parameters. An aggregate function requires an implementation
954** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
955** existing user function or aggregate, pass NULL for all three function
956** callback. Specifying an inconstent set of callback values, such as an
957** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
958** returned.
959*/
960int sqlite3_create_function(
961 sqlite3 *,
962 const char *zFunctionName,
963 int nArg,
964 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000965 void*,
966 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
967 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
968 void (*xFinal)(sqlite3_context*)
969);
970int sqlite3_create_function16(
971 sqlite3*,
972 const void *zFunctionName,
973 int nArg,
974 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000975 void*,
976 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
977 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
978 void (*xFinal)(sqlite3_context*)
979);
980
981/*
danielk197765904932004-05-26 06:18:37 +0000982** The next routine returns the number of calls to xStep for a particular
983** aggregate function instance. The current call to xStep counts so this
984** routine always returns at least 1.
985*/
986int sqlite3_aggregate_count(sqlite3_context*);
987
danielk19770ffba6b2004-05-24 09:10:10 +0000988/*
drh4f26d6c2004-05-26 23:25:30 +0000989** The next group of routines returns information about parameters to
990** a user-defined function. Function implementations use these routines
991** to access their parameters. These routines are the same as the
992** sqlite3_column_* routines except that these routines take a single
993** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
994** column number.
danielk19770ffba6b2004-05-24 09:10:10 +0000995*/
drhf4479502004-05-27 03:12:53 +0000996const void *sqlite3_value_blob(sqlite3_value*);
997int sqlite3_value_bytes(sqlite3_value*);
998int sqlite3_value_bytes16(sqlite3_value*);
999double sqlite3_value_double(sqlite3_value*);
1000int sqlite3_value_int(sqlite3_value*);
drhefad9992004-06-22 12:13:55 +00001001sqlite_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +00001002const unsigned char *sqlite3_value_text(sqlite3_value*);
1003const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +00001004const void *sqlite3_value_text16le(sqlite3_value*);
1005const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +00001006int sqlite3_value_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +00001007
1008/*
danielk19770ae8b832004-05-25 12:05:56 +00001009** Aggregate functions use the following routine to allocate
1010** a structure for storing their state. The first time this routine
1011** is called for a particular aggregate, a new structure of size nBytes
1012** is allocated, zeroed, and returned. On subsequent calls (for the
1013** same aggregate instance) the same buffer is returned. The implementation
1014** of the aggregate can use the returned buffer to accumulate data.
1015**
1016** The buffer allocated is freed automatically by SQLite.
1017*/
drh4f26d6c2004-05-26 23:25:30 +00001018void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +00001019
1020/*
drhc0f2a012005-07-09 02:39:40 +00001021** The pUserData parameter to the sqlite3_create_function()
1022** routine used to register user functions is available to
1023** the implementation of the function using this call.
danielk19777e18c252004-05-25 11:47:24 +00001024*/
1025void *sqlite3_user_data(sqlite3_context*);
1026
1027/*
danielk1977682f68b2004-06-05 10:22:17 +00001028** The following two functions may be used by scalar user functions to
1029** associate meta-data with argument values. If the same value is passed to
1030** multiple invocations of the user-function during query execution, under
1031** some circumstances the associated meta-data may be preserved. This may
1032** be used, for example, to add a regular-expression matching scalar
1033** function. The compiled version of the regular expression is stored as
1034** meta-data associated with the SQL value passed as the regular expression
1035** pattern.
1036**
1037** Calling sqlite3_get_auxdata() returns a pointer to the meta data
1038** associated with the Nth argument value to the current user function
1039** call, where N is the second parameter. If no meta-data has been set for
1040** that value, then a NULL pointer is returned.
1041**
1042** The sqlite3_set_auxdata() is used to associate meta data with a user
1043** function argument. The third parameter is a pointer to the meta data
1044** to be associated with the Nth user function argument value. The fourth
1045** parameter specifies a 'delete function' that will be called on the meta
1046** data pointer to release it when it is no longer required. If the delete
1047** function pointer is NULL, it is not invoked.
1048**
1049** In practice, meta-data is preserved between function calls for
1050** expressions that are constant at compile time. This includes literal
1051** values and SQL variables.
1052*/
1053void *sqlite3_get_auxdata(sqlite3_context*, int);
1054void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
1055
drha2854222004-06-17 19:04:17 +00001056
1057/*
1058** These are special value for the destructor that is passed in as the
1059** final argument to routines like sqlite3_result_blob(). If the destructor
1060** argument is SQLITE_STATIC, it means that the content pointer is constant
1061** and will never change. It does not need to be destroyed. The
1062** SQLITE_TRANSIENT value means that the content will likely change in
1063** the near future and that SQLite should make its own private copy of
1064** the content before returning.
1065*/
danielk1977d8123362004-06-12 09:25:12 +00001066#define SQLITE_STATIC ((void(*)(void *))0)
1067#define SQLITE_TRANSIENT ((void(*)(void *))-1)
1068
danielk1977682f68b2004-06-05 10:22:17 +00001069/*
drh4f26d6c2004-05-26 23:25:30 +00001070** User-defined functions invoke the following routines in order to
1071** set their return value.
danielk19777e18c252004-05-25 11:47:24 +00001072*/
danielk1977d8123362004-06-12 09:25:12 +00001073void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001074void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +00001075void sqlite3_result_error(sqlite3_context*, const char*, int);
1076void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +00001077void sqlite3_result_int(sqlite3_context*, int);
drhefad9992004-06-22 12:13:55 +00001078void sqlite3_result_int64(sqlite3_context*, sqlite_int64);
drh4f26d6c2004-05-26 23:25:30 +00001079void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +00001080void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
1081void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
1082void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
1083void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001084void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +00001085
drh52619df2004-06-11 17:48:02 +00001086/*
1087** These are the allowed values for the eTextRep argument to
1088** sqlite3_create_collation and sqlite3_create_function.
1089*/
danielk1977466be562004-06-10 02:16:01 +00001090#define SQLITE_UTF8 1
danielk1977dc8453f2004-06-12 00:42:34 +00001091#define SQLITE_UTF16LE 2
1092#define SQLITE_UTF16BE 3
1093#define SQLITE_UTF16 4 /* Use native byte order */
drh52619df2004-06-11 17:48:02 +00001094#define SQLITE_ANY 5 /* sqlite3_create_function only */
danielk1977466be562004-06-10 02:16:01 +00001095
danielk19777cedc8d2004-06-10 10:50:08 +00001096/*
1097** These two functions are used to add new collation sequences to the
1098** sqlite3 handle specified as the first argument.
1099**
1100** The name of the new collation sequence is specified as a UTF-8 string
1101** for sqlite3_create_collation() and a UTF-16 string for
1102** sqlite3_create_collation16(). In both cases the name is passed as the
1103** second function argument.
1104**
1105** The third argument must be one of the constants SQLITE_UTF8,
1106** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1107** routine expects to be passed pointers to strings encoded using UTF-8,
1108** UTF-16 little-endian or UTF-16 big-endian respectively.
1109**
1110** A pointer to the user supplied routine must be passed as the fifth
1111** argument. If it is NULL, this is the same as deleting the collation
1112** sequence (so that SQLite cannot call it anymore). Each time the user
1113** supplied function is invoked, it is passed a copy of the void* passed as
1114** the fourth argument to sqlite3_create_collation() or
1115** sqlite3_create_collation16() as its first parameter.
1116**
1117** The remaining arguments to the user-supplied routine are two strings,
1118** each represented by a [length, data] pair and encoded in the encoding
1119** that was passed as the third argument when the collation sequence was
1120** registered. The user routine should return negative, zero or positive if
1121** the first string is less than, equal to, or greater than the second
1122** string. i.e. (STRING1 - STRING2).
1123*/
danielk19770202b292004-06-09 09:55:16 +00001124int sqlite3_create_collation(
1125 sqlite3*,
1126 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001127 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001128 void*,
1129 int(*xCompare)(void*,int,const void*,int,const void*)
1130);
1131int sqlite3_create_collation16(
1132 sqlite3*,
1133 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001134 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001135 void*,
1136 int(*xCompare)(void*,int,const void*,int,const void*)
1137);
1138
danielk19777cedc8d2004-06-10 10:50:08 +00001139/*
1140** To avoid having to register all collation sequences before a database
1141** can be used, a single callback function may be registered with the
1142** database handle to be called whenever an undefined collation sequence is
1143** required.
1144**
1145** If the function is registered using the sqlite3_collation_needed() API,
1146** then it is passed the names of undefined collation sequences as strings
1147** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1148** are passed as UTF-16 in machine native byte order. A call to either
1149** function replaces any existing callback.
1150**
1151** When the user-function is invoked, the first argument passed is a copy
1152** of the second argument to sqlite3_collation_needed() or
1153** sqlite3_collation_needed16(). The second argument is the database
1154** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1155** SQLITE_UTF16LE, indicating the most desirable form of the collation
1156** sequence function required. The fourth parameter is the name of the
1157** required collation sequence.
1158**
1159** The collation sequence is returned to SQLite by a collation-needed
1160** callback using the sqlite3_create_collation() or
1161** sqlite3_create_collation16() APIs, described above.
1162*/
1163int sqlite3_collation_needed(
1164 sqlite3*,
1165 void*,
1166 void(*)(void*,sqlite3*,int eTextRep,const char*)
1167);
1168int sqlite3_collation_needed16(
1169 sqlite3*,
1170 void*,
1171 void(*)(void*,sqlite3*,int eTextRep,const void*)
1172);
1173
drh2011d5f2004-07-22 02:40:37 +00001174/*
1175** Specify the key for an encrypted database. This routine should be
1176** called right after sqlite3_open().
1177**
1178** The code to implement this API is not available in the public release
1179** of SQLite.
1180*/
1181int sqlite3_key(
1182 sqlite3 *db, /* Database to be rekeyed */
1183 const void *pKey, int nKey /* The key */
1184);
1185
1186/*
1187** Change the key on an open database. If the current database is not
1188** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the
1189** database is decrypted.
1190**
1191** The code to implement this API is not available in the public release
1192** of SQLite.
1193*/
1194int sqlite3_rekey(
1195 sqlite3 *db, /* Database to be rekeyed */
1196 const void *pKey, int nKey /* The new key */
1197);
danielk19770202b292004-06-09 09:55:16 +00001198
drhab3f9fe2004-08-14 17:10:10 +00001199/*
danielk1977600dd0b2005-01-20 01:14:23 +00001200** Sleep for a little while. The second parameter is the number of
1201** miliseconds to sleep for.
1202**
1203** If the operating system does not support sleep requests with
1204** milisecond time resolution, then the time will be rounded up to
1205** the nearest second. The number of miliseconds of sleep actually
1206** requested from the operating system is returned.
danielk1977600dd0b2005-01-20 01:14:23 +00001207*/
1208int sqlite3_sleep(int);
1209
1210/*
drh65efb652005-06-12 22:12:39 +00001211** Return TRUE (non-zero) if the statement supplied as an argument needs
drhd89bd002005-01-22 03:03:54 +00001212** to be recompiled. A statement needs to be recompiled whenever the
1213** execution environment changes in a way that would alter the program
1214** that sqlite3_prepare() generates. For example, if new functions or
1215** collating sequences are registered or if an authorizer function is
1216** added or changed.
1217**
drhd89bd002005-01-22 03:03:54 +00001218*/
1219int sqlite3_expired(sqlite3_stmt*);
1220
1221/*
drhf8db1bc2005-04-22 02:38:37 +00001222** Move all bindings from the first prepared statement over to the second.
1223** This routine is useful, for example, if the first prepared statement
1224** fails with an SQLITE_SCHEMA error. The same SQL can be prepared into
1225** the second prepared statement then all of the bindings transfered over
1226** to the second statement before the first statement is finalized.
drhf8db1bc2005-04-22 02:38:37 +00001227*/
1228int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*);
1229
1230/*
tpoindex9a09a3c2004-12-20 19:01:32 +00001231** If the following global variable is made to point to a
drhab3f9fe2004-08-14 17:10:10 +00001232** string which is the name of a directory, then all temporary files
1233** created by SQLite will be placed in that directory. If this variable
1234** is NULL pointer, then SQLite does a search for an appropriate temporary
1235** file directory.
1236**
danielk19776b456a22005-03-21 04:04:02 +00001237** Once sqlite3_open() has been called, changing this variable will invalidate
1238** the current temporary database, if any.
drhab3f9fe2004-08-14 17:10:10 +00001239*/
tpoindex9a09a3c2004-12-20 19:01:32 +00001240extern char *sqlite3_temp_directory;
drhab3f9fe2004-08-14 17:10:10 +00001241
danielk19776b456a22005-03-21 04:04:02 +00001242/*
1243** This function is called to recover from a malloc() failure that occured
1244** within the SQLite library. Normally, after a single malloc() fails the
1245** library refuses to function (all major calls return SQLITE_NOMEM).
drh9a7e6082005-03-31 22:26:19 +00001246** This function restores the library state so that it can be used again.
danielk19776b456a22005-03-21 04:04:02 +00001247**
1248** All existing statements (sqlite3_stmt pointers) must be finalized or
1249** reset before this call is made. Otherwise, SQLITE_BUSY is returned.
1250** If any in-memory databases are in use, either as a main or TEMP
1251** database, SQLITE_ERROR is returned. In either of these cases, the
1252** library is not reset and remains unusable.
1253**
1254** This function is *not* threadsafe. Calling this from within a threaded
1255** application when threads other than the caller have used SQLite is
1256** dangerous and will almost certainly result in malfunctions.
1257**
1258** This functionality can be omitted from a build by defining the
1259** SQLITE_OMIT_GLOBALRECOVER at compile time.
1260*/
drhd9cb6ac2005-10-20 07:28:17 +00001261int sqlite3_global_recover(void);
danielk19776b456a22005-03-21 04:04:02 +00001262
drh3e1d8e62005-05-26 16:23:34 +00001263/*
1264** Test to see whether or not the database connection is in autocommit
1265** mode. Return TRUE if it is and FALSE if not. Autocommit mode is on
1266** by default. Autocommit is disabled by a BEGIN statement and reenabled
1267** by the next COMMIT or ROLLBACK.
drh3e1d8e62005-05-26 16:23:34 +00001268*/
1269int sqlite3_get_autocommit(sqlite3*);
1270
drh51942bc2005-06-12 22:01:42 +00001271/*
1272** Return the sqlite3* database handle to which the prepared statement given
1273** in the argument belongs. This is the same database handle that was
1274** the first argument to the sqlite3_prepare() that was used to create
1275** the statement in the first place.
1276*/
1277sqlite3 *sqlite3_db_handle(sqlite3_stmt*);
drh3e1d8e62005-05-26 16:23:34 +00001278
drhb37df7b2005-10-13 02:09:49 +00001279/*
danielk19777ddad962005-12-12 06:53:03 +00001280** Place a "soft" limit on the amount of heap memory that may be allocated by
1281** SQLite within the current thread. If an internal allocation is requested
1282** that would exceed the specified limit, sqlite3_release_memory() is invoked
1283** one or more times to free up some space before the allocation is made.
1284**
1285** The limit is called "soft", because if sqlite3_release_memory() cannot free
1286** sufficient memory to prevent the limit from being exceeded, the memory is
1287** allocated anyway and the current operation proceeds.
1288**
1289** This function is only available if the library was compiled without the
danielk197713f72992005-12-18 08:51:22 +00001290** SQLITE_OMIT_MEMORY_MANAGEMENT option set.
danielk19777ddad962005-12-12 06:53:03 +00001291*/
danielk19775591df52005-12-20 09:19:37 +00001292void sqlite3_soft_heap_limit(sqlite_int64);
danielk19777ddad962005-12-12 06:53:03 +00001293
danielk197794eb6a12005-12-15 15:22:08 +00001294/*
1295** Register a callback function with the database connection identified by the
1296** first argument to be invoked whenever a row is updated, inserted or deleted.
1297** Any callback set by a previous call to this function for the same
1298** database connection is overridden.
1299**
1300** The second argument is a pointer to the function to invoke when a
1301** row is updated, inserted or deleted. The first argument to the callback is
1302** a copy of the third argument to sqlite3_update_hook. The second callback
1303** argument is one of SQLITE_INSERT, SQLITE_DELETE or SQLITE_UPDATE, depending
1304** on the operation that caused the callback to be invoked. The third and
1305** fourth arguments to the callback contain pointers to the database and
1306** table name containing the affected row. The final callback parameter is
1307** the rowid of the row. In the case of an update, this is the rowid after
1308** the update takes place.
1309**
1310** The update hook is not invoked when internal system tables are
1311** modified (i.e. sqlite_master and sqlite_sequence).
danielk197771fd80b2005-12-16 06:54:01 +00001312**
1313** If another function was previously registered, its pArg value is returned.
1314** Otherwise NULL is returned.
danielk197794eb6a12005-12-15 15:22:08 +00001315*/
danielk197771fd80b2005-12-16 06:54:01 +00001316void *sqlite3_update_hook(
danielk197794eb6a12005-12-15 15:22:08 +00001317 sqlite3*,
1318 void(*)(void *,int ,char const *,char const *,sqlite_int64),
1319 void*
1320);
danielk197713a68c32005-12-15 10:11:30 +00001321
danielk1977f3f06bb2005-12-16 15:24:28 +00001322/*
1323** Register a callback to be invoked whenever a transaction is rolled
1324** back.
1325**
1326** The new callback function overrides any existing rollback-hook
1327** callback. If there was an existing callback, then it's pArg value
1328** (the third argument to sqlite3_rollback_hook() when it was registered)
1329** is returned. Otherwise, NULL is returned.
1330**
1331** For the purposes of this API, a transaction is said to have been
1332** rolled back if an explicit "ROLLBACK" statement is executed, or
1333** an error or constraint causes an implicit rollback to occur. The
1334** callback is not invoked if a transaction is automatically rolled
1335** back because the database connection is closed.
1336*/
danielk197771fd80b2005-12-16 06:54:01 +00001337void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*);
1338
danielk19770190d1d2005-12-19 14:18:11 +00001339int sqlite3_release_memory(int);
1340
danielk19777ddad962005-12-12 06:53:03 +00001341/*
drhb37df7b2005-10-13 02:09:49 +00001342** Undo the hack that converts floating point types to integer for
1343** builds on processors without floating point support.
1344*/
1345#ifdef SQLITE_OMIT_FLOATING_POINT
1346# undef double
1347#endif
1348
drh382c0242001-10-06 16:33:02 +00001349#ifdef __cplusplus
1350} /* End of the 'extern "C"' block */
1351#endif
danielk19774adee202004-05-08 08:23:19 +00001352#endif