Home/ Questions/Q 6829885
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T22:33:10+00:00

When defining fields in a django model, there are two ways to say that

  • 0

When defining fields in a django model, there are two ways to say that the field is allowed to be empty. null means it can be empty in the database, and blank says the field can be empty in a form. Why are these distinct? Every time I set one but not the other something goes wrong. Allowing them to be different seems to be to just inviting problems of the form allowing you to create objects the database won’t accept.

In other words, when would you ever use null=True,blank=False or null=False,blank=True in a django model?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    null=False, blank=True is common for CharFields, where a blank answer is stored in the db as a blank string rather than a null. The other way around doesn’t make much sense to use.

    For non-string fields, a non-answer is stored as a null, and so you need both.

    • 0