Notice: This Wiki is now read only and edits are no longer 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/undelimited identifiers"
< EclipseLink | Development | JPA 2.0
(New page: = Cache APIs = JPA 2.0 Root | [http://bugs.eclipse.org/251908 Enhancement Request] ==Issue Summary== The specification has added support to always t...) |
(→Cache APIs) |
||
| Line 1: | Line 1: | ||
| − | = | + | = Undelimited Identifiers = |
[[EclipseLink/Development/JPA_2.0 | JPA 2.0 Root]] | | [[EclipseLink/Development/JPA_2.0 | JPA 2.0 Root]] | | ||
[http://bugs.eclipse.org/251908 Enhancement Request] | [http://bugs.eclipse.org/251908 Enhancement Request] | ||
Revision as of 08:33, 25 March 2009
Undelimited Identifiers
JPA 2.0 Root | Enhancement Request
Issue Summary
The specification has added support to always treat meta data identifiers as if they are "quoted" preserving case and allowing reserved words to be used.
See JPA 2.0 ED section 2.13 for details.
General Solution
Should be simple to process the ORM tag and update read in identifiers.
Work Required
- Develop tests
- approx 1 day
- Implement API
- approx 3 days