#28393: Make debugging of invalid values assignments to model fields easier
-------------------------------------+-------------------------------------
Reporter: Diederik | Owner: nobody
van der Boor |
Type: | Status: new
Uncategorized |
Component: Database | Version: 1.11
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
When a large model is updated and saved with invalid values,
Django produces a traceback deep within the ORM, with no clue
which field assignment caused the error.
Developers are faced with:
"TypeError: int() argument must be a string, a bytes-like object or a
number, not 'tuple'"
This change (PR included) displays the field name which makes spotting
errors a lot easier.
--
Ticket URL: <https://code.djangoproject.com/ticket/28393>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.e554221fe951d9c97fd6f5f22d79f20c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
