Re: Ability to migrate other applications

[Emmanuelle Delescolle]

Quote from Russ Magee's Twitter 

> Django 1.9 is coming - do you have something on your wishlist? DSF Fellow 
> Tim Graham has an offer for you: groups.google.com/d/msgid/django…


Well, actually, I'd  really like this for 1.9 ;-)

Has anyone +1's for this or is it more like -1's ?


> Sample project is available at 
> https://bitbucket.org/emma_nuelle/migrate_othe_app_sample. Django branch 
> is at https://github.com/nanuxbe/django/tree/migrate_other_app <-- current 
> test suite seems to pass fine (at least on my computer) just missing new 
> tests if actual PR has to be made
>


Cheers,
Emma 

-- 
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/33698862-4fe0-4d43-aadc-c970719f5bda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Improving MSSQL and Azure SQL support on Django

[Meet Bhagdev]

Hi Russ,Tim
That is a great idea. I am going to try to engage with the team at 
Microsoft who is in charge of the sponsorship. I plan on attending the 
conference so I will see some of you there. 

@Tim: I agree that a lot of ground work needs to be done in terms of 
testing out the current third party adapters and deciding which one/ones 
should we adopt and extend. I know Michael Manfre has a lot of expertise 
here. I will do my due diligence and test out the existing solutions but if 
Michael could share some of his findings, that would be great. If anyone 
else also wants to take a stab at testing and using the existing adapters 
for a sample app, that would be great as well. I will try to share my 
learnings soon.

Here are the ones I am going to test, am I missing any?

1. Django-mssql 

2. Django-pymssql 

3. Django-pyodbc-azure 

4. Django-pyodbc 

Thanks,
Meet

That is a great idea. I am going to try to get hold of 
On Monday, August 31, 2015 at 4:58:40 PM UTC-7, Russell Keith-Magee wrote:
>
> Hi Tim, Meet 
>
> I know this is very late to be mentioning, but one idea that worth 
> raising: DjangoCon US is next week (in Austin). Thursday and Friday 
> are coding sprints, where there will be many people (including a good 
> chunk of the core team) looking for projects to hack on. 
>
> Microsoft is already a sponsor of DjangoCon itself; if we can get some 
> engineers from the Azure team (assuming there aren't already some 
> coming), we can start some of this prep work. 
>
> Yours, 
> Russ Magee %-) 
>
> On Tue, Sep 1, 2015 at 3:46 AM, Tim Graham  > wrote: 
> > To arrive at the best solution, I think a lot of discussion needs to 
> happen 
> > on this mailing list before October. As for me, besides the name of some 
> > existing packages that offer SQL Server/Azure support, I know very 
> little 
> > about the current landscape so I really wouldn't have anything to offer 
> in a 
> > discussion, but there are others on this list who definitely do. 
> > 
> > The existing Microsoft database backends have come out of specific 
> developer 
> > needs and I think it would maximize success if your team were personally 
> > invested  in the backend by building a Django application backed by SQL 
> > Server/Azure. If I were a Microsoft engineer responsible for this 
> project, I 
> > would start by building a small Django application to solve some problem 
> > that my team has. Then I would test it out with all the third-party 
> backends 
> > for Microsoft databases previously mentioned to get a feel for how they 
> > work. I should learn enough to at least participate in a discussion with 
> > other Django developers about the direction of this project. Ideally, I 
> > would be able to learn enough to write up a Django Enhancement Proposal 
> [1] 
> > that summarizes the landscape and describes what an "official solution" 
> > should look like. 
> > 
> > If you are relying on members of the Django team to do all this upfront 
> > work, then please tell us so we can see if someone will do it. If you 
> are 
> > expecting to get all this done in a couple days in Seattle, this doesn't 
> > seem feasible to me. However, if we have a working proposal by 
> mid-September 
> > that the community can review and give feedback on, then I think our 
> time 
> > together in October could be productive. I don't know anything about the 
> > background of your team, but it seems pretty unlikely that any sort of 
> > coding sprint would be useful unless the work and learning I described 
> > happens well before the workshop. 
> > 
> > [1] https://github.com/django/deps/ 
> > 
> > 
> > On Monday, August 31, 2015 at 3:07:28 PM UTC-4, Meet Bhagdev wrote: 
> >> 
> >> Hi Tim, 
> >> Thanks for bringing it up. Yes, we will have developers who will engage 
> >> with Django developers (like yourself) during the workshop. 
> >> 
> >> The goals of the October workshop are to: 
> >> 
> >> 1)  Get to know each other and begin building a relationship 
> >> 
> >> 2)  Get in a room with Microsoft developers and discuss the current 
> >> landscape 
> >> 
> >> 3)  Work on half day coding sprint(s) with Microsoft developers to 
> get 
> >> started with contributions 
> >> 
> >> 4)  Establish a plan for how Microsoft can best contribute to 
> Django, 
> >> and ensure we have great integration between Azure SQL and MSSQL and 
> Django 
> >> by maintaining our contributions 
> >> 
> >> 
> >> The key takeaway is that we want to contribute to existing solutions to 
> >> improve the Django and MSSQL/Azure SQL story. To do so we want to 
> understand 
> >> the current landscape, the gaps, and the next steps to make this happen 
> (the 
> >> right way). 
> >> 
> >> 
> >> We are currently in the planning stages and would love to get feedback. 
> >> What d

