Live data from Hacker News

SQL is now 50 What is coming next to the query language?

coderoasis.com

21–22 of 22 posts

Re: SQL is now 50 What is coming next to the query language?

#21

This article is pure garbage. Here are some of its sins: * It says that SQL was introduced in 1974 and could be used for web applications (the web was invented in 1989). * Then it calls AI “Artistical Intelligence”. * And it never even talks about the topic of its title: what’s next for SQL.

It also claims that SQL is hard to learn, while in my experience it is quite easily picked up by many, including less tech-savy.

It is hard to master, but that goes for pretty much any skill.

Re: SQL is now 50 What is coming next to the query language?

#22

Earlier quoted context omitted.

Absolutely not. For example, there is literally nothing at all in common between a Postgres query and a Clickhouse query except some very basic surface-level syntax. (And even then lots of things are incompatible, e.g., count(*) vs count())

You don't have to write `count()` in ClickHouse - `count(*)` is also ok. ... while `count()` makes more sense from the engineering perspective: it is an aggregate function that takes zero number of arguments. I personally prefer `count()`, but when my friends write `count(*)` or even `COUNT(*)`, they are still my friends.

The count() invocation is a small but excellent feature in ClickHouse. There are many other great dialect extensions. -If combinators are another great example. [0] SQL would be a better language if there had been more innovation focused on code usability over its long history.

[0] https://clickhouse.com/docs/en/sql-reference/aggregate-funct...

Post reply on HN