From 0afe8ba2d6712f3766f1ef11bbd14734cb3b2d2a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tobias=20Kr=C3=B6nke?= <tobias@kroenke.de>
Date: Fri, 12 Jun 2020 14:54:23 +0200
Subject: [PATCH] [3.0.x] Fixed #31689 -- Doc'd caveat about using
 bulk_create()'s ignore_conflicts on MariDB and MySQL.

Backport of 69e0d9c553bb55dde8d7d1d479a78bfa7093f406 from master
---
 docs/ref/models/querysets.txt | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index a64d986dbb..4d41d0c390 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -2100,6 +2100,17 @@ that fail constraints such as duplicate unique values. Enabling this parameter
 disables setting the primary key on each model instance (if the database
 normally supports it).
 
+.. warning::
+
+    On MySQL and MariaDB, setting the ``ignore_conflicts`` parameter to
+    ``True`` turns certain types of errors, other than duplicate key, into
+    warnings. Even with Strict Mode. For example: invalid values or
+    non-nullable violations. See the `MySQL documentation`_ and
+    `MariaDB documentation`_ for more details.
+
+.. _MySQL documentation: https://dev.mysql.com/doc/refman/en/sql-mode.html#ignore-strict-comparison
+.. _MariaDB documentation: https://mariadb.com/kb/en/ignore/
+
 .. versionchanged:: 2.2
 
     The ``ignore_conflicts`` parameter was added.