On the jOOQ user group, we're often being asked how to perform transaction management with jOOQ. And we have an easy answer ready: You don't do that with jOOQ. You choose your favourite transaction management API, be it: JDBC Spring JEE JTA (e.g. as supported by Weblogic) Bitronix TM Hibernate And the above list is far … Continue reading MyBatis’ Alternative Transaction Management
Many people compare jOOQ with MyBatis. Both are seen as popular alternatives to Java's persistence standard JPA, as both are much more SQL-focused than JPA itself. When comparing the two tools, the first obvious difference is this: jOOQ is an internal domain-specific language modelling SQL through a Java fluent API. MyBatis is an XML-based SQL templating and mapping … Continue reading SQL Templating with jOOQ or MyBatis
I've recently stumbled upon an interesting blog post about when to use an ORM. I found it to be well-written and quite objective, specifically with respect to its model complexity and throughput diagram: The ORM or not ORM topic will probably never stop showing up on blogs. Some of them are more black and white, … Continue reading High Complexity and Low Throughput. Reasons for Using an ORM.
Now here's one of the most wicked API's I've seen in a while! MyBatis is well-known as a database abstraction framework on top of JDBC, allowing for externalising SQL into files, loading them at appropriate places in your Java code. For those of you who like this approach, you may be used to statements similar … Continue reading MyBatis’ Wicked Statement Builders
Nice feedback from a jOOQ user comparing it with iBATIS: jOOQ rocks! We implemented a large scale ETL service with it, and couldn't be happier. I've used iBATIS, and jOOQ gives all the same advantages of low level SQL without the reams of XML and lack of type safety. [...] one of the best features … Continue reading jOOQ compared to iBatis