About change

the change, close ObjectDB's connection, and run the project again. Important: do all that until a new ... to reproduce a similar situation by changing the order of the values in the enum, i.e. by first using enum ... ). Please try to remember if you might have changed your enum, and also try your test with a clean odb

that it takes several restarts of the the server to complete the change. The issue is that there may be changes in many places. Each change appears to be applied as the class is first encountered ... and everything is fine until the next set of changes are encountered. This cycle may repeat several times

... This is automatic - just change your class (see Database Schema Evolution in the manual ... indexes are automatically built and activated in the background. so, your strategy is changing ... definition and rebuild the database using the Object Doctor I'm not sure after index changing

...), REVISION:=1, isPersisted:=true ... As you can see, I changed from "ProfileName 99" to "ProfileName ... the changes, the Id of the new Value entity was still nulll (See #1). How can this be ? It is true ... the changes, the Id of the new Value entity was still nulll This is normal. You can choose an ID

) have i misconfigured something? edit: i should note that changing temp= in /etc/objectdb/objectdb ... using the same directory for their temporary files. Changing the temporary directory path ... ). A better solution could be changing the permissions of the temporary directory (/tmp/ObjectDB) in a way

we can confirm that a change in the behavior of merge in build 2.4.6_17 affects your test case. The change was applied following a support ticket that demonstrated a strange merge behavior. Following ... the cascading merge, and then also stored as a third instance during commit as part of the change in

are built in the background starting version 2.6.6, and apparently the last related code change was in ... schema change or any other hint? Small update: We think a workarround (but not usefull) is to create ... ");
}
} If we open a database without any Metamodel changes we don't get the tread. I think

to the replicated database by changing connection url, i.e. by connecting to the replicated database using ... to the replicated database url, switching the master and slave roles (in order to replicate changes in ... when ready. For support: do you have an idea how change the urls when in a Java EE JTA environment

is that this MAY happen when schema changes, even though nothing is changed in that Object's class. Any ideas ... while schema changes, but not all the times. The interesting part is that most of the times, schema changes ... a stable state. I will try to come with more details when I'll deal with schema changes again. Thank you. zmirc