sql: fix sql input to security.SQLUsername issue #68830
Merged
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.
Resolves: #67818
The statements
drop owned by
andreassigned owned by
were case-sensitive because they relied onrole_spec_list
which wasn't correctly generatingsecurity.SQLusername
. With this change the two statement useNameLists
that are then converted intosecurity.SQLusernames
.role_spec_list
has been removed from the parser because it is no longer being used.Release note: None