On 21 Mai, 15:50, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Fri, May 16, 2008 at 9:27 PM, Adrian R. <[EMAIL PROTECTED]> wrote:
>
> > Okay, so I've got some additional information for you which are
> > hopefully useful for you. I've
Okay, so I've got some additional information for you which are
hopefully useful for you. I've tried to switch to the dev version but
I don't think that I'm on the right way right now.
So, here the SQL-code which generates the database view:
SELECT tr.*, tp.TestPlanName,
(SELECT IF(COUNT(Produ
On May 15, 3:12 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> First off: support for GROUP BY, SUM and other aggregation functions
> is a work in progress. The new QS-RF code contains placeholders to
> hold GROUP BY statements, but there isn't a public API to get a GROUP
> BY into your qu
On 14 Mai, 17:44, "Scott Moonen" <[EMAIL PROTECTED]> wrote:
> Adrian, disregard my previous question (you're using your own paginator).
>
> Does your paginator use len(set) or does it use set.count() to determine the
> number of items? You should find that the latter has much better
> performance
On 14 Mai, 16:36, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> On May 14, 2008, at 9:26, "Adrian R." <[EMAIL PROTECTED]>
> wrote:
>
> > the problem is as faras I understood it, that the view is first
> > processed completely in the
> > database before
On 14 Mai, 16:18, "Scott Moonen" <[EMAIL PROTECTED]> wrote:
> Adrian, are you displaying all 30,000 entries on the same page? Or are you
> using some sort of pagination?
No, they aren't on the same page and I'm using pagination (and the
result can be filtered by different fields), but the proble
Hello Django developers,
I'm new to this mailing list and I hope that I didn't fail completely
by searching the django groups while I was considering to discuss this
on the list:
At the moment (like since 1.5 years) I'm working on a web interface
which is used to control some options for a softw
