About change

31-40 of 200Refresh
Issue
16

preUpdate-methods are called when there is no change

Dear Support Team, we ran into some difficulties with a database. When fetching a entity using the EntityManager and afterwards calling "iterator().next()" a transaction begin/commit will end up in updating the Entity even there was no change. RepositoryModelData repository = connection.find
Forum
16

Refresh data in application after database data has changed

with the same national number as a person I want to add. However when I change the value of the national number
Forum
16

Support of modifying an ObjectDB Entity class (Schema Change)

if ObjectDB can already handle changes to Entity classes. Please see my StackOverflow question
Issue
16

UPDATE query cannot set a new field after schema change

the changes to the DB via file->save. But when I execute a select on the DB I see that the field
Forum
16

UPDATE query to set a new field after schema change

the changes to the DB via file->save. But when I execute a select on the DB I see that the field
Manual
16

Database Schema Evolution

Modifications to entity classes that do not change their persistent field definitions (their schema ... after a schema change. Automatic Schema Evolution ObjectDB implements an automatic schema evolution mechanism that enables transparent use of old entity objects after schema change. When an entity object
Forum
16

Changes in detach behaviour?

Changes in detach behaviour?
Forum
16

Changing from client server to embedded mode

Changing from client server to embedded mode
Manual
15

Schema Update

refactoring. Only these schema changes are specified in the configuration file. As explained in chapter 2, other schema changes are handled by ObjectDB automatically. Note: Extreme caution ... that after such changes the application is run only with the configuration that matches these changes exactly
Manual
14

JPA Entity Fields

provider (such as Hibernate) or to change default field settings. For example: @Entity public class ... ; } The entity class declaration above demonstrates using field and relationship annotations to change ... (the Employee class in our example) is the owner. Only changes to the owner side affect the database