On Tue, Jun 10, 2008 at 11:33 PM, Gary Wilson Jr. <[EMAIL PROTECTED]> wrote:
>
> Nicolas E. Lara G. wrote:
>> I was wondering if there was some sort of design decision on this or
>> was just not implemented (yet).
>
> I would say it just hasn't been implemented yet.
I note that ValuesQuerySet.ite
Nicolas Lara wrote:
> The ticket is in the tracking sistem: #7256. I have claimed it, but am
> not planning to start working on it until I'm done with aggregation
> (or maybe in EuroPython's sprint), so if anybody bits me to it, it
> would be great.
>
>
In that case you would be better off leav
The ticket is in the tracking sistem: #7256. I have claimed it, but am
not planning to start working on it until I'm done with aggregation
(or maybe in EuroPython's sprint), so if anybody bits me to it, it
would be great.
On Wed, Jun 11, 2008 at 12:33 AM, Gary Wilson Jr. <[EMAIL PROTECTED]> wrote
Nicolas E. Lara G. wrote:
> I was wondering if there was some sort of design decision on this or
> was just not implemented (yet).
I would say it just hasn't been implemented yet.
> Adding the fields to appear in the dictionary seams like an easy fix
> that
> I might do while working on aggregat
That came quite unreadable... a translation here: (sorry for the
noise)
"""
Hello,
While doing some test cases for aggregates I came across the fact that
extra() does not play well with values().
For example, though
>>> Book.objects.all().extra(select={'price_per_page' : 'price /
>>> pages'}).
Hello,Book.objects.all().extra(select={'price_per_page' : 'price /
pages'}).values('price_per_page').get(pk=1)
While doing some test cases for aggregates I came across the fact that
extra() does not play well with values(). For example: though
Book.objects.all().extra(select={'price_per_page' : '
