I agree it would be great to get some help running the Django tests on 
Windows. I run them in a local virtual machine every so often, but I would 
love to be able to delegate fixing Windows issues. Meet, can your team 
provide ongoing help with fixing Windows-specific issues in Django, even if 
they aren't related to MSSQL/Azure? That is something where we've had a 
hard time finding volunteers to help with and is obviously important if we 
want to claim 1st-class support for Windows.

I don't have any experience with MSSQL/Azure, but I could probably attend 
the October 13-15 event at Microsoft if you think my participation would be 
valuable and if the DSF were to approve the time commitment as part of the 
fellow duties.

On Saturday, August 22, 2015 at 6:28:58 AM UTC-4, Aymeric Augustin wrote:
>
> Hello Meet,
>
> On 21 août 2015, at 19:39, Meet Bhagdev <meetb...@gmail.com <javascript:>> 
> wrote:
>   
>
> We’d love for Django users to have a solid option to use MSSQL and Azure 
> SQL if they wish, and it would be great to make this option a reality.
>
>
> Even though this isn’t what you’re asking for :-) I’ll take this 
> opportunity to summarize the landscape for combining Django and MSSQL / 
> Azure SQL, as far as I understand it.
>
> There’s a good option for MSSQL or Azure SQL users running Django on 
> Windows: https://bitbucket.org/Manfre/django-mssql. (Perhaps it could be 
> made even better, but from my perspective, it’s solid.)
>
> There’ve been talks of making it more official. But no consensus has been 
> found yet. The main difficulty is that very few Django committers use 
> Windows as a primary OS, perhaps two out of fifty. Most of us don’t even 
> own a Windows license. We face a similar issue with our continuous 
> integration. Currently it’s running on Linux. We lack the skills and money 
> to run Windows and SQL Server. (Sponsoring in the form of Azure SQL credits 
> for the purpose of testing Django may solve parts of this problem, if using 
> a remote database isn’t too slow for test suite’s workload.)
>
> There isn’t such a clear story for running Django on Linux. This led me to 
> write https://github.com/aaugustin/django-pymssql. Alternatives include 
> https://github.com/denisenkom/django-sqlserver and 
> https://github.com/lionheart/django-pyodbc.
>
> I can’t say django-pymssql is solid. But it works and it shows that 
> django-mssql could be made cross-platform with limited effort, subject to 
> the quality of the underlying libraries: 
> https://github.com/pymssql/pymssql and https://github.com/FreeTDS/freetds. 
> However my interest has faded since I left the company where I had this use 
> case. Furthermore testing is very painful. I'm running SQL Server Express 
> in a VM. Tests are about 20 times slower than with PostgreSQL or MySQL. As 
> a consequence Django’s test suite took about 2 hours. 
>
> I appreciate the invitation. Unfortunately I live a bit too far to make 
> the trip conveniently. I’m still interested in making Django work out of 
> the box with SQL Server like it does with Oracle. (That’s for historical 
> reasons: some people gathered and made it happen). I believe 
> interoperability with SQL Server is key for using Django in the 
> medium-sized companies where SQL Server is the obvious choice of database 
> server.
>
> I hope this helps. Thanks for reaching out!
>
> -- 
> Aymeric.
>
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/f0ac4f4c-2da0-4ba6-8b1f-72bdd148e61c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to