Import SQLite 3.10.2.

third_party/sqlite/src/test/e_update.test

 # 2010 September 20
 #
 # The author disclaims copyright to this source code.  In place of
 # a legal notice, here is a blessing:
 #
 #    May you do good and not evil.
 #    May you find forgiveness for yourself and forgive others.
 #    May you share freely, never taking more than you give.
 #
 #***********************************************************************
@@ skipping 128 matching lines @@
   INSERT INTO main.t1 VALUES(3, 'iii');
 } {}
 do_update_tests e_update-1.2 {
   1  "UPDATE t1 SET b = 'roman' ; SELECT * FROM t1"
      {1 roman  2 roman  3 roman}
 
   2  "UPDATE t1 SET a = 'greek' ; SELECT * FROM t1"
      {greek roman  greek roman  greek roman}
 }
 
-# EVIDENCE-OF: R-42117-40023 Otherwise, the UPDATE affects only those
-# rows for which the result of evaluating the WHERE clause expression as
-# a boolean expression is true.
+# EVIDENCE-OF: R-58095-46013 Otherwise, the UPDATE affects only those
+# rows for which the WHERE clause boolean expression is true.
 #
 do_execsql_test e_update-1.3.0 {
   DELETE FROM main.t1;
   INSERT INTO main.t1 VALUES(NULL, '');
   INSERT INTO main.t1 VALUES(1, 'i');
   INSERT INTO main.t1 VALUES(2, 'ii');
   INSERT INTO main.t1 VALUES(3, 'iii');
 } {}
 do_update_tests e_update-1.3 {
   1  "UPDATE t1 SET b = 'roman' WHERE a<2 ; SELECT * FROM t1"
@@ skipping 96 matching lines @@
   INSERT INTO t2(rowid, a, b, c) VALUES(3,  2, 6, 5);
 } {}
 do_update_tests e_update-1.7 -query {
   SELECT * FROM t2
 } {
   1   "UPDATE t2 SET a=b+c"          {5 1 4     14 5 9   11  6 5}
   2   "UPDATE t2 SET a=b, b=a"       {1 5 4     5 14 9    6 11 5}
   3   "UPDATE t2 SET a=c||c, c=NULL" {44 5 {}  99 14 {}  55 11 {}}
 }
 
-# EVIDENCE-OF: R-12619-24112 The optional conflict-clause allows the
-# user to nominate a specific constraint conflict resolution algorithm
-# to use during this one UPDATE command.
+# EVIDENCE-OF: R-28518-13457 The optional "OR action" conflict clause
+# that follows the UPDATE keyword allows the user to nominate a specific
+# constraint conflict resolution algorithm to use during this one UPDATE
+# command.
 #
 do_execsql_test e_update-1.8.0 {
   DELETE FROM t3;
   INSERT INTO t3 VALUES(1, 'one');
   INSERT INTO t3 VALUES(2, 'two');
   INSERT INTO t3 VALUES(3, 'three');
   INSERT INTO t3 VALUES(4, 'four');
 } {}
 foreach {tn sql error ac data } {
   1  "UPDATE t3 SET b='one' WHERE a=3" 
@@ skipping 34 matching lines @@
   do_catchsql_test e_update-1.8.$tn.1 $sql [list [expr {$error!=""}] $error]
   do_execsql_test  e_update-1.8.$tn.2 {SELECT * FROM t3} [list {*}$data]
   do_test          e_update-1.8.$tn.3 {sqlite3_get_autocommit db} $ac
 }
 
 
 
 # EVIDENCE-OF: R-12123-54095 The table-name specified as part of an
 # UPDATE statement within a trigger body must be unqualified.
 #
-# EVIDENCE-OF: R-09690-36749 In other words, the database-name. prefix
-# on the table name of the UPDATE is not allowed within triggers.
+# EVIDENCE-OF: R-43190-62442 In other words, the schema-name. prefix on
+# the table name of the UPDATE is not allowed within triggers.
 #
 do_update_tests e_update-2.1 -error {
   qualified table names are not allowed on INSERT, UPDATE, and DELETE statements within triggers
 } {
   1 {
       CREATE TRIGGER tr1 AFTER INSERT ON t1 BEGIN
         UPDATE main.t2 SET a=1, b=2, c=3;
       END;
   } {}
 
@@ skipping 259 matching lines @@
   1   "UPDATE t7 SET s = q ORDER BY r LIMIT -1"        {1 2 3 4 5 6 7 8 9 10}
   2   "UPDATE t7 SET s = q ORDER BY r ASC LIMIT -1"    {1 2 3 4 5 6 7 8 9 10}
   3   "UPDATE t7 SET s = q ORDER BY r DESC LIMIT -1"   {1 2 3 4 5 6 7 8 9 10}
   4   "UPDATE t7 SET s = q ORDER BY q DESC LIMIT 5"    {6 7 8 9 10}
 }
 
 
 } ;# ifcapable update_delete_limit
  
 finish_test