#19527: Allow QuerySet.bulk_create() to set the primary key of its objects
-------------------------------------+-------------------------------------
Reporter: Tuttle | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle | Triage Stage: Accepted
QuerySet.bulk_create |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tuttle):
Thank you for enlightening.
I tend to see this backend compat feature to rather configure the existing
call, so personally I see the way of adding a new API call as merely
complicating the stuff more. Many newbies are already frowning upon these
parts of ORM I guess.
So why not to allow both, the compatibility requirements of 3rd party apps
as well as efficient modern feature to those who can afford it and want to
avoid one by one inserts?
I'd propose s/t like this ''so the behavior stays the same'':
{{{
#!python
def bulk_create(..., allow_fallback=True):
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19527#comment:37>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.47972bc9d3ba5f8461379b321cf5e649%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
