---
title: "Comment by Abhinav Sharma on \"Building CI/CD for Oracle APEX - Part 2: When Different DDL Hashes Don't Mean Different Database Objects\" | Hashnode"
description: "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 tre"
url: "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"
---

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

Comment [Building CI/CD for Oracle APEX - Part 2: When Different DDL Hashes Don't Mean Different Database Objects](https://hashnode.com/posts/building-ci-cd-for-oracle-apex-part-2-when-different-ddl-hashes-don-t-mean-different-database-objects/6adf4e3592cceff05c10b1aa)

[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.
