Why Did SQLJ Die?
Every now and then, SQLJ pops up somewhere, mostly in a very dusty/enterprisey or in an academic context.
If you give SQLJ some thought, though, it isn’t such a bad idea. It is:
- An ANSI and ISO standard
- Part of the SQL standard
- Quite easy to understand
- Quite a powerful extension to JDBC
Let’s assume that you have already decided to embed your SQL (as opposed to externalising it through a templating mechanism, hiding it with an ORM, or with stored procedures). Here are a couple of reasons why SQLJ is not an optimal solution for embedding SQL:
While Pro*C worked well for C and C++ in the 90s, Java really took off in the early 2000’s. With Java, there were also an increasing number of powerful IDEs such as Eclipse, NetBeans, JBuilder, and others. Java preprocessors and IDEs have never become friends, though, as parsing one language is hard enough. Parsing (and providing tooling) for two languages is much harder.
In fact, SQLJ made the surrounding Java code type-unsafe as IDEs and compilers couldn’t process .sqlj files before they had been pre-processed.
There was a time when people started thinking that SQL itself was going to be dead. First, they did so with the advent of ORMs, then they did so with the advent of NoSQL. People thought that the DBA is dead. Again.
Well, this has been proven to be wrong a couple of times, but certainly not because of SQLJ.
In the late 2000’s, there had now been typesafe alternatives to SQLJ, such as jOOQ in Java, or LINQ-to.SQL in .NET, which leverage IDE features such as syntax autocompletion. By being internal domain-specific languages / query DSLs, these APIs not only bring typesafety to embedded SQL, but they also allow for dynamic SQL building, which SQLJ doesn’t support.
While embedding SQL into other languages is a useful thing, SQLJ never solved this problem adequately. Hence, R.I.P., SQLJ
Everytime you read an excellent article and don't share it, god kills a kitten!
- 1,302,649 hits
- Choose boring technology buff.ly/1DrRj6A 2 hours ago
- A late congratulations to Michael Stonebraker for winning the well-deserved Turing Award: buff.ly/1EzrO4T 5 hours ago
Get Back in Control of Your SQL
Top Posts & Pages
- Don't be Fooled by Generics and Backwards-Compatibility. Use Generic Generic Types
- 10 More Common Mistakes Java Developers Make when Writing SQL
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- Add Some Entropy to Your JVM
- 10 Subtle Best Practices when Coding Java
- 10 Things You Didn't Know About Java
- Java 8 Friday: 10 Subtle Mistakes When Using the Streams API
- 10 Common Mistakes Java Developers Make when Writing SQL
- Do You Really Understand SQL's GROUP BY and HAVING clauses?
- Java Auto-Unboxing Gotcha. Beware!
- Don’t be Fooled by Generics and Backwards-Compatibility. Use Generic Generic Types April 1, 2015
- Hack up a Simple JDBC ResultSet Cache Using jOOQ’s MockDataProvider March 26, 2015
- jOOQ vs. Hibernate: When to Choose Which March 24, 2015
- One Year After Java 8’s Release, IDEs and Compilers are not Fully Ready Yet March 18, 2015
- The 10 Things Everyone does Wrong when Committing Pull Requests March 16, 2015
- 10 Java Articles Everyone Must Read March 13, 2015
- 3 Reasons why It’s Okay to Stick with SQL March 12, 2015
- Integrating jOOQ with Grails Featuring the UWS-jOOQ Plugin March 10, 2015
- Yak Shaving is a Good Way to Improve an API March 9, 2015
- The Java Legacy is Constantly Growing March 5, 2015