[
https://issues.apache.org/jira/browse/OPENJPA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535782
]
Pinaki Poddar commented on OPENJPA-407:
---------------------------------------
> I think that it might be ok to ignore fetch, since I think it's the same as
> the one that was used to create the SelectImpl
Did not see the patch but a point comment is FetchConfiguration in constructing
a Select starts from a 'root' instance and then spawns other FetchConfiguration
instances as it traverses the fetch graph. But the spawned as well as the root
instance shares the same 'state' (ConfigurationState). They only differ by
'dynamic' state that tracks the current location in fetch graph traversal.
Effectively the shared root instances would be identify a fetch configuration
if one is considering to use it as a part of a lookup key.
> Cache SQL (or closer precursors to SQL) more aggressively
> ---------------------------------------------------------
>
> Key: OPENJPA-407
> URL: https://issues.apache.org/jira/browse/OPENJPA-407
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc, kernel, query, sql
> Affects Versions: 0.9.0, 0.9.6, 0.9.7, 1.0.0
> Reporter: Patrick Linskey
> Fix For: 1.1.0
>
> Attachments: OPENJPA-407.patch
>
>
> When data is not available in the data cache, OpenJPA dynamically creates SQL
> to look up the requested data. OpenJPA should more aggressively cache this
> SQL to accelerate pathways from a cache miss to the database.
> The generated SQL takes a number of factors into account, including the
> requested records, transaction status, currently-loaded data, and the current
> fetch configuration. Any caching would need to account for these factors as
> well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
