Hi, We found an assertion bug in Sqlite. Here’s the PoC:
— CREATE TABLE v0 ( v1 ) ; CREATE TABLE v2 ( v3 INTEGER UNIQUE ON CONFLICT ABORT ) ; CREATE TRIGGER x AFTER INSERT ON v2 WHEN ( ( SELECT v1 AS PROMO_REVENUE FROM v2 JOIN v0 USING ( VALUE ) ) AND 0 ) BEGIN DELETE FROM v2 ; END ; CREATE VIRTUAL TABLE v4 USING fts4 ( v5 FLOAT UNIQUE AS( 'AIR' ) , v7 UNIQUE GENERATED ALWAYS AS( v1 ) , v9 INT CHECK( NOT v3 < 'BUILDING' ) , v8 INT UNIQUE GENERATED ALWAYS AS( NULL ) , v6 ) ; ALTER TABLE zipfile RENAME TO x ; — This needs to be run in one line and the bug exists in the latest development code. Yongheng & Rui _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
