#33579: Raise a specialized exception when Model.save(update_fields) does not
affect any rows
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Dulalet
Type: New feature | Status: assigned
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* needs_better_patch: 0 => 1
Comment:
Left some comments on the PR about possible improvement to make the raised
exception more coherent with `ObjectDoesNotExist` and
`MultipleObjectsReturned` while still inheriting from `DatabaseError` for
backward compatiblity reasons.
--
Ticket URL: <https://code.djangoproject.com/ticket/33579#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/0107018fffeac65d-85adf737-62f4-47a4-bdec-5de470a9d053-000000%40eu-central-1.amazonses.com.
