#27222: Refresh fields that are expressions after Model.save()
-------------------------------------+-------------------------------------
     Reporter:  holvianssi           |                    Owner:  Simon
                                     |  Charette
         Type:  New feature          |                   Status:  assigned
    Component:  Database layer       |                  Version:  1.10
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"292b9e6fe8f23491680d9cc60f328562e2b1c823" 292b9e6f]:
 {{{#!CommitTicketReference repository=""
 revision="292b9e6fe8f23491680d9cc60f328562e2b1c823"
 Refs #27222 -- Adapted RETURNING handling to be usable for UPDATE queries.

 Renamed existing methods and abstractions used for INSERT … RETURNING
 to be generic enough to be used in the context of UPDATEs as well.

 This also consolidates SQL compliant implementations on
 BaseDatabaseOperations.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/27222#comment:13>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/01070198f1ff552b-afdabb31-5313-48b7-a3cf-35abbddaf4e6-000000%40eu-central-1.amazonses.com.

Reply via email to