blob: 6f8712145e619ab187c4356083a1070d359fed49 [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**
danielk1977348bb5d2003-10-18 09:37:26 +000015** @(#) $Id: sqlite.h.in,v 1.53 2003/10/18 09:37:26 danielk1977 Exp $
drh75897232000-05-29 14:26:00 +000016*/
17#ifndef _SQLITE_H_
18#define _SQLITE_H_
drha18c5682000-10-08 22:20:57 +000019#include <stdarg.h> /* Needed for the definition of va_list */
drh75897232000-05-29 14:26:00 +000020
21/*
drh382c0242001-10-06 16:33:02 +000022** Make sure we can call this stuff from C++.
23*/
24#ifdef __cplusplus
25extern "C" {
26#endif
27
28/*
drhb86ccfb2003-01-28 23:13:10 +000029** The version of the SQLite library.
30*/
31#define SQLITE_VERSION "--VERS--"
32
33/*
drhb217a572000-08-22 13:40:18 +000034** The version string is also compiled into the library so that a program
35** can check to make sure that the lib*.a file and the *.h file are from
36** the same version.
37*/
38extern const char sqlite_version[];
drh303aaa72000-08-17 10:22:34 +000039
40/*
drh297ecf12001-04-05 15:57:13 +000041** The SQLITE_UTF8 macro is defined if the library expects to see
42** UTF-8 encoded data. The SQLITE_ISO8859 macro is defined if the
43** iso8859 encoded should be used.
44*/
45#define SQLITE_--ENCODING-- 1
46
47/*
48** The following constant holds one of two strings, "UTF-8" or "iso8859",
49** depending on which character encoding the SQLite library expects to
50** see. The character encoding makes a difference for the LIKE and GLOB
51** operators and for the LENGTH() and SUBSTR() functions.
52*/
drhfbc3eab2001-04-06 16:13:42 +000053extern const char sqlite_encoding[];
drh297ecf12001-04-05 15:57:13 +000054
55/*
drh75897232000-05-29 14:26:00 +000056** Each open sqlite database is represented by an instance of the
57** following opaque structure.
58*/
59typedef struct sqlite sqlite;
60
61/*
62** A function to open a new sqlite database.
63**
64** If the database does not exist and mode indicates write
65** permission, then a new database is created. If the database
66** does not exist and mode does not indicate write permission,
67** then the open fails, an error message generated (if errmsg!=0)
68** and the function returns 0.
69**
70** If mode does not indicates user write permission, then the
71** database is opened read-only.
72**
73** The Truth: As currently implemented, all databases are opened
74** for writing all the time. Maybe someday we will provide the
75** ability to open a database readonly. The mode parameters is
drhb86ccfb2003-01-28 23:13:10 +000076** provided in anticipation of that enhancement.
drh75897232000-05-29 14:26:00 +000077*/
78sqlite *sqlite_open(const char *filename, int mode, char **errmsg);
79
80/*
81** A function to close the database.
82**
83** Call this function with a pointer to a structure that was previously
84** returned from sqlite_open() and the corresponding database will by closed.
85*/
86void sqlite_close(sqlite *);
87
88/*
89** The type for a callback function.
90*/
91typedef int (*sqlite_callback)(void*,int,char**, char**);
92
93/*
94** A function to executes one or more statements of SQL.
95**
96** If one or more of the SQL statements are queries, then
97** the callback function specified by the 3rd parameter is
98** invoked once for each row of the query result. This callback
99** should normally return 0. If the callback returns a non-zero
100** value then the query is aborted, all subsequent SQL statements
drh58b95762000-06-02 01:17:37 +0000101** are skipped and the sqlite_exec() function returns the SQLITE_ABORT.
drh75897232000-05-29 14:26:00 +0000102**
103** The 4th parameter is an arbitrary pointer that is passed
104** to the callback function as its first parameter.
105**
106** The 2nd parameter to the callback function is the number of
drhb19a2bc2001-09-16 00:13:26 +0000107** columns in the query result. The 3rd parameter to the callback
108** is an array of strings holding the values for each column.
109** The 4th parameter to the callback is an array of strings holding
110** the names of each column.
drh75897232000-05-29 14:26:00 +0000111**
112** The callback function may be NULL, even for queries. A NULL
113** callback is not an error. It just means that no callback
114** will be invoked.
115**
116** If an error occurs while parsing or evaluating the SQL (but
117** not while executing the callback) then an appropriate error
118** message is written into memory obtained from malloc() and
drhb19a2bc2001-09-16 00:13:26 +0000119** *errmsg is made to point to that message. The calling function
120** is responsible for freeing the memory that holds the error
drhb86ccfb2003-01-28 23:13:10 +0000121** message. Use sqlite_freemem() for this. If errmsg==NULL,
122** then no error message is ever written.
drhb19a2bc2001-09-16 00:13:26 +0000123**
124** The return value is is SQLITE_OK if there are no errors and
125** some other return code if there is an error. The particular
126** return value depends on the type of error.
drh58b95762000-06-02 01:17:37 +0000127**
128** If the query could not be executed because a database file is
drh2dfbbca2000-07-28 14:32:48 +0000129** locked or busy, then this function returns SQLITE_BUSY. (This
130** behavior can be modified somewhat using the sqlite_busy_handler()
drhb19a2bc2001-09-16 00:13:26 +0000131** and sqlite_busy_timeout() functions below.)
drh75897232000-05-29 14:26:00 +0000132*/
133int sqlite_exec(
134 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000135 const char *sql, /* SQL to be executed */
drh75897232000-05-29 14:26:00 +0000136 sqlite_callback, /* Callback function */
137 void *, /* 1st argument to callback function */
138 char **errmsg /* Error msg written here */
139);
140
drh58b95762000-06-02 01:17:37 +0000141/*
drhb86ccfb2003-01-28 23:13:10 +0000142** Return values for sqlite_exec() and sqlite_step()
drh58b95762000-06-02 01:17:37 +0000143*/
drh717e6402001-09-27 03:22:32 +0000144#define SQLITE_OK 0 /* Successful result */
145#define SQLITE_ERROR 1 /* SQL error or missing database */
146#define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */
147#define SQLITE_PERM 3 /* Access permission denied */
148#define SQLITE_ABORT 4 /* Callback routine requested an abort */
149#define SQLITE_BUSY 5 /* The database file is locked */
150#define SQLITE_LOCKED 6 /* A table in the database is locked */
151#define SQLITE_NOMEM 7 /* A malloc() failed */
152#define SQLITE_READONLY 8 /* Attempt to write a readonly database */
153#define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite_interrupt() */
154#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */
155#define SQLITE_CORRUPT 11 /* The database disk image is malformed */
156#define SQLITE_NOTFOUND 12 /* (Internal Only) Table or record not found */
157#define SQLITE_FULL 13 /* Insertion failed because database is full */
158#define SQLITE_CANTOPEN 14 /* Unable to open the database file */
159#define SQLITE_PROTOCOL 15 /* Database lock protocol error */
160#define SQLITE_EMPTY 16 /* (Internal Only) Database table is empty */
161#define SQLITE_SCHEMA 17 /* The database schema changed */
162#define SQLITE_TOOBIG 18 /* Too much data for one row of a table */
163#define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */
drh8aff1012001-12-22 14:49:24 +0000164#define SQLITE_MISMATCH 20 /* Data type mismatch */
drh247be432002-05-10 05:44:55 +0000165#define SQLITE_MISUSE 21 /* Library used incorrectly */
drh8766c342002-11-09 00:33:15 +0000166#define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
drhed6c8672003-01-12 18:02:16 +0000167#define SQLITE_AUTH 23 /* Authorization denied */
drh1c2d8412003-03-31 00:30:47 +0000168#define SQLITE_FORMAT 24 /* Auxiliary database format error */
drh7c972de2003-09-06 22:18:07 +0000169#define SQLITE_RANGE 25 /* 2nd parameter to sqlite_bind out of range */
drhb86ccfb2003-01-28 23:13:10 +0000170#define SQLITE_ROW 100 /* sqlite_step() has another row ready */
171#define SQLITE_DONE 101 /* sqlite_step() has finished executing */
drh717e6402001-09-27 03:22:32 +0000172
drhaf9ff332002-01-16 21:00:27 +0000173/*
174** Each entry in an SQLite table has a unique integer key. (The key is
175** the value of the INTEGER PRIMARY KEY column if there is such a column,
176** otherwise the key is generated at random. The unique key is always
177** available as the ROWID, OID, or _ROWID_ column.) The following routine
178** returns the integer key of the most recent insert in the database.
179**
180** This function is similar to the mysql_insert_id() function from MySQL.
181*/
182int sqlite_last_insert_rowid(sqlite*);
183
drhc8d30ac2002-04-12 10:08:59 +0000184/*
185** This function returns the number of database rows that were changed
186** (or inserted or deleted) by the most recent called sqlite_exec().
187**
188** All changes are counted, even if they were later undone by a
189** ROLLBACK or ABORT. Except, changes associated with creating and
190** dropping tables are not counted.
191**
192** If a callback invokes sqlite_exec() recursively, then the changes
193** in the inner, recursive call are counted together with the changes
194** in the outer call.
195**
196** SQLite implements the command "DELETE FROM table" without a WHERE clause
197** by dropping and recreating the table. (This is much faster than going
198** through and deleting individual elements form the table.) Because of
199** this optimization, the change count for "DELETE FROM table" will be
200** zero regardless of the number of elements that were originally in the
201** table. To get an accurate count of the number of rows deleted, use
202** "DELETE FROM table WHERE 1" instead.
203*/
204int sqlite_changes(sqlite*);
205
drh717e6402001-09-27 03:22:32 +0000206/* If the parameter to this routine is one of the return value constants
207** defined above, then this routine returns a constant text string which
208** descripts (in English) the meaning of the return value.
209*/
drh6d4abfb2001-10-22 02:58:08 +0000210const char *sqlite_error_string(int);
211#define sqliteErrStr sqlite_error_string /* Legacy. Do not use in new code. */
drh4c504392000-10-16 22:06:40 +0000212
213/* This function causes any pending database operation to abort and
214** return at its earliest opportunity. This routine is typically
drh66b89c82000-11-28 20:47:17 +0000215** called in response to a user action such as pressing "Cancel"
drh4c504392000-10-16 22:06:40 +0000216** or Ctrl-C where the user wants a long query operation to halt
217** immediately.
218*/
219void sqlite_interrupt(sqlite*);
220
drheec553b2000-06-02 01:51:20 +0000221
drh75897232000-05-29 14:26:00 +0000222/* This function returns true if the given input string comprises
223** one or more complete SQL statements.
224**
225** The algorithm is simple. If the last token other than spaces
226** and comments is a semicolon, then return true. otherwise return
227** false.
228*/
229int sqlite_complete(const char *sql);
230
drh2dfbbca2000-07-28 14:32:48 +0000231/*
232** This routine identifies a callback function that is invoked
233** whenever an attempt is made to open a database table that is
234** currently locked by another process or thread. If the busy callback
235** is NULL, then sqlite_exec() returns SQLITE_BUSY immediately if
236** it finds a locked table. If the busy callback is not NULL, then
237** sqlite_exec() invokes the callback with three arguments. The
238** second argument is the name of the locked table and the third
239** argument is the number of times the table has been busy. If the
240** busy callback returns 0, then sqlite_exec() immediately returns
241** SQLITE_BUSY. If the callback returns non-zero, then sqlite_exec()
242** tries to open the table again and the cycle repeats.
243**
244** The default busy callback is NULL.
245**
246** Sqlite is re-entrant, so the busy handler may start a new query.
247** (It is not clear why anyone would every want to do this, but it
248** is allowed, in theory.) But the busy handler may not close the
249** database. Closing the database from a busy handler will delete
250** data structures out from under the executing query and will
251** probably result in a coredump.
252*/
253void sqlite_busy_handler(sqlite*, int(*)(void*,const char*,int), void*);
254
255/*
256** This routine sets a busy handler that sleeps for a while when a
257** table is locked. The handler will sleep multiple times until
258** at least "ms" milleseconds of sleeping have been done. After
259** "ms" milleseconds of sleeping, the handler returns 0 which
260** causes sqlite_exec() to return SQLITE_BUSY.
261**
262** Calling this routine with an argument less than or equal to zero
263** turns off all busy handlers.
264*/
265void sqlite_busy_timeout(sqlite*, int ms);
266
drhe3710332000-09-29 13:30:53 +0000267/*
268** This next routine is really just a wrapper around sqlite_exec().
269** Instead of invoking a user-supplied callback for each row of the
270** result, this routine remembers each row of the result in memory
271** obtained from malloc(), then returns all of the result after the
drha18c5682000-10-08 22:20:57 +0000272** query has finished.
273**
274** As an example, suppose the query result where this table:
275**
276** Name | Age
277** -----------------------
278** Alice | 43
279** Bob | 28
280** Cindy | 21
281**
282** If the 3rd argument were &azResult then after the function returns
drh98699b52000-10-09 12:57:00 +0000283** azResult will contain the following data:
drha18c5682000-10-08 22:20:57 +0000284**
285** azResult[0] = "Name";
286** azResult[1] = "Age";
287** azResult[2] = "Alice";
288** azResult[3] = "43";
289** azResult[4] = "Bob";
290** azResult[5] = "28";
291** azResult[6] = "Cindy";
292** azResult[7] = "21";
293**
294** Notice that there is an extra row of data containing the column
295** headers. But the *nrow return value is still 3. *ncolumn is
296** set to 2. In general, the number of values inserted into azResult
297** will be ((*nrow) + 1)*(*ncolumn).
298**
299** After the calling function has finished using the result, it should
300** pass the result data pointer to sqlite_free_table() in order to
301** release the memory that was malloc-ed. Because of the way the
302** malloc() happens, the calling function must not try to call
303** malloc() directly. Only sqlite_free_table() is able to release
304** the memory properly and safely.
drhe3710332000-09-29 13:30:53 +0000305**
306** The return value of this routine is the same as from sqlite_exec().
307*/
308int sqlite_get_table(
309 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000310 const char *sql, /* SQL to be executed */
drhe3710332000-09-29 13:30:53 +0000311 char ***resultp, /* Result written to a char *[] that this points to */
312 int *nrow, /* Number of result rows written here */
313 int *ncolumn, /* Number of result columns written here */
314 char **errmsg /* Error msg written here */
315);
316
317/*
318** Call this routine to free the memory that sqlite_get_table() allocated.
319*/
320void sqlite_free_table(char **result);
321
drha18c5682000-10-08 22:20:57 +0000322/*
323** The following routines are wrappers around sqlite_exec() and
drh98699b52000-10-09 12:57:00 +0000324** sqlite_get_table(). The only difference between the routines that
drha18c5682000-10-08 22:20:57 +0000325** follow and the originals is that the second argument to the
326** routines that follow is really a printf()-style format
327** string describing the SQL to be executed. Arguments to the format
328** string appear at the end of the argument list.
329**
330** All of the usual printf formatting options apply. In addition, there
331** is a "%q" option. %q works like %s in that it substitutes a null-terminated
drh66b89c82000-11-28 20:47:17 +0000332** string from the argument list. But %q also doubles every '\'' character.
drha18c5682000-10-08 22:20:57 +0000333** %q is designed for use inside a string literal. By doubling each '\''
drh66b89c82000-11-28 20:47:17 +0000334** character it escapes that character and allows it to be inserted into
drha18c5682000-10-08 22:20:57 +0000335** the string.
336**
337** For example, so some string variable contains text as follows:
338**
339** char *zText = "It's a happy day!";
340**
341** We can use this text in an SQL statement as follows:
342**
343** sqlite_exec_printf(db, "INSERT INTO table VALUES('%q')",
344** callback1, 0, 0, zText);
345**
346** Because the %q format string is used, the '\'' character in zText
347** is escaped and the SQL generated is as follows:
348**
349** INSERT INTO table1 VALUES('It''s a happy day!')
350**
351** This is correct. Had we used %s instead of %q, the generated SQL
352** would have looked like this:
353**
354** INSERT INTO table1 VALUES('It's a happy day!');
355**
356** This second example is an SQL syntax error. As a general rule you
357** should always use %q instead of %s when inserting text into a string
358** literal.
359*/
360int sqlite_exec_printf(
361 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000362 const char *sqlFormat, /* printf-style format string for the SQL */
drha18c5682000-10-08 22:20:57 +0000363 sqlite_callback, /* Callback function */
364 void *, /* 1st argument to callback function */
365 char **errmsg, /* Error msg written here */
366 ... /* Arguments to the format string. */
367);
368int sqlite_exec_vprintf(
369 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000370 const char *sqlFormat, /* printf-style format string for the SQL */
drha18c5682000-10-08 22:20:57 +0000371 sqlite_callback, /* Callback function */
372 void *, /* 1st argument to callback function */
373 char **errmsg, /* Error msg written here */
374 va_list ap /* Arguments to the format string. */
375);
376int sqlite_get_table_printf(
377 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000378 const char *sqlFormat, /* printf-style format string for the SQL */
drha18c5682000-10-08 22:20:57 +0000379 char ***resultp, /* Result written to a char *[] that this points to */
380 int *nrow, /* Number of result rows written here */
381 int *ncolumn, /* Number of result columns written here */
382 char **errmsg, /* Error msg written here */
383 ... /* Arguments to the format string */
384);
385int sqlite_get_table_vprintf(
386 sqlite*, /* An open database */
drh9f71c2e2001-11-03 23:57:09 +0000387 const char *sqlFormat, /* printf-style format string for the SQL */
drha18c5682000-10-08 22:20:57 +0000388 char ***resultp, /* Result written to a char *[] that this points to */
389 int *nrow, /* Number of result rows written here */
390 int *ncolumn, /* Number of result columns written here */
391 char **errmsg, /* Error msg written here */
392 va_list ap /* Arguments to the format string */
393);
drh62160e72002-07-30 17:20:40 +0000394char *sqlite_mprintf(const char*,...);
drhd36a4832003-06-06 15:44:00 +0000395char *sqlite_vmprintf(const char*, va_list);
drha18c5682000-10-08 22:20:57 +0000396
drh8e0a2f92002-02-23 23:45:45 +0000397/*
drh5191b7e2002-03-08 02:12:00 +0000398** Windows systems should call this routine to free memory that
399** is returned in the in the errmsg parameter of sqlite_open() when
400** SQLite is a DLL. For some reason, it does not work to call free()
401** directly.
402*/
403void sqlite_freemem(void *p);
404
405/*
406** Windows systems need functions to call to return the sqlite_version
407** and sqlite_encoding strings.
408*/
409const char *sqlite_libversion(void);
410const char *sqlite_libencoding(void);
411
412/*
drh1350b032002-02-27 19:00:20 +0000413** A pointer to the following structure is used to communicate with
414** the implementations of user-defined functions.
415*/
416typedef struct sqlite_func sqlite_func;
417
418/*
drh8e0a2f92002-02-23 23:45:45 +0000419** Use the following routines to create new user-defined functions. See
420** the documentation for details.
421*/
422int sqlite_create_function(
drh1350b032002-02-27 19:00:20 +0000423 sqlite*, /* Database where the new function is registered */
424 const char *zName, /* Name of the new function */
425 int nArg, /* Number of arguments. -1 means any number */
426 void (*xFunc)(sqlite_func*,int,const char**), /* C code to implement */
427 void *pUserData /* Available via the sqlite_user_data() call */
drh8e0a2f92002-02-23 23:45:45 +0000428);
429int sqlite_create_aggregate(
drh1350b032002-02-27 19:00:20 +0000430 sqlite*, /* Database where the new function is registered */
431 const char *zName, /* Name of the function */
432 int nArg, /* Number of arguments */
433 void (*xStep)(sqlite_func*,int,const char**), /* Called for each row */
434 void (*xFinalize)(sqlite_func*), /* Called once to get final result */
435 void *pUserData /* Available via the sqlite_user_data() call */
drh8e0a2f92002-02-23 23:45:45 +0000436);
437
438/*
drhc9b84a12002-06-20 11:36:48 +0000439** Use the following routine to define the datatype returned by a
440** user-defined function. The second argument can be one of the
441** constants SQLITE_NUMERIC, SQLITE_TEXT, or SQLITE_ARGS or it
442** can be an integer greater than or equal to zero. The datatype
443** will be numeric or text (the only two types supported) if the
444** argument is SQLITE_NUMERIC or SQLITE_TEXT. If the argument is
445** SQLITE_ARGS, then the datatype is numeric if any argument to the
446** function is numeric and is text otherwise. If the second argument
447** is an integer, then the datatype of the result is the same as the
448** parameter to the function that corresponds to that integer.
449*/
450int sqlite_function_type(
451 sqlite *db, /* The database there the function is registered */
452 const char *zName, /* Name of the function */
453 int datatype /* The datatype for this function */
454);
455#define SQLITE_NUMERIC (-1)
456#define SQLITE_TEXT (-2)
457#define SQLITE_ARGS (-3)
458
459/*
drh8e0a2f92002-02-23 23:45:45 +0000460** The user function implementations call one of the following four routines
461** in order to return their results. The first parameter to each of these
drhdd5baa92002-02-27 19:50:59 +0000462** routines is a copy of the first argument to xFunc() or xFinialize().
drh1350b032002-02-27 19:00:20 +0000463** The second parameter to these routines is the result to be returned.
464** A NULL can be passed as the second parameter to sqlite_set_result_string()
465** in order to return a NULL result.
drh8e0a2f92002-02-23 23:45:45 +0000466**
467** The 3rd argument to _string and _error is the number of characters to
468** take from the string. If this argument is negative, then all characters
469** up to and including the first '\000' are used.
drh1350b032002-02-27 19:00:20 +0000470**
471** The sqlite_set_result_string() function allocates a buffer to hold the
472** result and returns a pointer to this buffer. The calling routine
473** (that is, the implmentation of a user function) can alter the content
474** of this buffer if desired.
drh8e0a2f92002-02-23 23:45:45 +0000475*/
drh1350b032002-02-27 19:00:20 +0000476char *sqlite_set_result_string(sqlite_func*,const char*,int);
477void sqlite_set_result_int(sqlite_func*,int);
478void sqlite_set_result_double(sqlite_func*,double);
479void sqlite_set_result_error(sqlite_func*,const char*,int);
480
481/*
482** The pUserData parameter to the sqlite_create_function() and
483** sqlite_create_aggregate() routines used to register user functions
484** is available to the implementation of the function using this
485** call.
486*/
487void *sqlite_user_data(sqlite_func*);
488
489/*
drhdd5baa92002-02-27 19:50:59 +0000490** Aggregate functions use the following routine to allocate
491** a structure for storing their state. The first time this routine
drh1350b032002-02-27 19:00:20 +0000492** is called for a particular aggregate, a new structure of size nBytes
493** is allocated, zeroed, and returned. On subsequent calls (for the
494** same aggregate instance) the same buffer is returned. The implementation
495** of the aggregate can use the returned buffer to accumulate data.
496**
497** The buffer allocated is freed automatically be SQLite.
498*/
499void *sqlite_aggregate_context(sqlite_func*, int nBytes);
500
501/*
drhdd5baa92002-02-27 19:50:59 +0000502** The next routine returns the number of calls to xStep for a particular
503** aggregate function instance. The current call to xStep counts so this
504** routine always returns at least 1.
drh1350b032002-02-27 19:00:20 +0000505*/
506int sqlite_aggregate_count(sqlite_func*);
drh8e0a2f92002-02-23 23:45:45 +0000507
drh411995d2002-06-25 19:31:18 +0000508/*
drhed6c8672003-01-12 18:02:16 +0000509** This routine registers a callback with the SQLite library. The
drhb86ccfb2003-01-28 23:13:10 +0000510** callback is invoked (at compile-time, not at run-time) for each
511** attempt to access a column of a table in the database. The callback
512** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire
513** SQL statement should be aborted with an error and SQLITE_IGNORE
514** if the column should be treated as a NULL value.
drhed6c8672003-01-12 18:02:16 +0000515*/
516int sqlite_set_authorizer(
517 sqlite*,
drhe22a3342003-04-22 20:30:37 +0000518 int (*xAuth)(void*,int,const char*,const char*,const char*,const char*),
drhe5f9c642003-01-13 23:27:31 +0000519 void *pUserData
drhed6c8672003-01-12 18:02:16 +0000520);
521
522/*
523** The second parameter to the access authorization function above will
drhe5f9c642003-01-13 23:27:31 +0000524** be one of the values below. These values signify what kind of operation
525** is to be authorized. The 3rd and 4th parameters to the authorization
526** function will be parameters or NULL depending on which of the following
drhe22a3342003-04-22 20:30:37 +0000527** codes is used as the second parameter. The 5th parameter is the name
528** of the database ("main", "temp", etc.) if applicable. The 6th parameter
drh5cf590c2003-04-24 01:45:04 +0000529** is the name of the inner-most trigger or view that is responsible for
530** the access attempt or NULL if this access attempt is directly from
531** input SQL code.
drhe5f9c642003-01-13 23:27:31 +0000532**
533** Arg-3 Arg-4
drhed6c8672003-01-12 18:02:16 +0000534*/
drh77ad4e42003-01-14 02:49:27 +0000535#define SQLITE_COPY 0 /* Table Name File Name */
drhe5f9c642003-01-13 23:27:31 +0000536#define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */
537#define SQLITE_CREATE_TABLE 2 /* Table Name NULL */
538#define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */
539#define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000540#define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000541#define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000542#define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000543#define SQLITE_CREATE_VIEW 8 /* View Name NULL */
544#define SQLITE_DELETE 9 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000545#define SQLITE_DROP_INDEX 10 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000546#define SQLITE_DROP_TABLE 11 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000547#define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000548#define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000549#define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000550#define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */
drh77ad4e42003-01-14 02:49:27 +0000551#define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */
drhe5f9c642003-01-13 23:27:31 +0000552#define SQLITE_DROP_VIEW 17 /* View Name NULL */
553#define SQLITE_INSERT 18 /* Table Name NULL */
554#define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */
555#define SQLITE_READ 20 /* Table Name Column Name */
556#define SQLITE_SELECT 21 /* NULL NULL */
557#define SQLITE_TRANSACTION 22 /* NULL NULL */
558#define SQLITE_UPDATE 23 /* Table Name Column Name */
drh81e293b2003-06-06 19:00:42 +0000559#define SQLITE_ATTACH 24 /* Filename NULL */
560#define SQLITE_DETACH 25 /* Database Name NULL */
561
drhed6c8672003-01-12 18:02:16 +0000562
563/*
564** The return value of the authorization function should be one of the
565** following constants:
566*/
567/* #define SQLITE_OK 0 // Allow access (This is actually defined above) */
568#define SQLITE_DENY 1 /* Abort the SQL statement with an error */
569#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
570
571/*
drhb86ccfb2003-01-28 23:13:10 +0000572** Register a function that is called at every invocation of sqlite_exec()
573** or sqlite_compile(). This function can be used (for example) to generate
574** a log file of all SQL executed against a database.
drh18de4822003-01-16 16:28:53 +0000575*/
576void *sqlite_trace(sqlite*, void(*xTrace)(void*,const char*), void*);
577
drhb86ccfb2003-01-28 23:13:10 +0000578/*** The Callback-Free API
579**
580** The following routines implement a new way to access SQLite that does not
581** involve the use of callbacks.
582**
583** An sqlite_vm is an opaque object that represents a single SQL statement
584** that is ready to be executed.
585*/
586typedef struct sqlite_vm sqlite_vm;
587
588/*
589** To execute an SQLite query without the use of callbacks, you first have
590** to compile the SQL using this routine. The 1st parameter "db" is a pointer
591** to an sqlite object obtained from sqlite_open(). The 2nd parameter
592** "zSql" is the text of the SQL to be compiled. The remaining parameters
593** are all outputs.
594**
595** *pzTail is made to point to the first character past the end of the first
596** SQL statement in zSql. This routine only compiles the first statement
597** in zSql, so *pzTail is left pointing to what remains uncompiled.
598**
599** *ppVm is left pointing to a "virtual machine" that can be used to execute
600** the compiled statement. Or if there is an error, *ppVm may be set to NULL.
drh326dce72003-01-29 14:06:07 +0000601** If the input text contained no SQL (if the input is and empty string or
602** a comment) then *ppVm is set to NULL.
drhb86ccfb2003-01-28 23:13:10 +0000603**
604** If any errors are detected during compilation, an error message is written
605** into space obtained from malloc() and *pzErrMsg is made to point to that
606** error message. The calling routine is responsible for freeing the text
607** of this message when it has finished with it. Use sqlite_freemem() to
608** free the message. pzErrMsg may be NULL in which case no error message
609** will be generated.
610**
611** On success, SQLITE_OK is returned. Otherwise and error code is returned.
612*/
613int sqlite_compile(
614 sqlite *db, /* The open database */
615 const char *zSql, /* SQL statement to be compiled */
616 const char **pzTail, /* OUT: uncompiled tail of zSql */
617 sqlite_vm **ppVm, /* OUT: the virtual machine to execute zSql */
618 char **pzErrmsg /* OUT: Error message. */
619);
620
621/*
622** After an SQL statement has been compiled, it is handed to this routine
623** to be executed. This routine executes the statement as far as it can
624** go then returns. The return value will be one of SQLITE_DONE,
625** SQLITE_ERROR, SQLITE_BUSY, SQLITE_ROW, or SQLITE_MISUSE.
626**
627** SQLITE_DONE means that the execute of the SQL statement is complete
628** an no errors have occurred. sqlite_step() should not be called again
629** for the same virtual machine. *pN is set to the number of columns in
630** the result set and *pazColName is set to an array of strings that
631** describe the column names and datatypes. The name of the i-th column
632** is (*pazColName)[i] and the datatype of the i-th column is
633** (*pazColName)[i+*pN]. *pazValue is set to NULL.
634**
635** SQLITE_ERROR means that the virtual machine encountered a run-time
636** error. sqlite_step() should not be called again for the same
637** virtual machine. *pN is set to 0 and *pazColName and *pazValue are set
638** to NULL. Use sqlite_finalize() to obtain the specific error code
639** and the error message text for the error.
640**
641** SQLITE_BUSY means that an attempt to open the database failed because
642** another thread or process is holding a lock. The calling routine
643** can try again to open the database by calling sqlite_step() again.
644** The return code will only be SQLITE_BUSY if no busy handler is registered
645** using the sqlite_busy_handler() or sqlite_busy_timeout() routines. If
646** a busy handler callback has been registered but returns 0, then this
647** routine will return SQLITE_ERROR and sqltie_finalize() will return
648** SQLITE_BUSY when it is called.
649**
650** SQLITE_ROW means that a single row of the result is now available.
651** The data is contained in *pazValue. The value of the i-th column is
652** (*azValue)[i]. *pN and *pazColName are set as described in SQLITE_DONE.
653** Invoke sqlite_step() again to advance to the next row.
654**
655** SQLITE_MISUSE is returned if sqlite_step() is called incorrectly.
656** For example, if you call sqlite_step() after the virtual machine
657** has halted (after a prior call to sqlite_step() has returned SQLITE_DONE)
658** or if you call sqlite_step() with an incorrectly initialized virtual
659** machine or a virtual machine that has been deleted or that is associated
660** with an sqlite structure that has been closed.
661*/
662int sqlite_step(
663 sqlite_vm *pVm, /* The virtual machine to execute */
664 int *pN, /* OUT: Number of columns in result */
665 const char ***pazValue, /* OUT: Column data */
666 const char ***pazColName /* OUT: Column names and datatypes */
667);
668
669/*
670** This routine is called to delete a virtual machine after it has finished
671** executing. The return value is the result code. SQLITE_OK is returned
672** if the statement executed successfully and some other value is returned if
673** there was any kind of error. If an error occurred and pzErrMsg is not
674** NULL, then an error message is written into memory obtained from malloc()
675** and *pzErrMsg is made to point to that error message. The calling routine
676** should use sqlite_freemem() to delete this message when it has finished
677** with it.
678**
679** This routine can be called at any point during the execution of the
680** virtual machine. If the virtual machine has not completed execution
681** when this routine is called, that is like encountering an error or
682** an interrupt. (See sqlite_interrupt().) Incomplete updates may be
683** rolled back and transactions cancelled, depending on the circumstances,
684** and the result code returned will be SQLITE_ABORT.
685*/
686int sqlite_finalize(sqlite_vm*, char **pzErrMsg);
687
danielk1977999af642003-07-22 09:24:43 +0000688/*
689** This routine deletes the virtual machine, writes any error message to
690** *pzErrMsg and returns an SQLite return code in the same way as the
691** sqlite_finalize() function.
692**
693** Additionally, if ppVm is not NULL, *ppVm is left pointing to a new virtual
694** machine loaded with the compiled version of the original query ready for
695** execution.
696**
697** If sqlite_reset() returns SQLITE_SCHEMA, then *ppVm is set to NULL.
698**
drh7c972de2003-09-06 22:18:07 +0000699******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
drh50457892003-09-06 01:10:47 +0000700*/
drh7c972de2003-09-06 22:18:07 +0000701int sqlite_reset(sqlite_vm*, char **pzErrMsg);
drh50457892003-09-06 01:10:47 +0000702
703/*
drh7c972de2003-09-06 22:18:07 +0000704** If the SQL that was handed to sqlite_compile contains variables that
705** are represeted in the SQL text by a question mark ('?'). This routine
706** is used to assign values to those variables.
707**
708** The first parameter is a virtual machine obtained from sqlite_compile().
709** The 2nd "idx" parameter determines which variable in the SQL statement
710** to bind the value to. The left most '?' is 1. The 3rd parameter is
711** the value to assign to that variable. The 4th parameter is the number
712** of bytes in the value, including the terminating \000 for strings.
713** Finally, the 5th "copy" parameter is TRUE if SQLite should make its
714** own private copy of this value, or false if the space that the 3rd
715** parameter points to will be unchanging and can be used directly by
716** SQLite.
717**
718** Unbound variables are treated as having a value of NULL. To explicitly
719** set a variable to NULL, call this routine with the 3rd parameter as a
720** NULL pointer.
721**
722** If the 4th "len" parameter is -1, then strlen() is used to find the
723** length.
drh50457892003-09-06 01:10:47 +0000724**
725** This routine can only be called immediately after sqlite_compile()
726** or sqlite_reset() and before any calls to sqlite_step().
727**
danielk1977999af642003-07-22 09:24:43 +0000728******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ******
729*/
drh7c972de2003-09-06 22:18:07 +0000730int sqlite_bind(sqlite_vm*, int idx, const char *value, int len, int copy);
danielk1977999af642003-07-22 09:24:43 +0000731
danielk1977348bb5d2003-10-18 09:37:26 +0000732/*
733** This routine configures a callback function - the progress callback - that
734** is invoked periodically during long running calls to sqlite_exec(),
735** sqlite_step() and sqlite_get_table(). An example use for this API is to keep
736** a GUI updated during a large query.
737**
738** The progress callback is invoked once for every N virtual machine opcodes,
739** where N is the second argument to this function. The progress callback
740** itself is identified by the third argument to this function. The fourth
741** argument to this function is a void pointer passed to the progress callback
742** function each time it is invoked.
743**
744** If a call to sqlite_exec(), sqlite_step() or sqlite_get_table() results
745** in less than N opcodes being executed, then the progress callback is not
746** invoked.
747**
748** Calling this routine overwrites any previously installed progress callback.
749** To remove the progress callback altogether, pass NULL as the third
750** argument to this function.
751**
752** If the progress callback returns a result other than 0, then the current
753** query is immediately terminated and any database changes rolled back. If the
754** query was part of a larger transaction, then the transaction is not rolled
755** back and remains active. The sqlite_exec() call returns SQLITE_ABORT.
756*/
757void sqlite_progress_handler(sqlite*, int, int(*)(void*), void*);
758
drh382c0242001-10-06 16:33:02 +0000759#ifdef __cplusplus
760} /* End of the 'extern "C"' block */
761#endif
762
drh75897232000-05-29 14:26:00 +0000763#endif /* _SQLITE_H_ */