You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the client 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 the client initially such as:
constclient=PostgrestClient('url',{schema: 'public'});// some where else in the appconst{ data, error }=awaitsupabase.from('table_name','schema_name').select()// orconst{ data, error }=awaitsupabase.rpc('function_name','another_schema_name')
In both cases, if no schema is given, then the default schema from the client is used.
Describe alternatives you've considered
Creating multiple clients (one per schema) seems like the only option but it'd be much easier and cleaner to use the same client.
The text was updated successfully, but these errors were encountered:
Feature request
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 the client 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 the client initially such as:
In both cases, if no schema is given, then the default schema from the client is used.
Describe alternatives you've considered
Creating multiple clients (one per schema) seems like the only option but it'd be much easier and cleaner to use the same client.
The text was updated successfully, but these errors were encountered: