Pain point · Self-hosting & upgrades · Causes churn
Separate Hasura instance needed per database when schemas share table names
2 source threads · first seen 2019-12 · last seen 2021-06
Summary
A team with many databases that share an identical table structure must run one Hasura instance per database because table names conflict and cannot be renamed, adding maintenance and routing work.
- Affects
- team exposing a public API over SQL Server databases for enterprise customers
- Workaround
- Run one instance per database, or add a routing proxy in front
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“As it stands, we have to maintain a separate Hasura instance for each of these databases as the table names conflict”
“it's populating them with the tenant name (e.g client1_users, should just be users)”