Skip to content
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

Names are automatically casted to lower-case, regardless of capitalisation in database #112

Closed
JoshuaClercx opened this issue Jan 16, 2023 · 4 comments · Fixed by #168
Closed
Labels
bug Something isn't working Stale

Comments

@JoshuaClercx
Copy link

Describe the bug

Source, schema, database, table, and column names are automatically casted to lowercase when generating source yaml files, regardless of the casing of the name in the actual database.

Steps to reproduce

Generate a source yaml file from any database that contains capitalisation in the names of any of the aforementioned.

Expected results

Conservation of capitalisation in the yaml file as it is in the database.

Actual results

All-lowercase names.

Are you interested in contributing the fix?

Yes, as it would just require minor adjustments of a few lines.

@JoshuaClercx JoshuaClercx added the bug Something isn't working label Jan 16, 2023
@charmiraval
Copy link

This will be really helpful in case of different standards for ColumnName as per project instead of converting to lowercase.

@yuhouzhou
Copy link

Using the persist_docs configuration to sync the documentation between BigQuery and dbt docs requires matching cases of column names. It makes sense to have the option to keep the original case as in the databases.

@github-actions
Copy link

github-actions bot commented Sep 4, 2023

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

@github-actions github-actions bot added the Stale label Sep 4, 2023
@github-actions
Copy link

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale
Projects
None yet
3 participants