DB cache issues for non-parametrized ID queries #6
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.
The generated provider has the
whereWithId
method that is used by single-entities queries such asquery
,update
,delete
.If a huge number of queries is executed on slow devices (I am using a Nexus One for testing purposes) a warning such as the following can be issued:
This can be solved by using the
_ID
column as a parameter. I have fixed this in my fork, I will make a pull request asap.