drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 1 | /* |
drh | b19a2bc | 2001-09-16 00:13:26 +0000 | [diff] [blame] | 2 | ** 2001 September 15 |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 3 | ** |
drh | b19a2bc | 2001-09-16 00:13:26 +0000 | [diff] [blame] | 4 | ** The author disclaims copyright to this source code. In place of |
| 5 | ** a legal notice, here is a blessing: |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 6 | ** |
drh | b19a2bc | 2001-09-16 00:13:26 +0000 | [diff] [blame] | 7 | ** 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. |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 10 | ** |
| 11 | ************************************************************************* |
drh | b19a2bc | 2001-09-16 00:13:26 +0000 | [diff] [blame] | 12 | ** This header file defines the interface that the SQLite library |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 13 | ** presents to client programs. |
| 14 | ** |
drh | d89bd00 | 2005-01-22 03:03:54 +0000 | [diff] [blame^] | 15 | ** @(#) $Id: sqlite.h.in,v 1.128 2005/01/22 03:03:54 drh Exp $ |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 16 | */ |
drh | 12057d5 | 2004-09-06 17:34:12 +0000 | [diff] [blame] | 17 | #ifndef _SQLITE3_H_ |
| 18 | #define _SQLITE3_H_ |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 19 | #include <stdarg.h> /* Needed for the definition of va_list */ |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 20 | |
| 21 | /* |
drh | 382c024 | 2001-10-06 16:33:02 +0000 | [diff] [blame] | 22 | ** Make sure we can call this stuff from C++. |
| 23 | */ |
| 24 | #ifdef __cplusplus |
| 25 | extern "C" { |
| 26 | #endif |
| 27 | |
| 28 | /* |
drh | b86ccfb | 2003-01-28 23:13:10 +0000 | [diff] [blame] | 29 | ** The version of the SQLite library. |
| 30 | */ |
drh | 1e284f4 | 2004-10-06 15:52:01 +0000 | [diff] [blame] | 31 | #ifdef SQLITE_VERSION |
| 32 | # undef SQLITE_VERSION |
| 33 | #else |
| 34 | # define SQLITE_VERSION "--VERS--" |
| 35 | #endif |
drh | b86ccfb | 2003-01-28 23:13:10 +0000 | [diff] [blame] | 36 | |
| 37 | /* |
drh | b217a57 | 2000-08-22 13:40:18 +0000 | [diff] [blame] | 38 | ** The version string is also compiled into the library so that a program |
| 39 | ** can check to make sure that the lib*.a file and the *.h file are from |
drh | 6f3a3ef | 2004-08-28 18:21:21 +0000 | [diff] [blame] | 40 | ** the same version. The sqlite3_libversion() function returns a pointer |
| 41 | ** to the sqlite3_version variable - useful in DLLs which cannot access |
| 42 | ** global variables. |
drh | b217a57 | 2000-08-22 13:40:18 +0000 | [diff] [blame] | 43 | */ |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 44 | extern const char sqlite3_version[]; |
drh | a3f70cb | 2004-09-30 14:24:50 +0000 | [diff] [blame] | 45 | const char *sqlite3_libversion(void); |
drh | 303aaa7 | 2000-08-17 10:22:34 +0000 | [diff] [blame] | 46 | |
| 47 | /* |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 48 | ** Each open sqlite database is represented by an instance of the |
| 49 | ** following opaque structure. |
| 50 | */ |
drh | 9bb575f | 2004-09-06 17:24:11 +0000 | [diff] [blame] | 51 | typedef struct sqlite3 sqlite3; |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 52 | |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 53 | |
| 54 | /* |
drh | efad999 | 2004-06-22 12:13:55 +0000 | [diff] [blame] | 55 | ** Some compilers do not support the "long long" datatype. So we have |
| 56 | ** to do a typedef that for 64-bit integers that depends on what compiler |
| 57 | ** is being used. |
| 58 | */ |
| 59 | #if defined(_MSC_VER) || defined(__BORLANDC__) |
| 60 | typedef __int64 sqlite_int64; |
drh | 1211de3 | 2004-07-26 12:24:22 +0000 | [diff] [blame] | 61 | typedef unsigned __int64 sqlite_uint64; |
drh | efad999 | 2004-06-22 12:13:55 +0000 | [diff] [blame] | 62 | #else |
| 63 | typedef long long int sqlite_int64; |
drh | 1211de3 | 2004-07-26 12:24:22 +0000 | [diff] [blame] | 64 | typedef unsigned long long int sqlite_uint64; |
drh | efad999 | 2004-06-22 12:13:55 +0000 | [diff] [blame] | 65 | #endif |
| 66 | |
| 67 | |
| 68 | /* |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 69 | ** A function to close the database. |
| 70 | ** |
| 71 | ** Call this function with a pointer to a structure that was previously |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 72 | ** returned from sqlite3_open() and the corresponding database will by closed. |
danielk1977 | 96d81f9 | 2004-06-19 03:33:57 +0000 | [diff] [blame] | 73 | ** |
| 74 | ** All SQL statements prepared using sqlite3_prepare() or |
| 75 | ** sqlite3_prepare16() must be deallocated using sqlite3_finalize() before |
| 76 | ** this routine is called. Otherwise, SQLITE_BUSY is returned and the |
| 77 | ** database connection remains open. |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 78 | */ |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 79 | int sqlite3_close(sqlite3 *); |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 80 | |
| 81 | /* |
| 82 | ** The type for a callback function. |
| 83 | */ |
drh | 12057d5 | 2004-09-06 17:34:12 +0000 | [diff] [blame] | 84 | typedef int (*sqlite3_callback)(void*,int,char**, char**); |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 85 | |
| 86 | /* |
| 87 | ** A function to executes one or more statements of SQL. |
| 88 | ** |
| 89 | ** If one or more of the SQL statements are queries, then |
| 90 | ** the callback function specified by the 3rd parameter is |
| 91 | ** invoked once for each row of the query result. This callback |
| 92 | ** should normally return 0. If the callback returns a non-zero |
| 93 | ** value then the query is aborted, all subsequent SQL statements |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 94 | ** are skipped and the sqlite3_exec() function returns the SQLITE_ABORT. |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 95 | ** |
| 96 | ** The 4th parameter is an arbitrary pointer that is passed |
| 97 | ** to the callback function as its first parameter. |
| 98 | ** |
| 99 | ** The 2nd parameter to the callback function is the number of |
drh | b19a2bc | 2001-09-16 00:13:26 +0000 | [diff] [blame] | 100 | ** columns in the query result. The 3rd parameter to the callback |
| 101 | ** is an array of strings holding the values for each column. |
| 102 | ** The 4th parameter to the callback is an array of strings holding |
| 103 | ** the names of each column. |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 104 | ** |
| 105 | ** The callback function may be NULL, even for queries. A NULL |
| 106 | ** callback is not an error. It just means that no callback |
| 107 | ** will be invoked. |
| 108 | ** |
| 109 | ** If an error occurs while parsing or evaluating the SQL (but |
| 110 | ** not while executing the callback) then an appropriate error |
| 111 | ** message is written into memory obtained from malloc() and |
drh | b19a2bc | 2001-09-16 00:13:26 +0000 | [diff] [blame] | 112 | ** *errmsg is made to point to that message. The calling function |
| 113 | ** is responsible for freeing the memory that holds the error |
drh | 3f4fedb | 2004-05-31 19:34:33 +0000 | [diff] [blame] | 114 | ** message. Use sqlite3_free() for this. If errmsg==NULL, |
drh | b86ccfb | 2003-01-28 23:13:10 +0000 | [diff] [blame] | 115 | ** then no error message is ever written. |
drh | b19a2bc | 2001-09-16 00:13:26 +0000 | [diff] [blame] | 116 | ** |
| 117 | ** The return value is is SQLITE_OK if there are no errors and |
| 118 | ** some other return code if there is an error. The particular |
| 119 | ** return value depends on the type of error. |
drh | 58b9576 | 2000-06-02 01:17:37 +0000 | [diff] [blame] | 120 | ** |
| 121 | ** If the query could not be executed because a database file is |
drh | 2dfbbca | 2000-07-28 14:32:48 +0000 | [diff] [blame] | 122 | ** locked or busy, then this function returns SQLITE_BUSY. (This |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 123 | ** behavior can be modified somewhat using the sqlite3_busy_handler() |
| 124 | ** and sqlite3_busy_timeout() functions below.) |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 125 | */ |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 126 | int sqlite3_exec( |
drh | 12057d5 | 2004-09-06 17:34:12 +0000 | [diff] [blame] | 127 | sqlite3*, /* An open database */ |
drh | 9f71c2e | 2001-11-03 23:57:09 +0000 | [diff] [blame] | 128 | const char *sql, /* SQL to be executed */ |
drh | 12057d5 | 2004-09-06 17:34:12 +0000 | [diff] [blame] | 129 | sqlite3_callback, /* Callback function */ |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 130 | void *, /* 1st argument to callback function */ |
| 131 | char **errmsg /* Error msg written here */ |
| 132 | ); |
| 133 | |
drh | 58b9576 | 2000-06-02 01:17:37 +0000 | [diff] [blame] | 134 | /* |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 135 | ** Return values for sqlite3_exec() and sqlite3_step() |
drh | 58b9576 | 2000-06-02 01:17:37 +0000 | [diff] [blame] | 136 | */ |
drh | 717e640 | 2001-09-27 03:22:32 +0000 | [diff] [blame] | 137 | #define SQLITE_OK 0 /* Successful result */ |
| 138 | #define SQLITE_ERROR 1 /* SQL error or missing database */ |
| 139 | #define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */ |
| 140 | #define SQLITE_PERM 3 /* Access permission denied */ |
| 141 | #define SQLITE_ABORT 4 /* Callback routine requested an abort */ |
| 142 | #define SQLITE_BUSY 5 /* The database file is locked */ |
| 143 | #define SQLITE_LOCKED 6 /* A table in the database is locked */ |
| 144 | #define SQLITE_NOMEM 7 /* A malloc() failed */ |
| 145 | #define SQLITE_READONLY 8 /* Attempt to write a readonly database */ |
drh | 24cd67e | 2004-05-10 16:18:47 +0000 | [diff] [blame] | 146 | #define SQLITE_INTERRUPT 9 /* Operation terminated by sqlite3_interrupt()*/ |
drh | 717e640 | 2001-09-27 03:22:32 +0000 | [diff] [blame] | 147 | #define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */ |
| 148 | #define SQLITE_CORRUPT 11 /* The database disk image is malformed */ |
| 149 | #define SQLITE_NOTFOUND 12 /* (Internal Only) Table or record not found */ |
| 150 | #define SQLITE_FULL 13 /* Insertion failed because database is full */ |
| 151 | #define SQLITE_CANTOPEN 14 /* Unable to open the database file */ |
| 152 | #define SQLITE_PROTOCOL 15 /* Database lock protocol error */ |
drh | 24cd67e | 2004-05-10 16:18:47 +0000 | [diff] [blame] | 153 | #define SQLITE_EMPTY 16 /* Database is empty */ |
drh | 717e640 | 2001-09-27 03:22:32 +0000 | [diff] [blame] | 154 | #define SQLITE_SCHEMA 17 /* The database schema changed */ |
| 155 | #define SQLITE_TOOBIG 18 /* Too much data for one row of a table */ |
| 156 | #define SQLITE_CONSTRAINT 19 /* Abort due to contraint violation */ |
drh | 8aff101 | 2001-12-22 14:49:24 +0000 | [diff] [blame] | 157 | #define SQLITE_MISMATCH 20 /* Data type mismatch */ |
drh | 247be43 | 2002-05-10 05:44:55 +0000 | [diff] [blame] | 158 | #define SQLITE_MISUSE 21 /* Library used incorrectly */ |
drh | 8766c34 | 2002-11-09 00:33:15 +0000 | [diff] [blame] | 159 | #define SQLITE_NOLFS 22 /* Uses OS features not supported on host */ |
drh | ed6c867 | 2003-01-12 18:02:16 +0000 | [diff] [blame] | 160 | #define SQLITE_AUTH 23 /* Authorization denied */ |
drh | 1c2d841 | 2003-03-31 00:30:47 +0000 | [diff] [blame] | 161 | #define SQLITE_FORMAT 24 /* Auxiliary database format error */ |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 162 | #define SQLITE_RANGE 25 /* 2nd parameter to sqlite3_bind out of range */ |
drh | c602f9a | 2004-02-12 19:01:04 +0000 | [diff] [blame] | 163 | #define SQLITE_NOTADB 26 /* File opened that is not a database file */ |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 164 | #define SQLITE_ROW 100 /* sqlite3_step() has another row ready */ |
| 165 | #define SQLITE_DONE 101 /* sqlite3_step() has finished executing */ |
drh | 717e640 | 2001-09-27 03:22:32 +0000 | [diff] [blame] | 166 | |
drh | af9ff33 | 2002-01-16 21:00:27 +0000 | [diff] [blame] | 167 | /* |
| 168 | ** Each entry in an SQLite table has a unique integer key. (The key is |
| 169 | ** the value of the INTEGER PRIMARY KEY column if there is such a column, |
| 170 | ** otherwise the key is generated at random. The unique key is always |
| 171 | ** available as the ROWID, OID, or _ROWID_ column.) The following routine |
| 172 | ** returns the integer key of the most recent insert in the database. |
| 173 | ** |
| 174 | ** This function is similar to the mysql_insert_id() function from MySQL. |
| 175 | */ |
drh | efad999 | 2004-06-22 12:13:55 +0000 | [diff] [blame] | 176 | sqlite_int64 sqlite3_last_insert_rowid(sqlite3*); |
drh | af9ff33 | 2002-01-16 21:00:27 +0000 | [diff] [blame] | 177 | |
drh | c8d30ac | 2002-04-12 10:08:59 +0000 | [diff] [blame] | 178 | /* |
| 179 | ** This function returns the number of database rows that were changed |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 180 | ** (or inserted or deleted) by the most recent called sqlite3_exec(). |
drh | c8d30ac | 2002-04-12 10:08:59 +0000 | [diff] [blame] | 181 | ** |
| 182 | ** All changes are counted, even if they were later undone by a |
| 183 | ** ROLLBACK or ABORT. Except, changes associated with creating and |
| 184 | ** dropping tables are not counted. |
| 185 | ** |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 186 | ** If a callback invokes sqlite3_exec() recursively, then the changes |
drh | c8d30ac | 2002-04-12 10:08:59 +0000 | [diff] [blame] | 187 | ** in the inner, recursive call are counted together with the changes |
| 188 | ** in the outer call. |
| 189 | ** |
| 190 | ** SQLite implements the command "DELETE FROM table" without a WHERE clause |
| 191 | ** by dropping and recreating the table. (This is much faster than going |
| 192 | ** through and deleting individual elements form the table.) Because of |
| 193 | ** this optimization, the change count for "DELETE FROM table" will be |
| 194 | ** zero regardless of the number of elements that were originally in the |
| 195 | ** table. To get an accurate count of the number of rows deleted, use |
| 196 | ** "DELETE FROM table WHERE 1" instead. |
| 197 | */ |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 198 | int sqlite3_changes(sqlite3*); |
drh | c8d30ac | 2002-04-12 10:08:59 +0000 | [diff] [blame] | 199 | |
rdc | f146a77 | 2004-02-25 22:51:06 +0000 | [diff] [blame] | 200 | /* |
danielk1977 | b28af71 | 2004-06-21 06:50:26 +0000 | [diff] [blame] | 201 | ** This function returns the number of database rows that have been |
| 202 | ** modified by INSERT, UPDATE or DELETE statements since the database handle |
| 203 | ** was opened. This includes UPDATE, INSERT and DELETE statements executed |
| 204 | ** as part of trigger programs. All changes are counted as soon as the |
| 205 | ** statement that makes them is completed (when the statement handle is |
| 206 | ** passed to sqlite3_reset() or sqlite_finalise()). |
rdc | f146a77 | 2004-02-25 22:51:06 +0000 | [diff] [blame] | 207 | ** |
| 208 | ** SQLite implements the command "DELETE FROM table" without a WHERE clause |
| 209 | ** by dropping and recreating the table. (This is much faster than going |
| 210 | ** through and deleting individual elements form the table.) Because of |
| 211 | ** this optimization, the change count for "DELETE FROM table" will be |
| 212 | ** zero regardless of the number of elements that were originally in the |
| 213 | ** table. To get an accurate count of the number of rows deleted, use |
| 214 | ** "DELETE FROM table WHERE 1" instead. |
rdc | f146a77 | 2004-02-25 22:51:06 +0000 | [diff] [blame] | 215 | */ |
danielk1977 | b28af71 | 2004-06-21 06:50:26 +0000 | [diff] [blame] | 216 | int sqlite3_total_changes(sqlite3*); |
| 217 | |
drh | 4c50439 | 2000-10-16 22:06:40 +0000 | [diff] [blame] | 218 | /* This function causes any pending database operation to abort and |
| 219 | ** return at its earliest opportunity. This routine is typically |
drh | 66b89c8 | 2000-11-28 20:47:17 +0000 | [diff] [blame] | 220 | ** called in response to a user action such as pressing "Cancel" |
drh | 4c50439 | 2000-10-16 22:06:40 +0000 | [diff] [blame] | 221 | ** or Ctrl-C where the user wants a long query operation to halt |
| 222 | ** immediately. |
| 223 | */ |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 224 | void sqlite3_interrupt(sqlite3*); |
drh | 4c50439 | 2000-10-16 22:06:40 +0000 | [diff] [blame] | 225 | |
drh | eec553b | 2000-06-02 01:51:20 +0000 | [diff] [blame] | 226 | |
danielk1977 | 61de0d1 | 2004-05-27 23:56:16 +0000 | [diff] [blame] | 227 | /* These functions return true if the given input string comprises |
| 228 | ** one or more complete SQL statements. For the sqlite3_complete() call, |
| 229 | ** the parameter must be a nul-terminated UTF-8 string. For |
| 230 | ** sqlite3_complete16(), a nul-terminated machine byte order UTF-16 string |
| 231 | ** is required. |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 232 | ** |
| 233 | ** The algorithm is simple. If the last token other than spaces |
| 234 | ** and comments is a semicolon, then return true. otherwise return |
| 235 | ** false. |
| 236 | */ |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 237 | int sqlite3_complete(const char *sql); |
danielk1977 | 61de0d1 | 2004-05-27 23:56:16 +0000 | [diff] [blame] | 238 | int sqlite3_complete16(const void *sql); |
drh | 7589723 | 2000-05-29 14:26:00 +0000 | [diff] [blame] | 239 | |
drh | 2dfbbca | 2000-07-28 14:32:48 +0000 | [diff] [blame] | 240 | /* |
| 241 | ** This routine identifies a callback function that is invoked |
| 242 | ** whenever an attempt is made to open a database table that is |
| 243 | ** currently locked by another process or thread. If the busy callback |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 244 | ** is NULL, then sqlite3_exec() returns SQLITE_BUSY immediately if |
drh | 2dfbbca | 2000-07-28 14:32:48 +0000 | [diff] [blame] | 245 | ** it finds a locked table. If the busy callback is not NULL, then |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 246 | ** sqlite3_exec() invokes the callback with three arguments. The |
drh | 2dfbbca | 2000-07-28 14:32:48 +0000 | [diff] [blame] | 247 | ** second argument is the name of the locked table and the third |
| 248 | ** argument is the number of times the table has been busy. If the |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 249 | ** busy callback returns 0, then sqlite3_exec() immediately returns |
| 250 | ** SQLITE_BUSY. If the callback returns non-zero, then sqlite3_exec() |
drh | 2dfbbca | 2000-07-28 14:32:48 +0000 | [diff] [blame] | 251 | ** tries to open the table again and the cycle repeats. |
| 252 | ** |
| 253 | ** The default busy callback is NULL. |
| 254 | ** |
| 255 | ** Sqlite is re-entrant, so the busy handler may start a new query. |
| 256 | ** (It is not clear why anyone would every want to do this, but it |
| 257 | ** is allowed, in theory.) But the busy handler may not close the |
| 258 | ** database. Closing the database from a busy handler will delete |
| 259 | ** data structures out from under the executing query and will |
| 260 | ** probably result in a coredump. |
| 261 | */ |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 262 | int sqlite3_busy_handler(sqlite3*, int(*)(void*,int), void*); |
drh | 2dfbbca | 2000-07-28 14:32:48 +0000 | [diff] [blame] | 263 | |
| 264 | /* |
| 265 | ** This routine sets a busy handler that sleeps for a while when a |
| 266 | ** table is locked. The handler will sleep multiple times until |
| 267 | ** at least "ms" milleseconds of sleeping have been done. After |
| 268 | ** "ms" milleseconds of sleeping, the handler returns 0 which |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 269 | ** causes sqlite3_exec() to return SQLITE_BUSY. |
drh | 2dfbbca | 2000-07-28 14:32:48 +0000 | [diff] [blame] | 270 | ** |
| 271 | ** Calling this routine with an argument less than or equal to zero |
| 272 | ** turns off all busy handlers. |
| 273 | */ |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 274 | int sqlite3_busy_timeout(sqlite3*, int ms); |
drh | 2dfbbca | 2000-07-28 14:32:48 +0000 | [diff] [blame] | 275 | |
drh | e371033 | 2000-09-29 13:30:53 +0000 | [diff] [blame] | 276 | /* |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 277 | ** This next routine is really just a wrapper around sqlite3_exec(). |
drh | e371033 | 2000-09-29 13:30:53 +0000 | [diff] [blame] | 278 | ** Instead of invoking a user-supplied callback for each row of the |
| 279 | ** result, this routine remembers each row of the result in memory |
| 280 | ** obtained from malloc(), then returns all of the result after the |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 281 | ** query has finished. |
| 282 | ** |
| 283 | ** As an example, suppose the query result where this table: |
| 284 | ** |
| 285 | ** Name | Age |
| 286 | ** ----------------------- |
| 287 | ** Alice | 43 |
| 288 | ** Bob | 28 |
| 289 | ** Cindy | 21 |
| 290 | ** |
| 291 | ** If the 3rd argument were &azResult then after the function returns |
drh | 98699b5 | 2000-10-09 12:57:00 +0000 | [diff] [blame] | 292 | ** azResult will contain the following data: |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 293 | ** |
| 294 | ** azResult[0] = "Name"; |
| 295 | ** azResult[1] = "Age"; |
| 296 | ** azResult[2] = "Alice"; |
| 297 | ** azResult[3] = "43"; |
| 298 | ** azResult[4] = "Bob"; |
| 299 | ** azResult[5] = "28"; |
| 300 | ** azResult[6] = "Cindy"; |
| 301 | ** azResult[7] = "21"; |
| 302 | ** |
| 303 | ** Notice that there is an extra row of data containing the column |
| 304 | ** headers. But the *nrow return value is still 3. *ncolumn is |
| 305 | ** set to 2. In general, the number of values inserted into azResult |
| 306 | ** will be ((*nrow) + 1)*(*ncolumn). |
| 307 | ** |
| 308 | ** After the calling function has finished using the result, it should |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 309 | ** pass the result data pointer to sqlite3_free_table() in order to |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 310 | ** release the memory that was malloc-ed. Because of the way the |
| 311 | ** malloc() happens, the calling function must not try to call |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 312 | ** malloc() directly. Only sqlite3_free_table() is able to release |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 313 | ** the memory properly and safely. |
drh | e371033 | 2000-09-29 13:30:53 +0000 | [diff] [blame] | 314 | ** |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 315 | ** The return value of this routine is the same as from sqlite3_exec(). |
drh | e371033 | 2000-09-29 13:30:53 +0000 | [diff] [blame] | 316 | */ |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 317 | int sqlite3_get_table( |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 318 | sqlite3*, /* An open database */ |
drh | 9f71c2e | 2001-11-03 23:57:09 +0000 | [diff] [blame] | 319 | const char *sql, /* SQL to be executed */ |
drh | e371033 | 2000-09-29 13:30:53 +0000 | [diff] [blame] | 320 | char ***resultp, /* Result written to a char *[] that this points to */ |
| 321 | int *nrow, /* Number of result rows written here */ |
| 322 | int *ncolumn, /* Number of result columns written here */ |
| 323 | char **errmsg /* Error msg written here */ |
| 324 | ); |
| 325 | |
| 326 | /* |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 327 | ** Call this routine to free the memory that sqlite3_get_table() allocated. |
drh | e371033 | 2000-09-29 13:30:53 +0000 | [diff] [blame] | 328 | */ |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 329 | void sqlite3_free_table(char **result); |
drh | e371033 | 2000-09-29 13:30:53 +0000 | [diff] [blame] | 330 | |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 331 | /* |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 332 | ** The following routines are variants of the "sprintf()" from the |
| 333 | ** standard C library. The resulting string is written into memory |
| 334 | ** obtained from malloc() so that there is never a possiblity of buffer |
| 335 | ** overflow. These routines also implement some additional formatting |
| 336 | ** options that are useful for constructing SQL statements. |
| 337 | ** |
| 338 | ** The strings returned by these routines should be freed by calling |
| 339 | ** sqlite3_free(). |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 340 | ** |
| 341 | ** All of the usual printf formatting options apply. In addition, there |
| 342 | ** is a "%q" option. %q works like %s in that it substitutes a null-terminated |
drh | 66b89c8 | 2000-11-28 20:47:17 +0000 | [diff] [blame] | 343 | ** string from the argument list. But %q also doubles every '\'' character. |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 344 | ** %q is designed for use inside a string literal. By doubling each '\'' |
drh | 66b89c8 | 2000-11-28 20:47:17 +0000 | [diff] [blame] | 345 | ** character it escapes that character and allows it to be inserted into |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 346 | ** the string. |
| 347 | ** |
| 348 | ** For example, so some string variable contains text as follows: |
| 349 | ** |
| 350 | ** char *zText = "It's a happy day!"; |
| 351 | ** |
| 352 | ** We can use this text in an SQL statement as follows: |
| 353 | ** |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 354 | ** sqlite3_exec_printf(db, "INSERT INTO table VALUES('%q')", |
drh | a18c568 | 2000-10-08 22:20:57 +0000 | [diff] [blame] | 355 | ** callback1, 0, 0, zText); |
| 356 | ** |
| 357 | ** Because the %q format string is used, the '\'' character in zText |
| 358 | ** is escaped and the SQL generated is as follows: |
| 359 | ** |
| 360 | ** INSERT INTO table1 VALUES('It''s a happy day!') |
| 361 | ** |
| 362 | ** This is correct. Had we used %s instead of %q, the generated SQL |
| 363 | ** would have looked like this: |
| 364 | ** |
| 365 | ** INSERT INTO table1 VALUES('It's a happy day!'); |
| 366 | ** |
| 367 | ** This second example is an SQL syntax error. As a general rule you |
| 368 | ** should always use %q instead of %s when inserting text into a string |
| 369 | ** literal. |
| 370 | */ |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 371 | char *sqlite3_mprintf(const char*,...); |
| 372 | char *sqlite3_vmprintf(const char*, va_list); |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 373 | void sqlite3_free(char *z); |
drh | feac5f8 | 2004-08-01 00:10:45 +0000 | [diff] [blame] | 374 | char *sqlite3_snprintf(int,char*,const char*, ...); |
drh | 5191b7e | 2002-03-08 02:12:00 +0000 | [diff] [blame] | 375 | |
drh | 1211de3 | 2004-07-26 12:24:22 +0000 | [diff] [blame] | 376 | #ifndef SQLITE_OMIT_AUTHORIZATION |
drh | 5191b7e | 2002-03-08 02:12:00 +0000 | [diff] [blame] | 377 | /* |
drh | ed6c867 | 2003-01-12 18:02:16 +0000 | [diff] [blame] | 378 | ** This routine registers a callback with the SQLite library. The |
drh | b86ccfb | 2003-01-28 23:13:10 +0000 | [diff] [blame] | 379 | ** callback is invoked (at compile-time, not at run-time) for each |
| 380 | ** attempt to access a column of a table in the database. The callback |
| 381 | ** returns SQLITE_OK if access is allowed, SQLITE_DENY if the entire |
| 382 | ** SQL statement should be aborted with an error and SQLITE_IGNORE |
| 383 | ** if the column should be treated as a NULL value. |
drh | ed6c867 | 2003-01-12 18:02:16 +0000 | [diff] [blame] | 384 | */ |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 385 | int sqlite3_set_authorizer( |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 386 | sqlite3*, |
drh | e22a334 | 2003-04-22 20:30:37 +0000 | [diff] [blame] | 387 | int (*xAuth)(void*,int,const char*,const char*,const char*,const char*), |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 388 | void *pUserData |
drh | ed6c867 | 2003-01-12 18:02:16 +0000 | [diff] [blame] | 389 | ); |
drh | 1211de3 | 2004-07-26 12:24:22 +0000 | [diff] [blame] | 390 | #endif |
drh | ed6c867 | 2003-01-12 18:02:16 +0000 | [diff] [blame] | 391 | |
| 392 | /* |
| 393 | ** The second parameter to the access authorization function above will |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 394 | ** be one of the values below. These values signify what kind of operation |
| 395 | ** is to be authorized. The 3rd and 4th parameters to the authorization |
| 396 | ** function will be parameters or NULL depending on which of the following |
drh | e22a334 | 2003-04-22 20:30:37 +0000 | [diff] [blame] | 397 | ** codes is used as the second parameter. The 5th parameter is the name |
| 398 | ** of the database ("main", "temp", etc.) if applicable. The 6th parameter |
drh | 5cf590c | 2003-04-24 01:45:04 +0000 | [diff] [blame] | 399 | ** is the name of the inner-most trigger or view that is responsible for |
| 400 | ** the access attempt or NULL if this access attempt is directly from |
| 401 | ** input SQL code. |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 402 | ** |
| 403 | ** Arg-3 Arg-4 |
drh | ed6c867 | 2003-01-12 18:02:16 +0000 | [diff] [blame] | 404 | */ |
drh | 77ad4e4 | 2003-01-14 02:49:27 +0000 | [diff] [blame] | 405 | #define SQLITE_COPY 0 /* Table Name File Name */ |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 406 | #define SQLITE_CREATE_INDEX 1 /* Index Name Table Name */ |
| 407 | #define SQLITE_CREATE_TABLE 2 /* Table Name NULL */ |
| 408 | #define SQLITE_CREATE_TEMP_INDEX 3 /* Index Name Table Name */ |
| 409 | #define SQLITE_CREATE_TEMP_TABLE 4 /* Table Name NULL */ |
drh | 77ad4e4 | 2003-01-14 02:49:27 +0000 | [diff] [blame] | 410 | #define SQLITE_CREATE_TEMP_TRIGGER 5 /* Trigger Name Table Name */ |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 411 | #define SQLITE_CREATE_TEMP_VIEW 6 /* View Name NULL */ |
drh | 77ad4e4 | 2003-01-14 02:49:27 +0000 | [diff] [blame] | 412 | #define SQLITE_CREATE_TRIGGER 7 /* Trigger Name Table Name */ |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 413 | #define SQLITE_CREATE_VIEW 8 /* View Name NULL */ |
| 414 | #define SQLITE_DELETE 9 /* Table Name NULL */ |
drh | 77ad4e4 | 2003-01-14 02:49:27 +0000 | [diff] [blame] | 415 | #define SQLITE_DROP_INDEX 10 /* Index Name Table Name */ |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 416 | #define SQLITE_DROP_TABLE 11 /* Table Name NULL */ |
drh | 77ad4e4 | 2003-01-14 02:49:27 +0000 | [diff] [blame] | 417 | #define SQLITE_DROP_TEMP_INDEX 12 /* Index Name Table Name */ |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 418 | #define SQLITE_DROP_TEMP_TABLE 13 /* Table Name NULL */ |
drh | 77ad4e4 | 2003-01-14 02:49:27 +0000 | [diff] [blame] | 419 | #define SQLITE_DROP_TEMP_TRIGGER 14 /* Trigger Name Table Name */ |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 420 | #define SQLITE_DROP_TEMP_VIEW 15 /* View Name NULL */ |
drh | 77ad4e4 | 2003-01-14 02:49:27 +0000 | [diff] [blame] | 421 | #define SQLITE_DROP_TRIGGER 16 /* Trigger Name Table Name */ |
drh | e5f9c64 | 2003-01-13 23:27:31 +0000 | [diff] [blame] | 422 | #define SQLITE_DROP_VIEW 17 /* View Name NULL */ |
| 423 | #define SQLITE_INSERT 18 /* Table Name NULL */ |
| 424 | #define SQLITE_PRAGMA 19 /* Pragma Name 1st arg or NULL */ |
| 425 | #define SQLITE_READ 20 /* Table Name Column Name */ |
| 426 | #define SQLITE_SELECT 21 /* NULL NULL */ |
| 427 | #define SQLITE_TRANSACTION 22 /* NULL NULL */ |
| 428 | #define SQLITE_UPDATE 23 /* Table Name Column Name */ |
drh | 81e293b | 2003-06-06 19:00:42 +0000 | [diff] [blame] | 429 | #define SQLITE_ATTACH 24 /* Filename NULL */ |
| 430 | #define SQLITE_DETACH 25 /* Database Name NULL */ |
danielk1977 | 1c8c23c | 2004-11-12 15:53:37 +0000 | [diff] [blame] | 431 | #define SQLITE_ALTER_TABLE 26 /* Database Name Table Name */ |
danielk1977 | 1d54df8 | 2004-11-23 15:41:16 +0000 | [diff] [blame] | 432 | #define SQLITE_REINDEX 27 /* Index Name NULL */ |
drh | 81e293b | 2003-06-06 19:00:42 +0000 | [diff] [blame] | 433 | |
drh | ed6c867 | 2003-01-12 18:02:16 +0000 | [diff] [blame] | 434 | |
| 435 | /* |
| 436 | ** The return value of the authorization function should be one of the |
| 437 | ** following constants: |
| 438 | */ |
| 439 | /* #define SQLITE_OK 0 // Allow access (This is actually defined above) */ |
| 440 | #define SQLITE_DENY 1 /* Abort the SQL statement with an error */ |
| 441 | #define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */ |
| 442 | |
| 443 | /* |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 444 | ** Register a function that is called at every invocation of sqlite3_exec() |
danielk1977 | 4ad1713 | 2004-05-21 01:47:26 +0000 | [diff] [blame] | 445 | ** or sqlite3_prepare(). This function can be used (for example) to generate |
drh | b86ccfb | 2003-01-28 23:13:10 +0000 | [diff] [blame] | 446 | ** a log file of all SQL executed against a database. |
drh | 18de482 | 2003-01-16 16:28:53 +0000 | [diff] [blame] | 447 | */ |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 448 | void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const char*), void*); |
drh | 18de482 | 2003-01-16 16:28:53 +0000 | [diff] [blame] | 449 | |
danielk1977 | 348bb5d | 2003-10-18 09:37:26 +0000 | [diff] [blame] | 450 | /* |
| 451 | ** This routine configures a callback function - the progress callback - that |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 452 | ** is invoked periodically during long running calls to sqlite3_exec(), |
danielk1977 | 2097e94 | 2004-11-20 06:05:56 +0000 | [diff] [blame] | 453 | ** sqlite3_step() and sqlite3_get_table(). An example use for this API is to |
| 454 | ** keep a GUI updated during a large query. |
danielk1977 | 348bb5d | 2003-10-18 09:37:26 +0000 | [diff] [blame] | 455 | ** |
| 456 | ** The progress callback is invoked once for every N virtual machine opcodes, |
| 457 | ** where N is the second argument to this function. The progress callback |
| 458 | ** itself is identified by the third argument to this function. The fourth |
| 459 | ** argument to this function is a void pointer passed to the progress callback |
| 460 | ** function each time it is invoked. |
| 461 | ** |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 462 | ** If a call to sqlite3_exec(), sqlite3_step() or sqlite3_get_table() results |
danielk1977 | 348bb5d | 2003-10-18 09:37:26 +0000 | [diff] [blame] | 463 | ** in less than N opcodes being executed, then the progress callback is not |
| 464 | ** invoked. |
| 465 | ** |
danielk1977 | 348bb5d | 2003-10-18 09:37:26 +0000 | [diff] [blame] | 466 | ** To remove the progress callback altogether, pass NULL as the third |
| 467 | ** argument to this function. |
| 468 | ** |
| 469 | ** If the progress callback returns a result other than 0, then the current |
| 470 | ** query is immediately terminated and any database changes rolled back. If the |
| 471 | ** query was part of a larger transaction, then the transaction is not rolled |
danielk1977 | 6f8a503 | 2004-05-10 10:34:51 +0000 | [diff] [blame] | 472 | ** back and remains active. The sqlite3_exec() call returns SQLITE_ABORT. |
drh | aa940ea | 2004-01-15 02:44:03 +0000 | [diff] [blame] | 473 | ** |
| 474 | ******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ****** |
danielk1977 | 348bb5d | 2003-10-18 09:37:26 +0000 | [diff] [blame] | 475 | */ |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 476 | void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*); |
danielk1977 | 348bb5d | 2003-10-18 09:37:26 +0000 | [diff] [blame] | 477 | |
drh | aa940ea | 2004-01-15 02:44:03 +0000 | [diff] [blame] | 478 | /* |
| 479 | ** Register a callback function to be invoked whenever a new transaction |
| 480 | ** is committed. The pArg argument is passed through to the callback. |
| 481 | ** callback. If the callback function returns non-zero, then the commit |
| 482 | ** is converted into a rollback. |
| 483 | ** |
| 484 | ** If another function was previously registered, its pArg value is returned. |
| 485 | ** Otherwise NULL is returned. |
| 486 | ** |
| 487 | ** Registering a NULL function disables the callback. |
| 488 | ** |
| 489 | ******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ****** |
| 490 | */ |
danielk1977 | f9d64d2 | 2004-06-19 08:18:07 +0000 | [diff] [blame] | 491 | void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*); |
drh | aa940ea | 2004-01-15 02:44:03 +0000 | [diff] [blame] | 492 | |
drh | 22fbcb8 | 2004-02-01 01:22:50 +0000 | [diff] [blame] | 493 | /* |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 494 | ** Open the sqlite database file "filename". The "filename" is UTF-8 |
| 495 | ** encoded for sqlite3_open() and UTF-16 encoded in the native byte order |
| 496 | ** for sqlite3_open16(). An sqlite3* handle is returned in *ppDb, even |
| 497 | ** if an error occurs. If the database is opened (or created) successfully, |
| 498 | ** then SQLITE_OK is returned. Otherwise an error code is returned. The |
| 499 | ** sqlite3_errmsg() or sqlite3_errmsg16() routines can be used to obtain |
| 500 | ** an English language description of the error. |
drh | 22fbcb8 | 2004-02-01 01:22:50 +0000 | [diff] [blame] | 501 | ** |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 502 | ** If the database file does not exist, then a new database is created. |
| 503 | ** The encoding for the database is UTF-8 if sqlite3_open() is called and |
| 504 | ** UTF-16 if sqlite3_open16 is used. |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 505 | ** |
| 506 | ** Whether or not an error occurs when it is opened, resources associated |
| 507 | ** with the sqlite3* handle should be released by passing it to |
| 508 | ** sqlite3_close() when it is no longer required. |
| 509 | */ |
| 510 | int sqlite3_open( |
| 511 | const char *filename, /* Database filename (UTF-8) */ |
danielk1977 | 4f057f9 | 2004-06-08 00:02:33 +0000 | [diff] [blame] | 512 | sqlite3 **ppDb /* OUT: SQLite db handle */ |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 513 | ); |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 514 | int sqlite3_open16( |
| 515 | const void *filename, /* Database filename (UTF-16) */ |
danielk1977 | 4f057f9 | 2004-06-08 00:02:33 +0000 | [diff] [blame] | 516 | sqlite3 **ppDb /* OUT: SQLite db handle */ |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 517 | ); |
danielk1977 | 295ba55 | 2004-05-19 10:34:51 +0000 | [diff] [blame] | 518 | |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 519 | /* |
| 520 | ** Return the error code for the most recent sqlite3_* API call associated |
| 521 | ** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent |
| 522 | ** API call was successful. |
| 523 | ** |
| 524 | ** Calls to many sqlite3_* functions set the error code and string returned |
| 525 | ** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16() |
| 526 | ** (overwriting the previous values). Note that calls to sqlite3_errcode(), |
| 527 | ** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the |
| 528 | ** results of future invocations. |
| 529 | ** |
| 530 | ** Assuming no other intervening sqlite3_* API calls are made, the error |
| 531 | ** code returned by this function is associated with the same error as |
| 532 | ** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16(). |
| 533 | */ |
| 534 | int sqlite3_errcode(sqlite3 *db); |
| 535 | |
| 536 | /* |
| 537 | ** Return a pointer to a UTF-8 encoded string describing in english the |
| 538 | ** error condition for the most recent sqlite3_* API call. The returned |
| 539 | ** string is always terminated by an 0x00 byte. |
| 540 | ** |
| 541 | ** The string "not an error" is returned when the most recent API call was |
| 542 | ** successful. |
| 543 | */ |
| 544 | const char *sqlite3_errmsg(sqlite3*); |
| 545 | |
| 546 | /* |
| 547 | ** Return a pointer to a UTF-16 native byte order encoded string describing |
| 548 | ** in english the error condition for the most recent sqlite3_* API call. |
| 549 | ** The returned string is always terminated by a pair of 0x00 bytes. |
| 550 | ** |
| 551 | ** The string "not an error" is returned when the most recent API call was |
| 552 | ** successful. |
| 553 | */ |
| 554 | const void *sqlite3_errmsg16(sqlite3*); |
| 555 | |
| 556 | /* |
| 557 | ** An instance of the following opaque structure is used to represent |
| 558 | ** a compiled SQL statment. |
| 559 | */ |
danielk1977 | fc57d7b | 2004-05-26 02:04:57 +0000 | [diff] [blame] | 560 | typedef struct sqlite3_stmt sqlite3_stmt; |
| 561 | |
danielk1977 | e3209e4 | 2004-05-20 01:40:18 +0000 | [diff] [blame] | 562 | /* |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 563 | ** To execute an SQL query, it must first be compiled into a byte-code |
| 564 | ** program using one of the following routines. The only difference between |
| 565 | ** them is that the second argument, specifying the SQL statement to |
| 566 | ** compile, is assumed to be encoded in UTF-8 for the sqlite3_prepare() |
| 567 | ** function and UTF-16 for sqlite3_prepare16(). |
| 568 | ** |
| 569 | ** The first parameter "db" is an SQLite database handle. The second |
| 570 | ** parameter "zSql" is the statement to be compiled, encoded as either |
| 571 | ** UTF-8 or UTF-16 (see above). If the next parameter, "nBytes", is less |
| 572 | ** than zero, then zSql is read up to the first nul terminator. If |
| 573 | ** "nBytes" is not less than zero, then it is the length of the string zSql |
| 574 | ** in bytes (not characters). |
| 575 | ** |
| 576 | ** *pzTail is made to point to the first byte past the end of the first |
| 577 | ** SQL statement in zSql. This routine only compiles the first statement |
| 578 | ** in zSql, so *pzTail is left pointing to what remains uncompiled. |
| 579 | ** |
| 580 | ** *ppStmt is left pointing to a compiled SQL statement that can be |
| 581 | ** executed using sqlite3_step(). Or if there is an error, *ppStmt may be |
| 582 | ** set to NULL. If the input text contained no SQL (if the input is and |
| 583 | ** empty string or a comment) then *ppStmt is set to NULL. |
| 584 | ** |
| 585 | ** On success, SQLITE_OK is returned. Otherwise an error code is returned. |
| 586 | */ |
| 587 | int sqlite3_prepare( |
| 588 | sqlite3 *db, /* Database handle */ |
| 589 | const char *zSql, /* SQL statement, UTF-8 encoded */ |
| 590 | int nBytes, /* Length of zSql in bytes. */ |
| 591 | sqlite3_stmt **ppStmt, /* OUT: Statement handle */ |
| 592 | const char **pzTail /* OUT: Pointer to unused portion of zSql */ |
| 593 | ); |
| 594 | int sqlite3_prepare16( |
| 595 | sqlite3 *db, /* Database handle */ |
| 596 | const void *zSql, /* SQL statement, UTF-16 encoded */ |
| 597 | int nBytes, /* Length of zSql in bytes. */ |
| 598 | sqlite3_stmt **ppStmt, /* OUT: Statement handle */ |
| 599 | const void **pzTail /* OUT: Pointer to unused portion of zSql */ |
| 600 | ); |
| 601 | |
| 602 | /* |
drh | f447950 | 2004-05-27 03:12:53 +0000 | [diff] [blame] | 603 | ** Pointers to the following two opaque structures are used to communicate |
| 604 | ** with the implementations of user-defined functions. |
| 605 | */ |
| 606 | typedef struct sqlite3_context sqlite3_context; |
| 607 | typedef struct Mem sqlite3_value; |
| 608 | |
| 609 | /* |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 610 | ** In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(), |
drh | 32c0d4f | 2004-12-07 02:14:51 +0000 | [diff] [blame] | 611 | ** one or more literals can be replace by parameters "?" or ":AAA" or |
| 612 | ** "$VVV" where AAA is an identifer and VVV is a variable name according |
| 613 | ** to the syntax rules of the TCL programming language. |
| 614 | ** The value of these parameters (also called "host parameter names") can |
| 615 | ** be set using the routines listed below. |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 616 | ** |
| 617 | ** In every case, the first parameter is a pointer to the sqlite3_stmt |
| 618 | ** structure returned from sqlite3_prepare(). The second parameter is the |
drh | 32c0d4f | 2004-12-07 02:14:51 +0000 | [diff] [blame] | 619 | ** index of the parameter. The first parameter as an index of 1. For |
| 620 | ** named parameters (":AAA" or "$VVV") you can use |
| 621 | ** sqlite3_bind_parameter_index() to get the correct index value given |
| 622 | ** the parameters name. If the same named parameter occurs more than |
| 623 | ** once, it is assigned the same index each time. |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 624 | ** |
drh | 900dfba | 2004-07-21 15:21:36 +0000 | [diff] [blame] | 625 | ** The fifth parameter to sqlite3_bind_blob(), sqlite3_bind_text(), and |
| 626 | ** sqlite3_bind_text16() is a destructor used to dispose of the BLOB or |
| 627 | ** text after SQLite has finished with it. If the fifth argument is the |
| 628 | ** special value SQLITE_STATIC, then the library assumes that the information |
| 629 | ** is in static, unmanaged space and does not need to be freed. If the |
| 630 | ** fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its |
| 631 | ** own private copy of the data. |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 632 | ** |
| 633 | ** The sqlite3_bind_* routine must be called before sqlite3_step() after |
drh | 32c0d4f | 2004-12-07 02:14:51 +0000 | [diff] [blame] | 634 | ** an sqlite3_prepare() or sqlite3_reset(). Unbound parameterss are |
| 635 | ** interpreted as NULL. |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 636 | */ |
danielk1977 | d812336 | 2004-06-12 09:25:12 +0000 | [diff] [blame] | 637 | int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*)); |
drh | f447950 | 2004-05-27 03:12:53 +0000 | [diff] [blame] | 638 | int sqlite3_bind_double(sqlite3_stmt*, int, double); |
| 639 | int sqlite3_bind_int(sqlite3_stmt*, int, int); |
drh | efad999 | 2004-06-22 12:13:55 +0000 | [diff] [blame] | 640 | int sqlite3_bind_int64(sqlite3_stmt*, int, sqlite_int64); |
drh | f447950 | 2004-05-27 03:12:53 +0000 | [diff] [blame] | 641 | int sqlite3_bind_null(sqlite3_stmt*, int); |
danielk1977 | d812336 | 2004-06-12 09:25:12 +0000 | [diff] [blame] | 642 | int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*)); |
| 643 | int sqlite3_bind_text16(sqlite3_stmt*, int, const void*, int, void(*)(void*)); |
drh | f447950 | 2004-05-27 03:12:53 +0000 | [diff] [blame] | 644 | int sqlite3_bind_value(sqlite3_stmt*, int, const sqlite3_value*); |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 645 | |
| 646 | /* |
drh | 32c0d4f | 2004-12-07 02:14:51 +0000 | [diff] [blame] | 647 | ** Return the number of parameters in a compiled SQL statement. This |
drh | 75f6a03 | 2004-07-15 14:15:00 +0000 | [diff] [blame] | 648 | ** routine was added to support DBD::SQLite. |
drh | 75f6a03 | 2004-07-15 14:15:00 +0000 | [diff] [blame] | 649 | */ |
| 650 | int sqlite3_bind_parameter_count(sqlite3_stmt*); |
| 651 | |
| 652 | /* |
drh | 32c0d4f | 2004-12-07 02:14:51 +0000 | [diff] [blame] | 653 | ** Return the name of the i-th parameter. Ordinary parameters "?" are |
| 654 | ** nameless and a NULL is returned. For parameters of the form :AAA or |
| 655 | ** $VVV the complete text of the parameter name is returned, including |
| 656 | ** the initial ":" or "$". NULL is returned if the index is out of range. |
drh | 895d747 | 2004-08-20 16:02:39 +0000 | [diff] [blame] | 657 | */ |
| 658 | const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int); |
| 659 | |
| 660 | /* |
drh | fa6bc00 | 2004-09-07 16:19:52 +0000 | [diff] [blame] | 661 | ** Return the index of a parameter with the given name. The name |
| 662 | ** must match exactly. If no parameter with the given name is found, |
| 663 | ** return 0. |
| 664 | */ |
| 665 | int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName); |
| 666 | |
| 667 | /* |
danielk1977 | 600dd0b | 2005-01-20 01:14:23 +0000 | [diff] [blame] | 668 | ** Set all the parameters in the compiled SQL statement to NULL. |
| 669 | ** |
| 670 | ******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ****** |
| 671 | */ |
| 672 | int sqlite3_clear_bindings(sqlite3_stmt*); |
| 673 | |
| 674 | /* |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 675 | ** Return the number of columns in the result set returned by the compiled |
| 676 | ** SQL statement. This routine returns 0 if pStmt is an SQL statement |
| 677 | ** that does not return data (for example an UPDATE). |
| 678 | */ |
| 679 | int sqlite3_column_count(sqlite3_stmt *pStmt); |
| 680 | |
| 681 | /* |
| 682 | ** The first parameter is a compiled SQL statement. This function returns |
| 683 | ** the column heading for the Nth column of that statement, where N is the |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 684 | ** second function parameter. The string returned is UTF-8 for |
| 685 | ** sqlite3_column_name() and UTF-16 for sqlite3_column_name16(). |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 686 | */ |
| 687 | const char *sqlite3_column_name(sqlite3_stmt*,int); |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 688 | const void *sqlite3_column_name16(sqlite3_stmt*,int); |
| 689 | |
| 690 | /* |
| 691 | ** The first parameter is a compiled SQL statement. If this statement |
| 692 | ** is a SELECT statement, the Nth column of the returned result set |
| 693 | ** of the SELECT is a table column then the declared type of the table |
| 694 | ** column is returned. If the Nth column of the result set is not at table |
| 695 | ** column, then a NULL pointer is returned. The returned string is always |
| 696 | ** UTF-8 encoded. For example, in the database schema: |
| 697 | ** |
| 698 | ** CREATE TABLE t1(c1 VARIANT); |
| 699 | ** |
| 700 | ** And the following statement compiled: |
| 701 | ** |
| 702 | ** SELECT c1 + 1, 0 FROM t1; |
| 703 | ** |
| 704 | ** Then this routine would return the string "VARIANT" for the second |
| 705 | ** result column (i==1), and a NULL pointer for the first result column |
| 706 | ** (i==0). |
| 707 | */ |
| 708 | const char *sqlite3_column_decltype(sqlite3_stmt *, int i); |
| 709 | |
| 710 | /* |
| 711 | ** The first parameter is a compiled SQL statement. If this statement |
| 712 | ** is a SELECT statement, the Nth column of the returned result set |
| 713 | ** of the SELECT is a table column then the declared type of the table |
| 714 | ** column is returned. If the Nth column of the result set is not at table |
| 715 | ** column, then a NULL pointer is returned. The returned string is always |
| 716 | ** UTF-16 encoded. For example, in the database schema: |
| 717 | ** |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 718 | ** CREATE TABLE t1(c1 INTEGER); |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 719 | ** |
| 720 | ** And the following statement compiled: |
| 721 | ** |
| 722 | ** SELECT c1 + 1, 0 FROM t1; |
| 723 | ** |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 724 | ** Then this routine would return the string "INTEGER" for the second |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 725 | ** result column (i==1), and a NULL pointer for the first result column |
| 726 | ** (i==0). |
| 727 | */ |
| 728 | const void *sqlite3_column_decltype16(sqlite3_stmt*,int); |
| 729 | |
danielk1977 | 106bb23 | 2004-05-21 10:08:53 +0000 | [diff] [blame] | 730 | /* |
| 731 | ** After an SQL query has been compiled with a call to either |
| 732 | ** sqlite3_prepare() or sqlite3_prepare16(), then this function must be |
| 733 | ** called one or more times to execute the statement. |
| 734 | ** |
| 735 | ** The return value will be either SQLITE_BUSY, SQLITE_DONE, |
| 736 | ** SQLITE_ROW, SQLITE_ERROR, or SQLITE_MISUSE. |
| 737 | ** |
| 738 | ** SQLITE_BUSY means that the database engine attempted to open |
| 739 | ** a locked database and there is no busy callback registered. |
| 740 | ** Call sqlite3_step() again to retry the open. |
| 741 | ** |
| 742 | ** SQLITE_DONE means that the statement has finished executing |
| 743 | ** successfully. sqlite3_step() should not be called again on this virtual |
| 744 | ** machine. |
| 745 | ** |
| 746 | ** If the SQL statement being executed returns any data, then |
| 747 | ** SQLITE_ROW is returned each time a new row of data is ready |
| 748 | ** for processing by the caller. The values may be accessed using |
| 749 | ** the sqlite3_column_*() functions described below. sqlite3_step() |
| 750 | ** is called again to retrieve the next row of data. |
| 751 | ** |
| 752 | ** SQLITE_ERROR means that a run-time error (such as a constraint |
| 753 | ** violation) has occurred. sqlite3_step() should not be called again on |
| 754 | ** the VM. More information may be found by calling sqlite3_errmsg(). |
| 755 | ** |
| 756 | ** SQLITE_MISUSE means that the this routine was called inappropriately. |
| 757 | ** Perhaps it was called on a virtual machine that had already been |
| 758 | ** finalized or on one that had previously returned SQLITE_ERROR or |
| 759 | ** SQLITE_DONE. Or it could be the case the the same database connection |
| 760 | ** is being used simulataneously by two or more threads. |
| 761 | */ |
danielk1977 | 17240fd | 2004-05-26 00:07:25 +0000 | [diff] [blame] | 762 | int sqlite3_step(sqlite3_stmt*); |
danielk1977 | 106bb23 | 2004-05-21 10:08:53 +0000 | [diff] [blame] | 763 | |
danielk1977 | 106bb23 | 2004-05-21 10:08:53 +0000 | [diff] [blame] | 764 | /* |
| 765 | ** Return the number of values in the current row of the result set. |
| 766 | ** |
| 767 | ** After a call to sqlite3_step() that returns SQLITE_ROW, this routine |
| 768 | ** will return the same value as the sqlite3_column_count() function. |
| 769 | ** After sqlite3_step() has returned an SQLITE_DONE, SQLITE_BUSY or |
| 770 | ** error code, or before sqlite3_step() has been called on a |
| 771 | ** compiled SQL statement, this routine returns zero. |
| 772 | */ |
danielk1977 | 93d4675 | 2004-05-23 13:30:58 +0000 | [diff] [blame] | 773 | int sqlite3_data_count(sqlite3_stmt *pStmt); |
danielk1977 | 4adee20 | 2004-05-08 08:23:19 +0000 | [diff] [blame] | 774 | |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 775 | /* |
| 776 | ** Values are stored in the database in one of the following fundamental |
| 777 | ** types. |
| 778 | */ |
drh | 9c05483 | 2004-05-31 18:51:57 +0000 | [diff] [blame] | 779 | #define SQLITE_INTEGER 1 |
| 780 | #define SQLITE_FLOAT 2 |
drh | 1e284f4 | 2004-10-06 15:52:01 +0000 | [diff] [blame] | 781 | /* #define SQLITE_TEXT 3 // See below */ |
drh | 9c05483 | 2004-05-31 18:51:57 +0000 | [diff] [blame] | 782 | #define SQLITE_BLOB 4 |
| 783 | #define SQLITE_NULL 5 |
danielk1977 | 4adee20 | 2004-05-08 08:23:19 +0000 | [diff] [blame] | 784 | |
danielk1977 | 106bb23 | 2004-05-21 10:08:53 +0000 | [diff] [blame] | 785 | /* |
drh | 1e284f4 | 2004-10-06 15:52:01 +0000 | [diff] [blame] | 786 | ** SQLite version 2 defines SQLITE_TEXT differently. To allow both |
| 787 | ** version 2 and version 3 to be included, undefine them both if a |
| 788 | ** conflict is seen. Define SQLITE3_TEXT to be the version 3 value. |
| 789 | */ |
| 790 | #ifdef SQLITE_TEXT |
| 791 | # undef SQLITE_TEXT |
| 792 | #else |
| 793 | # define SQLITE_TEXT 3 |
| 794 | #endif |
| 795 | #define SQLITE3_TEXT 3 |
| 796 | |
| 797 | /* |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 798 | ** The next group of routines returns information about the information |
| 799 | ** in a single column of the current result row of a query. In every |
| 800 | ** case the first parameter is a pointer to the SQL statement that is being |
| 801 | ** executed (the sqlite_stmt* that was returned from sqlite3_prepare()) and |
| 802 | ** the second argument is the index of the column for which information |
| 803 | ** should be returned. iCol is zero-indexed. The left-most column as an |
| 804 | ** index of 0. |
danielk1977 | 106bb23 | 2004-05-21 10:08:53 +0000 | [diff] [blame] | 805 | ** |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 806 | ** If the SQL statement is not currently point to a valid row, or if the |
| 807 | ** the colulmn index is out of range, the result is undefined. |
| 808 | ** |
| 809 | ** These routines attempt to convert the value where appropriate. For |
| 810 | ** example, if the internal representation is FLOAT and a text result |
| 811 | ** is requested, sprintf() is used internally to do the conversion |
| 812 | ** automatically. The following table details the conversions that |
| 813 | ** are applied: |
| 814 | ** |
| 815 | ** Internal Type Requested Type Conversion |
| 816 | ** ------------- -------------- -------------------------- |
| 817 | ** NULL INTEGER Result is 0 |
| 818 | ** NULL FLOAT Result is 0.0 |
| 819 | ** NULL TEXT Result is an empty string |
| 820 | ** NULL BLOB Result is a zero-length BLOB |
| 821 | ** INTEGER FLOAT Convert from integer to float |
| 822 | ** INTEGER TEXT ASCII rendering of the integer |
| 823 | ** INTEGER BLOB Same as for INTEGER->TEXT |
| 824 | ** FLOAT INTEGER Convert from float to integer |
| 825 | ** FLOAT TEXT ASCII rendering of the float |
| 826 | ** FLOAT BLOB Same as FLOAT->TEXT |
| 827 | ** TEXT INTEGER Use atoi() |
| 828 | ** TEXT FLOAT Use atof() |
| 829 | ** TEXT BLOB No change |
| 830 | ** BLOB INTEGER Convert to TEXT then use atoi() |
| 831 | ** BLOB FLOAT Convert to TEXT then use atof() |
| 832 | ** BLOB TEXT Add a \000 terminator if needed |
| 833 | ** |
| 834 | ** The following access routines are provided: |
| 835 | ** |
| 836 | ** _type() Return the datatype of the result. This is one of |
| 837 | ** SQLITE_INTEGER, SQLITE_FLOAT, SQLITE_TEXT, SQLITE_BLOB, |
| 838 | ** or SQLITE_NULL. |
| 839 | ** _blob() Return the value of a BLOB. |
| 840 | ** _bytes() Return the number of bytes in a BLOB value or the number |
| 841 | ** of bytes in a TEXT value represented as UTF-8. The \000 |
| 842 | ** terminator is included in the byte count for TEXT values. |
| 843 | ** _bytes16() Return the number of bytes in a BLOB value or the number |
| 844 | ** of bytes in a TEXT value represented as UTF-16. The \u0000 |
| 845 | ** terminator is included in the byte count for TEXT values. |
| 846 | ** _double() Return a FLOAT value. |
| 847 | ** _int() Return an INTEGER value in the host computer's native |
| 848 | ** integer representation. This might be either a 32- or 64-bit |
| 849 | ** integer depending on the host. |
| 850 | ** _int64() Return an INTEGER value as a 64-bit signed integer. |
| 851 | ** _text() Return the value as UTF-8 text. |
| 852 | ** _text16() Return the value as UTF-16 text. |
danielk1977 | 106bb23 | 2004-05-21 10:08:53 +0000 | [diff] [blame] | 853 | */ |
drh | f447950 | 2004-05-27 03:12:53 +0000 | [diff] [blame] | 854 | const void *sqlite3_column_blob(sqlite3_stmt*, int iCol); |
| 855 | int sqlite3_column_bytes(sqlite3_stmt*, int iCol); |
| 856 | int sqlite3_column_bytes16(sqlite3_stmt*, int iCol); |
| 857 | double sqlite3_column_double(sqlite3_stmt*, int iCol); |
| 858 | int sqlite3_column_int(sqlite3_stmt*, int iCol); |
drh | efad999 | 2004-06-22 12:13:55 +0000 | [diff] [blame] | 859 | sqlite_int64 sqlite3_column_int64(sqlite3_stmt*, int iCol); |
drh | f447950 | 2004-05-27 03:12:53 +0000 | [diff] [blame] | 860 | const unsigned char *sqlite3_column_text(sqlite3_stmt*, int iCol); |
| 861 | const void *sqlite3_column_text16(sqlite3_stmt*, int iCol); |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 862 | int sqlite3_column_type(sqlite3_stmt*, int iCol); |
danielk1977 | 4adee20 | 2004-05-08 08:23:19 +0000 | [diff] [blame] | 863 | |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 864 | /* |
| 865 | ** The sqlite3_finalize() function is called to delete a compiled |
| 866 | ** SQL statement obtained by a previous call to sqlite3_prepare() |
| 867 | ** or sqlite3_prepare16(). If the statement was executed successfully, or |
| 868 | ** not executed at all, then SQLITE_OK is returned. If execution of the |
| 869 | ** statement failed then an error code is returned. |
| 870 | ** |
| 871 | ** This routine can be called at any point during the execution of the |
| 872 | ** virtual machine. If the virtual machine has not completed execution |
| 873 | ** when this routine is called, that is like encountering an error or |
| 874 | ** an interrupt. (See sqlite3_interrupt().) Incomplete updates may be |
| 875 | ** rolled back and transactions cancelled, depending on the circumstances, |
| 876 | ** and the result code returned will be SQLITE_ABORT. |
| 877 | */ |
| 878 | int sqlite3_finalize(sqlite3_stmt *pStmt); |
| 879 | |
| 880 | /* |
| 881 | ** The sqlite3_reset() function is called to reset a compiled SQL |
| 882 | ** statement obtained by a previous call to sqlite3_prepare() or |
| 883 | ** sqlite3_prepare16() back to it's initial state, ready to be re-executed. |
| 884 | ** Any SQL statement variables that had values bound to them using |
| 885 | ** the sqlite3_bind_*() API retain their values. |
| 886 | */ |
| 887 | int sqlite3_reset(sqlite3_stmt *pStmt); |
| 888 | |
| 889 | /* |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 890 | ** The following two functions are used to add user functions or aggregates |
| 891 | ** implemented in C to the SQL langauge interpreted by SQLite. The |
| 892 | ** difference only between the two is that the second parameter, the |
| 893 | ** name of the (scalar) function or aggregate, is encoded in UTF-8 for |
| 894 | ** sqlite3_create_function() and UTF-16 for sqlite3_create_function16(). |
| 895 | ** |
| 896 | ** The first argument is the database handle that the new function or |
| 897 | ** aggregate is to be added to. If a single program uses more than one |
| 898 | ** database handle internally, then user functions or aggregates must |
| 899 | ** be added individually to each database handle with which they will be |
| 900 | ** used. |
| 901 | ** |
| 902 | ** The third parameter is the number of arguments that the function or |
| 903 | ** aggregate takes. If this parameter is negative, then the function or |
| 904 | ** aggregate may take any number of arguments. |
| 905 | ** |
danielk1977 | d812336 | 2004-06-12 09:25:12 +0000 | [diff] [blame] | 906 | ** The fourth parameter is one of SQLITE_UTF* values defined below, |
| 907 | ** indicating the encoding that the function is most likely to handle |
| 908 | ** values in. This does not change the behaviour of the programming |
| 909 | ** interface. However, if two versions of the same function are registered |
| 910 | ** with different encoding values, SQLite invokes the version likely to |
| 911 | ** minimize conversions between text encodings. |
danielk1977 | d02eb1f | 2004-06-06 09:44:03 +0000 | [diff] [blame] | 912 | ** |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 913 | ** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are |
| 914 | ** pointers to user implemented C functions that implement the user |
| 915 | ** function or aggregate. A scalar function requires an implementation of |
| 916 | ** the xFunc callback only, NULL pointers should be passed as the xStep |
| 917 | ** and xFinal parameters. An aggregate function requires an implementation |
| 918 | ** of xStep and xFinal, but NULL should be passed for xFunc. To delete an |
| 919 | ** existing user function or aggregate, pass NULL for all three function |
| 920 | ** callback. Specifying an inconstent set of callback values, such as an |
| 921 | ** xFunc and an xFinal, or an xStep but no xFinal, SQLITE_ERROR is |
| 922 | ** returned. |
| 923 | */ |
| 924 | int sqlite3_create_function( |
| 925 | sqlite3 *, |
| 926 | const char *zFunctionName, |
| 927 | int nArg, |
| 928 | int eTextRep, |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 929 | void*, |
| 930 | void (*xFunc)(sqlite3_context*,int,sqlite3_value**), |
| 931 | void (*xStep)(sqlite3_context*,int,sqlite3_value**), |
| 932 | void (*xFinal)(sqlite3_context*) |
| 933 | ); |
| 934 | int sqlite3_create_function16( |
| 935 | sqlite3*, |
| 936 | const void *zFunctionName, |
| 937 | int nArg, |
| 938 | int eTextRep, |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 939 | void*, |
| 940 | void (*xFunc)(sqlite3_context*,int,sqlite3_value**), |
| 941 | void (*xStep)(sqlite3_context*,int,sqlite3_value**), |
| 942 | void (*xFinal)(sqlite3_context*) |
| 943 | ); |
| 944 | |
| 945 | /* |
danielk1977 | 6590493 | 2004-05-26 06:18:37 +0000 | [diff] [blame] | 946 | ** The next routine returns the number of calls to xStep for a particular |
| 947 | ** aggregate function instance. The current call to xStep counts so this |
| 948 | ** routine always returns at least 1. |
| 949 | */ |
| 950 | int sqlite3_aggregate_count(sqlite3_context*); |
| 951 | |
danielk1977 | 0ffba6b | 2004-05-24 09:10:10 +0000 | [diff] [blame] | 952 | /* |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 953 | ** The next group of routines returns information about parameters to |
| 954 | ** a user-defined function. Function implementations use these routines |
| 955 | ** to access their parameters. These routines are the same as the |
| 956 | ** sqlite3_column_* routines except that these routines take a single |
| 957 | ** sqlite3_value* pointer instead of an sqlite3_stmt* and an integer |
| 958 | ** column number. |
danielk1977 | 0ffba6b | 2004-05-24 09:10:10 +0000 | [diff] [blame] | 959 | */ |
drh | f447950 | 2004-05-27 03:12:53 +0000 | [diff] [blame] | 960 | const void *sqlite3_value_blob(sqlite3_value*); |
| 961 | int sqlite3_value_bytes(sqlite3_value*); |
| 962 | int sqlite3_value_bytes16(sqlite3_value*); |
| 963 | double sqlite3_value_double(sqlite3_value*); |
| 964 | int sqlite3_value_int(sqlite3_value*); |
drh | efad999 | 2004-06-22 12:13:55 +0000 | [diff] [blame] | 965 | sqlite_int64 sqlite3_value_int64(sqlite3_value*); |
drh | f447950 | 2004-05-27 03:12:53 +0000 | [diff] [blame] | 966 | const unsigned char *sqlite3_value_text(sqlite3_value*); |
| 967 | const void *sqlite3_value_text16(sqlite3_value*); |
danielk1977 | d812336 | 2004-06-12 09:25:12 +0000 | [diff] [blame] | 968 | const void *sqlite3_value_text16le(sqlite3_value*); |
| 969 | const void *sqlite3_value_text16be(sqlite3_value*); |
danielk1977 | 93d4675 | 2004-05-23 13:30:58 +0000 | [diff] [blame] | 970 | int sqlite3_value_type(sqlite3_value*); |
danielk1977 | 0ffba6b | 2004-05-24 09:10:10 +0000 | [diff] [blame] | 971 | |
| 972 | /* |
danielk1977 | 0ae8b83 | 2004-05-25 12:05:56 +0000 | [diff] [blame] | 973 | ** Aggregate functions use the following routine to allocate |
| 974 | ** a structure for storing their state. The first time this routine |
| 975 | ** is called for a particular aggregate, a new structure of size nBytes |
| 976 | ** is allocated, zeroed, and returned. On subsequent calls (for the |
| 977 | ** same aggregate instance) the same buffer is returned. The implementation |
| 978 | ** of the aggregate can use the returned buffer to accumulate data. |
| 979 | ** |
| 980 | ** The buffer allocated is freed automatically by SQLite. |
| 981 | */ |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 982 | void *sqlite3_aggregate_context(sqlite3_context*, int nBytes); |
danielk1977 | 7e18c25 | 2004-05-25 11:47:24 +0000 | [diff] [blame] | 983 | |
| 984 | /* |
| 985 | ** The pUserData parameter to the sqlite3_create_function() and |
| 986 | ** sqlite3_create_aggregate() routines used to register user functions |
| 987 | ** is available to the implementation of the function using this |
| 988 | ** call. |
| 989 | */ |
| 990 | void *sqlite3_user_data(sqlite3_context*); |
| 991 | |
| 992 | /* |
danielk1977 | 682f68b | 2004-06-05 10:22:17 +0000 | [diff] [blame] | 993 | ** The following two functions may be used by scalar user functions to |
| 994 | ** associate meta-data with argument values. If the same value is passed to |
| 995 | ** multiple invocations of the user-function during query execution, under |
| 996 | ** some circumstances the associated meta-data may be preserved. This may |
| 997 | ** be used, for example, to add a regular-expression matching scalar |
| 998 | ** function. The compiled version of the regular expression is stored as |
| 999 | ** meta-data associated with the SQL value passed as the regular expression |
| 1000 | ** pattern. |
| 1001 | ** |
| 1002 | ** Calling sqlite3_get_auxdata() returns a pointer to the meta data |
| 1003 | ** associated with the Nth argument value to the current user function |
| 1004 | ** call, where N is the second parameter. If no meta-data has been set for |
| 1005 | ** that value, then a NULL pointer is returned. |
| 1006 | ** |
| 1007 | ** The sqlite3_set_auxdata() is used to associate meta data with a user |
| 1008 | ** function argument. The third parameter is a pointer to the meta data |
| 1009 | ** to be associated with the Nth user function argument value. The fourth |
| 1010 | ** parameter specifies a 'delete function' that will be called on the meta |
| 1011 | ** data pointer to release it when it is no longer required. If the delete |
| 1012 | ** function pointer is NULL, it is not invoked. |
| 1013 | ** |
| 1014 | ** In practice, meta-data is preserved between function calls for |
| 1015 | ** expressions that are constant at compile time. This includes literal |
| 1016 | ** values and SQL variables. |
| 1017 | */ |
| 1018 | void *sqlite3_get_auxdata(sqlite3_context*, int); |
| 1019 | void sqlite3_set_auxdata(sqlite3_context*, int, void*, void (*)(void*)); |
| 1020 | |
drh | a285422 | 2004-06-17 19:04:17 +0000 | [diff] [blame] | 1021 | |
| 1022 | /* |
| 1023 | ** These are special value for the destructor that is passed in as the |
| 1024 | ** final argument to routines like sqlite3_result_blob(). If the destructor |
| 1025 | ** argument is SQLITE_STATIC, it means that the content pointer is constant |
| 1026 | ** and will never change. It does not need to be destroyed. The |
| 1027 | ** SQLITE_TRANSIENT value means that the content will likely change in |
| 1028 | ** the near future and that SQLite should make its own private copy of |
| 1029 | ** the content before returning. |
| 1030 | */ |
danielk1977 | d812336 | 2004-06-12 09:25:12 +0000 | [diff] [blame] | 1031 | #define SQLITE_STATIC ((void(*)(void *))0) |
| 1032 | #define SQLITE_TRANSIENT ((void(*)(void *))-1) |
| 1033 | |
danielk1977 | 682f68b | 2004-06-05 10:22:17 +0000 | [diff] [blame] | 1034 | /* |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 1035 | ** User-defined functions invoke the following routines in order to |
| 1036 | ** set their return value. |
danielk1977 | 7e18c25 | 2004-05-25 11:47:24 +0000 | [diff] [blame] | 1037 | */ |
danielk1977 | d812336 | 2004-06-12 09:25:12 +0000 | [diff] [blame] | 1038 | void sqlite3_result_blob(sqlite3_context*, const void*, int, void(*)(void*)); |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 1039 | void sqlite3_result_double(sqlite3_context*, double); |
danielk1977 | 7e18c25 | 2004-05-25 11:47:24 +0000 | [diff] [blame] | 1040 | void sqlite3_result_error(sqlite3_context*, const char*, int); |
| 1041 | void sqlite3_result_error16(sqlite3_context*, const void*, int); |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 1042 | void sqlite3_result_int(sqlite3_context*, int); |
drh | efad999 | 2004-06-22 12:13:55 +0000 | [diff] [blame] | 1043 | void sqlite3_result_int64(sqlite3_context*, sqlite_int64); |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 1044 | void sqlite3_result_null(sqlite3_context*); |
danielk1977 | d812336 | 2004-06-12 09:25:12 +0000 | [diff] [blame] | 1045 | void sqlite3_result_text(sqlite3_context*, const char*, int, void(*)(void*)); |
| 1046 | void sqlite3_result_text16(sqlite3_context*, const void*, int, void(*)(void*)); |
| 1047 | void sqlite3_result_text16le(sqlite3_context*, const void*, int,void(*)(void*)); |
| 1048 | void sqlite3_result_text16be(sqlite3_context*, const void*, int,void(*)(void*)); |
drh | 4f26d6c | 2004-05-26 23:25:30 +0000 | [diff] [blame] | 1049 | void sqlite3_result_value(sqlite3_context*, sqlite3_value*); |
drh | f9b596e | 2004-05-26 16:54:42 +0000 | [diff] [blame] | 1050 | |
drh | 52619df | 2004-06-11 17:48:02 +0000 | [diff] [blame] | 1051 | /* |
| 1052 | ** These are the allowed values for the eTextRep argument to |
| 1053 | ** sqlite3_create_collation and sqlite3_create_function. |
| 1054 | */ |
danielk1977 | 466be56 | 2004-06-10 02:16:01 +0000 | [diff] [blame] | 1055 | #define SQLITE_UTF8 1 |
danielk1977 | dc8453f | 2004-06-12 00:42:34 +0000 | [diff] [blame] | 1056 | #define SQLITE_UTF16LE 2 |
| 1057 | #define SQLITE_UTF16BE 3 |
| 1058 | #define SQLITE_UTF16 4 /* Use native byte order */ |
drh | 52619df | 2004-06-11 17:48:02 +0000 | [diff] [blame] | 1059 | #define SQLITE_ANY 5 /* sqlite3_create_function only */ |
danielk1977 | 466be56 | 2004-06-10 02:16:01 +0000 | [diff] [blame] | 1060 | |
danielk1977 | 7cedc8d | 2004-06-10 10:50:08 +0000 | [diff] [blame] | 1061 | /* |
| 1062 | ** These two functions are used to add new collation sequences to the |
| 1063 | ** sqlite3 handle specified as the first argument. |
| 1064 | ** |
| 1065 | ** The name of the new collation sequence is specified as a UTF-8 string |
| 1066 | ** for sqlite3_create_collation() and a UTF-16 string for |
| 1067 | ** sqlite3_create_collation16(). In both cases the name is passed as the |
| 1068 | ** second function argument. |
| 1069 | ** |
| 1070 | ** The third argument must be one of the constants SQLITE_UTF8, |
| 1071 | ** SQLITE_UTF16LE or SQLITE_UTF16BE, indicating that the user-supplied |
| 1072 | ** routine expects to be passed pointers to strings encoded using UTF-8, |
| 1073 | ** UTF-16 little-endian or UTF-16 big-endian respectively. |
| 1074 | ** |
| 1075 | ** A pointer to the user supplied routine must be passed as the fifth |
| 1076 | ** argument. If it is NULL, this is the same as deleting the collation |
| 1077 | ** sequence (so that SQLite cannot call it anymore). Each time the user |
| 1078 | ** supplied function is invoked, it is passed a copy of the void* passed as |
| 1079 | ** the fourth argument to sqlite3_create_collation() or |
| 1080 | ** sqlite3_create_collation16() as its first parameter. |
| 1081 | ** |
| 1082 | ** The remaining arguments to the user-supplied routine are two strings, |
| 1083 | ** each represented by a [length, data] pair and encoded in the encoding |
| 1084 | ** that was passed as the third argument when the collation sequence was |
| 1085 | ** registered. The user routine should return negative, zero or positive if |
| 1086 | ** the first string is less than, equal to, or greater than the second |
| 1087 | ** string. i.e. (STRING1 - STRING2). |
| 1088 | */ |
danielk1977 | 0202b29 | 2004-06-09 09:55:16 +0000 | [diff] [blame] | 1089 | int sqlite3_create_collation( |
| 1090 | sqlite3*, |
| 1091 | const char *zName, |
danielk1977 | 7cedc8d | 2004-06-10 10:50:08 +0000 | [diff] [blame] | 1092 | int eTextRep, |
danielk1977 | 0202b29 | 2004-06-09 09:55:16 +0000 | [diff] [blame] | 1093 | void*, |
| 1094 | int(*xCompare)(void*,int,const void*,int,const void*) |
| 1095 | ); |
| 1096 | int sqlite3_create_collation16( |
| 1097 | sqlite3*, |
| 1098 | const char *zName, |
danielk1977 | 7cedc8d | 2004-06-10 10:50:08 +0000 | [diff] [blame] | 1099 | int eTextRep, |
danielk1977 | 0202b29 | 2004-06-09 09:55:16 +0000 | [diff] [blame] | 1100 | void*, |
| 1101 | int(*xCompare)(void*,int,const void*,int,const void*) |
| 1102 | ); |
| 1103 | |
danielk1977 | 7cedc8d | 2004-06-10 10:50:08 +0000 | [diff] [blame] | 1104 | /* |
| 1105 | ** To avoid having to register all collation sequences before a database |
| 1106 | ** can be used, a single callback function may be registered with the |
| 1107 | ** database handle to be called whenever an undefined collation sequence is |
| 1108 | ** required. |
| 1109 | ** |
| 1110 | ** If the function is registered using the sqlite3_collation_needed() API, |
| 1111 | ** then it is passed the names of undefined collation sequences as strings |
| 1112 | ** encoded in UTF-8. If sqlite3_collation_needed16() is used, the names |
| 1113 | ** are passed as UTF-16 in machine native byte order. A call to either |
| 1114 | ** function replaces any existing callback. |
| 1115 | ** |
| 1116 | ** When the user-function is invoked, the first argument passed is a copy |
| 1117 | ** of the second argument to sqlite3_collation_needed() or |
| 1118 | ** sqlite3_collation_needed16(). The second argument is the database |
| 1119 | ** handle. The third argument is one of SQLITE_UTF8, SQLITE_UTF16BE or |
| 1120 | ** SQLITE_UTF16LE, indicating the most desirable form of the collation |
| 1121 | ** sequence function required. The fourth parameter is the name of the |
| 1122 | ** required collation sequence. |
| 1123 | ** |
| 1124 | ** The collation sequence is returned to SQLite by a collation-needed |
| 1125 | ** callback using the sqlite3_create_collation() or |
| 1126 | ** sqlite3_create_collation16() APIs, described above. |
| 1127 | */ |
| 1128 | int sqlite3_collation_needed( |
| 1129 | sqlite3*, |
| 1130 | void*, |
| 1131 | void(*)(void*,sqlite3*,int eTextRep,const char*) |
| 1132 | ); |
| 1133 | int sqlite3_collation_needed16( |
| 1134 | sqlite3*, |
| 1135 | void*, |
| 1136 | void(*)(void*,sqlite3*,int eTextRep,const void*) |
| 1137 | ); |
| 1138 | |
drh | 2011d5f | 2004-07-22 02:40:37 +0000 | [diff] [blame] | 1139 | /* |
| 1140 | ** Specify the key for an encrypted database. This routine should be |
| 1141 | ** called right after sqlite3_open(). |
| 1142 | ** |
| 1143 | ** The code to implement this API is not available in the public release |
| 1144 | ** of SQLite. |
| 1145 | */ |
| 1146 | int sqlite3_key( |
| 1147 | sqlite3 *db, /* Database to be rekeyed */ |
| 1148 | const void *pKey, int nKey /* The key */ |
| 1149 | ); |
| 1150 | |
| 1151 | /* |
| 1152 | ** Change the key on an open database. If the current database is not |
| 1153 | ** encrypted, this routine will encrypt it. If pNew==0 or nNew==0, the |
| 1154 | ** database is decrypted. |
| 1155 | ** |
| 1156 | ** The code to implement this API is not available in the public release |
| 1157 | ** of SQLite. |
| 1158 | */ |
| 1159 | int sqlite3_rekey( |
| 1160 | sqlite3 *db, /* Database to be rekeyed */ |
| 1161 | const void *pKey, int nKey /* The new key */ |
| 1162 | ); |
danielk1977 | 0202b29 | 2004-06-09 09:55:16 +0000 | [diff] [blame] | 1163 | |
drh | ab3f9fe | 2004-08-14 17:10:10 +0000 | [diff] [blame] | 1164 | /* |
danielk1977 | 600dd0b | 2005-01-20 01:14:23 +0000 | [diff] [blame] | 1165 | ** Sleep for a little while. The second parameter is the number of |
| 1166 | ** miliseconds to sleep for. |
| 1167 | ** |
| 1168 | ** If the operating system does not support sleep requests with |
| 1169 | ** milisecond time resolution, then the time will be rounded up to |
| 1170 | ** the nearest second. The number of miliseconds of sleep actually |
| 1171 | ** requested from the operating system is returned. |
| 1172 | ** |
| 1173 | ******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ****** |
| 1174 | */ |
| 1175 | int sqlite3_sleep(int); |
| 1176 | |
| 1177 | /* |
drh | d89bd00 | 2005-01-22 03:03:54 +0000 | [diff] [blame^] | 1178 | ** Return TRUE (non-zero) of the statement supplied as an argument needs |
| 1179 | ** to be recompiled. A statement needs to be recompiled whenever the |
| 1180 | ** execution environment changes in a way that would alter the program |
| 1181 | ** that sqlite3_prepare() generates. For example, if new functions or |
| 1182 | ** collating sequences are registered or if an authorizer function is |
| 1183 | ** added or changed. |
| 1184 | ** |
| 1185 | ******* THIS IS AN EXPERIMENTAL API AND IS SUBJECT TO CHANGE ****** |
| 1186 | */ |
| 1187 | int sqlite3_expired(sqlite3_stmt*); |
| 1188 | |
| 1189 | /* |
tpoindex | 9a09a3c | 2004-12-20 19:01:32 +0000 | [diff] [blame] | 1190 | ** If the following global variable is made to point to a |
drh | ab3f9fe | 2004-08-14 17:10:10 +0000 | [diff] [blame] | 1191 | ** string which is the name of a directory, then all temporary files |
| 1192 | ** created by SQLite will be placed in that directory. If this variable |
| 1193 | ** is NULL pointer, then SQLite does a search for an appropriate temporary |
| 1194 | ** file directory. |
| 1195 | ** |
tpoindex | 9a09a3c | 2004-12-20 19:01:32 +0000 | [diff] [blame] | 1196 | ** Once sqlite3_open() has been called, changing this variable will invalidate the |
| 1197 | ** current temporary database, if any. |
drh | ab3f9fe | 2004-08-14 17:10:10 +0000 | [diff] [blame] | 1198 | */ |
tpoindex | 9a09a3c | 2004-12-20 19:01:32 +0000 | [diff] [blame] | 1199 | extern char *sqlite3_temp_directory; |
drh | ab3f9fe | 2004-08-14 17:10:10 +0000 | [diff] [blame] | 1200 | |
drh | 382c024 | 2001-10-06 16:33:02 +0000 | [diff] [blame] | 1201 | #ifdef __cplusplus |
| 1202 | } /* End of the 'extern "C"' block */ |
| 1203 | #endif |
danielk1977 | 4adee20 | 2004-05-08 08:23:19 +0000 | [diff] [blame] | 1204 | #endif |