Home » Search

About lazy

41-50 of 115Refresh
JPA Doc
4

Basic.fetch

Annotation Element javax.persistence.Basic FetchType fetch (Optional) Defines whether the value of the field or property should be lazily loaded or must be eagerly fetched. The EAGER strategy is a requirement on the persistence provider runtime that the value must be eagerly fetched. The LAZY
JPA Doc
4

javax.persistence.ManyToOne

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

javax.persistence.OneToOne

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

ManyToOne.fetch

Annotation Element javax.persistence.ManyToOne FetchType fetch (Optional) Whether the association should be lazily loaded or must be eagerly fetched. The EAGER strategy is a requirement on the persistence provider runtime that the associated entity must be eagerly fetched. The LAZY strategy
JPA Doc
4

OneToOne.fetch

Annotation Element javax.persistence.OneToOne FetchType fetch (Optional) Whether the association should be lazily loaded or must be eagerly fetched. The EAGER strategy is a requirement on the persistence provider runtime that the associated entity must be eagerly fetched. The LAZY strategy
Forum
3

EntityManager JPA or JDO impl and different behavior

fetch annotation and the map values were still lazy loaded(using the latest objectdb 2.3.4_03). I ... to get to the bottom of LAZY/EAGER loading of maps.   In addition, non related. Since upgrading to 2.3.4_03 I can no longer ... another problem with lazy loading. In the attached project it's demonstrated how, by having a Map
Forum
3

Left join fetch behaviour doesn't retrieve children?

, I have a question for you ... I have implemented a lazy left join fetch feature ... back to ALL EAGER ( seems to be faster ... ) and stoped all kind of lazy initialization. Left join ... :27 CEST 2015 193152 entities retrieved Duration : 22 seconds LAZY INIT on call size() on each
Issue
3

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

, which using a serious of cascading lazy builder methods (with complex entity building and wiring ... -shot builder to clear lazy builder method triggers. */ private void reset ... // of entities using cascading lazy creation methods. } return project
Issue
3

Enhanced classes problem

Marta The cause is unclear yet, but I can confirm that it happens in lazy loading, which is supported only when classes are enhanced. As a workaround, please try to disable this lazy loading by setting ... ("objectdb.temp.no-lazy-o2o-inverse", "true"); or as a JVM parameter: > java -Dobjectdb.temp.no-lazy
Forum
2

Listing large number of complicated objects with paging.

runs blazing fast (22ms) but I think it's because Explorer lazy loads all that objects and load ... with a lazy fetch hint (as done by the Explorer). Another solution may be to use report queries, i.e. instead ... will try lazy fetch hint, but as I understand it will run 50 queries find(Product) while iterating