Thank you very much for your feedback, Dayo I will comment inline
2016-07-08 18:17 GMT+02:00 <[email protected]>: > JOOQ has been really helpful. Like others have shared, I think mapping is > where I spend some considerable amount of time when using Jooq. I have not > really been leveraging JPA column annotation (appears you have or will be > deprecating support). > The deprecation will only affect the DefaultRecordMapper. The implementation should be moved out of this default mapper and into a separate JPARecordMapper. So, you should be safe to use this feature also in the future. > I have had to develop utilities to support mapping with the help of > Modelmapper library. For queries with multiple joins, how do you > effectively deal with duplicate records in results (from resulting joins) > and have them mapped to collection of different pojos without duplicates > with current mapping strategies? With multiple selects, I can make do with > the simplistic mappings but that is like going N + 1 queries. I will like > to know how folks are dealing with this without too many code duplication > or if there are libraries that can help or examples. > For simple use-cases, the various intoGroups() methods will certainly help. For more complex use-cases, this will be much harder. JPA doesn't solve this sufficiently well either. It just hides the complexity from the user but adds performance overhead just the same. > On a side note I find the amount of options (methods available, overloaded > etc) when using jooq api to be a distraction. Sometimes get the sense I > don't know enough about the tool. > That's interesting. Do you have a particular example in mind? E.g. the various fetch methods? -- 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.
