> The problem is that people pop up every couple weeks and ask precisely
> the sort of thing you're asking: in effect, "what's the status of
> this, and when will it land in trunk". The answers to these questions
> haven't changed in a very long time; what's needed is people writing
> code, not pe
On 11/17/07, ElegSub <[EMAIL PROTECTED]> wrote:
> We will disagree about the accuracy of that statement but your
> response is by far the most clear and succinct response to this
> question yet. Thank you.
The problem is that people pop up every couple weeks and ask precisely
the sort of thing yo
On Nov 17, 8:06 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> All you're doing is asking the same questions as in previous threads.
> How does that inject clarity?
We will disagree about the accuracy of that statement but your
response is by far the most clear and succinct response to th
On Fri, 2007-11-16 at 18:03 -0500, Elegantly Subtle wrote:
> There's no real decisive answer to this recurring question so
> hopefully this will inject some clarity into the discussion...
All you're doing is asking the same questions as in previous threads.
How does that inject clarity?
> Wha
There's no real decisive answer to this recurring question so
hopefully this will inject some clarity into the discussion...
What is the current status of Multiple Database support in Django?
What is the timeline for integration of Multiple Database support in
the trunk?
The current ticket
