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/283430"
(→Decisions) |
|||
Line 88: | Line 88: | ||
{| class="FCK__ShowTableBorders" | {| class="FCK__ShowTableBorders" | ||
|- | |- | ||
− | ! Issue | + | ! Issue |
! Description / Notes | ! Description / Notes | ||
− | |||
− | |||
! Decision | ! Decision | ||
|} | |} |
Revision as of 17:42, 5 September 2010
Design Specification: Indexes
Document History
Date | Author | Version Description & Notes |
---|---|---|
2010-08-25 | James | 0.1 Draft |
Project overview
The ability to define database indexes and have EclipseLink's DDL generation generate them.
Concepts
An index is a database structure define for a table to improve query and lookup performance for a set of columns.
Requirements
Support defining indexes in JPA through annotations. Support defining indexes in JPA through XML.
Design Constraints
Must be database independent.
Functionality
An @Index annotation and XML will be added. An index can be defined on an Entity, or attribute. For the Entity it must define a set of columns to index, the table will be defaulted. For an attribute the table and column will be defaulted.
The name of the index will be default toIssue # | Owner | Description / Notes |
---|---|---|
1 | What databases support indexes, do any use a different syntax? |
Decisions
Issue | Description / Notes | Decision |
---|
Future Considerations
- Other DDL options.