Lazy fetching
Hibernate JPA guy: So, how do you handle huge result sets in jOOQ?
jOOQ guy (me): jOOQ supports lazy fetching.
Hibernate JPA guy: And how do you manage LazyInitializationException?
jOOQ guy (me): For Hibernate JPA users that have just got here, I'd like to stress this right from the start – don't assume that jOOQ lazy fetching is related to or similar to Hibernate JPA lazy loading. jOOQ doesn't have and doesn't need a Persistence Context and doesn't rely on a Session object and proxy objects. Your code is not prone to any kind of lazy loading exceptions!
Then, what is jOOQ lazy fetching?
Well, most of the time, fetching the entire result set into memory is the best way to exploit your RDBMS (especially in web applications that face high traffic by optimizing small result sets and short transactions). However, there are cases (for instance, you might have a huge result set) when you'll like to fetch and process the result...
