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!
- 728,571 hits
- RT @sqlkris: Avoid these common mistakes and your SQL girlfriend will marry you! :/ #essentialsql slidesha.re/WJ8FJr 13 hours ago
- Our controversial article about why you shouldn't use layered architectures is discussed on the clojure user group: buff.ly/1slXYoN 15 hours ago
Get Back in Control of Your SQL
Top Posts & Pages
- Why You Should NOT Implement Layered Architectures
- 10 Subtle Best Practices when Coding Java
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- 10 Common Mistakes Java Developers Make when Writing SQL
- The 10 Most Popular DB Engines (SQL and NoSQL)
- Does Java 8 Still Need LINQ? Or is it Better than LINQ?
- 10 More Common Mistakes Java Developers Make when Writing SQL
- Top 10 Very Very VERY Important Topics to Discuss
- Easy Mocking of Your Database
- Java 8 Friday: No More Need for ORMs
- This Just In!! Updated Silly Keyword Metrics September 17, 2014
- This is the Final Discussion! September 15, 2014
- Why You Should NOT Implement Layered Architectures September 12, 2014
- When the Java 8 Streams API is not Enough September 10, 2014
- Look no Further! The Final Answer to “Where to Put Generated Code?” September 8, 2014
- Stop Manually Importing Your ERD Export into jOOQ September 5, 2014
- Awesome SQL Trick: Constraints on Views September 2, 2014
- jOOQ Newsletter: September 02, 2014 – Do You Really Need Support? September 2, 2014
- PL/SQL backtraces for debugging August 29, 2014
- Integrating jOOQ with PostgreSQL: Partitioning August 26, 2014