You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cayenne.apache.org by Bob Schellink <sa...@gmail.com> on 2018/08/15 17:07:37 UTC
EJBQL vs JPAQL
Hi all,
Would it make sense to rename EJBQLQuery to JPAQLQuery? Not sure is there
is a difference between the two languages, but the name JPAQL is more
commonly used.
Kind regards
Bob
Re: EJBQL vs JPAQL
Posted by Andrus Adamchik <an...@objectstyle.org>.
We need to decide. "select" is first on the list. Update and delete will require separate query objects.
Andrus
> On Aug 15, 2018, at 9:21 PM, Bob Schellink <sa...@gmail.com> wrote:
>
> Interesting. Would that still support update/delete? Or selects only?
>
> On Wed, Aug 15, 2018 at 7:23 PM Andrus Adamchik <an...@objectstyle.org>
> wrote:
>
>> You are totally right. EJBQL name is obsolete and was borrowed at one time
>> from the JPA spec before it got renamed there.
>>
>> There is a more ambitious plan for it though - simply make it a parseable
>> String representation of ObjectSelect query. It requires ObjectSelect to
>> catch up on some of the functionality only available in EJBQLQuery now, but
>> it is getting pretty close.
>>
>> Andrus
>>
>>
>>> On Aug 15, 2018, at 8:07 PM, Bob Schellink <sa...@gmail.com> wrote:
>>>
>>> Hi all,
>>>
>>> Would it make sense to rename EJBQLQuery to JPAQLQuery? Not sure is there
>>> is a difference between the two languages, but the name JPAQL is more
>>> commonly used.
>>>
>>> Kind regards
>>>
>>> Bob
>>
>>
Re: EJBQL vs JPAQL
Posted by Bob Schellink <sa...@gmail.com>.
Interesting. Would that still support update/delete? Or selects only?
On Wed, Aug 15, 2018 at 7:23 PM Andrus Adamchik <an...@objectstyle.org>
wrote:
> You are totally right. EJBQL name is obsolete and was borrowed at one time
> from the JPA spec before it got renamed there.
>
> There is a more ambitious plan for it though - simply make it a parseable
> String representation of ObjectSelect query. It requires ObjectSelect to
> catch up on some of the functionality only available in EJBQLQuery now, but
> it is getting pretty close.
>
> Andrus
>
>
> > On Aug 15, 2018, at 8:07 PM, Bob Schellink <sa...@gmail.com> wrote:
> >
> > Hi all,
> >
> > Would it make sense to rename EJBQLQuery to JPAQLQuery? Not sure is there
> > is a difference between the two languages, but the name JPAQL is more
> > commonly used.
> >
> > Kind regards
> >
> > Bob
>
>
Re: EJBQL vs JPAQL
Posted by Andrus Adamchik <an...@objectstyle.org>.
You are totally right. EJBQL name is obsolete and was borrowed at one time from the JPA spec before it got renamed there.
There is a more ambitious plan for it though - simply make it a parseable String representation of ObjectSelect query. It requires ObjectSelect to catch up on some of the functionality only available in EJBQLQuery now, but it is getting pretty close.
Andrus
> On Aug 15, 2018, at 8:07 PM, Bob Schellink <sa...@gmail.com> wrote:
>
> Hi all,
>
> Would it make sense to rename EJBQLQuery to JPAQLQuery? Not sure is there
> is a difference between the two languages, but the name JPAQL is more
> commonly used.
>
> Kind regards
>
> Bob