Documentation Source Text

Check-in [ec87587f77]
Login

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

Overview
Comment:Improvements to the PRAGMA secure_delete documentation.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: ec87587f77ee011b45970f403a111793e07491df
User & Date: drh 2016-08-09 17:38:47.159
Context
2016-08-09
19:48
Update fts5.html to document negative column filters. (check-in: e79e555f14 user: dan tags: trunk)
17:38
Improvements to the PRAGMA secure_delete documentation. (check-in: ec87587f77 user: drh tags: trunk)
00:13
Properly escape "<" and ">" characters in the vtab.html document. (check-in: 03ec352945 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/pragma.in.
︙︙
894
895
896
897
898
899
900
901
902
903
904
905
906





907
908
909
910
911
912
913

    application makes faulty assumptions about output order can be
    identified and fixed early, reducing problems
    that might be caused by linking against a different version of SQLite.
    </p>
}

Pragma secure_delete {
    <p>^(PRAGMA DB.secure_delete;
     <br>PRAGMA DB.secure_delete = </b><i>boolean</i></p>
    <p>Query or change the secure-delete setting.)^ ^When secure-delete
    on, SQLite overwrites deleted content with zeros.  ^The default
    setting is determined by the [SQLITE_SECURE_DELETE]
    compile-time option.






    <p>
    ^When there are [ATTACH | attached databases] and no database
    is specified in the pragma, all databases have their secure-delete
    setting altered.
    ^The secure-delete setting for newly attached databases is the setting
    of the main database at the time the ATTACH command is evaluated.








|

|

|
|
>
>
>
>
>








894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918

    application makes faulty assumptions about output order can be
    identified and fixed early, reducing problems
    that might be caused by linking against a different version of SQLite.
    </p>
}

Pragma secure_delete {
    <p>^(<b>PRAGMA DB.secure_delete;
     <br>PRAGMA DB.secure_delete = </b><i>boolean</i></p>
    <p>Query or change the secure-delete setting.)^ ^When secure_delete is
    on, SQLite overwrites deleted content with zeros.  ^The default
    setting for secure_delete is determined by the [SQLITE_SECURE_DELETE]
    compile-time option and is normally off.  The off setting for
    secure_delete improves performance by reducing the
    amount of disk I/O.  Applications that wish to avoid leaving
    forensic traces after content is deleted or updated should enable the
    secure_delete pragma prior to performing the delete or update, or else
    run [VACUUM] after the delete or update.

    <p>
    ^When there are [ATTACH | attached databases] and no database
    is specified in the pragma, all databases have their secure-delete
    setting altered.
    ^The secure-delete setting for newly attached databases is the setting
    of the main database at the time the ATTACH command is evaluated.
︙︙