You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're looking to use Hasura for a multi-tenant application, where each tenant is isolated by schema in PostgreSQL.
Each tenant has their own subdomain, and the schemas are identical for each tenant. I noticed that in Hasura, the schema is prepended to the table name, so something like "client" becomes _client.
What's the best way to handle tenancy in this case? Ideally, we could pass a claim in the JWT that would be respected, or could set a default schema for a role and pass the role dynamically.
From what I can tell, we don't have the option to do anything like that and would have to rewrite the query in some form or fashion, perhaps using Apollo Link, but I'd really prefer to avoid that if we can.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're looking to use Hasura for a multi-tenant application, where each tenant is isolated by schema in PostgreSQL.
Each tenant has their own subdomain, and the schemas are identical for each tenant. I noticed that in Hasura, the schema is prepended to the table name, so something like "client" becomes _client.
What's the best way to handle tenancy in this case? Ideally, we could pass a claim in the JWT that would be respected, or could set a default schema for a role and pass the role dynamically.
#3606
From what I can tell, we don't have the option to do anything like that and would have to rewrite the query in some form or fashion, perhaps using Apollo Link, but I'd really prefer to avoid that if we can.
Beta Was this translation helpful? Give feedback.
All reactions