@rgrzegorczyk
Oracle APEX & PL/SQL Developer at Pretius Low-Code
Oracle APEX & PL/SQL Developer with 10 years of experience in IT, including financial systems for government administration, energy, banking and logistics industry. Enthusiast of database automation. Oracle ACE Associate. Certified Liquibase database versioning tool fan. Speaker at Kscope, APEX World, SOUG, HrOUG, POUG and DOAG. Likes swimming in icy cold lakes in winter and playing basketball.
Nothing here yet.
Michael Abele dev_admin is an ADMIN user at OCI, so it will always have the required grants. For exports, you should always use a user who has the privileges required for the schemas included in the project. For OCI, it can be ADMIN, for non-premise, it could be a user with a role assigned ( and that role should have everything required). Basically, is up to you.
Lukasz Wasylow If you will "project export", then indeed, you will export everything. So a solution would be e.g.: 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." 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? :)
Hi Peter. SQLcl Projects use Liquibase in the background so there shouldn't be any problems if you will just manually add new changesets / changelogs -> sth like here https://rafal.hashnode.dev/liquibase-tutorial-a-step-by-step-guide-for-you#:~:text=anddepartmentstables).*-,Changesets,-Database%20change%20is