On Tue, May 13, 2008 at 12:01 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> I realize how the aggregates work, but if annotate is just for
> aggregates, then remove it as a standalone method. If it's not, then
> it should solve all the problems with one blow.
Pardon?
Annotate and aggregate
I realize how the aggregates work, but if annotate is just for
aggregates, then remove it as a standalone method. If it's not, then
it should solve all the problems with one blow.
On May 12, 4:37 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Mon, May 12, 2008 at 10:50 PM, David Cramer
Hey, just saw the update, and my suggestions would be, instead of
using round() figure out how many places of congruency there are
between the backends and use the ... syntax instead.
For example if:
pgsql: 37.4697
sqlite: 37.4701
mysql: 37.47
just print out
37.4...
On May 12, 6:37 pm, "Russell
I just dropped my code base on a Debian box that has python 2.4
installed and started encountering deepcopy errors on count()
queries. Looks like there's already a bug for this: #7204. This
seems like a pretty serious bug, hence mentioning it here. For what
it's worth, I don't have these errors
On Mon, May 12, 2008 at 10:50 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> What is the difference between annotate and aggregate? They seem like
> they'd do the same thing, except annotate sounds like it should be
> doing GROUP BY,
I don't mean to be rude, David, but the difference between
My assumption was annotate was the equiv of GROUP BY, which is what
annotate sounds like :)
If that's the case, I believe annotate should also replace distinct(),
as it is very very similar in its use-cases.
On May 12, 12:05 pm, koenb <[EMAIL PROTECTED]> wrote:
> If I understand it correctly, th
If I understand it correctly, the aggregate and annotate ideas are
result driven, not by the SQL that might be involved (which should
indeed be entirely hidden). Aggregate normally gives one result,
annotate gives you a bunch of objects, but with extra information PER
object (normally from an aggr
Thank you for taking the time to respond. I'm probably just not being
very clear.
In Satchmo, there is a view that uses an .rml (ReportLab Markup
Language) to generate a PDF file and return it to the client. This
.rml file is a Django template -- it has Django template markup and is
run through t
On Mon, 2008-05-12 at 10:44 -0400, Joshua 'jag' Ginsberg wrote:
> I know it's an obscure and rather inane question, but if one of the
> developers would take a moment to comment, I'd be appreciative.
> Thanks!
>
> -jag
>
> On Thu, May 8, 2008 at 3:33 PM, Joshua 'jag' Ginsberg
> <[EMAIL PROTECTED
What is the difference between annotate and aggregate? They seem like
they'd do the same thing, except annotate sounds like it should be
doing GROUP BY, which, if that's the case, then this goes against the
very reasoning which a group_by or something similar should not be
used. The logic in the i
I know it's an obscure and rather inane question, but if one of the
developers would take a moment to comment, I'd be appreciative.
Thanks!
-jag
On Thu, May 8, 2008 at 3:33 PM, Joshua 'jag' Ginsberg
<[EMAIL PROTECTED]> wrote:
> Is there a technical reason why django.template.loader.make_origin
>
Is there any interest on the developers part of getting Django to
accept request parameters through the WSGI handler that, if found,
would override any settings in the main environment on a per-request
basis?
This was wrote about in another thread and would help me greatly in
getting Django to ru
12 matches
Mail list logo
