Opened 15 months ago

Closed 15 months ago

Last modified 15 months ago

#30326 closed Cleanup/optimization (fixed)

Document how to avoid F() assignments persistence

Reported by: sage Owned by: sage
Component: Documentation Version: master
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 Changed 15 months ago by felixxm

Triage Stage: UnreviewedAccepted

comment:2 Changed 15 months ago by sage

Owner: changed from nobody to sage
Status: newassigned

comment:3 Changed 15 months ago by sage

Has patch: set

comment:4 Changed 15 months ago by Tim Bell

Patch needs improvement: set

comment:5 Changed 15 months ago by Tim Bell

Patch needs improvement: unset

comment:6 Changed 15 months ago by Tim Bell

Triage Stage: AcceptedReady for checkin

comment:7 Changed 15 months ago by Mariusz Felisiak <felisiak.mariusz@…>

Resolution: fixed
Status: assignedclosed

In bfae195b:

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

comment:8 Changed 15 months ago by Mariusz Felisiak <felisiak.mariusz@…>

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