Overwhelming feedback from the jOOQ User Survey
jOOQ has been the leading Java Open Source SQL building tool for the last three years. Feedback on social media such as Facebook, Twitter, reddit, Stack Overflow has been very positive.
The recent user survey was well received by an increasingly growing jOOQ community. It has shown a couple of interesting facts:
- jOOQ users are highly proficient with Java and SQL
- jOOQ users mainly concentrate on using H2, MySQL, Oracle, PostgreSQL, and SQL Server
- jOOQ’s maturity is mostly appreciated for mission-critical applications
- jOOQ users are generally satisfied or very satisfied with jOOQ’s mission, support and quality
Thank you for taking the time to complete the user survey. Your valuable comments will help jOOQ to take the right direction in the future, providing you with even more value.
SQL popularity still high
In recent years, many NoSQL vendors have surfaced to sell their alternative data stores and query languages. Some of them aim to solve entirely different problems than relational data stores. But as in pre-ANSI-SQL times, there is a huge amount of incompatible proprietary query languages and techniques.
SQL is standardised by ANSI / ISO and its vendors can still grow their market shares as the Big Data buzz is increasing. A clear sign of SQL’s popularity is the success that these Top 10 Mistakes articles had, recently, on DZone:
jOOQ 3.2 feature outlook
New jOOQ users have contributed new awesome ideas to the community. These include:
A new SPI to hook into query rendering and variable binding
This SPI will allow jOOQ users to perform arbitrary SQL transformations based on query rendering and variable binding events. A very common use-case is to listen for a given set of well-known tables and generate additional filtering predicates in the SQL WHERE clause, centrally restricting access to data.
This not only allows for adding an additional, transparent security layer to your SQL code generation, it will also allow for implementing multi-tenancy in shared-schema environments.
A new SPI to hook into CRUD operations
Many users profit from jOOQ’s ActiveRecord-style CRUD API. This API will be enhanced with a powerful SPI that allows to hook into store(), insert(), update(), delete(), refresh() operations.
A common use-case for this is data initialisation prior to inserts, or ID-generation.