Part 5: SQLcl Project (It will forever change your Database & APEX deployments)

Rafal Grzegorczyk Thank you, I did have a watch. One thing I'm still unsure is that on demo they working on main which often is protected so running project release is hard. However running that in branch does not allow multiple developers working together as each branch would essentially cut its own release and hence my question about managing this. Or did I misunderstood the process and missing something? Thanks in advance.

Lukasz Wasylow If you will "project export", then indeed, you will export everything. So a solution would be e.g.:

1. Developer 1 is working on some changes in the database, and periodically, he exports only his changes to a branch, let's say branch "feature1."
2. Developer2 is working on his changes on the "feature2" branch and exports his changes.

"project export -o OBJECT_NAME"

At the end, their changes are merged:

• feature1 into e.g. branch "version_2.0"
• feature1 into branch "version_2.0"

Then, the privileged user lets call him Release Guy execute the "project stage" command, then "project release" etc.

Does it answer your question? :)

Rafal Grzegorczyk It does, yes thank you :) Indeed it seem doable with a sort of git flow approach. Trunk based seems more complex. But I will try it out, looking for alternatives for flyway and this looked promising. Again thank you for the help and your time, much appreciated 🙏