>> .storeLocked() works very nicely :). So simple, just add 6 letters and >> suddenly a whole better level of data integrity :) > > Great!
The latest version on GitHub now uses a Settings property to indicate that jOOQ should use optimistic locking. This is documented here: https://github.com/jOOQ/jOOQ/issues/1547 The unpublished storeLocked() and deleteLocked() methods have been removed again. This will keep the API more concise and better aligned with what will be implemented soon, after Sergey Epik's suggestions in this thread (optimistic locking using "timestamp" or "version" columns): https://groups.google.com/d/topic/jooq-user/OO8TMx07ZCU/discussion
