How do we manage multiple changes on the same stored procedure in the open source community version?
Say if 3 developers have changes on a single stored procedure for the same release, how do we manage it? How do we keep track of it?
Thank you!
How do we manage multiple changes on the same stored procedure in the open source community version?
Say if 3 developers have changes on a single stored procedure for the same release, how do we manage it? How do we keep track of it?
Thank you!
My opinion is that you need to manage your concurrent development issues outside of Liquibase using github to merge branches via a PR, then deploy a single change to the stored procedure to the database.
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Multiple Developers Overwriting Others' Stored Procedure Commits | 1 | 321 | December 8, 2022 | |
| Multiple stored procedures within one changeset for MS SQL Server | 1 | 3767 | December 3, 2020 | |
| Best Practices regarding Stored Procedures. | 2 | 1381 | July 20, 2009 | |
| Functions, Stored Proc, and the Like | 1 | 574 | March 23, 2019 | |
| Liquibase not updating stored procedures on deployment | 3 | 1924 | September 16, 2021 |