2 ms·
I think your chained, tab-indented from-select structure is the worst idea ever conceived of by mankind, and the only purpose I can think of for it is you want
by cwyers 11y ago
I think your chained, tab-indented from-select structure is the worst idea ever conceived of by mankind, and the only purpose I can think of for it is you want to encourage my carpel-tunnel to flare up again. So much extra verbosity added to the standard SQL of writing that query for no additional clarity. (And you still need the from! Just comment out one line and two columns, it's no harder than commenting out the weird syntax you've come up with.)
Which is not to say that SQL can't be improved upon, but the amount of improvement you'd need to make to make it worth learning a different query language is I think higher than the benefits you can get from improving SQL, especially if you're not going to radically remake it, because being 80% SQL is worse than being 0% SQL because you keep running up against the principle of least surprise not working.
- hacker_9 11y agoHilarious that your argument is your carpel-tunnel - Look at the code again and you'll see it's laid out so the computer can fill in the information for you = less typing. By typing the FROM first, the whole next SELECT statement can be auto added with a single key (perhaps `). Or you can write the SELECT yourself, but only have to type the first char of each column name before the IDE auto completes it. The tab structure shows you at a glance what tables join to what (not uncommon to see this parent-child in XML for example, or you know, any other programming language ever). Your last point is void - just look at C#, Java, C++, Go and so on. All reuse keywords for different purposes. It's not hard to switch context in your head depending on the language.