commit 1d24a53125ab15f2d80ff4c64a2b65ed9d9ff44b
author dan <dan@noemail.net> Mon Dec 23 15:17:11 2019 +0000
committer dan <dan@noemail.net> Mon Dec 23 15:17:11 2019 +0000
tree 3c13535c1c4a106646fac7dff83da0321aa1eaba
parent 2811ea6be7f4d63d5cc0992c78db3b1b73112a93

Fix a case in which SQLite could fail to identify "x BETWEEN ? AND ?" being true as implying that x is not null. Ticket [dfd66334].

FossilOrigin-Name: 2f17974912ec5e99089dc0da803e7ff1bf033377a49762d2689a812c005f2641

src/expr.c

diff --git a/src/expr.c b/src/expr.c
index 4593ebb..617fcf0 100644
--- a/src/expr.c
+++ b/src/expr.c
@@ -5297,7 +5297,10 @@
       return WRC_Prune;
 
     case TK_BETWEEN:
-      sqlite3WalkExpr(pWalker, pExpr->pLeft);
+      if( sqlite3WalkExpr(pWalker, pExpr->pLeft)==WRC_Abort ){
+        assert( pWalker->eCode );
+        return WRC_Abort;
+      }
       return WRC_Prune;
 
     /* Virtual tables are allowed to use constraints like x=NULL.  So