Just to add a little to the thread, The last 2 times I have been involved with projects that needed Java based applications to be coded and developers hired I put forward jOOQ as the database layer. In the DevOps/SysOps role I had, it was easy to justify jOOQ as the databases had to be open relational structures. The developers on the other hand found it yet another thing they have to get up to speed on, so having it generate DAOs allows them to get up to speed over time as they started with the DAOs. The hiring process for both companies had no real focus on jOOQ skills as there were more important CV requirements, I think that the only DB related requirement was for possible hires to have an understanding relational database and the limitations of Hibernate :)
-- 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.
