On Wed, Jul 16, 2008 at 2:49 AM, Eric Abrahamsen <[EMAIL PROTECTED]> wrote:
> I've got an issue with multiple one-to-one relationships, which > probably arises from poor design decisions on my part. Given a model > like the following: > > class Translator(models.Model): > user = models.OneToOneField(User, unique=True, blank=True, > null=True, help_text="If this translator is a site contributor.") > author = models.OneToOneField(Author, unique=True, blank=True, > null=True, help_text="If this translator has an Author entry in the > database.") > > Saving any instance of this model sets both the user and author fields > to None – clearly not what I want. I suppose it has to do with the > OneToOneFields being blankable/nullable, but my (poor) design > decisions require these to be optional relationships. I came up with > this whole mess before model inheritance was an option; it's probably > time for a re-think. > > My question, should this be considered a bug? If not, can we update > the docs somewhere? There's currently no caveat to this effect, and > believe me, it was an unpleasant surprise. > Saving how, exactly? If admin, newforms-admin or old admin? If old admin, have you tried it on newforms-admin -- bugs in old admin are unlikely to get any attention at this point. If saving in your own code, more details of that code would help. 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 -~----------~----~----~----~------~----~------~--~---
