Starting from this: *jOOQ will never replace the Criteria API much like SQL will never replace JPQL.*
Obiouvsly the project is not intended to replace the Criteria API\JPQL, but for some scenario\functionality i think that for sure with this library (in theory) you could think about use Criteria API or JOOQ with the HibernateDSLContext, because basically both can work in terms of JPA Entity. - With SQL, you will NOT query the object graph. Yes, with SQL you don't query the object graph, infact one of the purpose of the library is try to find (if exists) the relationship between join conditions and Entity Objects, in order to specify automatically the "addJoin" for the hibernate SQLQuery API. The effect of doing this is obtain the root entity with the entity object associated eagerly fetched. - Thus, SQL is NOT an equivalent replacement for JPQL. Totally agree. - Thus, jOOQ is NOT an equivalent replacement for the Criteria API. Not equivalent for sure, but the purpose of this "jooq4hibernate" is trying to write a little layer that enable you to write select that returns Entity with Associations attached. So as i said, in some scenario maybe you can think about use Criteria API or HibernateDSLContext. Are you sure? Maybe with JPA 2.1 @NamedEntityGraph Maybe, i didn't study those yet, but you should write by hands the association logic. Instead the purpose of this library is to find "automagically" those associations from join conditions :P The reason of posting here is for sure try to understand with you if my work\thought have sense :D So for me it's a good thing receive those kind of feedback! Antonio -- 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.
