3 ms·
It's obvious to me and I imagine most programmers, too. However, as a data engineer I've been at some companies that treat SQL differently and seen bad practic
by castlecrasher2 5y ago
It's obvious to me and I imagine most programmers, too.
However, as a data engineer I've been at some companies that treat SQL differently and seen bad practices that I believe the article is addressing, like putting SQL statements as stored procedures or materialized views instead of in git.
- xupybd 5y agoI didn't understand the point about stored procedures. Why not have stored procedures? Yes, you treat it like code any changes to the stored procedure are scripted, stored in git and deployed with a data migration tool. But store procedures give you a single place to call SQL. If there is a procedure that does a standard calculation used by 5 reports then put it in a function or a stored procedure and have every report call that procedure / function.