Documentation Source Text

Check-in [e4d2cd7fd1]
Login

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

Overview
Comment:Update the secure_delete pragma documentation to conform to the latest implementation.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: e4d2cd7fd117c4f0003be10e4bb33ffde04d7e30
User & Date: drh 2010-02-12 19:58:29
Context
2010-02-13
15:43
Correction to the PRAGMA secure_delete documentation. check-in: 9523519a73 user: drh tags: trunk
2010-02-12
19:58
Update the secure_delete pragma documentation to conform to the latest implementation. check-in: e4d2cd7fd1 user: drh tags: trunk
18:34
Update the documentation to include information about the new secure_delete pragma. check-in: ae2879358d user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/pragma.in.

630
631
632
633
634
635
636

637


638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
    identified and fixed early, reducing problems
    that might be caused by linking against a different version of SQLite.
    </p>
</li>

<tcl>Subsection secure_delete</tcl>
<li><p>^(<b>PRAGMA secure_delete;

       <br>PRAGMA secure_delete = </b><i>boolean</i><b>;</b></p>


    <p>Query or change the secure-delete flag.)^ ^When the secure-delete
    flag is on, SQLite overwrites deleted content with zeros.  The default
    setting is determined by the [SQLITE_SECURE_DELETE]
    compile-time option.

    <p>
    ^This pragma sets or clears the secure-delete flag when the pragma is
    prepared, not when the resulting prepared statement is run.  ^The
    prepared statement for this pragma merely returns the value of the
    secure-delete flag at the time the statement was prepared.  One should
    not retain the prepared statement for this pragma.

    <p>
    ^When there are [ATTACH | attached databases], this pragma only changes
    the secure-delete flag for the one database specified in the pragma, or
    for the main database if no database is specified.
    ^To change the secure-delete flag on all attached databases, this
    pragma must be run separately for each attached datatabase.

    <p>
    ^When multiple database connections share the same cache, changing
    the secure-delete flag on one database connection changes it for them
    all.
    </p>
</li>







>
|
>
>
|
|







|
|


|
|
|
|
|







630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
    identified and fixed early, reducing problems
    that might be caused by linking against a different version of SQLite.
    </p>
</li>

<tcl>Subsection secure_delete</tcl>
<li><p>^(<b>PRAGMA secure_delete;
       <br>PRAGMA </b><i>database</i><b>.secure_delete;
       <br>PRAGMA secure_delete = </b><i>boolean</i><b>
       <br>PRAGMA </b><i>database</i><b>.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>
    ^This pragma sets or clears the secure-delete flag when the pragma is
    prepared, not when the resulting prepared statement is run.  ^The
    prepared statement for this pragma merely returns the value of the
    secure-delete setting at the time the statement was prepared.  One should
    not retain or reuse the prepared statement for this pragma.

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

    <p>
    ^When multiple database connections share the same cache, changing
    the secure-delete flag on one database connection changes it for them
    all.
    </p>
</li>