fix: dataElementIdScheme should not filter events DHIS2-14968 #19267
Conversation
This file contains 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
|
muilpp
approved these changes
Nov 22, 2024
larshelge
approved these changes
Nov 23, 2024
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.
dataElementIdScheme!=UIDfilters out events without a data value while it should not.I don't remember exactly at what stage I needed the
where, maybe when I tried approach #19123.dataElementIdSchemewas introduced in#19153
dataElementIdScheme!=UIDadds a join from the JSONB dataValues keys on dataelement in the parent query. There cannot be an empty JSON key. The JSON key is a data element UID that is validated on import.