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
That was awesome, right? Share it with your friends!
- 880,896 hits
- Super excited to announce #jOOQ 3.5.0 with tons of new features! groups.google.com/forum/#!topic/… #DataTypes #StoredProcedures #Informix #DDL #UNION 2 days ago
- Within 2015, #jOOQ will be more popular than #EclipseLink: buff.ly/1xVgPfU. Next goal: Become more popular than #Hibernate 2 days ago
Get Back in Control of Your SQL
Top Posts & Pages
- Add Some Entropy to Your JVM
- 10 Subtle Best Practices when Coding Java
- 10 Common Mistakes Java Developers Make when Writing SQL
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- The 10 Most Popular DB Engines (SQL and NoSQL)
- Java Auto-Unboxing Gotcha. Beware!
- 10 More Common Mistakes Java Developers Make when Writing SQL
- 10 Things You Didn't Know About Java
- Use MySQL's Strict Mode on all new Projects!
- Java 8 Friday Goodies: Map Enhancements
- Use MySQL’s Strict Mode on all new Projects! November 20, 2014
- jOOQ Tip of the Day: Discover all Primary Keys November 14, 2014
- Don’t Migrate to MariaDB just yet. MySQL is Back! November 12, 2014
- Have You Ever Wondered About the Difference Between NOT NULL and DEFAULT? November 11, 2014
- Don’t Miss out on Awesome SQL Power with FIRST_VALUE(), LAST_VALUE(), LEAD(), and LAG() November 7, 2014
- Painless Access from Java to PL/SQL Procedures with jOOQ November 4, 2014
- 10 Things You Didn’t Know About Java November 3, 2014
- A RESTful JDBC HTTP Server built on top of jOOQ October 31, 2014
- Let’s Stream a Map in Java 8 with jOOλ October 23, 2014
- Stop Claiming that you’re Using a Schemaless Database October 20, 2014