I hadn't really received any response from any active developers in the project on this... but was slowly attempting to do the merge with the trunk.... I spoke to Ben via email... waiting to hear back from him to verify where he was on the merge, as it sounds as though he has already got the merge further along than I have... the day after I started working on it, our network got hacked at our office... which caused a big ruckus... then my deadline got pushed back....so I haven't had as much time to devote to it as I had hoped. Anyways... I'm going to try and collaborate with Ben on this, since appears he has already gotten farther.
It would be nice if someone might tell either myself or Ben, how we would go about getting the merged code committed, once it's been completed and tested.... or do we just submit it as a patch or something on the wiki page for this branch? On Jun 6, 1:02 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > A few weeks back there was a discussion about providing support for > alternative database usage scenarios in Django and around that time > another userCaroleZieler(carole.zieler) had offered to do some > maintenance on the branch. I don't think she ever received a response > back and subsequently has struck out on her own to update the multi-db > branch. I'd suggest getting in contact so as not to duplicate > efforts. > > On Jun 5, 9:34 am, JP <[EMAIL PROTECTED]> wrote: > > > I replied to Ben via email, but for the group, again: multi-db needs a > > new maintainer. I don't have the time to keep up with merging it, let > > alone to add new features or complete the documentation. I think Ben > > has some excellent ideas here and would be a great maintainer > > candidate. > > > JP > > > On Jun 5, 12:27 am, "Ben Ford" <[EMAIL PROTECTED]> wrote: > > > > Hi JP, > > > I've been using your multiple-db-support for sometime now and i wondered > > > if > > > you are still actively developing it? I have a couple of > > > suggestions/queries > > > to do with a few of my specific needs and I would guess those of others... > > > There are a couple of tickets about this on trac, but I might try and do > > > some bits independently so I wanted to ask for your feedback... > > > - I'd really like if I could define a FK relationship that spans > > > databases, at present that will work but the backwards relationship is > > > broken and it throws a validation error. > > > - I'd like this 'spanning foreignkey' to not break the django ORM... > > > so > > > that Model.objects.filter(fk_class__column='whatever') would still work. > > > I'm guessing that this would be quite a lot of work... Probably consisting > > > of: > > > - A new type (or types) of Field, perhaps OtherDBForeignKey or > > > something > > > > - A new type of descriptor for each of these new field types > > > - Some new logic in django.db.models.query to catch the case of a db > > > spanning relationship and split the queries up > > > - Finally some way to build the sql so that it looks like SELECT > > > [columns,] from first_table where pk in (list_of_pk_values); the list will > > > be generated from a separate query as a result of splitting the queries up > > > in the last step. > > > What do you think about the amount of work that would be needed to get all > > > this working? > > > As an aside i have a copy of multiple-db-support that I've merged with > > > trunk > > > as of rev 5371, it might be good to get this checked into django so other > > > people can work on it, if there's still any interest... > > > Thanks in advance, > > > Ben > > > > -- > > > Regards, > > > Ben Ford > > > [EMAIL PROTECTED] > > > +628111880346 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
