summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJacob Walls <jacobtylerwalls@gmail.com>2025-09-25 09:56:24 -0400
committerJacob Walls <jacobtylerwalls@gmail.com>2025-10-03 11:26:37 -0400
commit2fe18d943f8e826cee22232a61363c36651ef1f0 (patch)
tree8268f87cce94e264fd754c91d9fca1e6cb66a2b7 /docs
parent851400194d90f17ade622abb79eaacab1e71b951 (diff)
[6.0.x] Refs #36143, #28596 -- Avoided mentioning exact query parameter limit in bulk_create() docs.
Backport of 0a09c60e97166e0188717ff340b4d93b72207e96 from main.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/models/querysets.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 59550e6690..99bbbb54a4 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -2455,8 +2455,8 @@ This has a number of caveats though:
Entry.objects.bulk_create(batch, batch_size)
The ``batch_size`` parameter controls how many objects are created in a single
-query. The default is to create all objects in one batch, except for SQLite
-where the default is such that at most 999 variables per query are used.
+query. The default is to create as many objects in one batch as the database
+will allow. (SQLite and Oracle limit the number of parameters in a query.)
On databases that support it (all but Oracle), setting the ``ignore_conflicts``
parameter to ``True`` tells the database to ignore failure to insert any rows