Skip to content
This repository has been archived by the owner on Jan 28, 2021. It is now read-only.

ORDER BY does not fail on non-existent columns #813

Closed
Hydrocharged opened this issue Sep 5, 2019 · 1 comment · Fixed by #818
Closed

ORDER BY does not fail on non-existent columns #813

Hydrocharged opened this issue Sep 5, 2019 · 1 comment · Fixed by #818
Assignees
Labels
bug Something isn't working

Comments

@Hydrocharged
Copy link
Contributor

Hydrocharged commented Sep 5, 2019

ORDER BY does not throw an error if a non-existent column is supplied. One would expect similar behavior to supplying a non-existent column to GROUP BY, which results in the following error:

ErrColumnNotFound = errors.NewKind("column %q could not be found in any table in scope")

Attached is a patch that may be applied to the latest as of the time of this issue filing. This adds a few lines to the TestOrderByGroupBy test that checks for an error to be returned when a non-existent column is supplied.

patch.txt

@erizocosmico erizocosmico added the bug Something isn't working label Sep 6, 2019
@erizocosmico
Copy link
Contributor

Thank you for reporting this issue, we'll take a look as soon as we can.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants