Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Postgres - do not lower case column and table names

Answered
Gaëtan User

I don't know if it's only related to the Postgres connector or if the following also happens for other connectors.

When table names and column names are in snakeCase/PascalCase in the sources, the connector lower cases the names in the destination, making them very difficult to read.

Example:

A column named in the source (Postgres)

CreatedAt

becomes in my destination (Redshift)

createdat

This also applies to table names;

UserTestRecommendations

becomes

usertestrecommendations


It would be much better if the connector would either keep the source's case style or use the snake case style by convention.

 

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Kevin Kim Fivetranner

    Hi,

    Thanks for your feedback. Our naming convention policy does lowercase all schema and column names automatically, you can find details of this in our documentation here: https://fivetran.com/docs/getting-started/core-concepts#namingconventions

    Your feedback on keeping the original casings and string values is something we have certainly heard from other customers. I will be sure to take this feedback to our teams to investigate how to keep original casings as much as possible.

    One reason this is a challenging problem is that different destinations often have different naming policies! For example, Snowflake is fully case sensitive, however Redshift is case insensitive, so we would need to design a solution that works across all destinations.

    Thank you for sharing this, as this information helps us understand the use cases our users have. While this improvement is not currently planned, I will share this with the team as a possible improvement for our users.