Ritika, You should not mark a JIRA issue as being resolved until all parts of the solution are complete -- coding, testing, and documentation. So, until those pieces are complete, we should leave the Issue open.
Kevin On 4/16/07, Ritika Maheshwari <[EMAIL PROTECTED]> wrote:
this issue should be marked resolved On 4/5/07, Ritika Maheshwari <[EMAIL PROTECTED]> wrote: > > It has not been documented in the OPENJPA documentation. > > > > > On 4/4/07, Patrick Linskey (JIRA) <[EMAIL PROTECTED]> wrote: > > > > > > [ > > https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486820 ] > > > > Patrick Linskey commented on OPENJPA-168: > > ----------------------------------------- > > > > Has this new feature been documented? > > > > > 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. > > > > >
