I would definitely get behind official support for SQL Server. The company
I work for is all about SQL Server and not willing to consider other
options. Right now we are using the django-mssql-backend:
https://github.com/ESSolutions/django-mssql-backend which works pretty well
for our use case, but official SQL Server support would be great.

Dave

On Wed, Feb 12, 2020 at 5:44 PM Adam Johnson <m...@adamj.eu> wrote:

> Microsoft posted in 2015 and there was an update last April about a
> working backend that claims support for 3.0:
> https://groups.google.com/d/msg/django-developers/FbBcUCzrSZo/EoFNbR2BDgAJ
>
> Any support in core would need clear evidence of widespread demand. I
> don't think there's much demand - e.g. that backend has only 38 stars on
> GitHub.
>
> On Wed, 12 Feb 2020 at 20:33, Martynas Puronas <marty...@puronas.me>
> wrote:
>
>> Hey, I've been working on adding support for SQL Server to Django, since
>> the package currently being linked recommended in Django's documentation
>> has been abandoned (as well as a few others seem to be either abandoned or
>> do not have the test suite passing), and I have made some significant
>> progress on it (all of admin tests are passing, as well as aggregates,
>> inserts, deletes, updates and a few other modules). I was wondering if you
>> would be open to adding support for SQL Server, provided I could make sure
>> that the entire test suite passes, and documentation is written? Or does
>> this go against Django's technical roadmap and you would rather keep
>> support for SQL Server outside of Django in a separate package?
>>
>> Thanks!
>>
>> --
>> 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/6d98459d-9616-4343-b4fe-3eabd9ef131f%40googlegroups.com
>> <https://groups.google.com/d/msgid/django-developers/6d98459d-9616-4343-b4fe-3eabd9ef131f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> Adam
>
> --
> 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/CAMyDDM2hna%2B%3D%3DPuHKjH0xzJmEGzReDP3DFyJwX2L2bt%3DtsR97Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-developers/CAMyDDM2hna%2B%3D%3DPuHKjH0xzJmEGzReDP3DFyJwX2L2bt%3DtsR97Q%40mail.gmail.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/CADR4itK8A5Cc_NEYBZvtiECJcm4PnqFhjDL_7a2OnFBTDs2%2BNQ%40mail.gmail.com.

Reply via email to