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/Development/JPA 2.0/query definition api"
< EclipseLink | Development | JPA 2.0
Line 24: | Line 24: | ||
#QueryBuilder.rebuildFrom(Root) | #QueryBuilder.rebuildFrom(Root) | ||
#: reformulates expression from new root. Usefull for reusing expressions on new queries | #: reformulates expression from new root. Usefull for reusing expressions on new queries | ||
+ | |||
+ | == Restrictions ++ | ||
+ | # Selection and Where must have at least one matching root to form query, otherwise illegal argument results |
Revision as of 12:55, 14 July 2009
Contents
Query Definition API
JPA 2.0 Root | Enhancement Request
Issue Summary
JPA 2.0 specification has introduced a comprehensive object oriented query definition API which compliments JPQL.
This feature is covered in section 5 of the specification.
General Solution
Should be a simple translation to EclipseLink Queries and Expressions but will be work intensive. Some methods and interfaces can not be completed until the equivalent functionality has been added to EclipseLink
- - see Entity Type Expressions
- - see Collection Parameters for IN
- - see CASE Expressions
Work Required
- Develop model for testing
- approx 4 day
- Update Processing
- approx 13 days - creating query definition implementation.
Extensions
- QueryBuilder.rebuildFrom(Root)
- reformulates expression from new root. Usefull for reusing expressions on new queries
== Restrictions ++
- Selection and Where must have at least one matching root to form query, otherwise illegal argument results