Re: [Django] #12033: ModelAdmin.search_fields throws exception when using @ for non mysql database
Django
database
-------------------------------------+-------------------------------------
Reporter: hvdklauw | Owner: nobody
Type: New | Status: new
feature | Component: contrib.admin
Milestone: | Severity: Normal
Version: 1.1 | Keywords: search_fields,
Resolution: | fulltext, mysql, sqlite, error
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* ui_ux: => 0
* easy: => 0
Comment:
Note that full-text search will work in backends other than MySQL if they
implement `fulltext_search_sql`, which is the topic of #3254.
--
Ticket URL: <https://code.djangoproject.com/ticket/12033#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
database
-------------------------------------+-------------------------------------
Type: New feature | Status: assigned
Component: contrib.admin | Version: 1.1
Severity: Normal | Resolution:
Keywords: search_fields, | Triage Stage: Accepted
fulltext, mysql, sqlite, error | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by szczav):
* status: new => assigned
* owner: nobody => szczav
--
Ticket URL: <https://code.djangoproject.com/ticket/12033#comment:4>
Django
database
-------------------------------------+-------------------------------------
Reporter: hvdklauw | Owner:
Component: contrib.admin | Version: 1.1
Severity: Normal | Resolution:
Keywords: search_fields, | Triage Stage: Accepted
fulltext, mysql, sqlite, error | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by szczav):
* status: assigned => new
* owner: szczav =>
--
Ticket URL: <https://code.djangoproject.com/ticket/12033#comment:5>
Django
database
-------------------------------------+-------------------------------------
Type: New feature | Status: closed
Component: contrib.admin | Version: 1.1
Severity: Normal | Resolution: wontfix
Keywords: search_fields, | Triage Stage: Accepted
fulltext, mysql, sqlite, error |
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => wontfix
Comment:
The MySQL specific `__search` lookup and its `@` search field reference
have been deprecated.
It's now possible to override the `ModelAdmin.get_search_results()` to
provide backend agnostic FTS.
--
Ticket URL: <https://code.djangoproject.com/ticket/12033#comment:6>
Django
database
-------------------------------------+-------------------------------------
Reporter: Harro | Owner: (none)
Type: New feature | Status: closed
Component: contrib.admin | Version: 1.1
Severity: Normal | Resolution: wontfix
Keywords: search_fields, | Triage Stage: Accepted
fulltext, mysql, sqlite, error |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Actually the `@` -> `__search` conversion is still present in
`get_search_result()` so could implement a `SearchLookup` that you
register to both `CharField` and `TextField` and you could implement it on
SQLite.
--
Ticket URL: <https://code.djangoproject.com/ticket/12033#comment:7>