As asked by auvipy, this is a thread to discuss the implementation for this ticket. <https://code.djangoproject.com/ticket/23268>
<https://code.djangoproject.com/ticket/23268>The idea in the proposed implementation <https://github.com/django/django/pull/7745/files> was: When a natural key is available for a GenericForeignKey, this one is used with the field name "content_object" rather than "object_id". As Tim Graham pointed out, that makes the *core* library (which contains fixtures serializers) aware of the generic foreign keys which are in the *contrib* library. In the github PR, i proposed an approach where we declare dependencies between fields (eg object_id depends on content_type) and use these deps to serialize/deserialize in the good order and benefit from natural keys if they exist. What do you think? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/fb174017-4fcc-4537-b0bf-0046b14fbd00%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
