#27222: Refresh fields that are expressions after Model.save()
-------------------------------------+-------------------------------------
Reporter: holvianssi | Owner: Simon
| Charette
Type: New feature | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"4fcc2883faa8e33152d9e45744354cff35636975" 4fcc2883]:
{{{#!CommitTicketReference repository=""
revision="4fcc2883faa8e33152d9e45744354cff35636975"
Refs #27222 -- Restored Model.save()'s refreshing of db_returning fields
even if a value is set.
The logic could likely be adjusted to assign the pre_save value in most
cases
to avoid the database transit but it could break in subtle ways so it's
not
worth the complexity it would require.
Regression in 94680437a45a71c70ca8bd2e68b72aa1e2eff337.
Co-authored-by: Tim Graham <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27222#comment:18>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701995782c622-5bbe6b21-39d3-4827-8851-6d9f8992b3c7-000000%40eu-central-1.amazonses.com.
