SQL is now 50 What is coming next to the query language?
coderoasis.com
SQL is now 50 What is coming next to the query language?
1–10 of 22 posts
Re: SQL is now 50 What is coming next to the query language?
#2The article does not answer "what comes next?". I was expecting topics like GraphQL and others but article jumps into AI and NLP which are very different discussions rather than standard protocol to access data
Re: SQL is now 50 What is coming next to the query language?
#3It can be 100.
Re: SQL is now 50 What is coming next to the query language?
#4It really is mind boggling, how come the forced bloat did not yet reach SQL. Of course people try very hard to "innovate" (ehm, the proper word would be poison) in this space, by adding more abstractions, confuse things with overly complex solutions or create syntax that just can't be remembered.
So if you have the feeling that you need to elevate yourself above the crowd by complicating things, package it and sell it as an invention, meaning: this is somehow too easy to remember and use, then of course there are myriads of ORMs and the like that bring you this very much needed panacea that is unneeded complexity for your programs. If you feel the need, then just enter the neverending forest and we'll hope you will get lost in it and never return.
Re: SQL is now 50 What is coming next to the query language?
#5The best thing to happen in sql in recent times is snowflake starting to allow an extra comma in the end of the expression list lol. Now I can ask all the DBAs in my life to stop formatting their queries comma first!
Re: SQL is now 50 What is coming next to the query language?
#6I am struggling to find any content in this article -- it seems like it was written by an AI
Re: SQL is now 50 What is coming next to the query language?
#7Is there really anything missing from SQL? I guess adding a few semantic shortcuts like Postgres' SELECT DISTINCT ON (x) are useful.
But otherwise this feels like asking what's coming next for Algebra.
Re: SQL is now 50 What is coming next to the query language?
#8Take a look at the SQL statements your app uses, replace them with your own code, three months later, your code is much larger, harder to understand, and may not even be any faster. I will be happy for SQL to carry on as it is.
Re: SQL is now 50 What is coming next to the query language?
#9Times up. LLMs are uniquely suited to convert data requests to SQL at compile-time. All ORMs will converge on this feature “scan your table layout and generate smarter queries with Knexjs Pro+” - one can see it coming.
My mother raised me as a broke single mother because she could write SQL. I bought a home in my California home town because I could write good SQL and tune my.cnf. I suppose my toddler will never SELECT * FROM.
I wish it weren’t so, but it’s always felt a bit silly, hasn’t it? “Hey Siri, People own many Widgets and belong to one Team” is coming. Why would we want the future of computing not to obscure database operations? Why should our grandchildren care about shards? Let it all die.
Re: SQL is now 50 What is coming next to the query language?
#10I am struggling to find any content in this article -- it seems like it was written by an AI
Only real content I can find is the original SEQUEL paper linked in the article: https://dl.acm.org/doi/10.1145/800296.811515?ref=coderoasis....