Hi In my case, the generation of the DAOs that brings me jOOQ was one of the main decision to choose it instead of QueryDSL for example. When you work in a medium/big project that manages information stored in relational database, where is the "best ubication" to include the queries? the services layer? my "own specific" layer? in that case, you will see how the size of the classes included in this layer will grow dramatically.
And it is a very bad design to spread the queries among several files without a strict criteria, for example, include a sql to get the list of users in the RoleService or something like that. jOOQ offers the possibility of generate DAOs or not, every developer can choose it in the XML configuration file. So if you prefer to use DSLContext directly or develop your own DAO, then go ahead. Currently, jOOQ allow you it. Unfortunately, not always I can write all required test (due to deadlines and similar issues) but when I can do it, the DAO layer offers me the possibility to test only this layer and verify "all required queries" by my project using a database used for testing purpose. And when I want to test "upper layers" like services or controllers for example, I only need to deal with the "specific business logic" added by this layer. Best regards Celestino Reyes -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
