Hello Djangoers! What is the current status of OneToOneField? Many developers implement one-to-one relationship using ForeignKey's. So is OneToOneField deprecated? Is it because models are going to be inheritable and the model inheritance will be the substitute for OneToOneField? What about one-to-one relationship of the type "HAS-A" (example relationship: one person has one working place)?
I am using Django 0.95 post-magic-removal. As expected, when I create a new OneToOneField for some model, the field is presented as a drop-down select box in the contributed administration. But it is showed as a select box only when I create an instance of the model. After saving, the form field turns to a number (the id of the related object), and I can neither change the related object to another one, nor save the same instance once again, because the OneToOneField is required, but there is no form field for it. Does the latest SVN version still has the same problem and should I use OneToOneField for one-to-one relationships at all? Regards, Aidas Bendoraitis [aka Archatas] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
