Hi Tomas Juarez I think you will find all the answers in the second part of this blog post here https://rafal.hashnode.dev/loki-installation-and-configuration-no-more-code-conflicts-in-the-shared-oracle-dev-database :)

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.

Michael Abele No problem. Slide 16 just show my pre-configured connections in SQL Developer extension for VS Code.

Hi Michael. To which part of my blog post is your question related to?

HI Jared. Yes, you can. Just use "ignore" parameter - described here in official documentation https://docs.oracle.com/en/database/oracle/sql-developer-command-line/24.4/sqcug/codescan-command.html#:~:text=%2Dignore%20skips%20specified%20rule%20checks.

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? :)

I recommend watching this office hours video: https://www.youtube.com/watch?v=EM3_2Dd3LOs.Guys from Oracle show examples of when 2 developers are working on different tickets in the same environment.

Peter Files, that are created with "project export" are already "Liquibase formatted sql". But if you want to somehow modify them before it's exported then I would recommend deep diving into Oracle Docs - there are some config options

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

Hi Neil! Thanks for asking. This tutorial is dedicated to using standalone Liquibase, which is why it's downloaded here. The original version of this text was published in 2021 ( when SQLcl Liquibase was just starting and still not perfect), and there are still many projects where we use the standalone version of Liquibase. Best wishes! Rafal