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!
- 1,173,598 hits
- RT @UWS_LTD: Got our second #Grails #plugin officially released, integrating #jOOQ library into any Grails development process: https://t.… 7 hours ago
- Time to learn some serious Oracle / SQL Server SQL: The PIVOT clause! "How to use SQL PIVOT to Compare Two Tables" buff.ly/1E2WJpo 8 hours ago
Get Back in Control of Your SQL
Top Posts & Pages
- 10 Common Mistakes Java Developers Make when Writing SQL
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- 10 More Common Mistakes Java Developers Make when Writing SQL
- 10 Subtle Best Practices when Coding Java
- Java 8 Friday: 10 Subtle Mistakes When Using the Streams API
- The 10 Most Popular DB Engines (SQL and NoSQL)
- Java 8 Friday Goodies: Map Enhancements
- Does Java 8 Still Need LINQ? Or is it Better than LINQ?
- Do You Really Understand SQL's GROUP BY and HAVING clauses?
- A Lesser-Known Java 8 Feature: Generalized Target-Type Inference
- How to use SQL PIVOT to Compare Two Tables in Your Database February 26, 2015
- How to Extract a Date Part in SQL February 25, 2015
- jOOQ vs. Slick – Pros and Cons of Each Approach February 24, 2015
- Thou Shalt Not Name Thy Method “Equals” February 18, 2015
- jOOQ Tuesdays: Raoul-Gabriel Urma Explores What Java 8 and English have in Common February 17, 2015
- 10 SQL Articles Everyone Must Read February 13, 2015
- “NoSQL Injection” – What 40000 Unsecured MongoDB Databases Mean for our Industry February 12, 2015
- Top 10 Easy Performance Optimisations in Java February 5, 2015
- Still Using Windows 3.1? So why stick to SQL-92? February 3, 2015
- Top 5 Use-Cases For Nested Types February 2, 2015