Hi folks, I was going to keep quiet on this until I was a bit further along... I've just started work on re-hashing multiple-db support to make it a bit more flexible. The existing code is quite hard to update with trunk as it makes a lot of changes to django's core codebase. I've also found it a little hard to work with in some more complicated contexts. (I'm not knocking it at all, it just doesn't quite do it for me). So in the spirit of "scratch your own itch" I'm going to have a play with it.
I wasn't going to mention it until I was further along, for two reasons: One that I didn't want to add more noise to this topic - it seems to rear it's head all on it's own fairly regularly! Two, I'm not really sure how much time I can commit to this - I'm just on my way back to the UK after an absence of nearly 2.5 years so I have a lot of catching up to do!! I will however do my best and will update with my progress (and some docs) at some usable point in the future. Cheers, Ben On 13/12/2007, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > > On Dec 13, 2007 12:25 AM, Derek Steinkamp <[EMAIL PROTECTED]> wrote: > > > > As an aside, I think it is a real showstopper to not include this > > feature in the main trunk... I can't believe the triage stage on the > > feature request was recently changed to "Someday/Maybe". To me it seems > > obvious that all of the data that a Django app could need might not > > reside on the same database for any number of reasons. > > It may well be a real showstopper - for you. Is it a showstopper for > everyone? Not even close. To date, I have never had a need for > multi-db support. There are a large number of Django sites out there > that are successfully deployed without support for multi-db. > > If multi-db were to magically materialize in the Django source tree, > would it be a valuable addition? Yes, certainly. Hence, the > "Someday/Maybe" tag. > > The "Someday/Maybe" tag is an indication that we (that is, the core > developers) are not opposed to introducing this feature, but it's not > on our immediate to-do list. At the moment, the big issues consuming > our time are things like: > * Completing the transition to newforms, thereby resolving the issues > with edit_inline and core=True > * Refactoring the query engine to resolve the myriad known issues with > order_by, select_related, and table joins > > Whereas multi-db is of interest to _some_ users, edit_inline and join > issues affect virtually _all_ users. Developer time is limited, so we > have to prioritize, and the issues that will be addressed first are > those that: > > 1) affect the most people. > 2) affect the core developers personally. > > Using this scheme, multi-db falls quite some way down the to-do list. > > > Perhaps I'll put some work into this when I have some time and get it > > caught up with the latest trunk. > > If multi-db support is important to you, then this is the most helpful > thing you can do. > > Yours, > Russ Magee %-) > > > > -- Regards, Ben Ford [EMAIL PROTECTED] +6281317958862 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
