ORDER BY does not fail on non-existent columns

[Hydrocharged]

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]

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