blob: 29f6d487844983f1be14f93a93a32cb6c2ee1928 [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**
danielk1977f9d64d22004-06-19 08:18:07 +000015** @(#) $Id: sqlite.h.in,v 1.104 2004/06/19 08:18:16 danielk1977 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/*
drh75897232000-05-29 14:26:00 +000048** A function to close the database.
49**
50** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +000051** returned from sqlite3_open() and the corresponding database will by closed.
danielk197796d81f92004-06-19 03:33:57 +000052**
53** All SQL statements prepared using sqlite3_prepare() or
54** sqlite3_prepare16() must be deallocated using sqlite3_finalize() before
55** this routine is called. Otherwise, SQLITE_BUSY is returned and the
56** database connection remains open.
drh75897232000-05-29 14:26:00 +000057*/
danielk1977f9d64d22004-06-19 08:18:07 +000058int sqlite3_close(sqlite3 *);
drh75897232000-05-29 14:26:00 +000059
60/*
61** The type for a callback function.
62*/
63typedef int (*sqlite_callback)(void*,int,char**, char**);
64
65/*
66** A function to executes one or more statements of SQL.
67**
68** If one or more of the SQL statements are queries, then
69** the callback function specified by the 3rd parameter is
70** invoked once for each row of the query result. This callback
71** should normally return 0. If the callback returns a non-zero
72** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +000073** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +000074**
75** The 4th parameter is an arbitrary pointer that is passed
76** to the callback function as its first parameter.
77**
78** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +000079** columns in the query result. The 3rd parameter to the callback
80** is an array of strings holding the values for each column.
81** The 4th parameter to the callback is an array of strings holding
82** the names of each column.
drh75897232000-05-29 14:26:00 +000083**
84** The callback function may be NULL, even for queries. A NULL
85** callback is not an error. It just means that no callback
86** will be invoked.
87**
88** If an error occurs while parsing or evaluating the SQL (but
89** not while executing the callback) then an appropriate error
90** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +000091** *errmsg is made to point to that message. The calling function
92** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +000093** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +000094** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +000095**
96** The return value is is SQLITE_OK if there are no errors and
97** some other return code if there is an error. The particular
98** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +000099**
100** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000101** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +0000102** behavior can be modified somewhat using the sqlite3_busy_handler()
103** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000104*/
danielk19776f8a5032004-05-10 10:34:51 +0000105int sqlite3_exec(
danielk1977f9d64d22004-06-19 08:18:07 +0000106 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000107 const char *sql, /* SQL to be executed */
drh75897232000-05-29 14:26:00 +0000108 sqlite_callback, /* Callback function */
109 void *, /* 1st argument to callback function */
110 char **errmsg /* Error msg written here */
111);
112
drh58b95762000-06-02 01:17:37 +0000113/*
danielk19776f8a5032004-05-10 10:34:51 +0000114** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000115*/
drh717e6402001-09-27 03:22:32 +0000116#define SQLITE_OK 0 /* Successful result */
117#define SQLITE_ERROR 1 /* SQL error or missing database */
118#define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */
119#define SQLITE_PERM 3 /* Access permission denied */
120#define SQLITE_ABORT 4 /* Callback routine requested an abort */
121#define SQLITE_BUSY 5 /* The database file is locked */
122#define SQLITE_LOCKED 6 /* A table in the database is locked */
123#define SQLITE_NOMEM 7 /* A malloc() failed */
124#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000125#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000126#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
127#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
128#define SQLITE_NOTFOUND 12 /* (Internal Only) Table or record not found */
129#define SQLITE_FULL 13 /* Insertion failed because database is full */
130#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
131#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000132#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000133#define SQLITE_SCHEMA 17 /* The database schema changed */
134#define SQLITE_TOOBIG 18 /* Too much data for one row of a table */
135#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000136#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000137#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000138#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000139#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000140#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000141#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000142#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000143#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
144#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh717e6402001-09-27 03:22:32 +0000145
drhaf9ff332002-01-16 21:00:27 +0000146/*
147** Each entry in an SQLite table has a unique integer key. (The key is
148** the value of the INTEGER PRIMARY KEY column if there is such a column,
149** otherwise the key is generated at random. The unique key is always
150** available as the ROWID, OID, or _ROWID_ column.) The following routine
151** returns the integer key of the most recent insert in the database.
152**
153** This function is similar to the mysql_insert_id() function from MySQL.
154*/
danielk1977f9d64d22004-06-19 08:18:07 +0000155long long int sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000156
drhc8d30ac2002-04-12 10:08:59 +0000157/*
158** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000159** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000160**
161** All changes are counted, even if they were later undone by a
162** ROLLBACK or ABORT. Except, changes associated with creating and
163** dropping tables are not counted.
164**
danielk19776f8a5032004-05-10 10:34:51 +0000165** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000166** in the inner, recursive call are counted together with the changes
167** in the outer call.
168**
169** SQLite implements the command "DELETE FROM table" without a WHERE clause
170** by dropping and recreating the table. (This is much faster than going
171** through and deleting individual elements form the table.) Because of
172** this optimization, the change count for "DELETE FROM table" will be
173** zero regardless of the number of elements that were originally in the
174** table. To get an accurate count of the number of rows deleted, use
175** "DELETE FROM table WHERE 1" instead.
176*/
danielk1977f9d64d22004-06-19 08:18:07 +0000177int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000178
rdcf146a772004-02-25 22:51:06 +0000179/*
180** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000181** by the last INSERT, UPDATE, or DELETE statment executed by sqlite3_exec(),
rdcf146a772004-02-25 22:51:06 +0000182** or by the last VM to run to completion. The change count is not updated
183** by SQL statements other than INSERT, UPDATE or DELETE.
184**
185** Changes are counted, even if they are later undone by a ROLLBACK or
186** ABORT. Changes associated with trigger programs that execute as a
187** result of the INSERT, UPDATE, or DELETE statement are not counted.
188**
danielk19776f8a5032004-05-10 10:34:51 +0000189** If a callback invokes sqlite3_exec() recursively, then the changes
rdcf146a772004-02-25 22:51:06 +0000190** in the inner, recursive call are counted together with the changes
191** in the outer call.
192**
193** SQLite implements the command "DELETE FROM table" without a WHERE clause
194** by dropping and recreating the table. (This is much faster than going
195** through and deleting individual elements form the table.) Because of
196** this optimization, the change count for "DELETE FROM table" will be
197** zero regardless of the number of elements that were originally in the
198** table. To get an accurate count of the number of rows deleted, use
199** "DELETE FROM table WHERE 1" instead.
200**
201******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
202*/
danielk1977f9d64d22004-06-19 08:18:07 +0000203int sqlite3_last_statement_changes(sqlite3*);
rdcf146a772004-02-25 22:51:06 +0000204
drh4c504392000-10-16 22:06:40 +0000205/* This function causes any pending database operation to abort and
206** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000207** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000208** or Ctrl-C where the user wants a long query operation to halt
209** immediately.
210*/
danielk1977f9d64d22004-06-19 08:18:07 +0000211void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000212
drheec553b2000-06-02 01:51:20 +0000213
danielk197761de0d12004-05-27 23:56:16 +0000214/* These functions return true if the given input string comprises
215** one or more complete SQL statements. For the sqlite3_complete() call,
216** the parameter must be a nul-terminated UTF-8 string. For
217** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
218** is required.
drh75897232000-05-29 14:26:00 +0000219**
220** The algorithm is simple. If the last token other than spaces
221** and comments is a semicolon, then return true. otherwise return
222** false.
223*/
danielk19776f8a5032004-05-10 10:34:51 +0000224int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000225int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000226
drh2dfbbca2000-07-28 14:32:48 +0000227/*
228** This routine identifies a callback function that is invoked
229** whenever an attempt is made to open a database table that is
230** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000231** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000232** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000233** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000234** second argument is the name of the locked table and the third
235** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000236** busy callback returns 0, then sqlite3_exec() immediately returns
237** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000238** tries to open the table again and the cycle repeats.
239**
240** The default busy callback is NULL.
241**
242** Sqlite is re-entrant, so the busy handler may start a new query.
243** (It is not clear why anyone would every want to do this, but it
244** is allowed, in theory.) But the busy handler may not close the
245** database. Closing the database from a busy handler will delete
246** data structures out from under the executing query and will
247** probably result in a coredump.
248*/
danielk1977f9d64d22004-06-19 08:18:07 +0000249int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000250
251/*
252** This routine sets a busy handler that sleeps for a while when a
253** table is locked. The handler will sleep multiple times until
254** at least "ms" milleseconds of sleeping have been done. After
255** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000256** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000257**
258** Calling this routine with an argument less than or equal to zero
259** turns off all busy handlers.
260*/
danielk1977f9d64d22004-06-19 08:18:07 +0000261int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000262
drhe3710332000-09-29 13:30:53 +0000263/*
danielk19776f8a5032004-05-10 10:34:51 +0000264** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000265** Instead of invoking a user-supplied callback for each row of the
266** result, this routine remembers each row of the result in memory
267** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000268** query has finished.
269**
270** As an example, suppose the query result where this table:
271**
272** Name | Age
273** -----------------------
274** Alice | 43
275** Bob | 28
276** Cindy | 21
277**
278** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000279** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000280**
281** azResult[0] = "Name";
282** azResult[1] = "Age";
283** azResult[2] = "Alice";
284** azResult[3] = "43";
285** azResult[4] = "Bob";
286** azResult[5] = "28";
287** azResult[6] = "Cindy";
288** azResult[7] = "21";
289**
290** Notice that there is an extra row of data containing the column
291** headers. But the *nrow return value is still 3. *ncolumn is
292** set to 2. In general, the number of values inserted into azResult
293** will be ((*nrow) + 1)*(*ncolumn).
294**
295** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000296** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000297** release the memory that was malloc-ed. Because of the way the
298** malloc() happens, the calling function must not try to call
danielk19776f8a5032004-05-10 10:34:51 +0000299** malloc() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000300** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000301**
danielk19776f8a5032004-05-10 10:34:51 +0000302** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000303*/
danielk19776f8a5032004-05-10 10:34:51 +0000304int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000305 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000306 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000307 char ***resultp, /* Result written to a char *[] that this points to */
308 int *nrow, /* Number of result rows written here */
309 int *ncolumn, /* Number of result columns written here */
310 char **errmsg /* Error msg written here */
311);
312
313/*
danielk19776f8a5032004-05-10 10:34:51 +0000314** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000315*/
danielk19776f8a5032004-05-10 10:34:51 +0000316void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000317
drha18c5682000-10-08 22:20:57 +0000318/*
drh4f26d6c2004-05-26 23:25:30 +0000319** The following routines are variants of the "sprintf()" from the
320** standard C library. The resulting string is written into memory
321** obtained from malloc() so that there is never a possiblity of buffer
322** overflow. These routines also implement some additional formatting
323** options that are useful for constructing SQL statements.
324**
325** The strings returned by these routines should be freed by calling
326** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000327**
328** All of the usual printf formatting options apply. In addition, there
329** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000330** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000331** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000332** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000333** the string.
334**
335** For example, so some string variable contains text as follows:
336**
337** char *zText = "It's a happy day!";
338**
339** We can use this text in an SQL statement as follows:
340**
danielk19776f8a5032004-05-10 10:34:51 +0000341** sqlite3_exec_printf(db, "INSERT INTO table VALUES('%q')",
drha18c5682000-10-08 22:20:57 +0000342** callback1, 0, 0, zText);
343**
344** Because the %q format string is used, the '\'' character in zText
345** is escaped and the SQL generated is as follows:
346**
347** INSERT INTO table1 VALUES('It''s a happy day!')
348**
349** This is correct. Had we used %s instead of %q, the generated SQL
350** would have looked like this:
351**
352** INSERT INTO table1 VALUES('It's a happy day!');
353**
354** This second example is an SQL syntax error. As a general rule you
355** should always use %q instead of %s when inserting text into a string
356** literal.
357*/
danielk19776f8a5032004-05-10 10:34:51 +0000358char *sqlite3_mprintf(const char*,...);
359char *sqlite3_vmprintf(const char*, va_list);
drh4f26d6c2004-05-26 23:25:30 +0000360void sqlite3_free(char *z);
drh5191b7e2002-03-08 02:12:00 +0000361
362/*
drhed6c8672003-01-12 18:02:16 +0000363** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000364** callback is invoked (at compile-time, not at run-time) for each
365** attempt to access a column of a table in the database. The callback
366** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
367** SQL statement should be aborted with an error and SQLITE_IGNORE
368** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000369*/
danielk19776f8a5032004-05-10 10:34:51 +0000370int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000371 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000372 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000373 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000374);
375
376/*
377** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000378** be one of the values below. These values signify what kind of operation
379** is to be authorized. The 3rd and 4th parameters to the authorization
380** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000381** codes is used as the second parameter. The 5th parameter is the name
382** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000383** is the name of the inner-most trigger or view that is responsible for
384** the access attempt or NULL if this access attempt is directly from
385** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000386**
387** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000388*/
drh77ad4e42003-01-14 02:49:27 +0000389#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000390#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
391#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
392#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
393#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000394#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000395#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000396#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000397#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
398#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000399#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000400#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000401#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000402#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000403#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000404#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000405#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000406#define SQLITE_DROP_VIEW 17 /* View Name NULL */
407#define SQLITE_INSERT 18 /* Table Name NULL */
408#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
409#define SQLITE_READ 20 /* Table Name Column Name */
410#define SQLITE_SELECT 21 /* NULL NULL */
411#define SQLITE_TRANSACTION 22 /* NULL NULL */
412#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000413#define SQLITE_ATTACH 24 /* Filename NULL */
414#define SQLITE_DETACH 25 /* Database Name NULL */
415
drhed6c8672003-01-12 18:02:16 +0000416
417/*
418** The return value of the authorization function should be one of the
419** following constants:
420*/
421/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
422#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
423#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
424
425/*
danielk19776f8a5032004-05-10 10:34:51 +0000426** Register a function that is called at every invocation of sqlite3_exec()
danielk19774ad17132004-05-21 01:47:26 +0000427** or sqlite3_prepare(). This function can be used (for example) to generate
drhb86ccfb2003-01-28 23:13:10 +0000428** a log file of all SQL executed against a database.
drh18de4822003-01-16 16:28:53 +0000429*/
danielk1977f9d64d22004-06-19 08:18:07 +0000430void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh18de4822003-01-16 16:28:53 +0000431
danielk1977348bb5d2003-10-18 09:37:26 +0000432/*
433** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000434** is invoked periodically during long running calls to sqlite3_exec(),
435** sqlite3_step() and sqlite3_get_table(). An example use for this API is to keep
danielk1977348bb5d2003-10-18 09:37:26 +0000436** a GUI updated during a large query.
437**
438** The progress callback is invoked once for every N virtual machine opcodes,
439** where N is the second argument to this function. The progress callback
440** itself is identified by the third argument to this function. The fourth
441** argument to this function is a void pointer passed to the progress callback
442** function each time it is invoked.
443**
danielk19776f8a5032004-05-10 10:34:51 +0000444** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000445** in less than N opcodes being executed, then the progress callback is not
446** invoked.
447**
danielk1977348bb5d2003-10-18 09:37:26 +0000448** To remove the progress callback altogether, pass NULL as the third
449** argument to this function.
450**
451** If the progress callback returns a result other than 0, then the current
452** query is immediately terminated and any database changes rolled back. If the
453** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000454** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000455**
456******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000457*/
danielk1977f9d64d22004-06-19 08:18:07 +0000458void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000459
drhaa940ea2004-01-15 02:44:03 +0000460/*
461** Register a callback function to be invoked whenever a new transaction
462** is committed. The pArg argument is passed through to the callback.
463** callback. If the callback function returns non-zero, then the commit
464** is converted into a rollback.
465**
466** If another function was previously registered, its pArg value is returned.
467** Otherwise NULL is returned.
468**
469** Registering a NULL function disables the callback.
470**
471******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
472*/
danielk1977f9d64d22004-06-19 08:18:07 +0000473void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000474
drh22fbcb82004-02-01 01:22:50 +0000475/*
drh4f26d6c2004-05-26 23:25:30 +0000476** Open the sqlite database file "filename". The "filename" is UTF-8
477** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
478** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
479** if an error occurs. If the database is opened (or created) successfully,
480** then SQLITE_OK is returned. Otherwise an error code is returned. The
481** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
482** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000483**
drh4f26d6c2004-05-26 23:25:30 +0000484** If the database file does not exist, then a new database is created.
485** The encoding for the database is UTF-8 if sqlite3_open() is called and
486** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000487**
488** Whether or not an error occurs when it is opened, resources associated
489** with the sqlite3* handle should be released by passing it to
490** sqlite3_close() when it is no longer required.
491*/
492int sqlite3_open(
493 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000494 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000495);
danielk197765904932004-05-26 06:18:37 +0000496int sqlite3_open16(
497 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000498 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000499);
danielk1977295ba552004-05-19 10:34:51 +0000500
danielk197765904932004-05-26 06:18:37 +0000501/*
502** Return the error code for the most recent sqlite3_* API call associated
503** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
504** API call was successful.
505**
506** Calls to many sqlite3_* functions set the error code and string returned
507** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
508** (overwriting the previous values). Note that calls to sqlite3_errcode(),
509** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
510** results of future invocations.
511**
512** Assuming no other intervening sqlite3_* API calls are made, the error
513** code returned by this function is associated with the same error as
514** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
515*/
516int sqlite3_errcode(sqlite3 *db);
517
518/*
519** Return a pointer to a UTF-8 encoded string describing in english the
520** error condition for the most recent sqlite3_* API call. The returned
521** string is always terminated by an 0x00 byte.
522**
523** The string "not an error" is returned when the most recent API call was
524** successful.
525*/
526const char *sqlite3_errmsg(sqlite3*);
527
528/*
529** Return a pointer to a UTF-16 native byte order encoded string describing
530** in english the error condition for the most recent sqlite3_* API call.
531** The returned string is always terminated by a pair of 0x00 bytes.
532**
533** The string "not an error" is returned when the most recent API call was
534** successful.
535*/
536const void *sqlite3_errmsg16(sqlite3*);
537
538/*
539** An instance of the following opaque structure is used to represent
540** a compiled SQL statment.
541*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000542typedef struct sqlite3_stmt sqlite3_stmt;
543
danielk1977e3209e42004-05-20 01:40:18 +0000544/*
danielk197765904932004-05-26 06:18:37 +0000545** To execute an SQL query, it must first be compiled into a byte-code
546** program using one of the following routines. The only difference between
547** them is that the second argument, specifying the SQL statement to
548** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
549** function and UTF-16 for sqlite3_prepare16().
550**
551** The first parameter "db" is an SQLite database handle. The second
552** parameter "zSql" is the statement to be compiled, encoded as either
553** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
554** than zero, then zSql is read up to the first nul terminator. If
555** "nBytes" is not less than zero, then it is the length of the string zSql
556** in bytes (not characters).
557**
558** *pzTail is made to point to the first byte past the end of the first
559** SQL statement in zSql. This routine only compiles the first statement
560** in zSql, so *pzTail is left pointing to what remains uncompiled.
561**
562** *ppStmt is left pointing to a compiled SQL statement that can be
563** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
564** set to NULL. If the input text contained no SQL (if the input is and
565** empty string or a comment) then *ppStmt is set to NULL.
566**
567** On success, SQLITE_OK is returned. Otherwise an error code is returned.
568*/
569int sqlite3_prepare(
570 sqlite3 *db, /* Database handle */
571 const char *zSql, /* SQL statement, UTF-8 encoded */
572 int nBytes, /* Length of zSql in bytes. */
573 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
574 const char **pzTail /* OUT: Pointer to unused portion of zSql */
575);
576int sqlite3_prepare16(
577 sqlite3 *db, /* Database handle */
578 const void *zSql, /* SQL statement, UTF-16 encoded */
579 int nBytes, /* Length of zSql in bytes. */
580 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
581 const void **pzTail /* OUT: Pointer to unused portion of zSql */
582);
583
584/*
drhf4479502004-05-27 03:12:53 +0000585** Pointers to the following two opaque structures are used to communicate
586** with the implementations of user-defined functions.
587*/
588typedef struct sqlite3_context sqlite3_context;
589typedef struct Mem sqlite3_value;
590
591/*
drh4f26d6c2004-05-26 23:25:30 +0000592** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
593** one or more literals can be replace by a wildcard "?" or ":N:" where
594** N is an integer. These value of these wildcard literals can be set
595** using the routines listed below.
596**
597** In every case, the first parameter is a pointer to the sqlite3_stmt
598** structure returned from sqlite3_prepare(). The second parameter is the
599** index of the wildcard. The first "?" has an index of 1. ":N:" wildcards
600** use the index N.
601**
602** When the eCopy parameter is true, a copy of the value is made into
603** memory obtained and managed by SQLite. When eCopy is false, SQLite
604** assumes that the value is a constant and just stores a pointer to the
605** value without making a copy.
606**
607** The sqlite3_bind_* routine must be called before sqlite3_step() after
608** an sqlite3_prepare() or sqlite3_reset(). Unbound wildcards are interpreted
609** as NULL.
610*/
danielk1977d8123362004-06-12 09:25:12 +0000611int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000612int sqlite3_bind_double(sqlite3_stmt*, int, double);
613int sqlite3_bind_int(sqlite3_stmt*, int, int);
614int sqlite3_bind_int64(sqlite3_stmt*, int, long long int);
615int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000616int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
617int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000618int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000619
620/*
danielk197765904932004-05-26 06:18:37 +0000621** Return the number of columns in the result set returned by the compiled
622** SQL statement. This routine returns 0 if pStmt is an SQL statement
623** that does not return data (for example an UPDATE).
624*/
625int sqlite3_column_count(sqlite3_stmt *pStmt);
626
627/*
628** The first parameter is a compiled SQL statement. This function returns
629** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000630** second function parameter. The string returned is UTF-8 for
631** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000632*/
633const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000634const void *sqlite3_column_name16(sqlite3_stmt*,int);
635
636/*
637** The first parameter is a compiled SQL statement. If this statement
638** is a SELECT statement, the Nth column of the returned result set
639** of the SELECT is a table column then the declared type of the table
640** column is returned. If the Nth column of the result set is not at table
641** column, then a NULL pointer is returned. The returned string is always
642** UTF-8 encoded. For example, in the database schema:
643**
644** CREATE TABLE t1(c1 VARIANT);
645**
646** And the following statement compiled:
647**
648** SELECT c1 + 1, 0 FROM t1;
649**
650** Then this routine would return the string "VARIANT" for the second
651** result column (i==1), and a NULL pointer for the first result column
652** (i==0).
653*/
654const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
655
656/*
657** The first parameter is a compiled SQL statement. If this statement
658** is a SELECT statement, the Nth column of the returned result set
659** of the SELECT is a table column then the declared type of the table
660** column is returned. If the Nth column of the result set is not at table
661** column, then a NULL pointer is returned. The returned string is always
662** UTF-16 encoded. For example, in the database schema:
663**
drh4f26d6c2004-05-26 23:25:30 +0000664** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000665**
666** And the following statement compiled:
667**
668** SELECT c1 + 1, 0 FROM t1;
669**
drh4f26d6c2004-05-26 23:25:30 +0000670** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000671** result column (i==1), and a NULL pointer for the first result column
672** (i==0).
673*/
674const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
675
danielk1977106bb232004-05-21 10:08:53 +0000676/*
677** After an SQL query has been compiled with a call to either
678** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
679** called one or more times to execute the statement.
680**
681** The return value will be either SQLITE_BUSY, SQLITE_DONE,
682** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
683**
684** SQLITE_BUSY means that the database engine attempted to open
685** a locked database and there is no busy callback registered.
686** Call sqlite3_step() again to retry the open.
687**
688** SQLITE_DONE means that the statement has finished executing
689** successfully. sqlite3_step() should not be called again on this virtual
690** machine.
691**
692** If the SQL statement being executed returns any data, then
693** SQLITE_ROW is returned each time a new row of data is ready
694** for processing by the caller. The values may be accessed using
695** the sqlite3_column_*() functions described below. sqlite3_step()
696** is called again to retrieve the next row of data.
697**
698** SQLITE_ERROR means that a run-time error (such as a constraint
699** violation) has occurred. sqlite3_step() should not be called again on
700** the VM. More information may be found by calling sqlite3_errmsg().
701**
702** SQLITE_MISUSE means that the this routine was called inappropriately.
703** Perhaps it was called on a virtual machine that had already been
704** finalized or on one that had previously returned SQLITE_ERROR or
705** SQLITE_DONE. Or it could be the case the the same database connection
706** is being used simulataneously by two or more threads.
707*/
danielk197717240fd2004-05-26 00:07:25 +0000708int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000709
danielk1977106bb232004-05-21 10:08:53 +0000710/*
711** Return the number of values in the current row of the result set.
712**
713** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
714** will return the same value as the sqlite3_column_count() function.
715** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
716** error code, or before sqlite3_step() has been called on a
717** compiled SQL statement, this routine returns zero.
718*/
danielk197793d46752004-05-23 13:30:58 +0000719int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000720
drh4f26d6c2004-05-26 23:25:30 +0000721/*
722** Values are stored in the database in one of the following fundamental
723** types.
724*/
drh9c054832004-05-31 18:51:57 +0000725#define SQLITE_INTEGER 1
726#define SQLITE_FLOAT 2
727#define SQLITE_TEXT 3
728#define SQLITE_BLOB 4
729#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000730
danielk1977106bb232004-05-21 10:08:53 +0000731/*
drh4f26d6c2004-05-26 23:25:30 +0000732** The next group of routines returns information about the information
733** in a single column of the current result row of a query. In every
734** case the first parameter is a pointer to the SQL statement that is being
735** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
736** the second argument is the index of the column for which information
737** should be returned. iCol is zero-indexed. The left-most column as an
738** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000739**
drh4f26d6c2004-05-26 23:25:30 +0000740** If the SQL statement is not currently point to a valid row, or if the
741** the colulmn index is out of range, the result is undefined.
742**
743** These routines attempt to convert the value where appropriate. For
744** example, if the internal representation is FLOAT and a text result
745** is requested, sprintf() is used internally to do the conversion
746** automatically. The following table details the conversions that
747** are applied:
748**
749** Internal Type Requested Type Conversion
750** ------------- -------------- --------------------------
751** NULL INTEGER Result is 0
752** NULL FLOAT Result is 0.0
753** NULL TEXT Result is an empty string
754** NULL BLOB Result is a zero-length BLOB
755** INTEGER FLOAT Convert from integer to float
756** INTEGER TEXT ASCII rendering of the integer
757** INTEGER BLOB Same as for INTEGER->TEXT
758** FLOAT INTEGER Convert from float to integer
759** FLOAT TEXT ASCII rendering of the float
760** FLOAT BLOB Same as FLOAT->TEXT
761** TEXT INTEGER Use atoi()
762** TEXT FLOAT Use atof()
763** TEXT BLOB No change
764** BLOB INTEGER Convert to TEXT then use atoi()
765** BLOB FLOAT Convert to TEXT then use atof()
766** BLOB TEXT Add a \000 terminator if needed
767**
768** The following access routines are provided:
769**
770** _type() Return the datatype of the result. This is one of
771** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
772** or SQLITE_NULL.
773** _blob() Return the value of a BLOB.
774** _bytes() Return the number of bytes in a BLOB value or the number
775** of bytes in a TEXT value represented as UTF-8. The \000
776** terminator is included in the byte count for TEXT values.
777** _bytes16() Return the number of bytes in a BLOB value or the number
778** of bytes in a TEXT value represented as UTF-16. The \u0000
779** terminator is included in the byte count for TEXT values.
780** _double() Return a FLOAT value.
781** _int() Return an INTEGER value in the host computer's native
782** integer representation. This might be either a 32- or 64-bit
783** integer depending on the host.
784** _int64() Return an INTEGER value as a 64-bit signed integer.
785** _text() Return the value as UTF-8 text.
786** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000787*/
drhf4479502004-05-27 03:12:53 +0000788const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
789int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
790int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
791double sqlite3_column_double(sqlite3_stmt*, int iCol);
792int sqlite3_column_int(sqlite3_stmt*, int iCol);
793long long int sqlite3_column_int64(sqlite3_stmt*, int iCol);
794const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
795const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000796int sqlite3_column_type(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000797
danielk197765904932004-05-26 06:18:37 +0000798/*
799** The sqlite3_finalize() function is called to delete a compiled
800** SQL statement obtained by a previous call to sqlite3_prepare()
801** or sqlite3_prepare16(). If the statement was executed successfully, or
802** not executed at all, then SQLITE_OK is returned. If execution of the
803** statement failed then an error code is returned.
804**
805** This routine can be called at any point during the execution of the
806** virtual machine. If the virtual machine has not completed execution
807** when this routine is called, that is like encountering an error or
808** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
809** rolled back and transactions cancelled, depending on the circumstances,
810** and the result code returned will be SQLITE_ABORT.
811*/
812int sqlite3_finalize(sqlite3_stmt *pStmt);
813
814/*
815** The sqlite3_reset() function is called to reset a compiled SQL
816** statement obtained by a previous call to sqlite3_prepare() or
817** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
818** Any SQL statement variables that had values bound to them using
819** the sqlite3_bind_*() API retain their values.
820*/
821int sqlite3_reset(sqlite3_stmt *pStmt);
822
823/*
danielk197765904932004-05-26 06:18:37 +0000824** The following two functions are used to add user functions or aggregates
825** implemented in C to the SQL langauge interpreted by SQLite. The
826** difference only between the two is that the second parameter, the
827** name of the (scalar) function or aggregate, is encoded in UTF-8 for
828** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
829**
830** The first argument is the database handle that the new function or
831** aggregate is to be added to. If a single program uses more than one
832** database handle internally, then user functions or aggregates must
833** be added individually to each database handle with which they will be
834** used.
835**
836** The third parameter is the number of arguments that the function or
837** aggregate takes. If this parameter is negative, then the function or
838** aggregate may take any number of arguments.
839**
danielk1977d8123362004-06-12 09:25:12 +0000840** The fourth parameter is one of SQLITE_UTF* values defined below,
841** indicating the encoding that the function is most likely to handle
842** values in. This does not change the behaviour of the programming
843** interface. However, if two versions of the same function are registered
844** with different encoding values, SQLite invokes the version likely to
845** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +0000846**
danielk197765904932004-05-26 06:18:37 +0000847** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
848** pointers to user implemented C functions that implement the user
849** function or aggregate. A scalar function requires an implementation of
850** the xFunc callback only, NULL pointers should be passed as the xStep
851** and xFinal parameters. An aggregate function requires an implementation
852** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
853** existing user function or aggregate, pass NULL for all three function
854** callback. Specifying an inconstent set of callback values, such as an
855** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
856** returned.
857*/
858int sqlite3_create_function(
859 sqlite3 *,
860 const char *zFunctionName,
861 int nArg,
862 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000863 void*,
864 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
865 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
866 void (*xFinal)(sqlite3_context*)
867);
868int sqlite3_create_function16(
869 sqlite3*,
870 const void *zFunctionName,
871 int nArg,
872 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000873 void*,
874 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
875 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
876 void (*xFinal)(sqlite3_context*)
877);
878
879/*
danielk197765904932004-05-26 06:18:37 +0000880** The next routine returns the number of calls to xStep for a particular
881** aggregate function instance. The current call to xStep counts so this
882** routine always returns at least 1.
883*/
884int sqlite3_aggregate_count(sqlite3_context*);
885
danielk19770ffba6b2004-05-24 09:10:10 +0000886/*
drh4f26d6c2004-05-26 23:25:30 +0000887** The next group of routines returns information about parameters to
888** a user-defined function. Function implementations use these routines
889** to access their parameters. These routines are the same as the
890** sqlite3_column_* routines except that these routines take a single
891** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
892** column number.
danielk19770ffba6b2004-05-24 09:10:10 +0000893*/
drhf4479502004-05-27 03:12:53 +0000894const void *sqlite3_value_blob(sqlite3_value*);
895int sqlite3_value_bytes(sqlite3_value*);
896int sqlite3_value_bytes16(sqlite3_value*);
897double sqlite3_value_double(sqlite3_value*);
898int sqlite3_value_int(sqlite3_value*);
899long long int sqlite3_value_int64(sqlite3_value*);
900const unsigned char *sqlite3_value_text(sqlite3_value*);
901const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +0000902const void *sqlite3_value_text16le(sqlite3_value*);
903const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +0000904int sqlite3_value_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +0000905
906/*
danielk19770ae8b832004-05-25 12:05:56 +0000907** Aggregate functions use the following routine to allocate
908** a structure for storing their state. The first time this routine
909** is called for a particular aggregate, a new structure of size nBytes
910** is allocated, zeroed, and returned. On subsequent calls (for the
911** same aggregate instance) the same buffer is returned. The implementation
912** of the aggregate can use the returned buffer to accumulate data.
913**
914** The buffer allocated is freed automatically by SQLite.
915*/
drh4f26d6c2004-05-26 23:25:30 +0000916void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +0000917
918/*
919** The pUserData parameter to the sqlite3_create_function() and
920** sqlite3_create_aggregate() routines used to register user functions
921** is available to the implementation of the function using this
922** call.
923*/
924void *sqlite3_user_data(sqlite3_context*);
925
926/*
danielk1977682f68b2004-06-05 10:22:17 +0000927** The following two functions may be used by scalar user functions to
928** associate meta-data with argument values. If the same value is passed to
929** multiple invocations of the user-function during query execution, under
930** some circumstances the associated meta-data may be preserved. This may
931** be used, for example, to add a regular-expression matching scalar
932** function. The compiled version of the regular expression is stored as
933** meta-data associated with the SQL value passed as the regular expression
934** pattern.
935**
936** Calling sqlite3_get_auxdata() returns a pointer to the meta data
937** associated with the Nth argument value to the current user function
938** call, where N is the second parameter. If no meta-data has been set for
939** that value, then a NULL pointer is returned.
940**
941** The sqlite3_set_auxdata() is used to associate meta data with a user
942** function argument. The third parameter is a pointer to the meta data
943** to be associated with the Nth user function argument value. The fourth
944** parameter specifies a 'delete function' that will be called on the meta
945** data pointer to release it when it is no longer required. If the delete
946** function pointer is NULL, it is not invoked.
947**
948** In practice, meta-data is preserved between function calls for
949** expressions that are constant at compile time. This includes literal
950** values and SQL variables.
951*/
952void *sqlite3_get_auxdata(sqlite3_context*, int);
953void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
954
drha2854222004-06-17 19:04:17 +0000955
956/*
957** These are special value for the destructor that is passed in as the
958** final argument to routines like sqlite3_result_blob(). If the destructor
959** argument is SQLITE_STATIC, it means that the content pointer is constant
960** and will never change. It does not need to be destroyed. The
961** SQLITE_TRANSIENT value means that the content will likely change in
962** the near future and that SQLite should make its own private copy of
963** the content before returning.
964*/
danielk1977d8123362004-06-12 09:25:12 +0000965#define SQLITE_STATIC ((void(*)(void *))0)
966#define SQLITE_TRANSIENT ((void(*)(void *))-1)
967
danielk1977682f68b2004-06-05 10:22:17 +0000968/*
drh4f26d6c2004-05-26 23:25:30 +0000969** User-defined functions invoke the following routines in order to
970** set their return value.
danielk19777e18c252004-05-25 11:47:24 +0000971*/
danielk1977d8123362004-06-12 09:25:12 +0000972void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +0000973void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +0000974void sqlite3_result_error(sqlite3_context*, const char*, int);
975void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +0000976void sqlite3_result_int(sqlite3_context*, int);
977void sqlite3_result_int64(sqlite3_context*, long long int);
978void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +0000979void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
980void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
981void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
982void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +0000983void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +0000984
drh52619df2004-06-11 17:48:02 +0000985/*
986** These are the allowed values for the eTextRep argument to
987** sqlite3_create_collation and sqlite3_create_function.
988*/
danielk1977466be562004-06-10 02:16:01 +0000989#define SQLITE_UTF8 1
danielk1977dc8453f2004-06-12 00:42:34 +0000990#define SQLITE_UTF16LE 2
991#define SQLITE_UTF16BE 3
992#define SQLITE_UTF16 4 /* Use native byte order */
drh52619df2004-06-11 17:48:02 +0000993#define SQLITE_ANY 5 /* sqlite3_create_function only */
danielk1977466be562004-06-10 02:16:01 +0000994
danielk19777cedc8d2004-06-10 10:50:08 +0000995/*
996** These two functions are used to add new collation sequences to the
997** sqlite3 handle specified as the first argument.
998**
999** The name of the new collation sequence is specified as a UTF-8 string
1000** for sqlite3_create_collation() and a UTF-16 string for
1001** sqlite3_create_collation16(). In both cases the name is passed as the
1002** second function argument.
1003**
1004** The third argument must be one of the constants SQLITE_UTF8,
1005** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1006** routine expects to be passed pointers to strings encoded using UTF-8,
1007** UTF-16 little-endian or UTF-16 big-endian respectively.
1008**
1009** A pointer to the user supplied routine must be passed as the fifth
1010** argument. If it is NULL, this is the same as deleting the collation
1011** sequence (so that SQLite cannot call it anymore). Each time the user
1012** supplied function is invoked, it is passed a copy of the void* passed as
1013** the fourth argument to sqlite3_create_collation() or
1014** sqlite3_create_collation16() as its first parameter.
1015**
1016** The remaining arguments to the user-supplied routine are two strings,
1017** each represented by a [length, data] pair and encoded in the encoding
1018** that was passed as the third argument when the collation sequence was
1019** registered. The user routine should return negative, zero or positive if
1020** the first string is less than, equal to, or greater than the second
1021** string. i.e. (STRING1 - STRING2).
1022*/
danielk19770202b292004-06-09 09:55:16 +00001023int sqlite3_create_collation(
1024 sqlite3*,
1025 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001026 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001027 void*,
1028 int(*xCompare)(void*,int,const void*,int,const void*)
1029);
1030int sqlite3_create_collation16(
1031 sqlite3*,
1032 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001033 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001034 void*,
1035 int(*xCompare)(void*,int,const void*,int,const void*)
1036);
1037
danielk19777cedc8d2004-06-10 10:50:08 +00001038/*
1039** To avoid having to register all collation sequences before a database
1040** can be used, a single callback function may be registered with the
1041** database handle to be called whenever an undefined collation sequence is
1042** required.
1043**
1044** If the function is registered using the sqlite3_collation_needed() API,
1045** then it is passed the names of undefined collation sequences as strings
1046** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1047** are passed as UTF-16 in machine native byte order. A call to either
1048** function replaces any existing callback.
1049**
1050** When the user-function is invoked, the first argument passed is a copy
1051** of the second argument to sqlite3_collation_needed() or
1052** sqlite3_collation_needed16(). The second argument is the database
1053** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1054** SQLITE_UTF16LE, indicating the most desirable form of the collation
1055** sequence function required. The fourth parameter is the name of the
1056** required collation sequence.
1057**
1058** The collation sequence is returned to SQLite by a collation-needed
1059** callback using the sqlite3_create_collation() or
1060** sqlite3_create_collation16() APIs, described above.
1061*/
1062int sqlite3_collation_needed(
1063 sqlite3*,
1064 void*,
1065 void(*)(void*,sqlite3*,int eTextRep,const char*)
1066);
1067int sqlite3_collation_needed16(
1068 sqlite3*,
1069 void*,
1070 void(*)(void*,sqlite3*,int eTextRep,const void*)
1071);
1072
danielk19770202b292004-06-09 09:55:16 +00001073
drh382c0242001-10-06 16:33:02 +00001074#ifdef __cplusplus
1075} /* End of the 'extern "C"' block */
1076#endif
danielk19774adee202004-05-08 08:23:19 +00001077#endif