Merge statements should only be generated when you turn on the onDuplicateKeyUpdate() flag, otherwise, insert statements are generated.
>From then on, you can fine-tune bulk (number of rows per statements), batch (number of statements per JDBC batch), and commit sizes to get the optimal performance on your target environment. Hope this helps, Lukas 2017-03-11 13:58 GMT+01:00 Jan Lessner <[email protected]>: > Hi Lucas > The problem with the loader API is that it produces SQL merge statements > instead of batch inserts. This is perfectly OK for the type of operation > which this API seems to be designed for - namely *loading*. But what I am > currently concerned with is *batch processing*. At least for Oracle I can > tell, that merge statements are considerably slower when being applied to > tables with vast amounts of records. In these cases the application's > business logic already assures that there are only inserts to perform. So > I'm looking for a way to run batched prepared insert statements. > > Is there a chance to tell the loader API not to run merge statements? > > Regards, > Jan > > -- > 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.
