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
The dbt compilation result: SELECT * FROM "101_supplier"."core"."supplier"
What I expected: SELECT * FROM [101_supplier].[core].[supplier]
Question:
Is there a way to configure the quoting for database, schema and identifier with square brackets. Or this issue a topic for the dbt core team?
Additional context
I found a core issue with similar problems: link
The text was updated successfully, but these errors were encountered:
The double quotes work fine in MS SQL. Did you try running the query? It works fine with tables that start with numbers. I don't have servers named like that to try.
I think this issue can be closed as 'by design'.
DBT handles database and table names beginning with numbers or contains spaces (ack!).
Sql Server databases have Quoted Identifiers set to False by default but most drivers, including the Sql Server ODBC driver, set Quoted Identifiers are on by default, which is the ANSI standard. If OP is having issues with quoted identifiers it might be the driver he is using.
Issue 2986 referenced by OP is simply cleaning up terminology that probably evolved during the organic development of the project.
This assumes the DBT configuration has quoting set to true (default).
If it is set to false then tables beginning with numbers or contains spaces will fail.
The quoting for msft sql not working. Dbt use double quotes when the config quoting is turned on but ms sql or tsql use square brackets.
I need quoting for databases and table. Our table or database prefix is sometimes a number like
101_Customers
.Example:
dbt config:
The dbt compilation result:
SELECT * FROM "101_supplier"."core"."supplier"
What I expected:
SELECT * FROM [101_supplier].[core].[supplier]
Question:
Is there a way to configure the quoting for database, schema and identifier with square brackets. Or this issue a topic for the dbt core team?
Additional context
I found a core issue with similar problems: link
The text was updated successfully, but these errors were encountered: