#32381: Include number of rows matched in bulk_update() return value
-------------------------------------+-------------------------------------
Reporter: Chris Jerdonek | Owner: Manav
| Agarwal
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: bulk_update | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
`update` will keep returning `int` unless `returning` is specified
otherwise it would break backward compatibility.
Can't this ticket be dedicated to having `bulk_update` returning `int`
when `returning` is not specified?
I don't see what needs to be made here to make `bulk_update` future proof?
How does making `bulk_update -> int` prevent us from having
`bulk_update(returning) -> list` match the signature of `update(returning)
-> list` in the future?
--
Ticket URL: <https://code.djangoproject.com/ticket/32381#comment:10>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.8ee3e92a4757f9e590ad643148b1266e%40djangoproject.com.