On Tue, Nov 17, 2009 at 3:19 AM, Warren Smith wrote:
> On Fri, Nov 13, 2009 at 8:06 PM, Russell Keith-Magee
> wrote:
>>> Would it make sense to factor out the connection selection logic into
>>> a utility function with parameters that make it usable in all
>>> contexts, thus yielding a single pla
On Fri, Nov 13, 2009 at 8:06 PM, Russell Keith-Magee
wrote:
>> The dynamic population of settings.DATABASES can happen at login time.
>> I can use a statically configured alias as a template, just replacing
>> the username and password. This new alias can be stored with a name
>> like '@' and se
On Sat, Nov 14, 2009 at 4:31 AM, Warren Smith wrote:
> On Thu, Nov 12, 2009 at 5:17 PM, Russell Keith-Magee
> wrote:
>>> 1. Retrieve the credentials from the session.
>>> 2. Create a new, or update an existing, entry for those credentials in
>>> the database configuration.
>>> 3. Somehow ensure t
On Thu, Nov 12, 2009 at 5:17 PM, Russell Keith-Magee
wrote:
>> 1. Retrieve the credentials from the session.
>> 2. Create a new, or update an existing, entry for those credentials in
>> the database configuration.
>> 3. Somehow ensure that the using() operator is used on all ORM operations.
>
> Th
On Fri, Nov 13, 2009 at 2:28 AM, Warren Smith wrote:
> On Wed, Nov 11, 2009 at 5:08 PM, Russell Keith-Magee
> wrote:
>> Multi-db allows you to set up multiple database credentials; the usual
>> reason for this is to split DB load across multiple database servers,
>> but I don't see any reason you
On Wed, Nov 11, 2009 at 5:08 PM, Russell Keith-Magee
wrote:
> Multi-db allows you to set up multiple database credentials; the usual
> reason for this is to split DB load across multiple database servers,
> but I don't see any reason you couldn't also use it to provide
> multiple connections to a
On Thu, Nov 12, 2009 at 6:20 AM, Warren Smith wrote:
>
> If this question would be more appropriate for django-users, please
> let me know. I ask it here because I suspect that the answer to my
> question may require someone with a fairly deep understanding of the
> ORM internals.
>
> I have a l
If this question would be more appropriate for django-users, please
let me know. I ask it here because I suspect that the answer to my
question may require someone with a fairly deep understanding of the
ORM internals.
I have a legacy oracle database that I would like to use with the
Django ORM.
