fix(security_label): Properly quote qualified column names in Postgre… #562
+11
−1
Conversation
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
…SQL security label creation
|
@cyrilgdn Can you have a look? Otherwise, I can't use your provider for security_label, which is a very nice feature. Thanks for the implementation |
|
Thanks for this, I'm also in this case to handle column based security using PostgreSQL Anonymizer.. @cyrilgdn can you please have a look at this? Thanks a lot for your work |
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.
This resolves a bug where SECURITY LABEL statements on qualified column names (e.g. user.name) did not correctly escape each identifier part individually. Now, names like user.name are properly transformed into "user"."name" to avoid syntax errors with mixed or case-sensitive identifiers.