From 706ae60e0d954e183a34a30a0a59a1e10b9c5a71 Mon Sep 17 00:00:00 2001
From: Alexander_Kabui
Date: Sun, 8 Jan 2023 16:28:01 +0300
Subject: update  issues/correlation-script-to-build-text-files

---
 issues/correlations-script-to-build-text-files.gmi | 23 ++++++++++++++++++++++
 1 file changed, 23 insertions(+)

(limited to 'issues')

diff --git a/issues/correlations-script-to-build-text-files.gmi b/issues/correlations-script-to-build-text-files.gmi
index f6344fe..0984c8a 100644
--- a/issues/correlations-script-to-build-text-files.gmi
+++ b/issues/correlations-script-to-build-text-files.gmi
@@ -22,3 +22,26 @@ The script could be triggered in any of the following ways
 * on-change: A "job" is run in the background to recreate the text file whenever data for a particular text dataset/trait/... is changed (created/updated/deleted).
 
 The automated triggers can be built in later once we have a working script. My (fredm) preferred method is to have the "on-change" trigger to avoid running the script even when data has not changed.
+
+
+
+## tasks
+
+[x] fetching all possible strains for specific probeset
+
+[x] fetch all probesetfreezes for script
+
+[] table tracker for change in tables then invoke the script
+
+[] add as a  job
+
+
+## Notes
+
+while using innodb engine last update time is  null possibly write
+a script/table o create track of this
+
+relevant resources
+
+=> https://dba.stackexchange.com/questions/291291/how-to-check-the-last-time-a-table-has-been-modified
+ 
\ No newline at end of file
-- 
cgit v1.2.3