Changes between Initial Version and Version 1 of Ticket #31382, comment 8


Ignore:
Timestamp:
Oct 11, 2020, 8:04:56 AM (4 years ago)
Author:
Florian Apolloner

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #31382, comment 8

    initial v1  
    1 >  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.
     1> 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.
    22
    33Did anyone create a ticket for the complex approach?
Back to Top