#36259: Unsaved related object with primary_key=True field does not raise usaved
object error
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Clifford
| Gama
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* cc: Csirmaz Bendegúz, Simon Charette (added)
* keywords: _is_pk_set =>
* severity: Release blocker => Normal
* stage: Unreviewed => Accepted
* summary: `_is_pk_set()` is incorrectly used to check for unsaved models.
=>
Unsaved related object with primary_key=True field does not raise
usaved object error
Comment:
Hi Clifford, thank you for the report!
This is also failing on 5.1, so this is not a regression introduced by
5.2. Note that the example test case isn't using CompositePrimaryKeys
--
Ticket URL: <https://code.djangoproject.com/ticket/36259#comment:5>
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/01070195a341b836-18f4a1cd-2c89-4200-b9d3-a5efc5a63181-000000%40eu-central-1.amazonses.com.
