Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix minor typo in pragma.html. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
0fec42b940eb30d6af22cc48167098c2 |
| User & Date: | dan 2009-01-14 06:51:10 |
Context
|
2009-01-15
| ||
| 14:45 | Preparation for the 3.6.10 release. check-in: fa09fac9b0 user: drh tags: trunk | |
|
2009-01-14
| ||
| 06:51 | Fix minor typo in pragma.html. check-in: 0fec42b940 user: dan tags: trunk | |
| 02:17 | Changes for version 3.6.9. check-in: 01bd9245c3 user: drh tags: trunk | |
Changes
Changes to pages/pragma.in.
295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 |
the transaction to commit.
(See the documented titled <a href="atomiccommit.html">
Atomic Commit In SQLite</a> for additional detail.)</p>
<p>The TRUNCATE journaling mode commits transactions by truncating
the rollback journal to zero-length instead of deleting it. On many
systems, truncating a file is much faster than deleting the file since
the containing directory need to be changed.</p>
<p>The PERSIST journaling mode prevents the rollback journal from
being deleted at the end of each transaction. Instead, the header
of the journal is overwritten with zeros. This will prevent other
database connections from rolling the journal back. The PERSIST
journaling mode is useful as an optimization on platforms where
deleting or truncating a file is much more expensive than overwriting
|
| |
295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 |
the transaction to commit.
(See the documented titled <a href="atomiccommit.html">
Atomic Commit In SQLite</a> for additional detail.)</p>
<p>The TRUNCATE journaling mode commits transactions by truncating
the rollback journal to zero-length instead of deleting it. On many
systems, truncating a file is much faster than deleting the file since
the containing directory does not need to be changed.</p>
<p>The PERSIST journaling mode prevents the rollback journal from
being deleted at the end of each transaction. Instead, the header
of the journal is overwritten with zeros. This will prevent other
database connections from rolling the journal back. The PERSIST
journaling mode is useful as an optimization on platforms where
deleting or truncating a file is much more expensive than overwriting
|