> > Integer & NULLS > If the admin interface knows the field is required, why does it even attempt to insert a null value? It could return a validation error.

> > Integer & NULLS > If the admin interface knows the field is required, why does it even attempt to insert a null value? It could return a validation error. There's a lot going on here. In this case, you're telling the admin interface that nothing is required of the user. There could be a default value, for example. On the more technical side, blank and null are different concepts that are codified differently in different database systems. Here, in most systems, a integer attribute is nullable. If it were a string attribute, however, there are cases (Oracle) where null and the empty string are not distinguished, which is rather sensible for text. This separation supports all of these modes. I'll give you that `blank=True` lives in the wrong place in today's Django, but it was an early design and it stuck.