Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix hyperlink errors in the documentation. CVSTrac ticket #2807. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
10fa1f2eea26efc9e176693e86ef0852 |
User & Date: | drh 2007-11-28 16:24:27.000 |
Context
2007-11-28
| ||
18:38 | Fix typos on the docs.html page of the website. CVSTrac ticket #2811. (check-in: d6475c6071 user: drh tags: trunk) | |
16:24 | Fix hyperlink errors in the documentation. CVSTrac ticket #2807. (check-in: 10fa1f2eea user: drh tags: trunk) | |
2007-11-27
| ||
23:36 | Clarify that the legacy_file_format pragma only effects new databases and does not provide information on the file format of the current database. CVSTrac ticket #2804. (check-in: 84748f6b9b user: drh tags: trunk) | |
Changes
Changes to pages/atomiccommit.in.
︙ | ︙ | |||
558 559 560 561 562 563 564 | <br clear="both"> <h2>5.0 Multi-file Commit</h2> <p>SQLite allows a single <a href="c3ref/sqlite3.html">database connection</a> to talk to two or more database files simultaneously through the use of | | | 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 | <br clear="both"> <h2>5.0 Multi-file Commit</h2> <p>SQLite allows a single <a href="c3ref/sqlite3.html">database connection</a> to talk to two or more database files simultaneously through the use of the <a href="lang_attach.html">ATTACH DATABASE</a> command. When multiple database files are modified within a single transaction, all files are updated atomically. In other words, either all of the database files are updated or else none of them are. Achieving an atomic commit across multiple database files is more complex that doing so for a single file. This section describes how SQLite works that bit of magic.</p> |
︙ | ︙ | |||
1073 1074 1075 1076 1077 1078 1079 | dot-file locks or vice versa.</p> <h3>9.2 Incomplete Disk Flushes</h3> <p>SQLite uses the fsync() system call on unix and the FlushFileBuffers() system call on w32 in order to sync the file system buffers onto disk oxide as shown in <a href="#section_3_7">step 3.7</a> and | | | 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 | dot-file locks or vice versa.</p> <h3>9.2 Incomplete Disk Flushes</h3> <p>SQLite uses the fsync() system call on unix and the FlushFileBuffers() system call on w32 in order to sync the file system buffers onto disk oxide as shown in <a href="#section_3_7">step 3.7</a> and <a href="#section_3_10">step 3.10</a>. Unfortunately, we have received reports that neither of these interfaces works as advertised on many systems. We hear that FlushFileBuffers() can be completely disabled using registry settings on some windows versions. Some historical versions of Linux contain versions of fsync() which are no-ops on some filesystems, we are told. Even on systems where FlushFileBuffers() and fsync() are said to be working, often the IDE disk control lies and says that data has reached oxide |
︙ | ︙ |
Changes to pages/lang.in.
︙ | ︙ | |||
1575 1576 1577 1578 1579 1580 1581 | or compound.</p> <p>The optional conflict-clause allows the specification of an alternative constraint conflict resolution algorithm to use during this one command. See the section titled <a href="lang_conflict.html">ON CONFLICT</a> for additional information. For compatibility with MySQL, the parser allows the use of the | | | 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 | or compound.</p> <p>The optional conflict-clause allows the specification of an alternative constraint conflict resolution algorithm to use during this one command. See the section titled <a href="lang_conflict.html">ON CONFLICT</a> for additional information. For compatibility with MySQL, the parser allows the use of the single keyword <a href="lang_replace.html">REPLACE</a> as an alias for "INSERT OR REPLACE". </p> <tcl> ############################################################################## Section {ON CONFLICT clause} conflict |
︙ | ︙ |