#25492: makemigrations can generate invalid migrations when removing null=True
from
a field
-----------------------------+--------------------------------------
Reporter: tarkatronic | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by tarkatronic):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Actually, it looks like this is related to #24630 and #25453. Possibly a
duplicate of them. Just a slightly different view/approach on it. My bad,
I should have searched better before posting.
Regardless, given that this has come up multiple times, should it be made
more difficult to create these invalid migrations, rather than simply
documenting the fact that you can easily create them?
--
Ticket URL: <https://code.djangoproject.com/ticket/25492#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/069.236f6da1ddf632ce767906717c0b5396%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
