Wednesday, February 27, 2013

blank and null with Oracle

Some odd behavior with Oracle involving blank and null.

blank is True on this field:
my_auto = models.AutoField(blank=False, null=False, primary_key=True)

null is True on this field:
uncles = models.ManyToManyField(Uncle, blank=False, null=False) 

null is True on this field:
photo = models.ImageField(upload_to="uploads/") 

And, then, as documented null=True on CharFields.

The most disturbing thing is that blank/null on the first two examples are the opposite of what is explicitly declared.

Should I post this on django-developers. Is this behavior documented? Are this problems/quirks known?


You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment