Actually openjpa.jdbc.QuerySQLCache is a poor naming choice. That name openjpa.jdbc.QuerySQLCache originated from a rationale that the currently existing technique is a replacement of a previous implementation. But that rationale is technically incorrect.
I had preferred and proposed a more appropriate name such as openjpa.PreparedQueryCache (without any jdbc reference to the name -- because technically the current implementation is a kernel-aware artifact -- with a JDBC specific implementation). But I had not been able to find a solution without replacing/removing the previous implementation altogether, and hence to concede that poor naming suggestion. Caching technique/stratgey used for the latest implementation is so very different than the previous one that considering it as replacement will be a factual error. ----- Pinaki -- View this message in context: http://n2.nabble.com/openjpa-jdbc-QuerySQLCache-property-tp4556392p4557587.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.
