We have an existing database that has a lot of data in a non-public Schema. I can’t seem to figure out how to access any of that data, I can only see the Public schema. Can anyone help. Alternately, is there source code for the Supabase Plugin where I could just tweak a few lines?
Hey there,
Did you try to create a View in SupaBase ?
I think it can access any Schema (at least I did it for Users), and you should get it okay in WeWeb then.
The only thing I didn’t crack just yet is how to secure a view. It’s not the same as for a Table with RLS / Policies.
Have a nice day.
Matth
Yeah, we are highly reliant on RLS, so that approach doesn’t quite work.
Hello,
I am also very interested to know if there is a way to access data from another schema as we are designing a multi tenant app.
I can’t seem to find a way to do it right now, is it going to happen one day?
As of now, the only solution I can find is to have a proxy in between Supabase and WeWeb that will reroute to the correct schema using some kind of data in the request.
Me too, can’t find a solution to access other schema’s. Any Solution?
You guys might want to check this one out. Not sure if it will help, but might be a problem of the schemas not being even exposed.
Thank you for the suggestion. Already tried that solution, and it did not make a difference in what tables where exposed to weweb.
I think weweb hits only the public schema by design, might be an another suggestion for @Alexis.
For now what you could do is use a little code and if you exposed the supabase schema via the sql query, you can use their js sdk to get values from your other schemas. It’s crazy simple. You could even build a formula that would fetch the data once in nocode to then use it in a nocode fashion
If you want to work with data in other Supabase schemas, Comnoco can do this and WeWeb can then speak to Comnoco via rest API. I’d be happy to show you how to do this and give you beta access…
In this case you could think of Comnoco as a no code alternative to Supabase edge functions.
With the recent changes in supabase that has been released in Januar, is there any news regarding accessing other schema’s than the public ?
Not possible in nocode at the moment. But I’m looking at this hidden feature implemented some months ago on supabase side. There is no documentation about it but it seems like it has been merged.
I will check if we can allow you to select a custom schema at the action/collection level.
Nevermind, I noticed it’s a Supabase fix.
Have there been any changes regarding this? Can WeWeb access non-public schemas, or is it limited to only the public schema?
My backend is already configured with multiple schemas. However, if accessing non-public schemas through WeWeb isn’t possible, I’ll transfer all of them to the public schema.
I would also be interested to know if supabase non-public schemas are available now?
@Jean I asked again here Supabase Plugin Custom Schema