#34099: update_or_create() not saving data assigned in a model's save() method
-------------------------------------+-------------------------------------
     Reporter:  Phil Gyford          |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Simon Charette):

 > I think it would still be worth to call out in the release notes as a
 possibly backwards incompatible change?

 Agreed. Ideally we'd have examples on how to properly override `save()` as
 well but a release note and maybe an `admonition` to the `update-or-
 create` / `versionchanged` could be valuable?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34099#comment:12>
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 on the web visit 
https://groups.google.com/d/msgid/django-updates/010701841bad11e9-6a9c60bb-f5b6-4cf4-81bf-0de6f91a056b-000000%40eu-central-1.amazonses.com.

Reply via email to