I have an existing Postgres database I want to use the Directus Data Studio with and this existing database has multiple schemas, including a few instances where the same table name exists in multiple schemas (example would be a “users” table in “public” schema and in “projects” schema where the projects.users table configures project specific roles for users from public.users).
I looked through GitHub, your roadmap, and here, and found a few GitHub discussions that are a few years old which describe usingDB_SEARCH_PATH as a possible approach to using multiple schemas. However I don’t think that will work in my scenario since calling the users table unqualified (without schema specified) would be ambiguous.
I want to check 2 things:
- Is
DB_SEARCH_PATHthe only potential approach for this right now, or are there any other viable approaches I can try? - If the above is a yes, is there any active plans to add more full support (such as via adding the schema to table references in Directus initiated queries) for this in the future? If not, can I add this proposal directly to your roadmap page or is there a more preferred way to propose this?