ModelAdmin.search_fields throws exception when using @ for non mysql database
|Reported by:||hvdklauw||Owned by:|
|Severity:||Normal||Keywords:||search_fields, fulltext, mysql, sqlite, error|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||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 russellm
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Accepted
comment:4 Changed 3 years ago by szczav
- Owner changed from nobody to szczav
- Status changed from new to assigned