>However, I don't like it if it's going to be introduced as a scaling
>solution; I'd rather have the various tiers of infrastructure (load
>balancing at the front, application in the middle, database in the
>back) remain as loosely coupled as possible.
Absolutly, scaling is the last reason to int
James Bennett wrote:
>
> I like multiple-backend support for the express purpose of doing
> things like having one set of objects in a MySQL DB over *here* and
> another set in an Oracle DB over *there*, or whatever. I hope no-one
> would ever create such a configuration when starting a new proje
On 3/21/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> Actually, the availability of connection splitting/pooling tools for
> various backends makes me less inclined to want to add it to Django,
> but that's all academic now :)
I like multiple-backend support for the express purpose of doing
Hi,
>Seriously, though -- this is obviously a very cool feature and one
>that would be AWESOME to have. Even better would be able to access
>the same object from multiple databases...
I _think_ this could be done based on the managers - actually that's
what we discussed some time earlier. The o
+2 on the idea of supporting multiple backends. Its a huge feature gap
which effects usability of the framework quiet severly. As for the
"how" I think it needs some very carefull thought as the current django
model is the global settings file it would have to have multiple setups
in there, and po
On Mar 21, 2006, at 3:43 PM, Ian Holsman wrote:
> you might also want to split reads/writes up as well.
>
> one thing i investigated was doing this in the DB layer with a tool
> called sequoia http://carob.continuent.org/LibMySequoia
> It emulates a mysql client, but you can sequoia how to divide
I think support should be added for accessing multiple databases in one
application/project. In the current organization where I work, I may have
two databases to work with, one Oracle and one MySQL. I think this would
be pretty easy to setup, it would just need to look like this:
class ObjectF
On 3/22/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On Mar 21, 2006, at 3:13 PM, Alan Bailey wrote:
> > I think support should be added for accessing multiple databases in
> > one application/project.
>
> Me too!
you might also want to split reads/writes up as well.
one thing i investiga
On Mar 21, 2006, at 3:13 PM, Alan Bailey wrote:
> I think support should be added for accessing multiple databases in
> one application/project.
Me too!
> I think this would be pretty easy to setup, it would just need to
> look like this:
Awesome -- should I expect a patch today, or tomorro