71 | Failed to generate dynamic type objectdb.java.util.ArrayList.InternalException: com.objectdb.o.UserException: Failed to generate dynamic type objectdb.java.util.ArrayList com.objectdb.o.UserException: Failed to generate dynamic type objectdb.java.util.ArrayList at com ... to generate dynamic type objectdb.java.util.HashSet com.objectdb.o.UserException: Failed to generate |
71 | Enhancement of type is old and cannot be used: [2021-01-26 15:20:33 #22 type.user] Enhancement of type eu.extech.quant.listing.data ... #23 type] Type eu.extech.quant.listing.data.ProductListingRequest is not enhanced. [2021-01-26 15:20:33 #24 type] Type eu.extech.quant.listing.data.ProductListingStateChangeList is not |
71 | Cast in typed query the generic list type: @ElementCollection(fetch = FetchType.EAGER) private List<MySuperType> types = null; Now I can use "instanceof" within a query in order to select only elements of the specific type: SELECT o FROM OtherType o JOIN o.types t WHERE t instanceof MySpecificType But how can I cast |
70 | DB Doctor sets type to "unknown" for new fieldsHi, we are using ObjectDB 2.5.4_04 on Linux. We added two new Boolean fields to a persistable type ... to the schema as expected, however their type is set to unknown - we were expecting Boolean. The attached ... in DB Explorer select r.emergency from RecordingMetaData as r you will notice that the type (RSL |
70 | @AttributeOverrides , and postgresql + own TYPE even if i wanted to. In structure of DB is this. -- -- Name: address; Type: TYPE; Schema: artio; Owner: facman -- CREATE TYPE address AS ( street character varying, city character varying, state ... ); ALTER TYPE artio.address OWNER TO facman; AS you notice, in my project i have more schemats let say |
70 | DB Explorer cannot be opened after schema package renaming of entity typesThe DB Explorer cannot be opened after schema package renaming of entity types because it seems that deprecated entity types which are removed from our java project break the database. In the database the entity types and deprecated entity types can be part of the identical package. The schema |
70 | Wrong @Id type that have already changed their types you will have to 'touch' the objects and store them again, or use an ObjectDB version before the fix, with an UPDATE queries that change the IDs to the correct type ... explorer the type of the id column is displayed as long, as it shold be, but selecting only id column from |
70 | Custom collection types, nevertheless it causes some questions. I checked that i can easily change the type of collection between ... this for collections which are not in java.util package? if this collection type will be used in first app release to allow data to be imported to db, can we next changed this type to standard |
14 | Removing of an entity removes also another entity type some new ResolverMappings DELETE FROM ToleranceDefinition SELECT rm from ResolverMapping WHERE rm.type = 'interfaces' // there are also other types like 'scopes' em.remove(toleranceDefinition ... ', but it works without exception SELECT rm from ResolverMapping WHERE rm.type = 'interfaces' // now |
14 | delete of a collection in explorer changes typeaccidently we used the option delete on a collection of type ArrayList<ObjectNode>. On doing so the type changed to List<ObjectNode>. we are using explorer version 2.7.1_02 How can we change that back again ? hgzwicker Hans-Georg Zwicker Is it only an issue with the type of the field as shown by |
