[GSOC] Multi-DB Update

2009-08-04 Thread Alex Gaynor
Hey all, This week I implemented the metaclass based solution for backwards compatibility in the Field API that Jacob suggested last week. Then I implemented by first stab at a solution to the Oracle/backend with custom query object problem. However, I don't have access to any of the the DBs I'

[GSOC] Multi-DB Status Update

2009-07-24 Thread Alex Gaynor
Hey all, I didn't get a ton of code written this week, however I have a very clearly laid out plan for how to handle custom Query classes now. It's my goal to get the code written and done this weekend while I'm at PyOhio (if you're in the Columbus area please come on out, it promises to be a gre

[GSOC] Multi-DB Update

2009-07-19 Thread Alex Gaynor
Hey all, This week I made the final major API changes, updating the get_db_prep_* methods to recieve connection, and work in a backwards compatible method. I also fixed the bug with using __in=queryset.using('other_db'), right now it raises an exception, but in the future I'll update it to just

[GSOC] Multi-DB Status Update

2009-07-03 Thread Alex Gaynor
Hey all, This week was fairly productive. I got a lot of good docs done this week, as well as implementing the using option in the inner Meta class. For this next week I'm writing up a detailed account of the last API changes that multi-db will need. Specifically with resepect to get_db_prep_*,

[GSOC] Multi-DB Update

2009-06-29 Thread Alex Gaynor
Hey all, This past week unfortunately wasn't super eventful. I did some final dead code elimination on my m2m-refactor branch, I was able to kill about 150 additional lines of code that no longer needed, there are a few small changes I need to make to remove some quadratic behavior that occurs du

[GSOC] Multi-DB Status Update

2009-06-20 Thread Alex Gaynor
Hey all, This past week I mostly finished off the m2m-refactoring work this week as well as fixing a few bugs Russ spotted in the multi-db code. For this next week I think I'm going to be working almost exclusively on docs, as Russ's wife just had a baby so I think spamming him with source code t

[GSOC] Multi-DB Update

2009-06-15 Thread Alex Gaynor
Hey all, Sorry about the delayed update, wanted to touch base with my mentor on a few small issues before firing this off. I spent last week augmenting ManyToManyFields to use a full Model internally, so we can remove some hard coded SQL. I've been doing this on a separate branch since it's a fa

[GSOC] Multi-DB Status Update - Week 2

2009-06-05 Thread Alex Gaynor
Hey all, This has been a productive week for multiple database support in Django. Firstly I got all my original work into Django's SVN repository, in more-or-less atomic commits (they weren't perfect, but unfortunately most of the early work was anything but linear). Secondly all tests are now pa

[GSOC] Multi-DB Status Update - Week 1

2009-06-01 Thread Alex Gaynor
Hey All, Sorry about the delayed updated, I got busy on Friday and then I had the dash through the weekend. During the last week I implemented multiple database support for transactions (which was necessary to solve the postgres DDL problems I mentioned last week). I got this ton and have gradua

Re: [GSOC] Multi-DB Week 0 Update

2009-05-24 Thread Russell Keith-Magee
On Sat, May 23, 2009 at 12:06 PM, Alex Gaynor wrote: > And I didn't actually finish writing before sending grand... > > So the issue is one of the remaining 1.1 tickets, > http://code.djangoproject.com/ticket/9964 , has patches that rewrite > basically all of the transaction handling code.  Can a

Re: [GSOC] Multi-DB Week 0 Update

2009-05-22 Thread Alex Gaynor
And I didn't actually finish writing before sending grand... So the issue is one of the remaining 1.1 tickets, http://code.djangoproject.com/ticket/9964 , has patches that rewrite basically all of the transaction handling code. Can anyone comment on whether those patches are likely to be represen

[GSOC] Multi-DB Week 0 Update

2009-05-22 Thread Alex Gaynor
Hey all, GSOC is officially scheduled to start tomorrow (my time), however I've take the liberty of getting quite a jump on my work (as I described last week). During this week I got the save using parameter and using queryset method, these are fairly untested however. The reason for this was aft

[GSOC] Multi-DB Status Update - Week 0

