Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Unfortunately, some procedures have already been modified in the development environment. What can be done in that case ? Is there any way to handle this such that we do not need to change the procedure name ? For example, like changing schemas of procedures, is there any such way ? Commented Aug 6, 2019 at 12:53
  • 6
    @Shanid If the development database is being treated as a gold copy and can't be rebuilt into the same state from scratch, it would be wise to stop what you're doing and reconsider your development processes. Commented Aug 6, 2019 at 17:02
  • In addition to David's excellent answer In your case the stored procedures can considered part of the API. Hence if there is a new version of the API which is not compatible than your software as well as your stored procedures need to follow suite. Apart from that versioning a (REST?) API is a bad think in itself for much the same reasons as David pointed out: an extra code base needs to be maintained. Consider making your API HOTEOAS and have clients automatically adapt newer versions (contracts) of your API Commented Jul 19, 2024 at 12:53