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!
- 562,212 hits
- jOOQ Newsletter: jOOLY 23, 2014 - Only 8 Days Left! - eepurl.com/ZzV3L 12 hours ago
- Stack Overflow scales "Big Data" vertically with SQL Server: buff.ly/1o9VsnJ 13 hours ago
Get Back in Control of Your SQL
Top Posts & Pages
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- The 10 Most Popular DB Engines (SQL and NoSQL)
- Frightening Facts about MySQL
- 10 Subtle Best Practices when Coding Java
- Does Java 8 Still Need LINQ? Or is it Better than LINQ?
- 10 Common Mistakes Java Developers Make when Writing SQL
- Easy Mocking of Your Database
- 10 More Common Mistakes Java Developers Make when Writing SQL
- Java 8 Friday Goodies: Map Enhancements
- Using SQL Injection Vulnerabilities to Dump Your Database
- jOOQ Newsletter: jOOLY 23, 2014 – Only 8 Days Left in jOOLY July 23, 2014
- Frightening Facts about MySQL July 22, 2014
- Keeping things DRY: Method overloading July 21, 2014
- Logon Triggers: The Oracle Database Magic Bullet July 14, 2014
- Java 8 Friday: More Functional Relational Transformation July 11, 2014
- PostgreSQL’s Table-Valued Functions July 7, 2014
- jOOQ Newsletter: July 2, 2014 – jOOLY 20% Discount Offering July 2, 2014
- Stop Unit Testing Database Code June 26, 2014
- Flyway and jOOQ for Unbeatable SQL Development Productivity June 25, 2014
- Should I Put That Table Alias or Not? June 24, 2014