Timeline for Direct database manipulation an anti-pattern?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 29, 2014 at 2:08 | comment | added | Ross Patterson | I thought your whole point was that database expertise was in short supply. My point is that, if data is important to your app, the database is as critical a component as the code, and that when the database is treated as a first-class citizen, you will have DBAs 24/7 just like you have coders (and hopefully Operations folks). | |
| May 28, 2014 at 18:48 | comment | added | JeffO | @RossPatterson - If you can write a properly tuned stored procedure you can write a high performing select statement. I just think building sql statement in code is easier in these cases. You want to search by abbreviation and phone number, why would my select statement bother to contain anything related to full name in this case? | |
| May 27, 2014 at 12:16 | comment | added | Ross Patterson | ""But what if I NEED to search on the full name or just the abbreviation and possibly phone number? It could happen."" - It could indeed, and when it does, the end-user will be much happier with the performance of a properly-tuned PROC than a non-SQL-coder-written SELECT that scans millions of rows on an unindexed column. | |
| May 20, 2014 at 12:53 | history | answered | JeffO | CC BY-SA 3.0 |