Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/DesignDocs/350469"
| Line 41: | Line 41: | ||
== Documentation == | == Documentation == | ||
| + | |||
| + | ==Work Required== | ||
| + | # Implement specification API | ||
| + | #: approx 3 day | ||
| + | # Testing | ||
| + | #: approx 2 days | ||
== Open Issues == | == Open Issues == | ||
Revision as of 09:05, 10 September 2012
Design Specification: JPA 2.1 Criteria Query framework Bulk Update/Delete support
Document History
| Date | Author | Version Description & Notes |
|---|---|---|
| 04 November 2011 | Gordon Yorke | Initial Doc creation |
Project overview
The next iteration of the Java Persistence API specification has added addition support for Bulk Update/Delete operations to the Criteria framework. This enhancement will cover the work involved to realize the implementation of this support
Concepts
The Criteria framework is an API for creating typesafe and/or dynamic Java Persistence queries. Similar in style to the EclipseLink Query and Expression framework. In previous version of the specification support for "UPDATE Employee e SET e.salary = :salary" and similar delete JPQL was not available using the Criteria API. Through the addition of CriteriaUpdate/CriteriaDelete classes support for bulk update/delete queries has now been added.
Requirements
Support Criteria bulk update/delete functionality through the implementation of the new CriteriaBuilder APIs, EntityManager APIs, CriteriaUpdate and CriteriaDelete.
Design Constraints
Design / Functionality
Testing
API
GUI
Config files
Documentation
Work Required
- Implement specification API
- approx 3 day
- Testing
- approx 2 days
Open Issues
This section lists the open issues that are still pending that must be decided prior to fully implementing this project's requirements.
| Issue # | Owner | Description / Notes |
|---|---|---|
| 1 | Because of the changes to the APIs the implementation will need a creative way to remain backward compatible. One option is a pluggable EntityManagerFactory that checks for the new APIs and if present produces the correct EntityManagerImpl for the libraries on the classpath. |
Decisions
This section lists decisions made. These are intended to document the resolution of open issues or constraints added to the project that are important.
| Issue # | Description / Notes | Decision |
|---|---|---|
Future Considerations
During the research for this project the following items were identified as out of scope but are captured here as potential future enhancements. If agreed upon during the review process these should be logged in the bug system.