Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

I am no fan of the syntax of SQL, however the authors solution of making SQL more procedural is (imo) correctly identifying an issue but then reaching for the wrong tool to fix it.

When I am authoring SQL, I find the declarative and relational concepts extremely powerful and well suited to the problem I am solving.



I agree with you.

Changing SQL to a description of how you'll get the data would make a query incomprehensible to me.


As long as I am allowed to write keywords in capital case I am fine with the syntax. I kinda like it. It smells like the 70s.


I enjoy how it builds on previous success WITH its use of regex. There is nothing quite LIKE ideas from the 50's haunting you in your sleep.

   SELECT age FROM Customers WHERE Country='Mexico'
Could be written something like:

   table.customers.filter(c=>c.country == "Mexico").age
The filter is kinda ugly, there is this strange assumption there to be only one Mexico in country.

Clearly the most advanced approach is this:

  //customer[country="mexico"]/age
1999!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: