Missing support for microsecond precision in ORM DateTimeField

[jorisroovers]

Micro precision support is disabled in the DatabaseFeatures class in base.py

supports_microsecond_precision = False

See here:

django-pyodbc/django_pyodbc/base.py

Line 57 in ba2daee

supports_microsecond_precision = False

You can use the following as a workaround (place this e.g. in local_settings.py):

from django_pyodbc.base import DatabaseFeatures
DatabaseFeatures.supports_microsecond_precision = True

[timgraham]

supports_microsecond_precision = False was added in 39128a7. Does Azure not support microseconds @michiya? MySQL 5.5 is the last database for a built-in database backend that doesn't support microseconds. When that version is dropped, it would be more difficult to maintain correct usage of supports_microsecond_precision in tests since nothing in our CI will be testing the flag (actually we don't test with MySQL 5.5 right now either). Ideally, we could drop the supports_microsecond_precision feature and require third-party backends to write their own logic to handle the lack of microsecond support, if that's still a limitation.