summaryrefslogtreecommitdiff
path: root/issues/database-migrations.gmi
diff options
context:
space:
mode:
authorFrederick Muriuki Muriithi2022-10-19 06:59:58 +0300
committerFrederick Muriuki Muriithi2022-10-19 06:59:58 +0300
commit519e494da85a08b184cb43400264df43d9aa6ea6 (patch)
treeb746379e639d7bf1fa2d7ee8b706368152e6e483 /issues/database-migrations.gmi
parentdcc3b19748b2b688e966701bc315c3a3fec84c7b (diff)
downloadgn-gemtext-519e494da85a08b184cb43400264df43d9aa6ea6.tar.gz
Issues (database-migrations): New issue
Diffstat (limited to 'issues/database-migrations.gmi')
-rw-r--r--issues/database-migrations.gmi25
1 files changed, 25 insertions, 0 deletions
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