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
Everytime you read an excellent article and don't share it, god kills a kitten!
- 1,870,785 hits
- What opportunities does SAP HANA Cloud Platform present for developers – and the Java community in particular? buff.ly/1MZkfIm 1 day ago
- The contest for the #Annotatiomaniac of the year 2015 is still running - We haven't yet decided. Are you up for it? buff.ly/1KdkMWV 1 day ago
Get Back in Control of Your SQL
Top Posts & Pages
- There is no Such Thing as Object-Relational Impedance Mismatch
- 10 Subtle Best Practices when Coding Java
- The 10 Most Popular DB Engines (SQL and NoSQL)
- Java 8 Friday: 10 Subtle Mistakes When Using the Streams API
- Do You Really Understand SQL's GROUP BY and HAVING clauses?
- Top 10 Easy Performance Optimisations in Java
- The Difference Between ROW_NUMBER(), RANK(), and DENSE_RANK()
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- Top 10 Useful, Yet Paranoid Java Programming Techniques
- Java 8 Friday Goodies: Map Enhancements
- There is no Such Thing as Object-Relational Impedance Mismatch August 26, 2015
- Divided we Stand: Optional August 20, 2015
- jOOQ Tuesdays: Thomas Müller Unveils How HSQLDB Evolved into the Popular H2 Database August 18, 2015
- Common SQL Clauses and Their Equivalents in Java 8 Streams August 13, 2015
- Top 10 Useful, Yet Paranoid Java Programming Techniques August 11, 2015
- RAM is the new SSD August 5, 2015
- INTERSECT – the Underestimated Two-Way IN Predicate August 4, 2015
- Java 8’s Method References Put Further Restrictions on Overloading July 28, 2015
- NULL is Not The Billion Dollar Mistake. A Counter-Rant July 22, 2015
- What the sun.misc.Unsafe Misery Teaches Us July 20, 2015