About change
2.0.5
... Fixed a Server/Explorer class loading bug (after schema change). Fixed a bug in the ObjectDB Doctor Tool. ...
2.0.4
... Fixed a Server/Explorer class loading bug (after schema change). Fixed a bug in the ObjectDB Doctor Tool. ...
2.0.3
... Fixed a Server/Explorer class loading bug (after schema change). Fixed a bug in the ObjectDB Doctor Tool. ...
2.0.2
... Fixed a Server/Explorer class loading bug (after schema change). Fixed a bug in the ObjectDB Doctor Tool. ...
2.0.1
... Fixed a Server/Explorer class loading bug (after schema change). Fixed a bug in the ObjectDB Doctor Tool. ...
2.0.0
... Fixed a Server/Explorer class loading bug (after schema change). Fixed a bug in the ObjectDB Doctor Tool. ...
Schema Update
Explains how to handle JPA/JDO database schema evolution in ObjectDB. The <schema> configuration element supports renaming packages, classes and fields in ObjectDB databases as a complementary operation to renaming or moving these elements in the IDE during source code refactoring. Only these schema changes are ...
Updating JPA Entity Objects
Explains how to use JPA to delete (remove) entity objects from the database.... Transparent Update Automatic Change Tracking UPDATE Queries Transparent ... are not managed yet are also persisted. Automatic Change Tracking As shown above, an update is achieved by modifying a ...
Primary key generation problem after changing entity package
Hi, I changed package name for some of my entities in database. I added info in <schema><package... /></schema> of my configuration file - and the changes have been succesfully made in database. Unfortunately, sequences have been probably lost for changed entity classes. After schema change I keep getting errors : Attempt to reuse an existing primary key value... My primary keys are annotated as shown below : ... probably lost for changed entity classes. After schema change I keep getting errors : Attempt to reuse an existing primary key ... made. Changing sequenceName don't help. Only when I change SequenceGenerator name new instances are persisted with correct ...
commit()
Commit the current resource transaction, writing any unflushed changes to the database.(Method of javax.persistence.EntityTransaction)
