blob: e710ada5d1152a4b7b91ef2b05398be9ad2d8bad [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**
danielk1977682f68b2004-06-05 10:22:17 +000015** @(#) $Id: sqlite.h.in,v 1.92 2004/06/05 10:22:18 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*/
44typedef struct sqlite sqlite;
danielk197765904932004-05-26 06:18:37 +000045typedef struct sqlite sqlite3;
46
drh75897232000-05-29 14:26:00 +000047
48/*
drh75897232000-05-29 14:26:00 +000049** A function to close the database.
50**
51** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +000052** returned from sqlite3_open() and the corresponding database will by closed.
drh75897232000-05-29 14:26:00 +000053*/
danielk19776f8a5032004-05-10 10:34:51 +000054void sqlite3_close(sqlite *);
drh75897232000-05-29 14:26:00 +000055
56/*
57** The type for a callback function.
58*/
59typedef int (*sqlite_callback)(void*,int,char**, char**);
60
61/*
62** A function to executes one or more statements of SQL.
63**
64** If one or more of the SQL statements are queries, then
65** the callback function specified by the 3rd parameter is
66** invoked once for each row of the query result. This callback
67** should normally return 0. If the callback returns a non-zero
68** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +000069** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +000070**
71** The 4th parameter is an arbitrary pointer that is passed
72** to the callback function as its first parameter.
73**
74** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +000075** columns in the query result. The 3rd parameter to the callback
76** is an array of strings holding the values for each column.
77** The 4th parameter to the callback is an array of strings holding
78** the names of each column.
drh75897232000-05-29 14:26:00 +000079**
80** The callback function may be NULL, even for queries. A NULL
81** callback is not an error. It just means that no callback
82** will be invoked.
83**
84** If an error occurs while parsing or evaluating the SQL (but
85** not while executing the callback) then an appropriate error
86** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +000087** *errmsg is made to point to that message. The calling function
88** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +000089** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +000090** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +000091**
92** The return value is is SQLITE_OK if there are no errors and
93** some other return code if there is an error. The particular
94** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +000095**
96** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +000097** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +000098** behavior can be modified somewhat using the sqlite3_busy_handler()
99** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000100*/
danielk19776f8a5032004-05-10 10:34:51 +0000101int sqlite3_exec(
drh75897232000-05-29 14:26:00 +0000102 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000103 const char *sql, /* SQL to be executed */
drh75897232000-05-29 14:26:00 +0000104 sqlite_callback, /* Callback function */
105 void *, /* 1st argument to callback function */
106 char **errmsg /* Error msg written here */
107);
108
drh58b95762000-06-02 01:17:37 +0000109/*
danielk19776f8a5032004-05-10 10:34:51 +0000110** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000111*/
drh717e6402001-09-27 03:22:32 +0000112#define SQLITE_OK 0 /* Successful result */
113#define SQLITE_ERROR 1 /* SQL error or missing database */
114#define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */
115#define SQLITE_PERM 3 /* Access permission denied */
116#define SQLITE_ABORT 4 /* Callback routine requested an abort */
117#define SQLITE_BUSY 5 /* The database file is locked */
118#define SQLITE_LOCKED 6 /* A table in the database is locked */
119#define SQLITE_NOMEM 7 /* A malloc() failed */
120#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000121#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000122#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
123#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
124#define SQLITE_NOTFOUND 12 /* (Internal Only) Table or record not found */
125#define SQLITE_FULL 13 /* Insertion failed because database is full */
126#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
127#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000128#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000129#define SQLITE_SCHEMA 17 /* The database schema changed */
130#define SQLITE_TOOBIG 18 /* Too much data for one row of a table */
131#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000132#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000133#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000134#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000135#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000136#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000137#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000138#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000139#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
140#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh717e6402001-09-27 03:22:32 +0000141
drhaf9ff332002-01-16 21:00:27 +0000142/*
143** Each entry in an SQLite table has a unique integer key. (The key is
144** the value of the INTEGER PRIMARY KEY column if there is such a column,
145** otherwise the key is generated at random. The unique key is always
146** available as the ROWID, OID, or _ROWID_ column.) The following routine
147** returns the integer key of the most recent insert in the database.
148**
149** This function is similar to the mysql_insert_id() function from MySQL.
150*/
drhf9b596e2004-05-26 16:54:42 +0000151long long int sqlite3_last_insert_rowid(sqlite*);
drhaf9ff332002-01-16 21:00:27 +0000152
drhc8d30ac2002-04-12 10:08:59 +0000153/*
154** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000155** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000156**
157** All changes are counted, even if they were later undone by a
158** ROLLBACK or ABORT. Except, changes associated with creating and
159** dropping tables are not counted.
160**
danielk19776f8a5032004-05-10 10:34:51 +0000161** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000162** in the inner, recursive call are counted together with the changes
163** in the outer call.
164**
165** SQLite implements the command "DELETE FROM table" without a WHERE clause
166** by dropping and recreating the table. (This is much faster than going
167** through and deleting individual elements form the table.) Because of
168** this optimization, the change count for "DELETE FROM table" will be
169** zero regardless of the number of elements that were originally in the
170** table. To get an accurate count of the number of rows deleted, use
171** "DELETE FROM table WHERE 1" instead.
172*/
danielk19776f8a5032004-05-10 10:34:51 +0000173int sqlite3_changes(sqlite*);
drhc8d30ac2002-04-12 10:08:59 +0000174
rdcf146a772004-02-25 22:51:06 +0000175/*
176** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000177** by the last INSERT, UPDATE, or DELETE statment executed by sqlite3_exec(),
rdcf146a772004-02-25 22:51:06 +0000178** or by the last VM to run to completion. The change count is not updated
179** by SQL statements other than INSERT, UPDATE or DELETE.
180**
181** Changes are counted, even if they are later undone by a ROLLBACK or
182** ABORT. Changes associated with trigger programs that execute as a
183** result of the INSERT, UPDATE, or DELETE statement are not counted.
184**
danielk19776f8a5032004-05-10 10:34:51 +0000185** If a callback invokes sqlite3_exec() recursively, then the changes
rdcf146a772004-02-25 22:51:06 +0000186** in the inner, recursive call are counted together with the changes
187** in the outer call.
188**
189** SQLite implements the command "DELETE FROM table" without a WHERE clause
190** by dropping and recreating the table. (This is much faster than going
191** through and deleting individual elements form the table.) Because of
192** this optimization, the change count for "DELETE FROM table" will be
193** zero regardless of the number of elements that were originally in the
194** table. To get an accurate count of the number of rows deleted, use
195** "DELETE FROM table WHERE 1" instead.
196**
197******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
198*/
danielk19776f8a5032004-05-10 10:34:51 +0000199int sqlite3_last_statement_changes(sqlite*);
rdcf146a772004-02-25 22:51:06 +0000200
drh4c504392000-10-16 22:06:40 +0000201/* This function causes any pending database operation to abort and
202** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000203** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000204** or Ctrl-C where the user wants a long query operation to halt
205** immediately.
206*/
danielk19776f8a5032004-05-10 10:34:51 +0000207void sqlite3_interrupt(sqlite*);
drh4c504392000-10-16 22:06:40 +0000208
drheec553b2000-06-02 01:51:20 +0000209
danielk197761de0d12004-05-27 23:56:16 +0000210/* These functions return true if the given input string comprises
211** one or more complete SQL statements. For the sqlite3_complete() call,
212** the parameter must be a nul-terminated UTF-8 string. For
213** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
214** is required.
drh75897232000-05-29 14:26:00 +0000215**
216** The algorithm is simple. If the last token other than spaces
217** and comments is a semicolon, then return true. otherwise return
218** false.
219*/
danielk19776f8a5032004-05-10 10:34:51 +0000220int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000221int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000222
drh2dfbbca2000-07-28 14:32:48 +0000223/*
224** This routine identifies a callback function that is invoked
225** whenever an attempt is made to open a database table that is
226** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000227** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000228** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000229** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000230** second argument is the name of the locked table and the third
231** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000232** busy callback returns 0, then sqlite3_exec() immediately returns
233** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000234** tries to open the table again and the cycle repeats.
235**
236** The default busy callback is NULL.
237**
238** Sqlite is re-entrant, so the busy handler may start a new query.
239** (It is not clear why anyone would every want to do this, but it
240** is allowed, in theory.) But the busy handler may not close the
241** database. Closing the database from a busy handler will delete
242** data structures out from under the executing query and will
243** probably result in a coredump.
244*/
danielk19776f8a5032004-05-10 10:34:51 +0000245void sqlite3_busy_handler(sqlite*, int(*)(void*,const char*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000246
247/*
248** This routine sets a busy handler that sleeps for a while when a
249** table is locked. The handler will sleep multiple times until
250** at least "ms" milleseconds of sleeping have been done. After
251** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000252** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000253**
254** Calling this routine with an argument less than or equal to zero
255** turns off all busy handlers.
256*/
danielk19776f8a5032004-05-10 10:34:51 +0000257void sqlite3_busy_timeout(sqlite*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000258
drhe3710332000-09-29 13:30:53 +0000259/*
danielk19776f8a5032004-05-10 10:34:51 +0000260** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000261** Instead of invoking a user-supplied callback for each row of the
262** result, this routine remembers each row of the result in memory
263** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000264** query has finished.
265**
266** As an example, suppose the query result where this table:
267**
268** Name | Age
269** -----------------------
270** Alice | 43
271** Bob | 28
272** Cindy | 21
273**
274** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000275** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000276**
277** azResult[0] = "Name";
278** azResult[1] = "Age";
279** azResult[2] = "Alice";
280** azResult[3] = "43";
281** azResult[4] = "Bob";
282** azResult[5] = "28";
283** azResult[6] = "Cindy";
284** azResult[7] = "21";
285**
286** Notice that there is an extra row of data containing the column
287** headers. But the *nrow return value is still 3. *ncolumn is
288** set to 2. In general, the number of values inserted into azResult
289** will be ((*nrow) + 1)*(*ncolumn).
290**
291** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000292** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000293** release the memory that was malloc-ed. Because of the way the
294** malloc() happens, the calling function must not try to call
danielk19776f8a5032004-05-10 10:34:51 +0000295** malloc() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000296** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000297**
danielk19776f8a5032004-05-10 10:34:51 +0000298** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000299*/
danielk19776f8a5032004-05-10 10:34:51 +0000300int sqlite3_get_table(
drhe3710332000-09-29 13:30:53 +0000301 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000302 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000303 char ***resultp, /* Result written to a char *[] that this points to */
304 int *nrow, /* Number of result rows written here */
305 int *ncolumn, /* Number of result columns written here */
306 char **errmsg /* Error msg written here */
307);
308
309/*
danielk19776f8a5032004-05-10 10:34:51 +0000310** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000311*/
danielk19776f8a5032004-05-10 10:34:51 +0000312void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000313
drha18c5682000-10-08 22:20:57 +0000314/*
drh4f26d6c2004-05-26 23:25:30 +0000315** The following routines are variants of the "sprintf()" from the
316** standard C library. The resulting string is written into memory
317** obtained from malloc() so that there is never a possiblity of buffer
318** overflow. These routines also implement some additional formatting
319** options that are useful for constructing SQL statements.
320**
321** The strings returned by these routines should be freed by calling
322** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000323**
324** All of the usual printf formatting options apply. In addition, there
325** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000326** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000327** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000328** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000329** the string.
330**
331** For example, so some string variable contains text as follows:
332**
333** char *zText = "It's a happy day!";
334**
335** We can use this text in an SQL statement as follows:
336**
danielk19776f8a5032004-05-10 10:34:51 +0000337** sqlite3_exec_printf(db, "INSERT INTO table VALUES('%q')",
drha18c5682000-10-08 22:20:57 +0000338** callback1, 0, 0, zText);
339**
340** Because the %q format string is used, the '\'' character in zText
341** is escaped and the SQL generated is as follows:
342**
343** INSERT INTO table1 VALUES('It''s a happy day!')
344**
345** This is correct. Had we used %s instead of %q, the generated SQL
346** would have looked like this:
347**
348** INSERT INTO table1 VALUES('It's a happy day!');
349**
350** This second example is an SQL syntax error. As a general rule you
351** should always use %q instead of %s when inserting text into a string
352** literal.
353*/
danielk19776f8a5032004-05-10 10:34:51 +0000354char *sqlite3_mprintf(const char*,...);
355char *sqlite3_vmprintf(const char*, va_list);
drh4f26d6c2004-05-26 23:25:30 +0000356void sqlite3_free(char *z);
drh5191b7e2002-03-08 02:12:00 +0000357
358/*
drhed6c8672003-01-12 18:02:16 +0000359** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000360** callback is invoked (at compile-time, not at run-time) for each
361** attempt to access a column of a table in the database. The callback
362** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
363** SQL statement should be aborted with an error and SQLITE_IGNORE
364** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000365*/
danielk19776f8a5032004-05-10 10:34:51 +0000366int sqlite3_set_authorizer(
drhed6c8672003-01-12 18:02:16 +0000367 sqlite*,
drhe22a3342003-04-22 20:30:37 +0000368 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000369 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000370);
371
372/*
373** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000374** be one of the values below. These values signify what kind of operation
375** is to be authorized. The 3rd and 4th parameters to the authorization
376** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000377** codes is used as the second parameter. The 5th parameter is the name
378** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000379** is the name of the inner-most trigger or view that is responsible for
380** the access attempt or NULL if this access attempt is directly from
381** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000382**
383** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000384*/
drh77ad4e42003-01-14 02:49:27 +0000385#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000386#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
387#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
388#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
389#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000390#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000391#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000392#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000393#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
394#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000395#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000396#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000397#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000398#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000399#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000400#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000401#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000402#define SQLITE_DROP_VIEW 17 /* View Name NULL */
403#define SQLITE_INSERT 18 /* Table Name NULL */
404#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
405#define SQLITE_READ 20 /* Table Name Column Name */
406#define SQLITE_SELECT 21 /* NULL NULL */
407#define SQLITE_TRANSACTION 22 /* NULL NULL */
408#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000409#define SQLITE_ATTACH 24 /* Filename NULL */
410#define SQLITE_DETACH 25 /* Database Name NULL */
411
drhed6c8672003-01-12 18:02:16 +0000412
413/*
414** The return value of the authorization function should be one of the
415** following constants:
416*/
417/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
418#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
419#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
420
421/*
danielk19776f8a5032004-05-10 10:34:51 +0000422** Register a function that is called at every invocation of sqlite3_exec()
danielk19774ad17132004-05-21 01:47:26 +0000423** or sqlite3_prepare(). This function can be used (for example) to generate
drhb86ccfb2003-01-28 23:13:10 +0000424** a log file of all SQL executed against a database.
drh18de4822003-01-16 16:28:53 +0000425*/
danielk19776f8a5032004-05-10 10:34:51 +0000426void *sqlite3_trace(sqlite*, void(*xTrace)(void*,const char*), void*);
drh18de4822003-01-16 16:28:53 +0000427
danielk1977348bb5d2003-10-18 09:37:26 +0000428/*
429** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000430** is invoked periodically during long running calls to sqlite3_exec(),
431** sqlite3_step() and sqlite3_get_table(). An example use for this API is to keep
danielk1977348bb5d2003-10-18 09:37:26 +0000432** a GUI updated during a large query.
433**
434** The progress callback is invoked once for every N virtual machine opcodes,
435** where N is the second argument to this function. The progress callback
436** itself is identified by the third argument to this function. The fourth
437** argument to this function is a void pointer passed to the progress callback
438** function each time it is invoked.
439**
danielk19776f8a5032004-05-10 10:34:51 +0000440** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000441** in less than N opcodes being executed, then the progress callback is not
442** invoked.
443**
danielk1977348bb5d2003-10-18 09:37:26 +0000444** To remove the progress callback altogether, pass NULL as the third
445** argument to this function.
446**
447** If the progress callback returns a result other than 0, then the current
448** query is immediately terminated and any database changes rolled back. If the
449** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000450** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000451**
452******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000453*/
danielk19776f8a5032004-05-10 10:34:51 +0000454void sqlite3_progress_handler(sqlite*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000455
drhaa940ea2004-01-15 02:44:03 +0000456/*
457** Register a callback function to be invoked whenever a new transaction
458** is committed. The pArg argument is passed through to the callback.
459** callback. If the callback function returns non-zero, then the commit
460** is converted into a rollback.
461**
462** If another function was previously registered, its pArg value is returned.
463** Otherwise NULL is returned.
464**
465** Registering a NULL function disables the callback.
466**
467******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
468*/
danielk19776f8a5032004-05-10 10:34:51 +0000469void *sqlite3_commit_hook(sqlite*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000470
drh22fbcb82004-02-01 01:22:50 +0000471/*
drh4f26d6c2004-05-26 23:25:30 +0000472** Open the sqlite database file "filename". The "filename" is UTF-8
473** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
474** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
475** if an error occurs. If the database is opened (or created) successfully,
476** then SQLITE_OK is returned. Otherwise an error code is returned. The
477** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
478** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000479**
drh4f26d6c2004-05-26 23:25:30 +0000480** If the database file does not exist, then a new database is created.
481** The encoding for the database is UTF-8 if sqlite3_open() is called and
482** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000483**
484** Whether or not an error occurs when it is opened, resources associated
485** with the sqlite3* handle should be released by passing it to
486** sqlite3_close() when it is no longer required.
487*/
488int sqlite3_open(
489 const char *filename, /* Database filename (UTF-8) */
490 sqlite3 **ppDb, /* OUT: SQLite db handle */
491 const char **args /* Null terminated array of option strings */
492);
danielk197765904932004-05-26 06:18:37 +0000493int sqlite3_open16(
494 const void *filename, /* Database filename (UTF-16) */
495 sqlite3 **ppDb, /* OUT: SQLite db handle */
496 const char **args /* Null terminated array of option strings */
497);
danielk1977295ba552004-05-19 10:34:51 +0000498
danielk197765904932004-05-26 06:18:37 +0000499/*
500** Return the error code for the most recent sqlite3_* API call associated
501** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
502** API call was successful.
503**
504** Calls to many sqlite3_* functions set the error code and string returned
505** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
506** (overwriting the previous values). Note that calls to sqlite3_errcode(),
507** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
508** results of future invocations.
509**
510** Assuming no other intervening sqlite3_* API calls are made, the error
511** code returned by this function is associated with the same error as
512** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
513*/
514int sqlite3_errcode(sqlite3 *db);
515
516/*
517** Return a pointer to a UTF-8 encoded string describing in english the
518** error condition for the most recent sqlite3_* API call. The returned
519** string is always terminated by an 0x00 byte.
520**
521** The string "not an error" is returned when the most recent API call was
522** successful.
523*/
524const char *sqlite3_errmsg(sqlite3*);
525
526/*
527** Return a pointer to a UTF-16 native byte order encoded string describing
528** in english the error condition for the most recent sqlite3_* API call.
529** The returned string is always terminated by a pair of 0x00 bytes.
530**
531** The string "not an error" is returned when the most recent API call was
532** successful.
533*/
534const void *sqlite3_errmsg16(sqlite3*);
535
536/*
537** An instance of the following opaque structure is used to represent
538** a compiled SQL statment.
539*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000540typedef struct sqlite3_stmt sqlite3_stmt;
541
danielk1977e3209e42004-05-20 01:40:18 +0000542/*
danielk197765904932004-05-26 06:18:37 +0000543** To execute an SQL query, it must first be compiled into a byte-code
544** program using one of the following routines. The only difference between
545** them is that the second argument, specifying the SQL statement to
546** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
547** function and UTF-16 for sqlite3_prepare16().
548**
549** The first parameter "db" is an SQLite database handle. The second
550** parameter "zSql" is the statement to be compiled, encoded as either
551** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
552** than zero, then zSql is read up to the first nul terminator. If
553** "nBytes" is not less than zero, then it is the length of the string zSql
554** in bytes (not characters).
555**
556** *pzTail is made to point to the first byte past the end of the first
557** SQL statement in zSql. This routine only compiles the first statement
558** in zSql, so *pzTail is left pointing to what remains uncompiled.
559**
560** *ppStmt is left pointing to a compiled SQL statement that can be
561** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
562** set to NULL. If the input text contained no SQL (if the input is and
563** empty string or a comment) then *ppStmt is set to NULL.
564**
565** On success, SQLITE_OK is returned. Otherwise an error code is returned.
566*/
567int sqlite3_prepare(
568 sqlite3 *db, /* Database handle */
569 const char *zSql, /* SQL statement, UTF-8 encoded */
570 int nBytes, /* Length of zSql in bytes. */
571 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
572 const char **pzTail /* OUT: Pointer to unused portion of zSql */
573);
574int sqlite3_prepare16(
575 sqlite3 *db, /* Database handle */
576 const void *zSql, /* SQL statement, UTF-16 encoded */
577 int nBytes, /* Length of zSql in bytes. */
578 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
579 const void **pzTail /* OUT: Pointer to unused portion of zSql */
580);
581
582/*
drhf4479502004-05-27 03:12:53 +0000583** Pointers to the following two opaque structures are used to communicate
584** with the implementations of user-defined functions.
585*/
586typedef struct sqlite3_context sqlite3_context;
587typedef struct Mem sqlite3_value;
588
589/*
drh4f26d6c2004-05-26 23:25:30 +0000590** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
591** one or more literals can be replace by a wildcard "?" or ":N:" where
592** N is an integer. These value of these wildcard literals can be set
593** using the routines listed below.
594**
595** In every case, the first parameter is a pointer to the sqlite3_stmt
596** structure returned from sqlite3_prepare(). The second parameter is the
597** index of the wildcard. The first "?" has an index of 1. ":N:" wildcards
598** use the index N.
599**
600** When the eCopy parameter is true, a copy of the value is made into
601** memory obtained and managed by SQLite. When eCopy is false, SQLite
602** assumes that the value is a constant and just stores a pointer to the
603** value without making a copy.
604**
605** The sqlite3_bind_* routine must be called before sqlite3_step() after
606** an sqlite3_prepare() or sqlite3_reset(). Unbound wildcards are interpreted
607** as NULL.
608*/
drhf4479502004-05-27 03:12:53 +0000609int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, int eCopy);
610int sqlite3_bind_double(sqlite3_stmt*, int, double);
611int sqlite3_bind_int(sqlite3_stmt*, int, int);
612int sqlite3_bind_int64(sqlite3_stmt*, int, long long int);
613int sqlite3_bind_null(sqlite3_stmt*, int);
614int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, int eCopy);
615int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int n, int eCopy);
616int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000617
618/*
danielk197765904932004-05-26 06:18:37 +0000619** Return the number of columns in the result set returned by the compiled
620** SQL statement. This routine returns 0 if pStmt is an SQL statement
621** that does not return data (for example an UPDATE).
622*/
623int sqlite3_column_count(sqlite3_stmt *pStmt);
624
625/*
626** The first parameter is a compiled SQL statement. This function returns
627** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000628** second function parameter. The string returned is UTF-8 for
629** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000630*/
631const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000632const void *sqlite3_column_name16(sqlite3_stmt*,int);
633
634/*
635** The first parameter is a compiled SQL statement. If this statement
636** is a SELECT statement, the Nth column of the returned result set
637** of the SELECT is a table column then the declared type of the table
638** column is returned. If the Nth column of the result set is not at table
639** column, then a NULL pointer is returned. The returned string is always
640** UTF-8 encoded. For example, in the database schema:
641**
642** CREATE TABLE t1(c1 VARIANT);
643**
644** And the following statement compiled:
645**
646** SELECT c1 + 1, 0 FROM t1;
647**
648** Then this routine would return the string "VARIANT" for the second
649** result column (i==1), and a NULL pointer for the first result column
650** (i==0).
651*/
652const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
653
654/*
655** The first parameter is a compiled SQL statement. If this statement
656** is a SELECT statement, the Nth column of the returned result set
657** of the SELECT is a table column then the declared type of the table
658** column is returned. If the Nth column of the result set is not at table
659** column, then a NULL pointer is returned. The returned string is always
660** UTF-16 encoded. For example, in the database schema:
661**
drh4f26d6c2004-05-26 23:25:30 +0000662** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000663**
664** And the following statement compiled:
665**
666** SELECT c1 + 1, 0 FROM t1;
667**
drh4f26d6c2004-05-26 23:25:30 +0000668** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000669** result column (i==1), and a NULL pointer for the first result column
670** (i==0).
671*/
672const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
673
danielk1977106bb232004-05-21 10:08:53 +0000674/*
675** After an SQL query has been compiled with a call to either
676** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
677** called one or more times to execute the statement.
678**
679** The return value will be either SQLITE_BUSY, SQLITE_DONE,
680** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
681**
682** SQLITE_BUSY means that the database engine attempted to open
683** a locked database and there is no busy callback registered.
684** Call sqlite3_step() again to retry the open.
685**
686** SQLITE_DONE means that the statement has finished executing
687** successfully. sqlite3_step() should not be called again on this virtual
688** machine.
689**
690** If the SQL statement being executed returns any data, then
691** SQLITE_ROW is returned each time a new row of data is ready
692** for processing by the caller. The values may be accessed using
693** the sqlite3_column_*() functions described below. sqlite3_step()
694** is called again to retrieve the next row of data.
695**
696** SQLITE_ERROR means that a run-time error (such as a constraint
697** violation) has occurred. sqlite3_step() should not be called again on
698** the VM. More information may be found by calling sqlite3_errmsg().
699**
700** SQLITE_MISUSE means that the this routine was called inappropriately.
701** Perhaps it was called on a virtual machine that had already been
702** finalized or on one that had previously returned SQLITE_ERROR or
703** SQLITE_DONE. Or it could be the case the the same database connection
704** is being used simulataneously by two or more threads.
705*/
danielk197717240fd2004-05-26 00:07:25 +0000706int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000707
danielk1977106bb232004-05-21 10:08:53 +0000708/*
709** Return the number of values in the current row of the result set.
710**
711** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
712** will return the same value as the sqlite3_column_count() function.
713** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
714** error code, or before sqlite3_step() has been called on a
715** compiled SQL statement, this routine returns zero.
716*/
danielk197793d46752004-05-23 13:30:58 +0000717int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000718
drh4f26d6c2004-05-26 23:25:30 +0000719/*
720** Values are stored in the database in one of the following fundamental
721** types.
722*/
drh9c054832004-05-31 18:51:57 +0000723#define SQLITE_INTEGER 1
724#define SQLITE_FLOAT 2
725#define SQLITE_TEXT 3
726#define SQLITE_BLOB 4
727#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000728
danielk1977106bb232004-05-21 10:08:53 +0000729/*
drh4f26d6c2004-05-26 23:25:30 +0000730** The next group of routines returns information about the information
731** in a single column of the current result row of a query. In every
732** case the first parameter is a pointer to the SQL statement that is being
733** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
734** the second argument is the index of the column for which information
735** should be returned. iCol is zero-indexed. The left-most column as an
736** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000737**
drh4f26d6c2004-05-26 23:25:30 +0000738** If the SQL statement is not currently point to a valid row, or if the
739** the colulmn index is out of range, the result is undefined.
740**
741** These routines attempt to convert the value where appropriate. For
742** example, if the internal representation is FLOAT and a text result
743** is requested, sprintf() is used internally to do the conversion
744** automatically. The following table details the conversions that
745** are applied:
746**
747** Internal Type Requested Type Conversion
748** ------------- -------------- --------------------------
749** NULL INTEGER Result is 0
750** NULL FLOAT Result is 0.0
751** NULL TEXT Result is an empty string
752** NULL BLOB Result is a zero-length BLOB
753** INTEGER FLOAT Convert from integer to float
754** INTEGER TEXT ASCII rendering of the integer
755** INTEGER BLOB Same as for INTEGER->TEXT
756** FLOAT INTEGER Convert from float to integer
757** FLOAT TEXT ASCII rendering of the float
758** FLOAT BLOB Same as FLOAT->TEXT
759** TEXT INTEGER Use atoi()
760** TEXT FLOAT Use atof()
761** TEXT BLOB No change
762** BLOB INTEGER Convert to TEXT then use atoi()
763** BLOB FLOAT Convert to TEXT then use atof()
764** BLOB TEXT Add a \000 terminator if needed
765**
766** The following access routines are provided:
767**
768** _type() Return the datatype of the result. This is one of
769** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
770** or SQLITE_NULL.
771** _blob() Return the value of a BLOB.
772** _bytes() Return the number of bytes in a BLOB value or the number
773** of bytes in a TEXT value represented as UTF-8. The \000
774** terminator is included in the byte count for TEXT values.
775** _bytes16() Return the number of bytes in a BLOB value or the number
776** of bytes in a TEXT value represented as UTF-16. The \u0000
777** terminator is included in the byte count for TEXT values.
778** _double() Return a FLOAT value.
779** _int() Return an INTEGER value in the host computer's native
780** integer representation. This might be either a 32- or 64-bit
781** integer depending on the host.
782** _int64() Return an INTEGER value as a 64-bit signed integer.
783** _text() Return the value as UTF-8 text.
784** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000785*/
drhf4479502004-05-27 03:12:53 +0000786const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
787int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
788int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
789double sqlite3_column_double(sqlite3_stmt*, int iCol);
790int sqlite3_column_int(sqlite3_stmt*, int iCol);
791long long int sqlite3_column_int64(sqlite3_stmt*, int iCol);
792const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
793const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000794int sqlite3_column_type(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000795
danielk197765904932004-05-26 06:18:37 +0000796/*
797** The sqlite3_finalize() function is called to delete a compiled
798** SQL statement obtained by a previous call to sqlite3_prepare()
799** or sqlite3_prepare16(). If the statement was executed successfully, or
800** not executed at all, then SQLITE_OK is returned. If execution of the
801** statement failed then an error code is returned.
802**
803** This routine can be called at any point during the execution of the
804** virtual machine. If the virtual machine has not completed execution
805** when this routine is called, that is like encountering an error or
806** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
807** rolled back and transactions cancelled, depending on the circumstances,
808** and the result code returned will be SQLITE_ABORT.
809*/
810int sqlite3_finalize(sqlite3_stmt *pStmt);
811
812/*
813** The sqlite3_reset() function is called to reset a compiled SQL
814** statement obtained by a previous call to sqlite3_prepare() or
815** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
816** Any SQL statement variables that had values bound to them using
817** the sqlite3_bind_*() API retain their values.
818*/
819int sqlite3_reset(sqlite3_stmt *pStmt);
820
821/*
danielk197765904932004-05-26 06:18:37 +0000822** The following two functions are used to add user functions or aggregates
823** implemented in C to the SQL langauge interpreted by SQLite. The
824** difference only between the two is that the second parameter, the
825** name of the (scalar) function or aggregate, is encoded in UTF-8 for
826** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
827**
828** The first argument is the database handle that the new function or
829** aggregate is to be added to. If a single program uses more than one
830** database handle internally, then user functions or aggregates must
831** be added individually to each database handle with which they will be
832** used.
833**
834** The third parameter is the number of arguments that the function or
835** aggregate takes. If this parameter is negative, then the function or
836** aggregate may take any number of arguments.
837**
838** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
839** pointers to user implemented C functions that implement the user
840** function or aggregate. A scalar function requires an implementation of
841** the xFunc callback only, NULL pointers should be passed as the xStep
842** and xFinal parameters. An aggregate function requires an implementation
843** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
844** existing user function or aggregate, pass NULL for all three function
845** callback. Specifying an inconstent set of callback values, such as an
846** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
847** returned.
848*/
849int sqlite3_create_function(
850 sqlite3 *,
851 const char *zFunctionName,
852 int nArg,
853 int eTextRep,
854 int iCollateArg,
855 void*,
856 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
857 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
858 void (*xFinal)(sqlite3_context*)
859);
860int sqlite3_create_function16(
861 sqlite3*,
862 const void *zFunctionName,
863 int nArg,
864 int eTextRep,
865 int iCollateArg,
866 void*,
867 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
868 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
869 void (*xFinal)(sqlite3_context*)
870);
871
872/*
danielk197765904932004-05-26 06:18:37 +0000873** The next routine returns the number of calls to xStep for a particular
874** aggregate function instance. The current call to xStep counts so this
875** routine always returns at least 1.
876*/
877int sqlite3_aggregate_count(sqlite3_context*);
878
danielk19770ffba6b2004-05-24 09:10:10 +0000879/*
drh4f26d6c2004-05-26 23:25:30 +0000880** The next group of routines returns information about parameters to
881** a user-defined function. Function implementations use these routines
882** to access their parameters. These routines are the same as the
883** sqlite3_column_* routines except that these routines take a single
884** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
885** column number.
danielk19770ffba6b2004-05-24 09:10:10 +0000886*/
drhf4479502004-05-27 03:12:53 +0000887const void *sqlite3_value_blob(sqlite3_value*);
888int sqlite3_value_bytes(sqlite3_value*);
889int sqlite3_value_bytes16(sqlite3_value*);
890double sqlite3_value_double(sqlite3_value*);
891int sqlite3_value_int(sqlite3_value*);
892long long int sqlite3_value_int64(sqlite3_value*);
893const unsigned char *sqlite3_value_text(sqlite3_value*);
894const void *sqlite3_value_text16(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +0000895int sqlite3_value_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +0000896
897/*
danielk19770ae8b832004-05-25 12:05:56 +0000898** Aggregate functions use the following routine to allocate
899** a structure for storing their state. The first time this routine
900** is called for a particular aggregate, a new structure of size nBytes
901** is allocated, zeroed, and returned. On subsequent calls (for the
902** same aggregate instance) the same buffer is returned. The implementation
903** of the aggregate can use the returned buffer to accumulate data.
904**
905** The buffer allocated is freed automatically by SQLite.
906*/
drh4f26d6c2004-05-26 23:25:30 +0000907void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +0000908
909/*
910** The pUserData parameter to the sqlite3_create_function() and
911** sqlite3_create_aggregate() routines used to register user functions
912** is available to the implementation of the function using this
913** call.
914*/
915void *sqlite3_user_data(sqlite3_context*);
916
917/*
danielk1977682f68b2004-06-05 10:22:17 +0000918** The following two functions may be used by scalar user functions to
919** associate meta-data with argument values. If the same value is passed to
920** multiple invocations of the user-function during query execution, under
921** some circumstances the associated meta-data may be preserved. This may
922** be used, for example, to add a regular-expression matching scalar
923** function. The compiled version of the regular expression is stored as
924** meta-data associated with the SQL value passed as the regular expression
925** pattern.
926**
927** Calling sqlite3_get_auxdata() returns a pointer to the meta data
928** associated with the Nth argument value to the current user function
929** call, where N is the second parameter. If no meta-data has been set for
930** that value, then a NULL pointer is returned.
931**
932** The sqlite3_set_auxdata() is used to associate meta data with a user
933** function argument. The third parameter is a pointer to the meta data
934** to be associated with the Nth user function argument value. The fourth
935** parameter specifies a 'delete function' that will be called on the meta
936** data pointer to release it when it is no longer required. If the delete
937** function pointer is NULL, it is not invoked.
938**
939** In practice, meta-data is preserved between function calls for
940** expressions that are constant at compile time. This includes literal
941** values and SQL variables.
942*/
943void *sqlite3_get_auxdata(sqlite3_context*, int);
944void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
945
946/*
drh4f26d6c2004-05-26 23:25:30 +0000947** User-defined functions invoke the following routines in order to
948** set their return value.
danielk19777e18c252004-05-25 11:47:24 +0000949*/
950void sqlite3_result_blob(sqlite3_context*, const void*, int n, int eCopy);
drh4f26d6c2004-05-26 23:25:30 +0000951void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +0000952void sqlite3_result_error(sqlite3_context*, const char*, int);
953void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +0000954void sqlite3_result_int(sqlite3_context*, int);
955void sqlite3_result_int64(sqlite3_context*, long long int);
956void sqlite3_result_null(sqlite3_context*);
957void sqlite3_result_text(sqlite3_context*, const char*, int n, int eCopy);
958void sqlite3_result_text16(sqlite3_context*, const void*, int n, int eCopy);
959void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +0000960
drh382c0242001-10-06 16:33:02 +0000961#ifdef __cplusplus
962} /* End of the 'extern "C"' block */
963#endif
danielk19774adee202004-05-08 08:23:19 +0000964#endif