That's really a matter of personal taste. You can do the "limiting" in either place. I weigh the decision on this type of thing based on the server resources used. If the cost of retrieving the data is high and likely to be large often, then I would put it into the controller. That way you can limit it as early as possible, for example if you know you want to page rows from the database 50 at a time, it's best to just make the SQL 'LIMIT 50'.

If the chance that the data is too large are small ( not frequent ) and the cost to retrieve it isn't large, then I would probably opt to limit it in the template. So as not to overly limit the flexibility of the application.

Frank Wiles <frank@revsys.com>
www.revsys.com

In reply to Re: Displaying output by ides
in thread Displaying output by megaurav2002

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.