Migrating from 1.3.6 to 1.4.0

Note

You should update directly to 1.4.1 instead of to this. Follow the steps below, but use rev v1.4.1 instead of 1.4.0.

Changes

  • A few new cache fields in the core database models to speed up database queries.
  • New examiner UI.

See also

http://devilry.readthedocs.org/en/latest/releasenotes-1.4.0.html

Backup database and files

BACKUP. YOUR. DATABASE. AND. FILES.

Update devilry

1 — Update as usual, but stop after step 3

Update REVISION to v1.4.0 using the instructions in the update guide, but stop after step 3 (do not restart supervisord).

2 — Migrate the database

Run the database migrations with:

$ bin/django.py migrate

Note

This may take some time. We migrate some data for existing groups and deliveries, so the migrations will query for all of your groups and deliveries, and update most of them.

Warning

If the migration fails with the following error message:

django.db.utils.DatabaseError: relation "celery_taskmeta" already exists

Check if:

$ bin/django.py migrate --list

shows that no migrations for djcelery has an (X) in front of it. If that is the case, run:

$ bin/django.py migrate djcelery 0001 --fake
$ bin/django.py migrate djcelery 0002 --fake
$ bin/django.py migrate djcelery 0003 --fake
$ bin/django.py migrate djcelery 0004 --fake

Then re-run:

$ bin/django.py migrate

3 — Continue the regular update guide

Continue with the last step of the update guide (restart supervisord).