Home » Search

About evolution

31-36 of 36Refresh
Issue
2

Schema-Update: Rename superclass and remove one subclass

demonstrates a bug in schema evolution that includes renaming a super class and removing
Issue
2

NullPointerException in __odbGetNumMember

that it has to do with enhancement? It may also be related to schema evolution. Can you post
Forum
2

Support of modifying an ObjectDB Entity class (Schema Change)

for more information! No need for this effort. See this manual page. Schema evolution is automatic
Forum
2

Removing an entity throws exception

when enhancement is not in use) - after schema evolution. Therefore, starting with a new database
Issue
2

ObjectDB 2.7.2_x Doctor Yields "Index Requires Rebuild" Always

notes state "Fixed a bug in schema evolution of indexes.") ... I can confirm that ObjectDB 2.7.2_05
Result
0

[ODB1] Chapter 3 - Persistent Classes

Point instances are deleted with it. 3.5  Automatic Schema Evolution Most of the changes to persistent ... . ObjectDB implements an automatic schema evolution mechanism, which enables transparent use of old