Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#30326 closed Cleanup/optimization (fixed)

Document how to avoid F() assignments persistence

Reported by: Sage Abdullah Owned by: Sage Abdullah
Component: Documentation Version: dev
Severity: Normal Keywords: documentation, models, expressions
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

In F() expressions documentation, it nicely explains that ​F() assignments persist after Model.save(). However, it does not explain how to avoid this persistence after we're done using the expression (which can be done by reloading the object). I think it'll be helpful to add this information in the docs.

Change History (8)

comment:1 by Mariusz Felisiak, 6 years ago

Triage Stage: Unreviewed → Accepted

comment:2 by Sage Abdullah, 6 years ago

Owner: changed from nobody to Sage Abdullah
Status: new → assigned

comment:3 by Sage Abdullah, 6 years ago

Has patch: set

​PR

comment:4 by Tim Bell, 6 years ago

Patch needs improvement: set

comment:5 by Tim Bell, 6 years ago

Patch needs improvement: unset

comment:6 by Tim Bell, 6 years ago

Triage Stage: Accepted → Ready for checkin

comment:7 by Mariusz Felisiak <felisiak.mariusz@…>, 6 years ago

Resolution: → fixed
Status: assigned → closed

In bfae195b:

Fixed #30326 -- Doc'd how to avoid persistence of F() assignment.

comment:8 by Mariusz Felisiak <felisiak.mariusz@…>, 6 years ago

In 86de1068:

[2.2.x] Fixed #30326 -- Doc'd how to avoid persistence of F() assignment.

Backport of bfae195b0a2c8dae755610a7e23add5c6bc37b5e from master

Note: See TracTickets for help on using tickets.
Back to Top