#11083: BackwardsIncompatibleChanges page does not mention OneToOneField change ---------------------------+------------------------------------------------ Reporter: adurdin | Owner: nobody Status: new | Milestone: Component: Uncategorized | Version: Keywords: wiki | Stage: Unreviewed Has_patch: 0 | ---------------------------+------------------------------------------------ After queryset-refactor, OneToOneFields are no longer automatically the primary key of a model. To make older code work post-queryset-refactor, the keyword argument `primary_key=True` must be added to the field instantiation.
I would have updated the wiki page, but do not appear to have permissions to edit it. -- Ticket URL: <http://code.djangoproject.com/ticket/11083> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