Re: Improving MSSQL and Azure SQL support on Django

[Meet Bhagdev]

Hi Russ,Tim
That is a great idea. I am going to try to engage with the team at 
Microsoft who is in charge of the sponsorship. I plan on attending the 
conference so I will see some of you there. 

@Tim: I agree that a lot of ground work needs to be done in terms of 
testing out the current third party adapters and deciding which one/ones 
should we adopt and extend. I know Michael Manfre has a lot of expertise 
here. I will do my due diligence and test out the existing solutions but if 
Michael could share some of his findings, that would be great. If anyone 
else also wants to take a stab at testing and using the existing adapters 
for a sample app, that would be great as well. I will try to share my 
learnings soon.

Here are the ones I am going to test, am I missing any?

1. Django-mssql 

2. Django-pymssql 

3. Django-pyodbc-azure 

4. Django-pyodbc 

Thanks,
Meet

On Monday, August 31, 2015 at 4:58:40 PM UTC-7, Russell Keith-Magee wrote:
>
> Hi Tim, Meet 
>
> I know this is very late to be mentioning, but one idea that worth 
> raising: DjangoCon US is next week (in Austin). Thursday and Friday 
> are coding sprints, where there will be many people (including a good 
> chunk of the core team) looking for projects to hack on. 
>
> Microsoft is already a sponsor of DjangoCon itself; if we can get some 
> engineers from the Azure team (assuming there aren't already some 
> coming), we can start some of this prep work. 
>
> Yours, 
> Russ Magee %-) 
>
> On Tue, Sep 1, 2015 at 3:46 AM, Tim Graham  > wrote: 
> > To arrive at the best solution, I think a lot of discussion needs to 
> happen 
> > on this mailing list before October. As for me, besides the name of some 
> > existing packages that offer SQL Server/Azure support, I know very 
> little 
> > about the current landscape so I really wouldn't have anything to offer 
> in a 
> > discussion, but there are others on this list who definitely do. 
> > 
> > The existing Microsoft database backends have come out of specific 
> developer 
> > needs and I think it would maximize success if your team were personally 
> > invested  in the backend by building a Django application backed by SQL 
> > Server/Azure. If I were a Microsoft engineer responsible for this 
> project, I 
> > would start by building a small Django application to solve some problem 
> > that my team has. Then I would test it out with all the third-party 
> backends 
> > for Microsoft databases previously mentioned to get a feel for how they 
> > work. I should learn enough to at least participate in a discussion with 
> > other Django developers about the direction of this project. Ideally, I 
> > would be able to learn enough to write up a Django Enhancement Proposal 
> [1] 
> > that summarizes the landscape and describes what an "official solution" 
> > should look like. 
> > 
> > If you are relying on members of the Django team to do all this upfront 
> > work, then please tell us so we can see if someone will do it. If you 
> are 
> > expecting to get all this done in a couple days in Seattle, this doesn't 
> > seem feasible to me. However, if we have a working proposal by 
> mid-September 
> > that the community can review and give feedback on, then I think our 
> time 
> > together in October could be productive. I don't know anything about the 
> > background of your team, but it seems pretty unlikely that any sort of 
> > coding sprint would be useful unless the work and learning I described 
> > happens well before the workshop. 
> > 
> > [1] https://github.com/django/deps/ 
> > 
> > 
> > On Monday, August 31, 2015 at 3:07:28 PM UTC-4, Meet Bhagdev wrote: 
> >> 
> >> Hi Tim, 
> >> Thanks for bringing it up. Yes, we will have developers who will engage 
> >> with Django developers (like yourself) during the workshop. 
> >> 
> >> The goals of the October workshop are to: 
> >> 
> >> 1)  Get to know each other and begin building a relationship 
> >> 
> >> 2)  Get in a room with Microsoft developers and discuss the current 
> >> landscape 
> >> 
> >> 3)  Work on half day coding sprint(s) with Microsoft developers to 
> get 
> >> started with contributions 
> >> 
> >> 4)  Establish a plan for how Microsoft can best contribute to 
> Django, 
> >> and ensure we have great integration between Azure SQL and MSSQL and 
> Django 
> >> by maintaining our contributions 
> >> 
> >> 
> >> The key takeaway is that we want to contribute to existing solutions to 
> >> improve the Django and MSSQL/Azure SQL story. To do so we want to 
> understand 
> >> the current landscape, the gaps, and the next steps to make this happen 
> (the 
> >> right way). 
> >> 
> >> 
> >> We are currently in the planning stages and would love to get feedback. 
> >> What do you think about the goals mentioned above? Is there an