Add the SQLITE_DEFAULT_DEFENSIVE compile-time option. Fix up test cases

so that they work with DEFENSIVE enabled. FossilOrigin-Name: 3212733cb6d1a59516d67a86df7c7b1d2456a1b2e5d7080c26b0e87b2609c65d
2018-11-07 02:17:01 +00:00
parent 0f0d3ddf71
commit 6ab91a7a7a
111 changed files with 157 additions and 217 deletions
@@ -244,4 +244,3 @@ foreach {tn sql res} {
 }

 finish_test
-
@@ -93,4 +93,3 @@ do_catchsql_test 3.3 {
  SELECT * FROM x2('^a');
 } {1 {fts5: phrase queries are not supported (detail!=full)}}
 finish_test
-
@@ -163,4 +163,3 @@ do_execsql_test 5.1 {
 } {30 31 32 33 34 35 36 37 38 39 40}

 finish_test
-
@@ -43,7 +43,6 @@ sqlite3_db_config db DEFENSIVE 0
 do_execsql_test 1.5 {
  DELETE FROM f1_data;
 } {}
-sqlite3_db_config db DEFENSIVE 1

 do_catchsql_test 1.6 {
  INSERT INTO f1(f1) VALUES('integrity-check');
@@ -75,7 +75,6 @@ do_execsql_test 2.4 {
  UPDATE x1_data SET block = X'';
  SELECT count(fts5_decode(rowid, block)) FROM x1_data;
 } $res
-sqlite3_db_config db DEFENSIVE 1

 do_execsql_test 2.5 {
  INSERT INTO x1(x1, rank) VALUES('pgsz', 1024);
@@ -206,4 +206,3 @@ do_execsql_test 3.5 {
 }

 finish_test
-