Opened 7 years ago

Last modified 3 years ago

#12033 new New feature

ModelAdmin.search_fields throws exception when using @ for non mysql database

Reported by: Harro Owned by:
Component: contrib.admin Version: 1.1
Severity: Normal Keywords: search_fields, fulltext, mysql, sqlite, error
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


So for the production environment I would really like to use the fulltext search capabilities the @ prefix offers, but for development we hardly use the search anyway. And most people will use sqlite anyway.

Django throwing an exception when using the @ option for a non mysql backend makes it impossible to keep your code the same.

I suggest when using @ for a non mysql backend django throws an error in the error log and the normal search is used.

Change History (5)

comment:1 Changed 7 years ago by Russell Keith-Magee

Triage Stage: UnreviewedAccepted

comment:2 Changed 6 years ago by Peter Baumgartner

Severity: Normal
Type: New feature

comment:3 Changed 5 years ago by Aymeric Augustin

Easy pickings: unset
UI/UX: unset

Note that full-text search will work in backends other than MySQL if they implement fulltext_search_sql, which is the topic of #3254.

comment:4 Changed 4 years ago by szczav

Owner: changed from nobody to szczav
Status: newassigned

comment:5 Changed 3 years ago by szczav

Owner: szczav deleted
Status: assignednew
Note: See TracTickets for help on using tickets.
Back to Top