#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: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Enrique Soria):
I've made a PR for this which simply creates a new exception by inheriting
from DatabaseError. This will be compatible with people who already was
catching DatabaseError, and will make new developments easier by having a
separate exception class.
https://github.com/django/django/pull/18244
--
Ticket URL: <https://code.djangoproject.com/ticket/33579#comment:9>
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/0107018ffcecbb82-f2299cd0-4776-407e-b13e-6f3ae8e8774f-000000%40eu-central-1.amazonses.com.
