An error occurred while fetching this tab.
Draft: JiHu guidelines for database migrations (separate schema approach)
- Sep 15, 2021
-
-
Andreas Brandl authored
-
Direct reading link: https://ab-jihu-db-separate.about.gitlab-review.app/handbook/ceo/chief-of-staff-team/jihu-support/jihu-database-change-process.html
In order to facilitate upgrades between GitLab CE/EE editions and JiHu editions, we need to find a good strategy for database schema changes. There are two different proposals:
This describes the "keep the database schema the same across GitLab CE/EE and JiHu editions" approach.
Related issues:
This proposal implements a clear separation of concerns between GitLab and JiHu database migrations. In order to support edition changes from GitLab to JiHu editions, we may need to resolve conflicts in database migrations for each release of JiHu.
This reduces operational overhead on GitLab.com, too, as we would not see any JiHu-specific database objects (e.g. indexes) on GitLab.com (where they are absolutely not required).