[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018385#comment-13018385
]
Matthew T. Adams commented on JDO-652:
--------------------------------------
Before I forget, there was another issue about how bulk update & delete affect
any callbacks that PC classes or listeners may implement. We discussed on the
call that it would be beneficial for the developer to make a conscious decision
to decide whether or not instance or listener callbacks should be invoked by
requiring all of the bulk update(..) and delete(..) methods to take a boolean
indicating whether callbacks should be invoked or not.
This would also be a new feature for the existing deletion by query feature,
since the specification currently requires that predeletion callbacks be
invoked.
In this way, the developer is required to tell JDO that he knows about the
callbacks and either wants or doesn't want to subvert the object model.
> 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
