I don't think "primary key size" is something that's even within
consideration for 99% of django apps. Sure a few more bytes are going to be
wasted here, but you could argue the same that the default AutoField was
already too big for most models that have 100's of instances and could use
even a one
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
