On Feb 18, 2008 7:10 PM, Grindizer <[EMAIL PROTECTED]> wrote: > > Hi everybody. > > We are actually trying to use Django multi-db support for internal > need in our group. We used this branch because we have historical > constraint (we build a Django app over an old db application which use > several databases) ... > So do you thing that it is a good idea to continue using this branch > for a real project ?
First off, this isn't a question for django-developers. Django-developers is for answering questions about the development of Django itself - user queries (how do I/should I type questions) should be directed to django-users. However, that said: the decision to use multi-db is entirely up to you, your capabilities and your expectations. The short answer is "probably not". Multi-db isn't part of the Django core. Nor is it one of the branches targeted for inclusion in v1.0 (those two branches are newforms-admin and queryset-refactor). This means that while it may be a useful feature (for some - certainly not me personally), multi-db isn't an immediate priority for the Django core developers. The branch has not been updated for some time - this is because the original maintainer has not been updating the branch. A number of people have offered to help maintain the branch. If you read the mailing list that refer to multi-db, you will find a consistent response - you don't need commit access to work on this branch, just work on the ticket in your own SVN checkout and upload tickets that implement the changes required by the branch. A number of people have gone down this path, and ticket #4747 has been the ticket where the patches congregate. However, these patches are currently 5 months and almost 800 revisions behind trunk at present. Last I heard, there were still many issues to be resolved, and I suspect that the upcoming queryset-refactor merge will cause all sorts of headaches for this branch. If you are willing to take on the challenge of handling any bugs that you find, and managing the merge process for any new features from trunk that you want, then you will be able to use multi-db. However, if you're just looking for a tool to use 'no questions asked', multi-db probably isn't the way to go. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
