When doing an UPDATE or DELETE using a multi-column index where only a few

of the earlier columns of the index are useful for the index lookup,
postpone doing the main table seek until after all WHERE clause constraints
have been evaluated, in case those constraints can be covered by unused
later terms of the index, thus avoiding unnecessary main table seeks.

FossilOrigin-Name: 0ecda433718f0bc973078099b19955dcfb0dcd15b68455e53156ac708e9d92e5

ext/rtree/rtreefuzz001.test

@@ -467,7 +467,7 @@ do_test rtreefuzz001-100 {
   catchsql {
      SELECT rtreecheck('t1');
   }
-} {1 {SQL logic error}}
+} {1 {database disk image is malformed}}
 
 do_test rtreefuzz001-200 {
   sqlite3 db {}