Removed need to grant ut_annotation_manager to users.#949
Merged
Conversation
lwasylow
approved these changes
Jun 20, 2019
| if l_item is not null then | ||
| l_result := | ||
| l_result || | ||
| dbms_crypto.hash( |
Member
There was a problem hiding this comment.
Would not be better to remove function get_hash from ut_compound_data_helper and put it into ut_utils then refer to that function rather than directly to dbms_crypto.hash that way it would be kept in one place?
Member
Author
There was a problem hiding this comment.
Ouch. Didn't notice the comment.
Can take care of it later.
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.
No description provided.