[Django] #26568: in_bulk when run on a query set should not need a list of IDs

2 views
Skip to first unread message

Django

unread,
May 2, 2016, 10:06:26 AM5/2/16
to django-...@googlegroups.com
#26568: in_bulk when run on a query set should not need a list of IDs
-------------------------------+--------------------
Reporter: brillgen | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
in_bulk provides a great shortcut for getting a primary key dictionary for
accessing objects randomly without hitting the database repeatedly.
However, for some use case it has been designed as a manager function
which takes a list of PKs. But when it is run on a query set, by default
it should just return that very query set in a dictionary form (sort of
obvious isn't it?)

--
Ticket URL: <https://code.djangoproject.com/ticket/26568>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
May 2, 2016, 10:18:38 AM5/2/16
to django-...@googlegroups.com
#26568: in_bulk when run on a query set should not need a list of IDs
-------------------------------------+-------------------------------------
Reporter: brillgen | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: duplicate
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 timgraham):

* status: new => closed
* needs_better_patch: => 0
* component: Uncategorized => Database layer (models, ORM)
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0
* type: Bug => Cleanup/optimization


Comment:

Duplicate of #8065 (fixed in Django 1.10).

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

Reply all
Reply to author
Forward
0 new messages