Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add a few extra words to the sqlite3_finalize() documentation. (CVS 4024) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
315dc71b921ffba514271a2ed571d5f4 |
User & Date: | danielk1977 2007-05-19 06:48:43.000 |
Context
2007-05-19
| ||
11:50 | Add the larger SQLite icon to the repository. (CVS 4025) (check-in: d7539c6e8b user: drh tags: trunk) | |
06:48 | Add a few extra words to the sqlite3_finalize() documentation. (CVS 4024) (check-in: 315dc71b92 user: danielk1977 tags: trunk) | |
2007-05-17
| ||
18:28 | Change the way overflow pages are allocated from the free-list to increase the chance that they are a contiguous block. Much more can still be done. (CVS 4023) (check-in: b739189204 user: danielk1977 tags: trunk) | |
Changes
Changes to www/capi3ref.tcl.
|
| | | 1 2 3 4 5 6 7 8 | set rcsid {$Id: capi3ref.tcl,v 1.60 2007/05/19 06:48:43 danielk1977 Exp $} source common.tcl header {C/C++ Interface For SQLite Version 3} puts { <h2 class=pdf_section>C/C++ Interface For SQLite Version 3</h2> } proc api {name prototype desc {notused x}} { |
︙ | ︙ | |||
958 959 960 961 962 963 964 965 966 967 968 969 970 971 | } { The sqlite3_finalize() function is called to delete a prepared SQL statement obtained by a previous call to sqlite3_prepare(), sqlite3_prepare_v2(), sqlite3_prepare16(), or sqlite3_prepare16_v2(). If the statement was executed successfully, or not executed at all, then SQLITE_OK is returned. If execution of the statement failed then an error code is returned. All prepared statements must finalized before sqlite3_close() is called or else the close will fail with a return code of SQLITE_BUSY. This routine can be called at any point during the execution of the virtual machine. If the virtual machine has not completed execution when this routine is called, that is like encountering an error or | > > > > | 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 | } { The sqlite3_finalize() function is called to delete a prepared SQL statement obtained by a previous call to sqlite3_prepare(), sqlite3_prepare_v2(), sqlite3_prepare16(), or sqlite3_prepare16_v2(). If the statement was executed successfully, or not executed at all, then SQLITE_OK is returned. If execution of the statement failed then an error code is returned. After sqlite_finalize() has been called, the statement handle is invalidated. Passing it to any other SQLite function may cause a crash. All prepared statements must finalized before sqlite3_close() is called or else the close will fail with a return code of SQLITE_BUSY. This routine can be called at any point during the execution of the virtual machine. If the virtual machine has not completed execution when this routine is called, that is like encountering an error or |
︙ | ︙ |