Hi Garth, Thanks for your message. jOOQ's loader API has ways to split data loading into:
- Bulk sizes (number of rows per insert statement) - Batch sizes (number of statements sent as JDBC batches) - Commit sizes (number of batches committed) See: http://www.jooq.org/doc/latest/manual/sql-execution/importing Is that what you mean? Other than that, there's currently no way to control batch sizes of the various DSLContext.batch() methods, apart from doing that in client code. Hope this helps, Lukas 2016-02-24 19:53 GMT+01:00 <[email protected]>: > How does Jooq handle batches that have grown too large for the underlying > database? Will Jooq internally split the batches into multiple batches at > execute time? Also, is it possible to iterate through the batch to split > it manually? Currently our batch sizes are variable, and I've basically > added statements to check the size of the batch while adding and if they > look too big, to execute the batch and start a new one. It would be nice > not to have to do this, but I'm unsure of the underlying behavior with very > large batches. > > Thanks. > > -- > 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/d/optout. > -- 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/d/optout.
