/ View Ticket
Login
2014-11-12
14:07
Make sure that NULL results from OP_Column are fully and completely NULL and do not have the MEM_Ephem bit set. Fix for ticket [094d39a4c95ee4]. (check-in: e1017745 user: drh tags: branch-3.8.7)
2014-11-05
15:57 Fixed ticket [094d39a4]: Assertion fault on CREATE TABLE ... AS SELECT ... plus 3 other changes (artifact: 3503a857 user: drh)
15:57
Make sure that NULL results from OP_Column are fully and completely NULL and do not have the MEM_Ephem bit set. Fix for ticket [094d39a4c95ee4]. (check-in: 42705fd7 user: drh tags: trunk)
15:45 Ticket [43107840] Assertion fault on UPDATE status still Fixed with 3 other changes (artifact: 22c19255 user: drh)
15:44 Ticket [094d39a4] Assertion fault on CREATE TABLE ... AS SELECT ... status still Open with 6 other changes (artifact: e881c36f user: drh)
14:53 New ticket [094d39a4]. (artifact: b5f433e5 user: drh)

Ticket Hash: 094d39a4c95ee4abbc417f04214617675ba15c63
Title: Assertion fault on CREATE TABLE ... AS SELECT ...
Status: Fixed Type: Code_Defect
Severity: Severe Priority: Immediate
Subsystem: Unknown Resolution: Fixed
Last Modified: 2014-11-05 15:57:49
Version Found In: 3.8.7.1
User Comments:
drh added on 2014-11-05 14:53:49:

The following SQL gives an assertion fault while running the SELECT in the CREATE TABLE statement:

CREATE TABLE t1(a TEXT);
INSERT INTO t1(a) VALUES(1),(2);
CREATE TABLE t2(x TEXT, y TEXT);
INSERT INTO t2(x,y) VALUES(3,4);
CREATE TEMP TABLE t3 AS
  SELECT a AS p, coalesce(y,a) AS q FROM t1 LEFT JOIN t2 ON a=x;

This problem was reported on the sqlite-users@sqlite.org mailing list by Nissl Reinhard. Bisecting shows that the problem was introduced by check-in [36b613ccf0ddb764a].


drh added on 2014-11-05 15:44:20:

This appears to be the same underlying problem as ticket [43107840f1c02], just in a different spot in the code.