Firstly, you define the structure of your model classes; this is done in a
single class method. Let's say you have a class Person, you'd create the definition
method like this:
#firstName as: String;
#relatives as: (OrderedCollection
Once this is done for all your model classes, evaluating the single
...will create all the required tables within the database.
If at any time you change the structure of your classes, re-evaluating synchronizeAllClasses
will update the database with the new structure and automatically migrate
your existing data. This powerful feature ensures that use of ReStore does
not interfere with the rapid development and refactoring potential of Smalltalk.