Opened 8 years ago

Closed 8 years ago

#15831 closed Bug (needsinfo)

Migration 1.2.5 to 1.3 breaks Apps

Reported by: dev66@… Owned by: nobody
Component: Forms Version: 1.3
Severity: Release blocker Keywords: Forms Save
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


We have the impression, that the form save behavior was revamped and works differently now.

observed behavior in v1.3: does not always return the primary key of the object saved to the database table.
why "not always"?

1) f = form(instance=None)
works. returns an instance object with the correct pk from the database.

2) f = form(instance=SomeModelObject()) 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?


Change History (1)

comment:1 Changed 8 years ago by Russell Keith-Magee

Resolution: needsinfo
Status: newclosed

There haven't been any intentional changes to form behavior, and you haven't provided enough detail to identify a specific use case that points to a bug.

If you want to ask a question to clarify what is (or isn't) working, please do so on the django-users mailing list. Trac isn't a service to help you track down bugs -- it's for tracking the bugs that we can verify exist.

Note: See TracTickets for help on using tickets.
Back to Top