I've been using the multi db branch of Django successfully for three
years on one of my projects...works great
On Apr 15, 8:03 pm, RaviKondamuru <[EMAIL PROTECTED]> wrote:
> Hi,
> I am intending to use two different databases. Essentially retrieve
> some data from a remote database and have some
I'm working on ticket #1142
(http://code.djangoproject.com/ticket/1142): "Support for multiple
database connections." I'm putting together on a prototype which I'll
attach to the ticket (as a patch with some rough documentation) that
you could test. I'm going to be careful not to promise when it
Hi,
I am intending to use two different databases. Essentially retrieve
some data from a remote database and have some data in the local
database. Is such configuration supported in Django? Any pointers to
such configuration possibility?
thanks,
Ravi.
--~--~-~--~~~---~-
On Dec 13, 10:54 am, birkin <[EMAIL PROTECTED]> wrote:
> For one of my projects I import data from a non-django-controlled
> database using the MySQLdb python library, populate adjangomodel
> object and save it (to my app's django-controlled database table).
> Works smoothly.
I did something sim
Derek,
> ...If not, what should I be doing?
For one of my projects I import data from a non-django-controlled
database using the MySQLdb python library, populate a django model
object and save it (to my app's django-controlled database table).
Works smoothly.
http://sourceforge.net/projects/mys
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
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
Please also have a look at ticket #4747. It was/is an effort to bring
multi db a little bit closer to trunk. Regrettably, I have not had the
time (nor the need) to continue working on this.
Good luck.
Koen
On 12 dec, 16:25, Derek Steinkamp <[EMAIL PROTECTED]> wrote:
> Thanks for the link, it is
Thanks for the link, it is very helpful. I see the last attachments are
the docs committed by you -- I'll be giving those a read here shortly.
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
There is a Multiple Database Branch which is not under active
development...and doesn't have some of the new stuff in the
trunk...but I'm using it in one of my projects...works pretty good for
the most part.
http://code.djangoproject.com/wiki/MultipleDatabaseSupport
On Dec 11, 2:48 pm, Derek Ste
I read through all the relevant documentation but I couldn't find any
info on an issue I am about to face: accessing multiple tables in
different databases with Django.
Here's a quick example:
My Django app (MyApp) has r/w access to the MyApp database on
MySQLserver1, and all of MyApp models l
t and I'll send
you the patch if you want it. Note that I haven't used the patch yet.
Ben
On 18/09/2007, msoulier <[EMAIL PROTECTED]> wrote:
>
>
> On Sep 17, 11:00 pm, "Ben Ford" <[EMAIL PROTECTED]> wrote:
> > Hi Mike,
> > There is a branch that supp
On Sep 17, 11:00 pm, "Ben Ford" <[EMAIL PROTECTED]> wrote:
> Hi Mike,
> There is a branch that supports multiple databases in the repository. It's
> quite out of date in the SVN repo but Koen put in some stirling work over
> the period of the sprint and produce
Hi Mike,
There is a branch that supports multiple databases in the repository. It's
quite out of date in the SVN repo but Koen put in some stirling work over
the period of the sprint and produced a patch against trunk at around r6100.
Multiple-db support is a feature that is asked for
I was hoping to use Django in a web management UI for a server that I
support, where new UIs are added as new applications are installed.
Due to this plugin requirement, I had planned to model that with one
large Django project, where each new plugin was a Django application.
Unfortunately it wou
Hi Guys,
I'm in the middle of the latest set of updates (the merge of the
oracle branch with trunk), the only thing left to do is sort out the
core.management module (68 conflicts!!). I should have that cracked by
the end of today and it would be great to get it checked in so others
could help wit
On 6/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Ben Ford is working on merging in changes from the trunk in with the
> branch... at this time neither he or myself ( I had planned on doing
> this but found he was farther ahead of me ) have commit permissions to
> the project... but hopef
... someone will give him permissions to commit.
On Jun 25, 3:19 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On 6/25/07, grassoalvaro <[EMAIL PROTECTED]> wrote:
>
>
>
> > Anyone? That was greate idea but i see that last update was long time
> > ago...
On 6/25/07, grassoalvaro <[EMAIL PROTECTED]> wrote:
>
> Anyone? That was greate idea but i see that last update was long time
> ago... i need multiple databases in my project so if anyone know
> anything about this (maybe own solutions in this area?) please inform
> me.
>
Anyone? That was greate idea but i see that last update was long time
ago... i need multiple databases in my project so if anyone know
anything about this (maybe own solutions in this area?) please inform
me.
On Jun 24, 6:14 pm, grassoalvaro <[EMAIL PROTECTED]> wrote:
> Is that projec
Is that project dead or maybe still unofficial supported?
--~--~-~--~~~---~--~~
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
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
I have two legacy databases which I can connect to
django separately without problems. I would like to read data from
one, wrangle the data a bit, and write them to the other.
How would I go about that, given that, as I understand it, I can
import the settings only once. I would seem that in prin
Hi, I was wondering if the feature is fully supported yet.
I have more than one existing "legacy" database that I would like to
support from the same Django instance.
How do I safely bring the Django tables into each database? Do you run
syncdb on an empty copy, then add your tables, then importd
Hi all,
Forgive me if this has been asked, but I went through both -users and
-developers and couldn't see anything similar.
So - is it possible to run django across multiple databases? The
project I'm working on at the moment has some rather
distinct/incompatible data sets, and I&#
201 - 239 of 239 matches
Mail list logo
