blob: d3f314a25d2e9a15e3c30e632a71829b09eff902 [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**
drh1211de32004-07-26 12:24:22 +000015** @(#) $Id: sqlite.h.in,v 1.111 2004/07/26 12:24:23 drh Exp $
drh75897232000-05-29 14:26:00 +000016*/
17#ifndef _SQLITE_H_
18#define _SQLITE_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
36** the same version.
37*/
danielk19776f8a5032004-05-10 10:34:51 +000038extern const char sqlite3_version[];
drh303aaa72000-08-17 10:22:34 +000039
40/*
drh75897232000-05-29 14:26:00 +000041** Each open sqlite database is represented by an instance of the
42** following opaque structure.
43*/
danielk197765904932004-05-26 06:18:37 +000044typedef struct sqlite sqlite3;
45
drh75897232000-05-29 14:26:00 +000046
47/*
drhefad9992004-06-22 12:13:55 +000048** Some compilers do not support the "long long" datatype. So we have
49** to do a typedef that for 64-bit integers that depends on what compiler
50** is being used.
51*/
52#if defined(_MSC_VER) || defined(__BORLANDC__)
53 typedef __int64 sqlite_int64;
drh1211de32004-07-26 12:24:22 +000054 typedef unsigned __int64 sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000055#else
56 typedef long long int sqlite_int64;
drh1211de32004-07-26 12:24:22 +000057 typedef unsigned long long int sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000058#endif
59
60
61/*
drh75897232000-05-29 14:26:00 +000062** A function to close the database.
63**
64** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +000065** returned from sqlite3_open() and the corresponding database will by closed.
danielk197796d81f92004-06-19 03:33:57 +000066**
67** All SQL statements prepared using sqlite3_prepare() or
68** sqlite3_prepare16() must be deallocated using sqlite3_finalize() before
69** this routine is called. Otherwise, SQLITE_BUSY is returned and the
70** database connection remains open.
drh75897232000-05-29 14:26:00 +000071*/
danielk1977f9d64d22004-06-19 08:18:07 +000072int sqlite3_close(sqlite3 *);
drh75897232000-05-29 14:26:00 +000073
74/*
75** The type for a callback function.
76*/
77typedef int (*sqlite_callback)(void*,int,char**, char**);
78
79/*
80** A function to executes one or more statements of SQL.
81**
82** If one or more of the SQL statements are queries, then
83** the callback function specified by the 3rd parameter is
84** invoked once for each row of the query result. This callback
85** should normally return 0. If the callback returns a non-zero
86** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +000087** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +000088**
89** The 4th parameter is an arbitrary pointer that is passed
90** to the callback function as its first parameter.
91**
92** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +000093** columns in the query result. The 3rd parameter to the callback
94** is an array of strings holding the values for each column.
95** The 4th parameter to the callback is an array of strings holding
96** the names of each column.
drh75897232000-05-29 14:26:00 +000097**
98** The callback function may be NULL, even for queries. A NULL
99** callback is not an error. It just means that no callback
100** will be invoked.
101**
102** If an error occurs while parsing or evaluating the SQL (but
103** not while executing the callback) then an appropriate error
104** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +0000105** *errmsg is made to point to that message. The calling function
106** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +0000107** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +0000108** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +0000109**
110** The return value is is SQLITE_OK if there are no errors and
111** some other return code if there is an error. The particular
112** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +0000113**
114** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000115** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +0000116** behavior can be modified somewhat using the sqlite3_busy_handler()
117** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000118*/
danielk19776f8a5032004-05-10 10:34:51 +0000119int sqlite3_exec(
danielk1977f9d64d22004-06-19 08:18:07 +0000120 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000121 const char *sql, /* SQL to be executed */
drh75897232000-05-29 14:26:00 +0000122 sqlite_callback, /* Callback function */
123 void *, /* 1st argument to callback function */
124 char **errmsg /* Error msg written here */
125);
126
drh58b95762000-06-02 01:17:37 +0000127/*
danielk19776f8a5032004-05-10 10:34:51 +0000128** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000129*/
drh717e6402001-09-27 03:22:32 +0000130#define SQLITE_OK 0 /* Successful result */
131#define SQLITE_ERROR 1 /* SQL error or missing database */
132#define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */
133#define SQLITE_PERM 3 /* Access permission denied */
134#define SQLITE_ABORT 4 /* Callback routine requested an abort */
135#define SQLITE_BUSY 5 /* The database file is locked */
136#define SQLITE_LOCKED 6 /* A table in the database is locked */
137#define SQLITE_NOMEM 7 /* A malloc() failed */
138#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000139#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000140#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
141#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
142#define SQLITE_NOTFOUND 12 /* (Internal Only) Table or record not found */
143#define SQLITE_FULL 13 /* Insertion failed because database is full */
144#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
145#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000146#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000147#define SQLITE_SCHEMA 17 /* The database schema changed */
148#define SQLITE_TOOBIG 18 /* Too much data for one row of a table */
149#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000150#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000151#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000152#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000153#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000154#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000155#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000156#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000157#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
158#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh717e6402001-09-27 03:22:32 +0000159
drhaf9ff332002-01-16 21:00:27 +0000160/*
161** Each entry in an SQLite table has a unique integer key. (The key is
162** the value of the INTEGER PRIMARY KEY column if there is such a column,
163** otherwise the key is generated at random. The unique key is always
164** available as the ROWID, OID, or _ROWID_ column.) The following routine
165** returns the integer key of the most recent insert in the database.
166**
167** This function is similar to the mysql_insert_id() function from MySQL.
168*/
drhefad9992004-06-22 12:13:55 +0000169sqlite_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000170
drhc8d30ac2002-04-12 10:08:59 +0000171/*
172** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000173** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000174**
175** All changes are counted, even if they were later undone by a
176** ROLLBACK or ABORT. Except, changes associated with creating and
177** dropping tables are not counted.
178**
danielk19776f8a5032004-05-10 10:34:51 +0000179** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000180** in the inner, recursive call are counted together with the changes
181** in the outer call.
182**
183** SQLite implements the command "DELETE FROM table" without a WHERE clause
184** by dropping and recreating the table. (This is much faster than going
185** through and deleting individual elements form the table.) Because of
186** this optimization, the change count for "DELETE FROM table" will be
187** zero regardless of the number of elements that were originally in the
188** table. To get an accurate count of the number of rows deleted, use
189** "DELETE FROM table WHERE 1" instead.
190*/
danielk1977f9d64d22004-06-19 08:18:07 +0000191int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000192
rdcf146a772004-02-25 22:51:06 +0000193/*
danielk1977b28af712004-06-21 06:50:26 +0000194** This function returns the number of database rows that have been
195** modified by INSERT, UPDATE or DELETE statements since the database handle
196** was opened. This includes UPDATE, INSERT and DELETE statements executed
197** as part of trigger programs. All changes are counted as soon as the
198** statement that makes them is completed (when the statement handle is
199** passed to sqlite3_reset() or sqlite_finalise()).
rdcf146a772004-02-25 22:51:06 +0000200**
201** SQLite implements the command "DELETE FROM table" without a WHERE clause
202** by dropping and recreating the table. (This is much faster than going
203** through and deleting individual elements form the table.) Because of
204** this optimization, the change count for "DELETE FROM table" will be
205** zero regardless of the number of elements that were originally in the
206** table. To get an accurate count of the number of rows deleted, use
207** "DELETE FROM table WHERE 1" instead.
rdcf146a772004-02-25 22:51:06 +0000208*/
danielk1977b28af712004-06-21 06:50:26 +0000209int sqlite3_total_changes(sqlite3*);
210
drh4c504392000-10-16 22:06:40 +0000211/* This function causes any pending database operation to abort and
212** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000213** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000214** or Ctrl-C where the user wants a long query operation to halt
215** immediately.
216*/
danielk1977f9d64d22004-06-19 08:18:07 +0000217void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000218
drheec553b2000-06-02 01:51:20 +0000219
danielk197761de0d12004-05-27 23:56:16 +0000220/* These functions return true if the given input string comprises
221** one or more complete SQL statements. For the sqlite3_complete() call,
222** the parameter must be a nul-terminated UTF-8 string. For
223** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
224** is required.
drh75897232000-05-29 14:26:00 +0000225**
226** The algorithm is simple. If the last token other than spaces
227** and comments is a semicolon, then return true. otherwise return
228** false.
229*/
danielk19776f8a5032004-05-10 10:34:51 +0000230int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000231int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000232
drh2dfbbca2000-07-28 14:32:48 +0000233/*
234** This routine identifies a callback function that is invoked
235** whenever an attempt is made to open a database table that is
236** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000237** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000238** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000239** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000240** second argument is the name of the locked table and the third
241** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000242** busy callback returns 0, then sqlite3_exec() immediately returns
243** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000244** tries to open the table again and the cycle repeats.
245**
246** The default busy callback is NULL.
247**
248** Sqlite is re-entrant, so the busy handler may start a new query.
249** (It is not clear why anyone would every want to do this, but it
250** is allowed, in theory.) But the busy handler may not close the
251** database. Closing the database from a busy handler will delete
252** data structures out from under the executing query and will
253** probably result in a coredump.
254*/
danielk1977f9d64d22004-06-19 08:18:07 +0000255int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000256
257/*
258** This routine sets a busy handler that sleeps for a while when a
259** table is locked. The handler will sleep multiple times until
260** at least "ms" milleseconds of sleeping have been done. After
261** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000262** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000263**
264** Calling this routine with an argument less than or equal to zero
265** turns off all busy handlers.
266*/
danielk1977f9d64d22004-06-19 08:18:07 +0000267int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000268
drhe3710332000-09-29 13:30:53 +0000269/*
danielk19776f8a5032004-05-10 10:34:51 +0000270** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000271** Instead of invoking a user-supplied callback for each row of the
272** result, this routine remembers each row of the result in memory
273** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000274** query has finished.
275**
276** As an example, suppose the query result where this table:
277**
278** Name | Age
279** -----------------------
280** Alice | 43
281** Bob | 28
282** Cindy | 21
283**
284** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000285** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000286**
287** azResult[0] = "Name";
288** azResult[1] = "Age";
289** azResult[2] = "Alice";
290** azResult[3] = "43";
291** azResult[4] = "Bob";
292** azResult[5] = "28";
293** azResult[6] = "Cindy";
294** azResult[7] = "21";
295**
296** Notice that there is an extra row of data containing the column
297** headers. But the *nrow return value is still 3. *ncolumn is
298** set to 2. In general, the number of values inserted into azResult
299** will be ((*nrow) + 1)*(*ncolumn).
300**
301** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000302** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000303** release the memory that was malloc-ed. Because of the way the
304** malloc() happens, the calling function must not try to call
danielk19776f8a5032004-05-10 10:34:51 +0000305** malloc() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000306** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000307**
danielk19776f8a5032004-05-10 10:34:51 +0000308** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000309*/
danielk19776f8a5032004-05-10 10:34:51 +0000310int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000311 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000312 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000313 char ***resultp, /* Result written to a char *[] that this points to */
314 int *nrow, /* Number of result rows written here */
315 int *ncolumn, /* Number of result columns written here */
316 char **errmsg /* Error msg written here */
317);
318
319/*
danielk19776f8a5032004-05-10 10:34:51 +0000320** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000321*/
danielk19776f8a5032004-05-10 10:34:51 +0000322void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000323
drha18c5682000-10-08 22:20:57 +0000324/*
drh4f26d6c2004-05-26 23:25:30 +0000325** The following routines are variants of the "sprintf()" from the
326** standard C library. The resulting string is written into memory
327** obtained from malloc() so that there is never a possiblity of buffer
328** overflow. These routines also implement some additional formatting
329** options that are useful for constructing SQL statements.
330**
331** The strings returned by these routines should be freed by calling
332** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000333**
334** All of the usual printf formatting options apply. In addition, there
335** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000336** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000337** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000338** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000339** the string.
340**
341** For example, so some string variable contains text as follows:
342**
343** char *zText = "It's a happy day!";
344**
345** We can use this text in an SQL statement as follows:
346**
danielk19776f8a5032004-05-10 10:34:51 +0000347** sqlite3_exec_printf(db, "INSERT INTO table VALUES('%q')",
drha18c5682000-10-08 22:20:57 +0000348** callback1, 0, 0, zText);
349**
350** Because the %q format string is used, the '\'' character in zText
351** is escaped and the SQL generated is as follows:
352**
353** INSERT INTO table1 VALUES('It''s a happy day!')
354**
355** This is correct. Had we used %s instead of %q, the generated SQL
356** would have looked like this:
357**
358** INSERT INTO table1 VALUES('It's a happy day!');
359**
360** This second example is an SQL syntax error. As a general rule you
361** should always use %q instead of %s when inserting text into a string
362** literal.
363*/
danielk19776f8a5032004-05-10 10:34:51 +0000364char *sqlite3_mprintf(const char*,...);
365char *sqlite3_vmprintf(const char*, va_list);
drh4f26d6c2004-05-26 23:25:30 +0000366void sqlite3_free(char *z);
drh5191b7e2002-03-08 02:12:00 +0000367
drh1211de32004-07-26 12:24:22 +0000368#ifndef SQLITE_OMIT_AUTHORIZATION
drh5191b7e2002-03-08 02:12:00 +0000369/*
drhed6c8672003-01-12 18:02:16 +0000370** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000371** callback is invoked (at compile-time, not at run-time) for each
372** attempt to access a column of a table in the database. The callback
373** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
374** SQL statement should be aborted with an error and SQLITE_IGNORE
375** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000376*/
danielk19776f8a5032004-05-10 10:34:51 +0000377int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000378 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000379 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000380 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000381);
drh1211de32004-07-26 12:24:22 +0000382#endif
drhed6c8672003-01-12 18:02:16 +0000383
384/*
385** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000386** be one of the values below. These values signify what kind of operation
387** is to be authorized. The 3rd and 4th parameters to the authorization
388** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000389** codes is used as the second parameter. The 5th parameter is the name
390** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000391** is the name of the inner-most trigger or view that is responsible for
392** the access attempt or NULL if this access attempt is directly from
393** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000394**
395** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000396*/
drh77ad4e42003-01-14 02:49:27 +0000397#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000398#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
399#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
400#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
401#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000402#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000403#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000404#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000405#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
406#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000407#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000408#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000409#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000410#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000411#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000412#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000413#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000414#define SQLITE_DROP_VIEW 17 /* View Name NULL */
415#define SQLITE_INSERT 18 /* Table Name NULL */
416#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
417#define SQLITE_READ 20 /* Table Name Column Name */
418#define SQLITE_SELECT 21 /* NULL NULL */
419#define SQLITE_TRANSACTION 22 /* NULL NULL */
420#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000421#define SQLITE_ATTACH 24 /* Filename NULL */
422#define SQLITE_DETACH 25 /* Database Name NULL */
423
drhed6c8672003-01-12 18:02:16 +0000424
425/*
426** The return value of the authorization function should be one of the
427** following constants:
428*/
429/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
430#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
431#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
432
433/*
danielk19776f8a5032004-05-10 10:34:51 +0000434** Register a function that is called at every invocation of sqlite3_exec()
danielk19774ad17132004-05-21 01:47:26 +0000435** or sqlite3_prepare(). This function can be used (for example) to generate
drhb86ccfb2003-01-28 23:13:10 +0000436** a log file of all SQL executed against a database.
drh18de4822003-01-16 16:28:53 +0000437*/
danielk1977f9d64d22004-06-19 08:18:07 +0000438void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh18de4822003-01-16 16:28:53 +0000439
danielk1977348bb5d2003-10-18 09:37:26 +0000440/*
441** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000442** is invoked periodically during long running calls to sqlite3_exec(),
443** sqlite3_step() and sqlite3_get_table(). An example use for this API is to keep
danielk1977348bb5d2003-10-18 09:37:26 +0000444** a GUI updated during a large query.
445**
446** The progress callback is invoked once for every N virtual machine opcodes,
447** where N is the second argument to this function. The progress callback
448** itself is identified by the third argument to this function. The fourth
449** argument to this function is a void pointer passed to the progress callback
450** function each time it is invoked.
451**
danielk19776f8a5032004-05-10 10:34:51 +0000452** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000453** in less than N opcodes being executed, then the progress callback is not
454** invoked.
455**
danielk1977348bb5d2003-10-18 09:37:26 +0000456** To remove the progress callback altogether, pass NULL as the third
457** argument to this function.
458**
459** If the progress callback returns a result other than 0, then the current
460** query is immediately terminated and any database changes rolled back. If the
461** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000462** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000463**
464******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000465*/
danielk1977f9d64d22004-06-19 08:18:07 +0000466void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000467
drhaa940ea2004-01-15 02:44:03 +0000468/*
469** Register a callback function to be invoked whenever a new transaction
470** is committed. The pArg argument is passed through to the callback.
471** callback. If the callback function returns non-zero, then the commit
472** is converted into a rollback.
473**
474** If another function was previously registered, its pArg value is returned.
475** Otherwise NULL is returned.
476**
477** Registering a NULL function disables the callback.
478**
479******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
480*/
danielk1977f9d64d22004-06-19 08:18:07 +0000481void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000482
drh22fbcb82004-02-01 01:22:50 +0000483/*
drh4f26d6c2004-05-26 23:25:30 +0000484** Open the sqlite database file "filename". The "filename" is UTF-8
485** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
486** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
487** if an error occurs. If the database is opened (or created) successfully,
488** then SQLITE_OK is returned. Otherwise an error code is returned. The
489** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
490** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000491**
drh4f26d6c2004-05-26 23:25:30 +0000492** If the database file does not exist, then a new database is created.
493** The encoding for the database is UTF-8 if sqlite3_open() is called and
494** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000495**
496** Whether or not an error occurs when it is opened, resources associated
497** with the sqlite3* handle should be released by passing it to
498** sqlite3_close() when it is no longer required.
499*/
500int sqlite3_open(
501 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000502 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000503);
danielk197765904932004-05-26 06:18:37 +0000504int sqlite3_open16(
505 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000506 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000507);
danielk1977295ba552004-05-19 10:34:51 +0000508
danielk197765904932004-05-26 06:18:37 +0000509/*
510** Return the error code for the most recent sqlite3_* API call associated
511** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
512** API call was successful.
513**
514** Calls to many sqlite3_* functions set the error code and string returned
515** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
516** (overwriting the previous values). Note that calls to sqlite3_errcode(),
517** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
518** results of future invocations.
519**
520** Assuming no other intervening sqlite3_* API calls are made, the error
521** code returned by this function is associated with the same error as
522** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
523*/
524int sqlite3_errcode(sqlite3 *db);
525
526/*
527** Return a pointer to a UTF-8 encoded string describing in english the
528** error condition for the most recent sqlite3_* API call. The returned
529** string is always terminated by an 0x00 byte.
530**
531** The string "not an error" is returned when the most recent API call was
532** successful.
533*/
534const char *sqlite3_errmsg(sqlite3*);
535
536/*
537** Return a pointer to a UTF-16 native byte order encoded string describing
538** in english the error condition for the most recent sqlite3_* API call.
539** The returned string is always terminated by a pair of 0x00 bytes.
540**
541** The string "not an error" is returned when the most recent API call was
542** successful.
543*/
544const void *sqlite3_errmsg16(sqlite3*);
545
546/*
547** An instance of the following opaque structure is used to represent
548** a compiled SQL statment.
549*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000550typedef struct sqlite3_stmt sqlite3_stmt;
551
danielk1977e3209e42004-05-20 01:40:18 +0000552/*
danielk197765904932004-05-26 06:18:37 +0000553** To execute an SQL query, it must first be compiled into a byte-code
554** program using one of the following routines. The only difference between
555** them is that the second argument, specifying the SQL statement to
556** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
557** function and UTF-16 for sqlite3_prepare16().
558**
559** The first parameter "db" is an SQLite database handle. The second
560** parameter "zSql" is the statement to be compiled, encoded as either
561** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
562** than zero, then zSql is read up to the first nul terminator. If
563** "nBytes" is not less than zero, then it is the length of the string zSql
564** in bytes (not characters).
565**
566** *pzTail is made to point to the first byte past the end of the first
567** SQL statement in zSql. This routine only compiles the first statement
568** in zSql, so *pzTail is left pointing to what remains uncompiled.
569**
570** *ppStmt is left pointing to a compiled SQL statement that can be
571** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
572** set to NULL. If the input text contained no SQL (if the input is and
573** empty string or a comment) then *ppStmt is set to NULL.
574**
575** On success, SQLITE_OK is returned. Otherwise an error code is returned.
576*/
577int sqlite3_prepare(
578 sqlite3 *db, /* Database handle */
579 const char *zSql, /* SQL statement, UTF-8 encoded */
580 int nBytes, /* Length of zSql in bytes. */
581 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
582 const char **pzTail /* OUT: Pointer to unused portion of zSql */
583);
584int sqlite3_prepare16(
585 sqlite3 *db, /* Database handle */
586 const void *zSql, /* SQL statement, UTF-16 encoded */
587 int nBytes, /* Length of zSql in bytes. */
588 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
589 const void **pzTail /* OUT: Pointer to unused portion of zSql */
590);
591
592/*
drhf4479502004-05-27 03:12:53 +0000593** Pointers to the following two opaque structures are used to communicate
594** with the implementations of user-defined functions.
595*/
596typedef struct sqlite3_context sqlite3_context;
597typedef struct Mem sqlite3_value;
598
599/*
drh4f26d6c2004-05-26 23:25:30 +0000600** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
601** one or more literals can be replace by a wildcard "?" or ":N:" where
602** N is an integer. These value of these wildcard literals can be set
603** using the routines listed below.
604**
605** In every case, the first parameter is a pointer to the sqlite3_stmt
606** structure returned from sqlite3_prepare(). The second parameter is the
607** index of the wildcard. The first "?" has an index of 1. ":N:" wildcards
608** use the index N.
609**
drh900dfba2004-07-21 15:21:36 +0000610** The fifth parameter to sqlite3_bind_blob(), sqlite3_bind_text(), and
611** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or
612** text after SQLite has finished with it. If the fifth argument is the
613** special value SQLITE_STATIC, then the library assumes that the information
614** is in static, unmanaged space and does not need to be freed. If the
615** fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its
616** own private copy of the data.
drh4f26d6c2004-05-26 23:25:30 +0000617**
618** The sqlite3_bind_* routine must be called before sqlite3_step() after
619** an sqlite3_prepare() or sqlite3_reset(). Unbound wildcards are interpreted
620** as NULL.
621*/
danielk1977d8123362004-06-12 09:25:12 +0000622int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000623int sqlite3_bind_double(sqlite3_stmt*, int, double);
624int sqlite3_bind_int(sqlite3_stmt*, int, int);
drhefad9992004-06-22 12:13:55 +0000625int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64);
drhf4479502004-05-27 03:12:53 +0000626int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000627int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
628int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000629int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000630
631/*
drh75f6a032004-07-15 14:15:00 +0000632** Return the number of wildcards in a compiled SQL statement. This
633** routine was added to support DBD::SQLite.
634**
635**** EXPERIMENTAL *****
636*/
637int sqlite3_bind_parameter_count(sqlite3_stmt*);
638
639/*
danielk197765904932004-05-26 06:18:37 +0000640** Return the number of columns in the result set returned by the compiled
641** SQL statement. This routine returns 0 if pStmt is an SQL statement
642** that does not return data (for example an UPDATE).
643*/
644int sqlite3_column_count(sqlite3_stmt *pStmt);
645
646/*
647** The first parameter is a compiled SQL statement. This function returns
648** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000649** second function parameter. The string returned is UTF-8 for
650** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000651*/
652const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000653const void *sqlite3_column_name16(sqlite3_stmt*,int);
654
655/*
656** The first parameter is a compiled SQL statement. If this statement
657** is a SELECT statement, the Nth column of the returned result set
658** of the SELECT is a table column then the declared type of the table
659** column is returned. If the Nth column of the result set is not at table
660** column, then a NULL pointer is returned. The returned string is always
661** UTF-8 encoded. For example, in the database schema:
662**
663** CREATE TABLE t1(c1 VARIANT);
664**
665** And the following statement compiled:
666**
667** SELECT c1 + 1, 0 FROM t1;
668**
669** Then this routine would return the string "VARIANT" for the second
670** result column (i==1), and a NULL pointer for the first result column
671** (i==0).
672*/
673const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
674
675/*
676** The first parameter is a compiled SQL statement. If this statement
677** is a SELECT statement, the Nth column of the returned result set
678** of the SELECT is a table column then the declared type of the table
679** column is returned. If the Nth column of the result set is not at table
680** column, then a NULL pointer is returned. The returned string is always
681** UTF-16 encoded. For example, in the database schema:
682**
drh4f26d6c2004-05-26 23:25:30 +0000683** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000684**
685** And the following statement compiled:
686**
687** SELECT c1 + 1, 0 FROM t1;
688**
drh4f26d6c2004-05-26 23:25:30 +0000689** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000690** result column (i==1), and a NULL pointer for the first result column
691** (i==0).
692*/
693const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
694
danielk1977106bb232004-05-21 10:08:53 +0000695/*
696** After an SQL query has been compiled with a call to either
697** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
698** called one or more times to execute the statement.
699**
700** The return value will be either SQLITE_BUSY, SQLITE_DONE,
701** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
702**
703** SQLITE_BUSY means that the database engine attempted to open
704** a locked database and there is no busy callback registered.
705** Call sqlite3_step() again to retry the open.
706**
707** SQLITE_DONE means that the statement has finished executing
708** successfully. sqlite3_step() should not be called again on this virtual
709** machine.
710**
711** If the SQL statement being executed returns any data, then
712** SQLITE_ROW is returned each time a new row of data is ready
713** for processing by the caller. The values may be accessed using
714** the sqlite3_column_*() functions described below. sqlite3_step()
715** is called again to retrieve the next row of data.
716**
717** SQLITE_ERROR means that a run-time error (such as a constraint
718** violation) has occurred. sqlite3_step() should not be called again on
719** the VM. More information may be found by calling sqlite3_errmsg().
720**
721** SQLITE_MISUSE means that the this routine was called inappropriately.
722** Perhaps it was called on a virtual machine that had already been
723** finalized or on one that had previously returned SQLITE_ERROR or
724** SQLITE_DONE. Or it could be the case the the same database connection
725** is being used simulataneously by two or more threads.
726*/
danielk197717240fd2004-05-26 00:07:25 +0000727int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000728
danielk1977106bb232004-05-21 10:08:53 +0000729/*
730** Return the number of values in the current row of the result set.
731**
732** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
733** will return the same value as the sqlite3_column_count() function.
734** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
735** error code, or before sqlite3_step() has been called on a
736** compiled SQL statement, this routine returns zero.
737*/
danielk197793d46752004-05-23 13:30:58 +0000738int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000739
drh4f26d6c2004-05-26 23:25:30 +0000740/*
741** Values are stored in the database in one of the following fundamental
742** types.
743*/
drh9c054832004-05-31 18:51:57 +0000744#define SQLITE_INTEGER 1
745#define SQLITE_FLOAT 2
746#define SQLITE_TEXT 3
747#define SQLITE_BLOB 4
748#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000749
danielk1977106bb232004-05-21 10:08:53 +0000750/*
drh4f26d6c2004-05-26 23:25:30 +0000751** The next group of routines returns information about the information
752** in a single column of the current result row of a query. In every
753** case the first parameter is a pointer to the SQL statement that is being
754** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
755** the second argument is the index of the column for which information
756** should be returned. iCol is zero-indexed. The left-most column as an
757** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000758**
drh4f26d6c2004-05-26 23:25:30 +0000759** If the SQL statement is not currently point to a valid row, or if the
760** the colulmn index is out of range, the result is undefined.
761**
762** These routines attempt to convert the value where appropriate. For
763** example, if the internal representation is FLOAT and a text result
764** is requested, sprintf() is used internally to do the conversion
765** automatically. The following table details the conversions that
766** are applied:
767**
768** Internal Type Requested Type Conversion
769** ------------- -------------- --------------------------
770** NULL INTEGER Result is 0
771** NULL FLOAT Result is 0.0
772** NULL TEXT Result is an empty string
773** NULL BLOB Result is a zero-length BLOB
774** INTEGER FLOAT Convert from integer to float
775** INTEGER TEXT ASCII rendering of the integer
776** INTEGER BLOB Same as for INTEGER->TEXT
777** FLOAT INTEGER Convert from float to integer
778** FLOAT TEXT ASCII rendering of the float
779** FLOAT BLOB Same as FLOAT->TEXT
780** TEXT INTEGER Use atoi()
781** TEXT FLOAT Use atof()
782** TEXT BLOB No change
783** BLOB INTEGER Convert to TEXT then use atoi()
784** BLOB FLOAT Convert to TEXT then use atof()
785** BLOB TEXT Add a \000 terminator if needed
786**
787** The following access routines are provided:
788**
789** _type() Return the datatype of the result. This is one of
790** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
791** or SQLITE_NULL.
792** _blob() Return the value of a BLOB.
793** _bytes() Return the number of bytes in a BLOB value or the number
794** of bytes in a TEXT value represented as UTF-8. The \000
795** terminator is included in the byte count for TEXT values.
796** _bytes16() Return the number of bytes in a BLOB value or the number
797** of bytes in a TEXT value represented as UTF-16. The \u0000
798** terminator is included in the byte count for TEXT values.
799** _double() Return a FLOAT value.
800** _int() Return an INTEGER value in the host computer's native
801** integer representation. This might be either a 32- or 64-bit
802** integer depending on the host.
803** _int64() Return an INTEGER value as a 64-bit signed integer.
804** _text() Return the value as UTF-8 text.
805** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000806*/
drhf4479502004-05-27 03:12:53 +0000807const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
808int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
809int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
810double sqlite3_column_double(sqlite3_stmt*, int iCol);
811int sqlite3_column_int(sqlite3_stmt*, int iCol);
drhefad9992004-06-22 12:13:55 +0000812sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +0000813const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
814const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000815int sqlite3_column_type(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000816
danielk197765904932004-05-26 06:18:37 +0000817/*
818** The sqlite3_finalize() function is called to delete a compiled
819** SQL statement obtained by a previous call to sqlite3_prepare()
820** or sqlite3_prepare16(). If the statement was executed successfully, or
821** not executed at all, then SQLITE_OK is returned. If execution of the
822** statement failed then an error code is returned.
823**
824** This routine can be called at any point during the execution of the
825** virtual machine. If the virtual machine has not completed execution
826** when this routine is called, that is like encountering an error or
827** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
828** rolled back and transactions cancelled, depending on the circumstances,
829** and the result code returned will be SQLITE_ABORT.
830*/
831int sqlite3_finalize(sqlite3_stmt *pStmt);
832
833/*
834** The sqlite3_reset() function is called to reset a compiled SQL
835** statement obtained by a previous call to sqlite3_prepare() or
836** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
837** Any SQL statement variables that had values bound to them using
838** the sqlite3_bind_*() API retain their values.
839*/
840int sqlite3_reset(sqlite3_stmt *pStmt);
841
842/*
danielk197765904932004-05-26 06:18:37 +0000843** The following two functions are used to add user functions or aggregates
844** implemented in C to the SQL langauge interpreted by SQLite. The
845** difference only between the two is that the second parameter, the
846** name of the (scalar) function or aggregate, is encoded in UTF-8 for
847** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
848**
849** The first argument is the database handle that the new function or
850** aggregate is to be added to. If a single program uses more than one
851** database handle internally, then user functions or aggregates must
852** be added individually to each database handle with which they will be
853** used.
854**
855** The third parameter is the number of arguments that the function or
856** aggregate takes. If this parameter is negative, then the function or
857** aggregate may take any number of arguments.
858**
danielk1977d8123362004-06-12 09:25:12 +0000859** The fourth parameter is one of SQLITE_UTF* values defined below,
860** indicating the encoding that the function is most likely to handle
861** values in. This does not change the behaviour of the programming
862** interface. However, if two versions of the same function are registered
863** with different encoding values, SQLite invokes the version likely to
864** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +0000865**
danielk197765904932004-05-26 06:18:37 +0000866** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
867** pointers to user implemented C functions that implement the user
868** function or aggregate. A scalar function requires an implementation of
869** the xFunc callback only, NULL pointers should be passed as the xStep
870** and xFinal parameters. An aggregate function requires an implementation
871** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
872** existing user function or aggregate, pass NULL for all three function
873** callback. Specifying an inconstent set of callback values, such as an
874** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
875** returned.
876*/
877int sqlite3_create_function(
878 sqlite3 *,
879 const char *zFunctionName,
880 int nArg,
881 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000882 void*,
883 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
884 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
885 void (*xFinal)(sqlite3_context*)
886);
887int sqlite3_create_function16(
888 sqlite3*,
889 const void *zFunctionName,
890 int nArg,
891 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000892 void*,
893 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
894 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
895 void (*xFinal)(sqlite3_context*)
896);
897
898/*
danielk197765904932004-05-26 06:18:37 +0000899** The next routine returns the number of calls to xStep for a particular
900** aggregate function instance. The current call to xStep counts so this
901** routine always returns at least 1.
902*/
903int sqlite3_aggregate_count(sqlite3_context*);
904
danielk19770ffba6b2004-05-24 09:10:10 +0000905/*
drh4f26d6c2004-05-26 23:25:30 +0000906** The next group of routines returns information about parameters to
907** a user-defined function. Function implementations use these routines
908** to access their parameters. These routines are the same as the
909** sqlite3_column_* routines except that these routines take a single
910** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
911** column number.
danielk19770ffba6b2004-05-24 09:10:10 +0000912*/
drhf4479502004-05-27 03:12:53 +0000913const void *sqlite3_value_blob(sqlite3_value*);
914int sqlite3_value_bytes(sqlite3_value*);
915int sqlite3_value_bytes16(sqlite3_value*);
916double sqlite3_value_double(sqlite3_value*);
917int sqlite3_value_int(sqlite3_value*);
drhefad9992004-06-22 12:13:55 +0000918sqlite_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +0000919const unsigned char *sqlite3_value_text(sqlite3_value*);
920const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +0000921const void *sqlite3_value_text16le(sqlite3_value*);
922const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +0000923int sqlite3_value_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +0000924
925/*
danielk19770ae8b832004-05-25 12:05:56 +0000926** Aggregate functions use the following routine to allocate
927** a structure for storing their state. The first time this routine
928** is called for a particular aggregate, a new structure of size nBytes
929** is allocated, zeroed, and returned. On subsequent calls (for the
930** same aggregate instance) the same buffer is returned. The implementation
931** of the aggregate can use the returned buffer to accumulate data.
932**
933** The buffer allocated is freed automatically by SQLite.
934*/
drh4f26d6c2004-05-26 23:25:30 +0000935void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +0000936
937/*
938** The pUserData parameter to the sqlite3_create_function() and
939** sqlite3_create_aggregate() routines used to register user functions
940** is available to the implementation of the function using this
941** call.
942*/
943void *sqlite3_user_data(sqlite3_context*);
944
945/*
danielk1977682f68b2004-06-05 10:22:17 +0000946** The following two functions may be used by scalar user functions to
947** associate meta-data with argument values. If the same value is passed to
948** multiple invocations of the user-function during query execution, under
949** some circumstances the associated meta-data may be preserved. This may
950** be used, for example, to add a regular-expression matching scalar
951** function. The compiled version of the regular expression is stored as
952** meta-data associated with the SQL value passed as the regular expression
953** pattern.
954**
955** Calling sqlite3_get_auxdata() returns a pointer to the meta data
956** associated with the Nth argument value to the current user function
957** call, where N is the second parameter. If no meta-data has been set for
958** that value, then a NULL pointer is returned.
959**
960** The sqlite3_set_auxdata() is used to associate meta data with a user
961** function argument. The third parameter is a pointer to the meta data
962** to be associated with the Nth user function argument value. The fourth
963** parameter specifies a 'delete function' that will be called on the meta
964** data pointer to release it when it is no longer required. If the delete
965** function pointer is NULL, it is not invoked.
966**
967** In practice, meta-data is preserved between function calls for
968** expressions that are constant at compile time. This includes literal
969** values and SQL variables.
970*/
971void *sqlite3_get_auxdata(sqlite3_context*, int);
972void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
973
drha2854222004-06-17 19:04:17 +0000974
975/*
976** These are special value for the destructor that is passed in as the
977** final argument to routines like sqlite3_result_blob(). If the destructor
978** argument is SQLITE_STATIC, it means that the content pointer is constant
979** and will never change. It does not need to be destroyed. The
980** SQLITE_TRANSIENT value means that the content will likely change in
981** the near future and that SQLite should make its own private copy of
982** the content before returning.
983*/
danielk1977d8123362004-06-12 09:25:12 +0000984#define SQLITE_STATIC ((void(*)(void *))0)
985#define SQLITE_TRANSIENT ((void(*)(void *))-1)
986
danielk1977682f68b2004-06-05 10:22:17 +0000987/*
drh4f26d6c2004-05-26 23:25:30 +0000988** User-defined functions invoke the following routines in order to
989** set their return value.
danielk19777e18c252004-05-25 11:47:24 +0000990*/
danielk1977d8123362004-06-12 09:25:12 +0000991void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +0000992void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +0000993void sqlite3_result_error(sqlite3_context*, const char*, int);
994void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +0000995void sqlite3_result_int(sqlite3_context*, int);
drhefad9992004-06-22 12:13:55 +0000996void sqlite3_result_int64(sqlite3_context*, sqlite_int64);
drh4f26d6c2004-05-26 23:25:30 +0000997void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +0000998void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
999void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
1000void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
1001void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001002void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +00001003
drh52619df2004-06-11 17:48:02 +00001004/*
1005** These are the allowed values for the eTextRep argument to
1006** sqlite3_create_collation and sqlite3_create_function.
1007*/
danielk1977466be562004-06-10 02:16:01 +00001008#define SQLITE_UTF8 1
danielk1977dc8453f2004-06-12 00:42:34 +00001009#define SQLITE_UTF16LE 2
1010#define SQLITE_UTF16BE 3
1011#define SQLITE_UTF16 4 /* Use native byte order */
drh52619df2004-06-11 17:48:02 +00001012#define SQLITE_ANY 5 /* sqlite3_create_function only */
danielk1977466be562004-06-10 02:16:01 +00001013
danielk19777cedc8d2004-06-10 10:50:08 +00001014/*
1015** These two functions are used to add new collation sequences to the
1016** sqlite3 handle specified as the first argument.
1017**
1018** The name of the new collation sequence is specified as a UTF-8 string
1019** for sqlite3_create_collation() and a UTF-16 string for
1020** sqlite3_create_collation16(). In both cases the name is passed as the
1021** second function argument.
1022**
1023** The third argument must be one of the constants SQLITE_UTF8,
1024** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1025** routine expects to be passed pointers to strings encoded using UTF-8,
1026** UTF-16 little-endian or UTF-16 big-endian respectively.
1027**
1028** A pointer to the user supplied routine must be passed as the fifth
1029** argument. If it is NULL, this is the same as deleting the collation
1030** sequence (so that SQLite cannot call it anymore). Each time the user
1031** supplied function is invoked, it is passed a copy of the void* passed as
1032** the fourth argument to sqlite3_create_collation() or
1033** sqlite3_create_collation16() as its first parameter.
1034**
1035** The remaining arguments to the user-supplied routine are two strings,
1036** each represented by a [length, data] pair and encoded in the encoding
1037** that was passed as the third argument when the collation sequence was
1038** registered. The user routine should return negative, zero or positive if
1039** the first string is less than, equal to, or greater than the second
1040** string. i.e. (STRING1 - STRING2).
1041*/
danielk19770202b292004-06-09 09:55:16 +00001042int sqlite3_create_collation(
1043 sqlite3*,
1044 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001045 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001046 void*,
1047 int(*xCompare)(void*,int,const void*,int,const void*)
1048);
1049int sqlite3_create_collation16(
1050 sqlite3*,
1051 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001052 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001053 void*,
1054 int(*xCompare)(void*,int,const void*,int,const void*)
1055);
1056
danielk19777cedc8d2004-06-10 10:50:08 +00001057/*
1058** To avoid having to register all collation sequences before a database
1059** can be used, a single callback function may be registered with the
1060** database handle to be called whenever an undefined collation sequence is
1061** required.
1062**
1063** If the function is registered using the sqlite3_collation_needed() API,
1064** then it is passed the names of undefined collation sequences as strings
1065** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1066** are passed as UTF-16 in machine native byte order. A call to either
1067** function replaces any existing callback.
1068**
1069** When the user-function is invoked, the first argument passed is a copy
1070** of the second argument to sqlite3_collation_needed() or
1071** sqlite3_collation_needed16(). The second argument is the database
1072** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1073** SQLITE_UTF16LE, indicating the most desirable form of the collation
1074** sequence function required. The fourth parameter is the name of the
1075** required collation sequence.
1076**
1077** The collation sequence is returned to SQLite by a collation-needed
1078** callback using the sqlite3_create_collation() or
1079** sqlite3_create_collation16() APIs, described above.
1080*/
1081int sqlite3_collation_needed(
1082 sqlite3*,
1083 void*,
1084 void(*)(void*,sqlite3*,int eTextRep,const char*)
1085);
1086int sqlite3_collation_needed16(
1087 sqlite3*,
1088 void*,
1089 void(*)(void*,sqlite3*,int eTextRep,const void*)
1090);
1091
drh2011d5f2004-07-22 02:40:37 +00001092/*
1093** Specify the key for an encrypted database. This routine should be
1094** called right after sqlite3_open().
1095**
1096** The code to implement this API is not available in the public release
1097** of SQLite.
1098*/
1099int sqlite3_key(
1100 sqlite3 *db, /* Database to be rekeyed */
1101 const void *pKey, int nKey /* The key */
1102);
1103
1104/*
1105** Change the key on an open database. If the current database is not
1106** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the
1107** database is decrypted.
1108**
1109** The code to implement this API is not available in the public release
1110** of SQLite.
1111*/
1112int sqlite3_rekey(
1113 sqlite3 *db, /* Database to be rekeyed */
1114 const void *pKey, int nKey /* The new key */
1115);
danielk19770202b292004-06-09 09:55:16 +00001116
drh382c0242001-10-06 16:33:02 +00001117#ifdef __cplusplus
1118} /* End of the 'extern "C"' block */
1119#endif
danielk19774adee202004-05-08 08:23:19 +00001120#endif