A Python dump of a database is a snapshot that can be used for data migration à la Lino.
When you upgrade to a newer version of the application you are running, or when you change certain parameters in your
settings.py, then this might require changes in the database
structure. This is called database migration.
Before upgrading or applying configuration changes, create a Backup.
After upgrading or applying configuration changes, restore your database from that backup. The
restore.pyscript will automatically detect version changes and apply any necessary changes to your data.
For example, here is a upgrade with data migration:
$ go prod $ a $ python manage.py dump2py 20130827 $ pull.sh $ python manage.py run 20130827/restore.py
It is of course recommended to stop any other processes which might access your database during the whole procedure.
Double Dump Test (DDT)¶
A Double Dump Test is a method to test for possible problems e.g. after a Database Migration: we make a first dump of the database to a Python fixture a.py, then we load that picture to the database, then we make a second dump to a fixture b.py. And finally we launch diff a.py b.py to verify that both pictures are identical.
restore.py successfully terminated without any warnings
and error messages, then there are good chances that your database has
been successfully migrated.
But here is one more automated test that you may run when everything seems okay: a Double Dump Test (DDT).
This consists of the following steps:
make another dump of the freshly migrated database to a directory a.
restore this dump to the database
make a third dump b
Compare the files
b: if there’s no difference, then the double dump test succeeded!
In other words:
$ python manage.py dump2py a $ python manage.py run a/restore.py $ python manage.py dump2py a $ diff a b
If there’s no difference between the two dumps, then the test succeeded!