Hi Dennis, Thanks for investigating this. I'm not sure if you should really "consume" the newRow ResultSet. Instead, you should set values into it, using ResultSet.updateObject() and similar methods. Consider H2's Javadoc on TriggerAdapter.fire(Connection, ResultSet, ResultSet): http://www.h2database.com/javadoc/org/h2/tools/TriggerAdapter.html#fire_Connection_ResultSet_ResultSet
It says: "ResultSet.next does not need to be called (and calling it has no effect; it will always return true)." This is quite astonishing, as H2 returns an infinite ResultSet for a single row. Hence, your fetchLazy() attempt is indeed the best approach to solve this problem, if you want to use H2's TriggerAdapter... Cheers Lukas 2013/3/14 Dennis Fischer <[email protected]> > Update: > I wrote a workaround for this now as I was able to understand what was > going on: > jooq seems to work as expected - however - h2 is returning an infinite > ResultSet (dunno why - but that's the fact). > I changed fetch to fetchLazy and did a check on my identity field - the > cursor will then stop once we're having a cycle detected. > > -- > 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. > > > -- 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.
