[FIX] - Decode bytestring for version from redcap#250
Merged
DESm1th merged 1 commit intoTIGRLab:masterfrom Dec 30, 2019
Merged
Conversation
…am database errors
DESm1th
approved these changes
Dec 30, 2019
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
3 participants
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.
Issue being fixed
Sometimes, when pulling from REDCAP, python interprets the content as bytestring rather than string. The database doesn't decode this automatically resulting in errors due to character length. This has been an issue for SENDEP for which redcap records have never pulled in correctly because the redcap_version was always read in as a bytestring
Solution
Run a decode to UTF-8 on the redcap version