Timeline for Pros and Cons of holding all the business logic in stored procedures in web application
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 26, 2018 at 8:56 | comment | added | Pushpendra | Why cant one unit test stored procs ?? I user TSQLT to unit test my TSQL | |
| Nov 19, 2013 at 16:16 | comment | added | sam yi | A agree this preference is generally tied to db resource scarcity. But it's also due to the "top" developers thinking they are dbas. Most good programmers are a confident bunch and they sell themselves as sql experts. They do not realize their shortcomings until they hire a competent dba... but most shops never get there. | |
| Jul 28, 2012 at 22:48 | comment | added | rally25rs | Well, in my situation dev's can't have their own DB, both in Oracle and DB2, because the "free" ones don't support all the features of the "real" ones. | |
| Jul 28, 2012 at 17:16 | comment | added | kevin cline | Stored procedures are pretty easy to unit-test, and every dev should have their own database, so there won't be any "concurrency and transaction troubles" | |
| Jul 28, 2012 at 16:21 | comment | added | gbjbaanb | I thought SPs were easy to unit test - they're already discrete units, you just need to work out what data to pre-populate the tables with to make them work. | |
| Jul 28, 2012 at 1:46 | history | answered | rally25rs | CC BY-SA 3.0 |