Home » Search

About fetch

131-140 of 200Refresh
JPA Doc
3

FetchType.EAGER

Enum Constant javax.persistence.FetchType EAGER Defines that data must be eagerly fetched. Since: JPA 1.0
JPA Doc
3

FetchType.LAZY

Enum Constant javax.persistence.FetchType LAZY Defines that data can be lazily fetched. Since: JPA 1.0
JDO Doc
3

getFetchGroup(cls, name)

for the FetchGroup name - the name of the fetch group Returns: the FetchGroup Throws: JDOUserException
JPA Doc
3

getReference(entityClass, primaryKey)

Method javax.persistence.EntityManager T getReference(   Class entityClass,   Object primaryKey ) Get an instance, whose state may be lazily fetched. If the requested instance does not exist in the database, the EntityNotFoundException is thrown when the instance state is first accessed
JDO Doc
3

hashCode()

Method javax.jdo.FetchGroup int hashCode() Return the hashCode for this instance. The hash code should combine both the class and fetch group name. The hash codes for two equal instances must be identical. Returns: the hash code Since: JDO 2.2
JDO Doc
3

javax.jdo.spi.JDOImplHelper

constructor ObjectIdFieldSupplier: the field value is fetched from the ObjectIdFieldSupplier
JPA Doc
3

javax.persistence.criteria.JoinType

javax.persistence.criteria Enum JoinType java.lang.Object java.lang.Enum javax.persistence.criteria.JoinType Implemented Interfaces: Serializable, Comparable Defines the three types of joins. Right outer joins and right outer fetch joins
JDO Doc
3

jdoNewObjectIdInstance(o)

: the field value is fetched from the ObjectIdFieldSupplier and passed to the single field identity
JDO Doc
3

makeTransient(pc, useFetchPlan)

. useFetchPlan - whether to use the current fetch plan to determine which fields to load and which instances to make transient Since: JDO 2.0
JDO Doc
3

makeTransientAll(pcs, useFetchPlan)

. Parameters: pcs - the root instances to make transient. useFetchPlan - whether to use the current fetch