 13 | Hello, we must change (extend) our entity model and therefor we convert the type of some entities ... Embedded Systems AG References to entity objects are implemented by ObjectDB as a pair of (type + id ... is faster when its exact type is known. Following your request we added a new option to version 1.7.0_02 |
13 | .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 ... .objectdb.o.InternalException: com.objectdb.o.UserException: Failed to generate dynamic type |
13 | 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 ...
);
ALTER TYPE artio.address OWNER TO facman; AS you notice, in my project i have more schemats let |
13 | Hi, 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 |
13 | ResolverMappings DELETE FROM ToleranceDefinition SELECT rm from ResolverMapping WHERE rm.type = 'interfaces' // there are also other types like 'scopes' em.remove(toleranceDefinition); // the 'attached ... without exception SELECT rm from ResolverMapping WHERE rm.type = 'interfaces' // now the ResolverMappings |
13 | , nevertheless it causes some questions. I checked that i can easily change the type of collection between ... achieve 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 |
13 | accidently we used the option delete on a collection of type ArrayList. On doing so the type changed to List. we are using explorer version 2.7.1_02 How can we change that back again ? Is it only an issue with the type of the field as shown by the Explorer or |
13 | type com.package.RootContainer (error 361) It seems that all dependent classes are on the classpath ... ? in a doc there is output from enhancer [ObjectDB 2.0] 3 persistable types have been enhanced: test.MyEntity1 test.MyEntity2 test.MyEmbeddable 2 NON persistable types have been enhanced: Main test |
13 | 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). We are using ObjectDB ... . Also we have noticed that using tree view of ObjectDB explorer the type of the id column |
13 | > The CollectionJoin interface is the type of the result of joining to a collection ... . Parameters: name - alias Returns: selection item Since: JPA 2.0 Expression as(Class type) Perform ... upon the expression, returning a new expression object. This method does not cause type conversion: the runtime type |