#26400: QuerySet bulk_create method to handle generators to prevent loading all
objects in memory at once
-------------------------------------+-------------------------------------
Reporter: likeon | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: bulk_create | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
Replying to [comment:2 likeon]:
> It's not the first time I need that opportunity. I mean sure I can write
that split thing one more time as I did in other projects, but I don't see
any reason why the feature couldn't be a part of Django.
We'd have to alter both the signature and the return type of `bulk_create`
in order to pass a flag enabling this feature and make sure not to return
a list of the created objects. At this point I think this should be
handled by another method/function.
I personally don't believe this use case is common enough to warrant an
inclusion in Django but as Tim pointed out you could try leveraging
support from the community on the developer mailing list.
--
Ticket URL: <https://code.djangoproject.com/ticket/26400#comment:4>
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.03e4f1cb5fe01e086f55b03cdc480858%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
