On Sat, 2006-05-20 at 22:15 +0000, qhfgva wrote: > Thanks for your response, I'm not having luck with this. It seems like > the admin interface is requiring ForeignKey fields even when marked as > null=True.
OK, this problem bites everybody once. It's documented, but easy enough to miss in all the optionks available: setting null = True on a field simply says that any empty value should be stored in the database as a NULL. If you also want to say "it is optional to enter this in the admin interface", then you also need to set blank = True on the field (this won't require any change to your database: it only affects the interface). One example why this difference is useful is that may be that you have legacy data containing NULLs, for example, but all new data must have that field included, so blank = False makes sense in that case. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
