2017-01-05
| ||
17:38 | • Fixed ticket [190c2507]: Assertion fault on a query against a view plus 5 other changes (artifact: db3c58de user: drh) | |
17:25 | Fix handling the case where a sub-query in a FROM clause is itself a UNION ALL, and one side of that UNION ALL is a query on a view that includes an ORDER BY. Fix for ticket [190c2507]. (check-in: ec1e85a6 user: dan tags: branch-3.16) | |
17:23 | Fix handling the case where a sub-query in a FROM clause is itself a UNION ALL, and one side of that UNION ALL is a query on a view that includes an ORDER BY. Fix for ticket [190c2507]. (check-in: 590ca83b user: dan tags: trunk) | |
16:34 | • New ticket [190c2507] Assertion fault on a query against a view. (artifact: 5c889138 user: drh) | |
Ticket Hash: | 190c2507eeffcd1154196faa18551cd10a3d4703 | |||
Title: | Assertion fault on a query against a view | |||
Status: | Fixed | Type: | Code_Defect | |
Severity: | Severe | Priority: | Immediate | |
Subsystem: | Unknown | Resolution: | Fixed | |
Last Modified: | 2017-01-05 17:38:31 | |||
Version Found In: | 3.16.1 | |||
User Comments: | ||||
drh added on 2017-01-05 16:34:50:
The following SQL causes an assertion fault: CREATE TABLE t1(a); CREATE TABLE t2(b); CREATE TABLE t3(c); CREATE VIEW vvv AS SELECT b FROM t2 ORDER BY 1; SELECT 123 FROM t1, (SELECT b FROM vvv UNION ALL SELECT c from t3); Bisecting isolates the problem to check-in [b9727e6bbfc3c] (2015-05-22). The problem first appeared in version 3.8.11 on 2015-07-27. |