About lazy

91-100 of 118Refresh
Forum
1

Does ObjectDB support @Parent for @Embeddable reference to parent?

property access, rather than the annotated fields, as shown on the first post. Sorry, excuse lazy copy
Forum
1

Error 363 - Failed to read value of inverse relationship

String text; @OneToMany(/*fetch=FetchType.LAZY, cascade=CascadeType.ALL, */mappedBy
Forum
1

Is 2 level cache in use?

:  query.setHint("objectdb.result-fetch", "lazy"); This is an instruction to the ObjectDB server to return
Forum
1

Is it ok to put list or map of embeddable objects in entity ?

would not be very efficient). I am not sure how ORM JPA implementations handle this. About the slow lazy
Forum
1

Is there a way to set EAGER fetch on all "ToMany" collection relationships

Given that the default seems to be FetchType.LAZY for all collections @OneToMany and @ManyToMany. Such as a configuration option. Instead of having to explicitly set fetch in annotation code in every relationship. No. There is no such configuration option, since having EAGER as the fetch type
Forum
1

Join query problem with new statetment

;     (...)     @ManyToMany(targetEntity = Product.class, fetch = FetchType.LAZY)     private List
Issue
1

JPQL Case Statements (JPA 2.0)

) - even when most relationship fields of an entity are forced lazy.   webel maratkalibek
Forum
1

Level 2 cache not hit in @ManyToOne

this behavior by setting the "objectdb.result-fetch" query hint to LAZY. By doing that you instruct
Issue
1

Mapped by fields are not initialized by JOIN FETCH in queries

As demonstrated in this forum thread, a mapped by collection field with lazy fetch mode is not initialized in results of a query that uses JOIN FETCH on that collection field (when enhancement is used).   Build 2.4.1_06 fixes this issue (fields are now initialized and the test in the forum passes
Forum
1

Merge of entity classes with "mapped by" very slow

Hi, I have found a strange behavior when merging entities with "mapped by" set on @OneToMany relation. Even if object is fetched with find on the same transaction, merge is very slow. It's because on merge every single relation marked as LAZY is fetch from database. Attached two examples