2009-05-16 Thread Alex Gaynor
Hi all, I officially began work this week (for some value of officially that doesn't include the official GSOC project starting :) ). I've had good success in getting a lot of the ground work laid, specifically I got the connections object in, updated a bunch of management commands for a --databa

Re: [GSOC] Multi-DB Status Update

2009-05-08 Thread Joey Wilhelm
Hi Alex, On Fri, May 8, 2009 at 16:04, Alex Gaynor wrote: > Hello All, > > I've spent the past week at EuroDjangocon, and as such I've had the > opportunity to discuss multi-db stuff with a bunch of very smart people. > Simon and I resolved the issue of DSNs vs. dicts (as long as Simon can > dyn

[GSOC] Multi-DB Status Update

2009-05-08 Thread Alex Gaynor
Hello All, I've spent the past week at EuroDjangocon, and as such I've had the opportunity to discuss multi-db stuff with a bunch of very smart people. Simon and I resolved the issue of DSNs vs. dicts (as long as Simon can dynamically add a new DB he's happy). Otherwise nothing has changed. Pers

Re: [GSOC] Multi-DB Update

2009-05-01 Thread Mike Panchenko
I would agree with you on the dict issue, given that some of the backends have custom settings etc. I also agree that this is not really something that matters now - DSNs will need to be parsed into dicts anyway, so you might as well implement the dicts first and then see what the demand is for DS

[GSOC] Multi-DB Update

2009-05-01 Thread Alex Gaynor
Hi all, Not a lot of new news or progress. I'll be at EuroDjangoCon all of next week so I may be starting my work there, depending on the status of 1.1. The only new news was Simon and I discussed switching to a DSN string in place of the dict of settings. Personally I'm -1 on that as I find the

Re: [GSOC] Multi-DB

2009-04-24 Thread Alex Gaynor
On Sat, Apr 25, 2009 at 2:21 AM, Richard S wrote: > when done is this giong to be as simple as adding installed apps to one DB > or the other? > > On Fri, Apr 24, 2009 at 11:11 PM, Alex Gaynor wrote: > >> >> >> On Sat, Apr 25, 2009 at 2:01 AM, Russell Keith-Magee < >> freakboy3...@gmail.com> wrot

Re: [GSOC] Multi-DB

2009-04-24 Thread Richard S
when done is this giong to be as simple as adding installed apps to one DB or the other? On Fri, Apr 24, 2009 at 11:11 PM, Alex Gaynor wrote: > > > On Sat, Apr 25, 2009 at 2:01 AM, Russell Keith-Magee < > freakboy3...@gmail.com> wrote: > >> >> On Wed, Apr 22, 2009 at 1:45 AM, Alex Gaynor >> wro

Re: [GSOC] Multi-DB

2009-04-24 Thread Alex Gaynor
On Sat, Apr 25, 2009 at 2:01 AM, Russell Keith-Magee wrote: > > On Wed, Apr 22, 2009 at 1:45 AM, Alex Gaynor > wrote: > > Hello All, > > > > As you know by now I've been selected to work on multiple database > support > > in Django as a part of the Google Summer of Code. I'm going to try to > k

Re: [GSOC] Multi-DB

2009-04-24 Thread Russell Keith-Magee
On Wed, Apr 22, 2009 at 1:45 AM, Alex Gaynor wrote: > Hello All, > > As you know by now I've been selected to work on multiple database support > in Django as a part of the Google Summer of Code.  I'm going to try to keep > this brief as a) not much of my API thoughts have changed since my origin

Re: [GSOC] Multi-DB

2009-04-21 Thread Malcolm Tredinnick
On Tue, 2009-04-21 at 16:36 -0400, Alex Gaynor wrote: > > > On Tue, Apr 21, 2009 at 4:29 PM, Malcolm Tredinnick > wrote: > > On Tue, 2009-04-21 at 15:46 -0400, Alex Gaynor wrote: > > > > > > On Tue, Apr 21, 2009 at 3:14 PM, Malcolm Tredinnick > >

Re: [GSOC] Multi-DB

2009-04-21 Thread Alex Gaynor
On Tue, Apr 21, 2009 at 4:29 PM, Malcolm Tredinnick < malc...@pointy-stick.com> wrote: > > On Tue, 2009-04-21 at 15:46 -0400, Alex Gaynor wrote: > > > > > > On Tue, Apr 21, 2009 at 3:14 PM, Malcolm Tredinnick > > wrote: > > [...] > > > > Postponing any real decision making (at the code le

Re: [GSOC] Multi-DB

2009-04-21 Thread Malcolm Tredinnick
On Tue, 2009-04-21 at 15:46 -0400, Alex Gaynor wrote: > > > On Tue, Apr 21, 2009 at 3:14 PM, Malcolm Tredinnick > wrote: [...] > > Postponing any real decision making (at the code level -- I'm > not > talking about the human level) makes things a lot more >

Re: [GSOC] Multi-DB

2009-04-21 Thread Alex Gaynor
On Tue, Apr 21, 2009 at 3:14 PM, Malcolm Tredinnick < malc...@pointy-stick.com> wrote: > > On Tue, 2009-04-21 at 13:45 -0400, Alex Gaynor wrote: > > Hello All, > > > > As you know by now I've been selected to work on multiple database > > support in Django as a part of the Google Summer of Code.

Re: [GSOC] Multi-DB

2009-04-21 Thread Malcolm Tredinnick
On Tue, 2009-04-21 at 12:14 -0700, Malcolm Tredinnick wrote: > On Tue, 2009-04-21 at 13:45 -0400, Alex Gaynor wrote: [...] > > 1) Make sure absolutely no tests are done against self.connection > > before the SQL is actually sent to the database(currently this occurs > > in the Where node, amongs

Re: [GSOC] Multi-DB

2009-04-21 Thread Malcolm Tredinnick
On Tue, 2009-04-21 at 13:45 -0400, Alex Gaynor wrote: > Hello All, > > As you know by now I've been selected to work on multiple database > support in Django as a part of the Google Summer of Code. I'm going > to try to keep this brief as a) not much of my API thoughts have > changed since my or

[GSOC] Multi-DB

2009-04-21 Thread Alex Gaynor
Hello All, As you know by now I've been selected to work on multiple database support in Django as a part of the Google Summer of Code. I'm going to try to keep this brief as a) not much of my API thoughts have changed since my original proposal, and b) Django 1.1 is getting ready to leave the fa