News for hackers. Stuff that matters.
Re:We Can Do Better Than SQL by sozy777 on Tuesday August 11, 2020 @04:08AM (#24118238)
You lose source control on your procedures. How you deal with that?
Re:We Can Do Better Than SQL by piva00 on Tuesday August 11, 2020 @04:58AM (#24118506)
Why? When I worked doing infrastructure and CI/CD automation we created a pipeline for deploying stored procedures, not that different from any other code lifecycle process.
Re:We Can Do Better Than SQL by dragonwriter on Tuesday August 11, 2020 @04:13AM (#24118258)
> You lose source control on your procedures

Why would you do that?

Re:We Can Do Better Than SQL by Akronymus on Tuesday August 11, 2020 @04:26AM (#24118339)
We use daily backups of the whole server, so if we really need to rollback, we can. And if we absolutely need source control, we could write a procedure in combination with a trigger to automatically write the stored procedure to some source control.

Also there are tools out there that provide that functionality. Found with a few seconds of searching. https://host.apexsql.com/sql-tools-source-control.aspx

Re:We Can Do Better Than SQL by gregw2 on Tuesday August 11, 2020 @06:40PM (#24126838)
You can use Liquibase or Flyway and an automated deployment process to keep your SQL code in sync with non-SQL code (if needed.) For bonus points, you can make your stored procedures be callable by other stored procedures, create/teardown mock data, and do TDD where your test suite of stored procedure tests runs on build during deployment and either has a PASS and deploys or hits a FAIL and the deployment aborts.
Re:We Can Do Better Than SQL by diegoperini on Tuesday August 11, 2020 @07:17AM (#24119161)
If you use a DBMS to manually update these, yes. Otherwise you can do this in code whenever you want in your build/deploy pipeline.
Re:We Can Do Better Than SQL by djrobstep on Tuesday August 11, 2020 @07:36AM (#24119264)
Just wrote a stored procedure in a text file and committed it to git. Seemed to work ok.