v0.3.0

• The primary key for tasks is now a uuid4.
• All task lookup functions now prefer the uuid , but most will lookup with a name if needed.

Rationale: Django Q was using a LUID (locally unique id) combined with a standard Django pk to identify saved tasks . Even though problems associated with this design were minor and probably non-existent on a small scale, the ambitions of the project warrant an UUID (universally unique id). In that light it was best to do that sooner rather than later and deal with the inconvenience now.

Upgrading: if you upgrade from v0.2 or earlier, don't forget to migrate your database with python manage.py migrate django_q

Note: A side effect of upgrading will be that schedule links to the last run before the upgrade break in the admin. Those tasks will still be accessible in the model admin though. Everything will be fine after the next scheduled run.

UUIDField: Django 1.8 offers a dedicated UUIDField for models. Unfortunately this is not compatible with Django 1.7 and only offers improvements with PostgreSQL backends. All other backends get a CharField, so that was selected for now. This will be probably be upgraded once Django 1.7 extended support is deprecated at the end of the year.