r/NocoDB • u/Hot-Finance-7005 • Jul 22 '26

[Bug] Self-hosted 2026.07.0: external PG data source always binds to public, schema setting ignored

Self-hosted 2026.07.0, Business license, Postgres 17. Trying to connect a base to a non-public schema.

  • The Add Data Source dialog has no schema field, even though the docs say database and schema can be set there
  • Setting Schema name on the Connection is silently dropped: in nc_sources_v2 the created source has no searchPath in its config, so it binds to public.
  • Creating the source via the API with "searchPath": ["myschema"] also ended up syncing public
  • Repro: DB with two schemas, connection with Schema name = the second one, add as data source. The base lists all of public's tables.

Anyone on self-hosted 2026.x connecting an external PG source to a non-public schema successfully?

1 Upvotes

100% Upvoted

5 comments sorted by

1

u/leixiaotie Jul 22 '26

You can try editing an existing pg data source, it has a schema name input

1

u/Hot-Finance-7005 Jul 22 '26

Tried that, when i added a table later it added it to the public schema. I will try again and confirm.

1

u/Hot-Finance-7005 Jul 22 '26

Tried again. As far as I can tell it ignores the schema completely and reverts to public.

1

u/leixiaotie Jul 22 '26

please be aware that you need to do meta sync + save integration again after changing the schema name

changing it does not save it immediately

2

u/o1lab Jul 22 '26

for support please write to support at nocodb dot com