Changes between Version 3 and Version 4 of Ticket #36741, comment 2


Ignore:
Timestamp:
Nov 18, 2025, 10:57:31 AM (4 weeks ago)
Author:
Youngkwang Yang

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36741, comment 2

    v3 v4  
    1 (Note: The screenshot you attached is from the bulk_update() section, not the update() section. "QuerySet.update()" is linked, and clicking it takes you to the update() section.)
     1(Note: The screenshot you attached is from the bulk_update() section, not the update() section. "QuerySet.update()" is linked and directs to the update() section.)
     2That said, I can see how the current wording could cause confusion - the bulk_update() documentation doesn't clarify that it uses update() internally.
    23
    3 there is potential for confusion here since the bulk_update() documentation doesn't explain that update() is called internally. This might explain why the bulk_update() section could be mistaken for the update() section.
     4I think the documentation could be improved with the following change:
    45
     6{{{
     7diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
     8--- a/docs/ref/models/querysets.txt
     9+++ b/docs/ref/models/querysets.txt
     10@@ -2508,7 +2508,7 @@
     11     >>> Entry.objects.bulk_update(objs, ["headline"])
     12     2
     13
     14-:meth:`.QuerySet.update` is used to save the changes, so this is more efficient
     15+This method uses :meth:`.QuerySet.update` internally, making it more efficient
     16 than iterating through the list of models and calling ``save()`` on each of
     17 them, but it has a few caveats:
     18}}}
Back to Top