News for hackers. Stuff that matters.

A comment on Beware of Developers Who Do Negative Work. Parent comment

Re:Beware of Developers Who Do Negative Work by yoz-y on Monday December 19, 2016 @03:06AM (#13210171)
From what I gathered one of the biggest problems of stored procedures is that they do not play well at all with source control and associated tooling such as code review.
[ Parent | on HN ]
Re:Beware of Developers Who Do Negative Work by djrobstep on Monday December 19, 2016 @03:55AM (#13210308)
I just tried to commit a stored procedure to git and it seemed to work.

I then asked a colleague to review it. This also worked.

[ Parent | on HN ]
Re:Beware of Developers Who Do Negative Work by yoz-y on Monday December 19, 2016 @11:08AM (#13212289)
Ok. I did not know that. As I said this is what I have gathered from what I have read around as a common complaint. Out of curiosity, what is the testing-deployment cycle of stored procedures in source control? How do you assure yourself that the database uses a procedure coming from a specific commit?
[ Parent | on HN ]
Re:Beware of Developers Who Do Negative Work by jholman on Monday December 19, 2016 @04:58PM (#13215338)
How do you assure yourself that your non-database code uses code coming from a specific commit?

In general, you have a deployment procedure that overwrites all the old code with all-new code, and from there on out you trust, right? Why not use the same approach?

[ Parent | on HN ]
Re:Beware of Developers Who Do Negative Work by lostboys67 on Monday December 19, 2016 @03:52AM (#13210297)
Rubbish you can check in your sprocs into a source control system along with the Database schema I never had any problems at BT when we did this.

And why can you not code review your sprocs?

[ Parent | on HN ]