Hello Lukas, Sorry for the delay (my turn), but my day job just came back at me... This may be the last message of my recent posting frenzy... And indeed this is your day job! I forgot that for a moment. And my congratulations/condolences (choose one) for your night life ;)
About this jOOQPQL stuff, I finally read the article about JPA you pointed me to, as well as the excellent Joel Spolsky's article about leaky abstractions. And now I see why adding a jOOQ abstraction on top of the JPQL abstraction of SQL may not be a good idea ;) I'm not 100% sure if I follow, but there is a feature request for embedded > records to be generated: > https://github.com/jOOQ/jOOQ/issues/2530 > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FjOOQ%2FjOOQ%2Fissues%2F2530&sa=D&sntz=1&usg=AFQjCNFAEwBgzwq1IfYMIxdwdAAwNu0v4Q> No, that was not my point. But that's a very interesting feature I'll keep an eye on. I just meant, given an @Embeddable Address class, using SQL (so jOOQ) to write the query forces me to voluntarily "leak through" my JPA model abstraction, by using the actual column names (probably something like ADDRESS_STREET and co). That would be particularly annoying for small code-first applications where the main point is to let JPA take charge of the DB. But that's probably completely off track for enterprise-grade applications. And yes, by jOOQPQL I meant criteria builder, but a fluent one, with a generator to create type-safe classes for entities, fields and embeddables from the JPA model. MULTISET would have been the right solution (again). *Especially* in JPA, > as that would be perfect for an ORM. You *do* love MULTISETs, don't you? But it seem indeed a very good news for the OO world. Would definitively replace the long collector chains I have to write to transform a result into a JSON-able tree. Cheers, Thomas @Danilo: You're welcome. And thanks for the pointers. -- 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.
