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

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

@Hydrocharged

Description

@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

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy