Self-referencing model with natural key: dumpdata can't resolve dependencies

[Simon Meers]

I have a self-referencing model with a natural key, but dumpdata won't serialize it:

    Error: Can't resolve dependencies for app_label.ModelName in serialized app list

This is probably perfectly valid if use_natural_keys=True, but shouldn't I be able to serialize it without natural keys? I suspect dumpdata.sort_dependencies should take the flag setting into consideration before throwing natural-key-based dependencies into the mix?

[Simon Meers]

(the intention is to serialise the self-referencing model separately natural keys, but use the natural key functionality in references from other models)

[Simone]

patch and tests

[Simone]

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.

[anonymous]

the patch is ready for current trunk 1.4 alpha

[Simone]

I've update the patch, for the new release 17765, the content is not changed.

[Anssi Kääriäinen]

The updated patch seems to be missing the dumpdata.py part.

[Simone]

At revision 17766

[Simone]

Yes thanks, you're right.
in the previous upload the dumpdata.py part was missing
now I've update the patch for the new release 17766

[duilio]

what happened to this patch? I've just caught this bug and found out it was issued here

[Claude Paroz <claude@…>]

In [4b722b31e1778310ba0c1ed96fdacf99aa203dd2]:

Fixed #16317 -- Fixed dumpdata for self-referencing models and natural keys

Thanks aldaran for the patch.