diff options
author | drh <drh@noemail.net> | 2019-12-18 01:31:21 +0000 |
---|---|---|
committer | drh <drh@noemail.net> | 2019-12-18 01:31:21 +0000 |
commit | 50efa586006c6ddb7290c37e35b9102747f18d78 (patch) | |
tree | e2d06f79f419dc3676748c964aaa1826f70b72e0 /src | |
parent | 75e95e1fcd52d3ec8282edb75ac8cd0814095d54 (diff) | |
download | sqlite-50efa586006c6ddb7290c37e35b9102747f18d78.tar.gz sqlite-50efa586006c6ddb7290c37e35b9102747f18d78.zip |
Remove an assert() in the code generator that can fail due to an invalid
INSERT statement. The same assert() appears again in the VDBE and will fire
there if the problem persists in an SQL statement that does not contain
errors. Gramfuzz find.
FossilOrigin-Name: 9bdd57cb9ad8ac1f4a0f1a3942d94ca5193109eeb1975343c4f0c7abf7135946
Diffstat (limited to 'src')
-rw-r--r-- | src/expr.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/expr.c b/src/expr.c index 981e18a8e..ea5906265 100644 --- a/src/expr.c +++ b/src/expr.c @@ -3507,7 +3507,6 @@ int sqlite3ExprCodeGetColumn( ** over to iTo..iTo+nReg-1. */ void sqlite3ExprCodeMove(Parse *pParse, int iFrom, int iTo, int nReg){ - assert( iFrom>=iTo+nReg || iFrom+nReg<=iTo ); sqlite3VdbeAddOp3(pParse->pVdbe, OP_Move, iFrom, iTo, nReg); } |