[FOLIO-2283] Compensation scripts in the schema migration guideline in the RMB Created: 25/Sep/19  Updated: 08/Jun/23  Resolved: 08/Jun/23

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Taras Spashchenko Assignee: Taras Spashchenko
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to MODSOURCE-392 Schema migration script is not runnin... Closed
Sprint:

 Description   

Add details regarding compensation scripts and preferred approach to use for schema migration



 Comments   
Comment by Julian Ladisch [ 04/Nov/21 ]

RMB doesn't support migrating to a previous version. SysOps and DevOps need to dump the database before migration if they want to undo the migration.

Liquibase has limited support for backward-compatible database migrations. For some change-types like create table, rename column, and add column Liquibase automatically creates rollback statements. However, for change-types like drop table and insert data the developers need to create a changeset tag and write the rollback commands: https://medium.com/podiihq/getting-started-with-liquibase-8965897092aa

FOLIO has very limited developer capacity. Do we really want to spend development time for making database migrations backward-compatible and testing them when SysOps and DevOps can easily use their database dumps to undo a migration?

Generated at Thu Feb 08 23:19:32 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.