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, which is part of 1.8,
will allow you to use custom methods on your model manager inside
`RunPython` (e.g `MyUser.objects.create_a_fancy_user_account()`) and isn't
related to the problem you are running into.
The sanest way to generate all ContentTypes and Permissions is to migrate
those two apps explicitly before migrating the remaining apps:
$ python manage.py migrate contenttypes
$ python manage.py migrate auth
$ python manage.py migrate
That way you can make sure the contenttypes app is completely migrated and
all contenttypes are created, the auth app is completely migrated and all
permission are created, and last but not least the remaining apps should
smoothly migrate forwards. There are thoughts about putting the migration
graph and the respective model states before/after all migrations into the
pre/post_migrate signals (#24100) as well as initial ideas emitting a
signal after each migration (no ticket yet afaik). The latter could be used
to tackle the above problem.
If you want to create a specific permission during a migration, do the
following in `RunPython`:
def forwards(apps, schema_editor):
Permission = apps.get_model('auth', 'Permission')
Permission.objects.create(...)
This is also the way to load initial data starting Django 1.7: using
`RunPython` or `RunSQL`.
The django-migration-fixture app seems to do some crazy stuff in the
management command that I'm not going to speculate about how long it's
going to work. That is completely undocumented and internal API. Apart from
that, the (de)serializers in django.core.serializers (specifically
.python.Deserializer) use the global apps for deserialization. Thus, a
fixture referring to a model that is later removed/renamed, or refers to a
field that doesn't exist later or must not be null, cannot be applied when
you run the migrations on an empty database.
/Markus
On Thursday, January 22, 2015 at 12:43:33 PM UTC+1, Daniel Hahler wrote:
>
> 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
> migration (from django.contrib.contenttypes.management).
>
> But then there's the problem with creating auth.groups.
>
> I've tried the following via `RunPython`:
>
> from django.contrib.auth.management import create_permissions
> create_permissions(apps.get_app_config('auth'), verbosity=0)
>
> This aborts because `app_config.models_module` is None:
>
> app_config.__dict__
> {'models_module': None, 'name': 'auth', 'models':
> OrderedDict([('group_permissions', <class 'Group_permissions'>), ...]),
> 'module': None, 'label': 'auth', 'verbose_name': 'Auth'}
>
> Is this related to https://code.djangoproject.com/ticket/23822
> ("Serialize model managers in migrations"), and would be possible in Django
> 1.8?
>
> I am trying to use https://github.com/alexhayes/django-migration-fixture,
> which is meant to provide a convenient wrapper around the initial_data
> fixtures (files). My PR with the changes mentioned above is viewable at:
> https://github.com/alexhayes/django-migration-fixture/pull/2/files.
>
> What is the suggested way to have initial data with Django 1.7, given that
> initial_data is not used for apps with migrations, and RunPython has the
> above shortcomings?
>
>
> Thanks,
> Daniel.
>
> Am Dienstag, 21. Oktober 2014 19:42:34 UTC+2 schrieb Torsten Bronger:
>>
>> 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 before my app. But this doesn't
>> help because update_all_contenttypes is a post_migrate signal.
>>
>> Tschö,
>> Torsten.
>>
>> --
>> Torsten Bronger Jabber ID: [email protected]
>> or http://bronger-jmp.appspot.com
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/d9c0ee9b-56a3-4b29-88e8-4e060b43fe38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
