Context Navigation

Changes between Version 1 and Version 2 of Ticket #33191

v1	v2
13	13	In the application where this behavior was first observed, the application was creating thousands of parent and child objects using bulk_create(). The subsequent lazy reads occurred when creating log entries to record the action, and added thousands of unwanted SELECT queries.
14	14
15		Closed ticket 29497 solved a problem with potential data loss in this situation by essentially executing {{{child.parent_id = child.parent.pk}}} while preparing the child object to be saved. However, when the child's ForeignKeyDeferredAttrbute "parent_id" changes value from None to the parent's ID, the child's internal cache containing the reference to "parent" is cleared. The subsequent reference to child.parent then must do a lazy read and reload parent from the database.
	15	Closed ticket #29497 solved a problem with potential data loss in this situation by essentially executing {{{child.parent_id = child.parent.pk}}} while preparing the child object to be saved. However, when the child's ForeignKeyDeferredAttrbute "parent_id" changes value from None to the parent's ID, the child's internal cache containing the reference to "parent" is cleared. The subsequent reference to child.parent then must do a lazy read and reload parent from the database.
16	16
17	17	A workaround to avoid this lazy read is to explicitly update both the "parent_id" and "parent" cache entry by adding this non-intuitive statement: