#36077: Incorrect mention of falsey primary key values in save() documentation
-------------------------------------+-------------------------------------
Reporter: Jacob | Owner: Jacob Walls
Walls |
Type: | Status: assigned
Cleanup/optimization |
Component: | Version: 5.1
Documentation |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
This
[https://github.com/django/django/blob/8c118c0e00846091c261b97dbed9a5b89ceb79bf/docs/ref/models/instances.txt#L556
sentence] in the description of `save()` is outdated since
c2ba59fc1da5287d6286e2c2aca4083d5bafe056. We only consider a pk set if
it's not None, as opposed to the empty string (before that commit) nor
other falsey values like 0 (since forever, AFAICT).
[https://github.com/django/django/pull/19019 PR]
Found during
[https://github.com/django/django/pull/19008#discussion_r1907945288 PR
discussion]
--
Ticket URL: <https://code.djangoproject.com/ticket/36077>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701944b8e33c6-67c3fe1e-1ce6-4981-b193-d027c0b2a03e-000000%40eu-central-1.amazonses.com.
