Re: query values() calls don't use transforms as filter() does

Thanks Tim, This is a great addition, maybe I can do what I want with that (I'll have to think about it) but what I was hoping for is more within the lookup string itself. A simple example (this is simplified from a stack overflow question I posted on this topic before I started poking around

Re: query values() calls don't use transforms as filter() does

I merged support for expressions in values() a few hours ago: https://github.com/django/django/commit/39f35d4b9de223b72c67bb1d12e65669b4e1355b If that doesn't meet your needs, can you give an idea of what the QuerySet you want would look like? On Thursday, August 18, 2016 at 5:10:41 PM UTC-4, R

query values() calls don't use transforms as filter() does

I noticed that the jsonb field indexing in postgres which is so handy in filtering does not seem to extend to calls to values(). After digging around a bit, it seems that sql.query.get_transform() is only called when building a filter, but not when adding fields for a values call. Using transf