#30491: Document changing primary key behavior in "How Django knows to UPDATE
vs.
INSERT" section.
--------------------------------------+------------------------------------
Reporter: Brad | Owner: Brad
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: 2.2
Severity: Normal | Resolution: fixed
Keywords: save | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"67b6cb7723b2765cb776bd59d5603e3e63eefc2e" 67b6cb77]:
{{{
#!CommitTicketReference repository=""
revision="67b6cb7723b2765cb776bd59d5603e3e63eefc2e"
Fixed #30491 -- Clarified when save() on object with pk executes INSERT.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30491#comment:4>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.9eff3a1a93e14d0a9c029e0d2b4ded87%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
