Documentation Source Text

Check-in [e771d11d93]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix typos in the psow.html document.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: e771d11d93ba194fa402e645604cb6803fc40627
User & Date: drh 2012-01-11 16:56:14.225
Context
2012-01-11
21:16
Describe fake-capacity USB sticks on the How-To-Corrupt page. (check-in: 0a50332c30 user: drh tags: trunk)
16:56
Fix typos in the psow.html document. (check-in: e771d11d93 user: drh tags: trunk)
2012-01-09
13:40
Add a note about data types and the compress/uncompress functions to the FTS documentation. (check-in: 8fadbd41ce user: dan tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/psow.in.
150
151
152
153
154
155
156
157
158
159
160
161
162
163
an application to query the powersafe overwrite property for a database
file.

<hr>
<h2>Notes:</h2>
<ol><li value=1><p>
SQLite never assumes atomic page writes <em>in its default configurations</em>.
But a custom [VFS] can sets one of the 
[SQLITE_IOCAP_ATOMIC] bits in the result of the xDeviceCharacteristic()
method and then SQLite will assume that page writes are atomic.  The
application must supply a custom VFS to accomplish this, however, since
none of the standard VFSes will ever set any of the atomic bits in the
xDeviceCharacteristics() vector.
</ol>







|






150
151
152
153
154
155
156
157
158
159
160
161
162
163
an application to query the powersafe overwrite property for a database
file.

<hr>
<h2>Notes:</h2>
<ol><li value=1><p>
SQLite never assumes atomic page writes <em>in its default configurations</em>.
But a custom [VFS] can set one of the 
[SQLITE_IOCAP_ATOMIC] bits in the result of the xDeviceCharacteristic()
method and then SQLite will assume that page writes are atomic.  The
application must supply a custom VFS to accomplish this, however, since
none of the standard VFSes will ever set any of the atomic bits in the
xDeviceCharacteristics() vector.
</ol>