Backward compatibility support with my object database?

I am writing an application using an object database ( db4o ) and in a flexible manner will start with a small minimal implementation and iteratively add functions from there, releasing new versions of the software when I go.

The main question I have is how to maintain backward compatibility for the database, as new implementations of model classes are being developed so that users can use the saved data of the first edition with the software of the 10th release.

Are there some standard ways to do this, especially using an object database?

+3
source share
1 answer

db4o supports the automatic evolution of the object schema for major changes to the class model (deleting / adding a field name). More complex modifications of the class model, such as changing the field name, changing the field type, moving the hierarchy, are not automated out of the box, but can be automated by writing a small utility update program.

See the documentation here and here .

+4
source

Source: https://habr.com/ru/post/1725104/


All Articles