Lazy loading of article content
and full-text search
#874
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
content
load lazily. To achieve that I had to movecontent
to a separate table - I don't know how to make a field load lazily with Greendao otherwise. This probably fixes IllegalStateException: Couldn't read row 0, col 0 from CursorWindow (in GreenDAO's list method) #413. Also improves performance of lists.Currently
title
andcontent
are separately indexed by FTS (can be used in queries liketitle:linux
, see the previous link).This PR implements external content FTS tables, so there's no data duplication as in #871. Updating of FTS table is implemented using triggers. A lot of triggers *sigh*.
The features are not so closely related, but seeing how FTS adds constraints, I decided to implement both in one PR.