# 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:** Product Support\
**Created:** [Abril 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:** 11

<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:** [Abril 3, 2015, 10:15pm UTC](https://meta.discourse.org/t/can-you-upgrade-discourse-seamlessly-if-there-is-a-breaking-db-change/27175/11 "2015-04-03T22:15:29Z")

</div>

> [@sam](#):
>
> Only way to keep them working under such conditions is to create a writable view during the migration that keeps backwards compat in place.
> 
> In general our migrations are backwards compat. Rarely they are not, when they are not there is a minor outage.

This is exactly what I’m talking about. And I’m happy that you follow this practice. Thank you.

---

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