#31382: Silent failure when saving non-concrete field with update_fields
-------------------------------------+-------------------------------------
Reporter: Peter Law | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(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
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* type: Uncategorized => Bug
* version: 2.2 => master
* component: Uncategorized => Database layer (models, ORM)
* stage: Unreviewed => Accepted
Comment:
> Ideally, I would like a way for a non-concrete field to be able to
specify the underlying concrete fields which should be saved on its
behalf. That's clearly rather complex though (and would likely have
impacts beyond just update_fields) -- a simpler solution would be to error
about this case so that the developer knows something is amis.
Completely agree with this premise, let's focus this ticket on addressing
the concrete field discrepancy. A later improvement could be to allow
specifying ''virtual'' update fields as aliases to the field they manage
but that should be tackled in another ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/31382#comment:2>
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/068.59ce86282b9dbf2de506a13413e2e0be%40djangoproject.com.
