AFAIK, the *supports_microsecond_precision* feature is still needed by *django-pyodbc-azure*, because of SQL Server's, ahem, creative datetime fields.
See: https://github.com/michiya/django-pyodbc-azure/blob/4df37f3ec40abaf1aca608e1922a93073db8f144/sql_server/pyodbc/operations.py#L474 There is a fair amount of logic needed (based off of the FreeTDS version and SQL Server version) necessary as well to determine whether to use SQL Server's *datetime* or *datetime2:* https://github.com/michiya/django-pyodbc-azure/blob/4df37f3ec40abaf1aca608e1922a93073db8f144/sql_server/pyodbc/base.py#L80 https://github.com/michiya/django-pyodbc-azure/blob/4df37f3ec40abaf1aca608e1922a93073db8f144/sql_server/pyodbc/base.py#L461 It may be possible to modify *django-pyodbc-azure* to work another way, but for that I would defer to Michaya. I haven't used any of the other pyodbc forks in years, as *django-pyodbc-azure* is very well maintained and supports both SQL Server and Azure. On Saturday, August 26, 2017 at 11:09:42 AM UTC-4, Tim Graham wrote: > > MySQL 5.5 is end-of-life in December 2018. Usually we drop support for a > particular database version in the Django release prior to the end-of-life > date [0], so that would mean dropping support in Django 2.1 (released > August 2018). We don't have MySQL 5.5 testing in our continuous integration > servers and in local testing, I noticed some GIS test failures with MySQL > 5.5. Before investigating them, I thought I'd ask to see if there might be > consensus to drop support for MySQL 5.5 in Django 2.0 instead of 2.1. I'd > guess anyone using MySQL 5.5 users would stick with Django 1.11 LTS or > older. > > https://github.com/django/django/pull/8980 shows the cleanups for removal > of MySQL 5.5 support. Also, MySQL 5.5 is the last usage among the built-in > database backends for the supports_microsecond_precision database feature > so there's a chance that could be removed also, though I found usage of it > in django_pyodbc [1]. > > [0] https://code.djangoproject.com/wiki/SupportedDatabaseVersions -- though > we've made some exceptions like dropping support earlier for Oracle 11, > https://groups.google.com/forum/#!topic/django-developers/IawbBWzPXaA/discussion > [1] https://github.com/lionheart/django-pyodbc/issues/87 > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6a97bf2b-3a90-4f68-ba34-86b39a649d64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
