Re: null=True and blank=False within model fields

The obvious use case there is something that can't be initialized with a reasonable default value. Null is valid because you just plain need it, but blank is false because you never want it to be null ever again except if the back end explicitly demands it. On Thu, Aug 4, 2016 at 1:35 AM, James

Re: null=True and blank=False within model fields

On Aug 3, 2016 5:18 PM, "Kevin Brown" wrote: > > Within Django REST framework a discussion sparked about how the combination of null=True and blank=False should be handled with validation. What side is right in the discussion isn't the question here. > > Are there cases

null=True and blank=False within model fields

Within Django REST framework a discussion sparked about how the combination of null=True and blank=False should be handled with validation. What side is right in the discussion isn't the question here. Are there cases where it