chore: set search path in migration - #2410
Open
staaldraad wants to merge 6 commits into
Open
Conversation
imor
reviewed
Sep 3, 2026
imor
approved these changes
Sep 3, 2026
imor
left a comment
imor
left a comment
Contributor
There was a problem hiding this comment.
LGTM, graphql_public.graphql no longer set search_path to empty.
utkarash2991
approved these changes
Sep 3, 2026
staaldraad
force-pushed
the
etienne/prodsec-248
branch
from
September 3, 2026 08:55
cb5ea9a to
88de835
Compare
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
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.
A number of Supabase owned functions are created without a search_path. This breaks from best practice and can lead to unintended side-effects if the current_user search_path changes.