RD-11280: a schema does not exist
error isn't reported to the user
#468
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.
It should be reported to the user. Note the query is a little peculiar: in place of an alias column name, the person entered a single quoted string (a regular string). With a regular identifier the error doesn't occur.
We already do catch errors due to typos in schema names since a long time, and receive them as "undefined table" (status
42
). When people typeSELECT FROM country.list
. That new error code is seen when someone types this kind of code:Only then it complains of "country" not existing as a schema name, using
3F
.