#32406: Allow QuerySet.update() to return fields on supported backends.
-------------------------------------+-------------------------------------
Reporter: Tom Carrick | Owner: aivarsk
Type: New feature | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:14 Aivars KalvÄns]:
> Just because the {{{update}}} is returning the number of rows updated. I
can do the same with {{{Foo.objects.update(x="newx", returning=True)}}}
assuming no model will have a {{{returning}}} field. Whatever fits best, I
just want to be able to do {{{returning}}} without executing a raw SQL.
Have you seen the [https://groups.google.com/g/django-
developers/c/qQ5DT91nBLM mailing list discussion]? There are some
proposals to use the current methods without breaking backward
compatibility, e.g. `namedtuple`.
--
Ticket URL: <https://code.djangoproject.com/ticket/32406#comment:15>
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/0107018acbde3be1-9e5b0044-0ca5-4acb-bd5d-445105cc220b-000000%40eu-central-1.amazonses.com.
