Hi Dennis, 2013/4/21 Dennis Fischer <[email protected]>: > Hey Lukas, > > this is how I usually search: If not used to an API I try to get a look at > the manual - it might provide easy and good solutions. > If that doesn't help - I take a look at JavaDoc. And if I then still got no > clue - I try (if it is worth spending this time) to look at the code, in > this case > especially the implementation. > > this is how I've searched: > I opened the multi html page documentation and searched for "Resultset". I'm > sure I've opened both posted links of your above post. > > - http://www.jooq.org/doc/3.0/manual/sql-execution/fetching > - > http://www.jooq.org/doc/3.0/manual/sql-execution/fetching/resultset-fetching > I wanted to load the full result set directly with (I guess) "fetch" and > convert this into a POJO-List.
Good to know. Thanks a lot for your explanation! > The H2 triggers however showed me a big > problem: > The result set is infinitely long - basically jooq won't find the end of the > resultset as there seems to be none. > Therefore I looked for a new solution and fetchLazy suited my needs. I had > to define the loop-break definition myself (I compared id's) - but that's > okay. Otherwise I'd have ended up using "fetch". Yes, I remember this discussion. The H2 trigger base implementation adds some convenience on top of the JDBC ResultSet, which essentially violates the ResultSet's contract. Cheers Lukas -- 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/groups/opt_out.
