blob: bad399e36642fc3216c887ed51070a7f569f7632 [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**
danielk19772097e942004-11-20 06:05:56 +000015** @(#) $Id: sqlite.h.in,v 1.123 2004/11/20 06:05:56 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
33#else
34# define SQLITE_VERSION "--VERS--"
35#endif
drhb86ccfb2003-01-28 23:13:10 +000036
37/*
drhb217a572000-08-22 13:40:18 +000038** The version string is also compiled into the library so that a program
39** can check to make sure that the lib*.a file and the *.h file are from
drh6f3a3ef2004-08-28 18:21:21 +000040** the same version. The sqlite3_libversion() function returns a pointer
41** to the sqlite3_version variable - useful in DLLs which cannot access
42** global variables.
drhb217a572000-08-22 13:40:18 +000043*/
danielk19776f8a5032004-05-10 10:34:51 +000044extern const char sqlite3_version[];
drha3f70cb2004-09-30 14:24:50 +000045const char *sqlite3_libversion(void);
drh303aaa72000-08-17 10:22:34 +000046
47/*
drh75897232000-05-29 14:26:00 +000048** Each open sqlite database is represented by an instance of the
49** following opaque structure.
50*/
drh9bb575f2004-09-06 17:24:11 +000051typedef struct sqlite3 sqlite3;
danielk197765904932004-05-26 06:18:37 +000052
drh75897232000-05-29 14:26:00 +000053
54/*
drhefad9992004-06-22 12:13:55 +000055** Some compilers do not support the "long long" datatype. So we have
56** to do a typedef that for 64-bit integers that depends on what compiler
57** is being used.
58*/
59#if defined(_MSC_VER) || defined(__BORLANDC__)
60 typedef __int64 sqlite_int64;
drh1211de32004-07-26 12:24:22 +000061 typedef unsigned __int64 sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000062#else
63 typedef long long int sqlite_int64;
drh1211de32004-07-26 12:24:22 +000064 typedef unsigned long long int sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000065#endif
66
67
68/*
drh75897232000-05-29 14:26:00 +000069** A function to close the database.
70**
71** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +000072** returned from sqlite3_open() and the corresponding database will by closed.
danielk197796d81f92004-06-19 03:33:57 +000073**
74** All SQL statements prepared using sqlite3_prepare() or
75** sqlite3_prepare16() must be deallocated using sqlite3_finalize() before
76** this routine is called. Otherwise, SQLITE_BUSY is returned and the
77** database connection remains open.
drh75897232000-05-29 14:26:00 +000078*/
danielk1977f9d64d22004-06-19 08:18:07 +000079int sqlite3_close(sqlite3 *);
drh75897232000-05-29 14:26:00 +000080
81/*
82** The type for a callback function.
83*/
drh12057d52004-09-06 17:34:12 +000084typedef int (*sqlite3_callback)(void*,int,char**, char**);
drh75897232000-05-29 14:26:00 +000085
86/*
87** A function to executes one or more statements of SQL.
88**
89** If one or more of the SQL statements are queries, then
90** the callback function specified by the 3rd parameter is
91** invoked once for each row of the query result. This callback
92** should normally return 0. If the callback returns a non-zero
93** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +000094** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +000095**
96** The 4th parameter is an arbitrary pointer that is passed
97** to the callback function as its first parameter.
98**
99** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +0000100** columns in the query result. The 3rd parameter to the callback
101** is an array of strings holding the values for each column.
102** The 4th parameter to the callback is an array of strings holding
103** the names of each column.
drh75897232000-05-29 14:26:00 +0000104**
105** The callback function may be NULL, even for queries. A NULL
106** callback is not an error. It just means that no callback
107** will be invoked.
108**
109** If an error occurs while parsing or evaluating the SQL (but
110** not while executing the callback) then an appropriate error
111** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +0000112** *errmsg is made to point to that message. The calling function
113** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +0000114** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +0000115** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +0000116**
117** The return value is is SQLITE_OK if there are no errors and
118** some other return code if there is an error. The particular
119** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +0000120**
121** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000122** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +0000123** behavior can be modified somewhat using the sqlite3_busy_handler()
124** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000125*/
danielk19776f8a5032004-05-10 10:34:51 +0000126int sqlite3_exec(
drh12057d52004-09-06 17:34:12 +0000127 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000128 const char *sql, /* SQL to be executed */
drh12057d52004-09-06 17:34:12 +0000129 sqlite3_callback, /* Callback function */
drh75897232000-05-29 14:26:00 +0000130 void *, /* 1st argument to callback function */
131 char **errmsg /* Error msg written here */
132);
133
drh58b95762000-06-02 01:17:37 +0000134/*
danielk19776f8a5032004-05-10 10:34:51 +0000135** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000136*/
drh717e6402001-09-27 03:22:32 +0000137#define SQLITE_OK 0 /* Successful result */
138#define SQLITE_ERROR 1 /* SQL error or missing database */
139#define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */
140#define SQLITE_PERM 3 /* Access permission denied */
141#define SQLITE_ABORT 4 /* Callback routine requested an abort */
142#define SQLITE_BUSY 5 /* The database file is locked */
143#define SQLITE_LOCKED 6 /* A table in the database is locked */
144#define SQLITE_NOMEM 7 /* A malloc() failed */
145#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000146#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000147#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
148#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
149#define SQLITE_NOTFOUND 12 /* (Internal Only) Table or record not found */
150#define SQLITE_FULL 13 /* Insertion failed because database is full */
151#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
152#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000153#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000154#define SQLITE_SCHEMA 17 /* The database schema changed */
155#define SQLITE_TOOBIG 18 /* Too much data for one row of a table */
156#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000157#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000158#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000159#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000160#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000161#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000162#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000163#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000164#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
165#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh717e6402001-09-27 03:22:32 +0000166
drhaf9ff332002-01-16 21:00:27 +0000167/*
168** Each entry in an SQLite table has a unique integer key. (The key is
169** the value of the INTEGER PRIMARY KEY column if there is such a column,
170** otherwise the key is generated at random. The unique key is always
171** available as the ROWID, OID, or _ROWID_ column.) The following routine
172** returns the integer key of the most recent insert in the database.
173**
174** This function is similar to the mysql_insert_id() function from MySQL.
175*/
drhefad9992004-06-22 12:13:55 +0000176sqlite_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000177
drhc8d30ac2002-04-12 10:08:59 +0000178/*
179** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000180** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000181**
182** All changes are counted, even if they were later undone by a
183** ROLLBACK or ABORT. Except, changes associated with creating and
184** dropping tables are not counted.
185**
danielk19776f8a5032004-05-10 10:34:51 +0000186** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000187** in the inner, recursive call are counted together with the changes
188** in the outer call.
189**
190** SQLite implements the command "DELETE FROM table" without a WHERE clause
191** by dropping and recreating the table. (This is much faster than going
192** through and deleting individual elements form the table.) Because of
193** this optimization, the change count for "DELETE FROM table" will be
194** zero regardless of the number of elements that were originally in the
195** table. To get an accurate count of the number of rows deleted, use
196** "DELETE FROM table WHERE 1" instead.
197*/
danielk1977f9d64d22004-06-19 08:18:07 +0000198int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000199
rdcf146a772004-02-25 22:51:06 +0000200/*
danielk1977b28af712004-06-21 06:50:26 +0000201** This function returns the number of database rows that have been
202** modified by INSERT, UPDATE or DELETE statements since the database handle
203** was opened. This includes UPDATE, INSERT and DELETE statements executed
204** as part of trigger programs. All changes are counted as soon as the
205** statement that makes them is completed (when the statement handle is
206** passed to sqlite3_reset() or sqlite_finalise()).
rdcf146a772004-02-25 22:51:06 +0000207**
208** SQLite implements the command "DELETE FROM table" without a WHERE clause
209** by dropping and recreating the table. (This is much faster than going
210** through and deleting individual elements form the table.) Because of
211** this optimization, the change count for "DELETE FROM table" will be
212** zero regardless of the number of elements that were originally in the
213** table. To get an accurate count of the number of rows deleted, use
214** "DELETE FROM table WHERE 1" instead.
rdcf146a772004-02-25 22:51:06 +0000215*/
danielk1977b28af712004-06-21 06:50:26 +0000216int sqlite3_total_changes(sqlite3*);
217
drh4c504392000-10-16 22:06:40 +0000218/* This function causes any pending database operation to abort and
219** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000220** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000221** or Ctrl-C where the user wants a long query operation to halt
222** immediately.
223*/
danielk1977f9d64d22004-06-19 08:18:07 +0000224void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000225
drheec553b2000-06-02 01:51:20 +0000226
danielk197761de0d12004-05-27 23:56:16 +0000227/* These functions return true if the given input string comprises
228** one or more complete SQL statements. For the sqlite3_complete() call,
229** the parameter must be a nul-terminated UTF-8 string. For
230** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
231** is required.
drh75897232000-05-29 14:26:00 +0000232**
233** The algorithm is simple. If the last token other than spaces
234** and comments is a semicolon, then return true. otherwise return
235** false.
236*/
danielk19776f8a5032004-05-10 10:34:51 +0000237int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000238int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000239
drh2dfbbca2000-07-28 14:32:48 +0000240/*
241** This routine identifies a callback function that is invoked
242** whenever an attempt is made to open a database table that is
243** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000244** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000245** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000246** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000247** second argument is the name of the locked table and the third
248** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000249** busy callback returns 0, then sqlite3_exec() immediately returns
250** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000251** tries to open the table again and the cycle repeats.
252**
253** The default busy callback is NULL.
254**
255** Sqlite is re-entrant, so the busy handler may start a new query.
256** (It is not clear why anyone would every want to do this, but it
257** is allowed, in theory.) But the busy handler may not close the
258** database. Closing the database from a busy handler will delete
259** data structures out from under the executing query and will
260** probably result in a coredump.
261*/
danielk1977f9d64d22004-06-19 08:18:07 +0000262int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000263
264/*
265** This routine sets a busy handler that sleeps for a while when a
266** table is locked. The handler will sleep multiple times until
267** at least "ms" milleseconds of sleeping have been done. After
268** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000269** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000270**
271** Calling this routine with an argument less than or equal to zero
272** turns off all busy handlers.
273*/
danielk1977f9d64d22004-06-19 08:18:07 +0000274int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000275
drhe3710332000-09-29 13:30:53 +0000276/*
danielk19776f8a5032004-05-10 10:34:51 +0000277** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000278** Instead of invoking a user-supplied callback for each row of the
279** result, this routine remembers each row of the result in memory
280** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000281** query has finished.
282**
283** As an example, suppose the query result where this table:
284**
285** Name | Age
286** -----------------------
287** Alice | 43
288** Bob | 28
289** Cindy | 21
290**
291** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000292** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000293**
294** azResult[0] = "Name";
295** azResult[1] = "Age";
296** azResult[2] = "Alice";
297** azResult[3] = "43";
298** azResult[4] = "Bob";
299** azResult[5] = "28";
300** azResult[6] = "Cindy";
301** azResult[7] = "21";
302**
303** Notice that there is an extra row of data containing the column
304** headers. But the *nrow return value is still 3. *ncolumn is
305** set to 2. In general, the number of values inserted into azResult
306** will be ((*nrow) + 1)*(*ncolumn).
307**
308** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000309** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000310** release the memory that was malloc-ed. Because of the way the
311** malloc() happens, the calling function must not try to call
danielk19776f8a5032004-05-10 10:34:51 +0000312** malloc() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000313** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000314**
danielk19776f8a5032004-05-10 10:34:51 +0000315** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000316*/
danielk19776f8a5032004-05-10 10:34:51 +0000317int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000318 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000319 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000320 char ***resultp, /* Result written to a char *[] that this points to */
321 int *nrow, /* Number of result rows written here */
322 int *ncolumn, /* Number of result columns written here */
323 char **errmsg /* Error msg written here */
324);
325
326/*
danielk19776f8a5032004-05-10 10:34:51 +0000327** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000328*/
danielk19776f8a5032004-05-10 10:34:51 +0000329void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000330
drha18c5682000-10-08 22:20:57 +0000331/*
drh4f26d6c2004-05-26 23:25:30 +0000332** The following routines are variants of the "sprintf()" from the
333** standard C library. The resulting string is written into memory
334** obtained from malloc() so that there is never a possiblity of buffer
335** overflow. These routines also implement some additional formatting
336** options that are useful for constructing SQL statements.
337**
338** The strings returned by these routines should be freed by calling
339** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000340**
341** All of the usual printf formatting options apply. In addition, there
342** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000343** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000344** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000345** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000346** the string.
347**
348** For example, so some string variable contains text as follows:
349**
350** char *zText = "It's a happy day!";
351**
352** We can use this text in an SQL statement as follows:
353**
danielk19776f8a5032004-05-10 10:34:51 +0000354** sqlite3_exec_printf(db, "INSERT INTO table VALUES('%q')",
drha18c5682000-10-08 22:20:57 +0000355** callback1, 0, 0, zText);
356**
357** Because the %q format string is used, the '\'' character in zText
358** is escaped and the SQL generated is as follows:
359**
360** INSERT INTO table1 VALUES('It''s a happy day!')
361**
362** This is correct. Had we used %s instead of %q, the generated SQL
363** would have looked like this:
364**
365** INSERT INTO table1 VALUES('It's a happy day!');
366**
367** This second example is an SQL syntax error. As a general rule you
368** should always use %q instead of %s when inserting text into a string
369** literal.
370*/
danielk19776f8a5032004-05-10 10:34:51 +0000371char *sqlite3_mprintf(const char*,...);
372char *sqlite3_vmprintf(const char*, va_list);
drh4f26d6c2004-05-26 23:25:30 +0000373void sqlite3_free(char *z);
drhfeac5f82004-08-01 00:10:45 +0000374char *sqlite3_snprintf(int,char*,const char*, ...);
drh5191b7e2002-03-08 02:12:00 +0000375
drh1211de32004-07-26 12:24:22 +0000376#ifndef SQLITE_OMIT_AUTHORIZATION
drh5191b7e2002-03-08 02:12:00 +0000377/*
drhed6c8672003-01-12 18:02:16 +0000378** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000379** callback is invoked (at compile-time, not at run-time) for each
380** attempt to access a column of a table in the database. The callback
381** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
382** SQL statement should be aborted with an error and SQLITE_IGNORE
383** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000384*/
danielk19776f8a5032004-05-10 10:34:51 +0000385int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000386 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000387 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000388 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000389);
drh1211de32004-07-26 12:24:22 +0000390#endif
drhed6c8672003-01-12 18:02:16 +0000391
392/*
393** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000394** be one of the values below. These values signify what kind of operation
395** is to be authorized. The 3rd and 4th parameters to the authorization
396** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000397** codes is used as the second parameter. The 5th parameter is the name
398** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000399** is the name of the inner-most trigger or view that is responsible for
400** the access attempt or NULL if this access attempt is directly from
401** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000402**
403** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000404*/
drh77ad4e42003-01-14 02:49:27 +0000405#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000406#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
407#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
408#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
409#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000410#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000411#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000412#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000413#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
414#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000415#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000416#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000417#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000418#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000419#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000420#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000421#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000422#define SQLITE_DROP_VIEW 17 /* View Name NULL */
423#define SQLITE_INSERT 18 /* Table Name NULL */
424#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
425#define SQLITE_READ 20 /* Table Name Column Name */
426#define SQLITE_SELECT 21 /* NULL NULL */
427#define SQLITE_TRANSACTION 22 /* NULL NULL */
428#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000429#define SQLITE_ATTACH 24 /* Filename NULL */
430#define SQLITE_DETACH 25 /* Database Name NULL */
danielk19771c8c23c2004-11-12 15:53:37 +0000431#define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */
drh81e293b2003-06-06 19:00:42 +0000432
drhed6c8672003-01-12 18:02:16 +0000433
434/*
435** The return value of the authorization function should be one of the
436** following constants:
437*/
438/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
439#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
440#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
441
442/*
danielk19776f8a5032004-05-10 10:34:51 +0000443** Register a function that is called at every invocation of sqlite3_exec()
danielk19774ad17132004-05-21 01:47:26 +0000444** or sqlite3_prepare(). This function can be used (for example) to generate
drhb86ccfb2003-01-28 23:13:10 +0000445** a log file of all SQL executed against a database.
drh18de4822003-01-16 16:28:53 +0000446*/
danielk1977f9d64d22004-06-19 08:18:07 +0000447void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh18de4822003-01-16 16:28:53 +0000448
danielk1977348bb5d2003-10-18 09:37:26 +0000449/*
450** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000451** is invoked periodically during long running calls to sqlite3_exec(),
danielk19772097e942004-11-20 06:05:56 +0000452** sqlite3_step() and sqlite3_get_table(). An example use for this API is to
453** keep a GUI updated during a large query.
danielk1977348bb5d2003-10-18 09:37:26 +0000454**
455** The progress callback is invoked once for every N virtual machine opcodes,
456** where N is the second argument to this function. The progress callback
457** itself is identified by the third argument to this function. The fourth
458** argument to this function is a void pointer passed to the progress callback
459** function each time it is invoked.
460**
danielk19776f8a5032004-05-10 10:34:51 +0000461** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000462** in less than N opcodes being executed, then the progress callback is not
463** invoked.
464**
danielk1977348bb5d2003-10-18 09:37:26 +0000465** To remove the progress callback altogether, pass NULL as the third
466** argument to this function.
467**
468** If the progress callback returns a result other than 0, then the current
469** query is immediately terminated and any database changes rolled back. If the
470** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000471** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000472**
473******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000474*/
danielk1977f9d64d22004-06-19 08:18:07 +0000475void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000476
drhaa940ea2004-01-15 02:44:03 +0000477/*
478** Register a callback function to be invoked whenever a new transaction
479** is committed. The pArg argument is passed through to the callback.
480** callback. If the callback function returns non-zero, then the commit
481** is converted into a rollback.
482**
483** If another function was previously registered, its pArg value is returned.
484** Otherwise NULL is returned.
485**
486** Registering a NULL function disables the callback.
487**
488******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
489*/
danielk1977f9d64d22004-06-19 08:18:07 +0000490void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000491
drh22fbcb82004-02-01 01:22:50 +0000492/*
drh4f26d6c2004-05-26 23:25:30 +0000493** Open the sqlite database file "filename". The "filename" is UTF-8
494** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
495** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
496** if an error occurs. If the database is opened (or created) successfully,
497** then SQLITE_OK is returned. Otherwise an error code is returned. The
498** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
499** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000500**
drh4f26d6c2004-05-26 23:25:30 +0000501** If the database file does not exist, then a new database is created.
502** The encoding for the database is UTF-8 if sqlite3_open() is called and
503** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000504**
505** Whether or not an error occurs when it is opened, resources associated
506** with the sqlite3* handle should be released by passing it to
507** sqlite3_close() when it is no longer required.
508*/
509int sqlite3_open(
510 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000511 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000512);
danielk197765904932004-05-26 06:18:37 +0000513int sqlite3_open16(
514 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000515 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000516);
danielk1977295ba552004-05-19 10:34:51 +0000517
danielk197765904932004-05-26 06:18:37 +0000518/*
519** Return the error code for the most recent sqlite3_* API call associated
520** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
521** API call was successful.
522**
523** Calls to many sqlite3_* functions set the error code and string returned
524** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
525** (overwriting the previous values). Note that calls to sqlite3_errcode(),
526** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
527** results of future invocations.
528**
529** Assuming no other intervening sqlite3_* API calls are made, the error
530** code returned by this function is associated with the same error as
531** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
532*/
533int sqlite3_errcode(sqlite3 *db);
534
535/*
536** Return a pointer to a UTF-8 encoded string describing in english the
537** error condition for the most recent sqlite3_* API call. The returned
538** string is always terminated by an 0x00 byte.
539**
540** The string "not an error" is returned when the most recent API call was
541** successful.
542*/
543const char *sqlite3_errmsg(sqlite3*);
544
545/*
546** Return a pointer to a UTF-16 native byte order encoded string describing
547** in english the error condition for the most recent sqlite3_* API call.
548** The returned string is always terminated by a pair of 0x00 bytes.
549**
550** The string "not an error" is returned when the most recent API call was
551** successful.
552*/
553const void *sqlite3_errmsg16(sqlite3*);
554
555/*
556** An instance of the following opaque structure is used to represent
557** a compiled SQL statment.
558*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000559typedef struct sqlite3_stmt sqlite3_stmt;
560
danielk1977e3209e42004-05-20 01:40:18 +0000561/*
danielk197765904932004-05-26 06:18:37 +0000562** To execute an SQL query, it must first be compiled into a byte-code
563** program using one of the following routines. The only difference between
564** them is that the second argument, specifying the SQL statement to
565** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
566** function and UTF-16 for sqlite3_prepare16().
567**
568** The first parameter "db" is an SQLite database handle. The second
569** parameter "zSql" is the statement to be compiled, encoded as either
570** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
571** than zero, then zSql is read up to the first nul terminator. If
572** "nBytes" is not less than zero, then it is the length of the string zSql
573** in bytes (not characters).
574**
575** *pzTail is made to point to the first byte past the end of the first
576** SQL statement in zSql. This routine only compiles the first statement
577** in zSql, so *pzTail is left pointing to what remains uncompiled.
578**
579** *ppStmt is left pointing to a compiled SQL statement that can be
580** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
581** set to NULL. If the input text contained no SQL (if the input is and
582** empty string or a comment) then *ppStmt is set to NULL.
583**
584** On success, SQLITE_OK is returned. Otherwise an error code is returned.
585*/
586int sqlite3_prepare(
587 sqlite3 *db, /* Database handle */
588 const char *zSql, /* SQL statement, UTF-8 encoded */
589 int nBytes, /* Length of zSql in bytes. */
590 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
591 const char **pzTail /* OUT: Pointer to unused portion of zSql */
592);
593int sqlite3_prepare16(
594 sqlite3 *db, /* Database handle */
595 const void *zSql, /* SQL statement, UTF-16 encoded */
596 int nBytes, /* Length of zSql in bytes. */
597 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
598 const void **pzTail /* OUT: Pointer to unused portion of zSql */
599);
600
601/*
drhf4479502004-05-27 03:12:53 +0000602** Pointers to the following two opaque structures are used to communicate
603** with the implementations of user-defined functions.
604*/
605typedef struct sqlite3_context sqlite3_context;
606typedef struct Mem sqlite3_value;
607
608/*
drh4f26d6c2004-05-26 23:25:30 +0000609** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
610** one or more literals can be replace by a wildcard "?" or ":N:" where
611** N is an integer. These value of these wildcard literals can be set
612** using the routines listed below.
613**
614** In every case, the first parameter is a pointer to the sqlite3_stmt
615** structure returned from sqlite3_prepare(). The second parameter is the
616** index of the wildcard. The first "?" has an index of 1. ":N:" wildcards
617** use the index N.
618**
drh900dfba2004-07-21 15:21:36 +0000619** The fifth parameter to sqlite3_bind_blob(), sqlite3_bind_text(), and
620** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or
621** text after SQLite has finished with it. If the fifth argument is the
622** special value SQLITE_STATIC, then the library assumes that the information
623** is in static, unmanaged space and does not need to be freed. If the
624** fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its
625** own private copy of the data.
drh4f26d6c2004-05-26 23:25:30 +0000626**
627** The sqlite3_bind_* routine must be called before sqlite3_step() after
628** an sqlite3_prepare() or sqlite3_reset(). Unbound wildcards are interpreted
629** as NULL.
630*/
danielk1977d8123362004-06-12 09:25:12 +0000631int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000632int sqlite3_bind_double(sqlite3_stmt*, int, double);
633int sqlite3_bind_int(sqlite3_stmt*, int, int);
drhefad9992004-06-22 12:13:55 +0000634int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64);
drhf4479502004-05-27 03:12:53 +0000635int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000636int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
637int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000638int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000639
640/*
drh75f6a032004-07-15 14:15:00 +0000641** Return the number of wildcards in a compiled SQL statement. This
642** routine was added to support DBD::SQLite.
drh75f6a032004-07-15 14:15:00 +0000643*/
644int sqlite3_bind_parameter_count(sqlite3_stmt*);
645
646/*
drh895d7472004-08-20 16:02:39 +0000647** Return the name of the i-th parameter. Ordinary wildcards "?" are
drhfa6bc002004-09-07 16:19:52 +0000648** nameless and a NULL is returned. For wildcards of the form :N or
drh895d7472004-08-20 16:02:39 +0000649** $vvvv the complete text of the wildcard is returned.
650** NULL is returned if the index is out of range.
651*/
652const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
653
654/*
drhfa6bc002004-09-07 16:19:52 +0000655** Return the index of a parameter with the given name. The name
656** must match exactly. If no parameter with the given name is found,
657** return 0.
658*/
659int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
660
661/*
danielk197765904932004-05-26 06:18:37 +0000662** Return the number of columns in the result set returned by the compiled
663** SQL statement. This routine returns 0 if pStmt is an SQL statement
664** that does not return data (for example an UPDATE).
665*/
666int sqlite3_column_count(sqlite3_stmt *pStmt);
667
668/*
669** The first parameter is a compiled SQL statement. This function returns
670** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000671** second function parameter. The string returned is UTF-8 for
672** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000673*/
674const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000675const void *sqlite3_column_name16(sqlite3_stmt*,int);
676
677/*
678** The first parameter is a compiled SQL statement. If this statement
679** is a SELECT statement, the Nth column of the returned result set
680** of the SELECT is a table column then the declared type of the table
681** column is returned. If the Nth column of the result set is not at table
682** column, then a NULL pointer is returned. The returned string is always
683** UTF-8 encoded. For example, in the database schema:
684**
685** CREATE TABLE t1(c1 VARIANT);
686**
687** And the following statement compiled:
688**
689** SELECT c1 + 1, 0 FROM t1;
690**
691** Then this routine would return the string "VARIANT" for the second
692** result column (i==1), and a NULL pointer for the first result column
693** (i==0).
694*/
695const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
696
697/*
698** The first parameter is a compiled SQL statement. If this statement
699** is a SELECT statement, the Nth column of the returned result set
700** of the SELECT is a table column then the declared type of the table
701** column is returned. If the Nth column of the result set is not at table
702** column, then a NULL pointer is returned. The returned string is always
703** UTF-16 encoded. For example, in the database schema:
704**
drh4f26d6c2004-05-26 23:25:30 +0000705** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000706**
707** And the following statement compiled:
708**
709** SELECT c1 + 1, 0 FROM t1;
710**
drh4f26d6c2004-05-26 23:25:30 +0000711** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000712** result column (i==1), and a NULL pointer for the first result column
713** (i==0).
714*/
715const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
716
danielk1977106bb232004-05-21 10:08:53 +0000717/*
718** After an SQL query has been compiled with a call to either
719** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
720** called one or more times to execute the statement.
721**
722** The return value will be either SQLITE_BUSY, SQLITE_DONE,
723** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
724**
725** SQLITE_BUSY means that the database engine attempted to open
726** a locked database and there is no busy callback registered.
727** Call sqlite3_step() again to retry the open.
728**
729** SQLITE_DONE means that the statement has finished executing
730** successfully. sqlite3_step() should not be called again on this virtual
731** machine.
732**
733** If the SQL statement being executed returns any data, then
734** SQLITE_ROW is returned each time a new row of data is ready
735** for processing by the caller. The values may be accessed using
736** the sqlite3_column_*() functions described below. sqlite3_step()
737** is called again to retrieve the next row of data.
738**
739** SQLITE_ERROR means that a run-time error (such as a constraint
740** violation) has occurred. sqlite3_step() should not be called again on
741** the VM. More information may be found by calling sqlite3_errmsg().
742**
743** SQLITE_MISUSE means that the this routine was called inappropriately.
744** Perhaps it was called on a virtual machine that had already been
745** finalized or on one that had previously returned SQLITE_ERROR or
746** SQLITE_DONE. Or it could be the case the the same database connection
747** is being used simulataneously by two or more threads.
748*/
danielk197717240fd2004-05-26 00:07:25 +0000749int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000750
danielk1977106bb232004-05-21 10:08:53 +0000751/*
752** Return the number of values in the current row of the result set.
753**
754** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
755** will return the same value as the sqlite3_column_count() function.
756** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
757** error code, or before sqlite3_step() has been called on a
758** compiled SQL statement, this routine returns zero.
759*/
danielk197793d46752004-05-23 13:30:58 +0000760int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000761
drh4f26d6c2004-05-26 23:25:30 +0000762/*
763** Values are stored in the database in one of the following fundamental
764** types.
765*/
drh9c054832004-05-31 18:51:57 +0000766#define SQLITE_INTEGER 1
767#define SQLITE_FLOAT 2
drh1e284f42004-10-06 15:52:01 +0000768/* #define SQLITE_TEXT 3 // See below */
drh9c054832004-05-31 18:51:57 +0000769#define SQLITE_BLOB 4
770#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000771
danielk1977106bb232004-05-21 10:08:53 +0000772/*
drh1e284f42004-10-06 15:52:01 +0000773** SQLite version 2 defines SQLITE_TEXT differently. To allow both
774** version 2 and version 3 to be included, undefine them both if a
775** conflict is seen. Define SQLITE3_TEXT to be the version 3 value.
776*/
777#ifdef SQLITE_TEXT
778# undef SQLITE_TEXT
779#else
780# define SQLITE_TEXT 3
781#endif
782#define SQLITE3_TEXT 3
783
784/*
drh4f26d6c2004-05-26 23:25:30 +0000785** The next group of routines returns information about the information
786** in a single column of the current result row of a query. In every
787** case the first parameter is a pointer to the SQL statement that is being
788** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
789** the second argument is the index of the column for which information
790** should be returned. iCol is zero-indexed. The left-most column as an
791** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000792**
drh4f26d6c2004-05-26 23:25:30 +0000793** If the SQL statement is not currently point to a valid row, or if the
794** the colulmn index is out of range, the result is undefined.
795**
796** These routines attempt to convert the value where appropriate. For
797** example, if the internal representation is FLOAT and a text result
798** is requested, sprintf() is used internally to do the conversion
799** automatically. The following table details the conversions that
800** are applied:
801**
802** Internal Type Requested Type Conversion
803** ------------- -------------- --------------------------
804** NULL INTEGER Result is 0
805** NULL FLOAT Result is 0.0
806** NULL TEXT Result is an empty string
807** NULL BLOB Result is a zero-length BLOB
808** INTEGER FLOAT Convert from integer to float
809** INTEGER TEXT ASCII rendering of the integer
810** INTEGER BLOB Same as for INTEGER->TEXT
811** FLOAT INTEGER Convert from float to integer
812** FLOAT TEXT ASCII rendering of the float
813** FLOAT BLOB Same as FLOAT->TEXT
814** TEXT INTEGER Use atoi()
815** TEXT FLOAT Use atof()
816** TEXT BLOB No change
817** BLOB INTEGER Convert to TEXT then use atoi()
818** BLOB FLOAT Convert to TEXT then use atof()
819** BLOB TEXT Add a \000 terminator if needed
820**
821** The following access routines are provided:
822**
823** _type() Return the datatype of the result. This is one of
824** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
825** or SQLITE_NULL.
826** _blob() Return the value of a BLOB.
827** _bytes() Return the number of bytes in a BLOB value or the number
828** of bytes in a TEXT value represented as UTF-8. The \000
829** terminator is included in the byte count for TEXT values.
830** _bytes16() Return the number of bytes in a BLOB value or the number
831** of bytes in a TEXT value represented as UTF-16. The \u0000
832** terminator is included in the byte count for TEXT values.
833** _double() Return a FLOAT value.
834** _int() Return an INTEGER value in the host computer's native
835** integer representation. This might be either a 32- or 64-bit
836** integer depending on the host.
837** _int64() Return an INTEGER value as a 64-bit signed integer.
838** _text() Return the value as UTF-8 text.
839** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000840*/
drhf4479502004-05-27 03:12:53 +0000841const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
842int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
843int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
844double sqlite3_column_double(sqlite3_stmt*, int iCol);
845int sqlite3_column_int(sqlite3_stmt*, int iCol);
drhefad9992004-06-22 12:13:55 +0000846sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +0000847const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
848const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000849int sqlite3_column_type(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000850
danielk197765904932004-05-26 06:18:37 +0000851/*
852** The sqlite3_finalize() function is called to delete a compiled
853** SQL statement obtained by a previous call to sqlite3_prepare()
854** or sqlite3_prepare16(). If the statement was executed successfully, or
855** not executed at all, then SQLITE_OK is returned. If execution of the
856** statement failed then an error code is returned.
857**
858** This routine can be called at any point during the execution of the
859** virtual machine. If the virtual machine has not completed execution
860** when this routine is called, that is like encountering an error or
861** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
862** rolled back and transactions cancelled, depending on the circumstances,
863** and the result code returned will be SQLITE_ABORT.
864*/
865int sqlite3_finalize(sqlite3_stmt *pStmt);
866
867/*
868** The sqlite3_reset() function is called to reset a compiled SQL
869** statement obtained by a previous call to sqlite3_prepare() or
870** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
871** Any SQL statement variables that had values bound to them using
872** the sqlite3_bind_*() API retain their values.
873*/
874int sqlite3_reset(sqlite3_stmt *pStmt);
875
876/*
danielk197765904932004-05-26 06:18:37 +0000877** The following two functions are used to add user functions or aggregates
878** implemented in C to the SQL langauge interpreted by SQLite. The
879** difference only between the two is that the second parameter, the
880** name of the (scalar) function or aggregate, is encoded in UTF-8 for
881** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
882**
883** The first argument is the database handle that the new function or
884** aggregate is to be added to. If a single program uses more than one
885** database handle internally, then user functions or aggregates must
886** be added individually to each database handle with which they will be
887** used.
888**
889** The third parameter is the number of arguments that the function or
890** aggregate takes. If this parameter is negative, then the function or
891** aggregate may take any number of arguments.
892**
danielk1977d8123362004-06-12 09:25:12 +0000893** The fourth parameter is one of SQLITE_UTF* values defined below,
894** indicating the encoding that the function is most likely to handle
895** values in. This does not change the behaviour of the programming
896** interface. However, if two versions of the same function are registered
897** with different encoding values, SQLite invokes the version likely to
898** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +0000899**
danielk197765904932004-05-26 06:18:37 +0000900** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
901** pointers to user implemented C functions that implement the user
902** function or aggregate. A scalar function requires an implementation of
903** the xFunc callback only, NULL pointers should be passed as the xStep
904** and xFinal parameters. An aggregate function requires an implementation
905** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
906** existing user function or aggregate, pass NULL for all three function
907** callback. Specifying an inconstent set of callback values, such as an
908** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
909** returned.
910*/
911int sqlite3_create_function(
912 sqlite3 *,
913 const char *zFunctionName,
914 int nArg,
915 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000916 void*,
917 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
918 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
919 void (*xFinal)(sqlite3_context*)
920);
921int sqlite3_create_function16(
922 sqlite3*,
923 const void *zFunctionName,
924 int nArg,
925 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000926 void*,
927 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
928 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
929 void (*xFinal)(sqlite3_context*)
930);
931
932/*
danielk197765904932004-05-26 06:18:37 +0000933** The next routine returns the number of calls to xStep for a particular
934** aggregate function instance. The current call to xStep counts so this
935** routine always returns at least 1.
936*/
937int sqlite3_aggregate_count(sqlite3_context*);
938
danielk19770ffba6b2004-05-24 09:10:10 +0000939/*
drh4f26d6c2004-05-26 23:25:30 +0000940** The next group of routines returns information about parameters to
941** a user-defined function. Function implementations use these routines
942** to access their parameters. These routines are the same as the
943** sqlite3_column_* routines except that these routines take a single
944** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
945** column number.
danielk19770ffba6b2004-05-24 09:10:10 +0000946*/
drhf4479502004-05-27 03:12:53 +0000947const void *sqlite3_value_blob(sqlite3_value*);
948int sqlite3_value_bytes(sqlite3_value*);
949int sqlite3_value_bytes16(sqlite3_value*);
950double sqlite3_value_double(sqlite3_value*);
951int sqlite3_value_int(sqlite3_value*);
drhefad9992004-06-22 12:13:55 +0000952sqlite_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +0000953const unsigned char *sqlite3_value_text(sqlite3_value*);
954const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +0000955const void *sqlite3_value_text16le(sqlite3_value*);
956const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +0000957int sqlite3_value_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +0000958
959/*
danielk19770ae8b832004-05-25 12:05:56 +0000960** Aggregate functions use the following routine to allocate
961** a structure for storing their state. The first time this routine
962** is called for a particular aggregate, a new structure of size nBytes
963** is allocated, zeroed, and returned. On subsequent calls (for the
964** same aggregate instance) the same buffer is returned. The implementation
965** of the aggregate can use the returned buffer to accumulate data.
966**
967** The buffer allocated is freed automatically by SQLite.
968*/
drh4f26d6c2004-05-26 23:25:30 +0000969void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +0000970
971/*
972** The pUserData parameter to the sqlite3_create_function() and
973** sqlite3_create_aggregate() routines used to register user functions
974** is available to the implementation of the function using this
975** call.
976*/
977void *sqlite3_user_data(sqlite3_context*);
978
979/*
danielk1977682f68b2004-06-05 10:22:17 +0000980** The following two functions may be used by scalar user functions to
981** associate meta-data with argument values. If the same value is passed to
982** multiple invocations of the user-function during query execution, under
983** some circumstances the associated meta-data may be preserved. This may
984** be used, for example, to add a regular-expression matching scalar
985** function. The compiled version of the regular expression is stored as
986** meta-data associated with the SQL value passed as the regular expression
987** pattern.
988**
989** Calling sqlite3_get_auxdata() returns a pointer to the meta data
990** associated with the Nth argument value to the current user function
991** call, where N is the second parameter. If no meta-data has been set for
992** that value, then a NULL pointer is returned.
993**
994** The sqlite3_set_auxdata() is used to associate meta data with a user
995** function argument. The third parameter is a pointer to the meta data
996** to be associated with the Nth user function argument value. The fourth
997** parameter specifies a 'delete function' that will be called on the meta
998** data pointer to release it when it is no longer required. If the delete
999** function pointer is NULL, it is not invoked.
1000**
1001** In practice, meta-data is preserved between function calls for
1002** expressions that are constant at compile time. This includes literal
1003** values and SQL variables.
1004*/
1005void *sqlite3_get_auxdata(sqlite3_context*, int);
1006void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
1007
drha2854222004-06-17 19:04:17 +00001008
1009/*
1010** These are special value for the destructor that is passed in as the
1011** final argument to routines like sqlite3_result_blob(). If the destructor
1012** argument is SQLITE_STATIC, it means that the content pointer is constant
1013** and will never change. It does not need to be destroyed. The
1014** SQLITE_TRANSIENT value means that the content will likely change in
1015** the near future and that SQLite should make its own private copy of
1016** the content before returning.
1017*/
danielk1977d8123362004-06-12 09:25:12 +00001018#define SQLITE_STATIC ((void(*)(void *))0)
1019#define SQLITE_TRANSIENT ((void(*)(void *))-1)
1020
danielk1977682f68b2004-06-05 10:22:17 +00001021/*
drh4f26d6c2004-05-26 23:25:30 +00001022** User-defined functions invoke the following routines in order to
1023** set their return value.
danielk19777e18c252004-05-25 11:47:24 +00001024*/
danielk1977d8123362004-06-12 09:25:12 +00001025void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001026void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +00001027void sqlite3_result_error(sqlite3_context*, const char*, int);
1028void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +00001029void sqlite3_result_int(sqlite3_context*, int);
drhefad9992004-06-22 12:13:55 +00001030void sqlite3_result_int64(sqlite3_context*, sqlite_int64);
drh4f26d6c2004-05-26 23:25:30 +00001031void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +00001032void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
1033void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
1034void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
1035void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001036void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +00001037
drh52619df2004-06-11 17:48:02 +00001038/*
1039** These are the allowed values for the eTextRep argument to
1040** sqlite3_create_collation and sqlite3_create_function.
1041*/
danielk1977466be562004-06-10 02:16:01 +00001042#define SQLITE_UTF8 1
danielk1977dc8453f2004-06-12 00:42:34 +00001043#define SQLITE_UTF16LE 2
1044#define SQLITE_UTF16BE 3
1045#define SQLITE_UTF16 4 /* Use native byte order */
drh52619df2004-06-11 17:48:02 +00001046#define SQLITE_ANY 5 /* sqlite3_create_function only */
danielk1977466be562004-06-10 02:16:01 +00001047
danielk19777cedc8d2004-06-10 10:50:08 +00001048/*
1049** These two functions are used to add new collation sequences to the
1050** sqlite3 handle specified as the first argument.
1051**
1052** The name of the new collation sequence is specified as a UTF-8 string
1053** for sqlite3_create_collation() and a UTF-16 string for
1054** sqlite3_create_collation16(). In both cases the name is passed as the
1055** second function argument.
1056**
1057** The third argument must be one of the constants SQLITE_UTF8,
1058** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1059** routine expects to be passed pointers to strings encoded using UTF-8,
1060** UTF-16 little-endian or UTF-16 big-endian respectively.
1061**
1062** A pointer to the user supplied routine must be passed as the fifth
1063** argument. If it is NULL, this is the same as deleting the collation
1064** sequence (so that SQLite cannot call it anymore). Each time the user
1065** supplied function is invoked, it is passed a copy of the void* passed as
1066** the fourth argument to sqlite3_create_collation() or
1067** sqlite3_create_collation16() as its first parameter.
1068**
1069** The remaining arguments to the user-supplied routine are two strings,
1070** each represented by a [length, data] pair and encoded in the encoding
1071** that was passed as the third argument when the collation sequence was
1072** registered. The user routine should return negative, zero or positive if
1073** the first string is less than, equal to, or greater than the second
1074** string. i.e. (STRING1 - STRING2).
1075*/
danielk19770202b292004-06-09 09:55:16 +00001076int sqlite3_create_collation(
1077 sqlite3*,
1078 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001079 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001080 void*,
1081 int(*xCompare)(void*,int,const void*,int,const void*)
1082);
1083int sqlite3_create_collation16(
1084 sqlite3*,
1085 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001086 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001087 void*,
1088 int(*xCompare)(void*,int,const void*,int,const void*)
1089);
1090
danielk19777cedc8d2004-06-10 10:50:08 +00001091/*
1092** To avoid having to register all collation sequences before a database
1093** can be used, a single callback function may be registered with the
1094** database handle to be called whenever an undefined collation sequence is
1095** required.
1096**
1097** If the function is registered using the sqlite3_collation_needed() API,
1098** then it is passed the names of undefined collation sequences as strings
1099** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1100** are passed as UTF-16 in machine native byte order. A call to either
1101** function replaces any existing callback.
1102**
1103** When the user-function is invoked, the first argument passed is a copy
1104** of the second argument to sqlite3_collation_needed() or
1105** sqlite3_collation_needed16(). The second argument is the database
1106** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1107** SQLITE_UTF16LE, indicating the most desirable form of the collation
1108** sequence function required. The fourth parameter is the name of the
1109** required collation sequence.
1110**
1111** The collation sequence is returned to SQLite by a collation-needed
1112** callback using the sqlite3_create_collation() or
1113** sqlite3_create_collation16() APIs, described above.
1114*/
1115int sqlite3_collation_needed(
1116 sqlite3*,
1117 void*,
1118 void(*)(void*,sqlite3*,int eTextRep,const char*)
1119);
1120int sqlite3_collation_needed16(
1121 sqlite3*,
1122 void*,
1123 void(*)(void*,sqlite3*,int eTextRep,const void*)
1124);
1125
drh2011d5f2004-07-22 02:40:37 +00001126/*
1127** Specify the key for an encrypted database. This routine should be
1128** called right after sqlite3_open().
1129**
1130** The code to implement this API is not available in the public release
1131** of SQLite.
1132*/
1133int sqlite3_key(
1134 sqlite3 *db, /* Database to be rekeyed */
1135 const void *pKey, int nKey /* The key */
1136);
1137
1138/*
1139** Change the key on an open database. If the current database is not
1140** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the
1141** database is decrypted.
1142**
1143** The code to implement this API is not available in the public release
1144** of SQLite.
1145*/
1146int sqlite3_rekey(
1147 sqlite3 *db, /* Database to be rekeyed */
1148 const void *pKey, int nKey /* The new key */
1149);
danielk19770202b292004-06-09 09:55:16 +00001150
drhab3f9fe2004-08-14 17:10:10 +00001151/*
1152** If the following global variable is made to point to a constant
1153** string which is the name of a directory, then all temporary files
1154** created by SQLite will be placed in that directory. If this variable
1155** is NULL pointer, then SQLite does a search for an appropriate temporary
1156** file directory.
1157**
1158** This variable should only be changed when there are no open databases.
1159** Once sqlite3_open() has been called, this variable should not be changed
1160** until all database connections are closed.
1161*/
drheffd02b2004-08-29 23:42:13 +00001162extern const char *sqlite3_temp_directory;
drhab3f9fe2004-08-14 17:10:10 +00001163
drh382c0242001-10-06 16:33:02 +00001164#ifdef __cplusplus
1165} /* End of the 'extern "C"' block */
1166#endif
danielk19774adee202004-05-08 08:23:19 +00001167#endif