Internal Website Search

after a schema change. Automatic Schema Evolution ObjectDB implements an automatic schema evolution mechanism ... might also be located in a different place in the class hierarchy. That makes automatic schema evolution ... ) The automatic schema evolution mechanism, as described above, is based on matching fields by

schema evolution is currently not supported. If you have to update a field type into a non

Hi, I am trying to understand the limitations of schema evolution and have read the material on http://www.objectdb.com/java/jpa/entity/schema as well as the link therein regarding manual schema update when changing a field’s name Yet, i am confused regarding how to handle the case

the duplicate name field. According the ObjectDB schema evolution rules , the first change is not supported

Schema Evolution Question

enhancement is optional (recommended before deployment). Schema Evolution Fully automatic schema evolution

. pretty sure that in the past schema evolution would not have triggered errors, is this case, a simple ... David Moshal The schema evolution should work in this case, nothing was changed. An exception ... . So, back to this question: does schema evolution work where you're relying only on the enhancement setting in the config

), but this is probably only in this post and not in your application. The ObjectDB schema evolution support consists of: Automatic schema evolution - for adding and removing fields and for class

Hello, we try to change the class hierarchy of an Entity. You wrote www.objectdb.com/database/forum/899 that ObjectDB support automatic schema evolution for adding and removing fields and for class ... up and down in the class hierarchy as part of the automatic schema evolution . You can also move the name

certain that we use the correct configuration file, as we also define schema evolution inside ... configuration file, as we also define schema evolution inside of it and a few other things

already contains a mechanism for supporting live schema evolution without restarting the server ... to be more dynamic, and then schema evolution will be more natural and this issue will not exist. support Support

scema evolution mechanism of ObjectDB, when changing hierarchy. As a work ... EmbeddedSystems Please try build 2.6.9_07 that includes an attempt to repair the schema evolution issue

btc_es BTC EmbeddedSystems The ObjectDB schema evolution support consists of: Automatic schema evolution - for adding and removing fields and for class hierarchy change. Configuration schema changes

, the two referred Point instances are deleted with it. 3.5  Automatic Schema Evolution ... , have to be converted to the new schema. ObjectDB implements an automatic schema evolution mechanism

you for this report and for the test. It demonstrates well a bug in schema evolution that includes renaming

it seems that we cannot provide a quick implementation of this type of automatic schema evolution

;application log wrote any errors, so it looks to me that it is some failing schema evolution . When I tried

with ordinary objects. Fixed a schema evolution bug when adding a new super entity class .   support Support

a critical database corruption bug ( issue #187 ). Fixed a critical bug in schema evolution

Hi, I want to drop one column from my database table suppose i have 3 column (id, name, address) now i want to drop address. then what will be the query or procedure..   Bimal Bimal kumar dalei Just remove the field from the entity class. See Automatic Schema Evolution . Space in the database

evolution , if you changed your persistable classes recently. support Support For now I just add

evolution is automatic and transparent.   support Support Thanks a lot for the reply here and on StackOverflow! dahui58 John-Paul Anderson

Evolution in the manual).  alter table add index ... Add the index definition and rebuild the database

Hello, we have an entity class hierarchy and we want to insert a new entity in this hierarchy and our database must be automatically updated by schema evolution . Unfortunately it does not work, because the class hierarchy had already always existed and the "new" entity class needed

a missing value, maybe as a result of schema evolution or index definition changes Please provide relevant

Schema Evolution Schema Update As you can see most schema changes are either fully automatic or

of this exception is unclear but according to the stack trace it is related to failed schema evolution

images (used mainly to detected changes when enhancement is not in use) - after schema evolution

after a schema evolution ? Have you restarted the server as requested ? support Support

- it demonstrates a bug in ObjectDB schema evolution . Please check build 2.0.5_01 that should fix

had many previous schema evolution changes (you might have a longer history of schema changes in ... necessarily causes exceptions, but if you are sure about the number of schema evolutions then it reduces ... that check that schema evolution work, including when fields of all types are added, and every build

to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema evolution (regression of 2.2.0). Fixed a bug in queries on large objects . Fixed a bug in using persistent properties with incomplete enhancement.

that it has to do with enhancement? quasado Alexander Adam It may also be related to schema evolution . Can you post the database

Improved the error message on exception during commit, reported in issue #2882 . Improved automatic schema evolution of enum fields. Fixed A NullPointException when using EntityManagerFactory with different class loaders. Fixed a missing call to @PostUpdate when object change is detached by 

evolution of indexes.") ... I can confirm that ObjectDB 2.7.2_05 also works as expected. CBE CBE Thanks for the update. support Support

schema evolution of modified ancestor classes. Fixed a bug in handling indexes in a new ancestor

( issue #1959 ). Fixed a schema evolution bug in handling hierarchy change . Fixed setting JDO's

Fixed Explorer issue after schema evolution ( issue #2726 ).

worked well before, it could be the result of a recent schema evolution . Particularly if you changed

#2050 ). Fixed a bug in schema evolution of non entity class to entity class in multi level hierarchy. 

through inverse (mapped by) fields. Fixed some bugs in automatic schema evolution . Fixed a Server

replacing proxy objects with ordinary objects. Fixed a schema evolution bug when adding a new super entity class .

evaluation. Improved automatic schema evolution of enum fields. Improved exception throwing from

you for your report. The test demonstrates a bug in schema evolution that includes renaming a super class

evolution ( issue #2726 ). Fixed field renaming schema upgrade of previous schema versions ( issue #2713 ).