#33586: Cannot delete object (A) referenced by another object (B) if said object
(A) has a foreign key to a custom user.
-------------------------------+------------------------------------
Reporter: Jeremy Poulin | Owner: Bhuvnesh
Type: Bug | Status: assigned
Component: Migrations | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Carlton Gibson):
Reading the issue, you've not addressed the points in
https://code.djangoproject.com/ticket/33586#comment:19 (and previous to
that).
> Do you have any numbers to support your performance claim? This is
important as you are forcing the eviction of a cache layer dedicated to
making performance better.
Creating some benchmarks (using pyperf perhaps) looks like a step forward.
From comment:15
> You should be able to demonstrate and explain why this change is needed
by writing a minimal test case from the issue reported by Jeremy that can
be integrated to the suite and demonstrates the origin of the issue. From
there we'd need numbers on the effect it has has on performance to
determine if that's the right place to make the changes.
So there's a couple of avenues already, but there were other points made.
--
Ticket URL: <https://code.djangoproject.com/ticket/33586#comment:22>
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/01070184385fce29-443eeb18-096b-4c9c-a5c3-032855c7f22d-000000%40eu-central-1.amazonses.com.
