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.
Difference between revisions of "EclipseLink/Examples/JPA/QueryOptimization"
< EclipseLink | Examples | JPA
(New page: EclipseLink allows users the option to optimize their queries through the use of a query hint. == Via Annotations == <code><pre> @Entity @Table(name="JPA_EMPLOYEE") @NamedQuery( name="f...) |
|||
| Line 1: | Line 1: | ||
| − | EclipseLink allows users the option to optimize their queries through the use of a query hint. | + | EclipseLink allows users the option to optimize their queries using batch and joined reading through the use of a query hint. |
== Via Annotations == | == Via Annotations == | ||
Revision as of 15:54, 15 October 2007
EclipseLink allows users the option to optimize their queries using batch and joined reading through the use of a query hint.
Via Annotations
@Entity
@Table(name="JPA_EMPLOYEE")
@NamedQuery(
name="findEmployeeByPK",
query="SELECT OBJECT(employee) FROM Employee employee WHERE employee.id = :id"),
hints={
@QueryHint(
name=EclipseLinkQueryHints.BATCH,
value=EclipseLinkQueryHints.BATCH),
@QueryHint(
name=EclipseLinkQueryHints.FETCH,
value=EclipseLinkQueryHints.FETCH),
}
)
public class Employee implements Serializable {
...
}
Via XML
<entity name="Employee" class="org.eclipse.testing.Employee" access="PROPERTY">
...
<named-query name="findAllEmployeesByFirstName">
<query>SELECT OBJECT(employee) FROM Employee employee WHERE employee.firstName = :firstname</query>
<hint name="eclipselink.batch" value="eclipselink.batch">
<hint name="eclipselink.join-fetch" value="eclipselink.join-fetch">
</named-query>
...
</entity>