fix: Fix notifiation authorization check on pg13- #234
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
Postgres 13 or lower don't have predefined roles, so we call unnest on an empty
python array which is emitted as '{}'. This is ambiguous for postgres so we
need to explicitly cast the value as an array of text, which works for both an
empty array and a non empty array (which is emitted as ARRAY[...]).
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.
Postgres 13 or lower don't have predefined roles, so we call unnest on an empty python array which is emitted as '{}'. This is ambiguous for postgres so we need to explicitly cast the value as an array of text, which works for both an empty array and a non empty array (which is emitted as ARRAY[...]).