Thanks Russ,
I'll checkout the database router feature.
Regards,
Bill
On Jan 25, 2010, at 6:53 AM, Russell Keith-Magee wrote:
> As of r12272 (committed about three days ago), the best approach to
> this problem is to define a database router that directs queries on a
> particular object type
Hi all,
Given the new multi-db implementation, I put together a couple of little
"helper" classes to make app specific, or model specific databases really easy.
Please consider the following and let me know if you think this is too abusive
of the internals of the multi-db implementation. Any
Hi all,
One of the use cases that may be common for multiple database support is being
able to combine multiple Django applications that require different databases
into a single site. This is exactly what I need to do for one project. This
can be done with the new multiple database suppor
On Jan 17, 2010, at 6:54 PM, Russell Keith-Magee wrote:
> As far as I'm aware, that's exactly what should be happening. If you
> retrieve an object from 'other', the object should retain an internal
> state that indicates that it came from 'other', and subsequent
> database operations (including
Hi all,
I'm new to the group, so my apologies if this has been discussed
already.I have some serious reservations about the implementation
of the "default" database in the new multi-db support feature.
Anytime you obtain a model from a given database (with the "using"),
shouldn't any operati
