Re: Is some problem in field options 'null'?

The document says to avoid null=True for character fields, because they both "mean the same thing": there is nothing in there. They are however different and this is why Django returns None: - Empty character fields are considered a value - NULL character fields are not This is important in

Is some problem in field options 'null'?

I read the document about field options 'null'. It is said that. If True, Django will store empty values as NULL in the database. Default is > False. > > Avoid using null >