jOOQ in action! Type Safe SQL with Java

I was lucky to find this great lecture while looking for ways to reflect jOOQ in an environment using R2DBC. It was very helpful for understanding because there were a lot of great contents that covered the basic knowledge of jOOQ. I am still trying to set it up to suit the environment and looking for ways to write codes for R2DBC, but I am moving forward step by step more easily than I thought by supporting what I learned in the lecture. Thank you for creating such a great lecture.

My experience using Jooq at my previous company was very good. JPA is very convenient and powerful, but on the other hand, I was disappointed when I encountered functions that were not supported. In the case of Jooq, it was very good that it supported all SQL functions, and that it could be made type-safe through J classes. I was very disappointed that there was no reference, but I personally really like that you made such a detailed lecture.

When I first learned about QueryDSL in JPA, I thought it would be nice if general SQL was also supported as a DSL, and since jooq was the technology I wanted, I bought it and learned it right away. If you have some knowledge of SQL, the learning curve is lower than JPA, so you can understand it without difficulty. I recommend the lecture itself because it includes basic usage + tips the instructor got while using it.

I am a 6-year SI developer who mainly uses MyBatis when dealing with SQL. I studied JPA at first because I wanted to avoid the inevitable human errors that occur after using MyBatis for a long time. I felt the charm of JPA when managing tables with entities without directly writing DDL and when writing C, U, D. However, I was losing my motivation to learn due to the disadvantages of writing SELECT statements and the strangely unfamiliar JPQL (if you use it, you risk having to carry human errors as they are...) and then I found out about this lecture. (I also tried QueryDSL, but I wondered if it was okay because it had not been maintained for a long time... ㅠㅠ) The introduction was long when writing a jOOQ course review, but in conclusion, I really liked this course. As someone who likes writing SQL, I thought that JOOQ, which reduces human errors and creates queries in a similar way to SQL, was the perfect technology for me. Thank you for the great lecture.

I was surprised that it seemed to be a technology stack worth considering introducing, even though it was a technology I was not familiar with. I also found it personally interesting because it compared it to licenses, queryDsl, and JPA.

This is a really good lecture. I thought jooq was a new technology, but it's been over 10 years. This great technology almost got buried, so thank you for introducing it to Korea. The other features are also really good.

I haven't used it in practice yet, but I found it interesting.

Thank you so much for the very helpful lecture!