In this case, we have a fairly efficient way for a template to invoke a fast database operation directly. We don't always know in a view which attributes of an object a template might want to make use of, and here the easy access to ``count()`` in the template - possibly by the template author rather than the person responsible for creating the view - might make it appropriate to do it this with rather than through re-writing the view.