Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
| Comment: | Split out the "Document Lists and Indexes" category at top of the categorical document list. Change the name of "Result Codes" to "Result and Error Codes" to make the document easier to find. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
8f221f2df8a08820dbdcc01a1f7c8ff1 |
| User & Date: | drh 2016-09-12 15:39:57 |
|
2016-09-12
| ||
| 16:22 | Updates to the "docs.html" page so that it uses the same <ul>-style format on desktop as it does on mobile, except that the detailed document descriptions are shown on desktop while still omitted on mobile. (check-in: 572767e60b user: drh tags: trunk) | |
| 15:39 | Split out the "Document Lists and Indexes" category at top of the categorical document list. Change the name of "Result Codes" to "Result and Error Codes" to make the document easier to find. (check-in: 8f221f2df8 user: drh tags: trunk) | |
| 10:59 | Corrections to the statement that defines when the "PRAGMA page_size" macro is not a no-op. (check-in: 1d425258b1 user: drh tags: trunk) | |
Changes to pages/docsdata.tcl.
1 2 3 4 5 6 7 .. 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 .. 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 |
heading {Overview Documents} overview
doc {About SQLite} {about.html} {
A high-level overview of what SQLite is and why you might be
interested in using it.
}
................................................................................
doc {Frequently Asked Questions} {faq.html} {
The title of the document says all...
}
doc {Books About SQLite} {books.html} {
A list of independently written books about SQLite.
}
doc {Alphabetical Listing Of Documents} {doclist.html} {
A list of all titled pages on this website, sorted by title.
}
doc {Website Keyword Index} {keyword_index.html} {
A cross-reference from keywords to various pages within this website.
}
doc {Permuted Title Index} {sitemap.html#pindex} {
Also known as a "keyword in context" or "KWIC" index or as a concordance,
this document is a listing of all other documents sorted by keyword.
}
heading {SQLite Programming Interfaces} programming {
Documentation describing the APIs used to program SQLite, and the SQL
dialect that it interprets.
}
................................................................................
doc {How To Compile SQLite} {howtocompile.html} {
Instructions and hints for compiling SQLite C code and integrating
that code with your own application.
}
doc {C/C++ API Reference} {c3ref/intro.html} {
This document describes each API function separately.
}
doc {Result Codes} {rescode.html} {
A description of the meanings of the numeric result codes
returned by various C/C++ interfaces.
}
doc {Tcl API} {tclsqlite.html} {
A description of the TCL interface bindings for SQLite.
}
doc {SQL Syntax} {lang.html} {
|
> > > > > > > > > > > > < < < < < < < < < < | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 .. 39 40 41 42 43 44 45 46 47 48 49 50 51 52 .. 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 |
heading {Document Lists And Indexes} lists doc {Alphabetical Listing Of Documents} {doclist.html} { A list of all titled pages on this website, sorted by title. } doc {Website Keyword Index} {keyword_index.html} { A cross-reference from keywords to various pages within this website. } doc {Permuted Title Index} {sitemap.html#pindex} { Also known as a "keyword in context" or "KWIC" index or as a concordance, this document is a listing of all other documents sorted by keyword. } heading {Overview Documents} overview doc {About SQLite} {about.html} { A high-level overview of what SQLite is and why you might be interested in using it. } ................................................................................ doc {Frequently Asked Questions} {faq.html} { The title of the document says all... } doc {Books About SQLite} {books.html} { A list of independently written books about SQLite. } heading {SQLite Programming Interfaces} programming { Documentation describing the APIs used to program SQLite, and the SQL dialect that it interprets. } ................................................................................ doc {How To Compile SQLite} {howtocompile.html} { Instructions and hints for compiling SQLite C code and integrating that code with your own application. } doc {C/C++ API Reference} {c3ref/intro.html} { This document describes each API function separately. } doc {Result and Error Codes} {rescode.html} { A description of the meanings of the numeric result codes returned by various C/C++ interfaces. } doc {Tcl API} {tclsqlite.html} { A description of the TCL interface bindings for SQLite. } doc {SQL Syntax} {lang.html} { |
Changes to pages/rescode.in.
1 2 3 4 5 6 7 8 |
<title>SQLite Result Codes</title>
<tcl>hd_keywords {result code} {result codes} {error code} {error codes}</tcl>
<table_of_contents>
<h2 style="margin-left:1.0em" notoc id=overview> Overview</h2>
<p>
|
| |
1 2 3 4 5 6 7 8 |
<title>Result and Error Codes</title>
<tcl>hd_keywords {result code} {result codes} {error code} {error codes}</tcl>
<table_of_contents>
<h2 style="margin-left:1.0em" notoc id=overview> Overview</h2>
<p>
|
Changes to pages/sessionintro.in.
480 481 482 483 484 485 486 487 488 489 |
[sqlite3changeset_concat()] or [sqlite3_changegroup] interfaces.
<li> <p>A changeset may be "inverted" using the [sqlite3changeset_invert()]
API function. An inverted changeset undoes the changes made by the
original. If changeset C<sup>+</sup> is the inverse of changeset C, then
applying C and then C<sup>+</sup> to a database should leave
the database unchanged.
|
< < < |
480 481 482 483 484 485 486 |
[sqlite3changeset_concat()] or [sqlite3_changegroup] interfaces.
<li> <p>A changeset may be "inverted" using the [sqlite3changeset_invert()]
API function. An inverted changeset undoes the changes made by the
original. If changeset C<sup>+</sup> is the inverse of changeset C, then
applying C and then C<sup>+</sup> to a database should leave
the database unchanged.
|