One of the features that I like in hibernate is the buffering that happens in the session cache. I can write my code and do things and then flush/commit the whole session at once. This allows hibernate to (1) automatically batch (prepare + bind) the dml (2) delay the statements so that db locks are held for minimum amount of time (instead of execute, round trip, do more app work, etc.), (3) hibernate re-orders the dml to avoid deadlocks. That's a pretty powerful combo for high throughput oltp systems like I tend to work on. Some kind of simple "session" concept that could aggregate/buffer jooq dml statements to flush them at a later point in time seems not too difficult. Could at least get #1 and #2 benefits pretty easily with this. #3 seems a little more tricky. I'm not sure that jooq should be in the business of doing things like this. But a simple mechanism to buffer dml work and auto-batch it seems right in the jooq wheelhouse.
Any plans for this? A github issue I can vote for? -- 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.
