On Sat, Mar 5, 2011 at 5:31 AM, Florin Jurcovici wrote:
> Hi.
>
> I would always recommend stored procedures, as long as there are a
> very few rules obeyed:
> - keep them simple - they should mostly implement just CRUD operations
> plus application-specific searches, and should not encapsulate a
Hi Team
I very much agree with the points shared by Florin (esp. the two rules).
But unfortunately, these rules are not standards and that is where the real
problem lies.
The injudicious use of SPs leads to un-manageable code which is rarely
portable (real life situations J which are too comm
Hi Team
I very much agree with the points shared by Florin (esp. the two rules).
But unfortunately, these rules are not standards and that is where the real
problem lies.
The injudicious use of SPs leads to un-manageable code which is rarely
portable (real life situations J which are too comm
Hi.
I would always recommend stored procedures, as long as there are a
very few rules obeyed:
- keep them simple - they should mostly implement just CRUD operations
plus application-specific searches, and should not encapsulate any
other logic
- use just portable SQL (well, as long as this is poss
Hi Nathan,
Nathan Nobbe wrote:
Also, bear in mind that personally I tend to favor OO paradigms for
application development so would prefer feedback that incorporates that
tendency.
Initial thoughts are
Bad:
. Not well suited for ORM, particularly procedures which return multiple
result sets co
5 matches
Mail list logo
