#30491: Document changing primary key behavior in "How Django knows to UPDATE
vs.
INSERT" section.
--------------------------------------+------------------------------------
Reporter: Brad | Owner: Brad
Type: Cleanup/optimization | Status: assigned
Component: Documentation | Version: 2.2
Severity: Normal | Resolution:
Keywords: save | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by felixxm):
* status: new => assigned
* owner: nobody => Brad
* stage: Unreviewed => Accepted
Comment:
This note is already in `topics/db/models` and `ref/models/fields`, but I
agree that we can add it in one more place.
--
Ticket URL: <https://code.djangoproject.com/ticket/30491#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 [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.760f948f9ee77e266f5707641b56611c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
