[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608584#comment-16608584
]
Craig L Russell commented on JDO-652:
-------------------------------------
I'd much prefer IfThenElse as a name to IfElseExpression.
Also, have the "constructor" take three arguments: if, then, else. This makes
queries much more fluent. e.g.
IfThenElse<Double> ifExpr =
query.ifThenElse<Double>(cand.department.name.eq("Development"), 15000.0,
25000.0); query.filter(cand.salary.gt(ifExpr));
And as Michael says, have IfThenElse<Double> extend DoubleExpression
Or have the constructor be ifThenElse(Double.class,
cand.department.name.eq("Development"), 15000.0, 25000.0
> Provision of a typesafe refactor-friendly query capability for JDOQL
> --------------------------------------------------------------------
>
> Key: JDO-652
> URL: https://issues.apache.org/jira/browse/JDO-652
> Project: JDO
> Issue Type: New Feature
> Components: api, specification, tck
> Reporter: Andy Jefferson
> Assignee: Michael Bouschen
> Priority: Major
> Fix For: JDO 3.2
>
> Attachments: JDO-652-api-patch-Andy.txt, JDO-652-patch3.txt,
> typesafe.patch, typesafe_manifest.patch
>
>
> There are various querying capabilities of this type around. JPA2 has its
> Criteria query API. Third party solutions like QueryDSL also exist, in its
> case providing a JDOQL implementation (as well as JPQL, and HQL). We should
> seriously consider introducing something along these lines in the JDO2.4
> timeframe.
> There is a comparison of JPA Criteria with QueryDSL over at
> http://source.mysema.com/forum/mvnforum/viewthread_thread,49
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
