Re:Shouldn't FROM come before SELECT in SQL? (2011)
by randomdata on Thursday January 25, 2024 @03:04PM
(#39134439)
Why is a very smart SQL IDE not able to work around that limitation with smart UI/UX? I can see why baby's first SQL IDE would benefit from the language being amenable to IDEs, but a very smart one should be able to take things further, no?
Re:Shouldn't FROM come before SELECT in SQL? (2011)
by mrguyorama on Thursday January 25, 2024 @04:29PM
(#39135588)
Alright, I start typing out "SELECT" in my super smart IDE, how does it know which table to suggest columns from?
Re:Shouldn't FROM come before SELECT in SQL? (2011)
by randomdata on Thursday January 25, 2024 @04:50PM
(#39135867)
Given that it is a very smart IDE, the column suggestion UI integrates table selection in a smart way. Once the IDE knows which table(s) you are referencing, it automatically fills in the FROM clause for you.
Re:Shouldn't FROM come before SELECT in SQL? (2011)
by The_Colonel on Friday January 26, 2024 @04:00PM
(#39148256)
Looks like my IDE isn't that smart. So I will have to endure the unfriendliness of the SQL towards humans.
Re:Shouldn't FROM come before SELECT in SQL? (2011)
by randomdata on Friday January 26, 2024 @05:08PM
(#39149294)
Or just use a better language. SQL was designed for non-technical people, using statements that resemble the English they already know. It was not designed for tech-minded people who are able to grasp higher level technical concepts.
I have a very smart SQL IDE with great intellisense, but when I type "SELECT", it can't help me because it has no idea what I want. Being able to type "FROM table SELECT" would be way friendlier for humans, because IDEs could offer me immediately columns I'm very likely interested in.