Re: Optimistic Locking

[Ryan How]

Sounds good. And thanks for the update so I'm not wondering what 
happened next time I update the JOOQ library :). I was a little 
concerned with the naming of the method, but couldn't think of anything 
better. Timestamp and version is also great, a more standard way of 
optimistic locking and should be more efficient than selecting the 
entire record.

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