openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abe White (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-168) sql optimize n rows query hint
Date Wed, 14 Mar 2007 20:48:09 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480920
] 

Abe White commented on OPENJPA-168:
-----------------------------------

I don't recall any way to know whether a given Select it is a top-level Select or a parallel
Select.  Note that if you take my advice and implement this as an ExpectedResultCount property
of SelectExecutor (which can also replace the isSingleResult propertyof Union), then you don't
need to know.  The query/storemanager/whatever that constructs the top-level select will set
the expected count based on hints / knowledge, and the dictionary will use it as needed. 
It won't get passed to parallel eager selects accidentally.

> 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
>
> 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.


Mime
View raw message