#33579: Raise a specialized exception when Model.save(update_fields) does not
affect any rows
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mohamed Nabil Rady):
Is it the best the idea to introduce a new subclass rather than using one
of the other ones ? Because I think we should stick with the ones
specified in [https://peps.python.org/pep-0249 PEP 249].
Not sure if we should raise a {{{ ProgrammingError }}} or {{{
InterfaceError }}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33579#comment:3>
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/0107017f94811bd9-e760bfda-505e-47b3-bfac-4cd362b36c47-000000%40eu-central-1.amazonses.com.
