[Django] #35596: Database access optimization page has outdated info

[Django]

#35596: Database access optimization page has outdated info
---------------------------------+-----------------------------------------
Reporter: Francisco Couzo | Type: Bug
Status: new | Component: Documentation
Version: | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-----------------------------------------
> Second, the lookup doesn’t guarantee that only one object will be
returned. If the query matches more than one object, it will retrieve and
transfer all of them from the database. This penalty could be substantial
if hundreds or thousands of records are returned. The penalty will be
compounded if the database lives on a separate server, where network
overhead and latency also play a factor.

This was modified 5 years ago in commit
330638b89f14e1fb06e9d313ccc9768ae167c53f

There is one specific case when get() can return all the result set, which
is when using the oracle db and select_for_update
--
Ticket URL: <https://code.djangoproject.com/ticket/35596>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#35596: Database access optimization page has outdated info

-------------------------------------+-------------------------------------
Reporter: Francisco Couzo | Owner: Ripoohann
| S Kumar
Type: Bug | Status: assigned
Component: Documentation | Version:
Severity: Normal | Resolution:

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

-------------------------------------+-------------------------------------
Changes (by Ripoohann S Kumar):

* owner: (none) => Ripoohann S Kumar
* status: new => assigned

--
Ticket URL: <https://code.djangoproject.com/ticket/35596#comment:1>