Skip to main content

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.

Jump to: navigation, search

EclipseLink/UserGuide/JPA/Advanced JPA Development/Schema Generation/Index

EclipseLink JPA

Eclipselink-logo.gif
EclipseLink
Website
Download
Community
Mailing ListForumsIRCmattermost
Issues
OpenHelp WantedBug Day
Contribute
Browse Source


@Index Annotation and <index> XML

This section is in progress...

An index is a database structure defined for a table, to improve query and look-up performance for a set of columns. Use the @Index annotation in code or the <index> element in the orm.xml desciptor to create an index on a table and to have EclipseLink's DDL generator generate it.

An index can be defined on an Entity class or on an attribute:

  • For the Entity it must define a set of columns to index. The table is defaulted.
  • For an attribute, the table and column are defaulted.

The name of the index defaults to _<column>_INDEX, but a name should be provided.

An IndexDefinition in the schema framework allows defining, creating, and dropping indexes using code.

The @Index annotation creates an IndexDefinition and stores it on the descriptor's DatabaseTable.

During default schema generation the DefaultSchemaGenerator adds the IndexDefinition to the TableDefinition to be created.

The IndexDefinition is used to create indexes for primary key and unique constraints. Support for indexes is defined in the platform. By default a platform is assumed to support indexes. MySQL requires special drop syntax to include the table name in the drop statement.


Configuration File

  • orm.xml
<index name="EMP_NAME_INDEX" table="EMPLOYEE" unique="true">
    <column>F_NAME</column>
    <column>L_NAME</column>
</index>

Eclipselink-logo.gif
Version: 2.2.0 DRAFT
Other versions...

Back to the top