# Does liquibase support update with specific version

**URL:** <https://forum.liquibase.org/t/does-liquibase-support-update-with-specific-version/2990>\
**Category:** General Discussion\
**Created:** [May 19, 2014, 10:05am UTC](https://forum.liquibase.org/t/does-liquibase-support-update-with-specific-version/2990 "2014-05-19T10:05:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![littcai](https://avatars.discourse-cdn.com/v4/letter/l/f14d63/32.png) [@littcai](https://forum.liquibase.org/u/littcai)\
**Post date:** [May 19, 2014, 10:05am UTC](https://forum.liquibase.org/t/does-liquibase-support-update-with-specific-version/2990/1 "2014-05-19T10:05:00Z")

</div>

**scenario:**

I have 3 databases, No.1 is initialized with version 1.0.0, No.2 is&nbsp;But is there a way to upgrade No.2 from 1.1.0 to 2.0.0?(Ignore the changeset of 1.1.0 without modify any of changelog.xml)

maybe read database version from a table and ignore some changesets

---

<div class="post-metadata">

**Author:** ![un1376558435824r75id](https://avatars.discourse-cdn.com/v4/letter/u/439d5e/32.png) [@un1376558435824r75id](https://forum.liquibase.org/u/un1376558435824r75id)\
**Post date:** [May 19, 2014, 10:05am UTC](https://forum.liquibase.org/t/does-liquibase-support-update-with-specific-version/2990/2 "2014-05-19T10:05:00Z")

</div>

In some conditions database is&nbsp;initialized&nbsp;with latest scripts, start from version 1.0.0 is ugly, so databasechangelog is empty and liquibase doesn’t known the current version of database.

---

<div class="post-metadata">

**Author:** ![un1382561729492r88id](https://avatars.discourse-cdn.com/v4/letter/u/c4cdca/32.png) [@un1382561729492r88id](https://forum.liquibase.org/u/un1382561729492r88id)\
**Post date:** [May 19, 2014, 10:05am UTC](https://forum.liquibase.org/t/does-liquibase-support-update-with-specific-version/2990/3 "2014-05-19T10:05:00Z")

</div>

I don’t know if what you are proposing is a good way of thinking about this. Though you may think of the schemas as being at a specific version, Liquibase thinks of them as sets of changes. You can label a particular union of sets of changes as having a particular label or version, but that version needs to be the union of all the changes. If version 1.0.0 has changes A, B, C, and version 1.1.0 has changes A, B, C, and D, then version 2.0 must, by necessity, include A, B, C, and D, plus any additional changes for 2.0.&nbsp;

There may be specific sets of changes that will work in this kind of scenario, but without examining the exact set of changes, it is impossible to say beforehand whether this would work. For it to work, the set of changes between version 1.0 and 1.1 would have to be things that cancelled each other out or that were otherwise inconsequential to the operation of the software.

Steve Donie

Principal Software Engineer  
Datical, Inc. [http://www.datical.com/](http://www.datical.com/)