#21896: makemigrations warning "trying to add a non-nullable field" is raised
even
when the table is empty
-------------------------------------+-------------------------------------
Reporter: kunitoki | Owner:
Type: | Status: closed
Cleanup/optimization | Version:
Component: Migrations | 1.7-alpha-1
Severity: Normal | Resolution: invalid
Keywords: migrations | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ashish1206):
Replying to [comment:3 andrewgodwin]:
> We don't know what size the table might be in the future, so we have to
raise this during ``makemigrations``; you might make the migration on a
dev box with no entries and then run it on a production box with millions
of rows, so it has to stay. Marking INVALID.
I am using django 1.7 and getting the same warning for fields when I use
`makemigrations` on dev server.How to fix this?
--
Ticket URL: <https://code.djangoproject.com/ticket/21896#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.1478549287a5af5ffd9b7aba9ad82a77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
