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
Today, if two tables are joined and they have shared columns other than the join key, suffixes are automatically appended to disambiguate. For example:
In many data pipelines, overlapping columns are unexpected and cause issues later in the pipeline. (I think this is why most SQL databases throw an error in this case, rather than automatically appending suffixes.) For such cases, it would be nice to have function-level or package-level options to throw an error.
The text was updated successfully, but these errors were encountered:
When I have overlapping columns, when the left and right columns are similar, I suffix all the right columns, like in SQL with prefix.
With that I handle name collisions in joins by avoid them: when an automatic setting (#4028) could be unpredictable or to much complex or with too many warnings or errors I prefer manual settings. :)
Today, if two tables are joined and they have shared columns other than the join key, suffixes are automatically appended to disambiguate. For example:
In many data pipelines, overlapping columns are unexpected and cause issues later in the pipeline. (I think this is why most SQL databases throw an error in this case, rather than automatically appending suffixes.) For such cases, it would be nice to have function-level or package-level options to throw an error.
The text was updated successfully, but these errors were encountered: