You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by Joel Halbert <jo...@su3analytics.com> on 2011/02/08 12:36:01 UTC
caching & use of openjpa.jdbc.QuerySQLCache
Hi,
What's the difference between these properties?
openjpa.QueryCache
openjpa.jdbc.QuerySQLCache
My understanding was that QueryCache controlled caching of result data, and QuerySQLCache
controlled caching of the mapping from JPQL to SQL statements (i.e. not data caching).
Given this understanding I thought it necessary to set only 'openjpa.QueryCache=false' if I did not want the data results from a query to be cached.
What I am actually seeing is result data being cached unless 'openjpa.jdbc.QuerySQLCache=false' is set.
Is this expected behaviour?
I'm using 2.0.1.
Thanks
Joel
Re: caching & use of openjpa.jdbc.QuerySQLCache
Posted by Michael Dick <mi...@gmail.com>.
Your understanding is correct. The cached data appears to be coming from the
connection pool or at least related to the pool.
For other readers' reference see this thread :
http://openjpa.208410.n2.nabble.com/How-to-disable-caching-td6003755.html.
-mike
On Tue, Feb 8, 2011 at 5:36 AM, Joel Halbert <jo...@su3analytics.com> wrote:
> Hi,
>
> What's the difference between these properties?
>
> openjpa.QueryCache
> openjpa.jdbc.QuerySQLCache
>
>
> My understanding was that QueryCache controlled caching of result data, and
> QuerySQLCache
> controlled caching of the mapping from JPQL to SQL statements (i.e. not
> data caching).
>
> Given this understanding I thought it necessary to set only
> 'openjpa.QueryCache=false' if I did not want the data results from a query
> to be cached.
>
> What I am actually seeing is result data being cached unless
> 'openjpa.jdbc.QuerySQLCache=false' is set.
>
> Is this expected behaviour?
>
> I'm using 2.0.1.
>
> Thanks
> Joel
>
>