Modern SQL: Inaugural Post
I've just launched my new website modern-sql.com. It's very small right now—just six content pages—but it will grow over next month and years and might eventually become a book like Use-The-Inde-Luke.com did. So I though I'd better get you on board right now so you can grow as the site grows.
So what is modern SQL about? Yet another SQL reference? Absolutely not. There are definitively enough references out there. And they all suffer from the same issues:
The examples just show the syntax but not how to solve real-world problems.
They don't document the availability of the features amongst different database products.
No question, the latter ones are a consequence of the first one. However, modern SQL is different:
modern SQL shows how to use the most recent SQL features to solve real world problems. It also provides “conforming alternatives” as a way to solve the same problem using other (often elder) standard methods. If necessary and possible it will also show “proprietary alternatives.”
Note that there is a hierarchy: the recommended (most idiomatic) approach is shown first, standard conforming alternatives next and proprietary alternatives last but only if inevitable.
modern SQL documents the availability of the features amongst six SQL databases (the example is about
Go here if you don't see an image above.
Click on a feature (e.g., “valid where
select is valid”) to see how the availability of the features has evolved.
There you can see that SQLite just recently started to accept
select is valid. The timeline view also documents the last checked version for those databases that don't support a feature.
Inevitably, modern SQL will become both: an homage to the SQL standard and a rant about its poor adaptation. The availability documentation and the above mentioned alternative approaches (conforming or proprietary) are there to keep the “rant” a productive one. Look at the “
from” use-case to get the idea.