# Connecting to Supabase PostgreSQL schema other than public

**URL:** <https://community.weweb.io/t/connecting-to-supabase-postgresql-schema-other-than-public/16817>\
**Category:** Ask us anything\
**Tags:** supabase\
**Created:** [February 25, 2025, 2:58am UTC](https://community.weweb.io/t/connecting-to-supabase-postgresql-schema-other-than-public/16817 "2025-02-25T02:58:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Perry](https://avatars.discourse-cdn.com/v4/letter/p/b4bc9f/32.png) [@Perry](https://community.weweb.io/u/Perry)\
**Post date:** [February 25, 2025, 2:58am UTC](https://community.weweb.io/t/connecting-to-supabase-postgresql-schema-other-than-public/16817/1 "2025-02-25T02:58:32Z")

</div>

I have a Supabase PostgreSQL database with multiple schemas that contain tables that I want to connect to from Weweb. I reviewed a similar post from January 2023 that basically indicated this was not currently possible.  
Has there been any advancements made that will allow connecting to non-public schemas in Supabase PostgreSQL database from Weweb?

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [February 25, 2025, 6:32am UTC](https://community.weweb.io/t/connecting-to-supabase-postgresql-schema-other-than-public/16817/2 "2025-02-25T06:32:41Z")

</div>

Not possible still, only maybe with a custom script.

---

<div class="post-metadata">

**Author:** ![Perry](https://avatars.discourse-cdn.com/v4/letter/p/b4bc9f/32.png) [@Perry](https://community.weweb.io/u/Perry)\
**Post date:** [February 25, 2025, 11:04am UTC](https://community.weweb.io/t/connecting-to-supabase-postgresql-schema-other-than-public/16817/3 "2025-02-25T11:04:05Z")

</div>

Thank you

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [July 8, 2025, 9:25am UTC](https://community.weweb.io/t/connecting-to-supabase-postgresql-schema-other-than-public/16817/4 "2025-07-08T09:25:41Z")

</div>

@Alexis I found that Supabase now allows [Using Custom Schemas | Supabase Docs](https://supabase.com/docs/guides/api/using-custom-schemas), it might be interesting to have this in the Supabase plugin, I heard you guys are re-vamping it a little.

---

<div class="post-metadata">

**Author:** ![gilsonricardomr](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/gilsonricardomr/32/6404_2.png) [@gilsonricardomr](https://community.weweb.io/u/gilsonricardomr)\
**Post date:** [August 26, 2025, 8:41pm UTC](https://community.weweb.io/t/connecting-to-supabase-postgresql-schema-other-than-public/16817/5 "2025-08-26T20:41:06Z")

</div>

Hey Perry, I ran into the exact same issue recently and the most reasonable solution I found was to create **views in the `public` schema** that point to the tables in your additional Supabase schema.

That way, WeWeb can interact with them as if they were regular tables in `public`.

For example, you can do this for each table you need:

create or replace view public.YOUR-schema\_YOUR-table as  
select \* from your\_schema.YOUR-schema\_YOUR-table;

After that, you’ll be able to query `public.schema_table` from WeWeb without worrying about schema limitations.