简体繁体 English

Django 1.7迁移和刷新

[英]Django 1.7 migrations and flush

原文 2015-01-14 16:46:02 7 1 python/ django/ data-migration/ django-1.7

I have an app that uses initial models (auth.Group). 我有一个使用初始模型（auth.Group）的应用程序。 Prior to django 1.7, I used Group.objects.get_or_create in the 'models.py'. 在Django 1.7之前，我在'models.py'中使用了Group.objects.get_or_create 。 This was ugly but worked most of the time. 这很丑陋，但大部分时间都有效。 Changes to the app loading in django 1.7 broke this. django 1.7中对应用程序加载的更改打破了这一点。

Now I am trying to use data migrations to provide these groups. 现在，我正在尝试使用数据迁移来提供这些组。 This works the first time ./manage migrate is run. 这在第一次运行./manage migrate时./manage migrate 。 However, when I run ./manage.py flush the groups are missing. 但是，当我运行./manage.py flush这些组丢失了。 Running ./manage migrate again also does not create them. 再次运行./manage migrate也不会创建它们。 What I want is to have this data in place after ./manage flush . 我想要的是在./manage flush之后放置这些数据。

I can see why django acts like this, but is there some way to flag a migration as always needing to be rerun? 我可以看到django为何会这样，但是有某种方法可以将迁移标记为始终需要重新运行吗？ Is this some way to have these groups in place always in a clean way. 是否可以通过某种方式使这些组始终保持干净。