Documentation Source Text

Check-in [83b8745219]
Login

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

Overview
Comment:Fix a minor typo in the transaction documentation.
Timelines: family | ancestors | descendants | both | branch-3.29
Files: files | file ages | folders
SHA3-256: 83b87452198f5de1e00449ef819c318f00df7c7932bb4631257f6c1f77d39ace
User & Date: drh 2019-09-20 17:37:30
Context
2019-09-24
10:30
Use single-quoted strings in the documention for PRAGMA encoding. check-in: 4c6aa056b7 user: drh tags: branch-3.29
2019-09-20
17:37
Fix a minor typo in the transaction documentation. check-in: 83b8745219 user: drh tags: branch-3.29
2019-09-13
17:55
Fix a bug in the documentation generator for PRAGMAs. check-in: d83262cc8b user: drh tags: branch-3.29
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/lang.in.

741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
not a transaction started by BEGIN) is committed automatically when
the last active statement finishes.  A statement finishes when its
last cursor closes, which is guaranteed to happen when the
prepared statement is [sqlite3_reset() | reset] or
[sqlite3_finalize() | finalized].  Some statements might "finish"
for the purpose of transaction control prior to being reset or finalized,
but there is no guarantee of this.  The only way to ensure that a
statement as "finished" is to invoke [sqlite3_reset()] or
[sqlite3_finalize()] on that statement.  An open [sqlite3_blob] used for
incremental BLOB I/O also counts as an unfinished statement.
The [sqlite3_blob] finishes when it is [sqlite3_blob_close() | closed].
</p>

<p>
^The explicit COMMIT command runs immediately, even if there are







|







741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
not a transaction started by BEGIN) is committed automatically when
the last active statement finishes.  A statement finishes when its
last cursor closes, which is guaranteed to happen when the
prepared statement is [sqlite3_reset() | reset] or
[sqlite3_finalize() | finalized].  Some statements might "finish"
for the purpose of transaction control prior to being reset or finalized,
but there is no guarantee of this.  The only way to ensure that a
statement has "finished" is to invoke [sqlite3_reset()] or
[sqlite3_finalize()] on that statement.  An open [sqlite3_blob] used for
incremental BLOB I/O also counts as an unfinished statement.
The [sqlite3_blob] finishes when it is [sqlite3_blob_close() | closed].
</p>

<p>
^The explicit COMMIT command runs immediately, even if there are