#26488: migrate crashes when renaming a multi-table inheritance base model
-------------------------------------+-------------------------------------
Reporter: Christopher | Owner: nobody
Neugebauer |
Type: Bug | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Markus Holtermann):
When I try to run `makemigrations` after *step 0* with the code you
provided I get the following system check failure:
{{{
$ ./manage.py makemigrations
SystemCheckError: System check identified some issues:
ERRORS:
ticket26488.SubModel.basemodel_ptr: (fields.E007) Primary keys must not
have null=True.
HINT: Set null=False on the field, or remove primary_key=True
argument.
}}}
Further, neither steps 0-2 nor steps 1-2 work for me. It comes down to
`django.core.exceptions.FieldError: Auto-generated field 'basemodel_ptr'
in class 'SubModel' for parent_link to base class 'BaseModel' clashes with
declared field of the same name.` both times.
--
Ticket URL: <https://code.djangoproject.com/ticket/26488#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.8693590e361531b6e77f7c9d40b171fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
