Home » Search

About lazy

61-70 of 114Refresh
Forum
2

How to Remove records from many to many relationship tables in JPA

Conclusion { .... @ManyToMany( fetch = FetchType.LAZY, cascade = CascadeType.PERSIST) private List ... .LAZY, cascade = CascadeType.ALL) @Cascade(org.hibernate.annotations.CascadeType.DELETE_ORPHAN
Forum
2

Is it possible to commit only specific elements?

would have a subsequent question: now in the retrieval of my entities from the database, I am working in a lazy loading ... in said hashmaps) in a lazy loading context (without loading the whole lists), excluding using
Forum
2

Is it possible to remove parent/child entities without refresh?

  private long id;   @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL, mappedBy ... {   @Id   @GeneratedValue   private long id;   @ManyToOne(fetch = FetchType.LAZY, cascade
Forum
2

Iterating over large result set

with a hint "objectdb.result-fetch" set to "LAZY". Another option is to use a report query, i.e ... "objectdb.result-fetch" set to "LAZY". That was first thing I was trying to do, but because objects
Forum
2

List of Enum Values in an entity

detachment (e.g. defined as eager rather than lazy, or accessed) are available. One way to solve the problem is to change the fetch policy of the field from LAZY to EAGER:     private @OneToMany(fetch
Forum
2

Merge with Parent/Child entities not possible

= FetchType.LAZY, cascade = CascadeType.ALL, mappedBy = "parent", orphanRemoval = true)   @MapKey ... long id;   @ManyToOne(fetch = FetchType.LAZY, cascade = { CascadeType.PERSIST, CascadeType.MERGE
Forum
2

performance limit

, what when we will have few milion records, how to handle this. Everything is set to lazy loading, we tried indexing ... with lazy result loading, using the objectdb.result-fetch query's hint in order to separate query
Forum
2

Pre-detach loading: retrieval by navigation not working in if statement

BooleanValue entity. This is @OneToOne with explicit LAZY fetch. - A BooleanValue entity wraps ... wrapper FloatQuantity entity. This is @OneToOne with explicit LAZY fetch. - A FloatQuantity entity
Forum
2

removed objects stay with null field values in the reference

uUid; ... @OneToMany(fetch=FetchType.LAZY) public Set workflow = new HashSet ... is still in the database and loaded by a subsequent lazy loading ? No, after deleting an object it does not
Forum
2

Removing an entity throws exception

; @OneToMany(mappedBy = "customer", fetch= FetchType.LAZY) private List itemList; @OneToMany(mappedBy = "customer", fetch= FetchType.LAZY) private List