---
title: "Discussion on \"Part 5: SQLcl Project (It will forever change your Database & APEX deployments)\" | Hashnode"
description: "Discussion on \"Part 5: SQLcl Project (It will forever change your Database & APEX deployments)\". Welcome to part 5 of \"A whirlwind tour of Database Schema Changes Tracking Tools\"\nIn this article, I will provide a general overview and test the basic functionalities of the Oracle SQLcl “Project” co"
url: "https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Part 5: SQLcl Project (It will forever change your Database & APEX deployments)](https://rafal.hashnode.dev/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments?utm_source=hashnode&utm_medium=feed)

Welcome to part 5 of "A whirlwind tour of Database Schema Changes Tracking Tools" In this article, I will provide a general overview and test the basic functionalities of the Oracle SQLcl “Project” co

Nov 28, 2024 · 7 min read · rafal.hashnode.dev  
Updated May 28  
Read the article

-   [#sqlcl](https://hashnode.com/tag/sqlcl)
-   [#cicd](https://hashnode.com/tag/cicd)
-   [#ci-cd](https://hashnode.com/tag/ci-cd)
-   [#apex](https://hashnode.com/tag/apex)
-   [#orclapex](https://hashnode.com/tag/orclapex)
-   [#oracle](https://hashnode.com/tag/oracle)
-   [#oracle-apex](https://hashnode.com/tag/oracle-apex)
-   [#databases](https://hashnode.com/tag/databases)
-   [#version-control](https://hashnode.com/tag/version-control)

## Written by

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk)

@rgrzegorczyk · Kielce, POLAND

  
[View profile](https://hashnode.com/@rgrzegorczyk)

Oracle APEX & PL/SQL Developer at Pretius Low-Code

Oracle APEX &amp; 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.

## Responses 2

Markdown supported · ⌘↵ to post

[Lukasz Wasylow](https://hashnode.com/@baalowy)

[Dec 10, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939)

Hi How do you manage versions in multi developer environment? So two or more people working in different branches on different features?

[Lukasz Wasylow](https://hashnode.com/@baalowy)

[Dec 10, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939#reply-675853bf8fa794a00bc03a3a)

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk) 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.

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk)

[Dec 10, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939#reply-67588771c3451339a7a2cc59)

[Lukasz Wasylow](https://hashnode.com/@baalowy) 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? :)

[Lukasz Wasylow](https://hashnode.com/@baalowy)

[Dec 10, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939#reply-67588e6c85550d72d611b478)

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk) 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 🙏

[Peter](https://hashnode.com/@pvdn)

[Nov 29, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67495d1ecfffb8e67bc4b16a)

Is it possible to add some custom text to the exports? I would like to add liquibase formatted sql to the object exports as well, just like add-custom.

[Peter](https://hashnode.com/@pvdn)

[Nov 29, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67495d1ecfffb8e67bc4b16a#reply-6749753efbb3965d8e915403)

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk) I mean, I would like liquibase formatted sql in the output from the command "project export" that export db objects.

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk)

[Nov 29, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67495d1ecfffb8e67bc4b16a#reply-6749768cef9ffb28cfb6dcd6)

[Peter](https://hashnode.com/@pvdn) 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

[Hamza Eraoui](https://hashnode.com/@panguan)

[Dec 9, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67495d1ecfffb8e67bc4b16a#reply-6757145775398779b75fb844)

Hey [Peter](https://hashnode.com/@pvdn), Not sure if I understand your use-case. But overall after you exported your objects using project export, you can then call project stage and you will find your objects wrapped with liquibase metadata under the dist folder.
