Improve error reporting for missing qualified columns #17397
Merged
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.
When binding qualified columns (e.g.
catalog.schema.table.column
) we have several different methods of binding, e.g.:When binding, we are clever about figuring out which configuration is used to find the "right" one, allowing users to flexibly qualify columns.
When columns are not present, however, this gets more difficult. Currently, we always fall back to assuming the first field is the table (i.e. the qualification is
[table].[column].[fields]
). In this PR, we expand this so that we improve the error message by figuring out which qualifications are possible. For example, if there is a typo in a table name, but[catalog].[schema]
exists in the query - we report an error as if we are bindingcatalog.schema.table.column
. This provides better error messages, e.g.: