5 | Removing an element from an @OneToMany doesn't workHello. I have a Parent and Child entities. // in the parent @OneToMany(mappedBy = "parent", fetch = FetchType.EAGER, cascade = CascadeType.ALL) private List<Child> children; // in the child @ManyToOne private Parent parent; Somewhere I do this: parent.getChildren().remove(0 |
5 | Help understanding Entity behavior with JPAHi Support, We have a entity with an @Id entity which we then put into a list and store in an different entity inside a field defined as: @OneToOne(orphanRemoval=true, cascade=CascadeType.ALL, fetch=FetchType.EAGER) private Object payload; the list that we put in the 'payload' is an java.util |
5 | Relationships and tracking changes = GenerationType.AUTO) private Long id; @OneToMany (fetch=FetchType.LAZY,cascade=CascadeType.ALL, mappedBy |
5 | Attempt to refresh a non managed entity object (error 635) David Moshal This error message indicates invoking refresh (explicitly or implicitly by cascading |
5 | The server cannot start in CentOS> <enhancement agent="true" reflection="warning" /> <cache ref="weak" level2="0" /> <cascade |
5 | The exception "Attempt to remove a detached entity object" have no information about the entityHello, the exception "Attempt to remove a detached entity object" have no information about the detached entity. It is very hard, especially if the involved entities uses cascading, to find the removed call for the detached entity. It would be very helpful if you can add a few information |
5 | Bidirectional OneToMany is slow on updated items that can improve performance dramatically, is to avoid using mapped by collections: @OneToMany(cascade |
1 | ArrayIndexOutOfBoundsException on flush: @OneToMany(orphanRemoval=true, cascade=CascadeType.ALL) private Map<String, TaskNode> _nodes; The TaskNode |
1 | ObjectDB 2.4.7Fixed bugs in cascading merge and refresh. Fixed an internal java.lang.ArrayStoreException bug (com.objectdb.o.InvToOneLoadRequest). Fixed a regression bug (starting 2.4.4_13) in handling embeddable types. Fixed a performance regression (since 2.4.4_01) in query result retrieval. Added INFO level |
1 | ObjectDB 2.7.1Fixed a critical bug that may cause database corruption (issue #1977). Improved error messages on entity operation exceptions. Fixed a NullPointerException on cascading persist throw an unloaded collection (issue #2049). Fixed the location of a temporary file for index update (issue #2050). Fixed |
