# Can you upgrade Discourse seamlessly if there is a breaking db change?

**URL:** <https://meta.discourse.org/t/can-you-upgrade-discourse-seamlessly-if-there-is-a-breaking-db-change/27175>\
**Category:** Support\
**Created:** [April 3, 2015, 9:48pm UTC](https://meta.discourse.org/t/can-you-upgrade-discourse-seamlessly-if-there-is-a-breaking-db-change/27175 "2015-04-03T21:48:59Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![skyeagle](https://avatars.discourse-cdn.com/v4/letter/s/7993a0/32.png) [@skyeagle](https://meta.discourse.org/u/skyeagle)\
**Post date:** [April 3, 2015, 9:22pm UTC](https://meta.discourse.org/t/can-you-upgrade-discourse-seamlessly-if-there-is-a-breaking-db-change/27175/5 "2015-04-03T21:22:16Z")

</div>

> [@Manually update Discourse and Docker image to latest](https://meta.discourse.org/t/manually-update-discourse-and-docker-image-to-latest/23325/17):
>
> If you want zero downtime, you must run 2 web containers and cycle them in and out using haproxy

So, one container in public and the second one is on stage. Let’s imagine that the second one goes with migration which makes breaking changes in db (for example, removes column). How do the first one will react on this?

---

_[View the full topic](https://meta.discourse.org/t/can-you-upgrade-discourse-seamlessly-if-there-is-a-breaking-db-change/27175)._