On Thursday, 10 October 2013 15:19:32 UTC+1, Ramiro Morales wrote:
>
>
> On Oct 10, 2013 10:02 AM, "Arnaud Delobelle"
> wrote:
> >
> > Hi Russ,
> >
> > Thanks for the feedback. I agree that this could possibly be integrated
> into the values() method. I just used a new
On Oct 10, 2013 10:02 AM, "Arnaud Delobelle" wrote:
>
> Hi Russ,
>
> Thanks for the feedback. I agree that this could possibly be integrated
into the values() method. I just used a new method in order to minimise
interference with our existing code. I'll read the
Hi Russ,
Thanks for the feedback. I agree that this could possibly be integrated
into the values() method. I just used a new method in order to minimise
interference with our existing code. I'll read the 'contributing' document
then see if I can find a bit of spare time to do this properly!
Hi Arnaud,
I can see value in the feature you're describing here.
>From a design perspective, my question would be whether a whole new method
is needed, or whether it could be integrated into the existing values()
method. There will be some complications around the 'flat' key, but its
worth
Hi there,
I quite often find that when using queryset.values() I would like to be
able to define myself the values of the keys, especially when they span
models:
e.g.
my_query_set.values('foo__bar__baz', 'quux',
'another__long__field__name')
Then I end up with dictionaries with
5 matches
Mail list logo