Add a windowSizeBytes parameter to AndroidSqliteDriver #4804
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.
Android has the concept of a cursor window, where a query will try to preemptively load data up to a certain size (by default 2MB). However if individual rows are too big to fit that size, a
SQLiteBlobTooBigException
will be thrown.A few issues where this happens:
More context about CursorWindow in this blog post.
Since Android 28+ this can be mitigated by controlling the window size. This PR adds the ability to pass this value to AndroidSqliteDriver.