3 ms·
In a technology career that started in the early 1990s, one of the constants has been relational databases and SQL. There is no better general-purpose data stor
by SoftTalker 2y ago
In a technology career that started in the early 1990s, one of the constants has been relational databases and SQL. There is no better general-purpose data storage and query architecture, and it's the first (and usually last) thing I consider for almost any new development project that involves storing and retreiving data.
- nickpeterson 2y agoI’d also add, being decent at sql queries and design/tuning is a massive advantage over programmers who are not. It’s like being tasked with bulk editing text and one person knowing regular expressions and the other person just knowing string manipulation functions.
- nanomonkey 2y agoThe number of companies I've worked out where I said, "We can do that in the database with a view or a trigger" to be followed up by "Sounds Hacky" or "How do you saved that to Version Control" is staggering though. Modern programmers seem to be afraid of SQL.
- SoftTalker 2y ago"How do you saved that to Version Control" I see that objection a lot and it is just weird to me. You save it to version control like you do any other program source code. SQL is just text. I'm conservative with triggers. They have their place, but can definitely be abused. The problem arises when someone doesn't realize they are there, and updates start having unexpected (to them) side effects. I'll tend to prefer a stored procedure that is explicit about doing the main update and any needed side-effects.