Import SQLite 3.7.6.3.

third_party/sqlite/src/test/index.test

 # 2001 September 15
 #
 # 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 336 matching lines @@
       b int,
       c float,
       PRIMARY KEY(b)
     );
   }
   for {set i 1} {$i<=50} {incr i} {
     execsql "INSERT INTO t3 VALUES('x${i}x',$i,0.$i)"
   }
   set sqlite_search_count 0
   concat [execsql {SELECT c FROM t3 WHERE b==10}] $sqlite_search_count
-} {0.1 3}
+} {0.1 2}
 integrity_check index-11.2
 
 
 # Numeric strings should compare as if they were numbers.  So even if the
 # strings are not character-by-character the same, if they represent the
 # same number they should compare equal to one another.  Verify that this
 # is true in indices.
 #
 # Updated for sqlite3 v3: SQLite will now store these values as numbers
 # (because the affinity of column a is NUMERIC) so the quirky
@@ skipping 157 matching lines @@
     INSERT INTO t1 VALUES('12.33e04',2);
     INSERT INTO t1 VALUES('12.35E4',3);
     INSERT INTO t1 VALUES('12.34e',4);
     INSERT INTO t1 VALUES('12.32e+4',5);
     INSERT INTO t1 VALUES('12.36E+04',6);
     INSERT INTO t1 VALUES('12.36E+',7);
     INSERT INTO t1 VALUES('+123.10000E+0003',8);
     INSERT INTO t1 VALUES('+',9);
     INSERT INTO t1 VALUES('+12347.E+02',10);
     INSERT INTO t1 VALUES('+12347E+02',11);
-    SELECT b FROM t1 ORDER BY a;
+    INSERT INTO t1 VALUES('+.125E+04',12);
+    INSERT INTO t1 VALUES('-.125E+04',13);
+    INSERT INTO t1 VALUES('.125E+0',14);
+    INSERT INTO t1 VALUES('.125',15);
+    SELECT b FROM t1 ORDER BY a, b;
   }
-} {8 5 2 1 3 6 11 9 10 4 7}
-integrity_check index-15.1
+} {13 14 15 12 8 5 2 1 3 6 10 11 9 4 7}
+do_test index-15.3 {
+  execsql {
+    SELECT b FROM t1 WHERE typeof(a) IN ('integer','real') ORDER BY b;
+  }
+} {1 2 3 5 6 8 10 11 12 13 14 15}
+integrity_check index-15.4
 
 # The following tests - index-16.* - test that when a table definition
 # includes qualifications that specify the same constraint twice only a
 # single index is generated to enforce the constraint.
 #
 # For example: "CREATE TABLE abc( x PRIMARY KEY, UNIQUE(x) );"
 #
 do_test index-16.1 {
   execsql {
     CREATE TABLE t7(c UNIQUE PRIMARY KEY);
@@ skipping 153 matching lines @@
   }
 } {}
 do_test index-20.2 {
   execsql {
     DROP INDEX "t6i1";
   }
 } {}
    
 
 finish_test