#15831: Migration 1.2.5 to 1.3 breaks Apps
------------------------+--------------------------------
Reporter: dev66@… | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Forms
Version: 1.3 | Severity: Release blocker
Keywords: Forms Save | Triage Stage: Unreviewed
Has patch: 0 |
------------------------+--------------------------------
We have the impression, that the form save behavior was revamped and works
differently now.
observed behavior in v1.3:
form.save() does not always return the primary key of the object saved to
the database table.
why "not always"?
1) f = form(instance=None)
works. form.save() returns an instance object with the correct pk from the
database.
2) f = form(instance=SomeModelObject())
form.save() returns an instance object but the pk of the instance is None.
however, the instance is correctly saved to the database.
Is this behavior intended?
TIA
--
Ticket URL: <http://code.djangoproject.com/ticket/15831>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
