#26285: Deprecate the MySQL specific __search lookup
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: master
(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 timgraham):
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/6208 PR]. As noted there, a
remaining problem is that the `__search` lookup is
[https://github.com/django/django/blob/d5f89ff6e873dbb2890ed05ce2aeae628792c8f7/django/contrib/admin/options.py#L888-L889
used by the admin]
for the `search_fields = ['@fieldname']` syntax. I think #26184 would
allow removing that code.
If we don't want to make that ticket a prerequisite of this one, I suppose
we could leave that code for now, even if the `search` lookup is removed
from Django itself.
--
Ticket URL: <https://code.djangoproject.com/ticket/26285#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.b5298fb55e23310f2a40fffc30f802d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
