Mercurial > gemma

diff TODOs-historization_ng.md @ 4066:6bfe42f88638 historization_ng

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Some thoughts on an extra SR constraint trigger to check for ref gauge..
author Sascha Wilde <wilde@intevation.de>
date Wed, 24 Jul 2019 18:55:09 +0200
parents 39441cdc5021
children
line wrap: on
line diff
--- a/TODOs-historization_ng.md	Wed Jul 24 18:16:27 2019 +0200
+++ b/TODOs-historization_ng.md	Wed Jul 24 18:55:09 2019 +0200
@@ -30,6 +30,12 @@
 
 ## Sounding Results:
 
+- Maybe add a constraint to check, that a ref gauge is available?
+  Maybe not neccessary as import isn't possible anyway, as the
+  reference gauge is needed for the import process... (So the
+  constraint would never catch anything, as no data could be produced
+  without ref gauge) Only upside: we would triger if there is an error
+  in the backend generating SR with invalid ref data.
 - Check during upload that matching bottleneck and reference gauge
   data is available (and use ist correctly)
 - Use correct reference gauge for X-Cuts