-
-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow overriding default schema in from
and rpc
#206
Comments
Hi @osaxma, Thanks for opening this issue! I really like your approach. I think it benefits the supabase-js client library as well to have this feature, so would you mind opening an issue on postgrest-js repo? If they want to implement this feature, let's go through with it on Dart side as well! |
Hi @dshukertjr Here's the feature request: supabase/postgrest-js#318 |
For anyone landing here, the discussion on adding this to the JS SDK has been moved here This feature will be added once the feature lands on JS SDK. |
Hi all, I've just created a PR over at postgrest-js that handles this case: supabase/postgrest-js#441 |
@dshukertjr is this available in flutter already ? |
@rddewan Not yet. |
This feature is now available via |
Is your feature request related to a problem? Please describe.
Currently it's only possible to use a single schema -- i.e. the one passed to
SupabaseClient
upon instantiation.Describe the solution you'd like
In some cases, I would like to run a query or invoke an rpc on a different schema than the one given to
SupabaseClient
such as:In the above example,
schema
should be nullable and if it was not passed then theSupabaseClient.schema
is used.Describe alternatives you've considered
Creating another
SupabaseClient
seems like the only option but it'd be much easier and cleaner to use the same client.Tasks
If you agree with the proposed changes, please let me know and I can carry the following tasks:
rpc
method on postgrest-dart packagefrom
method,rpc
method, and postgrest-dart version on supabase-dart packageThe text was updated successfully, but these errors were encountered: