blob: d801b33b7a49fa3a6123978fdfc3fe11275a0ee6 [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**
drh3f4fedb2004-05-31 19:34:33 +000015** @(#) $Id: sqlite.h.in,v 1.87 2004/05/31 19:34:33 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/*
drh297ecf12001-04-05 15:57:13 +000041** The SQLITE_UTF8 macro is defined if the library expects to see
42** UTF-8 encoded data. The SQLITE_ISO8859 macro is defined if the
43** iso8859 encoded should be used.
44*/
45#define SQLITE_--ENCODING-- 1
46
47/*
48** The following constant holds one of two strings, "UTF-8" or "iso8859",
49** depending on which character encoding the SQLite library expects to
50** see. The character encoding makes a difference for the LIKE and GLOB
51** operators and for the LENGTH() and SUBSTR() functions.
52*/
danielk19776f8a5032004-05-10 10:34:51 +000053extern const char sqlite3_encoding[];
drh297ecf12001-04-05 15:57:13 +000054
55/*
drh75897232000-05-29 14:26:00 +000056** Each open sqlite database is represented by an instance of the
57** following opaque structure.
58*/
59typedef struct sqlite sqlite;
danielk197765904932004-05-26 06:18:37 +000060typedef struct sqlite sqlite3;
61
drh75897232000-05-29 14:26:00 +000062
63/*
drh75897232000-05-29 14:26:00 +000064** A function to close the database.
65**
66** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +000067** returned from sqlite3_open() and the corresponding database will by closed.
drh75897232000-05-29 14:26:00 +000068*/
danielk19776f8a5032004-05-10 10:34:51 +000069void sqlite3_close(sqlite *);
drh75897232000-05-29 14:26:00 +000070
71/*
72** The type for a callback function.
73*/
74typedef int (*sqlite_callback)(void*,int,char**, char**);
75
76/*
77** A function to executes one or more statements of SQL.
78**
79** If one or more of the SQL statements are queries, then
80** the callback function specified by the 3rd parameter is
81** invoked once for each row of the query result. This callback
82** should normally return 0. If the callback returns a non-zero
83** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +000084** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +000085**
86** The 4th parameter is an arbitrary pointer that is passed
87** to the callback function as its first parameter.
88**
89** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +000090** columns in the query result. The 3rd parameter to the callback
91** is an array of strings holding the values for each column.
92** The 4th parameter to the callback is an array of strings holding
93** the names of each column.
drh75897232000-05-29 14:26:00 +000094**
95** The callback function may be NULL, even for queries. A NULL
96** callback is not an error. It just means that no callback
97** will be invoked.
98**
99** If an error occurs while parsing or evaluating the SQL (but
100** not while executing the callback) then an appropriate error
101** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +0000102** *errmsg is made to point to that message. The calling function
103** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +0000104** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +0000105** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +0000106**
107** The return value is is SQLITE_OK if there are no errors and
108** some other return code if there is an error. The particular
109** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +0000110**
111** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000112** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +0000113** behavior can be modified somewhat using the sqlite3_busy_handler()
114** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000115*/
danielk19776f8a5032004-05-10 10:34:51 +0000116int sqlite3_exec(
drh75897232000-05-29 14:26:00 +0000117 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000118 const char *sql, /* SQL to be executed */
drh75897232000-05-29 14:26:00 +0000119 sqlite_callback, /* Callback function */
120 void *, /* 1st argument to callback function */
121 char **errmsg /* Error msg written here */
122);
123
drh58b95762000-06-02 01:17:37 +0000124/*
danielk19776f8a5032004-05-10 10:34:51 +0000125** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000126*/
drh717e6402001-09-27 03:22:32 +0000127#define SQLITE_OK 0 /* Successful result */
128#define SQLITE_ERROR 1 /* SQL error or missing database */
129#define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */
130#define SQLITE_PERM 3 /* Access permission denied */
131#define SQLITE_ABORT 4 /* Callback routine requested an abort */
132#define SQLITE_BUSY 5 /* The database file is locked */
133#define SQLITE_LOCKED 6 /* A table in the database is locked */
134#define SQLITE_NOMEM 7 /* A malloc() failed */
135#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000136#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000137#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
138#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
139#define SQLITE_NOTFOUND 12 /* (Internal Only) Table or record not found */
140#define SQLITE_FULL 13 /* Insertion failed because database is full */
141#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
142#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000143#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000144#define SQLITE_SCHEMA 17 /* The database schema changed */
145#define SQLITE_TOOBIG 18 /* Too much data for one row of a table */
146#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000147#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000148#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000149#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000150#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000151#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000152#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000153#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000154#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
155#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh717e6402001-09-27 03:22:32 +0000156
drhaf9ff332002-01-16 21:00:27 +0000157/*
158** Each entry in an SQLite table has a unique integer key. (The key is
159** the value of the INTEGER PRIMARY KEY column if there is such a column,
160** otherwise the key is generated at random. The unique key is always
161** available as the ROWID, OID, or _ROWID_ column.) The following routine
162** returns the integer key of the most recent insert in the database.
163**
164** This function is similar to the mysql_insert_id() function from MySQL.
165*/
drhf9b596e2004-05-26 16:54:42 +0000166long long int sqlite3_last_insert_rowid(sqlite*);
drhaf9ff332002-01-16 21:00:27 +0000167
drhc8d30ac2002-04-12 10:08:59 +0000168/*
169** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000170** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000171**
172** All changes are counted, even if they were later undone by a
173** ROLLBACK or ABORT. Except, changes associated with creating and
174** dropping tables are not counted.
175**
danielk19776f8a5032004-05-10 10:34:51 +0000176** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000177** in the inner, recursive call are counted together with the changes
178** in the outer call.
179**
180** SQLite implements the command "DELETE FROM table" without a WHERE clause
181** by dropping and recreating the table. (This is much faster than going
182** through and deleting individual elements form the table.) Because of
183** this optimization, the change count for "DELETE FROM table" will be
184** zero regardless of the number of elements that were originally in the
185** table. To get an accurate count of the number of rows deleted, use
186** "DELETE FROM table WHERE 1" instead.
187*/
danielk19776f8a5032004-05-10 10:34:51 +0000188int sqlite3_changes(sqlite*);
drhc8d30ac2002-04-12 10:08:59 +0000189
rdcf146a772004-02-25 22:51:06 +0000190/*
191** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000192** by the last INSERT, UPDATE, or DELETE statment executed by sqlite3_exec(),
rdcf146a772004-02-25 22:51:06 +0000193** or by the last VM to run to completion. The change count is not updated
194** by SQL statements other than INSERT, UPDATE or DELETE.
195**
196** Changes are counted, even if they are later undone by a ROLLBACK or
197** ABORT. Changes associated with trigger programs that execute as a
198** result of the INSERT, UPDATE, or DELETE statement are not counted.
199**
danielk19776f8a5032004-05-10 10:34:51 +0000200** If a callback invokes sqlite3_exec() recursively, then the changes
rdcf146a772004-02-25 22:51:06 +0000201** in the inner, recursive call are counted together with the changes
202** in the outer call.
203**
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.
211**
212******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
213*/
danielk19776f8a5032004-05-10 10:34:51 +0000214int sqlite3_last_statement_changes(sqlite*);
rdcf146a772004-02-25 22:51:06 +0000215
drh717e6402001-09-27 03:22:32 +0000216/* If the parameter to this routine is one of the return value constants
217** defined above, then this routine returns a constant text string which
218** descripts (in English) the meaning of the return value.
219*/
danielk19776f8a5032004-05-10 10:34:51 +0000220const char *sqlite3_error_string(int);
221#define sqliteErrStr sqlite3_error_string /* Legacy. Do not use in new code. */
drh4c504392000-10-16 22:06:40 +0000222
223/* This function causes any pending database operation to abort and
224** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000225** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000226** or Ctrl-C where the user wants a long query operation to halt
227** immediately.
228*/
danielk19776f8a5032004-05-10 10:34:51 +0000229void sqlite3_interrupt(sqlite*);
drh4c504392000-10-16 22:06:40 +0000230
drheec553b2000-06-02 01:51:20 +0000231
danielk197761de0d12004-05-27 23:56:16 +0000232/* These functions return true if the given input string comprises
233** one or more complete SQL statements. For the sqlite3_complete() call,
234** the parameter must be a nul-terminated UTF-8 string. For
235** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
236** is required.
drh75897232000-05-29 14:26:00 +0000237**
238** The algorithm is simple. If the last token other than spaces
239** and comments is a semicolon, then return true. otherwise return
240** false.
241*/
danielk19776f8a5032004-05-10 10:34:51 +0000242int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000243int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000244
drh2dfbbca2000-07-28 14:32:48 +0000245/*
246** This routine identifies a callback function that is invoked
247** whenever an attempt is made to open a database table that is
248** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000249** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000250** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000251** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000252** second argument is the name of the locked table and the third
253** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000254** busy callback returns 0, then sqlite3_exec() immediately returns
255** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000256** tries to open the table again and the cycle repeats.
257**
258** The default busy callback is NULL.
259**
260** Sqlite is re-entrant, so the busy handler may start a new query.
261** (It is not clear why anyone would every want to do this, but it
262** is allowed, in theory.) But the busy handler may not close the
263** database. Closing the database from a busy handler will delete
264** data structures out from under the executing query and will
265** probably result in a coredump.
266*/
danielk19776f8a5032004-05-10 10:34:51 +0000267void sqlite3_busy_handler(sqlite*, int(*)(void*,const char*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000268
269/*
270** This routine sets a busy handler that sleeps for a while when a
271** table is locked. The handler will sleep multiple times until
272** at least "ms" milleseconds of sleeping have been done. After
273** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000274** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000275**
276** Calling this routine with an argument less than or equal to zero
277** turns off all busy handlers.
278*/
danielk19776f8a5032004-05-10 10:34:51 +0000279void sqlite3_busy_timeout(sqlite*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000280
drhe3710332000-09-29 13:30:53 +0000281/*
danielk19776f8a5032004-05-10 10:34:51 +0000282** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000283** Instead of invoking a user-supplied callback for each row of the
284** result, this routine remembers each row of the result in memory
285** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000286** query has finished.
287**
288** As an example, suppose the query result where this table:
289**
290** Name | Age
291** -----------------------
292** Alice | 43
293** Bob | 28
294** Cindy | 21
295**
296** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000297** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000298**
299** azResult[0] = "Name";
300** azResult[1] = "Age";
301** azResult[2] = "Alice";
302** azResult[3] = "43";
303** azResult[4] = "Bob";
304** azResult[5] = "28";
305** azResult[6] = "Cindy";
306** azResult[7] = "21";
307**
308** Notice that there is an extra row of data containing the column
309** headers. But the *nrow return value is still 3. *ncolumn is
310** set to 2. In general, the number of values inserted into azResult
311** will be ((*nrow) + 1)*(*ncolumn).
312**
313** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000314** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000315** release the memory that was malloc-ed. Because of the way the
316** malloc() happens, the calling function must not try to call
danielk19776f8a5032004-05-10 10:34:51 +0000317** malloc() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000318** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000319**
danielk19776f8a5032004-05-10 10:34:51 +0000320** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000321*/
danielk19776f8a5032004-05-10 10:34:51 +0000322int sqlite3_get_table(
drhe3710332000-09-29 13:30:53 +0000323 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000324 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000325 char ***resultp, /* Result written to a char *[] that this points to */
326 int *nrow, /* Number of result rows written here */
327 int *ncolumn, /* Number of result columns written here */
328 char **errmsg /* Error msg written here */
329);
330
331/*
danielk19776f8a5032004-05-10 10:34:51 +0000332** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000333*/
danielk19776f8a5032004-05-10 10:34:51 +0000334void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000335
drha18c5682000-10-08 22:20:57 +0000336/*
drh4f26d6c2004-05-26 23:25:30 +0000337** The following routines are variants of the "sprintf()" from the
338** standard C library. The resulting string is written into memory
339** obtained from malloc() so that there is never a possiblity of buffer
340** overflow. These routines also implement some additional formatting
341** options that are useful for constructing SQL statements.
342**
343** The strings returned by these routines should be freed by calling
344** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000345**
346** All of the usual printf formatting options apply. In addition, there
347** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000348** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000349** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000350** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000351** the string.
352**
353** For example, so some string variable contains text as follows:
354**
355** char *zText = "It's a happy day!";
356**
357** We can use this text in an SQL statement as follows:
358**
danielk19776f8a5032004-05-10 10:34:51 +0000359** sqlite3_exec_printf(db, "INSERT INTO table VALUES('%q')",
drha18c5682000-10-08 22:20:57 +0000360** callback1, 0, 0, zText);
361**
362** Because the %q format string is used, the '\'' character in zText
363** is escaped and the SQL generated is as follows:
364**
365** INSERT INTO table1 VALUES('It''s a happy day!')
366**
367** This is correct. Had we used %s instead of %q, the generated SQL
368** would have looked like this:
369**
370** INSERT INTO table1 VALUES('It's a happy day!');
371**
372** This second example is an SQL syntax error. As a general rule you
373** should always use %q instead of %s when inserting text into a string
374** literal.
375*/
danielk19776f8a5032004-05-10 10:34:51 +0000376char *sqlite3_mprintf(const char*,...);
377char *sqlite3_vmprintf(const char*, va_list);
drh4f26d6c2004-05-26 23:25:30 +0000378void sqlite3_free(char *z);
drh5191b7e2002-03-08 02:12:00 +0000379
380/*
danielk19776f8a5032004-05-10 10:34:51 +0000381** Windows systems need functions to call to return the sqlite3_version
382** and sqlite3_encoding strings.
drh5191b7e2002-03-08 02:12:00 +0000383*/
danielk19776f8a5032004-05-10 10:34:51 +0000384const char *sqlite3_libversion(void);
385const char *sqlite3_libencoding(void);
drh5191b7e2002-03-08 02:12:00 +0000386
387/*
drhed6c8672003-01-12 18:02:16 +0000388** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000389** callback is invoked (at compile-time, not at run-time) for each
390** attempt to access a column of a table in the database. The callback
391** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
392** SQL statement should be aborted with an error and SQLITE_IGNORE
393** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000394*/
danielk19776f8a5032004-05-10 10:34:51 +0000395int sqlite3_set_authorizer(
drhed6c8672003-01-12 18:02:16 +0000396 sqlite*,
drhe22a3342003-04-22 20:30:37 +0000397 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000398 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000399);
400
401/*
402** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000403** be one of the values below. These values signify what kind of operation
404** is to be authorized. The 3rd and 4th parameters to the authorization
405** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000406** codes is used as the second parameter. The 5th parameter is the name
407** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000408** is the name of the inner-most trigger or view that is responsible for
409** the access attempt or NULL if this access attempt is directly from
410** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000411**
412** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000413*/
drh77ad4e42003-01-14 02:49:27 +0000414#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000415#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
416#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
417#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
418#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000419#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000420#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000421#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000422#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
423#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000424#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000425#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000426#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000427#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000428#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000429#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000430#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000431#define SQLITE_DROP_VIEW 17 /* View Name NULL */
432#define SQLITE_INSERT 18 /* Table Name NULL */
433#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
434#define SQLITE_READ 20 /* Table Name Column Name */
435#define SQLITE_SELECT 21 /* NULL NULL */
436#define SQLITE_TRANSACTION 22 /* NULL NULL */
437#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000438#define SQLITE_ATTACH 24 /* Filename NULL */
439#define SQLITE_DETACH 25 /* Database Name NULL */
440
drhed6c8672003-01-12 18:02:16 +0000441
442/*
443** The return value of the authorization function should be one of the
444** following constants:
445*/
446/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
447#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
448#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
449
450/*
danielk19776f8a5032004-05-10 10:34:51 +0000451** Register a function that is called at every invocation of sqlite3_exec()
danielk19774ad17132004-05-21 01:47:26 +0000452** or sqlite3_prepare(). This function can be used (for example) to generate
drhb86ccfb2003-01-28 23:13:10 +0000453** a log file of all SQL executed against a database.
drh18de4822003-01-16 16:28:53 +0000454*/
danielk19776f8a5032004-05-10 10:34:51 +0000455void *sqlite3_trace(sqlite*, void(*xTrace)(void*,const char*), void*);
drh18de4822003-01-16 16:28:53 +0000456
danielk1977348bb5d2003-10-18 09:37:26 +0000457/*
458** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000459** is invoked periodically during long running calls to sqlite3_exec(),
460** sqlite3_step() and sqlite3_get_table(). An example use for this API is to keep
danielk1977348bb5d2003-10-18 09:37:26 +0000461** a GUI updated during a large query.
462**
463** The progress callback is invoked once for every N virtual machine opcodes,
464** where N is the second argument to this function. The progress callback
465** itself is identified by the third argument to this function. The fourth
466** argument to this function is a void pointer passed to the progress callback
467** function each time it is invoked.
468**
danielk19776f8a5032004-05-10 10:34:51 +0000469** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000470** in less than N opcodes being executed, then the progress callback is not
471** invoked.
472**
danielk1977348bb5d2003-10-18 09:37:26 +0000473** To remove the progress callback altogether, pass NULL as the third
474** argument to this function.
475**
476** If the progress callback returns a result other than 0, then the current
477** query is immediately terminated and any database changes rolled back. If the
478** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000479** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000480**
481******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000482*/
danielk19776f8a5032004-05-10 10:34:51 +0000483void sqlite3_progress_handler(sqlite*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000484
drhaa940ea2004-01-15 02:44:03 +0000485/*
486** Register a callback function to be invoked whenever a new transaction
487** is committed. The pArg argument is passed through to the callback.
488** callback. If the callback function returns non-zero, then the commit
489** is converted into a rollback.
490**
491** If another function was previously registered, its pArg value is returned.
492** Otherwise NULL is returned.
493**
494** Registering a NULL function disables the callback.
495**
496******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
497*/
danielk19776f8a5032004-05-10 10:34:51 +0000498void *sqlite3_commit_hook(sqlite*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000499
drh22fbcb82004-02-01 01:22:50 +0000500/*
drh4f26d6c2004-05-26 23:25:30 +0000501** Open the sqlite database file "filename". The "filename" is UTF-8
502** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
503** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
504** if an error occurs. If the database is opened (or created) successfully,
505** then SQLITE_OK is returned. Otherwise an error code is returned. The
506** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
507** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000508**
drh4f26d6c2004-05-26 23:25:30 +0000509** If the database file does not exist, then a new database is created.
510** The encoding for the database is UTF-8 if sqlite3_open() is called and
511** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000512**
513** Whether or not an error occurs when it is opened, resources associated
514** with the sqlite3* handle should be released by passing it to
515** sqlite3_close() when it is no longer required.
516*/
517int sqlite3_open(
518 const char *filename, /* Database filename (UTF-8) */
519 sqlite3 **ppDb, /* OUT: SQLite db handle */
520 const char **args /* Null terminated array of option strings */
521);
danielk197765904932004-05-26 06:18:37 +0000522int sqlite3_open16(
523 const void *filename, /* Database filename (UTF-16) */
524 sqlite3 **ppDb, /* OUT: SQLite db handle */
525 const char **args /* Null terminated array of option strings */
526);
danielk1977295ba552004-05-19 10:34:51 +0000527
danielk197765904932004-05-26 06:18:37 +0000528/*
danielk197761de0d12004-05-27 23:56:16 +0000529** The following two functions are identical to sqlite3_open() and
530** sqlite3_open16(), except that any option strings are specified as the
531** third and subsequent arguments, instead of as an array. The final
532** argument to either of the following two functions must be a NULL.
533*/
534int sqlite3_open_vararg(
535 const char *filename, /* Database filename (UTF-8) */
536 sqlite3 **ppDb, /* OUT: SQLite db handle */
537 ... /* Option strings */
538);
539int sqlite3_open16_vararg(
540 const void *filename, /* Database filename (UTF-16) */
541 sqlite3 **ppDb, /* OUT: SQLite db handle */
542 ... /* Option strings */
543);
544
545/*
danielk197765904932004-05-26 06:18:37 +0000546** Return the error code for the most recent sqlite3_* API call associated
547** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
548** API call was successful.
549**
550** Calls to many sqlite3_* functions set the error code and string returned
551** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
552** (overwriting the previous values). Note that calls to sqlite3_errcode(),
553** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
554** results of future invocations.
555**
556** Assuming no other intervening sqlite3_* API calls are made, the error
557** code returned by this function is associated with the same error as
558** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
559*/
560int sqlite3_errcode(sqlite3 *db);
561
562/*
563** Return a pointer to a UTF-8 encoded string describing in english the
564** error condition for the most recent sqlite3_* API call. The returned
565** string is always terminated by an 0x00 byte.
566**
567** The string "not an error" is returned when the most recent API call was
568** successful.
569*/
570const char *sqlite3_errmsg(sqlite3*);
571
572/*
573** Return a pointer to a UTF-16 native byte order encoded string describing
574** in english the error condition for the most recent sqlite3_* API call.
575** The returned string is always terminated by a pair of 0x00 bytes.
576**
577** The string "not an error" is returned when the most recent API call was
578** successful.
579*/
580const void *sqlite3_errmsg16(sqlite3*);
581
582/*
583** An instance of the following opaque structure is used to represent
584** a compiled SQL statment.
585*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000586typedef struct sqlite3_stmt sqlite3_stmt;
587
danielk1977e3209e42004-05-20 01:40:18 +0000588/*
danielk197765904932004-05-26 06:18:37 +0000589** To execute an SQL query, it must first be compiled into a byte-code
590** program using one of the following routines. The only difference between
591** them is that the second argument, specifying the SQL statement to
592** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
593** function and UTF-16 for sqlite3_prepare16().
594**
595** The first parameter "db" is an SQLite database handle. The second
596** parameter "zSql" is the statement to be compiled, encoded as either
597** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
598** than zero, then zSql is read up to the first nul terminator. If
599** "nBytes" is not less than zero, then it is the length of the string zSql
600** in bytes (not characters).
601**
602** *pzTail is made to point to the first byte past the end of the first
603** SQL statement in zSql. This routine only compiles the first statement
604** in zSql, so *pzTail is left pointing to what remains uncompiled.
605**
606** *ppStmt is left pointing to a compiled SQL statement that can be
607** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
608** set to NULL. If the input text contained no SQL (if the input is and
609** empty string or a comment) then *ppStmt is set to NULL.
610**
611** On success, SQLITE_OK is returned. Otherwise an error code is returned.
612*/
613int sqlite3_prepare(
614 sqlite3 *db, /* Database handle */
615 const char *zSql, /* SQL statement, UTF-8 encoded */
616 int nBytes, /* Length of zSql in bytes. */
617 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
618 const char **pzTail /* OUT: Pointer to unused portion of zSql */
619);
620int sqlite3_prepare16(
621 sqlite3 *db, /* Database handle */
622 const void *zSql, /* SQL statement, UTF-16 encoded */
623 int nBytes, /* Length of zSql in bytes. */
624 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
625 const void **pzTail /* OUT: Pointer to unused portion of zSql */
626);
627
628/*
drhf4479502004-05-27 03:12:53 +0000629** Pointers to the following two opaque structures are used to communicate
630** with the implementations of user-defined functions.
631*/
632typedef struct sqlite3_context sqlite3_context;
633typedef struct Mem sqlite3_value;
634
635/*
drh4f26d6c2004-05-26 23:25:30 +0000636** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
637** one or more literals can be replace by a wildcard "?" or ":N:" where
638** N is an integer. These value of these wildcard literals can be set
639** using the routines listed below.
640**
641** In every case, the first parameter is a pointer to the sqlite3_stmt
642** structure returned from sqlite3_prepare(). The second parameter is the
643** index of the wildcard. The first "?" has an index of 1. ":N:" wildcards
644** use the index N.
645**
646** When the eCopy parameter is true, a copy of the value is made into
647** memory obtained and managed by SQLite. When eCopy is false, SQLite
648** assumes that the value is a constant and just stores a pointer to the
649** value without making a copy.
650**
651** The sqlite3_bind_* routine must be called before sqlite3_step() after
652** an sqlite3_prepare() or sqlite3_reset(). Unbound wildcards are interpreted
653** as NULL.
654*/
drhf4479502004-05-27 03:12:53 +0000655int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, int eCopy);
656int sqlite3_bind_double(sqlite3_stmt*, int, double);
657int sqlite3_bind_int(sqlite3_stmt*, int, int);
658int sqlite3_bind_int64(sqlite3_stmt*, int, long long int);
659int sqlite3_bind_null(sqlite3_stmt*, int);
660int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, int eCopy);
661int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int n, int eCopy);
662int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000663
664/*
danielk197765904932004-05-26 06:18:37 +0000665** Return the number of columns in the result set returned by the compiled
666** SQL statement. This routine returns 0 if pStmt is an SQL statement
667** that does not return data (for example an UPDATE).
668*/
669int sqlite3_column_count(sqlite3_stmt *pStmt);
670
671/*
672** The first parameter is a compiled SQL statement. This function returns
673** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000674** second function parameter. The string returned is UTF-8 for
675** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000676*/
677const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000678const void *sqlite3_column_name16(sqlite3_stmt*,int);
679
680/*
681** The first parameter is a compiled SQL statement. If this statement
682** is a SELECT statement, the Nth column of the returned result set
683** of the SELECT is a table column then the declared type of the table
684** column is returned. If the Nth column of the result set is not at table
685** column, then a NULL pointer is returned. The returned string is always
686** UTF-8 encoded. For example, in the database schema:
687**
688** CREATE TABLE t1(c1 VARIANT);
689**
690** And the following statement compiled:
691**
692** SELECT c1 + 1, 0 FROM t1;
693**
694** Then this routine would return the string "VARIANT" for the second
695** result column (i==1), and a NULL pointer for the first result column
696** (i==0).
697*/
698const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
699
700/*
701** The first parameter is a compiled SQL statement. If this statement
702** is a SELECT statement, the Nth column of the returned result set
703** of the SELECT is a table column then the declared type of the table
704** column is returned. If the Nth column of the result set is not at table
705** column, then a NULL pointer is returned. The returned string is always
706** UTF-16 encoded. For example, in the database schema:
707**
drh4f26d6c2004-05-26 23:25:30 +0000708** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000709**
710** And the following statement compiled:
711**
712** SELECT c1 + 1, 0 FROM t1;
713**
drh4f26d6c2004-05-26 23:25:30 +0000714** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000715** result column (i==1), and a NULL pointer for the first result column
716** (i==0).
717*/
718const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
719
danielk1977106bb232004-05-21 10:08:53 +0000720/*
721** After an SQL query has been compiled with a call to either
722** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
723** called one or more times to execute the statement.
724**
725** The return value will be either SQLITE_BUSY, SQLITE_DONE,
726** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
727**
728** SQLITE_BUSY means that the database engine attempted to open
729** a locked database and there is no busy callback registered.
730** Call sqlite3_step() again to retry the open.
731**
732** SQLITE_DONE means that the statement has finished executing
733** successfully. sqlite3_step() should not be called again on this virtual
734** machine.
735**
736** If the SQL statement being executed returns any data, then
737** SQLITE_ROW is returned each time a new row of data is ready
738** for processing by the caller. The values may be accessed using
739** the sqlite3_column_*() functions described below. sqlite3_step()
740** is called again to retrieve the next row of data.
741**
742** SQLITE_ERROR means that a run-time error (such as a constraint
743** violation) has occurred. sqlite3_step() should not be called again on
744** the VM. More information may be found by calling sqlite3_errmsg().
745**
746** SQLITE_MISUSE means that the this routine was called inappropriately.
747** Perhaps it was called on a virtual machine that had already been
748** finalized or on one that had previously returned SQLITE_ERROR or
749** SQLITE_DONE. Or it could be the case the the same database connection
750** is being used simulataneously by two or more threads.
751*/
danielk197717240fd2004-05-26 00:07:25 +0000752int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000753
danielk1977106bb232004-05-21 10:08:53 +0000754/*
755** Return the number of values in the current row of the result set.
756**
757** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
758** will return the same value as the sqlite3_column_count() function.
759** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
760** error code, or before sqlite3_step() has been called on a
761** compiled SQL statement, this routine returns zero.
762*/
danielk197793d46752004-05-23 13:30:58 +0000763int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000764
drh4f26d6c2004-05-26 23:25:30 +0000765/*
766** Values are stored in the database in one of the following fundamental
767** types.
768*/
drh9c054832004-05-31 18:51:57 +0000769#define SQLITE_INTEGER 1
770#define SQLITE_FLOAT 2
771#define SQLITE_TEXT 3
772#define SQLITE_BLOB 4
773#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000774
danielk1977106bb232004-05-21 10:08:53 +0000775/*
drh4f26d6c2004-05-26 23:25:30 +0000776** The next group of routines returns information about the information
777** in a single column of the current result row of a query. In every
778** case the first parameter is a pointer to the SQL statement that is being
779** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
780** the second argument is the index of the column for which information
781** should be returned. iCol is zero-indexed. The left-most column as an
782** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000783**
drh4f26d6c2004-05-26 23:25:30 +0000784** If the SQL statement is not currently point to a valid row, or if the
785** the colulmn index is out of range, the result is undefined.
786**
787** These routines attempt to convert the value where appropriate. For
788** example, if the internal representation is FLOAT and a text result
789** is requested, sprintf() is used internally to do the conversion
790** automatically. The following table details the conversions that
791** are applied:
792**
793** Internal Type Requested Type Conversion
794** ------------- -------------- --------------------------
795** NULL INTEGER Result is 0
796** NULL FLOAT Result is 0.0
797** NULL TEXT Result is an empty string
798** NULL BLOB Result is a zero-length BLOB
799** INTEGER FLOAT Convert from integer to float
800** INTEGER TEXT ASCII rendering of the integer
801** INTEGER BLOB Same as for INTEGER->TEXT
802** FLOAT INTEGER Convert from float to integer
803** FLOAT TEXT ASCII rendering of the float
804** FLOAT BLOB Same as FLOAT->TEXT
805** TEXT INTEGER Use atoi()
806** TEXT FLOAT Use atof()
807** TEXT BLOB No change
808** BLOB INTEGER Convert to TEXT then use atoi()
809** BLOB FLOAT Convert to TEXT then use atof()
810** BLOB TEXT Add a \000 terminator if needed
811**
812** The following access routines are provided:
813**
814** _type() Return the datatype of the result. This is one of
815** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
816** or SQLITE_NULL.
817** _blob() Return the value of a BLOB.
818** _bytes() Return the number of bytes in a BLOB value or the number
819** of bytes in a TEXT value represented as UTF-8. The \000
820** terminator is included in the byte count for TEXT values.
821** _bytes16() Return the number of bytes in a BLOB value or the number
822** of bytes in a TEXT value represented as UTF-16. The \u0000
823** terminator is included in the byte count for TEXT values.
824** _double() Return a FLOAT value.
825** _int() Return an INTEGER value in the host computer's native
826** integer representation. This might be either a 32- or 64-bit
827** integer depending on the host.
828** _int64() Return an INTEGER value as a 64-bit signed integer.
829** _text() Return the value as UTF-8 text.
830** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000831*/
drhf4479502004-05-27 03:12:53 +0000832const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
833int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
834int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
835double sqlite3_column_double(sqlite3_stmt*, int iCol);
836int sqlite3_column_int(sqlite3_stmt*, int iCol);
837long long int sqlite3_column_int64(sqlite3_stmt*, int iCol);
838const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
839const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000840int sqlite3_column_type(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000841
danielk197765904932004-05-26 06:18:37 +0000842/*
843** The sqlite3_finalize() function is called to delete a compiled
844** SQL statement obtained by a previous call to sqlite3_prepare()
845** or sqlite3_prepare16(). If the statement was executed successfully, or
846** not executed at all, then SQLITE_OK is returned. If execution of the
847** statement failed then an error code is returned.
848**
849** This routine can be called at any point during the execution of the
850** virtual machine. If the virtual machine has not completed execution
851** when this routine is called, that is like encountering an error or
852** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
853** rolled back and transactions cancelled, depending on the circumstances,
854** and the result code returned will be SQLITE_ABORT.
855*/
856int sqlite3_finalize(sqlite3_stmt *pStmt);
857
858/*
859** The sqlite3_reset() function is called to reset a compiled SQL
860** statement obtained by a previous call to sqlite3_prepare() or
861** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
862** Any SQL statement variables that had values bound to them using
863** the sqlite3_bind_*() API retain their values.
864*/
865int sqlite3_reset(sqlite3_stmt *pStmt);
866
867/*
danielk197765904932004-05-26 06:18:37 +0000868** The following two functions are used to add user functions or aggregates
869** implemented in C to the SQL langauge interpreted by SQLite. The
870** difference only between the two is that the second parameter, the
871** name of the (scalar) function or aggregate, is encoded in UTF-8 for
872** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
873**
874** The first argument is the database handle that the new function or
875** aggregate is to be added to. If a single program uses more than one
876** database handle internally, then user functions or aggregates must
877** be added individually to each database handle with which they will be
878** used.
879**
880** The third parameter is the number of arguments that the function or
881** aggregate takes. If this parameter is negative, then the function or
882** aggregate may take any number of arguments.
883**
884** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
885** pointers to user implemented C functions that implement the user
886** function or aggregate. A scalar function requires an implementation of
887** the xFunc callback only, NULL pointers should be passed as the xStep
888** and xFinal parameters. An aggregate function requires an implementation
889** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
890** existing user function or aggregate, pass NULL for all three function
891** callback. Specifying an inconstent set of callback values, such as an
892** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
893** returned.
894*/
895int sqlite3_create_function(
896 sqlite3 *,
897 const char *zFunctionName,
898 int nArg,
899 int eTextRep,
900 int iCollateArg,
901 void*,
902 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
903 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
904 void (*xFinal)(sqlite3_context*)
905);
906int sqlite3_create_function16(
907 sqlite3*,
908 const void *zFunctionName,
909 int nArg,
910 int eTextRep,
911 int iCollateArg,
912 void*,
913 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
914 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
915 void (*xFinal)(sqlite3_context*)
916);
917
918/*
danielk197765904932004-05-26 06:18:37 +0000919** The next routine returns the number of calls to xStep for a particular
920** aggregate function instance. The current call to xStep counts so this
921** routine always returns at least 1.
922*/
923int sqlite3_aggregate_count(sqlite3_context*);
924
danielk19770ffba6b2004-05-24 09:10:10 +0000925/*
drh4f26d6c2004-05-26 23:25:30 +0000926** The next group of routines returns information about parameters to
927** a user-defined function. Function implementations use these routines
928** to access their parameters. These routines are the same as the
929** sqlite3_column_* routines except that these routines take a single
930** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
931** column number.
danielk19770ffba6b2004-05-24 09:10:10 +0000932*/
drhf4479502004-05-27 03:12:53 +0000933const void *sqlite3_value_blob(sqlite3_value*);
934int sqlite3_value_bytes(sqlite3_value*);
935int sqlite3_value_bytes16(sqlite3_value*);
936double sqlite3_value_double(sqlite3_value*);
937int sqlite3_value_int(sqlite3_value*);
938long long int sqlite3_value_int64(sqlite3_value*);
939const unsigned char *sqlite3_value_text(sqlite3_value*);
940const void *sqlite3_value_text16(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +0000941int sqlite3_value_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +0000942
943/*
danielk19770ae8b832004-05-25 12:05:56 +0000944** Aggregate functions use the following routine to allocate
945** a structure for storing their state. The first time this routine
946** is called for a particular aggregate, a new structure of size nBytes
947** is allocated, zeroed, and returned. On subsequent calls (for the
948** same aggregate instance) the same buffer is returned. The implementation
949** of the aggregate can use the returned buffer to accumulate data.
950**
951** The buffer allocated is freed automatically by SQLite.
952*/
drh4f26d6c2004-05-26 23:25:30 +0000953void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +0000954
955/*
956** The pUserData parameter to the sqlite3_create_function() and
957** sqlite3_create_aggregate() routines used to register user functions
958** is available to the implementation of the function using this
959** call.
960*/
961void *sqlite3_user_data(sqlite3_context*);
962
963/*
drh4f26d6c2004-05-26 23:25:30 +0000964** User-defined functions invoke the following routines in order to
965** set their return value.
danielk19777e18c252004-05-25 11:47:24 +0000966*/
967void sqlite3_result_blob(sqlite3_context*, const void*, int n, int eCopy);
drh4f26d6c2004-05-26 23:25:30 +0000968void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +0000969void sqlite3_result_error(sqlite3_context*, const char*, int);
970void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +0000971void sqlite3_result_int(sqlite3_context*, int);
972void sqlite3_result_int64(sqlite3_context*, long long int);
973void sqlite3_result_null(sqlite3_context*);
974void sqlite3_result_text(sqlite3_context*, const char*, int n, int eCopy);
975void sqlite3_result_text16(sqlite3_context*, const void*, int n, int eCopy);
976void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +0000977
drh382c0242001-10-06 16:33:02 +0000978#ifdef __cplusplus
979} /* End of the 'extern "C"' block */
980#endif
danielk19774adee202004-05-08 08:23:19 +0000981#endif