Tirumarai Selvan

@tom-pryor As a workaround, is it possible for you to client-side template all your queries with the schema name?

One idea is to have a default schema per role (default: public). Say, a role called **tenant1** can specify that its default schema is `tenant1` . Then the public schema...

@furlongce @ilijaNL There is a workaround to achieve schema-level tenancy with the "Dynamic DB Resolution" feature we have in[ preview](https://github.com/hasura/graphql-engine/issues/3606#issuecomment-1355855664). You can create "stub" databases corresponding to each schema and...

A view would be the quickest workaround!

Related: https://github.com/hasura/graphql-engine/issues/8259

Related: https://github.com/hasura/graphql-engine/issues/3685

I think `User-Agent` field should be overrideable since it is not a "[Forbidden header name](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent)"

Another use-case > extract the "sub" value from our JWTs and use that to enforce tenant separation

@nihonjinrxs We support the `sqlcommenter` syntax for query tags which is used in GCP Cloud SQL (you need to explicitly set the metadata value): https://hasura.io/docs/latest/observability/query-tags/#formats-of-query-tags

Ah, that's unfortunate. Hasura execution system barely matches the Rails-style comments that GCP supports. Anyway, we will think about it.