SQLite

View Ticket
Login
Ticket Hash: 89d259d45b855a0d35fa618da55593e8703cea6d
Title: Assertion fault on SQL input (2)
Status: Fixed Type: Code_Defect
Severity: Minor Priority: Low
Subsystem: Code_Generator Resolution: Fixed
Last Modified: 2023-03-17 00:04:47
2.14 years ago
Created: 2023-03-16 20:22:21
2.14 years ago
Version Found In: 3.41.1
User Comments:
drh added on 2023-03-16 20:22:21:

This is test2.sql from forum post d24ec63447:

CREATE  TEMP  TABLE t1(rootpage PRIMARY  KEY  ON  CONFLICT  IGNORE ) WITHOUT  ROWID ;
CREATE  TEMP  TRIGGER trig0 DELETE  ON t1 FOR  EACH  ROW  BEGIN  SELECT t2.* FROM (temp.t1 NOT  INDEXED ), (t1 AS t2 NOT  INDEXED , t1 AS t1 NOT  INDEXED ) GROUP  BY  NULL ,  FALSE ; END ;
CREATE  TRIGGER  IF  NOT  EXISTS temp.trig0 INSTEAD  OF  DELETE  ON t1 FOR  EACH  ROW  WHEN 0.0 BEGIN  INSERT  OR  FAIL  INTO t1 VALUES (0.0) ON  CONFLICT  DO  NOTHING  RETURNING *; INSERT  OR  FAIL  INTO t1 VALUES (0.0) ON  CONFLICT  DO  NOTHING  RETURNING *; SELECT  DISTINCT t1.*; END ;

drh added on 2023-03-17 00:04:47:

Same as [d15b3a4ea901ef0d]. This is a problem with the assert() statement only. The problem does not affect production code.