IndexedDB: Add IndexedDB implementation of EventCacheStore::load_last_chunk
#5384
+184
−26
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.
Background
This pull request is part of a series of pull requests to add a full IndexedDB implementation of the
EventCacheStore
(see #4617, #4996, #5090, #5138, #5226, #5274, #5343). This particular pull request focuses on providing an implementation ofEventCacheStore::load_last_chunk
.Changes
The primary change is the addition of
EventCacheStore::load_last_chunk
, as well as tests for ensuring this is functioning correctly.There are also a number of additions to
IndexeddbEventCacheStoreTransaction
which support the implementation ofEventCacheStore::load_last_chunk
.get_chunk_by_next_chunk_id
get_chunks_count_in_room
get_max_chunk_id
These are simply typed wrappers around the generic functions in
IndexeddbEventCacheStoreTransaction
.Future Work
EventCacheStore
functions without relying onMemoryStore
.Signed-off-by: Michael Goldenberg m@mgoldenberg.net