Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix a typo in capi3.tcl. (CVS 1784) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
982389b25d26201116fdfd390aa4b996 |
User & Date: | danielk1977 2004-06-30 13:28:33.000 |
Context
2004-06-30
| ||
14:29 | Specify ASCII versions of Win32 API functions. (CVS 1785) (check-in: 48b31540db user: drh tags: trunk) | |
13:28 | Fix a typo in capi3.tcl. (CVS 1784) (check-in: 982389b25d user: danielk1977 tags: trunk) | |
12:49 | Have the debug version of sqliteRealloc() return partially uninitialised memory in the same way as the non-debug version can. (CVS 1783) (check-in: e78b0ff30f user: danielk1977 tags: trunk) | |
Changes
Changes to www/capi3.tcl.
|
| | | 1 2 3 4 5 6 7 8 | set rcsid {$Id: capi3.tcl,v 1.6 2004/06/30 13:28:33 danielk1977 Exp $} source common.tcl header {C/C++ Interface For SQLite Version 3} puts { <h2>C/C++ Interface For SQLite Version 3</h2> <h3>1.0 Overview</h3> |
︙ | ︙ | |||
42 43 44 45 46 47 48 | to refer to UTF-16 strings. Client software can cast the void* to whatever datatype is appropriate for their system. </p> <h3>2.0 C/C++ Interface</h3> <p> | | | | | | 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 | to refer to UTF-16 strings. Client software can cast the void* to whatever datatype is appropriate for their system. </p> <h3>2.0 C/C++ Interface</h3> <p> The API for SQLite 3.0 includes 83 separate functions in addition to several data structures and #defines. (A complete <a href="capi3ref.html">API reference</a> is provided as a separate document.) Fortunately, the interface is not nearly as complex as its size implies. Simple programs can still make do with only 3 functions: <a href="capi3ref.html#sqlite3_open">sqlite3_open()</a>, <a href="capi3ref.html#sqlite3_exec">sqlite3_exec()</a>, and <a href="capi3ref.html#sqlite3_close">sqlite3_close()</a>. More control over the execution of the database engine is provided using <a href="capi3ref.html#sqlite3_prepare">sqlite3_prepare()</a> to compile an SQLite statement into byte code and <a href="capi3ref.html#sqlite3_prepare">sqlite3_step()</a> to execute that bytecode. A family of routines with names beginning with <a href="capi3ref.html#sqlite3_column_blob">sqlite3_column_</a> is used to extract information about the result set of a query. Many interface functions come in pairs, with both a UTF-8 and UTF-16 version. And there is a collection of routines used to implement user-defined SQL functions and user-defined text collating sequences. </p> <h4>2.1 Opening and closing a database</h4> |
︙ | ︙ | |||
107 108 109 110 111 112 113 | represented in UTF-8 and will be ephemeral - it could disappear on the next call to any SQLite API function. sqlite3_errmsg16() works like sqlite3_errmsg() except that it returns the error message represented as UTF-16 in host native byte order. </p> <p> | | | 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 | represented in UTF-8 and will be ephemeral - it could disappear on the next call to any SQLite API function. sqlite3_errmsg16() works like sqlite3_errmsg() except that it returns the error message represented as UTF-16 in host native byte order. </p> <p> The error codes for SQLite version 3 are unchanged from version 2. They are as follows: </p> <blockquote><pre> #define SQLITE_OK 0 /* Successful result */ #define SQLITE_ERROR 1 /* SQL error or missing database */ #define SQLITE_INTERNAL 2 /* An internal logic error in SQLite */ |
︙ | ︙ |