This is a fine way to do it but if you don't put things in your model space you likely end up instantiating the schema over and over which is annoying (to) code. Plus, while it's definitely not a best practice, it is sometimes nice to be able to do DB hacking in templates where debugging and prototyping can be faster and easier. I am not a PHP fan but it's pretty obvious why it became so popular -- having DB access in the template may be hacky but it's pretty damn useful and quick. 

[% foo = c.model("DB::Foo").search_rs() %]
[% foo.count() %] foo[% foo.count() == 1 ? "" : "s" %] in the DB

[download]

In reply to Re^2: Best Practice: Catalyst and DBIx::Class by Your Mother
in thread Best Practice: Catalyst and DBIx::Class by confused_elf

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.