Hello, I'm trying to see if my understanding is correct with respect to Optimistic locking (OL) and transactions.
1. Need to enable the OL in Jooq using executeWithOptimisticLocking settings 2. Since OL in Jooq automatically throws / fails when see the concurrent modification, I believe its totally fine to run them in any transaction mode (note that I'm using Postgres here). My understanding here is that OL themselves hides the complexity of transaction. May be I'm wrong here. Please correct me. 3. How does Jooq knows which column it needs to watch while versioning under OL? The documentation from here : https://www.jooq.org/doc/2.5/manual/sql-execution/crud-with-updatablerecords/optimistic-locking/ says that, we can create a column called MODIFIED as a TIMESTAMP. But the question here is, how does the column mapping works w.r.t to OL? Thanks for your time on this. Kamal. -- 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.
