Thanks for the feedback Adam. Your suggestions are actionable and potential sponsorship has been raised for discussion as recently as this week (no promises or strings attached).
We'll reach out to you directly if we have any direct follow-up on filling in the feature gaps. -Warren On Thursday, 31 March 2022 at 10:07:09 UTC-7 Adam Johnson wrote: > Hi again Warren, > > Good work on maintaining the backend. > > Merging the backend could be a good end goal, but I'd be concerned about > merging it in the current state. The README lists many features that don't > work: https://github.com/microsoft/mssql-django#limitations . This list > includes some key features like timezones, constraints, and renaming models > with foreign keys. The text also has very limited detail on the problems, > for example: "Timezones, timedeltas not fully supported" - what doesn't > work? > > For comparison, the Cockroach DB backend lists its differences and > deficiencies in much more detail: > https://github.com/cockroachdb/django-cockroachdb#known-issues-and-limitations-in-cockroachdb-212x-and-earlier > > . Although the list there is physically longer, the issues are much more > niche. This gives me the impression that the Cockroach DB backend has much > better feature coverage. > > Merging any code into core Django significantly limits the ability to > iterate on it, given the strict release cycle. Users would have to wait for > a new Django version to get improvements. I think that whilst the MS SQL > backend is missing coverage for key features, effort would be better spent > improving it than on any merge proposal. > > Adam > > P.S. I still don't see Microsoft on the sponsorship page: > https://www.djangoproject.com/fundraising/ 😉 > > > On Thu, Mar 31, 2022 at 5:30 PM Warren Chu <vwa...@gmail.com> wrote: > >> Hi All, >> >> There is increasing interest within Microsoft to have stronger ties >> between Microsoft SQL Server and Django. As you may be aware, Microsoft and >> their connectivity teams have been managing the 3rd party backend for >> "mssql-django" for over a year now at: >> https://github.com/microsoft/mssql-django >> >> Inclusion of SQL Server as a 1st party backend is viewed as a potential >> big milestone in that regard. >> >> @adamjohnson mentioned a year ago that ideally the community would like >> to see multiple years of ongoing Microsoft support before considering >> merging as a 1st party backend. >> >> We'd love to hear thoughts and feedback around the possibility of moving >> forward with a DEP enhancement proposal, with a commitment from Microsoft >> to providing continued dedicated support for the 1st party backend through >> the Django project itself (rather than the 3rd party repo). >> >> Cheers, >> Team Microsoft >> >> -- >> 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-develop...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/0c6ca059-d50e-4c84-bef6-ab0742fc4fa9n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/0c6ca059-d50e-4c84-bef6-ab0742fc4fa9n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/b8cf251e-1719-4f9e-95ed-4f65349370b8n%40googlegroups.com.
