[
https://issues.apache.org/jira/browse/OPENJPA-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925816#action_12925816
]
Kevin Sutter commented on OPENJPA-1827:
---------------------------------------
Disabling the QuerySQLCache affects the caching of generated SQL (which is
based on the JPQL queries). JPQL Queries that are used over and over again
will benefit from the generated SQL being cached. Otherwise, the SQL has to be
re-generated each time it is used.
So, the impact of disabling this particular QuerySQLCache depends on your
application. If you have a few JPQL Queries that are used extensively, then
you will pay a slight performance concern if the SQL has to be re-generated
every time the JPQL is used. But, if your application uses many different JPQL
Queries (maybe the JPQL string is modified based on usage), then the use of the
QuerySQLCache is not as important since we wouldn't find an "exact match" in
the cache anyway.
This problem still needs to be fixed. I was just trying to explain the
potential performance impact (since I mentioned the concern in the nabble
conversation).
Kevin
> ClassCastException / org.apache.openjpa.persistence.ArgumentException on
> heavy processing
> ------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1827
> URL: https://issues.apache.org/jira/browse/OPENJPA-1827
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.0.1
> Reporter: Norman Maurer
>
> For more details see:
> http://openjpa.208410.n2.nabble.com/ClassCastException-org-apache-openjpa-persistence-ArgumentException-on-heavy-processing-td5607876.html#a5607876
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
