Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DB cache issues for non-parametrized ID queries #6

Closed
wants to merge 4 commits into from

Conversation

frapontillo
Copy link
Contributor

The generated provider has the whereWithId method that is used by single-entities queries such as query, 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:

Reached MAX size for compiled-sql statement cache for database <nameofdatabase>; i.e., 
NO space for this sql statement in cache: 
SELECT COLUMN_NAME FROM TABLE_NAME WHERE _ID = '1337'. 
Please change your sql statements to use '?' for bindargs, instead of using actual values

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.

…low/older devices for a high number of queries.
@frapontillo frapontillo mentioned this pull request Mar 19, 2013
…ited by another class to implement some tricky logic.
…nerator

Conflicts:
	generator/res/provider.txt
… notify a change in the dataset by overriding the canNotify method.
@foxykeep foxykeep closed this in 7344b6a Mar 25, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant