Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Documentation updates. (CVS 2796) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
2ffb90c39d0b60de9a692326ca3f2595 |
User & Date: | drh 2005-12-02 01:57:43.000 |
Context
2005-12-02
| ||
02:44 | Add a test to verify that binding text with embedded '\000' works. Also comment changes in os.h. (CVS 2797) (check-in: 31251a9098 user: drh tags: trunk) | |
01:57 | Documentation updates. (CVS 2796) (check-in: 2ffb90c39d user: drh tags: trunk) | |
2005-11-30
| ||
03:20 | Restructure the OS interface yet again. This time make the OsFile object a virtual base class which is subclassed for unix, windows, and the crash test simulator. Add the new file "os.c" for common os layer code. Move all OS-specific routines into the sqlite3Os structure. (CVS 2795) (check-in: bd8740d1ae user: drh tags: trunk) | |
Changes
Changes to www/capi3ref.tcl.
|
| | | 1 2 3 4 5 6 7 8 | set rcsid {$Id: capi3ref.tcl,v 1.25 2005/12/02 01:57:43 drh Exp $} source common.tcl header {C/C++ Interface For SQLite Version 3} puts { <h2>C/C++ Interface For SQLite Version 3</h2> } proc api {name prototype desc {notused x}} { |
︙ | ︙ | |||
122 123 124 125 126 127 128 129 130 131 132 133 134 135 | fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its own private copy of the data before returning. The sqlite3_bind_*() routines must be called after sqlite3_prepare() or sqlite3_reset() and before sqlite3_step(). Bindings are not cleared by the sqlite3_reset() routine. Unbound parameters are interpreted as NULL. } api {} { int sqlite3_bind_parameter_count(sqlite3_stmt*); } { Return the number of parameters in the precompiled statement given as the argument. | > > > > > > | 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 | fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its own private copy of the data before returning. The sqlite3_bind_*() routines must be called after sqlite3_prepare() or sqlite3_reset() and before sqlite3_step(). Bindings are not cleared by the sqlite3_reset() routine. Unbound parameters are interpreted as NULL. These routines return SQLITE_OK on success or an error code if anything goes wrong. SQLITE_RANGE is returned if the parameter index is out of range. SQLITE_NOMEM is returned if malloc fails. SQLITE_MISUSE is returned if these routines are called on a virtual machine that is the wrong state or which has already been finalized. } api {} { int sqlite3_bind_parameter_count(sqlite3_stmt*); } { Return the number of parameters in the precompiled statement given as the argument. |
︙ | ︙ |
Changes to www/quickstart.tcl.
1 2 3 | # # Run this TCL script to generate HTML for the quickstart.html file. # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # Run this TCL script to generate HTML for the quickstart.html file. # set rcsid {$Id: quickstart.tcl,v 1.7 2005/12/02 01:57:43 drh Exp $} source common.tcl header {SQLite In 5 Minutes Or Less} puts { <p>Here is what you do to start experimenting with SQLite without having to do a lot of tedious reading and configuration:</p> <h2>Download The Code</h2> |
︙ | ︙ | |||
20 21 22 23 24 25 26 27 28 29 30 31 32 33 | <ul> <li><p>At a shell or DOS prompt, enter: "<b>sqlite3 test.db</b>". This will create a new database named "test.db". (You can use a different name if you like.)</p></li> <li><p>Enter SQL commands at the prompt to create and populate the new database.</p></li> </ul> <h2>Write Programs That Use SQLite</h2> <ul> <li><p>Below is a simple TCL program that demonstrates how to use the TCL interface to SQLite. The program executes the SQL statements | > | 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 | <ul> <li><p>At a shell or DOS prompt, enter: "<b>sqlite3 test.db</b>". This will create a new database named "test.db". (You can use a different name if you like.)</p></li> <li><p>Enter SQL commands at the prompt to create and populate the new database.</p></li> <li><p>Additional documentation is available <a href="sqlite.html">here</a></li> </ul> <h2>Write Programs That Use SQLite</h2> <ul> <li><p>Below is a simple TCL program that demonstrates how to use the TCL interface to SQLite. The program executes the SQL statements |
︙ | ︙ | |||
101 102 103 104 105 106 107 | <b>sqlite3_close</b>(db); return 0; } </pre></blockquote> </li> </ul> } | | | 102 103 104 105 106 107 108 109 | <b>sqlite3_close</b>(db); return 0; } </pre></blockquote> </li> </ul> } footer {$Id: quickstart.tcl,v 1.7 2005/12/02 01:57:43 drh Exp $} |
Changes to www/sqlite.tcl.
1 2 3 | # # Run this Tcl script to generate the sqlite.html file. # | | | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | # # Run this Tcl script to generate the sqlite.html file. # set rcsid {$Id: sqlite.tcl,v 1.23 2005/12/02 01:57:43 drh Exp $} source common.tcl header {sqlite: A command-line access program for SQLite databases} puts { <h2>sqlite: A command-line access program for SQLite databases</h2> <p>The SQLite library includes a simple command-line utility named <b>sqlite</b> that allows the user to manually enter and execute SQL commands against an SQLite database. This document provides a brief introduction on how to use <b>sqlite</b>. <h3>Getting Started</h3> |
︙ | ︙ |