Re: #6189: IntegrityError: Field "may not be NULL" even though blank=True

2007-12-12 Thread Karen Tracey
On Dec 11, 2007 11:55 PM, Tyson Tate <[EMAIL PROTECTED]> wrote: > > I submitted bug #6189 [1], but I thought I should ping django-users to > see if anyone has encountered this before or knows of a workaround. > > In summary, despite adding "blank=True" to my fields, many of them > throw IntegrityE

#6189: IntegrityError: Field "may not be NULL" even though blank=True

2007-12-12 Thread Tyson Tate
I submitted bug #6189 [1], but I thought I should ping django-users to see if anyone has encountered this before or knows of a workaround. In summary, despite adding "blank=True" to my fields, many of them throw IntegrityErrors when I try to save them with blank values in the admin interfac