Opened 13 years ago

Last modified 8 years ago

#18717 closed Bug

Setting attributes on deferred objects should trigger field's descriptor's __set__() — at Version 4

Reported by: German M. Bravo Owned by: nobody
Component: Database layer (models, ORM) Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: yes Patch needs improvement: yes
Easy pickings: no UI/UX: no
Pull Requests:How to create a pull request

Description (last modified by Tim Graham)

Setting attributes on deferred objects (DeferredAttribute) should trigger original field's descriptor's __set__() (if any).
Currently, specially for custom fields set up as descriptors defining __set__(), the original field's __set__ is never called when setting object attributes on deferred fields.

Change History (4)

by German M. Bravo, 13 years ago

Attachment: #18717-deferred_fields_and_descriptors.diff​ added

comment:1 by Łukasz Rekucki, 12 years ago

Needs tests: set
Patch needs improvement: set
Triage Stage: Unreviewed → Accepted

The patch failes as DeferredAttribute no longer has model_ref. On a side note, _meta.get_field_by_name can be used instead of iterating.

Last edited 12 years ago by Łukasz Rekucki (previous) (diff)

comment:2 by Aymeric Augustin, 12 years ago

Component: Uncategorized → Database layer (models, ORM)
Type: Uncategorized → Bug

comment:4 by Tim Graham, 9 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.
Back to Top