#28393: Make debugging of invalid values assignments to model fields easier
-------------------------------------+-------------------------------------
     Reporter:  Diederik van der     |                    Owner:  nobody
  Boor                               |
         Type:  Uncategorized        |                   Status:  new
    Component:  Database layer       |                  Version:  1.11
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Description changed by Diederik van der Boor:

Old description:

> 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.

New description:

 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.

 Pull request: https://github.com/django/django/pull/8760

--

-- 
Ticket URL: <https://code.djangoproject.com/ticket/28393#comment:1>
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/064.1c0190d6fd4389f0e47a577679488cd5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to