title: Role of django filters. Filtering or upfront formatting within the view?
body: <p>I would like to hear your opinion about this.</p>
  
  <p>I have a django application, where the data obtained from the model are rough. To make them nicer I have to do some potentially complex, but not much, operation. 
  An example, suppose you have a model where the US state is encoded as two letter codes. In the html rendering, you want to present the user the full state name. I have a correspondence two-letters -> full name in another db table. Let's assume I don't want to perform joins.</p>
  
  <p>I have two choices</p>
  
  <ol>
  <li>have the view code extract the two-letter information from the model, then perform a query against the second table, obtain the full name, and put it in the context. The template renders the full state name.</li>
  <li>create a custom filter which accepts two-letter codes, hits the db, and returns the full-length name. Have the view pass the two-letter information into the context, and put in the template the piping into the filter. The filter renders the two-letter code as a full string.</li>
  </ol>
  
  <p>Now, these solutions seem equivalent, but they could not be, also from the design point of view. I'm kind of skeptical where to draw the line between the filter responsibility and the view responsibility. Solution 1 is doing the task of the filter in solution 2, it's just integrated within the view itself. Of course, if I have to call the filter multiple times within the same page, solution 1 is probably faster (unless the filter output is memoized). </p>
  
  <p>What's your opinion in terms of design, proper coding and performance?</p>