Project

General

Profile

Actions

Feature #4230

closed

Make use of existing or implement own mechanism for handling SQL schema migrations.

Added by Jan Mach over 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Development - Core
Target version:
Start date:
07/27/2018
Due date:
% Done:

100%

Estimated time:
To be discussed:

Description

Currently there is no mechanism for intelligent handling of SQL schema changes. This could hurt very badly when we have to change or improve the schema. Take a look at Alembic.


Related issues

Related to Mentat - Support #4628: Consider/implement modeling of event database with SQLAlchemy declarative base.RejectedRadko Krkoš02/01/2019

Actions
Blocks Mentat - Bug #4367: Enumeration tables not consistent for non array columns that can contain NULLClosedPavel Kácha10/15/2018

Actions
Blocks Mentat - Feature #4383: Consider switching string classification fields to enumsRejectedJan Mach10/19/2018

Actions
Blocks Mentat - Feature #4275: Split jsonb column into its own tableClosedPavel Kácha

Actions
Actions

Also available in: Atom PDF