[BI-1315] germplasm import: fix next val germplasm sequence call#139
Merged
[BI-1315] germplasm import: fix next val germplasm sequence call#139
Conversation
timparsons
approved these changes
Jan 26, 2022
nickpalladino
approved these changes
Jan 26, 2022
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.
Description
There is a bug with dsl.nextval() that gets our germplasm sequence values where it surrounds program keys that aren't lowercased with quotes, select nextval('"program_sequence"'). This causes a not found error in psql.
Dependencies
none
Testing
Uppercase the program key in one of your germplasm sequences. For example, change bb_germplasm_sequence to BB_germplasm_sequence.
Checklist: