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/DesignDocs/350487"
(New page: <div style="margin:5px;float:right;border:1px solid #000000;padding:5px">__TOC__</div> = Design Specification: <feature-name> = [http://bugs.eclipse.org/350487 ER 350487] == Document His...) |
|||
| 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: Support for Stored Procedure Calls = |
[http://bugs.eclipse.org/350487 ER 350487] | [http://bugs.eclipse.org/350487 ER 350487] | ||
| Line 11: | Line 11: | ||
! Version Description & Notes | ! Version Description & Notes | ||
|- | |- | ||
| − | | | + | | 21 November 2011 |
| − | | | + | | Gordon Yorke |
| − | | | + | | Initial document creation |
|} | |} | ||
== Project overview == | == Project overview == | ||
| − | + | JPA specification 2.1 has introduced support for executing Stored Procedure calls. This includes a new StoredProcedureQuery API. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== Concepts == | == Concepts == | ||
| Line 30: | Line 26: | ||
== Requirements == | == Requirements == | ||
| − | + | Beyond implementation of the APIs ensure the surrounding behavioural requirements as outlined in section 3.8 are met. | |
== Design Constraints == | == Design Constraints == | ||
Revision as of 17:16, 21 November 2011
Design Specification: Support for Stored Procedure Calls
Document History
| Date | Author | Version Description & Notes |
|---|---|---|
| 21 November 2011 | Gordon Yorke | Initial document creation |
Project overview
JPA specification 2.1 has introduced support for executing Stored Procedure calls. This includes a new StoredProcedureQuery API.
Concepts
Present any concepts relevant to the feature.
Requirements
Beyond implementation of the APIs ensure the surrounding behavioural requirements as outlined in section 3.8 are met.
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.