You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have to use Windows authentication in production, but I see you removed support for using the original ADO driver in 31b1ffb. Perhaps because it was broken and tricky to actually use or test due to the dependancy on python-tdb?
It so happens I fixed it locally and got django-sqlserver up and running on Django 1.11 (which django-mssql doesn't support) with the ADO driver, only to pull and discover that you removed it.
So, my question is: Is it possible to use Windows authentication with the PyTDB driver, and if so, would you perhaps consider documenting it? If not, would you consider a patch to revive ADO support? After all, django-mssql doesn't seem all that active, and it'd be nice to use one driver everywhere.
The text was updated successfully, but these errors were encountered:
We have to use Windows authentication in production, but I see you removed support for using the original ADO driver in 31b1ffb. Perhaps because it was broken and tricky to actually use or test due to the dependancy on
python-tdb
?It so happens I fixed it locally and got
django-sqlserver
up and running on Django 1.11 (whichdjango-mssql
doesn't support) with the ADO driver, only to pull and discover that you removed it.So, my question is: Is it possible to use Windows authentication with the PyTDB driver, and if so, would you perhaps consider documenting it? If not, would you consider a patch to revive ADO support? After all,
django-mssql
doesn't seem all that active, and it'd be nice to use one driver everywhere.The text was updated successfully, but these errors were encountered: