4 ms·
This doesn't seem to have anything to do with Stored Procedures. Do a quick search & replace above: s/stored procedure/function ... and notice that you're
by jasonkester 16y ago
This doesn't seem to have anything to do with Stored Procedures. Do a quick search & replace above:
s/stored procedure/function
... and notice that you're simply describing a common issue with building anything. If you change the interface to something, you need to change the stuff that calls it. That's just life, and it's the same story whether you have databases in the mix or not.
- MartinCron 16y agoThe distinction is that with functions, I can have my automated refactoring tools help me change them safely, I can have my compiler tell me if I get them wrong, I can have my automated tests tell me if I get them wrong. By keeping the procedural stuff in the procedural layer and not in the persistence layer, it's easier (for me, anyway, your experience may be different) to keep things encapsulated and make contained changes in contained places.