blob: 568141f09ac5d052959bb3f176406384b629d033 [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**
drha09883f2007-01-10 12:57:29 +000015** @(#) $Id: sqlite.h.in,v 1.197 2007/01/10 12:57:29 drh Exp $
drh75897232000-05-29 14:26:00 +000016*/
drh12057d52004-09-06 17:34:12 +000017#ifndef _SQLITE3_H_
18#define _SQLITE3_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*/
drh1e284f42004-10-06 15:52:01 +000031#ifdef SQLITE_VERSION
32# undef SQLITE_VERSION
drh1e284f42004-10-06 15:52:01 +000033#endif
danielk197799ba19e2005-02-05 07:33:34 +000034#define SQLITE_VERSION "--VERS--"
35
36/*
37** The format of the version string is "X.Y.Z<trailing string>", where
38** X is the major version number, Y is the minor version number and Z
39** is the release number. The trailing string is often "alpha" or "beta".
40** For example "3.1.1beta".
41**
42** The SQLITE_VERSION_NUMBER is an integer with the value
43** (X*100000 + Y*1000 + Z). For example, for version "3.1.1beta",
44** SQLITE_VERSION_NUMBER is set to 3001001. To detect if they are using
45** version 3.1.1 or greater at compile time, programs may use the test
46** (SQLITE_VERSION_NUMBER>=3001001).
47*/
48#ifdef SQLITE_VERSION_NUMBER
49# undef SQLITE_VERSION_NUMBER
50#endif
51#define SQLITE_VERSION_NUMBER --VERSION-NUMBER--
drhb86ccfb2003-01-28 23:13:10 +000052
53/*
drhb217a572000-08-22 13:40:18 +000054** The version string is also compiled into the library so that a program
55** can check to make sure that the lib*.a file and the *.h file are from
drh6f3a3ef2004-08-28 18:21:21 +000056** the same version. The sqlite3_libversion() function returns a pointer
57** to the sqlite3_version variable - useful in DLLs which cannot access
58** global variables.
drhb217a572000-08-22 13:40:18 +000059*/
danielk19776f8a5032004-05-10 10:34:51 +000060extern const char sqlite3_version[];
drha3f70cb2004-09-30 14:24:50 +000061const char *sqlite3_libversion(void);
drh303aaa72000-08-17 10:22:34 +000062
63/*
danielk197799ba19e2005-02-05 07:33:34 +000064** Return the value of the SQLITE_VERSION_NUMBER macro when the
65** library was compiled.
66*/
67int sqlite3_libversion_number(void);
68
69/*
drh75897232000-05-29 14:26:00 +000070** Each open sqlite database is represented by an instance of the
71** following opaque structure.
72*/
drh9bb575f2004-09-06 17:24:11 +000073typedef struct sqlite3 sqlite3;
danielk197765904932004-05-26 06:18:37 +000074
drh75897232000-05-29 14:26:00 +000075
76/*
drhefad9992004-06-22 12:13:55 +000077** Some compilers do not support the "long long" datatype. So we have
78** to do a typedef that for 64-bit integers that depends on what compiler
79** is being used.
80*/
drh27436af2006-03-28 23:57:17 +000081#ifdef SQLITE_INT64_TYPE
drh9b8f4472006-04-04 01:54:55 +000082 typedef SQLITE_INT64_TYPE sqlite_int64;
drh27436af2006-03-28 23:57:17 +000083 typedef unsigned SQLITE_INT64_TYPE sqlite_uint64;
84#elif defined(_MSC_VER) || defined(__BORLANDC__)
drhefad9992004-06-22 12:13:55 +000085 typedef __int64 sqlite_int64;
drh1211de32004-07-26 12:24:22 +000086 typedef unsigned __int64 sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000087#else
88 typedef long long int sqlite_int64;
drh1211de32004-07-26 12:24:22 +000089 typedef unsigned long long int sqlite_uint64;
drhefad9992004-06-22 12:13:55 +000090#endif
91
drhb37df7b2005-10-13 02:09:49 +000092/*
93** If compiling for a processor that lacks floating point support,
94** substitute integer for floating-point
95*/
96#ifdef SQLITE_OMIT_FLOATING_POINT
97# define double sqlite_int64
98#endif
drhefad9992004-06-22 12:13:55 +000099
100/*
drh75897232000-05-29 14:26:00 +0000101** A function to close the database.
102**
103** Call this function with a pointer to a structure that was previously
danielk19776f8a5032004-05-10 10:34:51 +0000104** returned from sqlite3_open() and the corresponding database will by closed.
danielk197796d81f92004-06-19 03:33:57 +0000105**
106** All SQL statements prepared using sqlite3_prepare() or
107** sqlite3_prepare16() must be deallocated using sqlite3_finalize() before
108** this routine is called. Otherwise, SQLITE_BUSY is returned and the
109** database connection remains open.
drh75897232000-05-29 14:26:00 +0000110*/
danielk1977f9d64d22004-06-19 08:18:07 +0000111int sqlite3_close(sqlite3 *);
drh75897232000-05-29 14:26:00 +0000112
113/*
114** The type for a callback function.
115*/
drh12057d52004-09-06 17:34:12 +0000116typedef int (*sqlite3_callback)(void*,int,char**, char**);
drh75897232000-05-29 14:26:00 +0000117
118/*
119** A function to executes one or more statements of SQL.
120**
121** If one or more of the SQL statements are queries, then
122** the callback function specified by the 3rd parameter is
123** invoked once for each row of the query result. This callback
124** should normally return 0. If the callback returns a non-zero
125** value then the query is aborted, all subsequent SQL statements
danielk19776f8a5032004-05-10 10:34:51 +0000126** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +0000127**
drha09883f2007-01-10 12:57:29 +0000128** The 1st parameter is an arbitrary pointer that is passed
drh75897232000-05-29 14:26:00 +0000129** to the callback function as its first parameter.
130**
131** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +0000132** columns in the query result. The 3rd parameter to the callback
133** is an array of strings holding the values for each column.
134** The 4th parameter to the callback is an array of strings holding
135** the names of each column.
drh75897232000-05-29 14:26:00 +0000136**
137** The callback function may be NULL, even for queries. A NULL
138** callback is not an error. It just means that no callback
139** will be invoked.
140**
141** If an error occurs while parsing or evaluating the SQL (but
142** not while executing the callback) then an appropriate error
143** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +0000144** *errmsg is made to point to that message. The calling function
145** is responsible for freeing the memory that holds the error
drh3f4fedb2004-05-31 19:34:33 +0000146** message. Use sqlite3_free() for this. If errmsg==NULL,
drhb86ccfb2003-01-28 23:13:10 +0000147** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +0000148**
149** The return value is is SQLITE_OK if there are no errors and
150** some other return code if there is an error. The particular
151** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +0000152**
153** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000154** locked or busy, then this function returns SQLITE_BUSY. (This
danielk19776f8a5032004-05-10 10:34:51 +0000155** behavior can be modified somewhat using the sqlite3_busy_handler()
156** and sqlite3_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000157*/
danielk19776f8a5032004-05-10 10:34:51 +0000158int sqlite3_exec(
drh12057d52004-09-06 17:34:12 +0000159 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000160 const char *sql, /* SQL to be executed */
drh12057d52004-09-06 17:34:12 +0000161 sqlite3_callback, /* Callback function */
drh75897232000-05-29 14:26:00 +0000162 void *, /* 1st argument to callback function */
163 char **errmsg /* Error msg written here */
164);
165
drh58b95762000-06-02 01:17:37 +0000166/*
danielk19776f8a5032004-05-10 10:34:51 +0000167** Return values for sqlite3_exec() and sqlite3_step()
drh58b95762000-06-02 01:17:37 +0000168*/
drh717e6402001-09-27 03:22:32 +0000169#define SQLITE_OK 0 /* Successful result */
drh15b9a152006-01-31 20:49:13 +0000170/* beginning-of-error-codes */
drh717e6402001-09-27 03:22:32 +0000171#define SQLITE_ERROR 1 /* SQL error or missing database */
drh2db0bbc2005-08-11 02:10:18 +0000172#define SQLITE_INTERNAL 2 /* NOT USED. Internal logic error in SQLite */
drh717e6402001-09-27 03:22:32 +0000173#define SQLITE_PERM 3 /* Access permission denied */
174#define SQLITE_ABORT 4 /* Callback routine requested an abort */
175#define SQLITE_BUSY 5 /* The database file is locked */
176#define SQLITE_LOCKED 6 /* A table in the database is locked */
177#define SQLITE_NOMEM 7 /* A malloc() failed */
178#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
drh24cd67e2004-05-10 16:18:47 +0000179#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/
drh717e6402001-09-27 03:22:32 +0000180#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
181#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
drh2db0bbc2005-08-11 02:10:18 +0000182#define SQLITE_NOTFOUND 12 /* NOT USED. Table or record not found */
drh717e6402001-09-27 03:22:32 +0000183#define SQLITE_FULL 13 /* Insertion failed because database is full */
184#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
185#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
drh24cd67e2004-05-10 16:18:47 +0000186#define SQLITE_EMPTY 16 /* Database is empty */
drh717e6402001-09-27 03:22:32 +0000187#define SQLITE_SCHEMA 17 /* The database schema changed */
drh2db0bbc2005-08-11 02:10:18 +0000188#define SQLITE_TOOBIG 18 /* NOT USED. Too much data for one row */
drh717e6402001-09-27 03:22:32 +0000189#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000190#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000191#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000192#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000193#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000194#define SQLITE_FORMAT 24 /* Auxiliary database format error */
danielk19776f8a5032004-05-10 10:34:51 +0000195#define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */
drhc602f9a2004-02-12 19:01:04 +0000196#define SQLITE_NOTADB 26 /* File opened that is not a database file */
danielk19776f8a5032004-05-10 10:34:51 +0000197#define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
198#define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
drh15b9a152006-01-31 20:49:13 +0000199/* end-of-error-codes */
drh717e6402001-09-27 03:22:32 +0000200
drhaf9ff332002-01-16 21:00:27 +0000201/*
drh4ac285a2006-09-15 07:28:50 +0000202** Using the sqlite3_extended_result_codes() API, you can cause
203** SQLite to return result codes with additional information in
204** their upper bits. The lower 8 bits will be the same as the
205** primary result codes above. But the upper bits might contain
206** more specific error information.
207**
208** To extract the primary result code from an extended result code,
209** simply mask off the lower 8 bits.
210**
211** primary = extended & 0xff;
212**
213** New result error codes may be added from time to time. Software
214** that uses the extended result codes should plan accordingly and be
215** sure to always handle new unknown codes gracefully.
216**
217** The SQLITE_OK result code will never be extended. It will always
218** be exactly zero.
219**
220** The extended result codes always have the primary result code
221** as a prefix. Primary result codes only contain a single "_"
222** character. Extended result codes contain two or more "_" characters.
223*/
224#define SQLITE_IOERR_READ (SQLITE_IOERR | (1<<8))
225#define SQLITE_IOERR_SHORT_READ (SQLITE_IOERR | (2<<8))
226#define SQLITE_IOERR_WRITE (SQLITE_IOERR | (3<<8))
227#define SQLITE_IOERR_FSYNC (SQLITE_IOERR | (4<<8))
228#define SQLITE_IOERR_DIR_FSYNC (SQLITE_IOERR | (5<<8))
229#define SQLITE_IOERR_TRUNCATE (SQLITE_IOERR | (6<<8))
230#define SQLITE_IOERR_FSTAT (SQLITE_IOERR | (7<<8))
231#define SQLITE_IOERR_UNLOCK (SQLITE_IOERR | (8<<8))
232#define SQLITE_IOERR_RDLOCK (SQLITE_IOERR | (9<<8))
233
234/*
235** Enable or disable the extended result codes.
236*/
237int sqlite3_extended_result_codes(sqlite3*, int onoff);
238
239/*
drhaf9ff332002-01-16 21:00:27 +0000240** Each entry in an SQLite table has a unique integer key. (The key is
241** the value of the INTEGER PRIMARY KEY column if there is such a column,
242** otherwise the key is generated at random. The unique key is always
243** available as the ROWID, OID, or _ROWID_ column.) The following routine
244** returns the integer key of the most recent insert in the database.
245**
246** This function is similar to the mysql_insert_id() function from MySQL.
247*/
drhefad9992004-06-22 12:13:55 +0000248sqlite_int64 sqlite3_last_insert_rowid(sqlite3*);
drhaf9ff332002-01-16 21:00:27 +0000249
drhc8d30ac2002-04-12 10:08:59 +0000250/*
251** This function returns the number of database rows that were changed
danielk19776f8a5032004-05-10 10:34:51 +0000252** (or inserted or deleted) by the most recent called sqlite3_exec().
drhc8d30ac2002-04-12 10:08:59 +0000253**
254** All changes are counted, even if they were later undone by a
255** ROLLBACK or ABORT. Except, changes associated with creating and
256** dropping tables are not counted.
257**
danielk19776f8a5032004-05-10 10:34:51 +0000258** If a callback invokes sqlite3_exec() recursively, then the changes
drhc8d30ac2002-04-12 10:08:59 +0000259** in the inner, recursive call are counted together with the changes
260** in the outer call.
261**
262** SQLite implements the command "DELETE FROM table" without a WHERE clause
263** by dropping and recreating the table. (This is much faster than going
264** through and deleting individual elements form the table.) Because of
265** this optimization, the change count for "DELETE FROM table" will be
266** zero regardless of the number of elements that were originally in the
267** table. To get an accurate count of the number of rows deleted, use
268** "DELETE FROM table WHERE 1" instead.
269*/
danielk1977f9d64d22004-06-19 08:18:07 +0000270int sqlite3_changes(sqlite3*);
drhc8d30ac2002-04-12 10:08:59 +0000271
rdcf146a772004-02-25 22:51:06 +0000272/*
danielk1977b28af712004-06-21 06:50:26 +0000273** This function returns the number of database rows that have been
274** modified by INSERT, UPDATE or DELETE statements since the database handle
275** was opened. This includes UPDATE, INSERT and DELETE statements executed
276** as part of trigger programs. All changes are counted as soon as the
277** statement that makes them is completed (when the statement handle is
278** passed to sqlite3_reset() or sqlite_finalise()).
rdcf146a772004-02-25 22:51:06 +0000279**
280** SQLite implements the command "DELETE FROM table" without a WHERE clause
281** by dropping and recreating the table. (This is much faster than going
282** through and deleting individual elements form the table.) Because of
283** this optimization, the change count for "DELETE FROM table" will be
284** zero regardless of the number of elements that were originally in the
285** table. To get an accurate count of the number of rows deleted, use
286** "DELETE FROM table WHERE 1" instead.
rdcf146a772004-02-25 22:51:06 +0000287*/
danielk1977b28af712004-06-21 06:50:26 +0000288int sqlite3_total_changes(sqlite3*);
289
drh4c504392000-10-16 22:06:40 +0000290/* This function causes any pending database operation to abort and
291** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000292** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000293** or Ctrl-C where the user wants a long query operation to halt
294** immediately.
295*/
danielk1977f9d64d22004-06-19 08:18:07 +0000296void sqlite3_interrupt(sqlite3*);
drh4c504392000-10-16 22:06:40 +0000297
drheec553b2000-06-02 01:51:20 +0000298
danielk197761de0d12004-05-27 23:56:16 +0000299/* These functions return true if the given input string comprises
300** one or more complete SQL statements. For the sqlite3_complete() call,
301** the parameter must be a nul-terminated UTF-8 string. For
302** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string
303** is required.
drh75897232000-05-29 14:26:00 +0000304**
305** The algorithm is simple. If the last token other than spaces
306** and comments is a semicolon, then return true. otherwise return
307** false.
308*/
danielk19776f8a5032004-05-10 10:34:51 +0000309int sqlite3_complete(const char *sql);
danielk197761de0d12004-05-27 23:56:16 +0000310int sqlite3_complete16(const void *sql);
drh75897232000-05-29 14:26:00 +0000311
drh2dfbbca2000-07-28 14:32:48 +0000312/*
313** This routine identifies a callback function that is invoked
314** whenever an attempt is made to open a database table that is
315** currently locked by another process or thread. If the busy callback
danielk19776f8a5032004-05-10 10:34:51 +0000316** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if
drh2dfbbca2000-07-28 14:32:48 +0000317** it finds a locked table. If the busy callback is not NULL, then
drh86939b52007-01-10 12:54:51 +0000318** sqlite3_exec() invokes the callback with two arguments. The
319** first argument to the handler is a copy of the void* pointer which
320** is the third argument to this routine. The second argument to
321** the handler is the number of times that the busy handler has
322** been invoked for this locking event. If the
danielk19776f8a5032004-05-10 10:34:51 +0000323** busy callback returns 0, then sqlite3_exec() immediately returns
324** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec()
drh2dfbbca2000-07-28 14:32:48 +0000325** tries to open the table again and the cycle repeats.
326**
drh86939b52007-01-10 12:54:51 +0000327** The presence of a busy handler does not guarantee that
328** it will be invoked when there is lock contention.
329** If SQLite determines that invoking the busy handler could result in
330** a deadlock, it will return SQLITE_BUSY instead.
331** Consider a scenario where one process is holding a read lock that
332** it is trying to promote to a reserved lock and
333** a second process is holding a reserved lock that it is trying
334** to promote to an exclusive lock. The first process cannot proceed
335** because it is blocked by the second and the second process cannot
336** proceed because it is blocked by the first. If both processes
337** invoke the busy handlers, neither will make any progress. Therefore,
338** SQLite returns SQLITE_BUSY for the first process, hoping that this
339** will induce the first process to release its read lock and allow
340** the second process to proceed.
341**
drh2dfbbca2000-07-28 14:32:48 +0000342** The default busy callback is NULL.
343**
344** Sqlite is re-entrant, so the busy handler may start a new query.
345** (It is not clear why anyone would every want to do this, but it
346** is allowed, in theory.) But the busy handler may not close the
347** database. Closing the database from a busy handler will delete
348** data structures out from under the executing query and will
349** probably result in a coredump.
350*/
danielk1977f9d64d22004-06-19 08:18:07 +0000351int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*);
drh2dfbbca2000-07-28 14:32:48 +0000352
353/*
354** This routine sets a busy handler that sleeps for a while when a
355** table is locked. The handler will sleep multiple times until
356** at least "ms" milleseconds of sleeping have been done. After
357** "ms" milleseconds of sleeping, the handler returns 0 which
danielk19776f8a5032004-05-10 10:34:51 +0000358** causes sqlite3_exec() to return SQLITE_BUSY.
drh2dfbbca2000-07-28 14:32:48 +0000359**
360** Calling this routine with an argument less than or equal to zero
361** turns off all busy handlers.
362*/
danielk1977f9d64d22004-06-19 08:18:07 +0000363int sqlite3_busy_timeout(sqlite3*, int ms);
drh2dfbbca2000-07-28 14:32:48 +0000364
drhe3710332000-09-29 13:30:53 +0000365/*
danielk19776f8a5032004-05-10 10:34:51 +0000366** This next routine is really just a wrapper around sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000367** Instead of invoking a user-supplied callback for each row of the
368** result, this routine remembers each row of the result in memory
369** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000370** query has finished.
371**
372** As an example, suppose the query result where this table:
373**
374** Name | Age
375** -----------------------
376** Alice | 43
377** Bob | 28
378** Cindy | 21
379**
380** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000381** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000382**
383** azResult[0] = "Name";
384** azResult[1] = "Age";
385** azResult[2] = "Alice";
386** azResult[3] = "43";
387** azResult[4] = "Bob";
388** azResult[5] = "28";
389** azResult[6] = "Cindy";
390** azResult[7] = "21";
391**
392** Notice that there is an extra row of data containing the column
393** headers. But the *nrow return value is still 3. *ncolumn is
394** set to 2. In general, the number of values inserted into azResult
395** will be ((*nrow) + 1)*(*ncolumn).
396**
397** After the calling function has finished using the result, it should
danielk19776f8a5032004-05-10 10:34:51 +0000398** pass the result data pointer to sqlite3_free_table() in order to
drha18c5682000-10-08 22:20:57 +0000399** release the memory that was malloc-ed. Because of the way the
400** malloc() happens, the calling function must not try to call
danielk197799b214d2005-02-02 01:13:38 +0000401** free() directly. Only sqlite3_free_table() is able to release
drha18c5682000-10-08 22:20:57 +0000402** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000403**
danielk19776f8a5032004-05-10 10:34:51 +0000404** The return value of this routine is the same as from sqlite3_exec().
drhe3710332000-09-29 13:30:53 +0000405*/
danielk19776f8a5032004-05-10 10:34:51 +0000406int sqlite3_get_table(
danielk1977f9d64d22004-06-19 08:18:07 +0000407 sqlite3*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000408 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000409 char ***resultp, /* Result written to a char *[] that this points to */
410 int *nrow, /* Number of result rows written here */
411 int *ncolumn, /* Number of result columns written here */
412 char **errmsg /* Error msg written here */
413);
414
415/*
danielk19776f8a5032004-05-10 10:34:51 +0000416** Call this routine to free the memory that sqlite3_get_table() allocated.
drhe3710332000-09-29 13:30:53 +0000417*/
danielk19776f8a5032004-05-10 10:34:51 +0000418void sqlite3_free_table(char **result);
drhe3710332000-09-29 13:30:53 +0000419
drha18c5682000-10-08 22:20:57 +0000420/*
drh4f26d6c2004-05-26 23:25:30 +0000421** The following routines are variants of the "sprintf()" from the
422** standard C library. The resulting string is written into memory
423** obtained from malloc() so that there is never a possiblity of buffer
424** overflow. These routines also implement some additional formatting
425** options that are useful for constructing SQL statements.
426**
427** The strings returned by these routines should be freed by calling
428** sqlite3_free().
drha18c5682000-10-08 22:20:57 +0000429**
430** All of the usual printf formatting options apply. In addition, there
431** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000432** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000433** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000434** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000435** the string.
436**
437** For example, so some string variable contains text as follows:
438**
439** char *zText = "It's a happy day!";
440**
441** We can use this text in an SQL statement as follows:
442**
drh3224b322005-09-08 10:58:51 +0000443** char *z = sqlite3_mprintf("INSERT INTO TABLES('%q')", zText);
444** sqlite3_exec(db, z, callback1, 0, 0);
445** sqlite3_free(z);
drha18c5682000-10-08 22:20:57 +0000446**
447** Because the %q format string is used, the '\'' character in zText
448** is escaped and the SQL generated is as follows:
449**
450** INSERT INTO table1 VALUES('It''s a happy day!')
451**
452** This is correct. Had we used %s instead of %q, the generated SQL
453** would have looked like this:
454**
455** INSERT INTO table1 VALUES('It's a happy day!');
456**
457** This second example is an SQL syntax error. As a general rule you
458** should always use %q instead of %s when inserting text into a string
459** literal.
460*/
danielk19776f8a5032004-05-10 10:34:51 +0000461char *sqlite3_mprintf(const char*,...);
462char *sqlite3_vmprintf(const char*, va_list);
drhfeac5f82004-08-01 00:10:45 +0000463char *sqlite3_snprintf(int,char*,const char*, ...);
drh5191b7e2002-03-08 02:12:00 +0000464
drh28dd4792006-06-26 21:35:44 +0000465/*
466** SQLite uses its own memory allocator. On many installations, this
467** memory allocator is identical to the standard malloc()/realloc()/free()
468** and can be used interchangable. On others, the implementations are
469** different. For maximum portability, it is best not to mix calls
470** to the standard malloc/realloc/free with the sqlite versions.
471*/
472void *sqlite3_malloc(int);
473void *sqlite3_realloc(void*, int);
474void sqlite3_free(void*);
475
drh1211de32004-07-26 12:24:22 +0000476#ifndef SQLITE_OMIT_AUTHORIZATION
drh5191b7e2002-03-08 02:12:00 +0000477/*
drhed6c8672003-01-12 18:02:16 +0000478** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000479** callback is invoked (at compile-time, not at run-time) for each
480** attempt to access a column of a table in the database. The callback
481** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
482** SQL statement should be aborted with an error and SQLITE_IGNORE
483** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000484*/
danielk19776f8a5032004-05-10 10:34:51 +0000485int sqlite3_set_authorizer(
danielk1977f9d64d22004-06-19 08:18:07 +0000486 sqlite3*,
drhe22a3342003-04-22 20:30:37 +0000487 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000488 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000489);
drh1211de32004-07-26 12:24:22 +0000490#endif
drhed6c8672003-01-12 18:02:16 +0000491
492/*
493** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000494** be one of the values below. These values signify what kind of operation
495** is to be authorized. The 3rd and 4th parameters to the authorization
496** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000497** codes is used as the second parameter. The 5th parameter is the name
498** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000499** is the name of the inner-most trigger or view that is responsible for
500** the access attempt or NULL if this access attempt is directly from
501** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000502**
503** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000504*/
drh77ad4e42003-01-14 02:49:27 +0000505#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000506#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
507#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
508#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
509#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000510#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000511#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000512#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000513#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
514#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000515#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000516#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000517#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000518#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000519#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000520#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000521#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000522#define SQLITE_DROP_VIEW 17 /* View Name NULL */
523#define SQLITE_INSERT 18 /* Table Name NULL */
524#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
525#define SQLITE_READ 20 /* Table Name Column Name */
526#define SQLITE_SELECT 21 /* NULL NULL */
527#define SQLITE_TRANSACTION 22 /* NULL NULL */
528#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000529#define SQLITE_ATTACH 24 /* Filename NULL */
530#define SQLITE_DETACH 25 /* Database Name NULL */
danielk19771c8c23c2004-11-12 15:53:37 +0000531#define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */
danielk19771d54df82004-11-23 15:41:16 +0000532#define SQLITE_REINDEX 27 /* Index Name NULL */
drhe6e04962005-07-23 02:17:03 +0000533#define SQLITE_ANALYZE 28 /* Table Name NULL */
danielk1977f1a381e2006-06-16 08:01:02 +0000534#define SQLITE_CREATE_VTABLE 29 /* Table Name Module Name */
535#define SQLITE_DROP_VTABLE 30 /* Table Name Module Name */
drh5169bbc2006-08-24 14:59:45 +0000536#define SQLITE_FUNCTION 31 /* Function Name NULL */
drhed6c8672003-01-12 18:02:16 +0000537
538/*
539** The return value of the authorization function should be one of the
540** following constants:
541*/
542/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
543#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
544#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
545
546/*
drh19e2d372005-08-29 23:00:03 +0000547** Register a function for tracing SQL command evaluation. The function
548** registered by sqlite3_trace() is invoked at the first sqlite3_step()
549** for the evaluation of an SQL statement. The function registered by
550** sqlite3_profile() runs at the end of each SQL statement and includes
551** information on how long that statement ran.
552**
553** The sqlite3_profile() API is currently considered experimental and
554** is subject to change.
drh18de4822003-01-16 16:28:53 +0000555*/
danielk1977f9d64d22004-06-19 08:18:07 +0000556void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*);
drh19e2d372005-08-29 23:00:03 +0000557void *sqlite3_profile(sqlite3*,
558 void(*xProfile)(void*,const char*,sqlite_uint64), void*);
drh18de4822003-01-16 16:28:53 +0000559
danielk1977348bb5d2003-10-18 09:37:26 +0000560/*
561** This routine configures a callback function - the progress callback - that
danielk19776f8a5032004-05-10 10:34:51 +0000562** is invoked periodically during long running calls to sqlite3_exec(),
danielk19772097e942004-11-20 06:05:56 +0000563** sqlite3_step() and sqlite3_get_table(). An example use for this API is to
564** keep a GUI updated during a large query.
danielk1977348bb5d2003-10-18 09:37:26 +0000565**
566** The progress callback is invoked once for every N virtual machine opcodes,
567** where N is the second argument to this function. The progress callback
568** itself is identified by the third argument to this function. The fourth
569** argument to this function is a void pointer passed to the progress callback
570** function each time it is invoked.
571**
danielk19776f8a5032004-05-10 10:34:51 +0000572** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results
danielk1977348bb5d2003-10-18 09:37:26 +0000573** in less than N opcodes being executed, then the progress callback is not
574** invoked.
575**
danielk1977348bb5d2003-10-18 09:37:26 +0000576** To remove the progress callback altogether, pass NULL as the third
577** argument to this function.
578**
579** If the progress callback returns a result other than 0, then the current
580** query is immediately terminated and any database changes rolled back. If the
581** query was part of a larger transaction, then the transaction is not rolled
danielk19776f8a5032004-05-10 10:34:51 +0000582** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT.
drhaa940ea2004-01-15 02:44:03 +0000583**
584******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
danielk1977348bb5d2003-10-18 09:37:26 +0000585*/
danielk1977f9d64d22004-06-19 08:18:07 +0000586void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);
danielk1977348bb5d2003-10-18 09:37:26 +0000587
drhaa940ea2004-01-15 02:44:03 +0000588/*
589** Register a callback function to be invoked whenever a new transaction
590** is committed. The pArg argument is passed through to the callback.
591** callback. If the callback function returns non-zero, then the commit
592** is converted into a rollback.
593**
594** If another function was previously registered, its pArg value is returned.
595** Otherwise NULL is returned.
596**
597** Registering a NULL function disables the callback.
598**
599******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
600*/
danielk1977f9d64d22004-06-19 08:18:07 +0000601void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
drhaa940ea2004-01-15 02:44:03 +0000602
drh22fbcb82004-02-01 01:22:50 +0000603/*
drh4f26d6c2004-05-26 23:25:30 +0000604** Open the sqlite database file "filename". The "filename" is UTF-8
605** encoded for sqlite3_open() and UTF-16 encoded in the native byte order
606** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even
607** if an error occurs. If the database is opened (or created) successfully,
608** then SQLITE_OK is returned. Otherwise an error code is returned. The
609** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain
610** an English language description of the error.
drh22fbcb82004-02-01 01:22:50 +0000611**
drh4f26d6c2004-05-26 23:25:30 +0000612** If the database file does not exist, then a new database is created.
613** The encoding for the database is UTF-8 if sqlite3_open() is called and
614** UTF-16 if sqlite3_open16 is used.
danielk197765904932004-05-26 06:18:37 +0000615**
616** Whether or not an error occurs when it is opened, resources associated
617** with the sqlite3* handle should be released by passing it to
618** sqlite3_close() when it is no longer required.
619*/
620int sqlite3_open(
621 const char *filename, /* Database filename (UTF-8) */
danielk19774f057f92004-06-08 00:02:33 +0000622 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000623);
danielk197765904932004-05-26 06:18:37 +0000624int sqlite3_open16(
625 const void *filename, /* Database filename (UTF-16) */
danielk19774f057f92004-06-08 00:02:33 +0000626 sqlite3 **ppDb /* OUT: SQLite db handle */
danielk197765904932004-05-26 06:18:37 +0000627);
danielk1977295ba552004-05-19 10:34:51 +0000628
danielk197765904932004-05-26 06:18:37 +0000629/*
630** Return the error code for the most recent sqlite3_* API call associated
631** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
632** API call was successful.
633**
634** Calls to many sqlite3_* functions set the error code and string returned
635** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
636** (overwriting the previous values). Note that calls to sqlite3_errcode(),
637** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
638** results of future invocations.
639**
640** Assuming no other intervening sqlite3_* API calls are made, the error
641** code returned by this function is associated with the same error as
642** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
643*/
644int sqlite3_errcode(sqlite3 *db);
645
646/*
647** Return a pointer to a UTF-8 encoded string describing in english the
648** error condition for the most recent sqlite3_* API call. The returned
649** string is always terminated by an 0x00 byte.
650**
651** The string "not an error" is returned when the most recent API call was
652** successful.
653*/
654const char *sqlite3_errmsg(sqlite3*);
655
656/*
657** Return a pointer to a UTF-16 native byte order encoded string describing
658** in english the error condition for the most recent sqlite3_* API call.
659** The returned string is always terminated by a pair of 0x00 bytes.
660**
661** The string "not an error" is returned when the most recent API call was
662** successful.
663*/
664const void *sqlite3_errmsg16(sqlite3*);
665
666/*
667** An instance of the following opaque structure is used to represent
668** a compiled SQL statment.
669*/
danielk1977fc57d7b2004-05-26 02:04:57 +0000670typedef struct sqlite3_stmt sqlite3_stmt;
671
danielk1977e3209e42004-05-20 01:40:18 +0000672/*
danielk197765904932004-05-26 06:18:37 +0000673** To execute an SQL query, it must first be compiled into a byte-code
674** program using one of the following routines. The only difference between
675** them is that the second argument, specifying the SQL statement to
676** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare()
677** function and UTF-16 for sqlite3_prepare16().
678**
679** The first parameter "db" is an SQLite database handle. The second
680** parameter "zSql" is the statement to be compiled, encoded as either
681** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less
682** than zero, then zSql is read up to the first nul terminator. If
683** "nBytes" is not less than zero, then it is the length of the string zSql
684** in bytes (not characters).
685**
686** *pzTail is made to point to the first byte past the end of the first
687** SQL statement in zSql. This routine only compiles the first statement
688** in zSql, so *pzTail is left pointing to what remains uncompiled.
689**
690** *ppStmt is left pointing to a compiled SQL statement that can be
691** executed using sqlite3_step(). Or if there is an error, *ppStmt may be
692** set to NULL. If the input text contained no SQL (if the input is and
693** empty string or a comment) then *ppStmt is set to NULL.
694**
695** On success, SQLITE_OK is returned. Otherwise an error code is returned.
696*/
697int sqlite3_prepare(
698 sqlite3 *db, /* Database handle */
699 const char *zSql, /* SQL statement, UTF-8 encoded */
700 int nBytes, /* Length of zSql in bytes. */
701 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
702 const char **pzTail /* OUT: Pointer to unused portion of zSql */
703);
704int sqlite3_prepare16(
705 sqlite3 *db, /* Database handle */
706 const void *zSql, /* SQL statement, UTF-16 encoded */
707 int nBytes, /* Length of zSql in bytes. */
708 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
709 const void **pzTail /* OUT: Pointer to unused portion of zSql */
710);
711
712/*
drhb900aaf2006-11-09 00:24:53 +0000713** Newer versions of the prepare API work just like the legacy versions
714** but with one exception: The a copy of the SQL text is saved in the
715** sqlite3_stmt structure that is returned. If this copy exists, it
716** modifieds the behavior of sqlite3_step() slightly. First, sqlite3_step()
717** will no longer return an SQLITE_SCHEMA error but will instead automatically
718** rerun the compiler to rebuild the prepared statement. Secondly,
719** sqlite3_step() now turns a full result code - the result code that
720** use used to have to call sqlite3_reset() to get.
721*/
722int sqlite3_prepare_v2(
723 sqlite3 *db, /* Database handle */
724 const char *zSql, /* SQL statement, UTF-8 encoded */
725 int nBytes, /* Length of zSql in bytes. */
726 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
727 const char **pzTail /* OUT: Pointer to unused portion of zSql */
728);
729int sqlite3_prepare16_v2(
730 sqlite3 *db, /* Database handle */
731 const void *zSql, /* SQL statement, UTF-16 encoded */
732 int nBytes, /* Length of zSql in bytes. */
733 sqlite3_stmt **ppStmt, /* OUT: Statement handle */
734 const void **pzTail /* OUT: Pointer to unused portion of zSql */
735);
736
737/*
drhf4479502004-05-27 03:12:53 +0000738** Pointers to the following two opaque structures are used to communicate
739** with the implementations of user-defined functions.
740*/
741typedef struct sqlite3_context sqlite3_context;
742typedef struct Mem sqlite3_value;
743
744/*
drh4f26d6c2004-05-26 23:25:30 +0000745** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
drh32c0d4f2004-12-07 02:14:51 +0000746** one or more literals can be replace by parameters "?" or ":AAA" or
747** "$VVV" where AAA is an identifer and VVV is a variable name according
748** to the syntax rules of the TCL programming language.
749** The value of these parameters (also called "host parameter names") can
750** be set using the routines listed below.
drh4f26d6c2004-05-26 23:25:30 +0000751**
752** In every case, the first parameter is a pointer to the sqlite3_stmt
753** structure returned from sqlite3_prepare(). The second parameter is the
drh32c0d4f2004-12-07 02:14:51 +0000754** index of the parameter. The first parameter as an index of 1. For
755** named parameters (":AAA" or "$VVV") you can use
756** sqlite3_bind_parameter_index() to get the correct index value given
757** the parameters name. If the same named parameter occurs more than
758** once, it is assigned the same index each time.
drh4f26d6c2004-05-26 23:25:30 +0000759**
drh900dfba2004-07-21 15:21:36 +0000760** The fifth parameter to sqlite3_bind_blob(), sqlite3_bind_text(), and
761** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or
762** text after SQLite has finished with it. If the fifth argument is the
763** special value SQLITE_STATIC, then the library assumes that the information
764** is in static, unmanaged space and does not need to be freed. If the
765** fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its
766** own private copy of the data.
drh4f26d6c2004-05-26 23:25:30 +0000767**
768** The sqlite3_bind_* routine must be called before sqlite3_step() after
drh32c0d4f2004-12-07 02:14:51 +0000769** an sqlite3_prepare() or sqlite3_reset(). Unbound parameterss are
770** interpreted as NULL.
drh4f26d6c2004-05-26 23:25:30 +0000771*/
danielk1977d8123362004-06-12 09:25:12 +0000772int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000773int sqlite3_bind_double(sqlite3_stmt*, int, double);
774int sqlite3_bind_int(sqlite3_stmt*, int, int);
drhefad9992004-06-22 12:13:55 +0000775int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64);
drhf4479502004-05-27 03:12:53 +0000776int sqlite3_bind_null(sqlite3_stmt*, int);
danielk1977d8123362004-06-12 09:25:12 +0000777int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));
778int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*));
drhf4479502004-05-27 03:12:53 +0000779int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*);
drh4f26d6c2004-05-26 23:25:30 +0000780
781/*
drh32c0d4f2004-12-07 02:14:51 +0000782** Return the number of parameters in a compiled SQL statement. This
drh75f6a032004-07-15 14:15:00 +0000783** routine was added to support DBD::SQLite.
drh75f6a032004-07-15 14:15:00 +0000784*/
785int sqlite3_bind_parameter_count(sqlite3_stmt*);
786
787/*
drh32c0d4f2004-12-07 02:14:51 +0000788** Return the name of the i-th parameter. Ordinary parameters "?" are
789** nameless and a NULL is returned. For parameters of the form :AAA or
790** $VVV the complete text of the parameter name is returned, including
791** the initial ":" or "$". NULL is returned if the index is out of range.
drh895d7472004-08-20 16:02:39 +0000792*/
793const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
794
795/*
drhfa6bc002004-09-07 16:19:52 +0000796** Return the index of a parameter with the given name. The name
797** must match exactly. If no parameter with the given name is found,
798** return 0.
799*/
800int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
801
802/*
danielk1977600dd0b2005-01-20 01:14:23 +0000803** Set all the parameters in the compiled SQL statement to NULL.
danielk1977600dd0b2005-01-20 01:14:23 +0000804*/
805int sqlite3_clear_bindings(sqlite3_stmt*);
806
807/*
danielk197765904932004-05-26 06:18:37 +0000808** Return the number of columns in the result set returned by the compiled
809** SQL statement. This routine returns 0 if pStmt is an SQL statement
810** that does not return data (for example an UPDATE).
811*/
812int sqlite3_column_count(sqlite3_stmt *pStmt);
813
814/*
815** The first parameter is a compiled SQL statement. This function returns
816** the column heading for the Nth column of that statement, where N is the
drh4f26d6c2004-05-26 23:25:30 +0000817** second function parameter. The string returned is UTF-8 for
818** sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
danielk197765904932004-05-26 06:18:37 +0000819*/
820const char *sqlite3_column_name(sqlite3_stmt*,int);
danielk197765904932004-05-26 06:18:37 +0000821const void *sqlite3_column_name16(sqlite3_stmt*,int);
822
823/*
danielk1977955de522006-02-10 02:27:42 +0000824** The first parameter to the following calls is a compiled SQL statement.
825** These functions return information about the Nth column returned by
826** the statement, where N is the second function argument.
827**
828** If the Nth column returned by the statement is not a column value,
829** then all of the functions return NULL. Otherwise, the return the
830** name of the attached database, table and column that the expression
831** extracts a value from.
832**
833** As with all other SQLite APIs, those postfixed with "16" return UTF-16
834** encoded strings, the other functions return UTF-8. The memory containing
835** the returned strings is valid until the statement handle is finalized().
danielk19774b1ae992006-02-10 03:06:10 +0000836**
837** These APIs are only available if the library was compiled with the
838** SQLITE_ENABLE_COLUMN_METADATA preprocessor symbol defined.
danielk1977955de522006-02-10 02:27:42 +0000839*/
840const char *sqlite3_column_database_name(sqlite3_stmt*,int);
841const void *sqlite3_column_database_name16(sqlite3_stmt*,int);
842const char *sqlite3_column_table_name(sqlite3_stmt*,int);
843const void *sqlite3_column_table_name16(sqlite3_stmt*,int);
844const char *sqlite3_column_origin_name(sqlite3_stmt*,int);
845const void *sqlite3_column_origin_name16(sqlite3_stmt*,int);
846
847/*
danielk197765904932004-05-26 06:18:37 +0000848** The first parameter is a compiled SQL statement. If this statement
849** is a SELECT statement, the Nth column of the returned result set
850** of the SELECT is a table column then the declared type of the table
851** column is returned. If the Nth column of the result set is not at table
852** column, then a NULL pointer is returned. The returned string is always
853** UTF-8 encoded. For example, in the database schema:
854**
855** CREATE TABLE t1(c1 VARIANT);
856**
857** And the following statement compiled:
858**
danielk1977955de522006-02-10 02:27:42 +0000859** SELECT c1 + 1, c1 FROM t1;
danielk197765904932004-05-26 06:18:37 +0000860**
861** Then this routine would return the string "VARIANT" for the second
862** result column (i==1), and a NULL pointer for the first result column
863** (i==0).
864*/
865const char *sqlite3_column_decltype(sqlite3_stmt *, int i);
866
867/*
868** The first parameter is a compiled SQL statement. If this statement
869** is a SELECT statement, the Nth column of the returned result set
870** of the SELECT is a table column then the declared type of the table
871** column is returned. If the Nth column of the result set is not at table
872** column, then a NULL pointer is returned. The returned string is always
873** UTF-16 encoded. For example, in the database schema:
874**
drh4f26d6c2004-05-26 23:25:30 +0000875** CREATE TABLE t1(c1 INTEGER);
danielk197765904932004-05-26 06:18:37 +0000876**
877** And the following statement compiled:
878**
danielk1977955de522006-02-10 02:27:42 +0000879** SELECT c1 + 1, c1 FROM t1;
danielk197765904932004-05-26 06:18:37 +0000880**
drh4f26d6c2004-05-26 23:25:30 +0000881** Then this routine would return the string "INTEGER" for the second
danielk197765904932004-05-26 06:18:37 +0000882** result column (i==1), and a NULL pointer for the first result column
883** (i==0).
884*/
885const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
886
danielk1977106bb232004-05-21 10:08:53 +0000887/*
888** After an SQL query has been compiled with a call to either
889** sqlite3_prepare() or sqlite3_prepare16(), then this function must be
890** called one or more times to execute the statement.
891**
892** The return value will be either SQLITE_BUSY, SQLITE_DONE,
893** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE.
894**
895** SQLITE_BUSY means that the database engine attempted to open
896** a locked database and there is no busy callback registered.
897** Call sqlite3_step() again to retry the open.
898**
899** SQLITE_DONE means that the statement has finished executing
900** successfully. sqlite3_step() should not be called again on this virtual
901** machine.
902**
903** If the SQL statement being executed returns any data, then
904** SQLITE_ROW is returned each time a new row of data is ready
905** for processing by the caller. The values may be accessed using
906** the sqlite3_column_*() functions described below. sqlite3_step()
907** is called again to retrieve the next row of data.
908**
909** SQLITE_ERROR means that a run-time error (such as a constraint
910** violation) has occurred. sqlite3_step() should not be called again on
911** the VM. More information may be found by calling sqlite3_errmsg().
912**
913** SQLITE_MISUSE means that the this routine was called inappropriately.
914** Perhaps it was called on a virtual machine that had already been
915** finalized or on one that had previously returned SQLITE_ERROR or
916** SQLITE_DONE. Or it could be the case the the same database connection
917** is being used simulataneously by two or more threads.
918*/
danielk197717240fd2004-05-26 00:07:25 +0000919int sqlite3_step(sqlite3_stmt*);
danielk1977106bb232004-05-21 10:08:53 +0000920
danielk1977106bb232004-05-21 10:08:53 +0000921/*
922** Return the number of values in the current row of the result set.
923**
924** After a call to sqlite3_step() that returns SQLITE_ROW, this routine
925** will return the same value as the sqlite3_column_count() function.
926** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or
927** error code, or before sqlite3_step() has been called on a
928** compiled SQL statement, this routine returns zero.
929*/
danielk197793d46752004-05-23 13:30:58 +0000930int sqlite3_data_count(sqlite3_stmt *pStmt);
danielk19774adee202004-05-08 08:23:19 +0000931
drh4f26d6c2004-05-26 23:25:30 +0000932/*
933** Values are stored in the database in one of the following fundamental
934** types.
935*/
drh9c054832004-05-31 18:51:57 +0000936#define SQLITE_INTEGER 1
937#define SQLITE_FLOAT 2
drh1e284f42004-10-06 15:52:01 +0000938/* #define SQLITE_TEXT 3 // See below */
drh9c054832004-05-31 18:51:57 +0000939#define SQLITE_BLOB 4
940#define SQLITE_NULL 5
danielk19774adee202004-05-08 08:23:19 +0000941
danielk1977106bb232004-05-21 10:08:53 +0000942/*
drh1e284f42004-10-06 15:52:01 +0000943** SQLite version 2 defines SQLITE_TEXT differently. To allow both
944** version 2 and version 3 to be included, undefine them both if a
945** conflict is seen. Define SQLITE3_TEXT to be the version 3 value.
946*/
947#ifdef SQLITE_TEXT
948# undef SQLITE_TEXT
949#else
950# define SQLITE_TEXT 3
951#endif
952#define SQLITE3_TEXT 3
953
954/*
drh4f26d6c2004-05-26 23:25:30 +0000955** The next group of routines returns information about the information
956** in a single column of the current result row of a query. In every
957** case the first parameter is a pointer to the SQL statement that is being
958** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and
959** the second argument is the index of the column for which information
960** should be returned. iCol is zero-indexed. The left-most column as an
961** index of 0.
danielk1977106bb232004-05-21 10:08:53 +0000962**
drh4f26d6c2004-05-26 23:25:30 +0000963** If the SQL statement is not currently point to a valid row, or if the
964** the colulmn index is out of range, the result is undefined.
965**
966** These routines attempt to convert the value where appropriate. For
967** example, if the internal representation is FLOAT and a text result
968** is requested, sprintf() is used internally to do the conversion
969** automatically. The following table details the conversions that
970** are applied:
971**
972** Internal Type Requested Type Conversion
973** ------------- -------------- --------------------------
974** NULL INTEGER Result is 0
975** NULL FLOAT Result is 0.0
976** NULL TEXT Result is an empty string
977** NULL BLOB Result is a zero-length BLOB
978** INTEGER FLOAT Convert from integer to float
979** INTEGER TEXT ASCII rendering of the integer
980** INTEGER BLOB Same as for INTEGER->TEXT
981** FLOAT INTEGER Convert from float to integer
982** FLOAT TEXT ASCII rendering of the float
983** FLOAT BLOB Same as FLOAT->TEXT
984** TEXT INTEGER Use atoi()
985** TEXT FLOAT Use atof()
986** TEXT BLOB No change
987** BLOB INTEGER Convert to TEXT then use atoi()
988** BLOB FLOAT Convert to TEXT then use atof()
989** BLOB TEXT Add a \000 terminator if needed
990**
991** The following access routines are provided:
992**
993** _type() Return the datatype of the result. This is one of
994** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB,
995** or SQLITE_NULL.
996** _blob() Return the value of a BLOB.
997** _bytes() Return the number of bytes in a BLOB value or the number
998** of bytes in a TEXT value represented as UTF-8. The \000
999** terminator is included in the byte count for TEXT values.
1000** _bytes16() Return the number of bytes in a BLOB value or the number
1001** of bytes in a TEXT value represented as UTF-16. The \u0000
1002** terminator is included in the byte count for TEXT values.
1003** _double() Return a FLOAT value.
1004** _int() Return an INTEGER value in the host computer's native
1005** integer representation. This might be either a 32- or 64-bit
1006** integer depending on the host.
1007** _int64() Return an INTEGER value as a 64-bit signed integer.
1008** _text() Return the value as UTF-8 text.
1009** _text16() Return the value as UTF-16 text.
danielk1977106bb232004-05-21 10:08:53 +00001010*/
drhf4479502004-05-27 03:12:53 +00001011const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
1012int sqlite3_column_bytes(sqlite3_stmt*, int iCol);
1013int sqlite3_column_bytes16(sqlite3_stmt*, int iCol);
1014double sqlite3_column_double(sqlite3_stmt*, int iCol);
1015int sqlite3_column_int(sqlite3_stmt*, int iCol);
drhefad9992004-06-22 12:13:55 +00001016sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol);
drhf4479502004-05-27 03:12:53 +00001017const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol);
1018const void *sqlite3_column_text16(sqlite3_stmt*, int iCol);
drh4f26d6c2004-05-26 23:25:30 +00001019int sqlite3_column_type(sqlite3_stmt*, int iCol);
drh29d72102006-02-09 22:13:41 +00001020int sqlite3_column_numeric_type(sqlite3_stmt*, int iCol);
drh4be8b512006-06-13 23:51:34 +00001021sqlite3_value *sqlite3_column_value(sqlite3_stmt*, int iCol);
danielk19774adee202004-05-08 08:23:19 +00001022
danielk197765904932004-05-26 06:18:37 +00001023/*
1024** The sqlite3_finalize() function is called to delete a compiled
1025** SQL statement obtained by a previous call to sqlite3_prepare()
1026** or sqlite3_prepare16(). If the statement was executed successfully, or
1027** not executed at all, then SQLITE_OK is returned. If execution of the
1028** statement failed then an error code is returned.
1029**
1030** This routine can be called at any point during the execution of the
1031** virtual machine. If the virtual machine has not completed execution
1032** when this routine is called, that is like encountering an error or
1033** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be
1034** rolled back and transactions cancelled, depending on the circumstances,
1035** and the result code returned will be SQLITE_ABORT.
1036*/
1037int sqlite3_finalize(sqlite3_stmt *pStmt);
1038
1039/*
1040** The sqlite3_reset() function is called to reset a compiled SQL
1041** statement obtained by a previous call to sqlite3_prepare() or
1042** sqlite3_prepare16() back to it's initial state, ready to be re-executed.
1043** Any SQL statement variables that had values bound to them using
1044** the sqlite3_bind_*() API retain their values.
1045*/
1046int sqlite3_reset(sqlite3_stmt *pStmt);
1047
1048/*
danielk197765904932004-05-26 06:18:37 +00001049** The following two functions are used to add user functions or aggregates
1050** implemented in C to the SQL langauge interpreted by SQLite. The
1051** difference only between the two is that the second parameter, the
1052** name of the (scalar) function or aggregate, is encoded in UTF-8 for
1053** sqlite3_create_function() and UTF-16 for sqlite3_create_function16().
1054**
1055** The first argument is the database handle that the new function or
1056** aggregate is to be added to. If a single program uses more than one
1057** database handle internally, then user functions or aggregates must
1058** be added individually to each database handle with which they will be
1059** used.
1060**
1061** The third parameter is the number of arguments that the function or
1062** aggregate takes. If this parameter is negative, then the function or
1063** aggregate may take any number of arguments.
1064**
danielk1977d8123362004-06-12 09:25:12 +00001065** The fourth parameter is one of SQLITE_UTF* values defined below,
1066** indicating the encoding that the function is most likely to handle
1067** values in. This does not change the behaviour of the programming
1068** interface. However, if two versions of the same function are registered
1069** with different encoding values, SQLite invokes the version likely to
1070** minimize conversions between text encodings.
danielk1977d02eb1f2004-06-06 09:44:03 +00001071**
danielk197765904932004-05-26 06:18:37 +00001072** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
1073** pointers to user implemented C functions that implement the user
1074** function or aggregate. A scalar function requires an implementation of
1075** the xFunc callback only, NULL pointers should be passed as the xStep
1076** and xFinal parameters. An aggregate function requires an implementation
1077** of xStep and xFinal, but NULL should be passed for xFunc. To delete an
1078** existing user function or aggregate, pass NULL for all three function
1079** callback. Specifying an inconstent set of callback values, such as an
1080** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is
1081** returned.
1082*/
1083int sqlite3_create_function(
1084 sqlite3 *,
1085 const char *zFunctionName,
1086 int nArg,
1087 int eTextRep,
danielk197765904932004-05-26 06:18:37 +00001088 void*,
1089 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
1090 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
1091 void (*xFinal)(sqlite3_context*)
1092);
1093int sqlite3_create_function16(
1094 sqlite3*,
1095 const void *zFunctionName,
1096 int nArg,
1097 int eTextRep,
danielk197765904932004-05-26 06:18:37 +00001098 void*,
1099 void (*xFunc)(sqlite3_context*,int,sqlite3_value**),
1100 void (*xStep)(sqlite3_context*,int,sqlite3_value**),
1101 void (*xFinal)(sqlite3_context*)
1102);
1103
1104/*
drhcf85a512006-02-09 18:35:29 +00001105** This function is deprecated. Do not use it. It continues to exist
1106** so as not to break legacy code. But new code should avoid using it.
danielk197765904932004-05-26 06:18:37 +00001107*/
1108int sqlite3_aggregate_count(sqlite3_context*);
1109
danielk19770ffba6b2004-05-24 09:10:10 +00001110/*
drh4f26d6c2004-05-26 23:25:30 +00001111** The next group of routines returns information about parameters to
1112** a user-defined function. Function implementations use these routines
1113** to access their parameters. These routines are the same as the
1114** sqlite3_column_* routines except that these routines take a single
1115** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer
1116** column number.
danielk19770ffba6b2004-05-24 09:10:10 +00001117*/
drhf4479502004-05-27 03:12:53 +00001118const void *sqlite3_value_blob(sqlite3_value*);
1119int sqlite3_value_bytes(sqlite3_value*);
1120int sqlite3_value_bytes16(sqlite3_value*);
1121double sqlite3_value_double(sqlite3_value*);
1122int sqlite3_value_int(sqlite3_value*);
drhefad9992004-06-22 12:13:55 +00001123sqlite_int64 sqlite3_value_int64(sqlite3_value*);
drhf4479502004-05-27 03:12:53 +00001124const unsigned char *sqlite3_value_text(sqlite3_value*);
1125const void *sqlite3_value_text16(sqlite3_value*);
danielk1977d8123362004-06-12 09:25:12 +00001126const void *sqlite3_value_text16le(sqlite3_value*);
1127const void *sqlite3_value_text16be(sqlite3_value*);
danielk197793d46752004-05-23 13:30:58 +00001128int sqlite3_value_type(sqlite3_value*);
drh29d72102006-02-09 22:13:41 +00001129int sqlite3_value_numeric_type(sqlite3_value*);
danielk19770ffba6b2004-05-24 09:10:10 +00001130
1131/*
danielk19770ae8b832004-05-25 12:05:56 +00001132** Aggregate functions use the following routine to allocate
1133** a structure for storing their state. The first time this routine
1134** is called for a particular aggregate, a new structure of size nBytes
1135** is allocated, zeroed, and returned. On subsequent calls (for the
1136** same aggregate instance) the same buffer is returned. The implementation
1137** of the aggregate can use the returned buffer to accumulate data.
1138**
1139** The buffer allocated is freed automatically by SQLite.
1140*/
drh4f26d6c2004-05-26 23:25:30 +00001141void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
danielk19777e18c252004-05-25 11:47:24 +00001142
1143/*
drhc0f2a012005-07-09 02:39:40 +00001144** The pUserData parameter to the sqlite3_create_function()
1145** routine used to register user functions is available to
1146** the implementation of the function using this call.
danielk19777e18c252004-05-25 11:47:24 +00001147*/
1148void *sqlite3_user_data(sqlite3_context*);
1149
1150/*
danielk1977682f68b2004-06-05 10:22:17 +00001151** The following two functions may be used by scalar user functions to
1152** associate meta-data with argument values. If the same value is passed to
1153** multiple invocations of the user-function during query execution, under
1154** some circumstances the associated meta-data may be preserved. This may
1155** be used, for example, to add a regular-expression matching scalar
1156** function. The compiled version of the regular expression is stored as
1157** meta-data associated with the SQL value passed as the regular expression
1158** pattern.
1159**
1160** Calling sqlite3_get_auxdata() returns a pointer to the meta data
1161** associated with the Nth argument value to the current user function
1162** call, where N is the second parameter. If no meta-data has been set for
1163** that value, then a NULL pointer is returned.
1164**
1165** The sqlite3_set_auxdata() is used to associate meta data with a user
1166** function argument. The third parameter is a pointer to the meta data
1167** to be associated with the Nth user function argument value. The fourth
1168** parameter specifies a 'delete function' that will be called on the meta
1169** data pointer to release it when it is no longer required. If the delete
1170** function pointer is NULL, it is not invoked.
1171**
1172** In practice, meta-data is preserved between function calls for
1173** expressions that are constant at compile time. This includes literal
1174** values and SQL variables.
1175*/
1176void *sqlite3_get_auxdata(sqlite3_context*, int);
1177void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*));
1178
drha2854222004-06-17 19:04:17 +00001179
1180/*
1181** These are special value for the destructor that is passed in as the
1182** final argument to routines like sqlite3_result_blob(). If the destructor
1183** argument is SQLITE_STATIC, it means that the content pointer is constant
1184** and will never change. It does not need to be destroyed. The
1185** SQLITE_TRANSIENT value means that the content will likely change in
1186** the near future and that SQLite should make its own private copy of
1187** the content before returning.
1188*/
danielk1977d8123362004-06-12 09:25:12 +00001189#define SQLITE_STATIC ((void(*)(void *))0)
1190#define SQLITE_TRANSIENT ((void(*)(void *))-1)
1191
danielk1977682f68b2004-06-05 10:22:17 +00001192/*
drh4f26d6c2004-05-26 23:25:30 +00001193** User-defined functions invoke the following routines in order to
1194** set their return value.
danielk19777e18c252004-05-25 11:47:24 +00001195*/
danielk1977d8123362004-06-12 09:25:12 +00001196void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001197void sqlite3_result_double(sqlite3_context*, double);
danielk19777e18c252004-05-25 11:47:24 +00001198void sqlite3_result_error(sqlite3_context*, const char*, int);
1199void sqlite3_result_error16(sqlite3_context*, const void*, int);
drh4f26d6c2004-05-26 23:25:30 +00001200void sqlite3_result_int(sqlite3_context*, int);
drhefad9992004-06-22 12:13:55 +00001201void sqlite3_result_int64(sqlite3_context*, sqlite_int64);
drh4f26d6c2004-05-26 23:25:30 +00001202void sqlite3_result_null(sqlite3_context*);
danielk1977d8123362004-06-12 09:25:12 +00001203void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*));
1204void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*));
1205void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*));
1206void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*));
drh4f26d6c2004-05-26 23:25:30 +00001207void sqlite3_result_value(sqlite3_context*, sqlite3_value*);
drhf9b596e2004-05-26 16:54:42 +00001208
drh52619df2004-06-11 17:48:02 +00001209/*
1210** These are the allowed values for the eTextRep argument to
1211** sqlite3_create_collation and sqlite3_create_function.
1212*/
drh7d9bd4e2006-02-16 18:16:36 +00001213#define SQLITE_UTF8 1
1214#define SQLITE_UTF16LE 2
1215#define SQLITE_UTF16BE 3
1216#define SQLITE_UTF16 4 /* Use native byte order */
1217#define SQLITE_ANY 5 /* sqlite3_create_function only */
1218#define SQLITE_UTF16_ALIGNED 8 /* sqlite3_create_collation only */
danielk1977466be562004-06-10 02:16:01 +00001219
danielk19777cedc8d2004-06-10 10:50:08 +00001220/*
1221** These two functions are used to add new collation sequences to the
1222** sqlite3 handle specified as the first argument.
1223**
1224** The name of the new collation sequence is specified as a UTF-8 string
1225** for sqlite3_create_collation() and a UTF-16 string for
1226** sqlite3_create_collation16(). In both cases the name is passed as the
1227** second function argument.
1228**
1229** The third argument must be one of the constants SQLITE_UTF8,
1230** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied
1231** routine expects to be passed pointers to strings encoded using UTF-8,
1232** UTF-16 little-endian or UTF-16 big-endian respectively.
1233**
1234** A pointer to the user supplied routine must be passed as the fifth
1235** argument. If it is NULL, this is the same as deleting the collation
1236** sequence (so that SQLite cannot call it anymore). Each time the user
1237** supplied function is invoked, it is passed a copy of the void* passed as
1238** the fourth argument to sqlite3_create_collation() or
1239** sqlite3_create_collation16() as its first parameter.
1240**
1241** The remaining arguments to the user-supplied routine are two strings,
1242** each represented by a [length, data] pair and encoded in the encoding
1243** that was passed as the third argument when the collation sequence was
1244** registered. The user routine should return negative, zero or positive if
1245** the first string is less than, equal to, or greater than the second
1246** string. i.e. (STRING1 - STRING2).
1247*/
danielk19770202b292004-06-09 09:55:16 +00001248int sqlite3_create_collation(
1249 sqlite3*,
1250 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001251 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001252 void*,
1253 int(*xCompare)(void*,int,const void*,int,const void*)
1254);
1255int sqlite3_create_collation16(
1256 sqlite3*,
1257 const char *zName,
danielk19777cedc8d2004-06-10 10:50:08 +00001258 int eTextRep,
danielk19770202b292004-06-09 09:55:16 +00001259 void*,
1260 int(*xCompare)(void*,int,const void*,int,const void*)
1261);
1262
danielk19777cedc8d2004-06-10 10:50:08 +00001263/*
1264** To avoid having to register all collation sequences before a database
1265** can be used, a single callback function may be registered with the
1266** database handle to be called whenever an undefined collation sequence is
1267** required.
1268**
1269** If the function is registered using the sqlite3_collation_needed() API,
1270** then it is passed the names of undefined collation sequences as strings
1271** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names
1272** are passed as UTF-16 in machine native byte order. A call to either
1273** function replaces any existing callback.
1274**
1275** When the user-function is invoked, the first argument passed is a copy
1276** of the second argument to sqlite3_collation_needed() or
1277** sqlite3_collation_needed16(). The second argument is the database
1278** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or
1279** SQLITE_UTF16LE, indicating the most desirable form of the collation
1280** sequence function required. The fourth parameter is the name of the
1281** required collation sequence.
1282**
1283** The collation sequence is returned to SQLite by a collation-needed
1284** callback using the sqlite3_create_collation() or
1285** sqlite3_create_collation16() APIs, described above.
1286*/
1287int sqlite3_collation_needed(
1288 sqlite3*,
1289 void*,
1290 void(*)(void*,sqlite3*,int eTextRep,const char*)
1291);
1292int sqlite3_collation_needed16(
1293 sqlite3*,
1294 void*,
1295 void(*)(void*,sqlite3*,int eTextRep,const void*)
1296);
1297
drh2011d5f2004-07-22 02:40:37 +00001298/*
1299** Specify the key for an encrypted database. This routine should be
1300** called right after sqlite3_open().
1301**
1302** The code to implement this API is not available in the public release
1303** of SQLite.
1304*/
1305int sqlite3_key(
1306 sqlite3 *db, /* Database to be rekeyed */
1307 const void *pKey, int nKey /* The key */
1308);
1309
1310/*
1311** Change the key on an open database. If the current database is not
1312** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the
1313** database is decrypted.
1314**
1315** The code to implement this API is not available in the public release
1316** of SQLite.
1317*/
1318int sqlite3_rekey(
1319 sqlite3 *db, /* Database to be rekeyed */
1320 const void *pKey, int nKey /* The new key */
1321);
danielk19770202b292004-06-09 09:55:16 +00001322
drhab3f9fe2004-08-14 17:10:10 +00001323/*
danielk1977600dd0b2005-01-20 01:14:23 +00001324** Sleep for a little while. The second parameter is the number of
1325** miliseconds to sleep for.
1326**
1327** If the operating system does not support sleep requests with
1328** milisecond time resolution, then the time will be rounded up to
1329** the nearest second. The number of miliseconds of sleep actually
1330** requested from the operating system is returned.
danielk1977600dd0b2005-01-20 01:14:23 +00001331*/
1332int sqlite3_sleep(int);
1333
1334/*
drh65efb652005-06-12 22:12:39 +00001335** Return TRUE (non-zero) if the statement supplied as an argument needs
drhd89bd002005-01-22 03:03:54 +00001336** to be recompiled. A statement needs to be recompiled whenever the
1337** execution environment changes in a way that would alter the program
1338** that sqlite3_prepare() generates. For example, if new functions or
1339** collating sequences are registered or if an authorizer function is
1340** added or changed.
1341**
drhd89bd002005-01-22 03:03:54 +00001342*/
1343int sqlite3_expired(sqlite3_stmt*);
1344
1345/*
drhf8db1bc2005-04-22 02:38:37 +00001346** Move all bindings from the first prepared statement over to the second.
1347** This routine is useful, for example, if the first prepared statement
1348** fails with an SQLITE_SCHEMA error. The same SQL can be prepared into
1349** the second prepared statement then all of the bindings transfered over
1350** to the second statement before the first statement is finalized.
drhf8db1bc2005-04-22 02:38:37 +00001351*/
1352int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*);
1353
1354/*
tpoindex9a09a3c2004-12-20 19:01:32 +00001355** If the following global variable is made to point to a
drhab3f9fe2004-08-14 17:10:10 +00001356** string which is the name of a directory, then all temporary files
1357** created by SQLite will be placed in that directory. If this variable
1358** is NULL pointer, then SQLite does a search for an appropriate temporary
1359** file directory.
1360**
danielk19776b456a22005-03-21 04:04:02 +00001361** Once sqlite3_open() has been called, changing this variable will invalidate
1362** the current temporary database, if any.
drhab3f9fe2004-08-14 17:10:10 +00001363*/
tpoindex9a09a3c2004-12-20 19:01:32 +00001364extern char *sqlite3_temp_directory;
drhab3f9fe2004-08-14 17:10:10 +00001365
danielk19776b456a22005-03-21 04:04:02 +00001366/*
1367** This function is called to recover from a malloc() failure that occured
1368** within the SQLite library. Normally, after a single malloc() fails the
1369** library refuses to function (all major calls return SQLITE_NOMEM).
drh9a7e6082005-03-31 22:26:19 +00001370** This function restores the library state so that it can be used again.
danielk19776b456a22005-03-21 04:04:02 +00001371**
1372** All existing statements (sqlite3_stmt pointers) must be finalized or
1373** reset before this call is made. Otherwise, SQLITE_BUSY is returned.
1374** If any in-memory databases are in use, either as a main or TEMP
1375** database, SQLITE_ERROR is returned. In either of these cases, the
1376** library is not reset and remains unusable.
1377**
1378** This function is *not* threadsafe. Calling this from within a threaded
1379** application when threads other than the caller have used SQLite is
1380** dangerous and will almost certainly result in malfunctions.
1381**
1382** This functionality can be omitted from a build by defining the
1383** SQLITE_OMIT_GLOBALRECOVER at compile time.
1384*/
drhd9cb6ac2005-10-20 07:28:17 +00001385int sqlite3_global_recover(void);
danielk19776b456a22005-03-21 04:04:02 +00001386
drh3e1d8e62005-05-26 16:23:34 +00001387/*
1388** Test to see whether or not the database connection is in autocommit
1389** mode. Return TRUE if it is and FALSE if not. Autocommit mode is on
1390** by default. Autocommit is disabled by a BEGIN statement and reenabled
1391** by the next COMMIT or ROLLBACK.
drh3e1d8e62005-05-26 16:23:34 +00001392*/
1393int sqlite3_get_autocommit(sqlite3*);
1394
drh51942bc2005-06-12 22:01:42 +00001395/*
1396** Return the sqlite3* database handle to which the prepared statement given
1397** in the argument belongs. This is the same database handle that was
1398** the first argument to the sqlite3_prepare() that was used to create
1399** the statement in the first place.
1400*/
1401sqlite3 *sqlite3_db_handle(sqlite3_stmt*);
drh3e1d8e62005-05-26 16:23:34 +00001402
drhb37df7b2005-10-13 02:09:49 +00001403/*
danielk197794eb6a12005-12-15 15:22:08 +00001404** Register a callback function with the database connection identified by the
1405** first argument to be invoked whenever a row is updated, inserted or deleted.
1406** Any callback set by a previous call to this function for the same
1407** database connection is overridden.
1408**
1409** The second argument is a pointer to the function to invoke when a
1410** row is updated, inserted or deleted. The first argument to the callback is
1411** a copy of the third argument to sqlite3_update_hook. The second callback
1412** argument is one of SQLITE_INSERT, SQLITE_DELETE or SQLITE_UPDATE, depending
1413** on the operation that caused the callback to be invoked. The third and
1414** fourth arguments to the callback contain pointers to the database and
1415** table name containing the affected row. The final callback parameter is
1416** the rowid of the row. In the case of an update, this is the rowid after
1417** the update takes place.
1418**
1419** The update hook is not invoked when internal system tables are
1420** modified (i.e. sqlite_master and sqlite_sequence).
danielk197771fd80b2005-12-16 06:54:01 +00001421**
1422** If another function was previously registered, its pArg value is returned.
1423** Otherwise NULL is returned.
danielk197794eb6a12005-12-15 15:22:08 +00001424*/
danielk197771fd80b2005-12-16 06:54:01 +00001425void *sqlite3_update_hook(
danielk197794eb6a12005-12-15 15:22:08 +00001426 sqlite3*,
1427 void(*)(void *,int ,char const *,char const *,sqlite_int64),
1428 void*
1429);
danielk197713a68c32005-12-15 10:11:30 +00001430
danielk1977f3f06bb2005-12-16 15:24:28 +00001431/*
1432** Register a callback to be invoked whenever a transaction is rolled
1433** back.
1434**
1435** The new callback function overrides any existing rollback-hook
1436** callback. If there was an existing callback, then it's pArg value
1437** (the third argument to sqlite3_rollback_hook() when it was registered)
1438** is returned. Otherwise, NULL is returned.
1439**
1440** For the purposes of this API, a transaction is said to have been
1441** rolled back if an explicit "ROLLBACK" statement is executed, or
1442** an error or constraint causes an implicit rollback to occur. The
1443** callback is not invoked if a transaction is automatically rolled
1444** back because the database connection is closed.
1445*/
danielk197771fd80b2005-12-16 06:54:01 +00001446void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*);
1447
danielk19777ddad962005-12-12 06:53:03 +00001448/*
danielk1977aef0bf62005-12-30 16:28:01 +00001449** This function is only available if the library is compiled without
1450** the SQLITE_OMIT_SHARED_CACHE macro defined. It is used to enable or
1451** disable (if the argument is true or false, respectively) the
1452** "shared pager" feature.
1453*/
1454int sqlite3_enable_shared_cache(int);
1455
1456/*
danielk197752622822006-01-09 09:59:49 +00001457** Attempt to free N bytes of heap memory by deallocating non-essential
1458** memory allocations held by the database library (example: memory
1459** used to cache database pages to improve performance).
1460**
drh6f7adc82006-01-11 21:41:20 +00001461** This function is not a part of standard builds. It is only created
1462** if SQLite is compiled with the SQLITE_ENABLE_MEMORY_MANAGEMENT macro.
danielk197752622822006-01-09 09:59:49 +00001463*/
1464int sqlite3_release_memory(int);
1465
1466/*
1467** Place a "soft" limit on the amount of heap memory that may be allocated by
1468** SQLite within the current thread. If an internal allocation is requested
1469** that would exceed the specified limit, sqlite3_release_memory() is invoked
1470** one or more times to free up some space before the allocation is made.
1471**
1472** The limit is called "soft", because if sqlite3_release_memory() cannot free
1473** sufficient memory to prevent the limit from being exceeded, the memory is
1474** allocated anyway and the current operation proceeds.
1475**
drh6f7adc82006-01-11 21:41:20 +00001476** This function is only available if the library was compiled with the
1477** SQLITE_ENABLE_MEMORY_MANAGEMENT option set.
danielk197752622822006-01-09 09:59:49 +00001478** memory-management has been enabled.
1479*/
drhd2d4a6b2006-01-10 15:18:27 +00001480void sqlite3_soft_heap_limit(int);
danielk197752622822006-01-09 09:59:49 +00001481
1482/*
drh6f7adc82006-01-11 21:41:20 +00001483** This routine makes sure that all thread-local storage has been
1484** deallocated for the current thread.
1485**
1486** This routine is not technically necessary. All thread-local storage
1487** will be automatically deallocated once memory-management and
1488** shared-cache are disabled and the soft heap limit has been set
1489** to zero. This routine is provided as a convenience for users who
1490** want to make absolutely sure they have not forgotten something
1491** prior to killing off a thread.
1492*/
1493void sqlite3_thread_cleanup(void);
1494
1495/*
danielk1977deb802c2006-02-09 13:43:28 +00001496** Return meta information about a specific column of a specific database
1497** table accessible using the connection handle passed as the first function
1498** argument.
1499**
1500** The column is identified by the second, third and fourth parameters to
1501** this function. The second parameter is either the name of the database
1502** (i.e. "main", "temp" or an attached database) containing the specified
1503** table or NULL. If it is NULL, then all attached databases are searched
1504** for the table using the same algorithm as the database engine uses to
1505** resolve unqualified table references.
1506**
1507** The third and fourth parameters to this function are the table and column
1508** name of the desired column, respectively. Neither of these parameters
1509** may be NULL.
1510**
1511** Meta information is returned by writing to the memory locations passed as
1512** the 5th and subsequent parameters to this function. Any of these
1513** arguments may be NULL, in which case the corresponding element of meta
1514** information is ommitted.
1515**
1516** Parameter Output Type Description
1517** -----------------------------------
1518**
1519** 5th const char* Data type
1520** 6th const char* Name of the default collation sequence
1521** 7th int True if the column has a NOT NULL constraint
1522** 8th int True if the column is part of the PRIMARY KEY
1523** 9th int True if the column is AUTOINCREMENT
1524**
1525**
1526** The memory pointed to by the character pointers returned for the
1527** declaration type and collation sequence is valid only until the next
1528** call to any sqlite API function.
1529**
1530** If the specified table is actually a view, then an error is returned.
1531**
1532** If the specified column is "rowid", "oid" or "_rowid_" and an
1533** INTEGER PRIMARY KEY column has been explicitly declared, then the output
1534** parameters are set for the explicitly declared column. If there is no
1535** explicitly declared IPK column, then the output parameters are set as
1536** follows:
1537**
1538** data type: "INTEGER"
1539** collation sequence: "BINARY"
1540** not null: 0
1541** primary key: 1
1542** auto increment: 0
1543**
1544** This function may load one or more schemas from database files. If an
1545** error occurs during this process, or if the requested table or column
1546** cannot be found, an SQLITE error code is returned and an error message
1547** left in the database handle (to be retrieved using sqlite3_errmsg()).
danielk19774b1ae992006-02-10 03:06:10 +00001548**
1549** This API is only available if the library was compiled with the
1550** SQLITE_ENABLE_COLUMN_METADATA preprocessor symbol defined.
danielk1977deb802c2006-02-09 13:43:28 +00001551*/
1552int sqlite3_table_column_metadata(
1553 sqlite3 *db, /* Connection handle */
1554 const char *zDbName, /* Database name or NULL */
1555 const char *zTableName, /* Table name */
1556 const char *zColumnName, /* Column name */
1557 char const **pzDataType, /* OUTPUT: Declared data type */
1558 char const **pzCollSeq, /* OUTPUT: Collation sequence name */
1559 int *pNotNull, /* OUTPUT: True if NOT NULL constraint exists */
1560 int *pPrimaryKey, /* OUTPUT: True if column part of PK */
1561 int *pAutoinc /* OUTPUT: True if colums is auto-increment */
1562);
1563
1564/*
drh1e397f82006-06-08 15:28:43 +00001565****** EXPERIMENTAL - subject to change without notice **************
1566**
1567** Attempt to load an SQLite extension library contained in the file
1568** zFile. The entry point is zProc. zProc may be 0 in which case the
drhc2e87a32006-06-27 15:16:14 +00001569** name of the entry point defaults to "sqlite3_extension_init".
drh1e397f82006-06-08 15:28:43 +00001570**
1571** Return SQLITE_OK on success and SQLITE_ERROR if something goes wrong.
1572**
1573** If an error occurs and pzErrMsg is not 0, then fill *pzErrMsg with
1574** error message text. The calling function should free this memory
1575** by calling sqlite3_free().
1576**
drhc2e87a32006-06-27 15:16:14 +00001577** Extension loading must be enabled using sqlite3_enable_load_extension()
1578** prior to calling this API or an error will be returned.
drh1e397f82006-06-08 15:28:43 +00001579**
1580****** EXPERIMENTAL - subject to change without notice **************
1581*/
1582int sqlite3_load_extension(
1583 sqlite3 *db, /* Load the extension into this database connection */
1584 const char *zFile, /* Name of the shared library containing extension */
1585 const char *zProc, /* Entry point. Derived from zFile if 0 */
1586 char **pzErrMsg /* Put error message here if not 0 */
1587);
1588
1589/*
drhc2e87a32006-06-27 15:16:14 +00001590** So as not to open security holes in older applications that are
1591** unprepared to deal with extension load, and as a means of disabling
1592** extension loading while executing user-entered SQL, the following
1593** API is provided to turn the extension loading mechanism on and
1594** off. It is off by default. See ticket #1863.
1595**
1596** Call this routine with onoff==1 to turn extension loading on
1597** and call it with onoff==0 to turn it back off again.
1598*/
1599int sqlite3_enable_load_extension(sqlite3 *db, int onoff);
1600
1601/*
drhe09daa92006-06-10 13:29:31 +00001602****** EXPERIMENTAL - subject to change without notice **************
drh9eff6162006-06-12 21:59:13 +00001603**
drh1409be62006-08-23 20:07:20 +00001604** Register an extension entry point that is automatically invoked
1605** whenever a new database connection is opened.
1606**
1607** This API can be invoked at program startup in order to register
1608** one or more statically linked extensions that will be available
1609** to all new database connections.
1610**
1611** Duplicate extensions are detected so calling this routine multiple
1612** times with the same extension is harmless.
1613**
1614** This routine stores a pointer to the extension in an array
1615** that is obtained from malloc(). If you run a memory leak
1616** checker on your program and it reports a leak because of this
1617** array, then invoke sqlite3_automatic_extension_reset() prior
1618** to shutdown to free the memory.
1619**
1620** Automatic extensions apply across all threads.
1621*/
1622int sqlite3_auto_extension(void *xEntryPoint);
1623
1624
1625/*
1626****** EXPERIMENTAL - subject to change without notice **************
1627**
1628** Disable all previously registered automatic extensions. This
1629** routine undoes the effect of all prior sqlite3_automatic_extension()
1630** calls.
1631**
1632** This call disabled automatic extensions in all threads.
1633*/
1634void sqlite3_reset_auto_extension(void);
1635
1636
1637/*
1638****** EXPERIMENTAL - subject to change without notice **************
1639**
drh9eff6162006-06-12 21:59:13 +00001640** The interface to the virtual-table mechanism is currently considered
1641** to be experimental. The interface might change in incompatible ways.
1642** If this is a problem for you, do not use the interface at this time.
1643**
1644** When the virtual-table mechanism stablizes, we will declare the
1645** interface fixed, support it indefinitely, and remove this comment.
1646*/
1647
1648/*
1649** Structures used by the virtual table interface
drhe09daa92006-06-10 13:29:31 +00001650*/
1651typedef struct sqlite3_vtab sqlite3_vtab;
1652typedef struct sqlite3_index_info sqlite3_index_info;
1653typedef struct sqlite3_vtab_cursor sqlite3_vtab_cursor;
1654typedef struct sqlite3_module sqlite3_module;
drh9eff6162006-06-12 21:59:13 +00001655
1656/*
1657** A module is a class of virtual tables. Each module is defined
1658** by an instance of the following structure. This structure consists
1659** mostly of methods for the module.
1660*/
drhe09daa92006-06-10 13:29:31 +00001661struct sqlite3_module {
1662 int iVersion;
danielk19779da9d472006-06-14 06:58:15 +00001663 int (*xCreate)(sqlite3*, void *pAux,
drhe4102962006-09-11 00:34:22 +00001664 int argc, const char *const*argv,
drh4ca8aac2006-09-10 17:31:58 +00001665 sqlite3_vtab **ppVTab, char**);
danielk19779da9d472006-06-14 06:58:15 +00001666 int (*xConnect)(sqlite3*, void *pAux,
drhe4102962006-09-11 00:34:22 +00001667 int argc, const char *const*argv,
drh4ca8aac2006-09-10 17:31:58 +00001668 sqlite3_vtab **ppVTab, char**);
drhe09daa92006-06-10 13:29:31 +00001669 int (*xBestIndex)(sqlite3_vtab *pVTab, sqlite3_index_info*);
1670 int (*xDisconnect)(sqlite3_vtab *pVTab);
1671 int (*xDestroy)(sqlite3_vtab *pVTab);
1672 int (*xOpen)(sqlite3_vtab *pVTab, sqlite3_vtab_cursor **ppCursor);
1673 int (*xClose)(sqlite3_vtab_cursor*);
drh4be8b512006-06-13 23:51:34 +00001674 int (*xFilter)(sqlite3_vtab_cursor*, int idxNum, const char *idxStr,
drhe09daa92006-06-10 13:29:31 +00001675 int argc, sqlite3_value **argv);
1676 int (*xNext)(sqlite3_vtab_cursor*);
danielk1977a298e902006-06-22 09:53:48 +00001677 int (*xEof)(sqlite3_vtab_cursor*);
drhe09daa92006-06-10 13:29:31 +00001678 int (*xColumn)(sqlite3_vtab_cursor*, sqlite3_context*, int);
1679 int (*xRowid)(sqlite3_vtab_cursor*, sqlite_int64 *pRowid);
danielk19771f6eec52006-06-16 06:17:47 +00001680 int (*xUpdate)(sqlite3_vtab *, int, sqlite3_value **, sqlite_int64 *);
drhe09daa92006-06-10 13:29:31 +00001681 int (*xBegin)(sqlite3_vtab *pVTab);
1682 int (*xSync)(sqlite3_vtab *pVTab);
1683 int (*xCommit)(sqlite3_vtab *pVTab);
1684 int (*xRollback)(sqlite3_vtab *pVTab);
drhb7f6f682006-07-08 17:06:43 +00001685 int (*xFindFunction)(sqlite3_vtab *pVtab, int nArg, const char *zName,
drhe94b0c32006-07-08 18:09:15 +00001686 void (**pxFunc)(sqlite3_context*,int,sqlite3_value**),
1687 void **ppArg);
drhe09daa92006-06-10 13:29:31 +00001688};
drh9eff6162006-06-12 21:59:13 +00001689
1690/*
1691** The sqlite3_index_info structure and its substructures is used to
1692** pass information into and receive the reply from the xBestIndex
1693** method of an sqlite3_module. The fields under **Inputs** are the
1694** inputs to xBestIndex and are read-only. xBestIndex inserts its
1695** results into the **Outputs** fields.
1696**
1697** The aConstraint[] array records WHERE clause constraints of the
1698** form:
1699**
1700** column OP expr
1701**
1702** Where OP is =, <, <=, >, or >=. The particular operator is stored
1703** in aConstraint[].op. The index of the column is stored in
1704** aConstraint[].iColumn. aConstraint[].usable is TRUE if the
1705** expr on the right-hand side can be evaluated (and thus the constraint
1706** is usable) and false if it cannot.
1707**
1708** The optimizer automatically inverts terms of the form "expr OP column"
1709** and makes other simplificatinos to the WHERE clause in an attempt to
1710** get as many WHERE clause terms into the form shown above as possible.
1711** The aConstraint[] array only reports WHERE clause terms in the correct
1712** form that refer to the particular virtual table being queried.
1713**
1714** Information about the ORDER BY clause is stored in aOrderBy[].
1715** Each term of aOrderBy records a column of the ORDER BY clause.
1716**
1717** The xBestIndex method must fill aConstraintUsage[] with information
danielk19775fac9f82006-06-13 14:16:58 +00001718** about what parameters to pass to xFilter. If argvIndex>0 then
drh9eff6162006-06-12 21:59:13 +00001719** the right-hand side of the corresponding aConstraint[] is evaluated
1720** and becomes the argvIndex-th entry in argv. If aConstraintUsage[].omit
1721** is true, then the constraint is assumed to be fully handled by the
1722** virtual table and is not checked again by SQLite.
1723**
drh4be8b512006-06-13 23:51:34 +00001724** The idxNum and idxPtr values are recorded and passed into xFilter.
1725** sqlite3_free() is used to free idxPtr if needToFreeIdxPtr is true.
drh9eff6162006-06-12 21:59:13 +00001726**
1727** The orderByConsumed means that output from xFilter will occur in
1728** the correct order to satisfy the ORDER BY clause so that no separate
1729** sorting step is required.
1730**
1731** The estimatedCost value is an estimate of the cost of doing the
1732** particular lookup. A full scan of a table with N entries should have
1733** a cost of N. A binary search of a table of N entries should have a
1734** cost of approximately log(N).
1735*/
drhe09daa92006-06-10 13:29:31 +00001736struct sqlite3_index_info {
1737 /* Inputs */
drh9eff6162006-06-12 21:59:13 +00001738 const int nConstraint; /* Number of entries in aConstraint */
1739 const struct sqlite3_index_constraint {
1740 int iColumn; /* Column on left-hand side of constraint */
1741 unsigned char op; /* Constraint operator */
1742 unsigned char usable; /* True if this constraint is usable */
1743 int iTermOffset; /* Used internally - xBestIndex should ignore */
1744 } *const aConstraint; /* Table of WHERE clause constraints */
1745 const int nOrderBy; /* Number of terms in the ORDER BY clause */
1746 const struct sqlite3_index_orderby {
1747 int iColumn; /* Column number */
1748 unsigned char desc; /* True for DESC. False for ASC. */
1749 } *const aOrderBy; /* The ORDER BY clause */
drhe09daa92006-06-10 13:29:31 +00001750
1751 /* Outputs */
drh9eff6162006-06-12 21:59:13 +00001752 struct sqlite3_index_constraint_usage {
1753 int argvIndex; /* if >0, constraint is part of argv to xFilter */
1754 unsigned char omit; /* Do not code a test for this constraint */
1755 } *const aConstraintUsage;
drh4be8b512006-06-13 23:51:34 +00001756 int idxNum; /* Number used to identify the index */
1757 char *idxStr; /* String, possibly obtained from sqlite3_malloc */
1758 int needToFreeIdxStr; /* Free idxStr using sqlite3_free() if true */
drh9eff6162006-06-12 21:59:13 +00001759 int orderByConsumed; /* True if output is already ordered */
1760 double estimatedCost; /* Estimated cost of using this index */
drhe09daa92006-06-10 13:29:31 +00001761};
drh9eff6162006-06-12 21:59:13 +00001762#define SQLITE_INDEX_CONSTRAINT_EQ 2
1763#define SQLITE_INDEX_CONSTRAINT_GT 4
1764#define SQLITE_INDEX_CONSTRAINT_LE 8
1765#define SQLITE_INDEX_CONSTRAINT_LT 16
1766#define SQLITE_INDEX_CONSTRAINT_GE 32
1767#define SQLITE_INDEX_CONSTRAINT_MATCH 64
1768
1769/*
1770** This routine is used to register a new module name with an SQLite
1771** connection. Module names must be registered before creating new
1772** virtual tables on the module, or before using preexisting virtual
1773** tables of the module.
1774*/
drhb9bb7c12006-06-11 23:41:55 +00001775int sqlite3_create_module(
drh9eff6162006-06-12 21:59:13 +00001776 sqlite3 *db, /* SQLite connection to register module with */
1777 const char *zName, /* Name of the module */
danielk1977d1ab1ba2006-06-15 04:28:13 +00001778 const sqlite3_module *, /* Methods for the module */
1779 void * /* Client data for xCreate/xConnect */
drhb9bb7c12006-06-11 23:41:55 +00001780);
drhe09daa92006-06-10 13:29:31 +00001781
drh9eff6162006-06-12 21:59:13 +00001782/*
1783** Every module implementation uses a subclass of the following structure
1784** to describe a particular instance of the module. Each subclass will
1785** be taylored to the specific needs of the module implementation. The
1786** purpose of this superclass is to define certain fields that are common
1787** to all module implementations.
drhfe1368e2006-09-10 17:08:29 +00001788**
1789** Virtual tables methods can set an error message by assigning a
1790** string obtained from sqlite3_mprintf() to zErrMsg. The method should
1791** take care that any prior string is freed by a call to sqlite3_free()
1792** prior to assigning a new string to zErrMsg. After the error message
1793** is delivered up to the client application, the string will be automatically
1794** freed by sqlite3_free() and the zErrMsg field will be zeroed. Note
1795** that sqlite3_mprintf() and sqlite3_free() are used on the zErrMsg field
1796** since virtual tables are commonly implemented in loadable extensions which
1797** do not have access to sqlite3MPrintf() or sqlite3Free().
drh9eff6162006-06-12 21:59:13 +00001798*/
1799struct sqlite3_vtab {
drha967e882006-06-13 01:04:52 +00001800 const sqlite3_module *pModule; /* The module for this virtual table */
danielk1977be718892006-06-23 08:05:19 +00001801 int nRef; /* Used internally */
drh4ca8aac2006-09-10 17:31:58 +00001802 char *zErrMsg; /* Error message from sqlite3_mprintf() */
drh9eff6162006-06-12 21:59:13 +00001803 /* Virtual table implementations will typically add additional fields */
1804};
1805
1806/* Every module implementation uses a subclass of the following structure
1807** to describe cursors that point into the virtual table and are used
1808** to loop through the virtual table. Cursors are created using the
1809** xOpen method of the module. Each module implementation will define
1810** the content of a cursor structure to suit its own needs.
1811**
1812** This superclass exists in order to define fields of the cursor that
1813** are common to all implementations.
1814*/
1815struct sqlite3_vtab_cursor {
1816 sqlite3_vtab *pVtab; /* Virtual table of this cursor */
1817 /* Virtual table implementations will typically add additional fields */
1818};
1819
1820/*
1821** The xCreate and xConnect methods of a module use the following API
1822** to declare the format (the names and datatypes of the columns) of
1823** the virtual tables they implement.
1824*/
danielk19777e6ebfb2006-06-12 11:24:37 +00001825int sqlite3_declare_vtab(sqlite3*, const char *zCreateTable);
drhe09daa92006-06-10 13:29:31 +00001826
1827/*
drhb7481e72006-09-16 21:45:14 +00001828** Virtual tables can provide alternative implementations of functions
1829** using the xFindFunction method. But global versions of those functions
1830** must exist in order to be overloaded.
1831**
1832** This API makes sure a global version of a function with a particular
1833** name and number of parameters exists. If no such function exists
1834** before this API is called, a new function is created. The implementation
1835** of the new function always causes an exception to be thrown. So
1836** the new function is not good for anything by itself. Its only
1837** purpose is to be a place-holder function that can be overloaded
1838** by virtual tables.
1839**
1840** This API should be considered part of the virtual table interface,
1841** which is experimental and subject to change.
1842*/
1843int sqlite3_overload_function(sqlite3*, const char *zFuncName, int nArg);
1844
1845/*
drh9eff6162006-06-12 21:59:13 +00001846** The interface to the virtual-table mechanism defined above (back up
1847** to a comment remarkably similar to this one) is currently considered
1848** to be experimental. The interface might change in incompatible ways.
1849** If this is a problem for you, do not use the interface at this time.
1850**
1851** When the virtual-table mechanism stablizes, we will declare the
1852** interface fixed, support it indefinitely, and remove this comment.
1853**
1854****** EXPERIMENTAL - subject to change without notice **************
1855*/
1856
1857/*
drhb37df7b2005-10-13 02:09:49 +00001858** Undo the hack that converts floating point types to integer for
1859** builds on processors without floating point support.
1860*/
1861#ifdef SQLITE_OMIT_FLOATING_POINT
1862# undef double
1863#endif
1864
drh382c0242001-10-06 16:33:02 +00001865#ifdef __cplusplus
1866} /* End of the 'extern "C"' block */
1867#endif
danielk19774adee202004-05-08 08:23:19 +00001868#endif