#21896: makemigrations warning "trying to add a non-nullable field" is raised
even
when the table is empty
-------------------------------------+-------------------------------------
Reporter: kunitoki | Owner:
Type: | Status: new
Cleanup/optimization | Version:
Component: Migrations | 1.7-alpha-1
Severity: Normal | Resolution:
Keywords: migrations | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by anonymous):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I don't think we can silence the warning in that case since it may be
empty in dev, but then when you come to apply the migration in production
it might not work. Much safer to always warn to make sure you've
considered the possibility, as long as there's a way to ignore it if
you're sure it'll be fine.
--
Ticket URL: <https://code.djangoproject.com/ticket/21896#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.169d1300e6c97957adb5ee4ed95cabf2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
