Hi Sean, just an update from what I know.

We are still waiting for a reply from Microsoft. They're a large company, 
so understandably, it takes a little while.


For now, if people need to get onto Django 2.2 for long term support (which 
will last until April, 2022), you can use this package:

https://github.com/ESSolutions/django-mssql-backend I've been running it in 
production for months without incident. Of course, YMMV.


If Microsoft and/or the DSF end up wanting to bring support under the 
Django umbrella, the django-mssql-backend repository is a possible starting 
point, IMHO.

The django-mssql-backend is currently being developed and support for 
Django 3.0 is being worked on: ESSolutions/django-mssql-backend#18 
<https://github.com/ESSolutions/django-mssql-backend/issues/18>


Regards,


Tim

On Monday, December 2, 2019 at 11:03:56 AM UTC-5, Sean Martz wrote:
>
> Hello,
>
> It seems like this issue has lost momentum. Is this still something that's 
> on anyones radar? It looks like django-pyodbc-azure is not actively 
> maintained anymore (it looks like Michaya has taken a hiatus from GitHub). 
> It also looks like there's a small community potentially popping up that's 
> interested in first class MSSQL Server support for Django. (
> https://github.com/FlipperPA/django-mssql-backend). Is Microsoft still 
> interested in committing resources to this goal? In my situation, it would 
> be a lot easier to sell stakeholders and decision makers on Django if it 
> had first class support for MSSQL Server.
>
> For what it's worth, Django-pyodbc-azure is still working well.
>
> Cheers,
> Sean
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/3683f606-ad18-4935-85c8-8ca3ea18fecc%40googlegroups.com.

Reply via email to