#31219: Raising error about protected related objects can crash.
-------------------------------------+-------------------------------------
Reporter: Matthias Kestenholz | Owner: Matthias
| Kestenholz
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Matthias Kestenholz):
I added another commit on top
(https://github.com/django/django/pull/12394/commits/42fb622f8895f59ff6ad76b761c1eb9b41fd9549)
which tests the `RESTRICT` case.
The `RESTRICT` case shows a foreign key which actually exists, but it does
not point at the `P` object yet but at the intermediate `R` object. It
does not crash because there is no code accessing the first restricted
object as is the case with protected objects.
--
Ticket URL: <https://code.djangoproject.com/ticket/31219#comment:6>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/067.0373d6b95427e9fb61cd73147b43b38f%40djangoproject.com.
