On Thursday, November 8, 2018 at 3:52:01 PM UTC+1, [email protected] wrote: > > - If null=False is specified, then add an explicit not null constraint at > the db level >
As far as I understand Oracle makes no difference between null and an empty string. So if we were to add a not-null constraint, you could also no longer insert an empty string; which seems counterintuitive. Note that blank=True/False should be used there as validation on whether or not you want to allow empty values. This would prevent insertion of blank strings and nulls into required > columns, regardless of the client accessing the DB > Insertion of blank string and null is prevent if you set blank=False and run model validation, isn't it? I have to say my Oracle knowledge is somewhat limited, so please be patient and explain a bit more if I missunderstand you completly (code examples where you think the behavior is wrong would also help). Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/cd760491-764a-41eb-b9d4-5ab8c9b6fa6d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
