How are schema changes handled?
A consistent problem no matter what persistence technology one uses is handling changes in the database schema (or structure) and content as an application evolves. Sidekar includes explicit support for schema changes, reducing the developer’s workload to simply specifying what to change. Sidekar takes care of figuring out when to apply changes and what order to apply them in. Sidekar ensures that it is impossible to open an existing database with an incompatibly configured schema. Sidekar performs schema changes in a single transaction, so that if any update fails, the entire change is rolled back. Let’s talk terminology. Suppose your application changes somehow between version X and version Y. You may have added a new field, renamed some class, or simply moved data around without changing the structure. A database update is any change to a database that needs to be applied when upgrading from version X to version Y. In Sidekar, database updates are represented by Java objects you sup
