GenericForeignKey is pseudo-field. It doesn't have any own underlying db field representation, so there is no need to specify it as blank and nullable.
On Sat, Dec 13, 2008 at 22:45, mwebs <mic...@m-websolutions.de> wrote: > > Hello, > > I have a model that I want to have an optional generic relation to any > other kind of model. > > content_type = models.ForeignKey(ContentType, null=True, blank=True) > object_id = models.PositiveIntegerField(null=True, blank=True) > content_object = generic.GenericForeignKey(null=True, blank=True) > > > The problem is, that content_object does not accept "null=True, > blank=True". I always run into an "unexpected keyword argument" > exception. > > So any ideas how to make a generic FK optional?? > > Thanks > > > --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
