5 | Unexpected exception (Error 990)) at java.lang.Thread.run(Unknown Source) zmirc Mircea Chirac Currently schema changes require |
5 | Is persistence version 2.1 supported? seem to like version 2.x persitence.xml schema .. --> <persistence version="2.1" xmlns="http://xmlns.jcp.org |
5 | @AttributeOverrides , and postgresql + own TYPE even if i wanted to. In structure of DB is this. -- -- Name: address; Type: TYPE; Schema: artio; Owner |
5 | em.flush(); em.clear(); loosing data and not persisting managed objects.persistence.Lob; import javax.persistence.Table; @Entity @Table(name = "TestEntity", schema |
5 | Problem with @OrderByWhen I use @OrderBy and supply multiple order fields I get and error when ObjectDB Explorer expands a instance of the entity. Example code: @Entity @Table(name="Defects", schema = "myDB") public class Defects implements Serializable { ... ... @OneToMany(mappedBy="defect |
5 | OutOfMemoryError on search after update on DB created with DB Doctor DB Doctor in recovery mode to generate a recovered DB file. No schema (and index) changes - just |
5 | First persist takes long time are only required for a new entity type (e.g. analyzing and persisting the type schema, allocating |
5 | mappedSuperClass and subClass DuplicatesWhen I subclass a mappedSuperClass, a table for both appears in the Explorer. Am I correct to expect that only the subclass appear? If so, please provided any clues for a remedy. Thanks ... billdotnet Bill The super class is shown in the Explorer to enable viewing its schema and to enable opening |
1 | ObjectDB 2.3.5 display in the Explorer schema window. Fixed merging a new entity object with application set primary key. |
1 | Unexpected exception (Error 990) on find of my entity look now like this: @Entity @Table(schema="ebene1") public class MyEntity |
