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

[Harro]

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.

[Aymeric Augustin]

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

[Simon Charette]

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.

[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.