[
https://issues.apache.org/jira/browse/CAY-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrus Adamchik updated CAY-1960:
---------------------------------
Description:
Based on the https://github.com/apache/cayenne/pull/16 pull request...
1. let's refactor Expression.fromString(..) into ExpressionFactory.exp(..).
Parameters may be passed either as a Map (traditional parameter binding) or as
a vararg in which case parameters will be bound positionally regardless of
their names.
In the later case names are ignored so e.g. the same name mentioned twice can
be bound to two different values. Also the later case would not allow
subexpression pruning.
2. Let's add shortcuts and(..), or(..) for ExpressionFactory.joinExp(..)
was:
Based on the https://github.com/apache/cayenne/pull/16 pull request...
1. let's refactor Expression.fromString(..) into ExpressionFactory.exp(..) and
Parameters may be passed either as a Map (traditional parameter binding) or as
a vararg in which case parameters will be bound positionally regardless of
their names.
In the later case names are ignored so e.g. the same name mentioned twice can
be bound to two different values. Also the later case would not allow
subexpression pruning.
2. Let's add shortcuts and(..), or(..) for ExpressionFactory.joinExp(..)
> ExpressionFactory.exp(..) , and(..), or(..)
> -------------------------------------------
>
> Key: CAY-1960
> URL: https://issues.apache.org/jira/browse/CAY-1960
> Project: Cayenne
> Issue Type: Sub-task
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Fix For: 3.2.M2
>
>
> Based on the https://github.com/apache/cayenne/pull/16 pull request...
> 1. let's refactor Expression.fromString(..) into ExpressionFactory.exp(..).
> Parameters may be passed either as a Map (traditional parameter binding) or
> as a vararg in which case parameters will be bound positionally regardless of
> their names.
> In the later case names are ignored so e.g. the same name mentioned twice can
> be bound to two different values. Also the later case would not allow
> subexpression pruning.
> 2. Let's add shortcuts and(..), or(..) for ExpressionFactory.joinExp(..)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
