3 ms·
This specific issue is a problem for humans, not for APIs. I have a very smart SQL IDE with great intellisense, but when I type "SELECT", it can't help me beca
by The_Colonel 3y ago
This specific issue is a problem for humans, not for APIs.
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.
- deepsun 3y agoI usually write "SELECT FROM a" and then "Ctrl-Left-Left" to go back to columns. Starting from FROM would be better of course.
- randomdata 3y agoWhy 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?
- mrguyorama 3y agoAlright, I start typing out "SELECT" in my super smart IDE, how does it know which table to suggest columns from?
- randomdata 3y agoGiven 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.
- The_Colonel 3y agoLooks like my IDE isn't that smart. So I will have to endure the unfriendliness of the SQL towards humans.
- randomdata 3y agoOr 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.