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/Examples/JPA/Migration/OpenJPA/QueryHints

< EclipseLink‎ | Examples‎ | JPA‎ | Migration‎ | OpenJPA
Revision as of 11:45, 24 September 2009 by Douglas.clarke.oracle.com (Talk | contribs) (Migrating OpenJPA to EclipseLink JPA: Query Hints)

Migrating OpenJPA to EclipseLink JPA: Query Hints

Within a JPA application there is support for specifying query hints which define provider specific behaviour. These hints can be specified in annotations, within the ORM XML files, or within application code. The query hint names are strings and therefore do not typically force compile time dependencies on a particular provider but the values for these hints may introduce dependencies. The following sections outline OpenJPA query hints and their corresponding EclipseLink JPA features.


Note: This migration information is based on the OpenJPA 1.2.1 documentation.


OpenJPA Hint Description EclipseLink JPA Equivalent Functionality
openjpa.hint.OracleSelectHint Specifies an Oracle specific query hint to be generated eclipselink.sql.hint
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.
openjpa.hint.

Back to the top