SQLite

View Ticket
Login
Plaintext
2013-03-27
21:12 • Fixed ticket [38b1ae01]: Assertion fault on valid FTS4 query plus 5 other changes (artifact: 48cf60d5 user: drh)
2013-03-25
12:02
Add a second test for [38b1ae018f]. (check-in: 5062db67 user: dan tags: trunk)
11:38
In fts3, when filtering lists for hits in a specific column, edit the list in place in the same way as it is for NEAR filtering. Fix for [38b1ae018f]. (check-in: f85f9103 user: dan tags: trunk)
2013-03-24
20:45 • New ticket [38b1ae01] Assertion fault on valid FTS4 query. (artifact: cb548670 user: drh)
Ticket Hash: 38b1ae018f9033326bce4698c1453e52b4db7fc4
Title: Assertion fault on valid FTS4 query
Status: Fixed Type: Code_Defect
Severity: Severe Priority: Immediate
Subsystem: Unknown Resolution: Fixed
Last Modified: 2013-03-27 21:12:25
Version Found In: 3.7.16
User Comments:
drh added on 2013-03-24 20:45:11:

The following code generates an assertion fault on the SELECT: 

CREATE VIRTUAL TABLE x USING fts4(y,z);
INSERT INTO x VALUES('aaa bbb ccc ddd', 'bbb ddd aaa ccc');
SELECT * FROM x where y MATCH 'bbb NEAR/6 aaa';

This problem was introduced when the FTS4 prefix option was added with check-in [b1f9c1e0ac51c] on 2011-04-14 for version 3.7.7.