#30390: makemigrations requires default when adding non-nullable field even when
there are no rows.
-------------------------------------+-------------------------------------
Reporter: Neil du Toit | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Migrations | Version: 2.2
Severity: Normal | Resolution:
Keywords: makemigrations | Triage Stage:
default null | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jay Welborn):
I have recreated this behavior. I'm not sure if there is a reason behind
empty tables getting the same warning as populated tables.
If this is a desired change, I can write a patch that drops the warning
when adding a field to an empty database table.
--
Ticket URL: <https://code.djangoproject.com/ticket/30390#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/070.9dc8de29f47e09b8885b2e2b73878289%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
