11 | 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<DropdownValue> dropdownValues = new ... persist should be added to make the test valid: @OneToMany(fetch = FetchType.EAGER, cascade |
11 | EM.find() is suddenly slower = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH }) private ModelElementImpl element; @OneToMany (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH ... eager fetch that affects the performance of further operations. Could you please check build 2.8.6 |
11 | @ElementCollection of type enum.EAGER) private Set<UserPermission> permissions; package x.x.x.x public enum UserPermission ... and BASIC231. Conclusion: @ElementCollection(fetch = FetchType.EAGER) private Set<UserPermission> permissions ... printing logs directly in the code. Desired case: @ElementCollection(fetch = FetchType.EAGER) containing |
11 | Why are my Map entries not stored? id; @OneToMany(fetch = FetchType.EAGER, cascade=CascadeType.ALL, mappedBy = "ticket ... .EAGER) private Ticket ticket = null; [...] } public enum State { OPEN("Offen ... Martin Petzold I have now changed to and it is working: @OneToMany(fetch = FetchType.EAGER, cascade |
11 | @OneToMany(fetch = FetchType.LAZY) list is always null when using EAGER loading, but when I use LAZY with PersistenceUnit (not EntityManagerFactory), it fails ... think it relates to the no-detach option, because all is OK when using EAGER loading, but when I use ... fully supported, so if it doesn't work well in your project you will probably have to use EAGER when necessary. support Support |
11 | Listing large number of complicated objects with paging. (and therefore completes in 22 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 ... that there is a problem with extensive EAGER use and mapped by collections, but I can't repair this right now, so I'm |
9 | Multiple Collection Fields not update correctlyv2.8.8_2 I have an entity that has 2 collection fields: @OneToMany(fetch = FetchType.EAGER) Collection position; @OneToMany(fetch = FetchType.EAGER) Collection rotation; Now if I persist them so the values are: position has values 1.0f, 2.0, 3.0 rotation has values 4.0f, 5.0, 6.0 This works fine |
9 | Memory use in OneToMany relationships EAGER load (the default for collections is LAZY). There is a difference between using reflection mode ... may be changed in future versions, but the JPA rules remain: With EAGER you know that the referenced |
2 | Best practise loading big data that are not annotated as eager) in situations in which it is impossible to use lazy loading if the classes are enhanced. Eager / lazy setting can increase or decrease performance depending on the specific ... by eager / lazy setting. There may be other reasons. If you could post a simple basic test case |
1 | ClassCastException after upgrade to 2.3.5_03 { @Id String id; @OneToOne(orphanRemoval=true, cascade=CascadeType.ALL, fetch=FetchType.EAGER ... .EAGER) private Map<String, Object> metadata; ... In this case the "payload" field is a byte |
