[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929318#action_12929318
]
Andy Jefferson commented on JDO-652:
------------------------------------
Javadocs for what is proposed to be "javax.jdo.query" are at
http://www.datanucleus.org/javadocs/core/2.2/org/datanucleus/query/typesafe/package-summary.html
DN SVN trunk (and soon to be 2.2 M3) now has a functioning JDOQL "typesafe"
query API.
Amongst the areas to discuss
1. Naming convention for generated "Query" classes. Currently prefixed by "Q"
in this prototype
2. Way of obtaining candidate, parameter, variable, subquery. If the user wants
to access a field then they need to cast to the expression type. See the blog
entry for details. Ideally would like to avoid casting
3. Can we extend it to provide something for JDOQL *and* JPQL. That is, make
use of the "language" argument that JDO typically accepts on queries (not
implemented in the prototype) and have TypesafeJDOQLQuery, TypesafeJPQLQuery
(for example).
> 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.
