I'm not sure what you mean by handling relationships at code generation time...
Lazy/eager loading are core features of Object-relational Mapping tools, such as Hibernate/JPA. The same applies to second-level caching. Most of those features seem nice at first sight, but turn out to be a major performance-killer in applications where developers don't spend enough time to fine-tune lazy/eager loading or caching configurations. jOOQ is not really an ORM but just a slim layer on top of JDBC. You can explicitly "eager" load all sorts of relations using joins. You could also consider the generated fetchXXX() methods in your TableRecords as "lazy" loading implementations, even if the "lazy-loaded" data is not cached. Caching can be achieved using additional third-party libraries such as Terracotta EhCache, or JBoss Cache. Or just plain Hashtables in simple cases. Does this answer your question? 2011/8/1 Rakesh Waghela <[email protected]>: > what is the expected behavior from jooq when we have foreignkey > relationships among tables? > Does it have any feature like lazy/eager loading..etc? >
