Shouldn't FROM come before SELECT in SQL? (2011)
stackoverflow.com
Shouldn't FROM come before SELECT in SQL? (2011)
1–10 of 137 posts
Re: Shouldn't FROM come before SELECT in SQL? (2011)
#2When you get 1000 line SQL files or 100s of SQL files, code management pain makes you yearn for FROM ... SELECT ... (three cheers for data build tool!)
Re: Shouldn't FROM come before SELECT in SQL? (2011)
#3[0] https://learn.microsoft.com/en-us/dotnet/csharp/programming-...
Re: Shouldn't FROM come before SELECT in SQL? (2011)
#4https://duckdb.org/2023/08/23/even-friendlier-sql.html#from-...
Re: Shouldn't FROM come before SELECT in SQL? (2011)
#5The link to https://www.lib.umn.edu/collections/special?id=291 is dead, though?
Re: Shouldn't FROM come before SELECT in SQL? (2011)
#6SELECT ... FROM ... is more natural for smaller SQL. When you get 1000 line SQL files or 100s of SQL files, code management pain makes you yearn for FROM ... SELECT ... (three cheers for data build tool!)
Re: Shouldn't FROM come before SELECT in SQL? (2011)
#7Select, insert, update, delete, merge is the first word and says what you are doing.
If the keyword was in the middle of the query somewhere it would be harder to read.
Re: Shouldn't FROM come before SELECT in SQL? (2011)
#8Re: Shouldn't FROM come before SELECT in SQL? (2011)
#9"The syntax is meant to resemble English", obviously. The link to https://www.lib.umn.edu/collections/special?id=291 is dead, though?
The first is much more naturally spoken.
Re: Shouldn't FROM come before SELECT in SQL? (2011)
#10Row-oriented:
FROM table_name
WHERE condition
GROUP BY ...
HAVING ...
ORDER BY ...
SELECT column1, column2, ...;
Columnar: FROM table_name
SELECT column1, column2, ...
ORDER BY ...
WHERE condition
GROUP BY ...
HAVING ...;