Ticket #10903: method-template-doc.diff

docs/topics/db/queries.txt

@@ -818 +818 @@
     # THIS WILL RAISE A FieldError
     >>> Entry.objects.update(headline=F('blog__name'))
 
+.. _topics-db-queries-related:
+
 Related objects
 ===============
 

docs/topics/templates.txt

@@ -576 +576 @@
 The variable's contents are still automatically escaped, if necessary, because
 they're beyond the control of the template author.
 
+.. _template-accessing-methods:
+
+Accessing method calls
+======================
+
+Most method calls attached to objects are also available from within templates.
+This means that templates have access to much more than just  class attributes
+(field names) and variables passed in from views. For example, the Django ORM
+provides the :ref:`"entry_set"<topics-db-queries-related>` syntax for
+discovering a collection of objects related on a foreign key. Therefore, given
+a model called "comment" with a foreign key relationship to a model called
+"task" you can loop through all comments attached to a given task like this::
+
+    {% for comment in task.comment_set.all %}
+        {{ comment }}
+    {% endfor %}
+
+Similarly, :ref:`querysets<topics-db-queries>` provide a ``count()`` method
+to count the number of objects they contain. Therefore, you can obtain a count
+of all comments related to the current task with::
+
+    {{ task.comment_set.all.count }}
+    
+And of course you can easily access methods you've explicitly defined on your
+own models::
+
+    # In model
+    class Task(models.Model):
+        def foo(self):
+            return "bar"
+
+    # In template
+    {{ task.foo }}
+
+Because Django intentionally limits the amount of logic processing available
+in the template language, it is not possible to pass arguments from view code
+to method calls accessed from within templates. Data should be calculated in
+views, then passed to templates for display.
+
 .. _template-built-in-reference:
 
 Using the built-in reference