From f97400943dd915d3043cf85597f66351ef573e2e Mon Sep 17 00:00:00 2001
From: Lukas Eder <lukas.eder@gmail.com>
Date: Wed, 8 Apr 2020 10:31:04 +0200
Subject: [PATCH] [jOOQ/jOOQ#10050] Fixed Javadoc

---
 jOOQ/src/main/java/org/jooq/UpdatableRecord.java | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/jOOQ/src/main/java/org/jooq/UpdatableRecord.java b/jOOQ/src/main/java/org/jooq/UpdatableRecord.java
index 3f18a1bd2f..e9a5505934 100644
--- a/jOOQ/src/main/java/org/jooq/UpdatableRecord.java
+++ b/jOOQ/src/main/java/org/jooq/UpdatableRecord.java
@@ -380,10 +380,9 @@ public interface UpdatableRecord<R extends UpdatableRecord<R>> extends TableReco
      * update the row regardless of which (unique) key value is already present.
      * See {@link InsertOnDuplicateStep#onDuplicateKeyUpdate()}.
      * <p>
-     * Optimistic locking only works if the underlying dialect supports
-     * {@link InsertOnConflictWhereStep#where(Condition)}. Otherwise, the
-     * <code>UPDATE</code> path of the statement will not be able to update the
-     * row conditionally.
+     * When optimistic locking is active for this record, then this operation
+     * will execute {@link #insert()} or {@link #update()} explicitly, depending
+     * on whether the lock values are present already in the record.
      * <p>
      * If you want to enforce statement execution, regardless if the values in
      * this record were changed, you can explicitly set the changed flags for