Hello, We are starting a new project based on Spring Boot and have selected jOOQ as our main DB querying framework.
Does anybody have experiences with Spring and jOOQ? None of our devs have used jOOQ so far, so I'm looking for best practices and possible pitfalls. Since Spring Boot already has a sensible autoconfiguration for jOOQ, that is not an issue. I'm rather looking for infos on: * Integration with Spring Data? Is that possible? Can we reuse some of the Spring Data repository "magic" to reduce boilerplate? I'm not talking about Spring Data JPA but rather the "core" (or commons), since we at first try to avoid JPA completely. * What are the mechanisms that can help us with CRUD and domain mapping? We don't have too many tables and only a few simple CRUD operations (the larger portion being complex queries and data transformations), but for those cases, which patterns would be useful? I wouldn't like to leak the jOOQ ActiveRecord objects above the repository layer, since I think the consensus is that mixing ActiveRecord and business logic leads to difficult-to-maintain code. And because our domain objects don't necessarily map 1:1 to tables, jOOQs POJO or DAO autogeneration might not produce the best results. Thanks in advance for any insights! Best, Janne -- 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 jooq-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
