Add dynamic schemas on a per-query basis #828
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 supabase/postgrest-js#280
What kind of change does this PR introduce?
Feature
What is the current behavior?
Currently, the supabase client is created and defaults to the
public
schema when no option is supplied:Or, you can supply an alternative schema:
However, this means that all methods/queries for the client are associated to the single schema. Using multiple schemas requires multiple clients, which presents a challenge for auth where all clients need to be authenticated.
See pre-existing issue:
supabase/postgrest-js#280
What is the new behavior?
Extends on behavior added to underlying
PostgrestClient
: supabase/postgrest-js#455The method added to the supabase client allows for dynamic schema selection on a per-query basis.
If a
Database
generic type is supplied, type inference works as expected without additional generics:Additional context
Add any other context or screenshots.