Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| SHA1 Hash: | e4d2cd7fd117c4f0003be10e4bb33ffde04d7e30 |
|---|---|
| Date: | 2010-02-12 19:58:29 |
| User: | drh |
| Comment: | Update the secure_delete pragma documentation to conform to the latest implementation. |
Tags And Properties
- branch=trunk inherited from [b2e03e19ab]
- sym-trunk inherited from [b2e03e19ab]
Changes
Changes to pages/pragma.in
630 identified and fixed early, reducing problems 630 identified and fixed early, reducing problems 631 that might be caused by linking against a different version of SQLite. 631 that might be caused by linking against a different version of SQLite. 632 </p> 632 </p> 633 </li> 633 </li> 634 634 635 <tcl>Subsection secure_delete</tcl> 635 <tcl>Subsection secure_delete</tcl> 636 <li><p>^(<b>PRAGMA secure_delete; 636 <li><p>^(<b>PRAGMA secure_delete; > 637 <br>PRAGMA </b><i>database</i><b>.secure_delete; 637 <br>PRAGMA secure_delete = </b><i>boolean</i><b>;</b></p> | 638 <br>PRAGMA secure_delete = </b><i>boolean</i><b> > 639 <br>PRAGMA </b><i>database</i><b>.secure_delete = > 640 </b><i>boolean</i></p> 638 <p>Query or change the secure-delete flag.)^ ^When the secure-delete | 641 <p>Query or change the secure-delete setting.)^ ^When secure-delete 639 flag is on, SQLite overwrites deleted content with zeros. The default | 642 on, SQLite overwrites deleted content with zeros. ^The default 640 setting is determined by the [SQLITE_SECURE_DELETE] 643 setting is determined by the [SQLITE_SECURE_DELETE] 641 compile-time option. 644 compile-time option. 642 645 643 <p> 646 <p> 644 ^This pragma sets or clears the secure-delete flag when the pragma is 647 ^This pragma sets or clears the secure-delete flag when the pragma is 645 prepared, not when the resulting prepared statement is run. ^The 648 prepared, not when the resulting prepared statement is run. ^The 646 prepared statement for this pragma merely returns the value of the 649 prepared statement for this pragma merely returns the value of the 647 secure-delete flag at the time the statement was prepared. One should | 650 secure-delete setting at the time the statement was prepared. One should 648 not retain the prepared statement for this pragma. | 651 not retain or reuse the prepared statement for this pragma. 649 652 650 <p> 653 <p> 651 ^When there are [ATTACH | attached databases], this pragma only changes | 654 ^When there are [ATTACH | attached databases] and no database 652 the secure-delete flag for the one database specified in the pragma, or | 655 is specified in the pragma, all databases have their secure-delete 653 for the main database if no database is specified. | 656 setting altered and the return value is the value of the main database. 654 ^To change the secure-delete flag on all attached databases, this | 657 ^The secure-delete setting for newly attached databases is the setting 655 pragma must be run separately for each attached datatabase. | 658 of the main database at the time the ATTACH command is evaluated. 656 659 657 <p> 660 <p> 658 ^When multiple database connections share the same cache, changing 661 ^When multiple database connections share the same cache, changing 659 the secure-delete flag on one database connection changes it for them 662 the secure-delete flag on one database connection changes it for them 660 all. 663 all. 661 </p> 664 </p> 662 </li> 665 </li>