-
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
Adding a hasura-default naming convention for MSSQL / SQL Server #9426
Comments
How to reproduce the issue?
Any possible solutions/workarounds you're aware of?It is possible to work around this, but it is a very ugly hack and surfaces a separate bug that should actually be looked into. |
Hi folks, we are acknowledging this issue and this is currently being fixed. |
Closed via 96549b2 |
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 varWhat is the current behaviour?
We've set a global naming convention to be
graphql-default
with this env var: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?
Screenshots or Screencast
Please provide any traces or logs that could help here.
Any possible solutions/workarounds you're aware of?
Keywords
The text was updated successfully, but these errors were encountered: