Home » Search

About eager

41-50 of 128Refresh
Forum
3

Fetching Collections Puzzle

If I dont declare explicitly the fetch strategy for "children" as FetchType.Eager, then how can I ... to Eager, the children field of all my retrieved nodes are of size zero When I declare the FetchType as Eager, then isn't the database actually retrieving the whole graph stored in the database
Forum
3

can't get HashMap out of the database

(fetch=FetchType.EAGER). Outside the DAO method only fields that have already been loaded are available ... . In addition, you have to use the last build (2.3.2_04), since due to a bug (issue #552) eager load ... (fetch=FetchType.EAGER, cascade=CascadeType.ALL) private HashMap map = new HashMap
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=FetchType.EAGER) List flags; According to our checks this solves the problem, and produces
Forum
2

Optimistic locking: prevent version increment on entity collection attribute

of the owning side (Readings), added EAGER fetch to the collection no change. I have tried ... to add ManyToOne of the owning side (Readings), This should not make any difference. > added EAGER fetch to the collection no change. This should affect. An eager collection should be loaded
Forum
2

@ElementCollection of type enum

.EAGER) private Set permissions; package x.x.x.x public enum UserPermission ... and BASIC231. Conclusion: @ElementCollection(fetch = FetchType.EAGER) private Set permissions ... printing logs directly in the code. Desired case: @ElementCollection(fetch = FetchType.EAGER) containing
Forum
2

@OneToMany(fetch = FetchType.LAZY) list is always null

is enabled or not. I think it relates to the no-detach option, because all is OK when using EAGER ... application. > I think it relates to the no-detach option, because all is OK when using EAGER ... option is currently not fully supported, so if it doesn't work well in your project you will probably have to use EAGER when necessary. Vladiator
Forum
2

Listing large number of complicated objects with paging.

ms in the Explorer). The problem is probably with the extensive EAGER setting in Product, and particularly with eager fetch of inverse (mapped by) collections. Massive inverse fetch is currently ... the SELECT clause. Yes, I do remember that there is a problem with extensive EAGER use and mapped by
Issue
2

ArrayIndexOutOfBoundException

final class CacheableJobStat { @OneToOne(fetch = FetchType.EAGER) private CacheableJobInfo ji; @OneToOne(fetch = FetchType.EAGER) private CacheableJobLog jl; } Where CacheableJobInfo ... the @OneToOne(fetch = FetchType.EAGER) annotation. I am not sure wheather this annotation is allowed when not
Forum
2

TreeSet and compareTo() issue

.dropdownValue); } The dropdownValue's are accessed through a collection field in another class that uses eager fetch: @OneToMany(fetch = FetchType.EAGER) private Set dropdownValues = new ... :     @OneToMany(fetch = FetchType.EAGER, cascade=CascadeType.PERSIST)     private Set
Result
1

ObjectDB version 2.2.3

Version 2.2.3 Added support of @ElementCollection (for setting eager fetch of non entity collections, such as List). Improved performance of eager fetch in queries. Added Maven build enhancement to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in