43 | remove & persist in same transaction => Attempt to reuse an existing primary key valueHello Support, in our configuration (FlushModeType.AUTO) is the execution of em.find(Entity.class ... to the existing otherwise we create it. Now we got the problem that we try to do two thinks in the same ... . Is it expected that the commands not executed in the order they are pushed to the context or is it a BUG |
43 | JDO @Index in JPA?, which I know that it's not available in JPA, but ObjectDB works with JDO as well. Question1: will adding JDO @Index in a JPA entity have any effect or I have to switch that entity to JDO? Question2: switching entities from JPA to JDO can happen when there is already data in the database? Or do I |
43 | Can't modify @EmbeddedId in ObjectDB Explorer only on its parent. Problem: id's content can't be modified through its parent neither. Scenario: open db in ... Chirac ObjectDB doesn't support modifying object IDs, not just in the Explorer, but by ... , where everything can be modified. zmirc Mircea Chirac Object Ids are usually immutable in object oriented databases |
43 | How to apply constraints in collection attributes of entity.How to apply constraints like unique, not null ...etc in collection attribute of a entity. Example ... = PhoneNumbers; } } in above example i wants to implement unique and notnull constraints ... in lifecycle events. support Support no my question was If i have PhoneNumbers["1234","567","45689 |
43 | Is named-query supported in orm.xmlI prefer to keep custom JPQL named queries in an external file, e.g. orm.xml, rather than in ... against the JPA 2 ORM schema, probably because of the location of the named-query element in ... queries should be defined in the XML before any type (entity, embeddable, etc.) definition. Named queries |
43 | Entity Type is not found (error 301) in Query, EclipseLink For ObjectDB there is one query in following method, where the full qualified class ... .checkConstraints(User.java:11 This behaviour is very strange, because in the same method - other workflow ... This could happen if the entity class is not in the database yet (no instances of that class |
43 | Persist not working when ObjectDB and another db is used in the same application (through spring) with different tx managersHi, Object are not being persisted when ObjectDB and another db is used in the same application ... appreciate as we are currently evaluating ObjectDB to use in our new enterprise application ... : @Transactional(value ="myTxManager", readOnly = false) public void addObject() { ... } In addition |
43 | Retrieve data of all entity classes in a single queryI have in an objectdb file 10 Entity Classes with some data in each (Athlete, Trainer, Stadium etc) This is the code I use to retrieve all Managed Types and data for the Athlete class Metamodel ... fields in a generic way using Java reflection. support Support Thanks for your answers So in case I |
43 | Bug with unique constraint exception not resulting in transaction roll backI'm using ObjectDB 2.5.6_02 and running into a bug with a JDO @Unique constraint. I'm using JPA in ... over more than one transaction. In a managed environment, in which transactions are started and committed by the application ... Removing @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) on my method does result in |
8 | I can't get cascading delete to work in JDO cascading delete has never been implemented in ObjectDB (see also "Deleting Dependent Objects" on this old documentation page). Build 2.7.5_04 implements cascading delete in JDO. Your NetBeans project was converted to a minimal test case in the required format (please use this format |
