Comments on: Representing Relationships in Django Templates Without Writing Extra Code (RelatedManager and ManyRelatedManager)

By: Julio

Julio — Sat, 26 Feb 2011 22:47:43 +0000

save my day, thanks

By: Joshua Russo

Joshua Russo — Thu, 03 Sep 2009 12:30:16 +0000

I just implemented something similar to this using generic views. I got the idea from the tutorial that talks about using modelX.relationY_set. Something to remember about the object variable in templates (or any object you pass into your context) is that you have access to any of the properties and methods that do not require arguments. (I could be wrong, in that there may be a way to call methods with arguments but I have yet to need them)

By: Daily Digest for August 31st | William Stearns

Daily Digest for August 31st | William Stearns — Tue, 01 Sep 2009 03:28:44 +0000

[...] Shared Brian Jones: Representing Relationships in Django Templates Without Writing Extra Code (RelatedManag… [...]

By: m0j0

m0j0 — Mon, 31 Aug 2009 23:45:53 +0000

@malcolm — I suppose that’s fair, though it would’ve made debugging issues I had a breeze if I could’ve gotten something back when searching the django docs for “ManyRelatedManager”. I mean, Manager objects are covered, and related objects are covered. Maybe it’s more an argument for either more advanced documentation (and maybe this is out there and I just don’t know about it), or a troubleshooting reference section away from the main docs or something. Perhaps this feat is actually best left to the community. I don’t have the answer. Maybe it’s a case of Django being a victim of its own outstanding documentation: the expectations of the users are raised, and can never be met anyway. Still, I applaud the project for trying harder than most.

By: Malcolm Tredinnick

Malcolm Tredinnick — Mon, 31 Aug 2009 23:29:45 +0000

Django’s documentation doesn’t mention things like RelatedManager because they’re internal implementation details. You never need to know what they are to use Django and they aren’t part of the public API. Django does document how to traverse to related fields, as you’ve discovered and that is the relevant piece of information here. There’s a mild argument to be made that we could title a couple of sections slightly differently and maybe tweak the text, since it’s sometimes easy to miss.