From 519e494da85a08b184cb43400264df43d9aa6ea6 Mon Sep 17 00:00:00 2001
From: Frederick Muriuki Muriithi
Date: Wed, 19 Oct 2022 06:59:58 +0300
Subject: Issues (database-migrations): New issue

---
 issues/database-migrations.gmi | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 issues/database-migrations.gmi

diff --git a/issues/database-migrations.gmi b/issues/database-migrations.gmi
new file mode 100644
index 0000000..13c35f3
--- /dev/null
+++ b/issues/database-migrations.gmi
@@ -0,0 +1,25 @@
+# Database Migrations
+
+## Tags
+
+* assigned:
+* type: feature
+* priority: high
+* keywords: database migrations
+* status: pending
+
+## Description
+
+There might need to be some form of database migration to help keep the
+
+* schema
+* triggers
+* views
+* materialised views
+
+etc synchronised across all the databases (i.e. development, CI/CD, staging, production etc.).
+
+Some issues that might benefit from this are the following:
+
+=> /issues/systems/mariadb/move-to-innodb
+=> /issues/materialised-views-for-correlations
-- 
cgit 1.4.1