Oh, I see, that's a good hint. Indeed, all existing record.store() or record.insert() based approaches don't take advantage of your knowledge about wanting to insert *all* columns.
I think the Loader API solution will be the best one right now, as it also allows you to fine tune bulk, batch, and commit sizes (each of which highly depend on the database vendor, and your actual data). But there's certainly food for thought here for two improvements: 1. Look into what's so slow about batchInsert() and how that can be improved 2. Perhaps find a new API (or an adaptation of existing API) that will do exactly what you have in mind. 2016-07-15 18:28 GMT+02:00 Mike Foody <[email protected]>: > Hi Lukas, > > DSL.using(configuration).execute(CUSTOMER.insert(name, street1, ...)); > > > That's exactly what we're looking for. In particular we want to batch the > org.jooq.Insert instances. I'll take a look at your suggestions. What we > found was the dirty checking that occurs in the records when using > dsl.batchInsert(records) significantly slowed down the process. > -- 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.
