blob: e532aea86d8cbd9078857957430d6630579a844d [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**
drhefad9992004-06-22 12:13:55 +000015** @(#) $Id: sqlite.h.in,v 1.106 2004/06/22 12:13:55 drh Exp $
drh75897232000-05-29 14:26:00 +000016*/
17#ifndef _SQLITE_H_
18#define _SQLITE_H_
drha18c5682000-10-08 22:20:57 +000019#include <stdarg.h> /* Needed for the definition of va_list */
drh75897232000-05-29 14:26:00 +000020
21/*
drh382c0242001-10-06 16:33:02 +000022** Make sure we can call this stuff from C++.
23*/
24#ifdef __cplusplus
25extern "C" {
26#endif
27
28/*
drhb86ccfb2003-01-28 23:13:10 +000029** The version of the SQLite library.
30*/
31#define SQLITE_VERSION "--VERS--"
32
33/*
drhb217a572000-08-22 13:40:18 +000034** The version string is also compiled into the library so that a program
35** can check to make sure that the lib*.a file and the *.h file are from
36** the same version.
37*/
danielk19776f8a5032004-05-10 10:34:51 +000038extern const char sqlite3_version[];
drh303aaa72000-08-17 10:22:34 +000039
40/*
drh75897232000-05-29 14:26:00 +000041** Each open sqlite database is represented by an instance of the
42** following opaque structure.
43*/
danielk197765904932004-05-26 06:18:37 +000044typedef struct sqlite sqlite3;
45
drh75897232000-05-29 14:26:00 +000046
47/*
drhefad9992004-06-22 12:13:55 +000048** Some compilers do not support the "long long" datatype. So we have
49** to do a typedef that for 64-bit integers that depends on what compiler
50** is being used.
51*/
52#if defined(_MSC_VER) || defined(__BORLANDC__)
53 typedef __int64 sqlite_int64;
54#else
55 typedef long long int sqlite_int64;
56#endif
57
58
59/*
drh75897232000-05-29 14:26:00 +000060** A function to close the database.
61**
62** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +000063** returned from sqlite3_open() and the corresponding database will by closed.
danielk197796d81f92004-06-19 03:33:57 +000064**
65** All SQL statements prepared using sqlite3_prepare() or
66** sqlite3_prepare16() must be deallocated using sqlite3_finalize() before
67** this routine is called. Otherwise, SQLITE_BUSY is returned and the
68** database connection remains open.
drh75897232000-05-29 14:26:00 +000069*/
danielk1977f9d64d22004-06-19 08:18:07 +000070int sqlite3_close(sqlite3 *);
drh75897232000-05-29 14:26:00 +000071
72/*
73** The type for a callback function.
74*/
75typedef int (*sqlite_callback)(void*,int,char**, char**);
76
77/*
78** A function to executes one or more statements of SQL.
79**
80** If one or more of the SQL statements are queries, then
81** the callback function specified by the 3rd parameter is
82** invoked once for each row of the query result. This callback
83** should normally return 0. If the callback returns a non-zero
84** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +000085** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +000086**
87** The 4th parameter is an arbitrary pointer that is passed
88** to the callback function as its first parameter.
89**
90** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +000091** columns in the query result. The 3rd parameter to the callback
92** is an array of strings holding the values for each column.
93** The 4th parameter to the callback is an array of strings holding
94** the names of each column.
drh75897232000-05-29 14:26:00 +000095**
96** The callback function may be NULL, even for queries. A NULL
97** callback is not an error. It just means that no callback
98** will be invoked.
99**
100** If an error occurs while parsing or evaluating the SQL (but
101** not while executing the callback) then an appropriate error
102** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +0000103** *errmsg is made to point to that message. The calling function
104** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +0000105** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +0000106** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +0000107**
108** The return value is is SQLITE_OK if there are no errors and
109** some other return code if there is an error. The particular
110** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +0000111**
112** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000113** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +0000114** behavior can be modified somewhat using the sqlite3_busy_handler()
115** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000116*/
danielk19776f8a5032004-05-10 10:34:51 +0000117int sqlite3_exec(
danielk1977f9d64d22004-06-19 08:18:07 +0000118 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000119 const char *sql, /* SQL to be executed */
drh75897232000-05-29 14:26:00 +0000120 sqlite_callback, /* Callback function */
121 void *, /* 1st argument to callback function */
122 char **errmsg /* Error msg written here */
123);
124
drh58b95762000-06-02 01:17:37 +0000125/*
danielk19776f8a5032004-05-10 10:34:51 +0000126** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000127*/
drh717e6402001-09-27 03:22:32 +0000128#define SQLITE_OK 0 /* Successful result */
129#define SQLITE_ERROR 1 /* SQL error or missing database */
130#define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */
131#define SQLITE_PERM 3 /* Access permission denied */
132#define SQLITE_ABORT 4 /* Callback routine requested an abort */
133#define SQLITE_BUSY 5 /* The database file is locked */
134#define SQLITE_LOCKED 6 /* A table in the database is locked */
135#define SQLITE_NOMEM 7 /* A malloc() failed */
136#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000137#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000138#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
139#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
140#define SQLITE_NOTFOUND 12 /* (Internal Only) Table or record not found */
141#define SQLITE_FULL 13 /* Insertion failed because database is full */
142#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
143#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000144#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000145#define SQLITE_SCHEMA 17 /* The database schema changed */
146#define SQLITE_TOOBIG 18 /* Too much data for one row of a table */
147#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000148#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000149#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000150#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000151#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000152#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000153#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000154#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000155#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
156#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh717e6402001-09-27 03:22:32 +0000157
drhaf9ff332002-01-16 21:00:27 +0000158/*
159** Each entry in an SQLite table has a unique integer key. (The key is
160** the value of the INTEGER PRIMARY KEY column if there is such a column,
161** otherwise the key is generated at random. The unique key is always
162** available as the ROWID, OID, or _ROWID_ column.) The following routine
163** returns the integer key of the most recent insert in the database.
164**
165** This function is similar to the mysql_insert_id() function from MySQL.
166*/
drhefad9992004-06-22 12:13:55 +0000167sqlite_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000168
drhc8d30ac2002-04-12 10:08:59 +0000169/*
170** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000171** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000172**
173** All changes are counted, even if they were later undone by a
174** ROLLBACK or ABORT. Except, changes associated with creating and
175** dropping tables are not counted.
176**
danielk19776f8a5032004-05-10 10:34:51 +0000177** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000178** in the inner, recursive call are counted together with the changes
179** in the outer call.
180**
181** SQLite implements the command "DELETE FROM table" without a WHERE clause
182** by dropping and recreating the table. (This is much faster than going
183** through and deleting individual elements form the table.) Because of
184** this optimization, the change count for "DELETE FROM table" will be
185** zero regardless of the number of elements that were originally in the
186** table. To get an accurate count of the number of rows deleted, use
187** "DELETE FROM table WHERE 1" instead.
188*/
danielk1977f9d64d22004-06-19 08:18:07 +0000189int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000190
rdcf146a772004-02-25 22:51:06 +0000191/*
danielk1977b28af712004-06-21 06:50:26 +0000192** This function returns the number of database rows that have been
193** modified by INSERT, UPDATE or DELETE statements since the database handle
194** was opened. This includes UPDATE, INSERT and DELETE statements executed
195** as part of trigger programs. All changes are counted as soon as the
196** statement that makes them is completed (when the statement handle is
197** passed to sqlite3_reset() or sqlite_finalise()).
rdcf146a772004-02-25 22:51:06 +0000198**
199** SQLite implements the command "DELETE FROM table" without a WHERE clause
200** by dropping and recreating the table. (This is much faster than going
201** through and deleting individual elements form the table.) Because of
202** this optimization, the change count for "DELETE FROM table" will be
203** zero regardless of the number of elements that were originally in the
204** table. To get an accurate count of the number of rows deleted, use
205** "DELETE FROM table WHERE 1" instead.
rdcf146a772004-02-25 22:51:06 +0000206*/
danielk1977b28af712004-06-21 06:50:26 +0000207int sqlite3_total_changes(sqlite3*);
208
209/*
210** This function returns the number of database rows that were changed
211** by the last INSERT, UPDATE, or DELETE statment completed. The change
212** count is not updated by SQL statements other than INSERT, UPDATE or
213** DELETE.
214**
215** Changes are counted, even if they are later undone by a ROLLBACK or
216** ABORT. Changes associated with trigger programs that execute as a
217** result of the INSERT, UPDATE, or DELETE statement are not counted.
218**
219** SQLite implements the command "DELETE FROM table" without a WHERE clause
220** by dropping and recreating the table. (This is much faster than going
221** through and deleting individual elements form the table.) Because of
222** this optimization, the change count for "DELETE FROM table" will be
223** zero regardless of the number of elements that were originally in the
224** table. To get an accurate count of the number of rows deleted, use
225** "DELETE FROM table WHERE 1" instead.
226*/
227int sqlite3_changes(sqlite3*);
rdcf146a772004-02-25 22:51:06 +0000228
drh4c504392000-10-16 22:06:40 +0000229/* This function causes any pending database operation to abort and
230** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000231** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000232** or Ctrl-C where the user wants a long query operation to halt
233** immediately.
234*/
danielk1977f9d64d22004-06-19 08:18:07 +0000235void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000236
drheec553b2000-06-02 01:51:20 +0000237
danielk197761de0d12004-05-27 23:56:16 +0000238/* These functions return true if the given input string comprises
239** one or more complete SQL statements. For the sqlite3_complete() call,
240** the parameter must be a nul-terminated UTF-8 string. For
241** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
242** is required.
drh75897232000-05-29 14:26:00 +0000243**
244** The algorithm is simple. If the last token other than spaces
245** and comments is a semicolon, then return true. otherwise return
246** false.
247*/
danielk19776f8a5032004-05-10 10:34:51 +0000248int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000249int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000250
drh2dfbbca2000-07-28 14:32:48 +0000251/*
252** This routine identifies a callback function that is invoked
253** whenever an attempt is made to open a database table that is
254** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000255** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000256** it finds a locked table. If the busy callback is not NULL, then
danielk19776f8a5032004-05-10 10:34:51 +0000257** sqlite3_exec() invokes the callback with three arguments. The
drh2dfbbca2000-07-28 14:32:48 +0000258** second argument is the name of the locked table and the third
259** argument is the number of times the table has been busy. If the
danielk19776f8a5032004-05-10 10:34:51 +0000260** busy callback returns 0, then sqlite3_exec() immediately returns
261** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000262** tries to open the table again and the cycle repeats.
263**
264** The default busy callback is NULL.
265**
266** Sqlite is re-entrant, so the busy handler may start a new query.
267** (It is not clear why anyone would every want to do this, but it
268** is allowed, in theory.) But the busy handler may not close the
269** database. Closing the database from a busy handler will delete
270** data structures out from under the executing query and will
271** probably result in a coredump.
272*/
danielk1977f9d64d22004-06-19 08:18:07 +0000273int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000274
275/*
276** This routine sets a busy handler that sleeps for a while when a
277** table is locked. The handler will sleep multiple times until
278** at least "ms" milleseconds of sleeping have been done. After
279** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000280** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000281**
282** Calling this routine with an argument less than or equal to zero
283** turns off all busy handlers.
284*/
danielk1977f9d64d22004-06-19 08:18:07 +0000285int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000286
drhe3710332000-09-29 13:30:53 +0000287/*
danielk19776f8a5032004-05-10 10:34:51 +0000288** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000289** Instead of invoking a user-supplied callback for each row of the
290** result, this routine remembers each row of the result in memory
291** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000292** query has finished.
293**
294** As an example, suppose the query result where this table:
295**
296** Name | Age
297** -----------------------
298** Alice | 43
299** Bob | 28
300** Cindy | 21
301**
302** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000303** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000304**
305** azResult[0] = "Name";
306** azResult[1] = "Age";
307** azResult[2] = "Alice";
308** azResult[3] = "43";
309** azResult[4] = "Bob";
310** azResult[5] = "28";
311** azResult[6] = "Cindy";
312** azResult[7] = "21";
313**
314** Notice that there is an extra row of data containing the column
315** headers. But the *nrow return value is still 3. *ncolumn is
316** set to 2. In general, the number of values inserted into azResult
317** will be ((*nrow) + 1)*(*ncolumn).
318**
319** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000320** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000321** release the memory that was malloc-ed. Because of the way the
322** malloc() happens, the calling function must not try to call
danielk19776f8a5032004-05-10 10:34:51 +0000323** malloc() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000324** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000325**
danielk19776f8a5032004-05-10 10:34:51 +0000326** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000327*/
danielk19776f8a5032004-05-10 10:34:51 +0000328int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000329 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000330 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000331 char ***resultp, /* Result written to a char *[] that this points to */
332 int *nrow, /* Number of result rows written here */
333 int *ncolumn, /* Number of result columns written here */
334 char **errmsg /* Error msg written here */
335);
336
337/*
danielk19776f8a5032004-05-10 10:34:51 +0000338** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000339*/
danielk19776f8a5032004-05-10 10:34:51 +0000340void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000341
drha18c5682000-10-08 22:20:57 +0000342/*
drh4f26d6c2004-05-26 23:25:30 +0000343** The following routines are variants of the "sprintf()" from the
344** standard C library. The resulting string is written into memory
345** obtained from malloc() so that there is never a possiblity of buffer
346** overflow. These routines also implement some additional formatting
347** options that are useful for constructing SQL statements.
348**
349** The strings returned by these routines should be freed by calling
350** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000351**
352** All of the usual printf formatting options apply. In addition, there
353** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000354** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000355** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000356** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000357** the string.
358**
359** For example, so some string variable contains text as follows:
360**
361** char *zText = "It's a happy day!";
362**
363** We can use this text in an SQL statement as follows:
364**
danielk19776f8a5032004-05-10 10:34:51 +0000365** sqlite3_exec_printf(db, "INSERT INTO table VALUES('%q')",
drha18c5682000-10-08 22:20:57 +0000366** callback1, 0, 0, zText);
367**
368** Because the %q format string is used, the '\'' character in zText
369** is escaped and the SQL generated is as follows:
370**
371** INSERT INTO table1 VALUES('It''s a happy day!')
372**
373** This is correct. Had we used %s instead of %q, the generated SQL
374** would have looked like this:
375**
376** INSERT INTO table1 VALUES('It's a happy day!');
377**
378** This second example is an SQL syntax error. As a general rule you
379** should always use %q instead of %s when inserting text into a string
380** literal.
381*/
danielk19776f8a5032004-05-10 10:34:51 +0000382char *sqlite3_mprintf(const char*,...);
383char *sqlite3_vmprintf(const char*, va_list);
drh4f26d6c2004-05-26 23:25:30 +0000384void sqlite3_free(char *z);
drh5191b7e2002-03-08 02:12:00 +0000385
386/*
drhed6c8672003-01-12 18:02:16 +0000387** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000388** callback is invoked (at compile-time, not at run-time) for each
389** attempt to access a column of a table in the database. The callback
390** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
391** SQL statement should be aborted with an error and SQLITE_IGNORE
392** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000393*/
danielk19776f8a5032004-05-10 10:34:51 +0000394int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000395 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000396 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000397 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000398);
399
400/*
401** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000402** be one of the values below. These values signify what kind of operation
403** is to be authorized. The 3rd and 4th parameters to the authorization
404** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000405** codes is used as the second parameter. The 5th parameter is the name
406** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000407** is the name of the inner-most trigger or view that is responsible for
408** the access attempt or NULL if this access attempt is directly from
409** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000410**
411** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000412*/
drh77ad4e42003-01-14 02:49:27 +0000413#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000414#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
415#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
416#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
417#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000418#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000419#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000420#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000421#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
422#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000423#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000424#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000425#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000426#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000427#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000428#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000429#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000430#define SQLITE_DROP_VIEW 17 /* View Name NULL */
431#define SQLITE_INSERT 18 /* Table Name NULL */
432#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
433#define SQLITE_READ 20 /* Table Name Column Name */
434#define SQLITE_SELECT 21 /* NULL NULL */
435#define SQLITE_TRANSACTION 22 /* NULL NULL */
436#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000437#define SQLITE_ATTACH 24 /* Filename NULL */
438#define SQLITE_DETACH 25 /* Database Name NULL */
439
drhed6c8672003-01-12 18:02:16 +0000440
441/*
442** The return value of the authorization function should be one of the
443** following constants:
444*/
445/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
446#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
447#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
448
449/*
danielk19776f8a5032004-05-10 10:34:51 +0000450** Register a function that is called at every invocation of sqlite3_exec()
danielk19774ad17132004-05-21 01:47:26 +0000451** or sqlite3_prepare(). This function can be used (for example) to generate
drhb86ccfb2003-01-28 23:13:10 +0000452** a log file of all SQL executed against a database.
drh18de4822003-01-16 16:28:53 +0000453*/
danielk1977f9d64d22004-06-19 08:18:07 +0000454void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh18de4822003-01-16 16:28:53 +0000455
danielk1977348bb5d2003-10-18 09:37:26 +0000456/*
457** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000458** is invoked periodically during long running calls to sqlite3_exec(),
459** sqlite3_step() and sqlite3_get_table(). An example use for this API is to keep
danielk1977348bb5d2003-10-18 09:37:26 +0000460** a GUI updated during a large query.
461**
462** The progress callback is invoked once for every N virtual machine opcodes,
463** where N is the second argument to this function. The progress callback
464** itself is identified by the third argument to this function. The fourth
465** argument to this function is a void pointer passed to the progress callback
466** function each time it is invoked.
467**
danielk19776f8a5032004-05-10 10:34:51 +0000468** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000469** in less than N opcodes being executed, then the progress callback is not
470** invoked.
471**
danielk1977348bb5d2003-10-18 09:37:26 +0000472** To remove the progress callback altogether, pass NULL as the third
473** argument to this function.
474**
475** If the progress callback returns a result other than 0, then the current
476** query is immediately terminated and any database changes rolled back. If the
477** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000478** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000479**
480******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000481*/
danielk1977f9d64d22004-06-19 08:18:07 +0000482void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000483
drhaa940ea2004-01-15 02:44:03 +0000484/*
485** Register a callback function to be invoked whenever a new transaction
486** is committed. The pArg argument is passed through to the callback.
487** callback. If the callback function returns non-zero, then the commit
488** is converted into a rollback.
489**
490** If another function was previously registered, its pArg value is returned.
491** Otherwise NULL is returned.
492**
493** Registering a NULL function disables the callback.
494**
495******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
496*/
danielk1977f9d64d22004-06-19 08:18:07 +0000497void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000498
drh22fbcb82004-02-01 01:22:50 +0000499/*
drh4f26d6c2004-05-26 23:25:30 +0000500** Open the sqlite database file "filename". The "filename" is UTF-8
501** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
502** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
503** if an error occurs. If the database is opened (or created) successfully,
504** then SQLITE_OK is returned. Otherwise an error code is returned. The
505** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
506** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000507**
drh4f26d6c2004-05-26 23:25:30 +0000508** If the database file does not exist, then a new database is created.
509** The encoding for the database is UTF-8 if sqlite3_open() is called and
510** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000511**
512** Whether or not an error occurs when it is opened, resources associated
513** with the sqlite3* handle should be released by passing it to
514** sqlite3_close() when it is no longer required.
515*/
516int sqlite3_open(
517 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000518 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000519);
danielk197765904932004-05-26 06:18:37 +0000520int sqlite3_open16(
521 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000522 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000523);
danielk1977295ba552004-05-19 10:34:51 +0000524
danielk197765904932004-05-26 06:18:37 +0000525/*
526** Return the error code for the most recent sqlite3_* API call associated
527** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
528** API call was successful.
529**
530** Calls to many sqlite3_* functions set the error code and string returned
531** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
532** (overwriting the previous values). Note that calls to sqlite3_errcode(),
533** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
534** results of future invocations.
535**
536** Assuming no other intervening sqlite3_* API calls are made, the error
537** code returned by this function is associated with the same error as
538** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
539*/
540int sqlite3_errcode(sqlite3 *db);
541
542/*
543** Return a pointer to a UTF-8 encoded string describing in english the
544** error condition for the most recent sqlite3_* API call. The returned
545** string is always terminated by an 0x00 byte.
546**
547** The string "not an error" is returned when the most recent API call was
548** successful.
549*/
550const char *sqlite3_errmsg(sqlite3*);
551
552/*
553** Return a pointer to a UTF-16 native byte order encoded string describing
554** in english the error condition for the most recent sqlite3_* API call.
555** The returned string is always terminated by a pair of 0x00 bytes.
556**
557** The string "not an error" is returned when the most recent API call was
558** successful.
559*/
560const void *sqlite3_errmsg16(sqlite3*);
561
562/*
563** An instance of the following opaque structure is used to represent
564** a compiled SQL statment.
565*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000566typedef struct sqlite3_stmt sqlite3_stmt;
567
danielk1977e3209e42004-05-20 01:40:18 +0000568/*
danielk197765904932004-05-26 06:18:37 +0000569** To execute an SQL query, it must first be compiled into a byte-code
570** program using one of the following routines. The only difference between
571** them is that the second argument, specifying the SQL statement to
572** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
573** function and UTF-16 for sqlite3_prepare16().
574**
575** The first parameter "db" is an SQLite database handle. The second
576** parameter "zSql" is the statement to be compiled, encoded as either
577** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
578** than zero, then zSql is read up to the first nul terminator. If
579** "nBytes" is not less than zero, then it is the length of the string zSql
580** in bytes (not characters).
581**
582** *pzTail is made to point to the first byte past the end of the first
583** SQL statement in zSql. This routine only compiles the first statement
584** in zSql, so *pzTail is left pointing to what remains uncompiled.
585**
586** *ppStmt is left pointing to a compiled SQL statement that can be
587** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
588** set to NULL. If the input text contained no SQL (if the input is and
589** empty string or a comment) then *ppStmt is set to NULL.
590**
591** On success, SQLITE_OK is returned. Otherwise an error code is returned.
592*/
593int sqlite3_prepare(
594 sqlite3 *db, /* Database handle */
595 const char *zSql, /* SQL statement, UTF-8 encoded */
596 int nBytes, /* Length of zSql in bytes. */
597 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
598 const char **pzTail /* OUT: Pointer to unused portion of zSql */
599);
600int sqlite3_prepare16(
601 sqlite3 *db, /* Database handle */
602 const void *zSql, /* SQL statement, UTF-16 encoded */
603 int nBytes, /* Length of zSql in bytes. */
604 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
605 const void **pzTail /* OUT: Pointer to unused portion of zSql */
606);
607
608/*
drhf4479502004-05-27 03:12:53 +0000609** Pointers to the following two opaque structures are used to communicate
610** with the implementations of user-defined functions.
611*/
612typedef struct sqlite3_context sqlite3_context;
613typedef struct Mem sqlite3_value;
614
615/*
drh4f26d6c2004-05-26 23:25:30 +0000616** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
617** one or more literals can be replace by a wildcard "?" or ":N:" where
618** N is an integer. These value of these wildcard literals can be set
619** using the routines listed below.
620**
621** In every case, the first parameter is a pointer to the sqlite3_stmt
622** structure returned from sqlite3_prepare(). The second parameter is the
623** index of the wildcard. The first "?" has an index of 1. ":N:" wildcards
624** use the index N.
625**
626** When the eCopy parameter is true, a copy of the value is made into
627** memory obtained and managed by SQLite. When eCopy is false, SQLite
628** assumes that the value is a constant and just stores a pointer to the
629** value without making a copy.
630**
631** The sqlite3_bind_* routine must be called before sqlite3_step() after
632** an sqlite3_prepare() or sqlite3_reset(). Unbound wildcards are interpreted
633** as NULL.
634*/
danielk1977d8123362004-06-12 09:25:12 +0000635int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000636int sqlite3_bind_double(sqlite3_stmt*, int, double);
637int sqlite3_bind_int(sqlite3_stmt*, int, int);
drhefad9992004-06-22 12:13:55 +0000638int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64);
drhf4479502004-05-27 03:12:53 +0000639int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000640int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
641int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000642int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000643
644/*
danielk197765904932004-05-26 06:18:37 +0000645** Return the number of columns in the result set returned by the compiled
646** SQL statement. This routine returns 0 if pStmt is an SQL statement
647** that does not return data (for example an UPDATE).
648*/
649int sqlite3_column_count(sqlite3_stmt *pStmt);
650
651/*
652** The first parameter is a compiled SQL statement. This function returns
653** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000654** second function parameter. The string returned is UTF-8 for
655** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000656*/
657const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000658const void *sqlite3_column_name16(sqlite3_stmt*,int);
659
660/*
661** The first parameter is a compiled SQL statement. If this statement
662** is a SELECT statement, the Nth column of the returned result set
663** of the SELECT is a table column then the declared type of the table
664** column is returned. If the Nth column of the result set is not at table
665** column, then a NULL pointer is returned. The returned string is always
666** UTF-8 encoded. For example, in the database schema:
667**
668** CREATE TABLE t1(c1 VARIANT);
669**
670** And the following statement compiled:
671**
672** SELECT c1 + 1, 0 FROM t1;
673**
674** Then this routine would return the string "VARIANT" for the second
675** result column (i==1), and a NULL pointer for the first result column
676** (i==0).
677*/
678const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
679
680/*
681** The first parameter is a compiled SQL statement. If this statement
682** is a SELECT statement, the Nth column of the returned result set
683** of the SELECT is a table column then the declared type of the table
684** column is returned. If the Nth column of the result set is not at table
685** column, then a NULL pointer is returned. The returned string is always
686** UTF-16 encoded. For example, in the database schema:
687**
drh4f26d6c2004-05-26 23:25:30 +0000688** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000689**
690** And the following statement compiled:
691**
692** SELECT c1 + 1, 0 FROM t1;
693**
drh4f26d6c2004-05-26 23:25:30 +0000694** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000695** result column (i==1), and a NULL pointer for the first result column
696** (i==0).
697*/
698const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
699
danielk1977106bb232004-05-21 10:08:53 +0000700/*
701** After an SQL query has been compiled with a call to either
702** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
703** called one or more times to execute the statement.
704**
705** The return value will be either SQLITE_BUSY, SQLITE_DONE,
706** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
707**
708** SQLITE_BUSY means that the database engine attempted to open
709** a locked database and there is no busy callback registered.
710** Call sqlite3_step() again to retry the open.
711**
712** SQLITE_DONE means that the statement has finished executing
713** successfully. sqlite3_step() should not be called again on this virtual
714** machine.
715**
716** If the SQL statement being executed returns any data, then
717** SQLITE_ROW is returned each time a new row of data is ready
718** for processing by the caller. The values may be accessed using
719** the sqlite3_column_*() functions described below. sqlite3_step()
720** is called again to retrieve the next row of data.
721**
722** SQLITE_ERROR means that a run-time error (such as a constraint
723** violation) has occurred. sqlite3_step() should not be called again on
724** the VM. More information may be found by calling sqlite3_errmsg().
725**
726** SQLITE_MISUSE means that the this routine was called inappropriately.
727** Perhaps it was called on a virtual machine that had already been
728** finalized or on one that had previously returned SQLITE_ERROR or
729** SQLITE_DONE. Or it could be the case the the same database connection
730** is being used simulataneously by two or more threads.
731*/
danielk197717240fd2004-05-26 00:07:25 +0000732int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000733
danielk1977106bb232004-05-21 10:08:53 +0000734/*
735** Return the number of values in the current row of the result set.
736**
737** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
738** will return the same value as the sqlite3_column_count() function.
739** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
740** error code, or before sqlite3_step() has been called on a
741** compiled SQL statement, this routine returns zero.
742*/
danielk197793d46752004-05-23 13:30:58 +0000743int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000744
drh4f26d6c2004-05-26 23:25:30 +0000745/*
746** Values are stored in the database in one of the following fundamental
747** types.
748*/
drh9c054832004-05-31 18:51:57 +0000749#define SQLITE_INTEGER 1
750#define SQLITE_FLOAT 2
751#define SQLITE_TEXT 3
752#define SQLITE_BLOB 4
753#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000754
danielk1977106bb232004-05-21 10:08:53 +0000755/*
drh4f26d6c2004-05-26 23:25:30 +0000756** The next group of routines returns information about the information
757** in a single column of the current result row of a query. In every
758** case the first parameter is a pointer to the SQL statement that is being
759** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
760** the second argument is the index of the column for which information
761** should be returned. iCol is zero-indexed. The left-most column as an
762** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000763**
drh4f26d6c2004-05-26 23:25:30 +0000764** If the SQL statement is not currently point to a valid row, or if the
765** the colulmn index is out of range, the result is undefined.
766**
767** These routines attempt to convert the value where appropriate. For
768** example, if the internal representation is FLOAT and a text result
769** is requested, sprintf() is used internally to do the conversion
770** automatically. The following table details the conversions that
771** are applied:
772**
773** Internal Type Requested Type Conversion
774** ------------- -------------- --------------------------
775** NULL INTEGER Result is 0
776** NULL FLOAT Result is 0.0
777** NULL TEXT Result is an empty string
778** NULL BLOB Result is a zero-length BLOB
779** INTEGER FLOAT Convert from integer to float
780** INTEGER TEXT ASCII rendering of the integer
781** INTEGER BLOB Same as for INTEGER->TEXT
782** FLOAT INTEGER Convert from float to integer
783** FLOAT TEXT ASCII rendering of the float
784** FLOAT BLOB Same as FLOAT->TEXT
785** TEXT INTEGER Use atoi()
786** TEXT FLOAT Use atof()
787** TEXT BLOB No change
788** BLOB INTEGER Convert to TEXT then use atoi()
789** BLOB FLOAT Convert to TEXT then use atof()
790** BLOB TEXT Add a \000 terminator if needed
791**
792** The following access routines are provided:
793**
794** _type() Return the datatype of the result. This is one of
795** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
796** or SQLITE_NULL.
797** _blob() Return the value of a BLOB.
798** _bytes() Return the number of bytes in a BLOB value or the number
799** of bytes in a TEXT value represented as UTF-8. The \000
800** terminator is included in the byte count for TEXT values.
801** _bytes16() Return the number of bytes in a BLOB value or the number
802** of bytes in a TEXT value represented as UTF-16. The \u0000
803** terminator is included in the byte count for TEXT values.
804** _double() Return a FLOAT value.
805** _int() Return an INTEGER value in the host computer's native
806** integer representation. This might be either a 32- or 64-bit
807** integer depending on the host.
808** _int64() Return an INTEGER value as a 64-bit signed integer.
809** _text() Return the value as UTF-8 text.
810** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +0000811*/
drhf4479502004-05-27 03:12:53 +0000812const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
813int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
814int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
815double sqlite3_column_double(sqlite3_stmt*, int iCol);
816int sqlite3_column_int(sqlite3_stmt*, int iCol);
drhefad9992004-06-22 12:13:55 +0000817sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +0000818const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
819const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +0000820int sqlite3_column_type(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +0000821
danielk197765904932004-05-26 06:18:37 +0000822/*
823** The sqlite3_finalize() function is called to delete a compiled
824** SQL statement obtained by a previous call to sqlite3_prepare()
825** or sqlite3_prepare16(). If the statement was executed successfully, or
826** not executed at all, then SQLITE_OK is returned. If execution of the
827** statement failed then an error code is returned.
828**
829** This routine can be called at any point during the execution of the
830** virtual machine. If the virtual machine has not completed execution
831** when this routine is called, that is like encountering an error or
832** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
833** rolled back and transactions cancelled, depending on the circumstances,
834** and the result code returned will be SQLITE_ABORT.
835*/
836int sqlite3_finalize(sqlite3_stmt *pStmt);
837
838/*
839** The sqlite3_reset() function is called to reset a compiled SQL
840** statement obtained by a previous call to sqlite3_prepare() or
841** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
842** Any SQL statement variables that had values bound to them using
843** the sqlite3_bind_*() API retain their values.
844*/
845int sqlite3_reset(sqlite3_stmt *pStmt);
846
847/*
danielk197765904932004-05-26 06:18:37 +0000848** The following two functions are used to add user functions or aggregates
849** implemented in C to the SQL langauge interpreted by SQLite. The
850** difference only between the two is that the second parameter, the
851** name of the (scalar) function or aggregate, is encoded in UTF-8 for
852** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
853**
854** The first argument is the database handle that the new function or
855** aggregate is to be added to. If a single program uses more than one
856** database handle internally, then user functions or aggregates must
857** be added individually to each database handle with which they will be
858** used.
859**
860** The third parameter is the number of arguments that the function or
861** aggregate takes. If this parameter is negative, then the function or
862** aggregate may take any number of arguments.
863**
danielk1977d8123362004-06-12 09:25:12 +0000864** The fourth parameter is one of SQLITE_UTF* values defined below,
865** indicating the encoding that the function is most likely to handle
866** values in. This does not change the behaviour of the programming
867** interface. However, if two versions of the same function are registered
868** with different encoding values, SQLite invokes the version likely to
869** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +0000870**
danielk197765904932004-05-26 06:18:37 +0000871** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
872** pointers to user implemented C functions that implement the user
873** function or aggregate. A scalar function requires an implementation of
874** the xFunc callback only, NULL pointers should be passed as the xStep
875** and xFinal parameters. An aggregate function requires an implementation
876** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
877** existing user function or aggregate, pass NULL for all three function
878** callback. Specifying an inconstent set of callback values, such as an
879** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
880** returned.
881*/
882int sqlite3_create_function(
883 sqlite3 *,
884 const char *zFunctionName,
885 int nArg,
886 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000887 void*,
888 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
889 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
890 void (*xFinal)(sqlite3_context*)
891);
892int sqlite3_create_function16(
893 sqlite3*,
894 const void *zFunctionName,
895 int nArg,
896 int eTextRep,
danielk197765904932004-05-26 06:18:37 +0000897 void*,
898 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
899 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
900 void (*xFinal)(sqlite3_context*)
901);
902
903/*
danielk197765904932004-05-26 06:18:37 +0000904** The next routine returns the number of calls to xStep for a particular
905** aggregate function instance. The current call to xStep counts so this
906** routine always returns at least 1.
907*/
908int sqlite3_aggregate_count(sqlite3_context*);
909
danielk19770ffba6b2004-05-24 09:10:10 +0000910/*
drh4f26d6c2004-05-26 23:25:30 +0000911** The next group of routines returns information about parameters to
912** a user-defined function. Function implementations use these routines
913** to access their parameters. These routines are the same as the
914** sqlite3_column_* routines except that these routines take a single
915** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
916** column number.
danielk19770ffba6b2004-05-24 09:10:10 +0000917*/
drhf4479502004-05-27 03:12:53 +0000918const void *sqlite3_value_blob(sqlite3_value*);
919int sqlite3_value_bytes(sqlite3_value*);
920int sqlite3_value_bytes16(sqlite3_value*);
921double sqlite3_value_double(sqlite3_value*);
922int sqlite3_value_int(sqlite3_value*);
drhefad9992004-06-22 12:13:55 +0000923sqlite_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +0000924const unsigned char *sqlite3_value_text(sqlite3_value*);
925const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +0000926const void *sqlite3_value_text16le(sqlite3_value*);
927const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +0000928int sqlite3_value_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +0000929
930/*
danielk19770ae8b832004-05-25 12:05:56 +0000931** Aggregate functions use the following routine to allocate
932** a structure for storing their state. The first time this routine
933** is called for a particular aggregate, a new structure of size nBytes
934** is allocated, zeroed, and returned. On subsequent calls (for the
935** same aggregate instance) the same buffer is returned. The implementation
936** of the aggregate can use the returned buffer to accumulate data.
937**
938** The buffer allocated is freed automatically by SQLite.
939*/
drh4f26d6c2004-05-26 23:25:30 +0000940void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +0000941
942/*
943** The pUserData parameter to the sqlite3_create_function() and
944** sqlite3_create_aggregate() routines used to register user functions
945** is available to the implementation of the function using this
946** call.
947*/
948void *sqlite3_user_data(sqlite3_context*);
949
950/*
danielk1977682f68b2004-06-05 10:22:17 +0000951** The following two functions may be used by scalar user functions to
952** associate meta-data with argument values. If the same value is passed to
953** multiple invocations of the user-function during query execution, under
954** some circumstances the associated meta-data may be preserved. This may
955** be used, for example, to add a regular-expression matching scalar
956** function. The compiled version of the regular expression is stored as
957** meta-data associated with the SQL value passed as the regular expression
958** pattern.
959**
960** Calling sqlite3_get_auxdata() returns a pointer to the meta data
961** associated with the Nth argument value to the current user function
962** call, where N is the second parameter. If no meta-data has been set for
963** that value, then a NULL pointer is returned.
964**
965** The sqlite3_set_auxdata() is used to associate meta data with a user
966** function argument. The third parameter is a pointer to the meta data
967** to be associated with the Nth user function argument value. The fourth
968** parameter specifies a 'delete function' that will be called on the meta
969** data pointer to release it when it is no longer required. If the delete
970** function pointer is NULL, it is not invoked.
971**
972** In practice, meta-data is preserved between function calls for
973** expressions that are constant at compile time. This includes literal
974** values and SQL variables.
975*/
976void *sqlite3_get_auxdata(sqlite3_context*, int);
977void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
978
drha2854222004-06-17 19:04:17 +0000979
980/*
981** These are special value for the destructor that is passed in as the
982** final argument to routines like sqlite3_result_blob(). If the destructor
983** argument is SQLITE_STATIC, it means that the content pointer is constant
984** and will never change. It does not need to be destroyed. The
985** SQLITE_TRANSIENT value means that the content will likely change in
986** the near future and that SQLite should make its own private copy of
987** the content before returning.
988*/
danielk1977d8123362004-06-12 09:25:12 +0000989#define SQLITE_STATIC ((void(*)(void *))0)
990#define SQLITE_TRANSIENT ((void(*)(void *))-1)
991
danielk1977682f68b2004-06-05 10:22:17 +0000992/*
drh4f26d6c2004-05-26 23:25:30 +0000993** User-defined functions invoke the following routines in order to
994** set their return value.
danielk19777e18c252004-05-25 11:47:24 +0000995*/
danielk1977d8123362004-06-12 09:25:12 +0000996void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +0000997void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +0000998void sqlite3_result_error(sqlite3_context*, const char*, int);
999void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +00001000void sqlite3_result_int(sqlite3_context*, int);
drhefad9992004-06-22 12:13:55 +00001001void sqlite3_result_int64(sqlite3_context*, sqlite_int64);
drh4f26d6c2004-05-26 23:25:30 +00001002void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +00001003void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
1004void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
1005void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
1006void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001007void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +00001008
drh52619df2004-06-11 17:48:02 +00001009/*
1010** These are the allowed values for the eTextRep argument to
1011** sqlite3_create_collation and sqlite3_create_function.
1012*/
danielk1977466be562004-06-10 02:16:01 +00001013#define SQLITE_UTF8 1
danielk1977dc8453f2004-06-12 00:42:34 +00001014#define SQLITE_UTF16LE 2
1015#define SQLITE_UTF16BE 3
1016#define SQLITE_UTF16 4 /* Use native byte order */
drh52619df2004-06-11 17:48:02 +00001017#define SQLITE_ANY 5 /* sqlite3_create_function only */
danielk1977466be562004-06-10 02:16:01 +00001018
danielk19777cedc8d2004-06-10 10:50:08 +00001019/*
1020** These two functions are used to add new collation sequences to the
1021** sqlite3 handle specified as the first argument.
1022**
1023** The name of the new collation sequence is specified as a UTF-8 string
1024** for sqlite3_create_collation() and a UTF-16 string for
1025** sqlite3_create_collation16(). In both cases the name is passed as the
1026** second function argument.
1027**
1028** The third argument must be one of the constants SQLITE_UTF8,
1029** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1030** routine expects to be passed pointers to strings encoded using UTF-8,
1031** UTF-16 little-endian or UTF-16 big-endian respectively.
1032**
1033** A pointer to the user supplied routine must be passed as the fifth
1034** argument. If it is NULL, this is the same as deleting the collation
1035** sequence (so that SQLite cannot call it anymore). Each time the user
1036** supplied function is invoked, it is passed a copy of the void* passed as
1037** the fourth argument to sqlite3_create_collation() or
1038** sqlite3_create_collation16() as its first parameter.
1039**
1040** The remaining arguments to the user-supplied routine are two strings,
1041** each represented by a [length, data] pair and encoded in the encoding
1042** that was passed as the third argument when the collation sequence was
1043** registered. The user routine should return negative, zero or positive if
1044** the first string is less than, equal to, or greater than the second
1045** string. i.e. (STRING1 - STRING2).
1046*/
danielk19770202b292004-06-09 09:55:16 +00001047int sqlite3_create_collation(
1048 sqlite3*,
1049 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001050 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001051 void*,
1052 int(*xCompare)(void*,int,const void*,int,const void*)
1053);
1054int sqlite3_create_collation16(
1055 sqlite3*,
1056 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001057 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001058 void*,
1059 int(*xCompare)(void*,int,const void*,int,const void*)
1060);
1061
danielk19777cedc8d2004-06-10 10:50:08 +00001062/*
1063** To avoid having to register all collation sequences before a database
1064** can be used, a single callback function may be registered with the
1065** database handle to be called whenever an undefined collation sequence is
1066** required.
1067**
1068** If the function is registered using the sqlite3_collation_needed() API,
1069** then it is passed the names of undefined collation sequences as strings
1070** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1071** are passed as UTF-16 in machine native byte order. A call to either
1072** function replaces any existing callback.
1073**
1074** When the user-function is invoked, the first argument passed is a copy
1075** of the second argument to sqlite3_collation_needed() or
1076** sqlite3_collation_needed16(). The second argument is the database
1077** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1078** SQLITE_UTF16LE, indicating the most desirable form of the collation
1079** sequence function required. The fourth parameter is the name of the
1080** required collation sequence.
1081**
1082** The collation sequence is returned to SQLite by a collation-needed
1083** callback using the sqlite3_create_collation() or
1084** sqlite3_create_collation16() APIs, described above.
1085*/
1086int sqlite3_collation_needed(
1087 sqlite3*,
1088 void*,
1089 void(*)(void*,sqlite3*,int eTextRep,const char*)
1090);
1091int sqlite3_collation_needed16(
1092 sqlite3*,
1093 void*,
1094 void(*)(void*,sqlite3*,int eTextRep,const void*)
1095);
1096
danielk19770202b292004-06-09 09:55:16 +00001097
drh382c0242001-10-06 16:33:02 +00001098#ifdef __cplusplus
1099} /* End of the 'extern "C"' block */
1100#endif
danielk19774adee202004-05-08 08:23:19 +00001101#endif