Changes between Initial Version and Version 1 of Ticket #16818, comment 9


Ignore:
Timestamp:
10/02/11 08:44:03 (3 years ago)
Author:
pressureman
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16818, comment 9

    initial v1  
    55}}}
    66
    7 Inspecting parent_obj.m2m_children.all() shows the new_child_obj (cached), but if the cache is invalidate (eg. start new django shell, or new request) the new_child_obj is absent from parent_obj.m2m_children.all().
     7Inspecting parent_obj.m2m_children.all() shows the new_child_obj (cached), but if the cache is invalidated (eg. start new django shell, or new request) the new_child_obj is absent from parent_obj.m2m_children.all().
    88
    99However, if the parent_obj is explicitly saved after adding the new_child_obj, eg.
     
    1414}}}
    1515
    16 then the new_child_obj is committed to the DB, and present in subsequent requests.
     16then the new_child_obj is committed to the DB, and is present in subsequent requests.
    1717
    18 This is new behaviour - the explicit parent_obj.save() was not required r16739. I'm not sure if this still qualifies as a bug, or whether it is in fact a fix for a long-standing, incorrect behaviour.
     18This is new behaviour - the explicit parent_obj.save() was not required before r16739. I'm not sure if this still qualifies as a bug, or whether it is in fact a fix for a long-standing, incorrect behaviour.
Back to Top