Comments for SQLcl : Automating Your SQL and PL/SQL Deployments using the SQLcl implementation of Liquibase
Anonymous said...What if 2 people change same schema object, like packages? Its not uncommon. Its easy to miss changes here. Its very important to have a "maintainer" to manage schema and code changes so that we have changelogs in order. And yes, i don't like liquibase tag for schema change either! I have a hunch it does not work for complex table creation, like index or partitioned table.
Their changes are separate events. They will be merged into the relevant branch separately, or as a single pull request, if it is safe to pull both commits I guess. Either way, their change will only be included in the master change log when they are happy for it to be applied to the relevant environment. As a result, the change log is the serialisation of this.
As I mention in the article, this needs discipline and process in place to work. It's not magic. It's also why I suggest fix-forward. If something goes in that breaks stuff, you have to "load the old version". That is a new commit, putting back the old version and applying it. The "reversion" is a new version.
Deployment pipelines *always* have to consider how you handle multiple people working on the same thing. Databases are no different in this respect. That's the fun. :)
DO NOT ask technical questions here! They will be deleted!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!
If you post personal information (name, email address etc.) you are agreeing to them being stored and displayed. Feel free to remain anonymous.