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 IntegrityErrors when I try to save them with blank values in the > admin interface. > > [1] <http://code.djangoproject.com/ticket/6189> >
You need to specify null=True for these fields as well (and re-sync your database). The error you are seeing is coming from the database, which is currently set up to not allow NULL values for these fields. So even though admin is allowing blank values, the database does not accept the NULL that these turn into when admin tries to save the model instance. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
