blob: b9b5b681a03eff2355476c40d6aec4b211931605 [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**
drha3f70cb2004-09-30 14:24:50 +000015** @(#) $Id: sqlite.h.in,v 1.120 2004/09/30 14:24:50 drh Exp $
drh75897232000-05-29 14:26:00 +000016*/
drh12057d52004-09-06 17:34:12 +000017#ifndef _SQLITE3_H_
18#define _SQLITE3_H_
drha18c5682000-10-08 22:20:57 +000019#include <stdarg.h> /* Needed for the definition of va_list */
drh75897232000-05-29 14:26:00 +000020
21/*
drh382c0242001-10-06 16:33:02 +000022** Make sure we can call this stuff from C++.
23*/
24#ifdef __cplusplus
25extern "C" {
26#endif
27
28/*
drhb86ccfb2003-01-28 23:13:10 +000029** The version of the SQLite library.
30*/
31#define SQLITE_VERSION "--VERS--"
32
33/*
drhb217a572000-08-22 13:40:18 +000034** The version string is also compiled into the library so that a program
35** can check to make sure that the lib*.a file and the *.h file are from
drh6f3a3ef2004-08-28 18:21:21 +000036** the same version. The sqlite3_libversion() function returns a pointer
37** to the sqlite3_version variable - useful in DLLs which cannot access
38** global variables.
drhb217a572000-08-22 13:40:18 +000039*/
danielk19776f8a5032004-05-10 10:34:51 +000040extern const char sqlite3_version[];
drha3f70cb2004-09-30 14:24:50 +000041const char *sqlite3_libversion(void);
drh303aaa72000-08-17 10:22:34 +000042
43/*
drh75897232000-05-29 14:26:00 +000044** Each open sqlite database is represented by an instance of the
45** following opaque structure.
46*/
drh9bb575f2004-09-06 17:24:11 +000047typedef struct sqlite3 sqlite3;
danielk197765904932004-05-26 06:18:37 +000048
drh75897232000-05-29 14:26:00 +000049
50/*
drhefad9992004-06-22 12:13:55 +000051** Some compilers do not support the "long long" datatype. So we have
52** to do a typedef that for 64-bit integers that depends on what compiler
53** is being used.
54*/
55#if defined(_MSC_VER) || defined(__BORLANDC__)
56 typedef __int64 sqlite_int64;
drh1211de32004-07-26 12:24:22 +000057 typedef unsigned __int64 sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000058#else
59 typedef long long int sqlite_int64;
drh1211de32004-07-26 12:24:22 +000060 typedef unsigned long long int sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000061#endif
62
63
64/*
drh75897232000-05-29 14:26:00 +000065** A function to close the database.
66**
67** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +000068** returned from sqlite3_open() and the corresponding database will by closed.
danielk197796d81f92004-06-19 03:33:57 +000069**
70** All SQL statements prepared using sqlite3_prepare() or
71** sqlite3_prepare16() must be deallocated using sqlite3_finalize() before
72** this routine is called. Otherwise, SQLITE_BUSY is returned and the
73** database connection remains open.
drh75897232000-05-29 14:26:00 +000074*/
danielk1977f9d64d22004-06-19 08:18:07 +000075int sqlite3_close(sqlite3 *);
drh75897232000-05-29 14:26:00 +000076
77/*
78** The type for a callback function.
79*/
drh12057d52004-09-06 17:34:12 +000080typedef int (*sqlite3_callback)(void*,int,char**, char**);
drh75897232000-05-29 14:26:00 +000081
82/*
83** A function to executes one or more statements of SQL.
84**
85** If one or more of the SQL statements are queries, then
86** the callback function specified by the 3rd parameter is
87** invoked once for each row of the query result. This callback
88** should normally return 0. If the callback returns a non-zero
89** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +000090** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +000091**
92** The 4th parameter is an arbitrary pointer that is passed
93** to the callback function as its first parameter.
94**
95** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +000096** columns in the query result. The 3rd parameter to the callback
97** is an array of strings holding the values for each column.
98** The 4th parameter to the callback is an array of strings holding
99** the names of each column.
drh75897232000-05-29 14:26:00 +0000100**
101** The callback function may be NULL, even for queries. A NULL
102** callback is not an error. It just means that no callback
103** will be invoked.
104**
105** If an error occurs while parsing or evaluating the SQL (but
106** not while executing the callback) then an appropriate error
107** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +0000108** *errmsg is made to point to that message. The calling function
109** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +0000110** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +0000111** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +0000112**
113** The return value is is SQLITE_OK if there are no errors and
114** some other return code if there is an error. The particular
115** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +0000116**
117** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000118** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +0000119** behavior can be modified somewhat using the sqlite3_busy_handler()
120** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000121*/
danielk19776f8a5032004-05-10 10:34:51 +0000122int sqlite3_exec(
drh12057d52004-09-06 17:34:12 +0000123 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000124 const char *sql, /* SQL to be executed */
drh12057d52004-09-06 17:34:12 +0000125 sqlite3_callback, /* Callback function */
drh75897232000-05-29 14:26:00 +0000126 void *, /* 1st argument to callback function */
127 char **errmsg /* Error msg written here */
128);
129
drh58b95762000-06-02 01:17:37 +0000130/*
danielk19776f8a5032004-05-10 10:34:51 +0000131** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000132*/
drh717e6402001-09-27 03:22:32 +0000133#define SQLITE_OK 0 /* Successful result */
134#define SQLITE_ERROR 1 /* SQL error or missing database */
135#define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */
136#define SQLITE_PERM 3 /* Access permission denied */
137#define SQLITE_ABORT 4 /* Callback routine requested an abort */
138#define SQLITE_BUSY 5 /* The database file is locked */
139#define SQLITE_LOCKED 6 /* A table in the database is locked */
140#define SQLITE_NOMEM 7 /* A malloc() failed */
141#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000142#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000143#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
144#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
145#define SQLITE_NOTFOUND 12 /* (Internal Only) Table or record not found */
146#define SQLITE_FULL 13 /* Insertion failed because database is full */
147#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
148#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000149#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000150#define SQLITE_SCHEMA 17 /* The database schema changed */
151#define SQLITE_TOOBIG 18 /* Too much data for one row of a table */
152#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000153#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000154#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000155#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000156#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000157#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000158#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000159#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000160#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
161#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh717e6402001-09-27 03:22:32 +0000162
drhaf9ff332002-01-16 21:00:27 +0000163/*
164** Each entry in an SQLite table has a unique integer key. (The key is
165** the value of the INTEGER PRIMARY KEY column if there is such a column,
166** otherwise the key is generated at random. The unique key is always
167** available as the ROWID, OID, or _ROWID_ column.) The following routine
168** returns the integer key of the most recent insert in the database.
169**
170** This function is similar to the mysql_insert_id() function from MySQL.
171*/
drhefad9992004-06-22 12:13:55 +0000172sqlite_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000173
drhc8d30ac2002-04-12 10:08:59 +0000174/*
175** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000176** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000177**
178** All changes are counted, even if they were later undone by a
179** ROLLBACK or ABORT. Except, changes associated with creating and
180** dropping tables are not counted.
181**
danielk19776f8a5032004-05-10 10:34:51 +0000182** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000183** in the inner, recursive call are counted together with the changes
184** in the outer call.
185**
186** SQLite implements the command "DELETE FROM table" without a WHERE clause
187** by dropping and recreating the table. (This is much faster than going
188** through and deleting individual elements form the table.) Because of
189** this optimization, the change count for "DELETE FROM table" will be
190** zero regardless of the number of elements that were originally in the
191** table. To get an accurate count of the number of rows deleted, use
192** "DELETE FROM table WHERE 1" instead.
193*/
danielk1977f9d64d22004-06-19 08:18:07 +0000194int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000195
rdcf146a772004-02-25 22:51:06 +0000196/*
danielk1977b28af712004-06-21 06:50:26 +0000197** This function returns the number of database rows that have been
198** modified by INSERT, UPDATE or DELETE statements since the database handle
199** was opened. This includes UPDATE, INSERT and DELETE statements executed
200** as part of trigger programs. All changes are counted as soon as the
201** statement that makes them is completed (when the statement handle is
202** passed to sqlite3_reset() or sqlite_finalise()).
rdcf146a772004-02-25 22:51:06 +0000203**
204** SQLite implements the command "DELETE FROM table" without a WHERE clause
205** by dropping and recreating the table. (This is much faster than going
206** through and deleting individual elements form the table.) Because of
207** this optimization, the change count for "DELETE FROM table" will be
208** zero regardless of the number of elements that were originally in the
209** table. To get an accurate count of the number of rows deleted, use
210** "DELETE FROM table WHERE 1" instead.
rdcf146a772004-02-25 22:51:06 +0000211*/
danielk1977b28af712004-06-21 06:50:26 +0000212int sqlite3_total_changes(sqlite3*);
213
drh4c504392000-10-16 22:06:40 +0000214/* This function causes any pending database operation to abort and
215** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000216** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000217** or Ctrl-C where the user wants a long query operation to halt
218** immediately.
219*/
danielk1977f9d64d22004-06-19 08:18:07 +0000220void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000221
drheec553b2000-06-02 01:51:20 +0000222
danielk197761de0d12004-05-27 23:56:16 +0000223/* These functions return true if the given input string comprises
224** one or more complete SQL statements. For the sqlite3_complete() call,
225** the parameter must be a nul-terminated UTF-8 string. For
226** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
227** is required.
drh75897232000-05-29 14:26:00 +0000228**
229** The algorithm is simple. If the last token other than spaces
230** and comments is a semicolon, then return true. otherwise return
231** false.
232*/
danielk19776f8a5032004-05-10 10:34:51 +0000233int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000234int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000235
drh2dfbbca2000-07-28 14:32:48 +0000236/*
237** This routine identifies a callback function that is invoked
238** whenever an attempt is made to open a database table that is
239** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000240** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000241** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000242** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000243** second argument is the name of the locked table and the third
244** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000245** busy callback returns 0, then sqlite3_exec() immediately returns
246** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000247** tries to open the table again and the cycle repeats.
248**
249** The default busy callback is NULL.
250**
251** Sqlite is re-entrant, so the busy handler may start a new query.
252** (It is not clear why anyone would every want to do this, but it
253** is allowed, in theory.) But the busy handler may not close the
254** database. Closing the database from a busy handler will delete
255** data structures out from under the executing query and will
256** probably result in a coredump.
257*/
danielk1977f9d64d22004-06-19 08:18:07 +0000258int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000259
260/*
261** This routine sets a busy handler that sleeps for a while when a
262** table is locked. The handler will sleep multiple times until
263** at least "ms" milleseconds of sleeping have been done. After
264** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000265** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000266**
267** Calling this routine with an argument less than or equal to zero
268** turns off all busy handlers.
269*/
danielk1977f9d64d22004-06-19 08:18:07 +0000270int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000271
drhe3710332000-09-29 13:30:53 +0000272/*
danielk19776f8a5032004-05-10 10:34:51 +0000273** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000274** Instead of invoking a user-supplied callback for each row of the
275** result, this routine remembers each row of the result in memory
276** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000277** query has finished.
278**
279** As an example, suppose the query result where this table:
280**
281** Name | Age
282** -----------------------
283** Alice | 43
284** Bob | 28
285** Cindy | 21
286**
287** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000288** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000289**
290** azResult[0] = "Name";
291** azResult[1] = "Age";
292** azResult[2] = "Alice";
293** azResult[3] = "43";
294** azResult[4] = "Bob";
295** azResult[5] = "28";
296** azResult[6] = "Cindy";
297** azResult[7] = "21";
298**
299** Notice that there is an extra row of data containing the column
300** headers. But the *nrow return value is still 3. *ncolumn is
301** set to 2. In general, the number of values inserted into azResult
302** will be ((*nrow) + 1)*(*ncolumn).
303**
304** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000305** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000306** release the memory that was malloc-ed. Because of the way the
307** malloc() happens, the calling function must not try to call
danielk19776f8a5032004-05-10 10:34:51 +0000308** malloc() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000309** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000310**
danielk19776f8a5032004-05-10 10:34:51 +0000311** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000312*/
danielk19776f8a5032004-05-10 10:34:51 +0000313int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000314 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000315 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000316 char ***resultp, /* Result written to a char *[] that this points to */
317 int *nrow, /* Number of result rows written here */
318 int *ncolumn, /* Number of result columns written here */
319 char **errmsg /* Error msg written here */
320);
321
322/*
danielk19776f8a5032004-05-10 10:34:51 +0000323** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000324*/
danielk19776f8a5032004-05-10 10:34:51 +0000325void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000326
drha18c5682000-10-08 22:20:57 +0000327/*
drh4f26d6c2004-05-26 23:25:30 +0000328** The following routines are variants of the "sprintf()" from the
329** standard C library. The resulting string is written into memory
330** obtained from malloc() so that there is never a possiblity of buffer
331** overflow. These routines also implement some additional formatting
332** options that are useful for constructing SQL statements.
333**
334** The strings returned by these routines should be freed by calling
335** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000336**
337** All of the usual printf formatting options apply. In addition, there
338** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000339** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000340** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000341** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000342** the string.
343**
344** For example, so some string variable contains text as follows:
345**
346** char *zText = "It's a happy day!";
347**
348** We can use this text in an SQL statement as follows:
349**
danielk19776f8a5032004-05-10 10:34:51 +0000350** sqlite3_exec_printf(db, "INSERT INTO table VALUES('%q')",
drha18c5682000-10-08 22:20:57 +0000351** callback1, 0, 0, zText);
352**
353** Because the %q format string is used, the '\'' character in zText
354** is escaped and the SQL generated is as follows:
355**
356** INSERT INTO table1 VALUES('It''s a happy day!')
357**
358** This is correct. Had we used %s instead of %q, the generated SQL
359** would have looked like this:
360**
361** INSERT INTO table1 VALUES('It's a happy day!');
362**
363** This second example is an SQL syntax error. As a general rule you
364** should always use %q instead of %s when inserting text into a string
365** literal.
366*/
danielk19776f8a5032004-05-10 10:34:51 +0000367char *sqlite3_mprintf(const char*,...);
368char *sqlite3_vmprintf(const char*, va_list);
drh4f26d6c2004-05-26 23:25:30 +0000369void sqlite3_free(char *z);
drhfeac5f82004-08-01 00:10:45 +0000370char *sqlite3_snprintf(int,char*,const char*, ...);
drh5191b7e2002-03-08 02:12:00 +0000371
drh1211de32004-07-26 12:24:22 +0000372#ifndef SQLITE_OMIT_AUTHORIZATION
drh5191b7e2002-03-08 02:12:00 +0000373/*
drhed6c8672003-01-12 18:02:16 +0000374** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000375** callback is invoked (at compile-time, not at run-time) for each
376** attempt to access a column of a table in the database. The callback
377** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
378** SQL statement should be aborted with an error and SQLITE_IGNORE
379** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000380*/
danielk19776f8a5032004-05-10 10:34:51 +0000381int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000382 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000383 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000384 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000385);
drh1211de32004-07-26 12:24:22 +0000386#endif
drhed6c8672003-01-12 18:02:16 +0000387
388/*
389** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000390** be one of the values below. These values signify what kind of operation
391** is to be authorized. The 3rd and 4th parameters to the authorization
392** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000393** codes is used as the second parameter. The 5th parameter is the name
394** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000395** is the name of the inner-most trigger or view that is responsible for
396** the access attempt or NULL if this access attempt is directly from
397** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000398**
399** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000400*/
drh77ad4e42003-01-14 02:49:27 +0000401#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000402#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
403#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
404#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
405#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000406#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000407#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000408#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000409#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
410#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000411#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000412#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000413#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000414#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000415#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000416#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000417#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000418#define SQLITE_DROP_VIEW 17 /* View Name NULL */
419#define SQLITE_INSERT 18 /* Table Name NULL */
420#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
421#define SQLITE_READ 20 /* Table Name Column Name */
422#define SQLITE_SELECT 21 /* NULL NULL */
423#define SQLITE_TRANSACTION 22 /* NULL NULL */
424#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000425#define SQLITE_ATTACH 24 /* Filename NULL */
426#define SQLITE_DETACH 25 /* Database Name NULL */
427
drhed6c8672003-01-12 18:02:16 +0000428
429/*
430** The return value of the authorization function should be one of the
431** following constants:
432*/
433/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
434#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
435#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
436
437/*
danielk19776f8a5032004-05-10 10:34:51 +0000438** Register a function that is called at every invocation of sqlite3_exec()
danielk19774ad17132004-05-21 01:47:26 +0000439** or sqlite3_prepare(). This function can be used (for example) to generate
drhb86ccfb2003-01-28 23:13:10 +0000440** a log file of all SQL executed against a database.
drh18de4822003-01-16 16:28:53 +0000441*/
danielk1977f9d64d22004-06-19 08:18:07 +0000442void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh18de4822003-01-16 16:28:53 +0000443
danielk1977348bb5d2003-10-18 09:37:26 +0000444/*
445** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000446** is invoked periodically during long running calls to sqlite3_exec(),
447** sqlite3_step() and sqlite3_get_table(). An example use for this API is to keep
danielk1977348bb5d2003-10-18 09:37:26 +0000448** a GUI updated during a large query.
449**
450** The progress callback is invoked once for every N virtual machine opcodes,
451** where N is the second argument to this function. The progress callback
452** itself is identified by the third argument to this function. The fourth
453** argument to this function is a void pointer passed to the progress callback
454** function each time it is invoked.
455**
danielk19776f8a5032004-05-10 10:34:51 +0000456** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000457** in less than N opcodes being executed, then the progress callback is not
458** invoked.
459**
danielk1977348bb5d2003-10-18 09:37:26 +0000460** To remove the progress callback altogether, pass NULL as the third
461** argument to this function.
462**
463** If the progress callback returns a result other than 0, then the current
464** query is immediately terminated and any database changes rolled back. If the
465** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000466** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000467**
468******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000469*/
danielk1977f9d64d22004-06-19 08:18:07 +0000470void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000471
drhaa940ea2004-01-15 02:44:03 +0000472/*
473** Register a callback function to be invoked whenever a new transaction
474** is committed. The pArg argument is passed through to the callback.
475** callback. If the callback function returns non-zero, then the commit
476** is converted into a rollback.
477**
478** If another function was previously registered, its pArg value is returned.
479** Otherwise NULL is returned.
480**
481** Registering a NULL function disables the callback.
482**
483******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
484*/
danielk1977f9d64d22004-06-19 08:18:07 +0000485void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000486
drh22fbcb82004-02-01 01:22:50 +0000487/*
drh4f26d6c2004-05-26 23:25:30 +0000488** Open the sqlite database file "filename". The "filename" is UTF-8
489** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
490** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
491** if an error occurs. If the database is opened (or created) successfully,
492** then SQLITE_OK is returned. Otherwise an error code is returned. The
493** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
494** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000495**
drh4f26d6c2004-05-26 23:25:30 +0000496** If the database file does not exist, then a new database is created.
497** The encoding for the database is UTF-8 if sqlite3_open() is called and
498** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000499**
500** Whether or not an error occurs when it is opened, resources associated
501** with the sqlite3* handle should be released by passing it to
502** sqlite3_close() when it is no longer required.
503*/
504int sqlite3_open(
505 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000506 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000507);
danielk197765904932004-05-26 06:18:37 +0000508int sqlite3_open16(
509 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000510 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000511);
danielk1977295ba552004-05-19 10:34:51 +0000512
danielk197765904932004-05-26 06:18:37 +0000513/*
514** Return the error code for the most recent sqlite3_* API call associated
515** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
516** API call was successful.
517**
518** Calls to many sqlite3_* functions set the error code and string returned
519** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
520** (overwriting the previous values). Note that calls to sqlite3_errcode(),
521** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
522** results of future invocations.
523**
524** Assuming no other intervening sqlite3_* API calls are made, the error
525** code returned by this function is associated with the same error as
526** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
527*/
528int sqlite3_errcode(sqlite3 *db);
529
530/*
531** Return a pointer to a UTF-8 encoded string describing in english the
532** error condition for the most recent sqlite3_* API call. The returned
533** string is always terminated by an 0x00 byte.
534**
535** The string "not an error" is returned when the most recent API call was
536** successful.
537*/
538const char *sqlite3_errmsg(sqlite3*);
539
540/*
541** Return a pointer to a UTF-16 native byte order encoded string describing
542** in english the error condition for the most recent sqlite3_* API call.
543** The returned string is always terminated by a pair of 0x00 bytes.
544**
545** The string "not an error" is returned when the most recent API call was
546** successful.
547*/
548const void *sqlite3_errmsg16(sqlite3*);
549
550/*
551** An instance of the following opaque structure is used to represent
552** a compiled SQL statment.
553*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000554typedef struct sqlite3_stmt sqlite3_stmt;
555
danielk1977e3209e42004-05-20 01:40:18 +0000556/*
danielk197765904932004-05-26 06:18:37 +0000557** To execute an SQL query, it must first be compiled into a byte-code
558** program using one of the following routines. The only difference between
559** them is that the second argument, specifying the SQL statement to
560** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
561** function and UTF-16 for sqlite3_prepare16().
562**
563** The first parameter "db" is an SQLite database handle. The second
564** parameter "zSql" is the statement to be compiled, encoded as either
565** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
566** than zero, then zSql is read up to the first nul terminator. If
567** "nBytes" is not less than zero, then it is the length of the string zSql
568** in bytes (not characters).
569**
570** *pzTail is made to point to the first byte past the end of the first
571** SQL statement in zSql. This routine only compiles the first statement
572** in zSql, so *pzTail is left pointing to what remains uncompiled.
573**
574** *ppStmt is left pointing to a compiled SQL statement that can be
575** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
576** set to NULL. If the input text contained no SQL (if the input is and
577** empty string or a comment) then *ppStmt is set to NULL.
578**
579** On success, SQLITE_OK is returned. Otherwise an error code is returned.
580*/
581int sqlite3_prepare(
582 sqlite3 *db, /* Database handle */
583 const char *zSql, /* SQL statement, UTF-8 encoded */
584 int nBytes, /* Length of zSql in bytes. */
585 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
586 const char **pzTail /* OUT: Pointer to unused portion of zSql */
587);
588int sqlite3_prepare16(
589 sqlite3 *db, /* Database handle */
590 const void *zSql, /* SQL statement, UTF-16 encoded */
591 int nBytes, /* Length of zSql in bytes. */
592 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
593 const void **pzTail /* OUT: Pointer to unused portion of zSql */
594);
595
596/*
drhf4479502004-05-27 03:12:53 +0000597** Pointers to the following two opaque structures are used to communicate
598** with the implementations of user-defined functions.
599*/
600typedef struct sqlite3_context sqlite3_context;
601typedef struct Mem sqlite3_value;
602
603/*
drh4f26d6c2004-05-26 23:25:30 +0000604** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
605** one or more literals can be replace by a wildcard "?" or ":N:" where
606** N is an integer. These value of these wildcard literals can be set
607** using the routines listed below.
608**
609** In every case, the first parameter is a pointer to the sqlite3_stmt
610** structure returned from sqlite3_prepare(). The second parameter is the
611** index of the wildcard. The first "?" has an index of 1. ":N:" wildcards
612** use the index N.
613**
drh900dfba2004-07-21 15:21:36 +0000614** The fifth parameter to sqlite3_bind_blob(), sqlite3_bind_text(), and
615** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or
616** text after SQLite has finished with it. If the fifth argument is the
617** special value SQLITE_STATIC, then the library assumes that the information
618** is in static, unmanaged space and does not need to be freed. If the
619** fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its
620** own private copy of the data.
drh4f26d6c2004-05-26 23:25:30 +0000621**
622** The sqlite3_bind_* routine must be called before sqlite3_step() after
623** an sqlite3_prepare() or sqlite3_reset(). Unbound wildcards are interpreted
624** as NULL.
625*/
danielk1977d8123362004-06-12 09:25:12 +0000626int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000627int sqlite3_bind_double(sqlite3_stmt*, int, double);
628int sqlite3_bind_int(sqlite3_stmt*, int, int);
drhefad9992004-06-22 12:13:55 +0000629int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64);
drhf4479502004-05-27 03:12:53 +0000630int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000631int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
632int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000633int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000634
635/*
drh75f6a032004-07-15 14:15:00 +0000636** Return the number of wildcards in a compiled SQL statement. This
637** routine was added to support DBD::SQLite.
drh75f6a032004-07-15 14:15:00 +0000638*/
639int sqlite3_bind_parameter_count(sqlite3_stmt*);
640
641/*
drh895d7472004-08-20 16:02:39 +0000642** Return the name of the i-th parameter. Ordinary wildcards "?" are
drhfa6bc002004-09-07 16:19:52 +0000643** nameless and a NULL is returned. For wildcards of the form :N or
drh895d7472004-08-20 16:02:39 +0000644** $vvvv the complete text of the wildcard is returned.
645** NULL is returned if the index is out of range.
646*/
647const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
648
649/*
drhfa6bc002004-09-07 16:19:52 +0000650** Return the index of a parameter with the given name. The name
651** must match exactly. If no parameter with the given name is found,
652** return 0.
653*/
654int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
655
656/*
danielk197765904932004-05-26 06:18:37 +0000657** Return the number of columns in the result set returned by the compiled
658** SQL statement. This routine returns 0 if pStmt is an SQL statement
659** that does not return data (for example an UPDATE).
660*/
661int sqlite3_column_count(sqlite3_stmt *pStmt);
662
663/*
664** The first parameter is a compiled SQL statement. This function returns
665** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000666** second function parameter. The string returned is UTF-8 for
667** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000668*/
669const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000670const void *sqlite3_column_name16(sqlite3_stmt*,int);
671
672/*
673** The first parameter is a compiled SQL statement. If this statement
674** is a SELECT statement, the Nth column of the returned result set
675** of the SELECT is a table column then the declared type of the table
676** column is returned. If the Nth column of the result set is not at table
677** column, then a NULL pointer is returned. The returned string is always
678** UTF-8 encoded. For example, in the database schema:
679**
680** CREATE TABLE t1(c1 VARIANT);
681**
682** And the following statement compiled:
683**
684** SELECT c1 + 1, 0 FROM t1;
685**
686** Then this routine would return the string "VARIANT" for the second
687** result column (i==1), and a NULL pointer for the first result column
688** (i==0).
689*/
690const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
691
692/*
693** The first parameter is a compiled SQL statement. If this statement
694** is a SELECT statement, the Nth column of the returned result set
695** of the SELECT is a table column then the declared type of the table
696** column is returned. If the Nth column of the result set is not at table
697** column, then a NULL pointer is returned. The returned string is always
698** UTF-16 encoded. For example, in the database schema:
699**
drh4f26d6c2004-05-26 23:25:30 +0000700** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000701**
702** And the following statement compiled:
703**
704** SELECT c1 + 1, 0 FROM t1;
705**
drh4f26d6c2004-05-26 23:25:30 +0000706** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000707** result column (i==1), and a NULL pointer for the first result column
708** (i==0).
709*/
710const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
711
danielk1977106bb232004-05-21 10:08:53 +0000712/*
713** After an SQL query has been compiled with a call to either
714** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
715** called one or more times to execute the statement.
716**
717** The return value will be either SQLITE_BUSY, SQLITE_DONE,
718** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
719**
720** SQLITE_BUSY means that the database engine attempted to open
721** a locked database and there is no busy callback registered.
722** Call sqlite3_step() again to retry the open.
723**
724** SQLITE_DONE means that the statement has finished executing
725** successfully. sqlite3_step() should not be called again on this virtual
726** machine.
727**
728** If the SQL statement being executed returns any data, then
729** SQLITE_ROW is returned each time a new row of data is ready
730** for processing by the caller. The values may be accessed using
731** the sqlite3_column_*() functions described below. sqlite3_step()
732** is called again to retrieve the next row of data.
733**
734** SQLITE_ERROR means that a run-time error (such as a constraint
735** violation) has occurred. sqlite3_step() should not be called again on
736** the VM. More information may be found by calling sqlite3_errmsg().
737**
738** SQLITE_MISUSE means that the this routine was called inappropriately.
739** Perhaps it was called on a virtual machine that had already been
740** finalized or on one that had previously returned SQLITE_ERROR or
741** SQLITE_DONE. Or it could be the case the the same database connection
742** is being used simulataneously by two or more threads.
743*/
danielk197717240fd2004-05-26 00:07:25 +0000744int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000745
danielk1977106bb232004-05-21 10:08:53 +0000746/*
747** Return the number of values in the current row of the result set.
748**
749** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
750** will return the same value as the sqlite3_column_count() function.
751** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
752** error code, or before sqlite3_step() has been called on a
753** compiled SQL statement, this routine returns zero.
754*/
danielk197793d46752004-05-23 13:30:58 +0000755int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000756
drh4f26d6c2004-05-26 23:25:30 +0000757/*
758** Values are stored in the database in one of the following fundamental
759** types.
760*/
drh9c054832004-05-31 18:51:57 +0000761#define SQLITE_INTEGER 1
762#define SQLITE_FLOAT 2
763#define SQLITE_TEXT 3
764#define SQLITE_BLOB 4
765#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000766
danielk1977106bb232004-05-21 10:08:53 +0000767/*
drh4f26d6c2004-05-26 23:25:30 +0000768** The next group of routines returns information about the information
769** in a single column of the current result row of a query. In every
770** case the first parameter is a pointer to the SQL statement that is being
771** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
772** the second argument is the index of the column for which information
773** should be returned. iCol is zero-indexed. The left-most column as an
774** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000775**
drh4f26d6c2004-05-26 23:25:30 +0000776** If the SQL statement is not currently point to a valid row, or if the
777** the colulmn index is out of range, the result is undefined.
778**
779** These routines attempt to convert the value where appropriate. For
780** example, if the internal representation is FLOAT and a text result
781** is requested, sprintf() is used internally to do the conversion
782** automatically. The following table details the conversions that
783** are applied:
784**
785** Internal Type Requested Type Conversion
786** ------------- -------------- --------------------------
787** NULL INTEGER Result is 0
788** NULL FLOAT Result is 0.0
789** NULL TEXT Result is an empty string
790** NULL BLOB Result is a zero-length BLOB
791** INTEGER FLOAT Convert from integer to float
792** INTEGER TEXT ASCII rendering of the integer
793** INTEGER BLOB Same as for INTEGER->TEXT
794** FLOAT INTEGER Convert from float to integer
795** FLOAT TEXT ASCII rendering of the float
796** FLOAT BLOB Same as FLOAT->TEXT
797** TEXT INTEGER Use atoi()
798** TEXT FLOAT Use atof()
799** TEXT BLOB No change
800** BLOB INTEGER Convert to TEXT then use atoi()
801** BLOB FLOAT Convert to TEXT then use atof()
802** BLOB TEXT Add a \000 terminator if needed
803**
804** The following access routines are provided:
805**
806** _type() Return the datatype of the result. This is one of
807** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
808** or SQLITE_NULL.
809** _blob() Return the value of a BLOB.
810** _bytes() Return the number of bytes in a BLOB value or the number
811** of bytes in a TEXT value represented as UTF-8. The \000
812** terminator is included in the byte count for TEXT values.
813** _bytes16() Return the number of bytes in a BLOB value or the number
814** of bytes in a TEXT value represented as UTF-16. The \u0000
815** terminator is included in the byte count for TEXT values.
816** _double() Return a FLOAT value.
817** _int() Return an INTEGER value in the host computer's native
818** integer representation. This might be either a 32- or 64-bit
819** integer depending on the host.
820** _int64() Return an INTEGER value as a 64-bit signed integer.
821** _text() Return the value as UTF-8 text.
822** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000823*/
drhf4479502004-05-27 03:12:53 +0000824const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
825int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
826int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
827double sqlite3_column_double(sqlite3_stmt*, int iCol);
828int sqlite3_column_int(sqlite3_stmt*, int iCol);
drhefad9992004-06-22 12:13:55 +0000829sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +0000830const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
831const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000832int sqlite3_column_type(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000833
danielk197765904932004-05-26 06:18:37 +0000834/*
835** The sqlite3_finalize() function is called to delete a compiled
836** SQL statement obtained by a previous call to sqlite3_prepare()
837** or sqlite3_prepare16(). If the statement was executed successfully, or
838** not executed at all, then SQLITE_OK is returned. If execution of the
839** statement failed then an error code is returned.
840**
841** This routine can be called at any point during the execution of the
842** virtual machine. If the virtual machine has not completed execution
843** when this routine is called, that is like encountering an error or
844** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
845** rolled back and transactions cancelled, depending on the circumstances,
846** and the result code returned will be SQLITE_ABORT.
847*/
848int sqlite3_finalize(sqlite3_stmt *pStmt);
849
850/*
851** The sqlite3_reset() function is called to reset a compiled SQL
852** statement obtained by a previous call to sqlite3_prepare() or
853** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
854** Any SQL statement variables that had values bound to them using
855** the sqlite3_bind_*() API retain their values.
856*/
857int sqlite3_reset(sqlite3_stmt *pStmt);
858
859/*
danielk197765904932004-05-26 06:18:37 +0000860** The following two functions are used to add user functions or aggregates
861** implemented in C to the SQL langauge interpreted by SQLite. The
862** difference only between the two is that the second parameter, the
863** name of the (scalar) function or aggregate, is encoded in UTF-8 for
864** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
865**
866** The first argument is the database handle that the new function or
867** aggregate is to be added to. If a single program uses more than one
868** database handle internally, then user functions or aggregates must
869** be added individually to each database handle with which they will be
870** used.
871**
872** The third parameter is the number of arguments that the function or
873** aggregate takes. If this parameter is negative, then the function or
874** aggregate may take any number of arguments.
875**
danielk1977d8123362004-06-12 09:25:12 +0000876** The fourth parameter is one of SQLITE_UTF* values defined below,
877** indicating the encoding that the function is most likely to handle
878** values in. This does not change the behaviour of the programming
879** interface. However, if two versions of the same function are registered
880** with different encoding values, SQLite invokes the version likely to
881** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +0000882**
danielk197765904932004-05-26 06:18:37 +0000883** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
884** pointers to user implemented C functions that implement the user
885** function or aggregate. A scalar function requires an implementation of
886** the xFunc callback only, NULL pointers should be passed as the xStep
887** and xFinal parameters. An aggregate function requires an implementation
888** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
889** existing user function or aggregate, pass NULL for all three function
890** callback. Specifying an inconstent set of callback values, such as an
891** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
892** returned.
893*/
894int sqlite3_create_function(
895 sqlite3 *,
896 const char *zFunctionName,
897 int nArg,
898 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000899 void*,
900 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
901 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
902 void (*xFinal)(sqlite3_context*)
903);
904int sqlite3_create_function16(
905 sqlite3*,
906 const void *zFunctionName,
907 int nArg,
908 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000909 void*,
910 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
911 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
912 void (*xFinal)(sqlite3_context*)
913);
914
915/*
danielk197765904932004-05-26 06:18:37 +0000916** The next routine returns the number of calls to xStep for a particular
917** aggregate function instance. The current call to xStep counts so this
918** routine always returns at least 1.
919*/
920int sqlite3_aggregate_count(sqlite3_context*);
921
danielk19770ffba6b2004-05-24 09:10:10 +0000922/*
drh4f26d6c2004-05-26 23:25:30 +0000923** The next group of routines returns information about parameters to
924** a user-defined function. Function implementations use these routines
925** to access their parameters. These routines are the same as the
926** sqlite3_column_* routines except that these routines take a single
927** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
928** column number.
danielk19770ffba6b2004-05-24 09:10:10 +0000929*/
drhf4479502004-05-27 03:12:53 +0000930const void *sqlite3_value_blob(sqlite3_value*);
931int sqlite3_value_bytes(sqlite3_value*);
932int sqlite3_value_bytes16(sqlite3_value*);
933double sqlite3_value_double(sqlite3_value*);
934int sqlite3_value_int(sqlite3_value*);
drhefad9992004-06-22 12:13:55 +0000935sqlite_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +0000936const unsigned char *sqlite3_value_text(sqlite3_value*);
937const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +0000938const void *sqlite3_value_text16le(sqlite3_value*);
939const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +0000940int sqlite3_value_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +0000941
942/*
danielk19770ae8b832004-05-25 12:05:56 +0000943** Aggregate functions use the following routine to allocate
944** a structure for storing their state. The first time this routine
945** is called for a particular aggregate, a new structure of size nBytes
946** is allocated, zeroed, and returned. On subsequent calls (for the
947** same aggregate instance) the same buffer is returned. The implementation
948** of the aggregate can use the returned buffer to accumulate data.
949**
950** The buffer allocated is freed automatically by SQLite.
951*/
drh4f26d6c2004-05-26 23:25:30 +0000952void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +0000953
954/*
955** The pUserData parameter to the sqlite3_create_function() and
956** sqlite3_create_aggregate() routines used to register user functions
957** is available to the implementation of the function using this
958** call.
959*/
960void *sqlite3_user_data(sqlite3_context*);
961
962/*
danielk1977682f68b2004-06-05 10:22:17 +0000963** The following two functions may be used by scalar user functions to
964** associate meta-data with argument values. If the same value is passed to
965** multiple invocations of the user-function during query execution, under
966** some circumstances the associated meta-data may be preserved. This may
967** be used, for example, to add a regular-expression matching scalar
968** function. The compiled version of the regular expression is stored as
969** meta-data associated with the SQL value passed as the regular expression
970** pattern.
971**
972** Calling sqlite3_get_auxdata() returns a pointer to the meta data
973** associated with the Nth argument value to the current user function
974** call, where N is the second parameter. If no meta-data has been set for
975** that value, then a NULL pointer is returned.
976**
977** The sqlite3_set_auxdata() is used to associate meta data with a user
978** function argument. The third parameter is a pointer to the meta data
979** to be associated with the Nth user function argument value. The fourth
980** parameter specifies a 'delete function' that will be called on the meta
981** data pointer to release it when it is no longer required. If the delete
982** function pointer is NULL, it is not invoked.
983**
984** In practice, meta-data is preserved between function calls for
985** expressions that are constant at compile time. This includes literal
986** values and SQL variables.
987*/
988void *sqlite3_get_auxdata(sqlite3_context*, int);
989void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
990
drha2854222004-06-17 19:04:17 +0000991
992/*
993** These are special value for the destructor that is passed in as the
994** final argument to routines like sqlite3_result_blob(). If the destructor
995** argument is SQLITE_STATIC, it means that the content pointer is constant
996** and will never change. It does not need to be destroyed. The
997** SQLITE_TRANSIENT value means that the content will likely change in
998** the near future and that SQLite should make its own private copy of
999** the content before returning.
1000*/
danielk1977d8123362004-06-12 09:25:12 +00001001#define SQLITE_STATIC ((void(*)(void *))0)
1002#define SQLITE_TRANSIENT ((void(*)(void *))-1)
1003
danielk1977682f68b2004-06-05 10:22:17 +00001004/*
drh4f26d6c2004-05-26 23:25:30 +00001005** User-defined functions invoke the following routines in order to
1006** set their return value.
danielk19777e18c252004-05-25 11:47:24 +00001007*/
danielk1977d8123362004-06-12 09:25:12 +00001008void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001009void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +00001010void sqlite3_result_error(sqlite3_context*, const char*, int);
1011void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +00001012void sqlite3_result_int(sqlite3_context*, int);
drhefad9992004-06-22 12:13:55 +00001013void sqlite3_result_int64(sqlite3_context*, sqlite_int64);
drh4f26d6c2004-05-26 23:25:30 +00001014void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +00001015void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
1016void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
1017void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
1018void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001019void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +00001020
drh52619df2004-06-11 17:48:02 +00001021/*
1022** These are the allowed values for the eTextRep argument to
1023** sqlite3_create_collation and sqlite3_create_function.
1024*/
danielk1977466be562004-06-10 02:16:01 +00001025#define SQLITE_UTF8 1
danielk1977dc8453f2004-06-12 00:42:34 +00001026#define SQLITE_UTF16LE 2
1027#define SQLITE_UTF16BE 3
1028#define SQLITE_UTF16 4 /* Use native byte order */
drh52619df2004-06-11 17:48:02 +00001029#define SQLITE_ANY 5 /* sqlite3_create_function only */
danielk1977466be562004-06-10 02:16:01 +00001030
danielk19777cedc8d2004-06-10 10:50:08 +00001031/*
1032** These two functions are used to add new collation sequences to the
1033** sqlite3 handle specified as the first argument.
1034**
1035** The name of the new collation sequence is specified as a UTF-8 string
1036** for sqlite3_create_collation() and a UTF-16 string for
1037** sqlite3_create_collation16(). In both cases the name is passed as the
1038** second function argument.
1039**
1040** The third argument must be one of the constants SQLITE_UTF8,
1041** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1042** routine expects to be passed pointers to strings encoded using UTF-8,
1043** UTF-16 little-endian or UTF-16 big-endian respectively.
1044**
1045** A pointer to the user supplied routine must be passed as the fifth
1046** argument. If it is NULL, this is the same as deleting the collation
1047** sequence (so that SQLite cannot call it anymore). Each time the user
1048** supplied function is invoked, it is passed a copy of the void* passed as
1049** the fourth argument to sqlite3_create_collation() or
1050** sqlite3_create_collation16() as its first parameter.
1051**
1052** The remaining arguments to the user-supplied routine are two strings,
1053** each represented by a [length, data] pair and encoded in the encoding
1054** that was passed as the third argument when the collation sequence was
1055** registered. The user routine should return negative, zero or positive if
1056** the first string is less than, equal to, or greater than the second
1057** string. i.e. (STRING1 - STRING2).
1058*/
danielk19770202b292004-06-09 09:55:16 +00001059int sqlite3_create_collation(
1060 sqlite3*,
1061 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001062 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001063 void*,
1064 int(*xCompare)(void*,int,const void*,int,const void*)
1065);
1066int sqlite3_create_collation16(
1067 sqlite3*,
1068 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001069 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001070 void*,
1071 int(*xCompare)(void*,int,const void*,int,const void*)
1072);
1073
danielk19777cedc8d2004-06-10 10:50:08 +00001074/*
1075** To avoid having to register all collation sequences before a database
1076** can be used, a single callback function may be registered with the
1077** database handle to be called whenever an undefined collation sequence is
1078** required.
1079**
1080** If the function is registered using the sqlite3_collation_needed() API,
1081** then it is passed the names of undefined collation sequences as strings
1082** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1083** are passed as UTF-16 in machine native byte order. A call to either
1084** function replaces any existing callback.
1085**
1086** When the user-function is invoked, the first argument passed is a copy
1087** of the second argument to sqlite3_collation_needed() or
1088** sqlite3_collation_needed16(). The second argument is the database
1089** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1090** SQLITE_UTF16LE, indicating the most desirable form of the collation
1091** sequence function required. The fourth parameter is the name of the
1092** required collation sequence.
1093**
1094** The collation sequence is returned to SQLite by a collation-needed
1095** callback using the sqlite3_create_collation() or
1096** sqlite3_create_collation16() APIs, described above.
1097*/
1098int sqlite3_collation_needed(
1099 sqlite3*,
1100 void*,
1101 void(*)(void*,sqlite3*,int eTextRep,const char*)
1102);
1103int sqlite3_collation_needed16(
1104 sqlite3*,
1105 void*,
1106 void(*)(void*,sqlite3*,int eTextRep,const void*)
1107);
1108
drh2011d5f2004-07-22 02:40:37 +00001109/*
1110** Specify the key for an encrypted database. This routine should be
1111** called right after sqlite3_open().
1112**
1113** The code to implement this API is not available in the public release
1114** of SQLite.
1115*/
1116int sqlite3_key(
1117 sqlite3 *db, /* Database to be rekeyed */
1118 const void *pKey, int nKey /* The key */
1119);
1120
1121/*
1122** Change the key on an open database. If the current database is not
1123** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the
1124** database is decrypted.
1125**
1126** The code to implement this API is not available in the public release
1127** of SQLite.
1128*/
1129int sqlite3_rekey(
1130 sqlite3 *db, /* Database to be rekeyed */
1131 const void *pKey, int nKey /* The new key */
1132);
danielk19770202b292004-06-09 09:55:16 +00001133
drhab3f9fe2004-08-14 17:10:10 +00001134/*
1135** If the following global variable is made to point to a constant
1136** string which is the name of a directory, then all temporary files
1137** created by SQLite will be placed in that directory. If this variable
1138** is NULL pointer, then SQLite does a search for an appropriate temporary
1139** file directory.
1140**
1141** This variable should only be changed when there are no open databases.
1142** Once sqlite3_open() has been called, this variable should not be changed
1143** until all database connections are closed.
1144*/
drheffd02b2004-08-29 23:42:13 +00001145extern const char *sqlite3_temp_directory;
drhab3f9fe2004-08-14 17:10:10 +00001146
drh382c0242001-10-06 16:33:02 +00001147#ifdef __cplusplus
1148} /* End of the 'extern "C"' block */
1149#endif
danielk19774adee202004-05-08 08:23:19 +00001150#endif