# Ignore changesets for a new deploy

**URL:** <https://forum.liquibase.org/t/ignore-changesets-for-a-new-deploy/1592>\
**Category:** General Discussion\
**Created:** [August 18, 2011, 10:18pm UTC](https://forum.liquibase.org/t/ignore-changesets-for-a-new-deploy/1592 "2011-08-18T22:18:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guest](https://avatars.discourse-cdn.com/v4/letter/g/8dc957/32.png) [@Guest](https://forum.liquibase.org/u/Guest)\
**Post date:** [August 18, 2011, 10:18pm UTC](https://forum.liquibase.org/t/ignore-changesets-for-a-new-deploy/1592/1 "2011-08-18T22:18:00Z")

</div>

Is it possible to ignore changesets and only run the “final” database DDL-scripts that creates the database. I guess liquibase should mark the last changesets as “ran”, so the next deploy + start with news changesets will apply correctly.

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [August 18, 2011, 10:18pm UTC](https://forum.liquibase.org/t/ignore-changesets-for-a-new-deploy/1592/2 "2011-08-18T22:18:00Z")

</div>

[http://www.liquibase.org/manual/contexts](http://www.liquibase.org/manual/contexts)&nbsp;are the normal way for&nbsp;conditionally&nbsp;applying changesets at runtime.

You can also add preconditions to only run changesets if tables already exist.

If you are asking if you can have liquibase skip old changesets that are no longer needed (like a create changeset where the table is later dropped) you can not. That will require you to manually edit the changelog based on how you understand the database to evolve. It’s usually not best to do that, however, since it can have unintended&nbsp;consequences.

Nathan