Code

Opened 3 years ago

Closed 3 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: UI/UX:

Description

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

Attachments (0)

Change History (1)

comment:1 Changed 3 years ago by russellm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to needsinfo
  • Status changed from new to closed

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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.