5 | Performance and memory usage of queries { @OneToMany(cascade = CascadeType.ALL) private List<MyEntityElement> list = new ArrayList |
5 | Removing an entity throws exception; private String name; private String surname; @OneToOne(cascade=CascadeType.ALL, fetch |
5 | Upgrade to 2.4.1_03.o.TVS.cascade(TVS.java:156) at com.objectdb.o.TVS.g(TVS.java:105) at com.objectdb.o.TVS.g(TVS |
5 | how to query by properties of onetomany relations? (Error 990) public static final class Foo { @OneToMany(cascade=CascadeType.PERSIST) private Set |
5 | virtual servers and one file="warning" /> <cache ref="weak" level2="256mb" /> <persist serialization="false" /> <cascade-persist |
5 | Upgrade to 2.4.1_02.cascade(TVS.java:156) at com.objectdb.o.TVS.g(TVS.java:105) at com.objectdb.o.TVS.g(TVS.java:93 |
5 | InternalException when reading a HashMap.o.TVS.cascade(TVS.java:157) at com.objectdb.o.TVS.b(TVS.java:106) at com.objectdb |
5 | Different behavior with persist() and queried instances?Hi, We have a simple class that by itself contains (among others) a property pointing to a collection: class Bla { @OneToMany(cascade = CascadeType.ALL) private List<AttributeEntity> metaAttributes = new ArrayList<AttributeEntity>(); } Now we do a simple em.persist(BlaInstance |
1 | [ObjectDB 2.2.6_02] Unexpected exception (Error 990) at com.objectdb.o.OBC.aJ(OBC.java:961).java:1143) at com.objectdb.o.TVS.j(TVS.java:169) at com.objectdb.o.TVS.cascade(TVS.java:156) at com |
1 | ObjectDB 2.3.3 with cascading persist after updating the database and before commit (issue #544). Fixed NullPointerException |
