null = True

意味着没有数据库对要填充的字段的约束，因此您可以有一个具有此选项的填充的空值对象。

blank = True

意味着在django表单中没有验证约束。所以当你为这个模型填写一个modelForm时，你可以不填这个选项。

简单来说就是答案:-

通过null = True，我们告诉数据库模型的这个字段可以为null，通过blank = True，我们告诉Django模型的这个字段可以为null

默认值为“null”和“blank”为“False”。

Null:与数据库相关。定义给定的数据库列是否接受空值。

Blank:这是验证相关的。它将在表单验证期间调用form.is_valid()时使用。

也就是说，有一个null=True和blank=False的字段是完全没问题的。意思是在数据库级别上，该字段可以为NULL，但在应用程序级别上，它是必需的字段。

现在，大多数开发人员都犯了错误:为基于字符串的字段(如CharField和TextField)定义null=True。避免这样做。否则，你最终会有两个可能的“无数据”值，即:None和一个空字符串。对于“无数据”有两个可能的值是多余的。Django的约定是使用空字符串，而不是NULL。

这里，是null=True和blank=True的主要区别:

null和blank的默认值都是False。这两个值都在字段级工作，即，我们是否想要保持字段为空或空白。

null=True将字段的值设置为null，即没有数据。它基本上是为数据库列的值。

date = models.DateTimeField(null=True)

blank=True确定表单中是否需要该字段。这包括管理表单和您自己的自定义表单。

title = models.CharField(blank=True) // title可以为空。 在数据库中(“”)将被存储。 null=True blank=True这意味着该字段在所有情况下都是可选的。

epic = models.ForeignKey(null=True, blank=True)
// The exception is CharFields() and TextFields(), which in Django are never saved as NULL. Blank values a

当你设置null=true时，如果字段没有填充，它将在你的数据库中设置为空。如果 你设置blank=true，它不会为该字段设置任何值。

理解Django模型字段定义中的选项(至少)有两个目的是至关重要的:定义数据库表，定义模型表单的默认格式和验证。(我说“默认”是因为可以通过提供自定义表单来覆盖这些值。)一些选项会影响数据库，一些选项会影响表单，还有一些会同时影响两者。

说到null和blank，其他答案已经说明，前者影响数据库表定义，后者影响模型验证。我认为，通过查看所有四种可能配置的用例，可以更清楚地区分它们:

null=False, blank=False: This is the default configuration and means that the value is required in all circumstances. null=True, blank=True: This means that the field is optional in all circumstances. As noted below, though, this is not the recommended way to make string-based fields optional. null=False, blank=True: This means that the form doesn't require a value but the database does. There are a number of use cases for this: The most common use is for optional string-based fields. As noted in the documentation, the Django idiom is to use the empty string to indicate a missing value. If NULL was also allowed you would end up with two different ways to indicate a missing value. (If the field is also unique, though, you'll have to use null=True to prevent multiple empty strings from failing the uniqueness check.) Another common situation is that you want to calculate one field automatically based on the value of another (in your save() method, say). You don't want the user to provide the value in a form (hence blank=True), but you do want the database to enforce that a value is always provided (null=False). Another use is when you want to indicate that a ManyToManyField is optional. Because this field is implemented as a separate table rather than a database column, null is meaningless. The value of blank will still affect forms, though, controlling whether or not validation will succeed when there are no relations. null=True, blank=False: This means that the form requires a value but the database doesn't. This may be the most infrequently used configuration, but there are some use cases for it: It's perfectly reasonable to require your users to always include a value even if it's not actually required by your business logic. After all, forms are only one way of adding and editing data. You may have code that is generating data that doesn't need the same stringent validation you want to require of a human editor. Another use case that I've seen is when you have a ForeignKey for which you don't wish to allow cascade deletion. That is, in normal use the relation should always be there (blank=False), but if the thing it points to happens to be deleted, you don't want this object to be deleted too. In that case you can use null=True and on_delete=models.SET_NULL to implement a simple kind of soft deletion.