Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Merge branch-3.31 fixes into trunk. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
15a047bc79409af5df915a08574327c1 |
| User & Date: | drh 2020-04-14 22:15:00 |
Context
|
2020-04-20
| ||
| 23:07 | Fix a typo in the CREATE TRIGGER documentation. (check-in: 79b74d138c user: drh tags: trunk) | |
|
2020-04-14
| ||
| 22:15 | Merge branch-3.31 fixes into trunk. (check-in: 15a047bc79 user: drh tags: trunk) | |
| 21:45 | Fix fork on trunk. (check-in: a9da99ea1c user: drh tags: trunk) | |
| 16:00 | Change "null-terminated" to "zero-terminated" in contexts that are referring to a C-language string. (check-in: ab201643e5 user: drh tags: branch-3.31) | |
Changes
Changes to pages/c_interface.in.
| ︙ | ︙ | |||
93 94 95 96 97 98 99 |
<p>The <b>sqlite_exec</b> function is used to process SQL statements
and queries. This function requires 5 parameters as follows:</p>
<ol>
<li><p>A pointer to the sqlite structure obtained from a prior call
to <b>sqlite_open</b>.</p></li>
| | | 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 |
<p>The <b>sqlite_exec</b> function is used to process SQL statements
and queries. This function requires 5 parameters as follows:</p>
<ol>
<li><p>A pointer to the sqlite structure obtained from a prior call
to <b>sqlite_open</b>.</p></li>
<li><p>A zero-terminated string containing the text of one or more
SQL statements and/or queries to be processed.</p></li>
<li><p>A pointer to a callback function which is invoked once for each
row in the result of a query. This argument may be NULL, in which
case no callbacks will ever be invoked.</p></li>
<li><p>A pointer that is forwarded to become the first argument
to the callback function.</p></li>
<li><p>A pointer to an error string. Error messages are written to space
|
| ︙ | ︙ |
Changes to pages/rescode.in.
| ︙ | ︙ | |||
846 847 848 849 850 851 852 |
lappend lx [list $name "$name ($ext_rc($name))" 0]
}
hd_list_of_links {} 450 $lx
</tcl>
<h1>Result Code Meanings</h1>
<p>
| | > | 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 |
lappend lx [list $name "$name ($ext_rc($name))" 0]
}
hd_list_of_links {} 450 $lx
</tcl>
<h1>Result Code Meanings</h1>
<p>
The meanings for all <tcl>hd_puts $nResCode</tcl>
result code values are shown below,
in numeric order.
<tcl>
# Generate the table of result codes
#
foreach val [lsort -int [array names valtoname]] {
set name $valtoname($val)
|
| ︙ | ︙ |
Changes to pages/vdbe.in.
| ︙ | ︙ | |||
41 42 43 44 45 46 47 | interrogate or change the database. Toward this end, the machine language that the VDBE implements is specifically designed to search, read, and modify databases.</p> <p>Each instruction of the VDBE language contains an opcode and three operands labeled P1, P2, and P3. Operand P1 is an arbitrary integer. P2 is a non-negative integer. P3 is a pointer to a data | | | 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 | interrogate or change the database. Toward this end, the machine language that the VDBE implements is specifically designed to search, read, and modify databases.</p> <p>Each instruction of the VDBE language contains an opcode and three operands labeled P1, P2, and P3. Operand P1 is an arbitrary integer. P2 is a non-negative integer. P3 is a pointer to a data structure or zero-terminated string, possibly null. Only a few VDBE instructions use all three operands. Many instructions use only one or two operands. A significant number of instructions use no operands at all but instead take their data and store their results on the execution stack. The details of what each instruction does and which operands it uses are described in the separate <a href="opcode.html">opcode description</a> document.</p> |
| ︙ | ︙ |