[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036690#comment-13036690
]
Andy Jefferson commented on JDO-652:
------------------------------------
Re: Query result specification
There are two approaches ... constructor argument, or execute argument. If you
do as constructor argument then you can't change the result class thereafter.
With "normal" API you can change the result class/result definition after
construction (i.e reuse Query objects). Consequently I don't see a sensible
alternative to what is already there.
Re: Parameter specification
Why is it so important to pass the parameter values in to execute() ? Obviously
we could add an argument (Map?, array?) to executeXXX() but I don't see an
alternative to passing the result in also. What difference does it make if a
parameter is "state"?
> 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
>
> Attachments: 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
