About lazy

21-30 of 118Refresh
Issue
23

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
22

Query in nested transaction returns detached entity if lazy-loaded

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

Setting and Tuning of JPA Queries

"LAZY". When LAZY is used result entity objects are returned as references (with no content
Result
19

ObjectDB Object Database Features [2018-01-27]

. Lazy/Eager Loading Automatic pre-loading optimizations. Configurable JPA eager/lazy fetch and JPA
Result
19

ObjectDB Object Database Features [2018-10-27]

. Lazy/Eager Loading Automatic pre-loading optimizations. Configurable JPA eager/lazy fetch and JPA
Result
19

ObjectDB Object Database Features

are indexable. Indices are also used for fast ordering and aggregate calculations. Lazy/Eager Loading Automatic pre-loading optimizations. Configurable JPA eager/lazy fetch and JPA query FETCH JOIN
Manual
13

JPA / JDO Class Enhancer

notifies ObjectDB whenever a persistent field is modified. Enhanced code enables lazy loading
Manual
13

Entity Management Settings

") specifies if lazy loading of entity objects content is enabled. Instantiating entity objects as hollow
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