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
I would love the output from compare_all_columns to be applicable to multiple columns across two queries. Its like compare_column_values, but supporting multiple columns and thus using the output format from compare_all_columns.
Happy to consider alternative naming for macro and args, but below should give clear indication on what I would like.
Describe alternatives you've considered
Alternative is to use all of these individually.
Additional context
I see that compare_all_columns depends on using column definitions defined in the relations, so that means we should just pass them along.
This is useful for comparing source and target queries in detail in one go, without relations defined and without comparing all columns, or repeating many times for a single specific column.
Are you interested in contributing this feature?
Yes, I would consider contributing only if it is deemed useful and likely to be merged into the lib.
Great lib, and of course it's simple enough for me to do in my own codebase, but also happy to enrich this lib for others if there is a general desire.
The text was updated successfully, but these errors were encountered:
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.
Describe the feature
I would love the output from
compare_all_columns
to be applicable to multiple columns across two queries. Its likecompare_column_values
, but supporting multiple columns and thus using the output format fromcompare_all_columns
.Happy to consider alternative naming for macro and args, but below should give clear indication on what I would like.
Describe alternatives you've considered
Alternative is to use all of these individually.
Additional context
I see that
compare_all_columns
depends on using column definitions defined in the relations, so that means we should just pass them along.Example summary
Summary output
Example verbose
Detailed response
Who will this benefit?
This is useful for comparing source and target queries in detail in one go, without relations defined and without comparing all columns, or repeating many times for a single specific column.
Are you interested in contributing this feature?
Yes, I would consider contributing only if it is deemed useful and likely to be merged into the lib.
Great lib, and of course it's simple enough for me to do in my own codebase, but also happy to enrich this lib for others if there is a general desire.
The text was updated successfully, but these errors were encountered: