Dear all
I have a requirement to integrate the multiple database using mongodb is
this possible to integrate the
multiple database with mongodb and if possible then whats the process
involved in this process
Regards
Shvam Taneja
--
You received this message because you are subscribed to the
Hi Lee,
There's been a lot of historic discussion about multi-database support, and
the upshot is that no it isn't supported well right now. There's a branch in
SVN, but it's pretty much defunct. I believe the current thinking is to use
SQLAlchemy if you need to access other databases (try
Hello,
I seen some code in trak for multiple db support. Is this something
that is usable now, is there some documentation on it? I have my app
that mainly interacts with mysql but I need to pull some data from a
mssql database for specific reasons, is this possible or should i just
use
I thought this *was* the last one that was asked :)
On Nov 7, 4:01 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Nov 8, 2007 7:00 AM, Josh <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hi!
>
> > Has there been any more progress toward getting themultipledatabase
> > branch merged into trunk?
Hi!
Has there been any more progress toward getting the multiple database
branch merged into trunk? I, among many others, would really like to
be able to use the newer features of django and access multiple
databases from the same project...
Thanks!
Josh
On Oct 17, 12:03 am, koenb <[EMAIL
Hi There,
I've had similar problems and it comes down to the line in query.py that
looks in backend and sets QuerySet to _QuerySet or backend.QuesrySet if
there is one... I've also written some code to mitigate against this, and
I'd suggest anyone with an interest gets together on this so that
Thanks Koen! I will try the patch.
On Oct 17, 12:03 am, koenb <[EMAIL PROTECTED]> wrote:
> Hi Mark,
>
> You can find some newer work at ticket #4747. The patches there are
> some work in progress trying to bring multi-db back in line with
> trunk.
> A lot has changed in trunk in the last year,
On Oct 17, 1:29 pm, Carlos Hanson <[EMAIL PROTECTED]> wrote:
> On Oct 17, 12:33 am, koenb <[EMAIL PROTECTED]> wrote:
>
> > In the latest patches for multi-db the QuerySet that is returned is no
> > longer fixed, but varies with the model's manager. That should fix
> > that problem for now.
>
> >
On Oct 17, 12:33 am, koenb <[EMAIL PROTECTED]> wrote:
> In the latest patches for multi-db the QuerySet that is returned is no
> longer fixed, but varies with the model's manager. That should fix
> that problem for now.
>
> Koen
I've installed the latest patches for multi-db agains revision
In the latest patches for multi-db the QuerySet that is returned is no
longer fixed, but varies with the model's manager. That should fix
that problem for now.
Koen
On 17 okt, 09:03, Ian <[EMAIL PROTECTED]> wrote:
> I don't know anything about the multi-db branch, but I imagine that
> whatever
Hi Mark,
You can find some newer work at ticket #4747. The patches there are
some work in progress trying to bring multi-db back in line with
trunk.
A lot has changed in trunk in the last year, so I think it is worth
trying those out instead of the old branch. Off course there are still
a lot of
On Oct 16, 6:38 pm, Carlos Hanson <[EMAIL PROTECTED]> wrote:
> I am having trouble with Django revision 6110 patched with multi-
> db-6110.patch.
>
> Traceback (most recent call last):
> File "", line 1, in ?
> File "/usr/local/lib64/python2.4/site-packages/django/db/models/
> query.py", line
Sorry Carlos,
those patches are far from complete, and I don't use Oracle myself.
For the moment the backends in the patches use the following to get
the connection:
connection = self.model._default_manager.db.connection
Removing the import and putting in that line should do the
I am having trouble with Django revision 6110 patched with multi-
db-6110.patch.
Traceback (most recent call last):
File "", line 1, in ?
File "/usr/local/lib64/python2.4/site-packages/django/db/models/
query.py", line 108, in __repr__
return repr(self._get_data())
File
Hi,
I need to support multiple database connections in our Django
application.
One option being considered is to use the multi-db branch at
http://code.djangoproject.com/svn/django/branches/multiple-db-support
which is already in alpha release.
However by examining the code, it seems the
On 1/10/06, Greg <[EMAIL PROTECTED]> wrote:
> So I hacked
> DatabaseWrapper.quote_name so that it doesn't quote periods, but is
> that the "right" way to handle this or is it an ugly hack? It seems to
> work very well, but it feels like it might be cleaner to add a
> db_schema attribute or
I'm faced with the multiple-schema problem in MySQL, which AFAICT is a
lot simpler than actually having multiple databases because at least
you don't have to coordinate multiple connections. Actually, it
basically already works. I wrote
class Poll(meta.Model):
class META:
db_table =
On Friday 30 Dec 2005 5:12 am, hugo wrote:
> So, yes, I do think it would be very useful for Django to be able
> to access multiple databases via it's ORM
incidently, we need support for postgres schemas also - i have an
Financial Accounting app where, in multi-company mode, the tables
for
>I've always though that this particular -- and common -- use case
>should be delegated to the DB level using one of the many excellent
>replication/distribution tools for your database. For example, you
>could easily do read distribution with pg_pool or sqlrelay, and it
>would be transparent to
On 29 Dec 2005, at 20:29, Jacob Kaplan-Moss wrote:
I've always though that this particular -- and common -- use case
should be delegated to the DB level using one of the many excellent
replication/distribution tools for your database. For example, you
could easily do read distribution
On Dec 29, 2005, at 9:10 AM, Adrian Holovaty wrote:
... or would you be doing more of a standard setup,
in which you'd want database reads to be spread evenly across multiple
DBs? Go ahead and explain the setup, and we can get started on
designing the feature.
I've always though that this
On 12/29/05, Scott johnson <[EMAIL PROTECTED]> wrote:
> Now I haven't hacked Django much myself yet (I've been working on the back
> end tools, db loader and overall schema). What support does Django have for
> multiple db stuff?
Hey Scott,
Welcome!
Django doesn't support multiple DBs out of
Hello, *Long time lurker; first time poster*. My partner and I are standarizing on Django / Python for the front end of www.ookles.com, our new startup. We're both php folk and I've convinced him that Django is better than ruby (based, honestly, on my respect for Simon and Adrian rather than a
23 matches
Mail list logo
