-
Notifications
You must be signed in to change notification settings - Fork 14
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
Column name specified via AS can't be used in WHERE #46
Comments
I implemented support for referring to columns names set with Using the I see the convenience of being able to reference column aliases in the |
Good question. I have no idea either.
We should all the SQLite authors.
I'm curious
…On Sat, Apr 16, 2022, 05:54 Daniele Nicolodi ***@***.***> wrote:
I implemented support for referring to columns names set with AS in the
WHERE and HAVING clauses in #29
<#29>. However, I am not sure
this is a desirable feature.
Using the AS column names in WHERE and HAVING is not allowed by the SQL
standard and is not supported by PostgreSQL (which is my SQL reference
implementation) see "SELECT list" in
https://www.postgresql.org/docs/current/sql-select.html SQLite supports
this use, but the SQLite author wishes he could remove support for this
***@***.***/msg94070.html
I see the convenience of being able to reference column aliases in the
WHERE and HAVING clause but I wonder if I am missing some good reason not
to support this that can come biting us down the road.
—
Reply to this email directly, view it on GitHub
<#46 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACSBE4ZNQVJRHGVQE772WTVFKE4TANCNFSM5SMN74YA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I didn't realize this was not a standard SQL feature. I'm ok with this request being closed since this is not a standard SQL feature. |
I also wonder why SQL does not support this. It always surprises me when I
write SQL (and I do). Id love to know the rationale
…On Wed, Nov 30, 2022, 21:20 Martin Michlmayr ***@***.***> wrote:
I didn't realize this was not a standard SQL feature. I'm ok with this
request being closed since this is not a standard SQL feature.
—
Reply to this email directly, view it on GitHub
<#46 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACSBE2PTHAKAZRG43CK7Z3WLADPVANCNFSM5SMN74YA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Original report by Martin Michlmayr (Bitbucket: tbm13, GitHub: tbm).
I specify a column name via "AS foo" but then "WHERE foo" says that "foo" is an invalid column. It would be nice if it would recognise the custom column names I make via "AS".
The text was updated successfully, but these errors were encountered: