From 6fcf0f9b3022df5dd79c8e1469d9fafe7d504478 Mon Sep 17 00:00:00 2001
From: Lukas Eder <lukas.eder@gmail.com>
Date: Fri, 20 Apr 2012 08:31:11 +0000
Subject: [PATCH] [#1320] Document the possibility of accessing
 Connection.getWarnings() when errors are ignored in the Loader API

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

diff --git a/jOOQ/src/main/java/org/jooq/LoaderOptionsStep.java b/jOOQ/src/main/java/org/jooq/LoaderOptionsStep.java
index 4198b611ba..dc8e07d1a5 100644
--- a/jOOQ/src/main/java/org/jooq/LoaderOptionsStep.java
+++ b/jOOQ/src/main/java/org/jooq/LoaderOptionsStep.java
@@ -74,7 +74,9 @@ public interface LoaderOptionsStep<R extends TableRecord<R>> extends LoaderSourc
      * unique key's value is already in the database.
      * <p>
      * If the loaded table does not have a main key, then all records are
-     * inserted.
+     * inserted. This may influence the JDBC driver's outcome on
+     * {@link Connection#getWarnings()}, depending on your JDBC driver's
+     * implementation
      * <p>
      * If you don't specify a behaviour, {@link #onDuplicateKeyError()} will be
      * the default. This cannot be combined with {@link #onDuplicateKeyError()}