SQLite

View Ticket
Login
2011-10-13
18:25 Closed ticket [9861b74a]: Fts3 offsets() function may report SQLITE_CORRUPT with empty string. plus 3 other changes (artifact: ccd01a1dc5 user: drh)
2010-03-24
15:57
Fix for [9861b74ab9]. Correctly handle strings with zero tokens in the fts3 offsets() function. (check-in: d37034f7fc user: dan tags: trunk)
15:38 New ticket [9861b74a] Fts3 offsets() function may report SQLITE_CORRUPT with empty string.. (artifact: 0888a21a26 user: dan)

Ticket Hash: 9861b74ab9bf250b8850c577ebad87d6e0a1f645
Title: Fts3 offsets() function may report SQLITE_CORRUPT with empty string.
Status: Closed Type: Code_Defect
Severity: Important Priority: Immediate
Subsystem: Unknown Resolution: Overcome_By_Events
Last Modified: 2011-10-13 18:25:15
Version Found In: 3.6.23
Description:
The last statement in this script returns SQLITE_CORRUPT.
  CREATE VIRTUAL TABLE ft USING fts3(one, two);
  INSERT INTO ft VALUES('', 'foo');
  INSERT INTO ft VALUES('foo', 'foo');
  SELECT offsets(ft) FROM ft WHERE ft MATCH 'foo';

drh added on 2011-10-13 18:25:15:
There have been many fixes and enhancements to FTS since 3.6.23. This got repaired somewhere along the way.