#9422: Incorrect handling of foreign keys by serializers ------------------------------------+--------------------------------------- Reporter: etianen | Owner: mtredinnick Status: assigned | Milestone: Component: Serialization | Version: 1.0 Resolution: | Keywords: Stage: Unreviewed | Has_patch: 1 Needs_docs: 0 | Needs_tests: 0 Needs_better_patch: 0 | ------------------------------------+--------------------------------------- Changes (by mtredinnick):
* owner: nobody => mtredinnick * needs_better_patch: => 0 * status: new => assigned * needs_tests: => 0 * needs_docs: => 0 Comment: You forgot to include the patch to the test cases that fails beforehand and works afterwards. :-) Also, I think this is more symptomatic of a larger problem that was sort of hacked around in r8957. Trying to fix that properly has shown it extends further than just that (particularly once you start chaining multiple foreign key references together, not just one level deep). Definitely a bug here, but I'm not convinced that this is quite the right fix for it. -- Ticket URL: <http://code.djangoproject.com/ticket/9422#comment:1> Django <http://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 django-updates@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---