Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo in the how-to-corrupt document. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: | a1408d26c61ffc145daeae32a4b0cc3a97fd058c |
| User & Date: | drh 2011-06-08 15:11:21 |
Context
|
2011-06-14
| ||
| 19:38 | Update fts3.html with the new "order" and "prefix" options. check-in: 074255f9eb user: dan tags: trunk | |
|
2011-06-08
| ||
| 15:11 | Fix a typo in the how-to-corrupt document. check-in: a1408d26c6 user: drh tags: trunk | |
|
2011-06-04
| ||
| 23:20 | Fix a missing end-requirement mark in the expression documentation. check-in: 957ac800cf user: drh tags: trunk | |
Changes
Changes to pages/howtocorrupt.in.
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 |
or the application. </p> <p>Though SQLite is resistant to database corruption, it is not immune. This document describes the various ways that an SQLite database might go corrupt.</p> <h2>1.0 File overwrite by a rogue thread process</h2> <p>SQLite database files are ordinary disk files. That means that any process can open the file and overwrite it with garbage. There is nothing that the SQLite library can do to defend against this.</p> <h3>1.1 Continuing to use a file descriptor after it has been closed</h3> |
| |
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 |
or the application.
</p>
<p>Though SQLite is resistant to database corruption, it is not immune.
This document describes the various ways that an SQLite database might
go corrupt.</p>
<h2>1.0 File overwrite by a rogue thread or process</h2>
<p>SQLite database files are ordinary disk files.
That means that any process can open the file and
overwrite it with garbage. There is nothing that the SQLite
library can do to defend against this.</p>
<h3>1.1 Continuing to use a file descriptor after it has been closed</h3>
|