#23268: Fixtures: Natural Key support for Generic Foreign Keys
-------------------------------------+-------------------------------------
Reporter: eskhool | Owner: nobody
Type: Bug | Status: new
Component: Core | Version: 1.6
(Serialization) | Keywords: natural generic
Severity: Normal | fixtures
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Currently, the natural key support is incomplete when it comes to generic
foreign keys (I say bug, you may think feature). One cannot remove PKs
from any object that has a generic foreign key reference limiting the
whole idea of having natural keys to direct foreign keys only. Since
generic foreign keys can inherently have an entry with any model, PKs have
to be dumped for all models necessitating the maintenance of updated PKs
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.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.4ca9c9ee2002fadfa9980f294cb23470%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
