FeatureFuel
7

Support wildcards in postgrest exposed schemas

Source: supabase/supabase#12270 · opened by @relferreira
Feature request


I'm using Supabase in a multi-tenant way, meaning that every client will have a separate schema. As discussed here:

Supabase only exposes those other schemas through the API only when they are manually added to this list:

![image](

Is your feature request related to a problem? Please describe.


Trying to access another schema besides public and storage using supabase.js or postgrest.js gives the following error:



Describe the solution you'd like

It would be nice to have access to other schemas without needing to include them on the Dashboard manually. Maybe accept a pattern like tenant_*

Describe alternatives you've considered

I tried using postgrest-js but got the same error.


Many thanks for considering my request.

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests