Hello, On Jan 23, 2008 11:17 PM, Wyley <[EMAIL PROTECTED]> wrote: > > Michael, > > Thanks for your reply! > > > Many databases will allow a constraint with a foreign key to be deferrable > > and initially deferred so that you don't have to disable the relationship > > to load data. > > Can you say a bit more about this? I'm by no means an expert on > databases; I'm not quite sure what "deferable" means. >
I too have not quite understood this, and am now curious since I have been using both blank=True and null=True on ForeignKeys, but haven't had an error so far. To me, the original problem felt like the database wasn't in sync with the model (allowing NULL), but apparently that's not the case? Also, the docs[1] have a section describing field options in which it states that it applies to all fields. It comes right before the descriptions for ForeignKey and ManyToMany, but it is where it defined help_text, verbose_name and other fields that, in fact, do apply to ForeignKeys as well. So that kind of confuses me. Is it really the case that null=True is not allowed for ForeignKeys? [1] http://www.djangoproject.com/documentation/model-api/#field-options Thanks in advance, Eduardo. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
