Hi Warren, given that the current django-mssql-backend maintainers might not be reading here I'd suggest you open a ticket on the repository to get in contact with them. It also might be a good idea to re-evaluate this thread (and possibly at Microsoft internally) to see why the last approaches failed and what can be done better this time. Personally I'd also suggest to work "openly" with the existing fork from ESSolutions and submit PRs there for testing pipelines etc (I assume you'd want to run them on azure or something and having that integration developed in the open would certainly provide good guidance for other projects). I am not sure what internal compliance entails, but please keep in mind that this is an open source project used already by people and compliance to some internal microsoft standards might not be something people care about or need.
I am excited to see your PRs against the repo. Cheers, Florian On Friday, November 27, 2020 at 2:40:18 AM UTC+1 vwa...@gmail.com wrote: > Hi All, > > Microsoft has now committed ongoing resources towards improving MSSQL and > Azure SQL support for Django. We're currently focused on internal > compliance and forking the ESSolutions django-mssql-backend > <https://github.com/ESSolutions/django-mssql-backend>, adding testing > pipelines, refactoring the Django DB engine naming convention, and > addressing current test suite errors. > > We'd love to hear from current mssql-backend maintainers as well as > mssql-backend users about the existing issues and feature requests that we > should be prioritizing. > > We looking forward to engaging the community and working towards MSSQL as > a first-class supported backend for Django. > > -Warren > > On Wednesday, 4 December 2019 at 07:05:25 UTC-8 Tim Allen wrote: > >> 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/0eb67fc9-8edd-4774-9e60-7233a2cabb4dn%40googlegroups.com.
