Hi Patrick, Yes, the QuerySQLCache property was first into the 1.2.x stream and the functionality has been improved in the 2.0.x stream. So, changing the name might be difficult... We've thought about an overall uber-optimization or uber-cache property that would enable all of the associated caches. But, just merging one with another probably wouldn't fly with existing customers.
Kevin On Thu, Feb 11, 2010 at 12:15 PM, Patrick Linskey <[email protected]>wrote: > Hi, > > Is this out there in a released version yet? If not, I'd like to propose > changing the name to openjpa.QueryStatementCache or merge it with the > QueryCompilationCache or do something less JDBC-specific in the kernel. > > I'm working on a non-relational plug-in to OpenJPA, and the encroachment of > JDBC into the core kernel is causing some problems here and there. > > Incidentally, one of my changes is to create a default no-op implementation > of the query statement cache, to avoid some NPEs. > > -Patrick > > -- > Patrick Linskey > 202 669 5907 > >
