new migrations coming up when blank=True in booleanfield in django 2.1+
8 views
Skip to first unread message
anvesh Agarwal
unread,
Dec 5, 2019, 8:24:59 AM12/5/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Django users
As document says, https://docs.djangoproject.com/en/2.2/ref/models/fields/#booleanfield previously blank=True was implicit but in django 2.1+ , we have to add it externally. So i dont understand why new migrations are coming up for this? Does this mean that previously blank=True wasnt considered for the migrations?