Hi Markus,
thanks for your answer and explanations!
I am now using a management hook to call the `loaddata` command manually
via the post_migrate signal:
% cat project/appname/management/__init__.py
# Handle initial data in Django 1.7+.
from django.db.models import signals
from
Hi,
first of all, both, update_all_contenttypes and create_permissions, expect
their respective app to be migrated completely in order to work as of
1.7.4
(https://github.com/django/django/commit/478546fcef38d95866a92bc44d10e15b26c7254c).
The "serialize model manager in migrations" issue, whic
Hello,
I was having the same issue as Torsten: it does not appear to be possible
to load initial data related to contenttypes or auth during migrations.
As for the problem with contenttypes reported by Torsten, a workaround
appears to be calling `update_all_contenttypes` manually from your
mig
Hallöchen!
Markus Holtermann writes:
> Are you talking about Django 1.7 migrations or South? In the
> former case you need to make sure that your datamigration depends
> on the contenttypes application.
I'm talking about Django 1.7 migrations. Unfortunately,
contenttypes is already migrated bef
Hey Torsten,
Are you talking about Django 1.7 migrations or South? In the former case
you need to make sure that your datamigration depends on the
contenttypes application.
If you use South: yes, calling update_all_contenttypes seems to be a
valid solution.
Best,
Markus
On Tue, Oct 21, 2014 a
Hallöchen!
I want to implement an initial data migration (basically, the same
thing initial_data.json used to do). The problem is that my initial
data must be connected with ContentType instances. However,
update_all_contenttypes() hasn't been called at this stage, so my
migration fails.
As far
6 matches
Mail list logo
