#36077: Incorrect mention of falsey primary key values in save() documentation
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: closed
Component: Documentation | Version: 5.1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"d66137b39b1503ca3d4d4fac687251adbc845068" d66137b3]:
{{{#!CommitTicketReference repository=""
revision="d66137b39b1503ca3d4d4fac687251adbc845068"
Fixed #36077 -- Corrected docs on pk value where Model.save() executes an
UPDATE.
The empty string is no longer special-cased since
c2ba59fc1da5287d6286e2c2aca4083d5bafe056.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36077#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701945f2bb9de-be1a2fe5-2694-44f7-9482-f430b6515101-000000%40eu-central-1.amazonses.com.
