2 ms·
You're making good points. First, I'm talking about a PL "middleware" layer than does not necessarily involves restructuring the data itself (basically, instea
by throw_m239339 7y ago
You're making good points.
First, I'm talking about a PL "middleware" layer than does not necessarily involves restructuring the data itself (basically, instead of querying tables or views, you query stored procedures or functions).
When it comes to version control, wouldn't a migration system suffice to assess the state of that layer?
As for unit testing, I kind of agree, it's possible though, like any other programming language.
- scarface74 7y agoThat doesn’t help. You can’t imagine the times I see Get_Customer_1 Get_Customer_2 Get_Customer_3 As far as version control, if someone does make a change to the unversioned “Get_Customer” and I want to switch branches. How do I make sure all of the stored procedures are in sync?
- AmericanChopper 7y agoThis is pretty much my experience with stored proc codebases too. I do consider SQL to be a very simple language, but store proc codebases tend to become incredibly complex. Finding an engineer that can maintain SQL code is very easy. Finding one that can maintain a particular maze of 1000+ stored procedures, views, functions, table triggers... is a completely different question.