Back to Top

"Reached MAX size for compiled-sql statement cache" warning

4 posts / 0 new
Last post
snappingturtle
Offline
Last seen: 9 years 5 months ago
Joined: 09/19/2010 - 15:32
"Reached MAX size for compiled-sql statement cache" warning

In case the devs haven's seen this message, after booting cyanogenmod 6 I was doing a logcat and noticed the following. It's apparently just a warning, but it might cause a performance penalty.

W/Database( 662): Reached MAX size for compiled-sql statement cache for database /data/data/com.snoggdoggler.android.applications.doggcatcher.v1_0/databases/rss; i.e., NO space for this sql statement in cache: UPDATE item SET play_max_position=?, enclosure_url=?, duration=?, title=?, pub_date=?, description=?, link=?, length=?, consumed_state=?, play_position=? WHERE item_id=33010. Please change your sql statements to use '?' for bindargs, instead of using actual values

eric
Offline
Last seen: 1 week 22 hours ago
Joined: 11/06/2008 - 22:02
Bindings

That's a pretty strange warning considering there are only about 10 different queries in the app...and more importantly...the recommendation is to use ? bindings. That update statement (and all others) does use ? bindings.

I'll check the timings on that query but it looks like it should be ok.

Thanks for letting me know.

packy
Offline
Last seen: 2 years 5 months ago
Joined: 07/27/2010 - 13:01
bindings

Perhaps it's recommending that the "WHERE item_id=" part use a ? binding as well.

eric
Offline
Last seen: 1 week 22 hours ago
Joined: 11/06/2008 - 22:02
Binds in the where

The db api has a parameter for bind vars on the where clause but it's missing from the documentation. I can probably guess enough to get it working though.

I created an issue for this - http://mantis.snoggdoggler.com/view.php?id=649