I'll give the merging a shot...then try and see about getting it
committed... it might take me a few weeks...since it's my initial
voyage through the Django code base, and subversion branches, etc
plus I still have tons of deadlines at work on top of that :)
At anyrate...when I get all of the
Hi carole.zieler,
I posted a reply to you earlier but don't see it here so I guess it
went to the groups twilight zone. Anyway I was just saying I'm glad
to hear you are having success with the current state of the multidb
branch. I've used it as a proof of concept but am hesitant to run
with i
I've just posted over in django-dev that I'm intersted in taking over
maintenance of this branch ... I'm not to skilled with subversion...
but I'm going to go ahead and give it a shot, and attempt over the
next two weeks ( out of town for a few days on vacation ) to merge the
changes to the trunk
I've also seen a lot of demand for the multi-db support; however, I do
understand the time that this would take to get updated, stabilized,
and worked into trunk. I have several apps I would like to work on
where I need to pull data from a couple legacy databases
(datawarehouse type dbs), but thi
Hi Russ,
Thanks for the detailed response and I agree with all of your
sentiments. You're doing a great job and you are a tremendous asset
to this list. Keep up the great work.
Having been a committer to other framework projects, I understand the
constant pressure to integrate feature X,Y, and
On 5/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I'm using the multi-db branch actively on a large project I have
> found a few bugs, but am uncertain if they are specific to the branch
> or if are also found in the trunk, as I haven't ever installed the
> trunk.
>
> I would like to
On 5/2/07, Brian Luft <[EMAIL PROTECTED]> wrote:
>
> Although I've successfully used the multi-db branch experimentally, it
> looks to be getting more and more out of date with the django trunk.
...
> Just for the sake of lively discussion, I would go so far as to say
> that only being able to acc
I'm using the multi-db branch actively on a large project I have
found a few bugs, but am uncertain if they are specific to the branch
or if are also found in the trunk, as I haven't ever installed the
trunk.
I would like to try and take on maintenance of the branch...but am
unsure of how to
Although I've successfully used the multi-db branch experimentally, it
looks to be getting more and more out of date with the django trunk.
I do completely understand the desire of the django devs to ensure a
solid commitment to a branch and also that there have not been enough
requests to drive i
That looks very interesting, Michal. Thank you very much. As soon as I have
some time I will try it out. (My original problem went away by itself,
but I am sure
this will come in handy sometime.)
Ewout
--~--~-~--~~~---~--~~
You received this message because you ar
I had an data import task for django application. Client moved data
from several databses into new one. All legacy databases had same
model, so there was proper django model created for them. And I had
problem with importing data from all those legacy system. I've sniffed
a bit and on the base of
> Anyway, back to the question: do think there is a way with standard django
> to access two databases (maybe sequentially, changing database connections)
> in one script? Or is the only way to use intermediate storage like a file?
The simplest way I can think of is to write your own SQL to acce
On 3/3/07, Ewout ter Haar <[EMAIL PROTECTED]> wrote:
>
> Anyway, back to the question: do think there is a way with standard django
> to access two databases (maybe sequentially, changing database connections)
> in one script? Or is the only way to use intermediate storage like a file?
I can't t
> You need to read what Jacob said. The condition for multi-db being
> accepted into trunk is for someone to take control of it - not just
> for the immediate term (finishing docs, etc), but for the medium to
> long term (maintenance of the code).
I understand. For branches which are not supporte
On 3/3/07, Ewout ter Haar <[EMAIL PROTECTED]> wrote:
> I read this as saying that that the multi-db will never be incorporated
> in trunk, because even if all the bugs would be worked out, even if there
> would be documation, etc, etc, there is no commiter that wants to maintain
> it. If it will n
15 matches
Mail list logo
