The query compilation cache doesn't cache data that would be directly useful for those calls. However, I'm all for optimizing those pathways, and the query compilation cache could be a place to store whatever intermediate caches we are able to assemble.
-Patrick On 10/11/07, Kevin Sutter <[EMAIL PROTECTED]> wrote: > Hi, > For those of you that are more verse with the QueryCompilationCache, I'm > wondering how difficult it would be to utilize this type of cache for the > em.find() operations as well as traversal of lazy relationships. We're > finding that these operations are more prevalent in customer's applications > than the use of createQuery() and createNamedQuery() operations and it's > affecting our performance (especially as compared to our competitors). So, > I am wondering whether anybody has put any thought in this space before I do > a deeper dive. Any suggestions or thoughts? > > Thanks, > Kevin > -- Patrick Linskey 202 669 5907
