About hints

21-30 of 100Refresh
JPA Doc
6

find(entityClass, primaryKey, properties)

context, it is returned from there. If a vendor-specific property or hint is not recognized ... and vendor-specific properties and hints Returns: the found entity instance or null if the entity
JPA Doc
6

getHints()

Method javax.persistence.Query Map getHints() Get the properties and hints and associated values that are in effect for the query instance. Returns: query properties and hints Since: JPA 2.0
JPA Doc
6

getProperties()

Method javax.persistence.EntityManager Map getProperties() Get the properties and hints and associated values that are in effect for the entity manager. Changing the contents of the map does not change the configuration in effect. Returns: map of properties and hints in effect for entity manager Since: JPA 2.0
JDO Doc
6

javax.jdo.datastore.Sequence

. Since: JDO 2.0 void allocate(int additional) Provides a hint to the implementation that the application will need additional sequence value objects in short order. Provides a hint
JPA Doc
6

javax.persistence.Basic

on the persistence provider runtime that the value must be eagerly fetched. The LAZY strategy is a hint ... may be null. This is a hint and is disregarded for primitive types; it may be used in schema generation
JPA Doc
6

javax.persistence.FetchType

on the persistence provider runtime that data must be eagerly fetched. The LAZY strategy is a hint ... . The implementation is permitted to eagerly fetch data for which the LAZY strategy hint has been specified. Example
JPA Doc
6

refresh(entity, properties)

, and overwriting changes made to the entity, if any. If a vendor-specific property or hint is not recognized ... -specific properties and hints Throws: IllegalArgumentException - if the instance is not an entity or
JDO Doc
6

javax.jdo.Query

1.0 void compile() Verify the elements of the query and provide a hint to the query to prepare and optimize an execution plan. Verify the elements of the query and provide a hint to the query
Forum
5

NULL prefered in ORDER BY?

Hi! Is there a way to NOT prefer NULL in Order BY? I.e. assume this: @Entity class Hint {     private String name; } @Entity class Test {     private Hint hint; } I've got a few Test entries, some do have a hint assigned, some do not (NULL). Now when I do something like SELECT FROM
JDO Doc
4

allocate(additional)

Method javax.jdo.datastore.Sequence void allocate(   int additional ) Provides a hint to the implementation that the application will need additional sequence value objects in short order. There is no externally visible behavior of this method. It is used to potentially improve the efficiency