Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Clarify the wording of the SQLITE_SECURE_DELETE documentation. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
ce7c9f89a7b793cdb523e9d90292e4ae |
| User & Date: | drh 2015-03-31 14:31:03 |
Context
|
2015-04-02
| ||
| 17:10 | Fix typo in the shared cache documentation. (check-in: 078a97faa5 user: drh tags: trunk) | |
|
2015-03-31
| ||
| 14:31 | Clarify the wording of the SQLITE_SECURE_DELETE documentation. (check-in: ce7c9f89a7 user: drh tags: trunk) | |
|
2015-03-27
| ||
| 10:58 | Improved wording of a statement in the CREATE VIEW documentation. (check-in: 629e137c8d user: drh tags: trunk) | |
Changes
Changes to pages/compile.in.
429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 |
COMPILE_OPTION {SQLITE_SECURE_DELETE} {
This compile-time option changes the default setting of the
[secure_delete pragma]. When this option is not used, secure_delete defaults
to off. When this option is present, secure_delete defaults to on.
The secure_delete setting causes deleted content to be overwritten with
zeros. There is a small performance penalty for this since additional I/O
must occur. On the other hand, secure_delete can prevent sensitive
information from lingering in unused parts of the database file after it
has allegedly been deleted. See the documentation on the
[secure_delete pragma] for additional information.
}
COMPILE_OPTION {SQLITE_THREADSAFE=<i><0 or 1 or 2></i>} {
This option controls whether or not code is included in SQLite to
enable it to operate safely in a multithreaded environment. The
default is SQLITE_THREADSAFE=1 which is safe for use in a multithreaded
|
| | | | |
429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 |
COMPILE_OPTION {SQLITE_SECURE_DELETE} {
This compile-time option changes the default setting of the
[secure_delete pragma]. When this option is not used, secure_delete defaults
to off. When this option is present, secure_delete defaults to on.
The secure_delete setting causes deleted content to be overwritten with
zeros. There is a small performance penalty since additional I/O
must occur. On the other hand, secure_delete can prevent fragments of
sensitive information from lingering in unused parts of the database file
after it has been deleted. See the documentation on the
[secure_delete pragma] for additional information.
}
COMPILE_OPTION {SQLITE_THREADSAFE=<i><0 or 1 or 2></i>} {
This option controls whether or not code is included in SQLite to
enable it to operate safely in a multithreaded environment. The
default is SQLITE_THREADSAFE=1 which is safe for use in a multithreaded
|