[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929581#action_12929581
]
Andy Jefferson commented on JDO-652:
------------------------------------
Thx for your feedback Matthew.
I actually updated DN SVN this morning with some changes for casting, and also
the most recent blog entry examples to match. The casting isn't there now (at
least on the examples I've worked through). The main things on this change are
* use static method on Query class to get the candidate.
* use static method on Query class to get variable of that type
* use xxxParameter methods on TypesafeQuery to get the XXXExpression for the
parameter (e.g stringParameter(paramName), doubleParameter(paramName).
* multiple select() methods on TypesafeSubquery so we can get the correct
XXXExpression there too.
Step in the right direction at least
> 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
> Fix For: JDO 3 maintenance release 1
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
