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/374688"
< EclipseLink | DesignDocs
(→Design Specification: Join with ON clause) |
|||
| Line 1: | Line 1: | ||
<div style="margin:5px;float:right;border:1px solid #000000;padding:5px">__TOC__</div> | <div style="margin:5px;float:right;border:1px solid #000000;padding:5px">__TOC__</div> | ||
| − | = Design Specification: | + | = Design Specification: Converter support = |
[http://bugs.eclipse.org/374688 ER 374688] | [http://bugs.eclipse.org/374688 ER 374688] | ||
| Line 18: | Line 18: | ||
== Project overview == | == Project overview == | ||
| − | JPA 2.1 will add support for Converters. Currently converters are pieces of code that are | + | JPA 2.1 will add support for Converters. Currently converters are pieces of code that are responsible for converting from an attribute type and value to the corresponding database type and value. |
== Concepts == | == Concepts == | ||
| Line 26: | Line 26: | ||
== Requirements == | == Requirements == | ||
| − | + | * Auto-apply converters must not be applied to disallowed mapping types (ie Id, Version etc) | |
== Design Constraints == | == Design Constraints == | ||
Revision as of 15:21, 20 March 2012
Design Specification: Converter support
Document History
| Date | Author | Version Description & Notes |
|---|---|---|
| 19 March 2012 | Gordon Yorke | Initial Document created |
Project overview
JPA 2.1 will add support for Converters. Currently converters are pieces of code that are responsible for converting from an attribute type and value to the corresponding database type and value.
Concepts
Requirements
- Auto-apply converters must not be applied to disallowed mapping types (ie Id, Version etc)
Design Constraints
Design / Functionality
Testing
API
GUI
Config files
Documentation
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 |
|---|---|---|
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.