-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
Description
Version Information
Server Version: v2.17.1
CLI Version (for CLI related issue): v2.17.1
Environment
EE — since we're using a HASURA_GRAPHQL_PRO_KEY env var
What is the current behaviour?
We've set a global naming convention to be graphql-default with this env var:
HASURA_GRAPHQL_DEFAULT_NAMING_CONVENTION: graphql-default
However, when we're connecting to a SQLServer / MSSQL database, due to their case sensitivity, we have to use hasura-default in order to override the globally-defined behavior.
The UI currently makes this difficult.
What is the expected behaviour?
Either the UI should default to and only allow hasura-default for MSSQL, or it should be automatically set in metadata.
How to reproduce the issue?
- Introduce a new DB connection to a MSSQL instance
- Try to set the DB's naming convention.