Prepared statement caching does not work
Bug #1168616 reported by
Joni Freeman
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BoneCP |
Fix Released
|
Medium
|
Wallace Wadge |
Bug Description
It looks like 0.8 version never returns cached PreparedStatements. I suspect that this check always resets the cached statement to null:
That line was changed in this commit:
https:/
I noticed this bug while working on Databench benchmark application (http://
To post a comment you must log in.
Yup. Same here. I've got a huge batch of millions of the very same insert statement. They're not cached at all.
With 0.7.1 the jmx statistics indicate caching, but still indicates the creation of prepared statements too.