Fix!: Improve handling of the --where
option in table_diff
#2975
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this change, running
sqlmesh table_diff
with something like--where "foo = 'bar'"
would throw an error like:This was because the where clause was injected verbatim without automatically qualifying the columns. The user had to know that table_diff used a subselect internally and supply
--where "s.foo = 'bar' and t.foo = 'bar'"
in order to get this to work.This PR refactors the generated table_diff query to use CTE's to build the source / target / stats datasets so the
--where
clause can still be injected verbatim but it's now scoped to each dataset so there are no more ambiguous column references