requirements.html

这是sqlite3.56的文档。拿来给大家阅读使用

#define SQLITE_CREATE_TEMP_TRIGGER   5   /* Trigger Name    Table Name      */
#define SQLITE_CREATE_TEMP_VIEW      6   /* View Name       NULL            */
#define SQLITE_CREATE_TRIGGER        7   /* Trigger Name    Table Name      */
#define SQLITE_CREATE_VIEW           8   /* View Name       NULL            */
#define SQLITE_DELETE                9   /* Table Name      NULL            */
#define SQLITE_DROP_INDEX           10   /* Index Name      Table Name      */
#define SQLITE_DROP_TABLE           11   /* Table Name      NULL            */
#define SQLITE_DROP_TEMP_INDEX      12   /* Index Name      Table Name      */
#define SQLITE_DROP_TEMP_TABLE      13   /* Table Name      NULL            */
#define SQLITE_DROP_TEMP_TRIGGER    14   /* Trigger Name    Table Name      */
#define SQLITE_DROP_TEMP_VIEW       15   /* View Name       NULL            */
#define SQLITE_DROP_TRIGGER         16   /* Trigger Name    Table Name      */
#define SQLITE_DROP_VIEW            17   /* View Name       NULL            */
#define SQLITE_INSERT               18   /* Table Name      NULL            */
#define SQLITE_PRAGMA               19   /* Pragma Name     1st arg or NULL */
#define SQLITE_READ                 20   /* Table Name      Column Name     */
#define SQLITE_SELECT               21   /* NULL            NULL            */
#define SQLITE_TRANSACTION          22   /* NULL            NULL            */
#define SQLITE_UPDATE               23   /* Table Name      Column Name     */
#define SQLITE_ATTACH               24   /* Filename        NULL            */
#define SQLITE_DETACH               25   /* Database Name   NULL            */
#define SQLITE_ALTER_TABLE          26   /* Database Name   Table Name      */
#define SQLITE_REINDEX              27   /* Index Name      NULL            */
#define SQLITE_ANALYZE              28   /* Table Name      NULL            */
#define SQLITE_CREATE_VTABLE        29   /* Table Name      Module Name     */
#define SQLITE_DROP_VTABLE          30   /* Table Name      Module Name     */
#define SQLITE_FUNCTION             31   /* Function Name   NULL            */
#define SQLITE_COPY                  0   /* No longer used */

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12551</td><td valign="top">
The second parameter to an

<a href="c3ref/set_authorizer.html">authorizer callback is always an integer
[SQLITE_COPY</a> that specifies what action
is being authorized.
</td></tr>
<tr><td valign="top">F12552</td><td valign="top">
The 3rd and 4th parameters to the

<a href="c3ref/set_authorizer.html">authorization callback function</a>
will be parameters or NULL depending on which

<a href="c3ref/c_alter_table.html">authorizer code</a> is used as the second parameter.
</td></tr>
<tr><td valign="top">F12553</td><td valign="top">
The 5th parameter to the

<a href="c3ref/set_authorizer.html">authorizer callback</a> is the name
of the database (example: "main", "temp", etc.) if applicable.
</td></tr>
<tr><td valign="top">F12554</td><td valign="top">
The 6th parameter to the

<a href="c3ref/set_authorizer.html">authorizer callback</a> is the name
of the inner-most trigger or view that is responsible for
the access attempt or NULL if this access attempt is directly from
top-level SQL code.
</td></tr>
<tr><td valign="top">F12590</td><td valign="top">
The sqlite3.h header file defines the following interfaces:
<blockquote><pre>
#define SQLITE_DENY   1   /* Abort the SQL statement with an error */
#define SQLITE_IGNORE 2   /* Don't allow access, but don't generate an error */

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12600</td><td valign="top">
The sqlite3.h header file defines the following interfaces:
<blockquote><pre>
int sqlite3_load_extension(
  sqlite3 *db,          /* Load the extension into this database connection */
  const char *zFile,    /* Name of the shared library containing extension */
  const char *zProc,    /* Entry point.  Derived from zFile if 0 */
  char **pzErrMsg       /* Put error message here if not 0 */
);

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12620</td><td valign="top">
The sqlite3.h header file defines the following interfaces:
<blockquote><pre>
int sqlite3_enable_load_extension(sqlite3 *db, int onoff);

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12640</td><td valign="top">
The sqlite3.h header file defines the following interfaces:
<blockquote><pre>
int sqlite3_auto_extension(void *xEntryPoint);

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12660</td><td valign="top">
The sqlite3.h header file defines the following interfaces:
<blockquote><pre>
void sqlite3_reset_auto_extension(void);

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12700</td><td valign="top">
The sqlite3.h header file defines the following interfaces:
<blockquote><pre>
int sqlite3_open(
  const char *filename,   /* Database filename (UTF-8) */
  sqlite3 **ppDb          /* OUT: SQLite db handle */
);
int sqlite3_open16(
  const void *filename,   /* Database filename (UTF-16) */
  sqlite3 **ppDb          /* OUT: SQLite db handle */
);
int sqlite3_open_v2(
  const char *filename,   /* Database filename (UTF-8) */
  sqlite3 **ppDb,         /* OUT: SQLite db handle */
  int flags,              /* Flags */
  const char *zVfs        /* Name of VFS module to use */
);

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12701</td><td valign="top">
The 
<a href="c3ref/open.html">sqlite3_open()</a>, 
<a href="c3ref/open.html">sqlite3_open16()</a>, and

<a href="c3ref/open.html">sqlite3_open_v2()</a> interfaces create a new

<a href="c3ref/sqlite3.html">database connection</a> associated with
the database file given in their first parameter.
</td></tr>
<tr><td valign="top">F12702</td><td valign="top">
The filename argument is interpreted as UTF-8
for 
<a href="c3ref/open.html">sqlite3_open()</a> and 
<a href="c3ref/open.html">sqlite3_open_v2()</a> and as UTF-16
in the native byte order for 
<a href="c3ref/open.html">sqlite3_open16()</a>.
</td></tr>
<tr><td valign="top">F12703</td><td valign="top">
A successful invocation of 
<a href="c3ref/open.html">sqlite3_open()</a>, 
<a href="c3ref/open.html">sqlite3_open16()</a>,
or 
<a href="c3ref/open.html">sqlite3_open_v2()</a> writes a pointer to a new

<a href="c3ref/sqlite3.html">database connection</a> into *ppDb.
</td></tr>
<tr><td valign="top">F12704</td><td valign="top">
The 
<a href="c3ref/open.html">sqlite3_open()</a>, 
<a href="c3ref/open.html">sqlite3_open16()</a>, and

<a href="c3ref/open.html">sqlite3_open_v2()</a> interfaces return 
<a href="c3ref/c_abort.html">SQLITE_OK</a> upon success,
or an appropriate 
<a href="c3ref/c_abort.html">error code</a> on failure.
</td></tr>
<tr><td valign="top">F12706</td><td valign="top">
The default text encoding for a new database created using

<a href="c3ref/open.html">sqlite3_open()</a> or 
<a href="c3ref/open.html">sqlite3_open_v2()</a> will be UTF-8.
</td></tr>
<tr><td valign="top">F12707</td><td valign="top">
The default text encoding for a new database created using

<a href="c3ref/open.html">sqlite3_open16()</a> will be UTF-16.
</td></tr>
<tr><td valign="top">F12709</td><td valign="top">
The 
<a href="c3ref/open.html">sqlite3_open(F,D)</a> interface is equivalent to

<a href="c3ref/open.html">sqlite3_open_v2(F,D,G,0)</a> where the G parameter is

<a href="c3ref/c_open_create.html">SQLITE_OPEN_READWRITE</a>|
<a href="c3ref/c_open_create.html">SQLITE_OPEN_CREATE</a>.
</td></tr>
<tr><td valign="top">F12711</td><td valign="top">
If the G parameter to 
<a href="c3ref/open.html">sqlite3_open_v2(F,D,G,V)</a> contains the
bit value 
<a href="c3ref/c_open_create.html">SQLITE_OPEN_READONLY</a> then the database is opened
for reading only.
</td></tr>
<tr><td valign="top">F12712</td><td valign="top">
If the G parameter to 
<a href="c3ref/open.html">sqlite3_open_v2(F,D,G,V)</a> contains the
bit value 
<a href="c3ref/c_open_create.html">SQLITE_OPEN_READWRITE</a> then the database is opened
reading and writing if possible, or for reading only if the
file is write protected by the operating system.
</td></tr>
<tr><td valign="top">F12713</td><td valign="top">
If the G parameter to 
<a href="c3ref/open.html">sqlite3_open(v2(F,D,G,V)</a> omits the
bit value 
<a href="c3ref/c_open_create.html">SQLITE_OPEN_CREATE</a> and the database does not
previously exist, an error is returned.
</td></tr>
<tr><td valign="top">F12714</td><td valign="top">
If the G parameter to 
<a href="c3ref/open.html">sqlite3_open(v2(F,D,G,V)</a> contains the
bit value 
<a href="c3ref/c_open_create.html">SQLITE_OPEN_CREATE</a> and the database does not
previously exist, then an attempt is made to create and
initialize the database.
</td></tr>
<tr><td valign="top">F12717</td><td valign="top">
If the filename argument to 
<a href="c3ref/open.html">sqlite3_open()</a>, 
<a href="c3ref/open.html">sqlite3_open16()</a>,
or 
<a href="c3ref/open.html">sqlite3_open_v2()</a> is ":memory:", then an private,
ephemeral, in-memory database is created for the connection.
<todo>Is SQLITE_OPEN_CREATE|SQLITE_OPEN_READWRITE required
in sqlite3_open_v2()?</todo>
</td></tr>
<tr><td valign="top">F12719</td><td valign="top">
If the filename is an empty string, then a private, ephermeral
on-disk database will be created.
<todo>Is SQLITE_OPEN_CREATE|SQLITE_OPEN_READWRITE required
in sqlite3_open_v2()?</todo>
</td></tr>
<tr><td valign="top">F12721</td><td valign="top">
The 
<a href="c3ref/sqlite3.html">database connection</a> created by

<a href="c3ref/open.html">sqlite3_open_v2(F,D,G,V)</a> will use the

<a href="c3ref/vfs.html">sqlite3_vfs</a> object identified by the V parameter, or
the default 
<a href="c3ref/vfs.html">sqlite3_vfs</a> object is V is a NULL pointer.
</td></tr>
<tr><td valign="top">F12800</td><td valign="top">
The sqlite3.h header file defines the following interfaces:
<blockquote><pre>
int sqlite3_errcode(sqlite3 *db);
const char *sqlite3_errmsg(sqlite3*);
const void *sqlite3_errmsg16(sqlite3*);

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12801</td><td valign="top">
The 
<a href="c3ref/errcode.html">sqlite3_errcode(D)</a> interface returns the numeric

<a href="c3ref/c_abort.html">result code</a> or

<a href="c3ref/c_ioerr_blocked.html">extended result code</a>
for the most recent failed interface call associated
with 
<a href="c3ref/sqlite3.html">sqlite3</a> handle D.
</td></tr>
<tr><td valign="top">F12803</td><td valign="top">
The 
<a href="c3ref/errcode.html">sqlite3_errmsg(D)</a> and 
<a href="c3ref/errcode.html">sqlite3_errmsg16(D)</a>
interfaces return English-language text that describes
the error in the mostly recently failed interface call,
encoded as either UTF8 or UTF16 respectively.
</td></tr>
<tr><td valign="top">F12807</td><td valign="top">
Calls to 
<a href="c3ref/errcode.html">sqlite3_errcode()</a>, 
<a href="c3ref/errcode.html">sqlite3_errmsg()</a>, and

<a href="c3ref/errcode.html">sqlite3_errmsg16()</a> themselves do not affect the
results of future invocations of these routines.
</td></tr>
<tr><td valign="top">F12808</td><td valign="top">
Calls to API routines that do not return an error code
(example: 
<a href="c3ref/data_count.html">sqlite3_data_count()</a>) do not
change the error code or message returned by

<a href="c3ref/errcode.html">sqlite3_errcode()</a>, 
<a href="c3ref/errcode.html">sqlite3_errmsg()</a>, or 
<a href="c3ref/errcode.html">sqlite3_errmsg16()</a>.
</td></tr>
<tr><td valign="top">F12809</td><td valign="top">
Interfaces that are not associated with a specific

<a href="c3ref/sqlite3.html">database connection</a> (examples:

<a href="c3ref/mprintf.html">sqlite3_mprintf()</a> or 
<a href="c3ref/enable_shared_cache.html">sqlite3_enable_shared_cache()</a>
do not change the values returned by

<a href="c3ref/errcode.html">sqlite3_errcode()</a>, 
<a href="c3ref/errcode.html">sqlite3_errmsg()</a>, or 
<a href="c3ref/errcode.html">sqlite3_errmsg16()</a>.
</td></tr>
<tr><td valign="top">F12850</td><td valign="top">
The sqlite3.h header file defines the following interfaces:
<blockquote><pre>
int sqlite3_table_column_metadata(
  sqlite3 *db,                /* Connection handle */
  const char *zDbName,        /* Database name or NULL */
  const char *zTableName,     /* Table name */
  const char *zColumnName,    /* Column name */
  char const **pzDataType,    /* OUTPUT: Declared data type */
  char const **pzCollSeq,     /* OUTPUT: Collation sequence name */
  int *pNotNull,              /* OUTPUT: True if NOT NULL constraint exists */
  int *pPrimaryKey,           /* OUTPUT: True if column part of PK */
  int *pAutoinc               /* OUTPUT: True if column is auto-increment */
);

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12910</td><td valign="top">
The sqlite3.h header file defines the following interfaces:
<blockquote><pre>
void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);

</pre></blockquote>
</td></tr>
<tr><td valign="top">F12911</td><td valign="top">
The callback function registered by 
<a href="c3ref/progress_handler.html">sqlite3_progress_handler()</a>
is invoked periodically during long running calls to

<a href="c3ref/step.html">sqlite3_step()</a>.
</td></tr>
<tr><td valign="top">F12912</td><td valign="top">
The progress callback is invoked once for every N virtual
machine opcodes, where N is the second argument to
the 
<a href="c3ref/progress_handler.html">sqlite3_progress_handler()</a> call that registered
the callback.  <todo>What if N is less than 1?</todo>
</td></tr>
<tr><td valign="top">F12913</td><td valign="top">
The progress callback itself is identified by the third
argument to 
<a href="c3ref/progress_handler.html">sqlite3_progress_handler()</a>.
</td></tr>
<tr><td valign="top">F12914</td><td valign="top">
The fourth argument 
<a href="c3ref/progress_handler.html">sqlite3_progress_handler()</a> is a