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!
- 670,759 hits
- Speaking of #OFFSET pagination. Are you aware of its alternative, the much faster #KEYSET pagination? buff.ly/1ppNN6L 1 day ago
- RT @javacodegeeks: Integrating #JOOQ with #PostgreSQL: Partitioning - #SoftwareDevelopment #Databases goo.gl/Bv6QTh 1 day ago
Get Back in Control of Your SQL
Top Posts & Pages
- Stop Trying to Emulate SQL OFFSET Pagination with Your In-House DB Framework!
- The 10 Most Popular DB Engines (SQL and NoSQL)
- 10 Subtle Best Practices when Coding Java
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- Does Java 8 Still Need LINQ? Or is it Better than LINQ?
- 10 Common Mistakes Java Developers Make when Writing SQL
- Using SQL Injection Vulnerabilities to Dump Your Database
- Faster SQL Pagination with Keysets, Continued
- 10 More Common Mistakes Java Developers Make when Writing SQL
- PL/SQL backtraces for debugging
- PL/SQL backtraces for debugging August 29, 2014
- Integrating jOOQ with PostgreSQL: Partitioning August 26, 2014
- All You Ever Need to Know About Recursive SQL August 18, 2014
- jOOQ Newsletter: August 15, 2014 – jOOQ 3.5 Outlook August 15, 2014
- A Wonderful SQL Feature: Quantified Comparison Predicates (ANY, ALL) August 14, 2014
- The Difference Between ROW_NUMBER(), RANK(), and DENSE_RANK() August 12, 2014
- The “Free”, “Standard”, “Open” Software Heresy August 11, 2014
- SQL Tip of the Day: Be Wary of SELECT COUNT(*) August 8, 2014
- Join the No OFFSET Movement! August 6, 2014
- Are You Using SQL PIVOT Yet? You Should! August 5, 2014