mirror of
https://github.com/sqlite/sqlite.git
synced 2025-08-01 06:27:03 +03:00
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
This commit is contained in:
@ -1165,4 +1165,24 @@ do_execsql_test select1-18.4 {
|
||||
);
|
||||
} {1}
|
||||
|
||||
# 2019-12-17 gramfuzz find
|
||||
#
|
||||
do_execsql_test select-19.10 {
|
||||
DROP TABLE IF EXISTS t1;
|
||||
CREATE TABLE t1(x);
|
||||
} {}
|
||||
do_catchsql_test select-19.20 {
|
||||
INSERT INTO t1
|
||||
SELECT 1,2,3,4,5,6,7
|
||||
UNION ALL SELECT 1,2,3,4,5,6,7
|
||||
ORDER BY 1;
|
||||
} {1 {table t1 has 1 columns but 7 values were supplied}}
|
||||
do_catchsql_test select-19.21 {
|
||||
INSERT INTO t1
|
||||
SELECT 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
|
||||
UNION ALL SELECT 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
|
||||
ORDER BY 1;
|
||||
} {1 {table t1 has 1 columns but 15 values were supplied}}
|
||||
|
||||
|
||||
finish_test
|
||||
|
Reference in New Issue
Block a user