diff options
Diffstat (limited to 'test')
| -rw-r--r-- | test/journal2.test | 2 | ||||
| -rw-r--r-- | test/zerodamage.test | 35 |
2 files changed, 20 insertions, 17 deletions
diff --git a/test/journal2.test b/test/journal2.test index 2272f139f..8f9b4d0b7 100644 --- a/test/journal2.test +++ b/test/journal2.test @@ -34,7 +34,7 @@ proc a_string {n} { # characteristics flags to "SAFE_DELETE". # testvfs tvfs -default 1 -tvfs devchar {undeletable_when_open zero_damage} +tvfs devchar {undeletable_when_open powersafe_overwrite} # Set up a hook so that each time a journal file is opened, closed or # deleted, the method name ("xOpen", "xClose" or "xDelete") and the final diff --git a/test/zerodamage.test b/test/zerodamage.test index bef82b2ed..0e82ce350 100644 --- a/test/zerodamage.test +++ b/test/zerodamage.test @@ -9,29 +9,32 @@ # #*********************************************************************** # -# This file implements tests of the SQLITE_IOCAP_ZERO_DAMAGE property -# and the SQLITE_FCNTL_ZERO_DAMAGE file-control for manipulating it. +# This file implements tests of the SQLITE_IOCAP_POWERSAFE_OVERWRITE property +# and the SQLITE_FCNTL_POWERSAFE_OVERWRITE file-control for manipulating it. +# +# The name of this file comes from the fact that we used to call the +# POWERSAFE_OVERWRITE property ZERO_DAMAGE. # set testdir [file dirname $argv0] source $testdir/tester.tcl set testprefix wal5 -# ZERO_DAMAGE defaults to true +# POWERSAFE_OVERWRITE defaults to true # do_test zerodamage-1.0 { - file_control_zero_damage db -1 + file_control_powersafe_overwrite db -1 } {0 1} # Check the ability to turn zero-damage on and off. # do_test zerodamage-1.1 { - file_control_zero_damage db 0 - file_control_zero_damage db -1 + file_control_powersafe_overwrite db 0 + file_control_powersafe_overwrite db -1 } {0 0} do_test zerodamage-1.2 { - file_control_zero_damage db 1 - file_control_zero_damage db -1 + file_control_powersafe_overwrite db 1 + file_control_powersafe_overwrite db -1 } {0 1} # Run a transaction with zero-damage on, a small page size and a much larger @@ -42,7 +45,7 @@ do_test zerodamage-2.0 { db close testvfs tv -default 1 tv sectorsize 8192 - sqlite3 db file:test.db?zero_damage=1 -uri 1 + sqlite3 db file:test.db?psow=TRUE -uri 1 unset -nocomplain ::max_journal_size set ::max_journal_size 0 proc xDeleteCallback {method file args} { @@ -65,7 +68,7 @@ do_test zerodamage-2.0 { db eval { UPDATE t1 SET y=randomblob(50) WHERE x=123; } - concat [file_control_zero_damage db -1] [set ::max_journal_size] + concat [file_control_powersafe_overwrite db -1] [set ::max_journal_size] } {0 1 2576} # Repeat the previous step with zero-damage turned off. This time the @@ -74,14 +77,14 @@ do_test zerodamage-2.0 { do_test zerodamage-2.1 { set ::max_journal_size 0 db close - sqlite3 db file:test.db?zero_damage=0 -uri 1 + sqlite3 db file:test.db?psow=FALSE -uri 1 db eval { UPDATE t1 SET y=randomblob(50) WHERE x=124; } - concat [file_control_zero_damage db -1] [set ::max_journal_size] + concat [file_control_powersafe_overwrite db -1] [set ::max_journal_size] } {0 0 24704} -# Run a WAL-mode transaction with ZERO_DAMAGE on to verify that the +# Run a WAL-mode transaction with POWERSAFE_OVERWRITE on to verify that the # WAL file does not get too big. # do_test zerodamage-3.0 { @@ -89,19 +92,19 @@ do_test zerodamage-3.0 { PRAGMA journal_mode=WAL; } db close - sqlite3 db file:test.db?zero_damage=1 -uri 1 + sqlite3 db file:test.db?psow=TRUE -uri 1 db eval { UPDATE t1 SET y=randomblob(50) WHERE x=124; } file size test.db-wal } {1080} -# Repeat the previous with ZERO_DAMAGE off. Verify that the WAL file +# Repeat the previous with POWERSAFE_OVERWRITE off. Verify that the WAL file # is padded. # do_test zerodamage-3.1 { db close - sqlite3 db file:test.db?zero_damage=0 -uri 1 + sqlite3 db file:test.db?psow=FALSE -uri 1 db eval { UPDATE t1 SET y=randomblob(50) WHERE x=124; } |