About evolution

manual

Database Schema Evolution

Explains how ObjectDB handles automatically schema changes.... the following topics: Automatic Schema Evolution Convertible Types Renaming (Package, Class and Field) Automatic Schema Evolution ObjectDB implements an automatic schema evolution mechanism ...

 
manual

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 ...

 
forum_thread

Automatic schema evolution causes ArrayOutOfBoundsException

Hi, I did 2 modification to our schema. Our schema looks like this: class Entity     - List<String> permissions class ServiceProvider extends Entity     - String name class Airline extends Entity     - String name     - String iata ... name field. According the ObjectDB schema evolution rules , the first change is not supported (since String and ...

 
forum_thread

Schema evolution & renamed/moved enum

Hello, I have an entity with an attribute of type enum say com.pkg1.MyEnum. I created a few instances of the class with this attribute of type com.pkg1.MyEnum. Now, I moved that enum to a different package and renamed it say com.pkg2.MyNewEnum. When I open my database again, the attribute is null. I don't seem to be able to use the <schema> tag in the config file because my enum is not an entity. What is a the proper way of handling the migration? Thanks, Farid  ... It seems that in this case automatic schema evolution is currently not supported. If you have to update a field ...

 
forum_thread

Understanding limitations of schema evolution

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... Hi, I am trying to understand the limitations of schema evolution and have read the material on ...

 
forum_thread

PersistenceException: Failed to locate field

Hi, have recently been running into this issue when changing the schema: com.objectdb.o._PersistenceException: Failed to locate field in this case, adding a primitive String field to an Entity. pretty sure that in the past schema evolution would not have triggered errors, is this case, a simple new field, shouldn't the policy be to add a null in that field, or other default for that primitive. ... to an Entity. pretty sure that in the past schema evolution would not have triggered errors, is this case, a simple new field, ... 16:33 The schema evolution should work in this case, nothing was changed. An exception ...

 
release

2.2.3

... 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 ...

 
release

2.7.3

... on dates in queries. Fixed a bug in schema evolution of indexes. Fixed a new false alarm of the Doctor, ... ( issue #296 ). Fixed a bug in schema evolution of non entity class to entity class in multi level hierarchy.  ...

 
release

2.7.3_01

... on dates in queries. Fixed a bug in schema evolution of indexes. Fixed a new false alarm of the Doctor, ... ( issue #296 ). Fixed a bug in schema evolution of non entity class to entity class in multi level hierarchy.  ...

 
release

2.2.4

... 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 ...