Modern SQL: Inaugural Post
Modern SQL: Inaugural Post
I've just launched my new website, Modern SQL. So what is Modern SQL about? Yet another SQL reference? Absolutely not. Modern SQL is different.
Join the DZone community and get the full member experience.Join For Free
RavenDB vs MongoDB: Which is Better? This White Paper compares the two leading NoSQL Document Databases on 9 features to find out which is the best solution for your next project.
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 the following 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 definitely enough references out there. And they all suffer from the same issues:
- They hardly cover more than entry-level SQL-92. Some tutorials don't even mention that they describe a proprietary dialect.
- 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 covers SQL:2011—the current release of the ISO SQL standard. But it adheres to the fact that many databases are developed against elder releases or only support a subset of the standard.
- 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 older) 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. Go here if you can't click a feature in the image above.
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.
Published at DZone with permission of Markus Winand , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.