/ Check-in [ef2a6a37]
Login
SQLite training in Houston TX on 2019-11-05 (details)
Part of the 2019 Tcl Conference

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

Overview
Comment:Minor fixes for test cases. No code changes.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: ef2a6a37366f91889dc2f1ba9cb6d1257d9b05db
User & Date: dan 2013-08-21 20:04:54
Context
2013-08-21
21:12
Simplification to the StrAccum object and the sqlite3StrAccumAppend() method that also results in slightly better performance. check-in: 700dbbea user: drh tags: trunk
20:04
Minor fixes for test cases. No code changes. check-in: ef2a6a37 user: dan tags: trunk
19:59
Fix typo in test. check-in: f9859fe9 user: mistachkin tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to test/malloc5.test.

   201    201   do_test malloc5-4.1 {
   202    202     execsql {BEGIN;}
   203    203     execsql {DELETE FROM abc;}
   204    204     for {set i 0} {$i < 10000} {incr i} {
   205    205       execsql "INSERT INTO abc VALUES($i, $i, '[string repeat X 100]');"
   206    206     }
   207    207     execsql {COMMIT;}
          208  +  db cache flush
   208    209     sqlite3_release_memory
   209    210     sqlite3_memory_highwater 1
   210    211     execsql {SELECT * FROM abc}
   211    212     set nMaxBytes [sqlite3_memory_highwater 1]
   212    213     puts -nonewline " (Highwater mark: $nMaxBytes) "
   213    214     expr $nMaxBytes > 1000000
   214    215   } {1}
   215    216   do_test malloc5-4.2 {
          217  +  db cache flush
   216    218     sqlite3_release_memory
   217    219     sqlite3_soft_heap_limit 100000
   218    220     sqlite3_memory_highwater 1
   219    221     execsql {SELECT * FROM abc}
   220    222     set nMaxBytes [sqlite3_memory_highwater 1]
   221    223     puts -nonewline " (Highwater mark: $nMaxBytes) "
   222    224     expr $nMaxBytes <= 110000

Changes to test/where2.test.

   697    697     execsql {
   698    698       SELECT d FROM t11 WHERE c=7 OR (a=1 AND b=2) ORDER BY d;
   699    699     }
   700    700   } {4 8 10}
   701    701   
   702    702   # Verify that the OR clause is used in an outer loop even when
   703    703   # the OR clause scores slightly better on an inner loop.
          704  +if {[permutation] != "no_optimization"} {
   704    705   do_execsql_test where2-12.1 {
   705    706     CREATE TABLE t12(x INTEGER PRIMARY KEY, y);
   706    707     CREATE INDEX t12y ON t12(y);
   707    708     EXPLAIN QUERY PLAN
   708    709       SELECT a.x, b.x
   709    710         FROM t12 AS a JOIN t12 AS b ON a.y=b.x
   710    711        WHERE (b.x=$abc OR b.y=$abc);
   711    712   } {/.*SEARCH TABLE t12 AS b .*SEARCH TABLE t12 AS b .*/}
          713  +}
   712    714   
   713    715   
   714    716   finish_test