-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optional database schema prefix #5394
Labels
Comments
This is highly related to #3606 |
I would love being able to prefix hasura schema names... same situation as @ludovicc |
Same situation here! It would be great to have such way to work with different schemas. |
Have the same problem |
One idea to solve this is being discussed in #3606 Would love all you feedback there! |
Closing this in favour of #3606 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
The text was updated successfully, but these errors were encountered: