Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/JPA/Migration/OpenJPA/QueryHints"

< EclipseLink‎ | Examples‎ | JPA‎ | Migration‎ | OpenJPA
(Migrating OpenJPA to EclipseLink JPA: Query Hints)
Line 1: Line 1:
 
== 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: Under Construction''
  
 +
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. If any query hint related migration information is missing or incomplete please log a [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EclipseLink&bug_severity=enhancement documentation enhancement request] referencing this page and provide details of your migration challenge.
 +
 +
__TOC__
  
 
<blockquote>
 
<blockquote>
Line 16: Line 19:
 
|-
 
|-
 
| openjpa.hint.OracleSelectHint || Specifies an Oracle specific query hint to be generated  || eclipselink.sql.hint
 
| 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. || ||
 
 
|}
 
|}

Revision as of 04:52, 3 November 2009

Migrating OpenJPA to EclipseLink JPA: Query Hints

NOTE: Under Construction

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. If any query hint related migration information is missing or incomplete please log a documentation enhancement request referencing this page and provide details of your migration challenge.

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

Back to the top