Adam Johnson

And here: http://www.cnblogs.com/clowwindy/archive/2010/09/11/django_timestamp_field.html

And here: http://stackoverflow.com/questions/11332107/timestamp-fields-in-django

Since Django 1.10 just deprecated the `__search` method and added [postgres fulltext search expressions](https://docs.djangoproject.com/en/1.10/releases/1.10/#full-text-search-for-postgresql) we should follow suit and add the expressions!

How-to http://varokism.blogspot.co.uk/2011/01/20-to-50-improvement-in-mariadb-53.html

So this isn't possible with `mysqlclient`/`MySQLdb` - there is no (binary) API for the handler statements. The only thing I know that implements prepared statements is the (kinda dead) `oursql`...

Re: edit 2, that seems like it shouldn't be necessary as both vars should be lists. Can you give the full traceback? Where did the `tuple` come from? Transforms inside...

Huh. It looks like this might be a bug in django itself, the subquery on the left hand side is what's returning its params in a tuple. And indeed it...

Version 3.2.0 treats everything as tuples, try that.

@javiplx I am not sure how that MongoDB ORM issue aligns with here. Can yuo make a PR for your patch, including a test that fails before and passes after?

> I wasn't even aware that it was mongodb for django. It's not even for Django. They just happened to copy the Django ORM for their MongoDB ORM.