Optional database schema prefix

[ludovicc]

Hello,

In my company, we use Postgres schemas to segregate data by customer. The table structure is the same for different schemas, but data in one schema is always linked to a customer and cannot be accessed from another customer.

This architecture makes compliance and multi-tenancy easier to manage, but with Hasura we have what looks like many different schemas but differ only by the schema prefix (cust1_tableA, cust2_tableA...). Ideally from GraphQL only tableA should be used when there are no ambiguities.

In Postgres, search_path is used to remove the need to specify the schema on each statement, can a similar functionality be added to Hasura, for example as a prefix in the url (/cust1/v1/graphql) or as x-hasura-search-path=cust1 header?

This issue is related to:

• Feature Request: Support graphql schema export by postgres schemas Feature Request: Support graphql schema export by postgres schemas #2747
• rfc: renaming types and fields rfc: renaming types and fields for remote schemas #4821

[tirumaraiselvan]

This is highly related to #3606

[jflambert]

I would love being able to prefix hasura schema names... same situation as @ludovicc

[MarcusBondezan]

Same situation here! It would be great to have such way to work with different schemas.

[nezzard]

Have the same problem

[tirumaraiselvan]

One idea to solve this is being discussed in #3606

Would love all you feedback there!

[tirumaraiselvan]

Closing this in favour of #3606