 32 | Exception in thread "main" [ObjectDB 2.2.9_04] javax.persistence.RollbackException
Failed to commit transaction: Attempt to reuse an existing primary key value (image.Meta:0) (error 613)
at com.objectdb.jpa.EMImpl.commit(EMImpl.java:277) I check the db by explorer.jar, and find |
30 | Internal ObjectDB error by read the primary key |
29 | and primary key separated by # (e.g. Point#1). A collection can be specified as a comma separated list ... to set a reference to an existing entity object, which has to be specified by type and primary key ... to an existing entity object, which has to be specified by type and primary key separated by # (e.g |
29 | databases do not support user defined primary keys, even though this is very useful in almost every application. ObjectDB supports user defined primary keys including composite primary keys. The support |
26 | ) Find by primary key. Find by primary key. Search for an entity of the specified class and primary key ... there. Parameters: entityClass - entity class primaryKey - primary key Returns: the found entity instance or null ... an entity type or the second argument is is not a valid type for that entity’s primary key or |
24 | javax.jdo.annotations Annotation Key Target: Fields (including property get methods) Annotation for the key of a map relation. Corresponds to the xml element "key". Since: JDO 2.1 String column Name of the column to store the key in. Name of the column to store the key in. Returns: name |
24 | (Class entityClass, Object primaryKey) Find by primary key. Find by primary key. Search for an entity of the specified class and primary key. If the entity instance is contained in the persistence context, it is returned from there. Parameters: entityClass - entity class primaryKey - primary key |
24 | Hello, I have a problem with inserting of many entities. We use strings as primary key and indices ... ? See both examples. Correction. The case with strings as primary key and indices needs only more ram memory ... keys are indeed much more efficient than String UID primary keys. The main reasons for this (ordered |
23 | are useful in representing composite primary keys as explained in the Primary Key section of the ObjectDB manual. |
23 | Automatically generated values are mainly useful for primary key fields, but are supported by ObjectDB also for regular (non primary key) persistent fields. At the field level, the @GeneratedValue with an optional GenerationType strategy is specified: The @GeneratedValue annotation |