On Wed, Apr 06, 2022 at 08:59:09AM -0700, Vasanth Mohan wrote:
> I'm building a PoC for a multi-tenant app where I'm trying to use the same
> schema across multiple databases with Django instance. I've got a couple of
> questions and I'd be happy to have some input
>
> 1. Is there a way to defin
It won't be in 1.0. It's only really been kicked off recently, so you'll
have to wait a while :-)
2008/7/21 CPF_ <[EMAIL PROTECTED]>:
>
> Ben Ford wrote:
> > Hi There,
> >
> > It has been possible in the past to use multiple databases with
> > django. There was a branch for it and about a year ag
Have a look a this http://code.djangoproject.com/ticket/4747 &
http://trac.woe-beti.de/
On 21 juil, 03:04, CPF_ <[EMAIL PROTECTED]> wrote:
> Ben Ford wrote:
> > Hi There,
>
> > It has been possible in the past to use multiple databases with
> > django. There was a branch for it and about a year a
Ben Ford wrote:
> Hi There,
>
> It has been possible in the past to use multiple databases with
> django. There was a branch for it and about a year ago it was bought
> up to date with trunk. However that branch hasn't seen any activity
> for some time and is effectively dead. There's now a (lo
Hi There,
It has been possible in the past to use multiple databases with django.
There was a branch for it and about a year ago it was bought up to date with
trunk. However that branch hasn't seen any activity for some time and is
effectively dead. There's now a (low key) effort under way to come
[EMAIL PROTECTED] wrote:
> Dan wrote:
>>
>> Most ideally we would like to have it so that the application
>> uses DB1
>> (defined in the settings.py file) as the main database, but when
>> it's
>> down to users, uses DB2.user as the users table.
>> Currently we are thinking of us
Dan wrote:
>
> Most ideally we would like to have it so that the application uses DB1
> (defined in the settings.py file) as the main database, but when it's
> down to users, uses DB2.user as the users table.
> Currently we are thinking of using raw sql, but that would only be a
>
> Most ideally we would like to have it so that the application uses DB1
> (defined in the settings.py file) as the main database, but when it's
> down to users, uses DB2.user as the users table.
> Currently we are thinking of using raw sql, but that would only be a
> last resort preferably. And at
You can use the multi-db branch as is and use it for a different app for
each db if you want as per the instructions. However you'll lose a lot of
the recent functionality from trunk that way. I'd suggest checking out trunk
at r 6100 and then patching against that. Contact me off list and I'll send
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 produced a patch against trunk at around r61
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 very regularl
11 matches
Mail list logo
