# 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:** [3 Aprile 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:** 10

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [3 Aprile 2015, 9:53pm UTC](https://meta.discourse.org/t/can-you-upgrade-discourse-seamlessly-if-there-is-a-breaking-db-change/27175/10 "2015-04-03T21:53:11Z")

</div>

I have no idea what you are proposing here and am having extreme issues following you.

**IF** we decide one day to rename the table `topics` to `amazing-topics` then old web servers running our old repo will break. 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.

I am happy with you to slowly explain your technical recommendations but your one-liners here are not really helping me.

---

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