Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RD-11280: a schema does not exist error isn't reported to the user #468

Merged
merged 2 commits into from
Aug 1, 2024

Conversation

bgaidioz
Copy link
Collaborator

@bgaidioz bgaidioz commented Jul 24, 2024

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 type SELECT FROM country.list. That new error code is seen when someone types this kind of code:

SELECT
 airport_id,
 city,
 country.name 'cname' -- <== the alias 'cname' is entered with quotes, as a string

Only then it complains of "country" not existing as a schema name, using 3F.

@bgaidioz bgaidioz changed the title RD-11280: Typo in query triggers a schema does not exist error RD-11280: a schema does not exist error isn't reported to the user Jul 24, 2024
@bgaidioz bgaidioz merged commit 5d81a44 into main Aug 1, 2024
6 checks passed
@bgaidioz bgaidioz deleted the RD-11280-sql-schema-does-not-exist branch August 1, 2024 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants