Changes between Initial Version and Version 1 of Ticket #35044, comment 1


Ignore:
Timestamp:
Dec 16, 2023, 11:43:17 AM (9 months ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35044, comment 1

    initial v1  
    33When `refresh_from_db(fields)` is specified it should likely not clear reverse relationships and I think the same can be said about
    44
    5 Regression in a7b5ad8b19a08d7d57302ece74f6e26d2887fd9f #27846 for reverse relations and possibly 123b1d3fcf79f091573c40be6da7113a6ef35b62 #34137 for private fields. The private field situation is more complex though as they might be composed of other fields (e.g. `GenericForeignKey`) but the field APIs doesn't expose a generic way of introspecting that so I would assume we'd still want to clear .
     5Regression in a7b5ad8b19a08d7d57302ece74f6e26d2887fd9f #27846 for reverse relations and possibly 123b1d3fcf79f091573c40be6da7113a6ef35b62 #34137 for private fields. The private field situation is more complex though as they might be composed of other fields (e.g. `GenericForeignKey`) but the field APIs doesn't expose a generic way of introspecting that so I would assume we'd still want to clear even if `fields` is specified.
    66
    77An alternative here would be to accept another kwarg to denote field cache clearing that would default to `True` and that `DeferredAttribute.__get__` would pass `False` to.
Back to Top