/ Check-in [f494ed38]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Remove all mention of sqlite3_next_stmt() from the documentation of sqlite3_close().
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: f494ed38a8d3fabb7a064ba4a860d5288c5a571b
User & Date: drh 2009-10-20 14:23:09
References
2009-10-20
14:24 Fixed ticket [1751725c]: sqlite_close doc should qualify advice plus 3 other changes artifact: 27fd2602 user: drh
Context
2009-10-20
15:01
Fix the VACUUM command so that when the MAIN and TEMP databases have identically named tables, content from the TEMP database does not accidently overwrite MAIN database content. Ticket [d82e3f3721296e905d7e8c9dee718f71a826b0eb]. Note that this bug could potentially lead to database corruption. check-in: 0bbd8d72 user: drh tags: trunk
14:23
Remove all mention of sqlite3_next_stmt() from the documentation of sqlite3_close(). check-in: f494ed38 user: drh tags: trunk
14:08
Update documentation on the sqlite3_prepare_v2() interface. No changes to code. check-in: 3b00e769 user: drh tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to src/sqlite.h.in.

   236    236   #endif
   237    237   
   238    238   /*
   239    239   ** CAPI3REF: Closing A Database Connection {H12010} <S30100><S40200>
   240    240   **
   241    241   ** This routine is the destructor for the [sqlite3] object.
   242    242   **
   243         -** Applications should [sqlite3_finalize | finalize] all [prepared statements]
          243  +** Applications must [sqlite3_finalize | finalize] all [prepared statements]
   244    244   ** and [sqlite3_blob_close | close] all [BLOB handles] associated with
   245    245   ** the [sqlite3] object prior to attempting to close the object.
   246         -** The [sqlite3_next_stmt()] interface can be used to locate all
   247         -** [prepared statements] associated with a [database connection] if desired.
   248         -** Typical code might look like this:
   249         -**
   250         -** <blockquote><pre>
   251         -** sqlite3_stmt *pStmt;
   252         -** while( (pStmt = sqlite3_next_stmt(db, 0))!=0 ){
   253         -** &nbsp;   sqlite3_finalize(pStmt);
   254         -** }
   255         -** </pre></blockquote>
   256    246   **
   257    247   ** If [sqlite3_close()] is invoked while a transaction is open,
   258    248   ** the transaction is automatically rolled back.
   259    249   **
   260    250   ** The C parameter to [sqlite3_close(C)] must be either a NULL
   261    251   ** pointer or an [sqlite3] object pointer obtained
   262    252   ** from [sqlite3_open()], [sqlite3_open16()], or