When I run makeviewmigration, it generates a migration file called, e.g., 0034_auto_20231130_2243.py.
I understand that that is the Django default, but it is not easy to understand. It would be much easier to read if
your migrations had names like the built in migration tools: Minimally something like 0034_person_doctor.py,
where person and doctor were names of the models that you were creating or altering views for.
Even better would be if it could do ...create_person_alter_doctor.py depending on the view existing before then.
When I run
makeviewmigration
, it generates a migration file called, e.g.,0034_auto_20231130_2243.py
.I understand that that is the Django default, but it is not easy to understand. It would be much easier to read if your migrations had names like the built in migration tools: Minimally something like
0034_person_doctor.py
, whereperson
anddoctor
were names of the models that you were creating or altering views for.Even better would be if it could do
...create_person_alter_doctor.py
depending on the view existing before then.