diff options
| author | Frederick Muriuki Muriithi | 2022-10-19 09:39:19 +0300 |
|---|---|---|
| committer | Frederick Muriuki Muriithi | 2022-10-19 09:39:19 +0300 |
| commit | aa83e732ed8ec29cfeb923ae014ab89e1203a398 (patch) | |
| tree | 45ba796ccb65e972be1c803946f8456af22fbcc5 | |
| parent | 519e494da85a08b184cb43400264df43d9aa6ea6 (diff) | |
| download | gn-gemtext-aa83e732ed8ec29cfeb923ae014ab89e1203a398.tar.gz | |
Issues (materialised-views-for-correlations): Update issue
* Add notes on work done for lmdb
| -rw-r--r-- | issues/materialised-views-for-correlations.gmi | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/issues/materialised-views-for-correlations.gmi b/issues/materialised-views-for-correlations.gmi index cc87ad0..855a143 100644 --- a/issues/materialised-views-for-correlations.gmi +++ b/issues/materialised-views-for-correlations.gmi @@ -18,6 +18,10 @@ As part of the optimisation effort, we need to look into materialised views to s MySQL/MariaDB does not support materialised views (there is no `CREATE MATERIALIZED VIEW ...` command or equivalent) but there are ways around that, to simulate the materialized views. +There is some work on +=> /topics/genotype-database the genotype database +that should allow intermediate materialised views to be stored in lmdb + ### Implementation Concerns The implementation of the materialised views will need to concern itself with the following issues: |