#29331: Model fields where the field name is shadowed by Python property aren't
saved
-------------------------------------+-------------------------------------
     Reporter:  Ben Mathes           |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  2.0
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  models,              |             Triage Stage:  Accepted
  deferred_field, save               |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Ben Mathes):

 We're working around it in our specific use case, but not a general
 solution. Possible the codebase where we found this was mistaking
 {{{name}}} for {{{db_column}}}, as setting the {{{name}}} kwarg does seem
 to set the DB column name.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29331#comment:5>
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/067.16a923b7f3d3addf39995365df2a7bf7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to