#31588: Unclear behaviour for ModelForms
-------------------------------------+-------------------------------------
     Reporter:  Vladislav            |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Forms                |                  Version:  3.0
     Severity:  Normal               |               Resolution:  invalid
     Keywords:  forms                |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Hi. Thanks for the report.

 The ''official decision'', the recommended way of doing it is to call
 `save()` with `commit=False`, then make your modifications before saving
 the instance finally.
 This is documented in
 [https://docs.djangoproject.com/en/3.0/topics/forms/modelforms/#the-save-
 method the save method docs]. See the example there of modifying an author
 in this way.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31588#comment:1>
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/066.c82eb75ad80ea0fa1cdffdfe3a2baf1d%40djangoproject.com.

Reply via email to