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
It's easy enough to standardize on the convention by splitting PostgresColumn into its own file.
Describe alternatives you've considered
It won't affect the functionality of the dbt-postgres adapter if it stays as-is. But it also won't affect the functionality if it is moved.
Who will this benefit?
It is easier to find the definition or compare definitions across adapters if things are in the standard locations. This is helpful for anyone inspecting the code, including adapter maintainers outside of dbt-postgres that want to compare/contrast implementation details.
It will also allow for slightly more standardization of this file:
github-actionsbot
changed the title
[Feature] Stand-alone Python module for PostgresColumn
[CT-1940] [Feature] Stand-alone Python module for PostgresColumn
Jan 27, 2023
See also: dbt-labs/dbt-redshift#290
Is this your first time submitting a feature request?
Describe the feature
There is a stand-alone
{adapter}/column.py
module almost everywhere:The two exceptions are:
It's easy enough to standardize on the convention by splitting
PostgresColumn
into its own file.Describe alternatives you've considered
It won't affect the functionality of the dbt-postgres adapter if it stays as-is. But it also won't affect the functionality if it is moved.
Who will this benefit?
It is easier to find the definition or compare definitions across adapters if things are in the standard locations. This is helpful for anyone inspecting the code, including adapter maintainers outside of dbt-postgres that want to compare/contrast implementation details.
It will also allow for slightly more standardization of this file:
dbt-core/plugins/postgres/dbt/adapters/postgres/__init__.py
Line 4 in c653330
Are you interested in contributing this feature?
Yep 👍
Anything else?
No response
The text was updated successfully, but these errors were encountered: