---
title: "Discussion on \"Building CI/CD for Oracle APEX - Part 2: When Different DDL Hashes Don't Mean Different Database Objects\" | Hashnode"
description: "Discussion on \"Building CI/CD for Oracle APEX - Part 2: When Different DDL Hashes Don't Mean Different Database Objects\". Different DDL hashes do not always mean deployment changes. How I use versioned, object-specific normalization to compare Oracle database environments"
url: "https://hashnode.com/posts/building-ci-cd-for-oracle-apex-part-2-when-different-ddl-hashes-don-t-mean-different-database-objects/6adf4e3592cceff05c10b1aa"
---

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

Discussion

# [Building CI/CD for Oracle APEX - Part 2: When Different DDL Hashes Don't Mean Different Database Objects](https://davidpataki.com/building-ci-cd-for-oracle-apex-part-2-when-different-ddl-hashes-don-t-mean-different-database-objects?utm_source=hashnode&utm_medium=feed)

Different DDL hashes do not always mean deployment changes. How I use versioned, object-specific normalization to compare Oracle database environments

Oct 26 · 12 min read · davidpataki.com  
Read the article

-   [#oracle-apex](https://hashnode.com/tag/oracle-apex)
-   [#ci-cd](https://hashnode.com/tag/ci-cd)
-   [#devops](https://hashnode.com/tag/devops)
-   [#plsql](https://hashnode.com/tag/plsql)

## Written by

[David Pataki](https://hashnode.com/@enrol)

@enrol · Budaörs, Hungary

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

Oracle Database & APEX Consultant | Oracle ACE Pro

Oracle ACE Pro, founder of Enrol Consulting, and Oracle Database and APEX developer with more than two decades of experience building data-driven business applications. I write about Oracle Database, APEX, cloud and AI-assisted development.

## Responses 1

Markdown supported · ⌘↵ to post

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 26](https://hashnode.com/posts/building-ci-cd-for-oracle-apex-part-2-when-different-ddl-hashes-don-t-mean-different-database-objects/6adf4e3592cceff05c10b1aa/comment/6adf9db43b9bd4b0552ee10b)

The rule-version field is a useful detail here. Keeping it beside the hash makes it clear whether two snapshots were compared on the same basis, rather than treating every changed hash as a deployment task.
