DM-25411: Fix for expected exception in put() method
#314
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
Added explicit check for empty attribute name and value in put() method, this should work identically across all backends. Tested with postgres on my CentOS7 virtual machine and it works OK now. Oracle is still not tested but should work as well.
andy-slac
force-pushed
the
tickets/DM-25411
branch
from
6bdb880
to
78dee54
Compare
timj
approved these changes
Jun 12, 2020
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.
Added explicit check for empty attribute name and value in put() method,
this should work identically across all backends. Tested with postgres
on my CentOS7 virtual machine and it works OK now. Oracle is still not
tested but should work as well.