Exactly. The idea is to have a single query combining the capabilities
of SelectQuery and EJBQLQuery, with API allowing to build it in the
code (as well as keeping the String representation as an option).
Andrus
On Apr 27, 2010, at 5:51 PM, Andrew Lindesay wrote:
> Hello Andrus;
>
>> ...unfortunate situation, as there are plans for SelectQuery-like
>> API for EJBQL in 3.1, but...
>
> I just want to check on this one; you are planning to expose an
> "object interface" to the EJBQL in 3.1 such that arbitrary EJBSQL
> queries could be assembled in-code as opposed to through text
> assembly?
>
> Do you feel that such a model would supersede the SelectQuery/
> Expression approach or sit alongside it?
>
> cheers
>
> ___
> Andrew Lindesay
> www.silvereye.co.nz
>
>
This archive was generated by hypermail 2.0.0 : Tue Apr 27 2010 - 06:11:56 EDT