I'm sure that you can make it work, and make it work well. Also if the system has been factored in a given way, maintaining the factoring is typically going to work far better than degrading it.

I'm also sure that my preferences are shaped by an experience with some stored procedures which were very poorly written, which contrasted nicely with cases where the same logic had been moved into an application layer and then was organized there fairly cleanly.

And I would like to point out that when I said, "I wouldn't lean that way..." I meant that to be truly understood as a personal preference which others disagree with, and which I might choose either way on in practice. You demonstrated nicely that others do disagree, and confirmed at least one of the grounds on which they disagree. (The performance benefit from being able to rethink your database design.)

Plus finally I would like to note that the choice of which way to make this decision is not as important as who you have doing the work. Competent people can make either decision work, incompetent people (or even competent people with the wrong background or pressures) can make either fail.

In reply to Re: Re: N-tier, client/model, and business rules? by tilly
in thread N-tier, model/view, and business rules? by LameNerd

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.