Version Control
Gerardo Lopez, September 18, 2024 - 7:01 pm UTC
Hello,
Thank you very much for your prompt response and the attention given to our inquiry. We greatly appreciate your time and dedication.
We would like to ask for your advice regarding some strategies to effectively manage version control when the business logic is implemented directly within the database. We understand that handling version control in these cases can be challenging, especially when dealing with complex SQL code and internal dependencies.
Additionally, we sometimes encounter situations where compiling one object causes others to break due to dependencies within the database. Could you please share any recommendations or approaches to mitigate these issues? Are there best practices or tools that you would suggest to avoid these conflicts during the development and deployment cycle?
Once again, we sincerely appreciate your cooperation and look forward to your valuable insights.
September 19, 2024 - 9:39 am UTC
Edition-based redefinition is what to look at here. This enables you to change database objects with zero downtime. This is by having multiple copies of editionable objects (PL/SQL, views, etc.) in separate editions. Using these allows you to deploy & validate changes in a private edition while customers use the public edition(s).
https://www.oracle.com/database/technologies/high-availability/ebr.html