Instead of trying to dynamically change the manager used for reverse
relations or any manager/queryset (either by getting and then throwing
away the default manager, or some other method), or applying manual
filters to achieve the same result, there is another alternative.
Instead of:
{{{
reporte
Hi all,
I don't know if using the queryset's hypothetical use_manager() method
would be the right approach to the reverse manager problem. In fact,
I'm not entirely happy with the current manager() proposal either: it
feels very much like an after-the-fact change to the default manager.
That's how
On Jan 16, 7:00 pm, Javier Guerra Giraldez wrote:
> On Mon, Jan 16, 2012 at 11:46 AM, Anssi Kääriäinen
>
> wrote:
> > I have been investigating what takes time in Django's test runner and
> > if there is anything to do about it. The short answer is: yes, there
> > is a lot of room for improvement
On Mon, Jan 16, 2012 at 11:46 AM, Anssi Kääriäinen
wrote:
> I have been investigating what takes time in Django's test runner and
> if there is anything to do about it. The short answer is: yes, there
> is a lot of room for improvement. I managed to reduce the running
> speed of the test suite (on
I have been investigating what takes time in Django's test runner and
if there is anything to do about it. The short answer is: yes, there
is a lot of room for improvement. I managed to reduce the running
speed of the test suite (on sqlite3) from 1700 seconds to around 500
seconds. On postgresql I
