You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2007/04/05 02:43:32 UTC

[jira] Commented: (OPENJPA-168) sql optimize n rows query hint

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


Re: [jira] Commented: (OPENJPA-168) sql optimize n rows query hint

Posted by Kevin Sutter <kw...@gmail.com>.
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 <ri...@gmail.com> wrote:
>
> this issue should be marked resolved
>
> On 4/5/07, Ritika Maheshwari <ri...@gmail.com> wrote:
> >
> > It has not been documented in the OPENJPA documentation.
> >
> >
> >
> >
> > On 4/4/07, Patrick Linskey (JIRA) <ji...@apache.org> 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.
> > >
> > >
> >
>

Re: [jira] Commented: (OPENJPA-168) sql optimize n rows query hint

Posted by Ritika Maheshwari <ri...@gmail.com>.
this issue should be marked resolved

On 4/5/07, Ritika Maheshwari <ri...@gmail.com> wrote:
>
> It has not been documented in the OPENJPA documentation.
>
>
>
>
> On 4/4/07, Patrick Linskey (JIRA) <ji...@apache.org> 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.
> >
> >
>

Re: [jira] Commented: (OPENJPA-168) sql optimize n rows query hint

Posted by Ritika Maheshwari <ri...@gmail.com>.
It has not been documented in the OPENJPA documentation.




On 4/4/07, Patrick Linskey (JIRA) <ji...@apache.org> 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.
>
>