Home » Support » Forum » Understanding limitations of schema evolution

Understanding limitations of schema evolution

#1
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 where one re-factors a class by moving one if it's Fields to a different class. Is this case managable? Thanks
#2

If a persistent field is moved to a super class or a sub class (i.e. changes hierarchy but still remains relevant to objects that contains values of that field), ObjectDB handles this situation automatically. However, if the field is moved between different classes with different objects, ObjectDB cannot map automatically the old objects that had the field values to new objects, and you will have to write code for making this schema change.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#3
Thanks for your reply. Could you please elaborate more on the nature and complexity of the code that one has to write in the second case (namely moving a field between different classes of defferent objects)? Going over the schema update page http://www.objectdb.com/java/jpa/setting/schema it is not clear how to handle this case.
#4

Obviously it depends on the specific required changes.

It is like asking "Could you please elaborate more on the nature and complexity of the code that one has to write in order to develop an application?"

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)

Post Reply

To post a reply and/or subscribe to update notifications - please login