Introduction

Purpose and scope

This documents describes adjusting metadata storage to provide optimal way to work manually applied with database changes in scope of new feature delivery (authorized FR backports) and/or db hotfixes

Overview

Current database metadata (DB_Version table in appropriate schema) requires strictly unique identification of database changes (release+minor)  through all possible branches of database structure.

This practically creates limitation for update utilities, that prevent capability to support out-of-order db changes (hotfixes,FR backports) even in cases when there are no issue with their SQL compatibility.

Such modification gets applied by support manually, which consequently leads to issues during update of modified schema in future.

Specifications

Feature integration guide

Once implemented Policy of applying DB changes should be updated, to highlight new capabilities.

Ticket NumberYT:DB-53
Target Build
MR51-0
Area

Database,

Database update utilities (dbup/dbup2)

Business Department

Development Department

Testing and Support Departments