Dumpdata complains celery_taskmeta doesn't exist about django-celery HOT 11 CLOSED

Humm,

I am having the same issue. Did you find a work-around in the end?

I do have these tables: crontabschedule, djcelery_intervalschedule, djcelery_periodictask, djcelery_periodictasks, djcelery_taskstate, djcelery_workerstate

But no djcelery_taskmeta or djcelery_tasksetmeta tables.

from django-celery.

Same issue here. If I exclude djcelery it works fine.

Note: If you're using Django 1.3 you can just pass --exclude djcelery to dumpdata and it'll work.

from django-celery.

am having the same problem, is there a root fix to this problem since i have some data populated in the djcelery app and i would like to dump it as well?

from django-celery.

Same issue here, couldn't find it quicky so here a dirty workaround in the meanwhile:

$ ./manage.py dumpdata djcelery.crontabschedule --indent=2 > fixtures/djcelery.json
$ ./manage.py dumpdata djcelery.periodictask --indent=2 >> fixtures/djcelery.json

after that you'd have to replace [] with , in the json file

from django-celery.

Why the model is not synchronized TaskMeta when not in use the DB backend storage. However, when creating fixtures, it fails because it can not find this table. (Same issue :P)

I think this model should always synchronized, so avoid affecting other aspects.

from django-celery.

Workaround: Comment on these lines in djcelery / models.py at the end of the file.
I think these lines generate more problems than solutions.

if (django.VERSION[0], django.VERSION[1]) >= (1, 1):
    # Keep models away from syncdb/reset if Django database
    # backend is not being used.
    if not getattr(celery.backend, "create_django_tables", False):
        TaskMeta._meta.managed = False
        TaskSetMeta._meta.managed = False

from django-celery.

I'm having this issue too.

Luckily my backup scripts can exclude arbitrary models. But still.

from django-celery.

Just a +1 on this issue. Thank you for the workaround suggestions in the meantime.

from django-celery.

+1 Having this issue on celery==2.2.x & django-celery==2.2.x. @ShawnMilo's tip of using --exclude djcelery on the dumpdata command worked.

from django-celery.

+1 Having same issue on celery==2.5.1 and django-celery==2.5.1. --exclude djcelery works wonders.

from django-celery.

django-celery used to include the database models conditionally, so the result backend models were only included
if the database result backend was selected. This was later proved to be a bad idea so the models are always created now.

from django-celery.