Re: Increasing support for Microsoft SQL Server

[Adam Johnson]

Hi Warren,

Thanks for looking at working on this. SQL Server is (I believe) the most
popular not-in-core DB backend. Carlton's suggestions are solid.

I'd also point you to reading the old mailing list posts:
https://groups.google.com/g/django-developers/search?q=microsoft%20sql . I
recall there was a few years ago a previous Microsoft effort to support
Django + SQL Server, and some people including the author of django-mssql,
Michael Manfre, were flown out to Redmond(?) for some discussions. But I
don't know what came of that.

Thanks,

Adam

On Sun, 8 Nov 2020 at 11:32, Carlton Gibson 
wrote:

> HI Warren.
>
> Thanks for your mail.
>
> 1 - How can we best collaborate?
>
>
> I’d guess the best thing would be to communicate with the existing
> contributors and ask where resource would be best spent.
>
> I’m not mssql-server user myself, but first question I’d be asking is
> where is the backend not feature-equivalent to the backends in core? (I
> can’t tell you that I’m afraid.) A good test would be whether it passes the
> django test suite?
>
> Kind Regards,
>
> Carlton
>
>
>
>
> On 3 Nov 2020, at 21:50, Warren Chu  wrote:
>
> Hi All,
>
> Microsoft has commissioned internal resources, of which I'm a member, to
> drive development and support of an open source Microsoft SQL Server
> backend solution for Django. This project would exist under the
> github.com/microsoft organization.
>
> We recognize there is an existing and active project [
> https://github.com/ESSolutions/django-mssql-backend], and we'd like to
> solicit ideas and feedback from the Django community on the best way to
> proceed.
>
> Some initial questions we have are:
>
> 1 - How can we best collaborate?
> 2 - What issues or challenges are most pressing to make MSSQL-Django work
> better for you?
>
> Thanks,
> Warren
>
> --
> 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/25102379-5df3-4c55-a786-ac9acda20b13n%40googlegroups.com
> 
> .
>
>
> --
> 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/52921BEA-3ACE-4C49-995A-FD8F3597352C%40gmail.com
> 
> .
>


-- 
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/CAMyDDM2-%2Bi-ddAa0sP2-s9-pnNdzr2mf2e8PDpWkWAerjD6DJA%40mail.gmail.com.

Re: Increasing support for Microsoft SQL Server

[uri...@gmail.com]

This thread in particular, I think.
https://groups.google.com/g/django-developers/c/FbBcUCzrSZo/m/EoFNbR2BDgAJ
On Monday, November 9, 2020 at 11:56:01 PM UTC-10 Adam Johnson wrote:

> Hi Warren,
>
> Thanks for looking at working on this. SQL Server is (I believe) the most 
> popular not-in-core DB backend. Carlton's suggestions are solid.
>
> I'd also point you to reading the old mailing list posts: 
> https://groups.google.com/g/django-developers/search?q=microsoft%20sql . 
> I recall there was a few years ago a previous Microsoft effort to support 
> Django + SQL Server, and some people including the author of django-mssql, 
> Michael Manfre, were flown out to Redmond(?) for some discussions. But I 
> don't know what came of that.
>
> Thanks,
>
> Adam
>
> On Sun, 8 Nov 2020 at 11:32, Carlton Gibson  wrote:
>
>> HI Warren. 
>>
>> Thanks for your mail. 
>>
>> 1 - How can we best collaborate?
>>
>>
>> I’d guess the best thing would be to communicate with the existing 
>> contributors and ask where resource would be best spent. 
>>
>> I’m not mssql-server user myself, but first question I’d be asking is 
>> where is the backend not feature-equivalent to the backends in core? (I 
>> can’t tell you that I’m afraid.) A good test would be whether it passes the 
>> django test suite?
>>
>> Kind Regards,
>>
>> Carlton
>>
>>
>>
>>
>> On 3 Nov 2020, at 21:50, Warren Chu  wrote:
>>
>> Hi All,
>>
>> Microsoft has commissioned internal resources, of which I'm a member, to 
>> drive development and support of an open source Microsoft SQL Server 
>> backend solution for Django. This project would exist under the 
>> github.com/microsoft organization.
>>
>> We recognize there is an existing and active project [
>> https://github.com/ESSolutions/django-mssql-backend], and we'd like to 
>> solicit ideas and feedback from the Django community on the best way to 
>> proceed.
>>
>> Some initial questions we have are:
>>
>> 1 - How can we best collaborate?
>> 2 - What issues or challenges are most pressing to make MSSQL-Django work 
>> better for you?
>>
>> Thanks,
>> Warren
>>
>> -- 
>> 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/25102379-5df3-4c55-a786-ac9acda20b13n%40googlegroups.com
>>  
>> 
>> .
>>
>>
>> -- 
>> 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/52921BEA-3ACE-4C49-995A-FD8F3597352C%40gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
> 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/d2edd833-e86b-4693-b564-505184cd3bb9n%40googlegroups.com.

Adding a security concerned feature

[Shoury Sharma]

Hello everyone!
I was going though idea of admin page but sometimes it can be a security 
concern regarding access of admin stuff by URL/admin.
I would therefore like to give a suggestions regarding the URL/admin to be 
some key which only the owners would have access to so the user can never 
have anyway to check admin by penetrating into it in any malicious way. 
Generous regards,
Shoury Sharma

-- 
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/46bf01ff-dc32-47ff-92bc-c56c260a9f29n%40googlegroups.com.

Re: Adding a security concerned feature

[Arvind Nedumaran]

The one I follow is to set an environment variable to see if it’s a 
public facing instance or a private one (disconnected from the internet) 
and use that as a condition, which when true will add some urls.


It’s the same pattern you’ll follow when using something like Django 
debug toolbar - where you check if debug is true and if it is, you add 
some more urls to the root urlconf conf.


Hope that helps.

P.s. This is the mailing list for contributions to Django itself. 
Questions about how to use django are better suited in the Django Users 
mailing list or the forums.


Onward,
Arvind


On 10 Nov 2020, at 14:46, Shoury Sharma wrote:


Hello everyone!
I was going though idea of admin page but sometimes it can be a 
security

concern regarding access of admin stuff by URL/admin.
I would therefore like to give a suggestions regarding the URL/admin 
to be
some key which only the owners would have access to so the user can 
never
have anyway to check admin by penetrating into it in any malicious 
way.

Generous regards,
Shoury Sharma

--
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/46bf01ff-dc32-47ff-92bc-c56c260a9f29n%40googlegroups.com.


--
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/10669A3E-5DBB-46C8-8CF3-411C7DC149CC%40gmail.com.

Regarding my first bug fix.

[Nishant Sagar]

This is the first time I'm contributing to an open source and I found a 
ticket and wanted to solve that issue but I don't actually know how to do 
so. Can someone please help me fixing the first bug?
This is the bug I want to work on.

Thank You.
[image: Screenshot 2020-11-11 115512.png]

-- 
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/ee60fb96-b14d-40f1-af85-3312acc0978bn%40googlegroups.com.

Re: Regarding my first bug fix.

[Carlton Gibson]

Hi Nishan. 

This is the exact same query you posted two days ago... — please don't post 
multiple times, that's just spammy. You have to understand that folks can't 
always reply to you instantly. 

Looking at Markus' comment on the ticket, it's a documentation issue, so 
your task is to read through the related tickets and come to understand the 
issue, then look at the docs to see what can be clarified. 

The first bit there is the hard one — understanding the issue — take your 
time, have fun. 

If you hit specific problems, and can explain where you're at, folks can 
often input, but just pointing at an issue isn't likely to get much 
response, as all you're doing there is asking others to do work that they 
probably don't have time for. On the other hand, if you explain the issue, 
you're likely to get a response. 

Hope that helps you begin. 

Kind Regards,

Carlton


On Wednesday, 11 November 2020 at 07:30:46 UTC+1 nishan...@gmail.com wrote:

> This is the first time I'm contributing to an open source and I found a 
> ticket and wanted to solve that issue but I don't actually know how to do 
> so. Can someone please help me fixing the first bug?
> This is the bug I want to work on.
>
> Thank You.
> [image: Screenshot 2020-11-11 115512.png]
>

-- 
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/01cac1d6-bea1-438d-a8c7-fcbb802419a2n%40googlegroups.com.