# Can we change order of multiple changeSets in an xml file in a version 2 release, if those changesets are independent (means different tables)?

**URL:** <https://forum.liquibase.org/t/can-we-change-order-of-multiple-changesets-in-an-xml-file-in-a-version-2-release-if-those-changesets-are-independent-means-different-tables/7097>\
**Category:** Liquibase Development\
**Created:** [July 21, 2022, 1:50am UTC](https://forum.liquibase.org/t/can-we-change-order-of-multiple-changesets-in-an-xml-file-in-a-version-2-release-if-those-changesets-are-independent-means-different-tables/7097 "2022-07-21T01:50:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Benjamin\_JO](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/benjamin_jo/32/805_2.png) [@Benjamin\_JO](https://forum.liquibase.org/u/Benjamin_JO)\
**Post date:** [July 21, 2022, 1:50am UTC](https://forum.liquibase.org/t/can-we-change-order-of-multiple-changesets-in-an-xml-file-in-a-version-2-release-if-those-changesets-are-independent-means-different-tables/7097/1 "2022-07-21T01:50:17Z")

</div>

I am a beginner using liquibase with Corda, Imagine we had 2 changeSets =\>

**table1\_v1** , **table2\_v1** in version **1** first release.

We introduced **table1\_v2** in version **2** release in between.

Now I suppose order would be **table1\_v1** → **table1\_v2** → **table2\_v1** ,

Will inserting it like this (between two change sets) become an issue at a later point (like if any dependency came into picture between tables in future or does checksum change in this scenario, since order is changed now?

I found a related scenario here: [liquibase - execution order of changesets - Stack Overflow](https://stackoverflow.com/a/33914644/12489459) (we are also thinking of split xml’s based on tables from first release).

Basically my idea is also same for better readability by grouping changesets in each file based on table and then include those files into master xml.

```auto
table1_v1.xml -------->
                         table1.xml ------------> 
table1_v2.xml -------->

                                                   master.xml
table2_v1.xml -------->
                         table2.xml ------------> 
table2_v2.xml -------->

```

_table **1\_v1** , table **1\_v2** included as file inside **table1**.xml & **table1**.xml & **table2**.xml included as file inside **master**.xml_

I need to know the drawback this have.

---

<div class="post-metadata">

**Author:** ![daryldoak](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/daryldoak/32/764_2.png) [@daryldoak](https://forum.liquibase.org/u/daryldoak)\
**Post date:** [July 22, 2022, 5:42pm UTC](https://forum.liquibase.org/t/can-we-change-order-of-multiple-changesets-in-an-xml-file-in-a-version-2-release-if-those-changesets-are-independent-means-different-tables/7097/2 "2022-07-22T17:42:42Z")

</div>

Changeset are executed in sequential order. Adding a new changeset between to existing changesets should cause no problem, but there is always the chance of a dependency problem if you were to deploy to a database that does not yet have any changeset deployed, and you have something in **table1\_v2** that depends on **table2\_v1**.

---

<div class="post-metadata">

**Author:** ![Benjamin\_JO](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/benjamin_jo/32/805_2.png) [@Benjamin\_JO](https://forum.liquibase.org/u/Benjamin_JO)\
**Post date:** [July 27, 2022, 1:58am UTC](https://forum.liquibase.org/t/can-we-change-order-of-multiple-changesets-in-an-xml-file-in-a-version-2-release-if-those-changesets-are-independent-means-different-tables/7097/3 "2022-07-27T01:58:04Z")

</div>

ok, means. to a new database, there is a risk with version 2. for older db migration, its fine, right