Tables - Instruments - Remove null constraint on relationship#186
Closed
jomey wants to merge 1 commit into
Closed
Conversation
Remving the requirement for an instrument with layers as we not always will have that information. For instance with temperatures or densities.
Member
Author
|
Also open to keep this in place and add a new fallback category of 'unknown' or 'manual' (in cases like the temps) in place. |
Contributor
|
After some conversation with @jomey we decided it is better to always have an instrument for all observations. If instrument is not provided, we will hard code to it being "unknown" in SnowEx/snowex_db#56 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remving the requirement for an instrument with layers as we not always will have that information. For instance with temperatures or densities.