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