3 ms·
What do you mean hack to keep them in source control? They're just sql source code files, like any other source code you can simply commit to version control?
by ako 2y ago
What do you mean hack to keep them in source control? They're just sql source code files, like any other source code you can simply commit to version control?
Wouldn't advise anyone to use Oracle, but neither would i advise them to use sql-server. Usually Postgres is good enough, although oracle plsql is still nicer than postgres plsql (e.g, packages).
- dalyons 2y agoi feel like i addressed this in a different subthread https://news.ycombinator.com/reply?id=40526231&goto=threads%3Fid%3Ddalyons%2340526231 https://news.ycombinator.com/reply?id=40526231&goto=threads%... > You can source control them, but then you have a deployment coordination problem. Often changes to business logic will be half in application code and half in the sproc, and you have to coordinate the deployment of that change. You have to somehow reason about what version of the sprocs are on your server. Add on that usually in enviroments that use sprocs, changes to them are gatekept by DBAs. Just write your business logic in application code.