#16063: Problem with searching in m2m fields in inherited model
--------------------------------------+------------------------------------
Reporter: Evgeny Sizikov | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.admin | Version: 1.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by goblinJoel):
* cc: goblinJoel (added)
Comment:
This is old, but I think it's a good idea. It's still a problem in Django
1.11, and I didn't see any changes in the 2.x code that looked relevant.
It can end up devouring storage space larger than the db itself and suck
up CPU to the point where the database system becomes unresponsive or runs
out of storage.
I'm not sure whether I should be making unilateral edits, so I suggest
renaming to something like:
**Multi-word admin searches hang with foreign keys in search_fields**
Related:
* https://github.com/django/django/pull/7277 with a similar solution
* https://groups.google.com/forum/#!topic/django-developers/V8M49P326dI
thread related to above PR
* https://code.djangoproject.com/ticket/27864 more recent attempt to
mitigate by limiting how many search terms you can use
--
Ticket URL: <https://code.djangoproject.com/ticket/16063#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.26377d5b87fa0f63a5f44011633c041e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
