There is a great answer by someone who has done the leg work for figuring
out what is required.
http://stackoverflow.com/questions/11159377/is-it-possible-to-use-a
-natural-key-for-a-genericforeignkey-in-django
Creating a ticket to document it here and see what the interest is for the
same.
--
Ticket URL: <https://code.djangoproject.com/ticket/23268>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* cc: dev@… (added)
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/23268#comment:1>
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/23268#comment:2>
* owner: nobody => Guillaume Thomas
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/23268#comment:3>
* has_patch: 0 => 1
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/23268#comment:4>
* stage: Ready for checkin => Accepted
Comment:
"Ready for checkin" is set by a patch reviewer, not the patch author.
--
Ticket URL: <https://code.djangoproject.com/ticket/23268#comment:5>
* needs_better_patch: 0 => 1
Comment:
As I mentioned on the pull request, it doesn't seem like a good separation
of concerns to modify the "core" serializers for a "contrib" field.
Unfortunately, I haven't studied the problem enough to suggest an
alternate solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/23268#comment:6>
* cc: Ian Foote (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/23268#comment:7>