问题描述
I have the following models.
BaseClass1
and BaseClass2
are abstract models used by models.
In this case, the model AdBreak
is used by a viewset and a serializer.
When I run python manage.py makemigrations
, the changes on AdBreak
model is detected. The model AdBreakStatus
is not getting created.
Since, AdBreakStatus
is linked to AdBreak
, I am expecting a migration for AdBreakStatus
also. Is my understanding wrong?
Edit
In the initial state, there was only AdBreak and BaseClass1 model. The new state, AdBreakStatus and BaseClass2 models were added. Some of the fields from AdBreak were moved to AdBreakStatus.
Thanks in advance for the help.
class BaseClass1(models.Model):
class Meta:
abstract=True
timestamp = models.DateTimeField(auto_now_add=True)
class BaseClass2(models.Model):
class Meta:
abstract=True
other_field = models.IntegerField()
class AdBreak(BaseClass1):
class Meta:
db_table = "ad_break"
ad_break_id = models.AutoField(primary_key=True)
... # Other fields
class AdBreakStatus(BaseClass2):
class Meta:
db_table = "ad_break_status"
ad_break = models.ForeignKey(AdBreak)
... # Other Fields
I solved it in multiple ways.
Solution 1
There is a serializer AdBreakSerializer
which serializes the model AdBreak
.
Import AdBreakStatus
model into the AdBreakSerializer
file.
Now AdBreakStatus
model is detected and migrated.
Problem in this approach is that, the import is not used, and hence will not follow the standards.
Solution 2
Write the AdBreakStatus
model class inside the same file of AdBreak
. This will also solve the problem.
Finding / Understanding
The makemigrations
script looks for models which are connected from urls.py
. The script navigates from urls.py
to all the viewset, then the corresponding serializers and models.
All the models which needs to be migrated should come in the path of this traversal. OR Only those models which are traversed in this manner will be migrated.
这篇关于Django 迁移未检测到所有更改的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!