## Summary
<!--Explain briefly what goes wrong and explain why you believe this is a bug and not the intended behavior of SQLite (if it is not a crash).-->**No review yet**

## Minimized query

```sql
PRAGMA journal_mode = 'WAL';
CREATE TABLE t1(a,b INT);
INSERT INTO t1(a,b) VALUES(datetime(((length('') + 0) + 1), '+1 day'),2),(3,3),(4,5);
CREATE UNIQUE INDEX i1 ON t1(b,b,a,a,a,a,a,b,a);
ANALYZE;
DROP TABLE IF EXISTS sqlite_stat4;
INSERT INTO sqlite_stat1 VALUES('t1','i1','30 30 30 2 2 2 2 2 2 2');
ANALYZE sqlite_master;

CREATE UNIQUE  INDEX IF NOT EXISTS idx_t1_650 ON t1(a COLLATE NOCASE);
CREATE TABLE T (
  a INTEGER,
  b REAL
);
INSERT INTO T VALUES (1,1.5), (2,-2.5), (3,0.0);
CREATE INDEX c
ON T(b);
SELECT * FROM T WHERE +b != -2.5 OR b < 2.0;
VACUUM main;
PRAGMA wal_checkpoint('RESTART');
INSERT INTO t1 VALUES (NULL, NULL);

SELECT COUNT(*) FROM t1;
SELECT a, COUNT(*) FROM t1 GROUP BY a HAVING a IN (SELECT a FROM t1);
DELETE FROM T WHERE rowid = 62;
UPDATE T SET b = CURRENT_TIMESTAMP WHERE b IS NOT NULL RETURNING *;
INSERT INTO t1 DEFAULT VALUES;
INSERT INTO t1 DEFAULT VALUES;
VACUUM main;
CREATE UNIQUE  INDEX IF NOT EXISTS idx_t1_4468 ON t1(lower(b)) WHERE b > 0;
SELECT STRING_AGG(b, '|') FROM t1;
SELECT COUNT(a) FILTER (WHERE a IS NOT NULL) OVER (PARTITION BY a ORDER BY a RANGE BETWEEN 1 PRECEDING AND 1 FOLLOWING) FROM T;
ANALYZE T;
INSERT INTO t1 DEFAULT VALUES;
INSERT INTO t1 VALUES (1, 'x') ON CONFLICT(a) DO UPDATE SET a = excluded.a, b = excluded.b;
PRAGMA secure_delete = 0;
```

## Actual output

```sql
memory
1|1.5
2|-2.5
3|0.0
0|-1|-1
4
3|1
4|1
-4713-11-26 12:00:00|1
1|2026-05-15 11:43:31
2|2026-05-15 11:43:31
3|2026-05-15 11:43:31
1
1
1
0
```

## Expectation

```sql

```

## Flag

```

```