#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 |
Pull Requests: | |||
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 , 6 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 6 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 6 years ago
Has patch: | set |
---|
comment:4 by , 6 years ago
Patch needs improvement: | set |
---|
comment:5 by , 6 years ago
Patch needs improvement: | unset |
---|
comment:6 by , 6 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
Note:
See TracTickets
for help on using tickets.
PR