Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typo in the pragma documentation: dartbase to database. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
bd64b1f2abfa30d1ab714b92370b24d5 |
| User & Date: | drh 2011-01-13 16:09:38 |
Context
|
2011-01-17
| ||
| 18:29 | Begin recording changes in preparation for the 3.7.5 release. check-in: d098a0558d user: drh tags: trunk | |
|
2011-01-13
| ||
| 16:09 | Fix typo in the pragma documentation: dartbase to database. check-in: bd64b1f2ab user: drh tags: trunk | |
| 12:28 | Update the names of the Fossil repositories for source code and documentation. check-in: aae700de31 user: drh tags: trunk | |
Changes
Changes to pages/pragma.in.
747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 |
<p>Query or change the setting of the "synchronous" flag.)^
^The first (query) form will return the synchronous setting as an
integer. ^When synchronous is FULL (2), the SQLite database engine will
use the xSync method of the VFS to ensure that all content is safely
written to the disk surface prior to continuing.
This ensures that an operating system crash or power failure will
not corrupt the dartbase.
FULL synchronous is very safe, but it is also slower.
^When synchronous is NORMAL (1), the SQLite database
engine will still sync at the most critical moments, but less often
than in FULL mode. There is a very small (though non-zero) chance that
a power failure at just the wrong time could corrupt the database in
NORMAL mode. But in practice, you are more likely to suffer
a catastrophic disk failure or some other unrecoverable hardware
|
| |
747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 |
<p>Query or change the setting of the "synchronous" flag.)^
^The first (query) form will return the synchronous setting as an
integer. ^When synchronous is FULL (2), the SQLite database engine will
use the xSync method of the VFS to ensure that all content is safely
written to the disk surface prior to continuing.
This ensures that an operating system crash or power failure will
not corrupt the database.
FULL synchronous is very safe, but it is also slower.
^When synchronous is NORMAL (1), the SQLite database
engine will still sync at the most critical moments, but less often
than in FULL mode. There is a very small (though non-zero) chance that
a power failure at just the wrong time could corrupt the database in
NORMAL mode. But in practice, you are more likely to suffer
a catastrophic disk failure or some other unrecoverable hardware
|