#25247: makemigrations unable to generate necessary migration for making a
superclass abstract
-------------------------------------+-------------------------------------
Reporter: rapilabs | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: abstract | Triage Stage: Accepted
makemigrations |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_docs: => 0
* needs_better_patch: => 0
* type: Uncategorized => Cleanup/optimization
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
I guess it's probably not feasible to allow `makemigrations` to generate a
correct migration in cases like this (e.g. auto-generating data migration
seems risky), but we could at least throw a more helpful error message or
add some documentation about how to handle this case to `docs/howto
/writing-migrations.txt`.
--
Ticket URL: <https://code.djangoproject.com/ticket/25247#comment:1>
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.7b519d7bd996a7d258637d83a9b869b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
