[
https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484288
]
Patrick Linskey commented on OPENJPA-168:
-----------------------------------------
> 2. I don't think we need a FetchConfiguration instance variable.
My understanding is that you can often provide hints about how many results
might be returned, as well as whether one or many results will be loaded. So it
seems like we might want to expose some way for the user to specify for an
arbitrary query (or relation load) that they expect n records to be returned.
> 4. "getOptimizeClause" seems too generic.
Agreed. The optimizations tend to get tucked into different parts of the SQL
statement; this probably will end up needing to be significantly different for
different db back-ends.
> sql optimize n rows query hint
> ------------------------------
>
> Key: OPENJPA-168
> URL: https://issues.apache.org/jira/browse/OPENJPA-168
> Project: OpenJPA
> Issue Type: New Feature
> Reporter: David Wisneski
> Assigned To: David Wisneski
> Attachments: OPENJPA-168.patch.txt, OPENJPA-168.patch2.txt
>
>
> There werre various comments from Patrick, Abe and Kevin Sutter about the
> code that I checked related to Optimize hint. So I have gone back and
> relooked at this and wil be making some changes. At Kevin's suggestion I
> will do this through a JIRA feature so that folks will have opportunity to
> comment on this before the code is actually done and checked in.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
