Re: The tragedy of SQL

> On Sep 14, 2021, at 11:10 AM, Michael Nolan <htfoot(at)gmail(dot)com> wrote:
>
> I started programming in 1967, and over the last 50+ years I've programmed in more languages than I would want to list. I spent a decade writing in FORTRAN on a GA 18/30 (essentially a clone of the IBM 1130) with limited memory space, so you had to write EFFICIENT code, something that is a bit of a lost art these days. I also spent a decade writing in COBOL.
>
> I've not found many tasks that I couldn't find a way to write in whatever language I had available to write it in. There may be bad (or at least inefficient) languages, but there are lots of bad programmers.

Yep, me too. I would say that SQL has not achieved its design goals yet. The original concept was to write what you want to achieve and have the server figure out the best way to get at it.

What people hate about SQL is that the programmer has to optimize SQL to get acceptable performance. And the optimization is different for every implementation. I think SQL has not hit its stride yet. When the common $1000 server has 1024+ CPUs and 1+TB memory, and SQL implementations have adopted good multithreading architecture with access to 1024+ CPU dedicated AI engines, etc. a lot of the crap associated with performant SQL will go away.

At this point, I think it will be smart to strip out implementation details that have made it into the SQL syntax. There will no longer be a need for it. This will make the SQL language simpler and easier to use, understand, and reason about.

Of course, that might not happen until my grandchildren are retired and in a nursing home. But who knows, stranger things have happened.

Neil
www.fairwindsoft.com