About hints

41-50 of 100Refresh
JPA Doc
4

javax.persistence.OneToOne

runtime that the associated entity must be eagerly fetched. The LAZY strategy is a hint
JPA Doc
4

ManyToMany.fetch

is a hint to the persistence provider runtime. Default value: javax.persistence.FetchType.LAZY Since: JPA 1.0
JPA Doc
4

ManyToOne.fetch

is a hint to the persistence provider runtime. Default value: javax.persistence.FetchType.EAGER Since: JPA 1.0
JPA Doc
4

OneToMany.fetch

is a hint to the persistence provider runtime. Default value: javax.persistence.FetchType.LAZY Since: JPA 1.0
JPA Doc
4

OneToOne.fetch

is a hint to the persistence provider runtime. Default value: javax.persistence.FetchType.EAGER Since: JPA 1.0
JPA Doc
4

QueryHint.name

Annotation Element javax.persistence.QueryHint String name Name of the hint. Since: JPA 1.0
JPA Doc
4

QueryHint.value

Annotation Element javax.persistence.QueryHint String value Value of the hint. Since: JPA 1.0
Forum
2

how to query by properties of onetomany relations? (Error 990)

objects. i adapted my query and it works like expected. thanks for the hint Support of direct ... but it is JPA portable. ObjectDB can enforce using standard JPQL by setting the following query hint ... , which is a union of JPQL and JDOQL + ObjectDB extensions. When the query language is set to JPQL using a hint
Forum
2

Is 2 level cache in use?

in queries). You may try the following undocumented ObjectDB query hint and check if it helps ... the primary data. Currently this hint must be set at the query level (as demonstrated above) - but it should be supported in all other query hint scopes in future versions. Thanks for the explanation. I
Forum
2

Pessimistic Lock Timeouts setting

. However, there is a standardised query 'hint' that can be setup to make the underlying DB lock a record for a specific time. The hint property is: "javax.persistence.lock.timeout" I have a situation ... (hence why they made it a 'hint' - that should be considered non-portable). Thanks again for the prompt answers. In