cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <>
Subject [jira] [Commented] (CAY-1935) EJBQL; Handling Collection as Parameter in IN Expression
Date Tue, 03 Jun 2014 17:28:01 GMT


Andrus Adamchik commented on CAY-1935:

I agree with the idea, and the patch looks good. So +1.

As a side note, at this point we don't care so much about compatibility with JPA spec, but
rather about eventual unification and merging of EJBQL and Expression. Proposed change is
in line with this goal, and seems to match the Expression grammar:
"in" ( namedParameter | "(" scalarCommaList ")" ) 

> EJBQL; Handling Collection as Parameter in IN Expression
> --------------------------------------------------------
>                 Key: CAY-1935
>                 URL:
>             Project: Cayenne
>          Issue Type: Improvement
>    Affects Versions: 3.2M1
>            Reporter: Andrew Lindesay
>         Attachments: CAY-1935-17may2014_in.patch
> Consider an EJBQL expression fragment...
> {noformat}
> ... p.toArtist IN (:artists)
> {noformat}
> ...where :artists may be bound to a Collection such as List or Set.  Cayenne presently
takes the named or positional parameter bound to the collection to be a _member_ of the set
of elements to which the lvar should be a member rather than the set itself.  Obviously this
doesn't process correctly.
> This patch will mean that in this situation above, the parameter bound to the Collection
is _expanded_ to actually be the set of elements to which the LVAR should be a member.
> There is some discussion of this [here|]
and [here|].
> Because some query systems support an unbracketed collection-parameter for IN, "EJBQLParser.jjt"
has been modified in this patch to allow for either approach; hence a query of the following
form would also be supported;
> {noformat}
> ... p.toArtist IN :artists
> {noformat}
> Note that this new functionality only applies if there is a _single_ unbracketed parameter
or if there is a _single_ bracketed parameter - it does not take effect if there are multiple
parameters in play.  If there is a single unbracketed parameter that is not a collection then
it will function as if that parameter were bracketed.

This message was sent by Atlassian JIRA

View raw message