Home » Search

About lazy

21-30 of 115Refresh
Forum
18

Lazy Init / Eager / Join Fetch collection strategy ? What to choose ?

Hello, I'm doing some tests to choose the best collection fetch strategy. I have entities with many lazy collections and i don't want to load them all. (depends on context) In JPA / Hibernate world ... up the Lazy collection (by getting size() of Collection) is a very weak solution. In case of millions
Forum
18

problem with lazy loading - unittest project attached

STS 2.6.0. i have checked the zip content again and the test resource file spring-data-jpa-lazy ... becomes detached. Since the relationship between Foo And Bar is lazy - it is unavailable in
Issue
18

Cascade.ALL with LAZY fetchtype does not clean up all references on remove

Hello, I have a tree of entity classes that reference others using Cascade.ALL in combination with FetchType.LAZY. If I now delete a root entity using EntityManager.remove all leaf nodes will not be deleted. This only applies to the leaf nodes. If I add an additional the behaviour changes
Issue
16

Query in nested transaction returns detached entity if lazy-loaded

Query in nested transaction returns detached entity if lazy-loaded
Manual
13

Entity Management Settings

") specifies if lazy loading of entity objects content is enabled. Instantiating entity objects as hollow
Manual
13

JPA / JDO Class Enhancer

notifies ObjectDB whenever a persistent field is modified. Enhanced code enables lazy loading
JPA Doc
8

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: @Basic(fetch=LAZY) protected String getName() { return name; } Since: JPA 1.0
Issue
6

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

; @ManyToOne(fetch = FetchType.LAZY) @JoinTable(name = "Element_owns_Element ... . Because the ownedElements relationship is defined as LAZY (the default fetch type for to-many ... under FetchType.LAZY (which the above would seem to suggest is your default) is broken. Please investigate
Forum
6

Performance issues on aggregate query

; public Double usedSolutionObjectTypeVersion; @OneToMany(fetch=FetchType.LAZY) @Index public List actions = new ArrayList(); @OneToMany(fetch=FetchType.LAZY) @Index public List childNodes = new ArrayList();   @OneToMany(fetch=FetchType.LAZY) public List
JPA Doc
5

ElementCollection.fetch

on the persistence provider runtime that the collection elements must be eagerly fetched. The LAZY strategy is a hint to the persistence provider runtime. Default value: javax.persistence.FetchType.LAZY Since: JPA 2.0