#16317: Self-referencing model with natural key: dumpdata can't resolve
dependencies
--------------------------------------+------------------------------------
Reporter: DrMeers | Owner: nobody
Type: Bug | Status: new
Component: Core (Serialization) | Version: 1.3
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by aldaran):
* has_patch: 0 => 1
Comment:
The patch is valid for ForeignKey, ManyToMany and OneToYne Fields
I've added a simple test case.
There is another problem related to this issue, in order to load "self
related objects" by natural keys using get_by_natural_key()
is obvious think that the related instances are already in the database.
The Serializator needs to serialize in a intelligent order (but if there
are cycle dependency it is impossible) or by serializing the objects with
no relations and after another serialization with them. I don't want open
another issue for that, actually I think it is possible by writing the
fixtures by hand.
--
Ticket URL: <https://code.djangoproject.com/ticket/16317#comment:3>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
