 1 | objects. Fixed a schema evolution bug when adding a new super entity class. |
1 | database corruption bug (issue #187). Fixed a critical bug in schema evolution of modified ancestor |
1 | when enhancement is not in use) - after schema evolution. Therefore, starting with a new database |
1 | . It demonstrates well a bug in schema evolution that includes renaming a super class and removing |
1 | demonstrates a bug in schema evolution that includes renaming a super class and removing |
1 | for more information! No need for this effort. See this manual page. Schema evolution is automatic |
1 | of automatic schema evolution at the moment, as critical parts of ObjectDB currently require references to include the exact type of the referred object. btc_es |
1 | 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.. Just remove the field from the entity class. See Automatic Schema Evolution. Space in the database file will be reclaimed lazily |
0 | 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 |